Why Document Management Isn't Enough and Why PLM is Required using Aras by Razorleaf

1,655 views
1,513 views

Published on

Why Document Management Isn't Enough and Why PLM is Required using Aras by Razorleaf

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,655
On SlideShare
0
From Embeds
0
Number of Embeds
150
Actions
Shares
0
Downloads
30
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Why Document Management Isn't Enough and Why PLM is Required using Aras by Razorleaf

  1. 1. ACE 2011 InternationalWhy Document Management Why Document ManagementIsn’t Enough g Eric Smith, Razorleaf www.Razorleaf.com aras.com
  2. 2. Agenda History Lesson Defining BOM Management fi i Why Change? How BOM Management Works Organizational Impact O i ti lI t Example aras.com
  3. 3. aras.com
  4. 4. Learning from Abiogenesis The simple model ‘life spontaneously develops out of nothing’ There was evidence But there were contradictions Louis Pasteur The complex model Microbiology • …which yielded germ theory and vaccinationsSometimes the complex answer is better aras.com
  5. 5. aras.com
  6. 6. PLM and Abiogenesis Document Mgmt is like abiogenesis Simple/basic model Easily understood Well accepted BOM Mgmt is like microbiology and germ theory Complex l Better model of realitySometimes the complex answer is better aras.com
  7. 7. Part ManagementPart Management Document Management Document Management aras.com
  8. 8. Part ManagementPart Management Document Management Document Management aras.com
  9. 9. BOM ManagementBOM Management Document Management Document Management + aras.com
  10. 10. Why Change? Drawing Revision is insufficient: Describing status and maturity with revisions is hard Describing status and maturity with revisions is hard ev XA.1 XA 1 XA.2 XA 2 XE.1 XE 1 XE.2 XE 2DeProto XA XB XC XE XF od C D FPro aras.com
  11. 11. Why Change?Drawing Revision is insufficient: Describing status and maturity Describing status and maturity Change stacking A B C DDCN A1 DCN B1 DCN C1 DCN D1DCN A2 DCN C2 DCN D2DCN A3 aras.com
  12. 12. Why Change? Drawing Revision is insufficient: Describing status and maturity Describing status and maturity Change stacking N parts on 1 drawing N parts on 1 drawing 444 A 999 A 444 B 999 A 35353 A 35353 B ? SUPPLIER aras.com
  13. 13. Why Change? CAD is a barrier to collaboration CAD = Top Secret protection? CAD = Top Secret protection? aras.com
  14. 14. Why Change? CAD is a barrier to collaboration CAD = Top Secret protection? CAD = Top Secret protection? aras.com
  15. 15. Why Change? CAD is a barrier to collaboration CAD = Top Secret protection? CAD = Top Secret protection? What do people use to collaborate instead? aras.com
  16. 16. Why Change? Added flexibility “Model” products quickly Model products quickly Avoid non‐value‐add during change • Mass note updates p • Full ECx approvals for clerical fixes aras.com
  17. 17. How Does It Work? Separate Parts from Documents Parts get their own identifiers (PN and Rev) 1001 Rev 1.01 1001-01 Rev A 9990 Rev 1 aras.com
  18. 18. How Does It Work? Separate Parts from Documents Parts get their own identifiers (PN and Rev) Parts get their own maturity 1001 Rev 1.01 Released R l d 1001-01 Rev A Prototype 9990 Rev 1 In Process aras.com
  19. 19. How Does It Work? Separate Parts from Documents Parts get their own identifiers (PN and Rev) Parts get their own maturity Parts and Documents get Rev specific links 1001 Rev 1.011001-01 Rev A Released Prototype 9990 Rev 1 In Process 1001 R 5 Rev 1001-01 Rev D Released Production 9990 Rev 3 Released aras.com
  20. 20. How Does It Work? Part maturity models reality, relates to Document  maturity Part states: • Development = in development, not ready to be made • Prototype = you can make one but design isn’t vetted Prototype = you can make one, but design isn t vetted • Approved = design finalized • Production = ready to be made in volume • Superseded = only for legacy product support • Inactive = not to be made evelopment Superseded Prototype Approved Production Inactive SDe aras.com
  21. 21. How Does It Work? Part maturity models reality, relates to Document  maturity Part states: Development, Prototype, Approved,  Production, Superseded, Inactive, etc. Related Document maturity rules: • Can’t promote to Approved until Documents are all Released • Can’t change linked Docs after Part reaches Approved state aras.com
  22. 22. How Does It Work? Part maturity models reality, relates to Document  maturity Part states: Development, Prototype, Approved,  Production, Superseded, Inactive, etc. Related Document maturity rules Part maturity rules, too: • Minimum child state (Approved Parts can’t have Temporary  children) • Production Parts must have Production children Production Parts must have Production children aras.com
  23. 23. How Does It Work? Engineering Change operates on Parts, Documents,  or Both or Both Simple design change • Rev Document, Rev Part aras.com
  24. 24. How Does It Work? Engineering Change operates on Parts, Documents,  or Both or Both Simple design change • Rev Document, Rev Part Broad design improvement • Rev Document, Mass Change Parts aras.com
  25. 25. How Does It Work? Engineering Change operates on Parts, Documents,  or Both or Both Simple design change • Rev Document, Rev Part Broad design improvement • Rev Document, Mass change Parts Upgrade design using other existing designs • Rev Parts Only aras.com
  26. 26. How Does It Work? Engineering Change operates on Parts, Documents,  or Both or Both Simple design change • Rev Document, Rev Part Broad design improvement • Rev Document, Mass Change Parts Upgrade design using other existing designs • Rev Parts Only Fix non‐substantive error Fi b i • Rev Document, Adjust Part aras.com
  27. 27. How Does It Work? Engineering Change operates on Parts, Documents,  or Both or Both Non‐conformances, Deviations, and other processes  operate on Parts, Documents, or Both operate on Parts, Documents, or Both aras.com
  28. 28. Organizational Impact People will hate this “Too complicated” Too complicated “More work” “Systems can’t handle it” Systems can t handle it aras.com
  29. 29. Organizational Impact People will hate this Reality? The situation is complicated People are already doing this work People are already doing this work Systems need to be updated to support business  p processes aras.com
  30. 30. Organizational Impact People will hate this Reality? Bonus – roles become clearer I never understood why a Buyer had to approve a spelling  fix The Drafter owns the drawing, not the Engineering  The Drafter owns the drawing not the Engineering Manager Who owns the drawing, Manufacturing or Engineering? aras.com
  31. 31. Organizational Impact Communication improves From: “Can you find me the drawing for ” Can you find me the drawing for… To: “I can find my own drawings now.” From: “I wish I could have seen what you guys were  planning earlier in the process” To: “Check the system to see my idea” y y From: “I don’t understand what happened on this ECO,  can you explain it to me? can you explain it to me?” To: “I see the affected and replacement Parts, and also  which Documents changed.” aras.com
  32. 32. Organizational Impact Product data now has a center‐of‐gravity It never made sense to link everything to the Drawing It never made sense to link everything to the Drawing You can link everything to the Part: • Drawings g • 3D models • Material specs • CNC code • Tooling drawings & models • Calculations & analysis Calculations & analysis • Assembly instructions aras.com
  33. 33. Scenario Preview Time Parts Documents aras.com
  34. 34. ScenarioEngineer with a new Engineer with a newidea creates a 3D modelPart created as Temporary while the concept is reviewed aras.com
  35. 35. ScenarioSpecifying drawing Specifying drawingcreatedPart set as “pending” and given part number aras.com
  36. 36. ScenarioSpecifying drawing Specifying drawing Inactive I tiapproved ActivePending Part  Released Apromoted to state  A Pending“released” A Temporary Promote Demote 1 1 1 1 1 Inactivate Revise 1 3D Model 1 2D Drawing 1 Approved 1 Obsolete aras.com
  37. 37. ScenarioProblems found during Problems found duringtooling developmentNew revision needed for PartPart rev A made “inactive” inactiveOld drawing made obsoleteNew 3D and 2D prepared aras.com
  38. 38. ScenarioSpecifying drawing Specifying drawing Inactive I ti A Areviewed and  Activeapproved A B ReleasedPart rev B promoted  A B Pendingfrom “pending” to “released” Temporary A Promote Demote 1 1 1 1 1 1 1 1 1 Inactivate Revise 2 2 2 2 1 3D Model 2D Drawing 3 3 1 1 Approved 1 Obsolete aras.com
  39. 39. ScenarioTooling completedTooling completed Inactive I ti A A A BPart rev B promoted  Activefrom “released” to  Released A B“active” A B PendingProduction begins A Temporary Promote Demote 1 1 1 1 1 1 1 1 1 1 1 Inactivate Revise 2 2 2 2 2 2 1 3D Model 2D Drawing 3 3 3 1 1 Approved 1 Obsolete aras.com
  40. 40. ScenarioPart redesign initiated Part redesign initiated Inactive I ti A A A Afor cost savings  B B Activeprogram A B ReleasedNew revision needed  A B C Pending(rev C) A TemporaryNew 3D and 2D New 3D and 2D Promote Demoteprepared Inactivate Revise 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 1 3D Model 2D Drawing 3 3 3 3 1 1 Approved 4 3 1 Obsolete 5 aras.com
  41. 41. ScenarioNew 2D drawing New 2D drawing Inactive I ti A A A A Aapproved B B C B ActivePart rev C promoted  Released A Bfrom “pending”  A B C Pendingdirectly to “active” A Temporary2 revisions of the Part 2 revisions of the Part Promote Demotein production at one  Inactivate Revise 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2time 1 3D Model 2D Drawing 3 3 3 3 3 1 1 Approved 4 3 4 3 1 Obsolete 5 5 aras.com
  42. 42. ScenarioPart rev B demoted to Part rev B demoted to Inactive I ti A A A A A A“released” after  B B C B C Activeinventory depleted A B B Released A B C Pending A Temporary Promote Demote 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Inactivate Revise 2 2 2 2 2 2 2 2 2 2 2 2 1 3D Model 2D Drawing 3 3 3 3 3 3 1 1 Approved 4 3 4 3 4 3 1 Obsolete 5 5 5 aras.com
  43. 43. Scenario A A A A A A A Inactive B B B C C Active C A B B B Released A B C Pending A Temporary Promote Demote 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Inactivate Revise 2 2 2 2 2 2 2 2 2 2 2 2 2 2 1 3D Model 2D Drawing 3 3 3 3 3 3 3 1 1 Approved 4 3 4 3 4 3 4 3 1 Obsolete 5 5 5 5 aras.com
  44. 44. Thank YouEric S ithE i Smith www.Razorleaf.com Eric.Smith@Razorleaf.com 330.676.0022 x7135 aras.com

×