1 / 20

CM Spec analysis

CM Spec analysis. Markup from discussion 15/3 and 22/3. Summary of the 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.

umeko
Download Presentation

CM Spec analysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CM Spec analysis Markup from discussion 15/3 and 22/3 OSLC PLM workgroup workings

  2. Summary of the 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

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

  4. 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

  5. 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

  6. 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

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

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

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

  10. 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

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

  12. 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

  13. 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

  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. 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

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

  19. 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

  20. 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

More Related