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

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

3. OSLC PLM workgroup workings3 Findings

4. OSLC PLM workgroup workings4 Findings summary Support available Key shortfallSource CoreVersions Configuration identity RM for RequirementVersions Limited types of relationship links e.g missing isComposedby Configured set of requirements or baseline ? Tracelink Context as managed concept (project, product coding & classification Uses relationship Collection Project = collection of resources, with e..g common attribute CM for CRCR relationship network Ability to support CR state change AM for Implementation As Core Query link Jim’s remarks 29/3

5. OSLC PLM workgroup workings5 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

6. OSLC PLM workgroup workings6 RM Spec analysis

7. OSLC PLM workgroup workings7 Requirement 1 of 2 QuestionOSLC RM Spec 2.0 AnswerPLM Reference model Answer How is a requirement defined ?Requirement is a type. A Requirement resource has a shape which prescribe a set of mandatory attributes Three primary entities of Requirement, Requirement version and Requirement view definition How is a Requirement uniquely identified Globally by a URIBy an id within a context What determines the rules for representing a requirement ? Meta-model rules (RDF) Resource shape FILE_SCHEMA (('AP233_SYSTEMS_ENGINEERING_ARM_LF')); What is the visibility of the requirements description ? Global? Header includes the names, time stamp, org How is requirements meta-data defined ? E.g. organisational ownership Title is mandatory plus optional properties properties ? ID, name and description ? Validate the usage of the Req view definition (effectivity only ?) How is the relationship between collection and other resources ? A special named relationship properties is “uses” properties For requirements: #1230=REQUIREMENT_COLLECTION_RELATIONS HIP('','isComposedOf','',#720,#1220) “the descriptor isComposedOf is optional” How is the relationship between requirements and other resources defined ? Named relationship properties available for useproperties #10700=REQUIREMENT_VIEW_DEFINITION_RELA TIONSHIP('10700','DeriveReqt','DeriveReqt1',#3220,# 8720); How to version a requirement ?3 level structure with the version defined through the REQUIREMENT_VERSION CR Req Implem System or product context Controlled config

8. OSLC PLM workgroup workings8 Requirement 2 of 2 QuestionOSLC RM Spec 2.0 AnswerPLM Reference model Answer How are groups of Requirements organised ? Identifying as a group Treat as a group e.g. Approve, implement, assign to a block or an organisational unit as group e.g. a black box approach “satisfiedby” Short hand URI of the Requirements collection Dcterm: “Selected requirements for HSUV release XYZ” Can have a collection of collection etc A collection is looser grouping of elements that happen to have a common locator OSLC lacks the explicit “isComposedBy” SysML package holds the Requirements as a container (as opposed to a collection) Any sub-tree denotes a group The Requirements are defined in isolation within the scope of a package and then associations are made buy way of e.g. #4530=REQUIREMENT_COLLECTION_REL ATIONSHIP('','isComposedOf','',#820,#4520); SysML does not have an external class for composition Identify interdependency Uses: URI (not titles) (Uses is not well defined e.g. to mean “isComposedby” Uses is a reference to another resource (as opposed to the strong decomposition inherent in UML) Open set (not supported) Tracelink here e.g. for an external link #36=EXTERNAL_CLASS('http://www.omg.org/spec/SysML/Current/ SysML-profile#DeriveReqt','DeriveReqt','The "derive requirement" relationship relates a derived requirement to its source requirement.',#34); #38=EXTERNAL_CLASS('http://www.omg.org/spec/SysML/Current/ SysML-profile#Refine','Refine','The refine requirement relationship can be used to describe how a model element or set of elements can be used to further refine a requirement.',#34); #1230=REQUIREMENT_COLLECTION_RELATIONSHIP('','isComp osedOf','',#720,#1220) “the descriptor isComposedOf is optional and arbitrary isComposedOf is derived from the decomposition paradigm of SysMl modeling. CR Req Implem System or product context Controlled config

9. OSLC PLM workgroup workings9 RM Context 1 of 2 QuestionOSLC RM Spec 2.0 AnswerPLM Reference model Answer How is the root context defined ? (Using a tiering concept for context Service Provider (may not be the authority STEP Filename and date created (as a snapshot for data exchange Organisation ? Have parts been assigned to blocks ? What constrains the context description ? FILE_SCHEMA (('AP233_SYSTEMS_ENGINEERING_ARM_LF')); #20=ACTIVITY_METHOD('XSLT_Extract','XSLT Extract of STEP Part 21 Data File from Topcased SysML XMI','','For initial creation of dataset'); In what context is a requirement valid ? Valid everywhere Qualified by associations e.g. Query project name in a WI See above CR Req Implem System or product context Controlled config

10. OSLC PLM workgroup workings10 RM Context 2 of 2 QuestionOSLC RM Spec 2.0 AnswerPLM Reference model Answer How is project, product or system context defined ? e.g. a WI within a Jazz project as a proxy for a new System release ? e.g. a name or property of a baseline / cfg ? Identity, name and a version in reality this as an entry point to a config #23600=SYSTEM('23600','HybridSUV','HybridSUV System'); #23610=SYSTEM_VERSION('1','HybridSUV System Element Version',#23600); How is product & system coding and classification supported ? Not available except by tags or attributes to a thing – tags or attributes (see note below about requirements specifically Use the PRT or PRODUT or SYSTEM structure to define a taxonomy and then create associations How is a requirement associated with a project, product or system coding & classification ? Through a Requirement collection Query of link identified an external resource. E.g. a WI within a Jazz project for a new System release Or use attributes to explicitly hold tags e..g Rational, RM, Doors10 using dcterms:subject (today changing a tag changes a requirement) (lose ability to look at history as not separately maintained #114700=REQUIREMENT_ASSIGNMENT('114700','Satisfy3',#1820,#30120); Where the associated reference already sits in a system structure CR Req Implem System or product context Controlled config

11. OSLC PLM workgroup workings11 CM Spec analysis

12. OSLC PLM workgroup workings12 CM 1 of 2 QuestionOSLC CM Spec 2.0 AnswerPLM Reference model Answer How is a CR defined ?CR is a type. A CR resource has a shape which prescribe a set of mandatory attributes CR is not currently addressed in the PLM Reference Model. AP233 and AP239 have the possibility How is a CR uniquely identifiedGlobally by a URI. Within the service provider by a dcterms identifier within a given container scope (relative to) By a CR id within an enterprise or container scope (repository) What determines the rules for representing a CR ? CM Spec 2.0 Model rules (RDF) Resource shape per scenario (Create, Query, Instance state FILE_SCHEMA (('AP233_SYSTEMS_ENGINEERING_ARM_LF')); (To validate) What is the visibility of the CR description ? Global? Header includes the names, time stamp, org How is CR meta-data defined ? E.g. organisational ownership Title and identifier are mandatory plus optional properties defined by service provider properties In the PM Schema ID, name and description see Work Request / Work Order page How is the relationship between CR and other resources defined ? Named optional relationship properties available for use properties Activity method assignment Affected items assignment How to version a CR ?Dcterms: Modified date changes the http header etag ITEM & ITEM_VERSION associated with a VIEW_DESCRIPTION CR Req Implem System or product context Controlled config

13. OSLC PLM workgroup workings13 CR 2 of 2 QuestionOSLC CM Spec 2.0 AnswerPLM Reference model Answer How are groups of CR organised ? Identifying as a group Treat as a group e.g. Approve, implement, assign to a block or an organisational unit as group e.g. a black box approach “satisfiedby” Short hand By a common attribute or through association with say back to another OSLC resource like single Requirement oslc_cm:relatedChangeRequest (valid via tags e.g. oslc_cm:implementsRequirement OSLC lacks the explicit “isComposedBy” CRs can be grouped for implementation as a change activity and an effectivity AP239 has effectivity parameters Check in AP233 / AP239 Identify interdependency 3 types * related - Identifies a loose relationship between a Change Request and referenced resource. These relationships can be used to name associated resources managed by other service providers. * tracks - Identifies that a Change Request is used to track the lifecycle of referenced resource. From the CM tool perspective, these relationships can be used to track work that needs to be done for referenced resources. * affects - Indicates that the Change Request affects, has been predetermined to have impact, related resource. These property relationships can be used to understand the potential impact of referenced resources. Uses: URI (not titles) (Uses is not well defined e.g. to mean “isComposedby” Uses is a reference to another resource (as opposed to the strong decomposition inherent in UML) Open set (not supported) Tracelink here e.g. for an external link CR Req Implem System or product context Controlled config

14. OSLC PLM workgroup workings14 CR Context 1 of 2 QuestionOSLC CM Spec 2.0 AnswerPLM Reference model Answer How is the root context defined ? (Using a tiering concept for context Service Provider (may not be the authority STEP Filename and date created (as a snapshot for data exchange Organisation ? Have parts been assigned to blocks ? What constraints the CR context description ? CM Spec dcterms FILE_SCHEMA (('AP233_SYSTEMS_ENGINEERING_ARM_LF')); AP233 WORK REQUEST / WORK ORDER AP239 has "Work request identification code" (urn:plcs:rdl:std:Work request identification code) Task Set DEX "Work request name" (urn:plcs:rdl:std:Work request name) Task Set DEX #20=ACTIVITY_METHOD('XSLT_Extract','XSLT Extract of STEP Part 21 Data File from Topcased SysML XMI','','For initial creation of dataset'); In what context is a requirement valid ? Valid everywhere Qualified by associations e.g. Query project name in a WI See above CR Req Implem System or product context Controlled config

15. OSLC PLM workgroup workings15 CR classification is optional  Dcterms: subject

16. OSLC PLM workgroup workings16 CR Context 2 of 2 QuestionOSLC CM Spec 2.0 AnswerPLM Reference model Answer How is project, product or system context defined ? As a property named as affected items or reference Product or Product Version identity, as an extension; or a link to relevant context resource Identity, name and a version in reality this as an entry point to a config #23600=SYSTEM('23600','HybridSUV','Hybrid SUV System'); #23610=SYSTEM_VERSION('1','HybridSUV System Element Version',#23600); As a context linke.g relation from dcAs a resource for Item, Product or System resolved to a View_definition e.g. via variant expression or effectivity evaluation How is product & system coding and classification supported ? Not available except by tags or attributes to a thing – tags or attributes (see note below about requirements specifically Use the PRT or PRODUCT or SYSTEM structure to define a taxonomy and then create associations How is a CR associated with a project, product or system coding & classification ? Through a CR attributeLocate via Product or Product View Definition CR Req Implem System or product context Controlled config

17. OSLC PLM workgroup workings17 PLM Resource requirements

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

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

20. OSLC PLM workgroup workings20 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

21. OSLC PLM workgroup workings21 Method applied

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

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

24. OSLC PLM workgroup workings24 Workings

25. OSLC PLM workgroup workings25 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

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

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

28. OSLC PLM workgroup workings28 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

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

30. OSLC PLM workgroup workings30 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

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

32. OSLC PLM workgroup workings32 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/dcterm s/

33. OSLC PLM workgroup workings33 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

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

35. OSLC PLM workgroup workings35 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 ?

36. OSLC PLM workgroup workings36 Backup / reference

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

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