what every change analyst should know - our experience with agile plm

7
What every Change Analyst should know - our experience with Agile PLM

Upload: gwenda-richard

Post on 31-Dec-2015

212 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: What every Change Analyst should know - our experience with Agile PLM

What every Change Analyst should know - our experience with Agile PLM

Page 2: What every Change Analyst should know - our experience with Agile PLM

Symmetricom

~$200M annual sales Two major and distinct markets Time, frequency, and synchronization 5 major divisions 6 major sites 5 time zones ~700 employees

Page 3: What every Change Analyst should know - our experience with Agile PLM

Agile and Symmetricom

Initial purchase in November 2007 Go-Live on Product Collaboration (design data) in

April 2008 Go-Live on Product Quality in March 2009 Version update project in October 2009 One way integration – Agile to Oracle ERP

Page 4: What every Change Analyst should know - our experience with Agile PLM

Current Use

All sites, all divisions – global tool Key workflows

ECO/PECO/CO – Change Orders for product PTR – Problem Tracking and Resolution for released

product CAPA – Corrective And Preventive Actions TDA – Temporary Deviation on released products,

including shipment authorization for unreleased LCO – Lifecycle Change Order – moves product from

one lifecycle status to another (e.g. Production to Service Only)

Page 5: What every Change Analyst should know - our experience with Agile PLM

Things That Make Life Easier

‘Workflow Routing’ tab as a to-do list Subscriptions to receive alert of a particular action Bookmarks to find frequently accessed information Use a status in workflows to confirm data transfer to ERP

before moving to status of ‘Complete’ Import from Excel spreadsheet to update item attributes Escalations send reminder notifications to approver or

manager after n hours/days

Page 6: What every Change Analyst should know - our experience with Agile PLM

Things To Watch Out For

Wrong workflow on change order When to use different change types / workflows Sequence of Revisions (e.g., ‘001’ is not the same as ‘1’) Clean up Notifications and Workflow Routing tab entries

(only limited number are displayed and refresh is faster) Using wrong change type to obsolete an item Attribute used on both change order and affected items has

mismatch in value (e.g., different product line on CO header and affected items)

Data not sync'd to ERP (if data is transferred to ERP)

Page 7: What every Change Analyst should know - our experience with Agile PLM

Q and A

Questions?????