OSLC PLM Spec analysis

1. OSLC PLM Spec analysis Consolidation from previous discussions 29/3 inc meeting notes OSLC PLM workgroup workings

2. Contents • Findings • Discussion about PLM Resource requirements • Reference information • Method • Notes captured during analysis OSLC PLM workgroup workings

3. Findings OSLC PLM workgroup workings

4. Findings summary OSLC PLM workgroup workings

5. Meeting notes 29/3 • Project context in PLM • Same resource referenced by many projects with access and control specification • Additional concerns re project concerns • Planning through to assignment to execution / implementation in development • Assume the “project” finishes with release from devt • E.g. CR/WIs • WBS • Assignable project resource • Progress tracking • RTC Project is a generalised grouping of WIs OSLC PLM workgroup workings

6. RM Spec analysis OSLC PLM workgroup workings

7. CR System or product context Req Implem Controlled config Requirement 1 of 2 OSLC PLM workgroup workings

8. CR System or product context Req Implem Controlled config Requirement 2 of 2 OSLC PLM workgroup workings

9. CR System or product context Req Implem Controlled config RM Context 1 of 2 OSLC PLM workgroup workings

10. CR System or product context Req Implem Controlled config RM Context 2 of 2 OSLC PLM workgroup workings

11. CM Spec analysis OSLC PLM workgroup workings

12. CR System or product context Req Implem Controlled config CM 1 of 2 OSLC PLM workgroup workings

13. CR System or product context Req Implem Controlled config CR 2 of 2 OSLC PLM workgroup workings

14. CR System or product context Req Implem Controlled config CR Context 1 of 2 OSLC PLM workgroup workings

15. CR classification is optional • Dcterms: subject OSLC PLM workgroup workings

16. CR System or product context Req Implem Controlled config CR Context 2 of 2 OSLC PLM workgroup workings

17. PLM Resource requirements OSLC PLM workgroup workings

18. Identity Change control PLM resource behaviour Version Associations Structural relationships Variability Structure relationships Structure relationships The resource shall provide product consistsof support The resource shall provide product coding and classification identity The resource shall provide relevant PLM behaviour The resource shall support product versions The resource shall provide product structure support The resource shall provide product includedin support The resource shall support associations to additional resources The resource shall notify subscribers of changes The resource shall support parametric variation PLM behaviour requirements of an OSLC resource OSLC PLM workgroup workings

19. Version Associations Structure relationships Structure relationships Structural relationships Specification Variability Change control PLM resource behaviour Identity The resource shall support product versions The resource shall notify subscribers of changes The resource shall provide product includedin support The resource shall provide product coding and classification identity The resource shall provide product consistsof support The resource shall support product The resource shall provide relevant PLM behaviour The resource shall support parametric variation The resource shall support associations to additional resources The resource shall provide product structure support PLM behaviour requirements of an OSLC resource – alt view OSLC PLM workgroup workings

20. Additional topics • Configuration of a resource as a “spec” • Location of one product resource from another • E.g. traverse structure • Lifecycle state change of a resource • Support for concurrency • Formal relationship with WBS OSLC PLM workgroup workings

21. Method applied OSLC PLM workgroup workings

22. We analysed the ability of the OSLC Specs to support scenario by way of the key business entities & their relationships Pre-condition (Before Is based upon or applies to* CR * Assuming basic triaging has been done prior to the start of the scenario At some context version V’ System or product context Controlled config Req Implem Post-condition (After Is implemented by At some new context version V’’ CR System or product context System or product context Controlled config Controlled config Req Implem Req Implem Updated to achieve the CR Updated to achieve the CR OSLC PLM workgroup workings

23. We posed questions and compared the OSLC Specs and the PLM Reference Model OSLC PLM workgroup workings

24. Workings OSLC PLM workgroup workings

25. CRs typically don’t exist stand alone • CR can be an enhancement or a correction or some combination • Prioritised for criticality, value • Grouped by impact area • Grouped and sequenced for effectivity • CRs need to be associated and managed (inc merge, split, superced OSLC PLM workgroup workings

26. Have today Need Identify in product and/or system context Heterogeneous problem list (of affected items) Heterogeneous solution list Enterprise approval Group, sequence, deprecate CR resource behaviour OSLC PLM workgroup workings

27. http://open-services.net/bin/view/Main/CmSpecificationV2 • Set of 6 states • “State predicate properties • Set of relationships • “Relationship properties: OSLC PLM workgroup workings

28. Working notes 22/3 • CR link to a context resource as opposed to defining a set of affected items ? • Core ? Separate Spec ? • Allow to query resource to see what is linked to a context resource • CR context is defined in the PLM Reference model • either as a resource for Item, Product or System or resolved to a View_Definition OSLC PLM workgroup workings

29. Additional comments 22/3 • How user engage with context e.g. to assign • How align or synchronise across tools ? OSLC PLM workgroup workings

30. AP233 Module 1042 • In the Project Mngmnt schema • Work request • id mand • Version mand • Purpose • Description (opt • Affected items • Number • Type • Status • Work Order • Authorisation for Work request OSLC PLM workgroup workings

31. PLM CR rel • Activity method assignment • Affected items assignment OSLC PLM workgroup workings

32. Version comments (noted item 15/3 • dcterms has today • Resource A “has versions of” Resource B • Resource B “is version of” Resource A • http://web.resource.org/rss/1.0/modules/dcterms/ OSLC PLM workgroup workings

33. CR Context discussion • How does the CR Spec allow a CR to carry PLM context info ? • What examples ? • CR identity • Affected product or system context • Configuration • Effectivity • Affected items / Problem list • CR Solution list • CR State OSLC PLM workgroup workings

34. Quick notes on AM Spec • This spec only defines one resource type allowing maximum flexibility • It follows the OSLC Core Spec OSLC PLM workgroup workings

35. Next steps at 22/3 • Additional look at AM Spec to support the scenario • Conclude and summarise findings across Core, RM, CM and AM • Discuss and summarise the context resource behaviour in the scenario • (How to propel fwd ? OSLC PLM workgroup workings

36. Backup / reference OSLC PLM workgroup workings

37. STEP supports PLM representation of System & Product decomposition e.g. AP233 OSLC PLM workgroup workings

38. PLM Reference model can be further built out to support model driven development Applied in the PLM Reference Model Base diagram from OMG OSLC PLM workgroup workings