OSLC PLM Spec analysis Consolidation from previous discussions

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

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

Findings OSLC PLM workgroup workings 3

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

Meeting notes 29/3 l Project context in PLM ¡ l 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 l l ¡ ¡ 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 5

RM Spec analysis OSLC PLM workgroup workings 6

CR System or product context Requirement 1 of 2 Req Controlled config Implem Question OSLC RM Spec 2. 0 Answer PLM 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 URI By an id within a context What determines the rules for representing a requirement ? Meta-model rules (RDF) Resource shape FILE_SCHEMA (('AP 233_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 ? 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” For requirements: #1230=REQUIREMENT_COLLECTION_RELATIONS HIP('', 'is. Composed. Of', '', #720, #1220) “the descriptor is. Composed. Of is optional” How is the relationship between requirements and other resources defined ? Named relationship properties available for use #10700=REQUIREMENT_VIEW_DEFINITION_RELA TIONSHIP('10700', 'Derive. Reqt 1', #3220, # 8720); How to version a requirement ? 3 level structure with the version defined through the REQUIREMENT_VERSION OSLC PLM workgroup workings 7

CR Requirement 2 of 2 System or product context Req Controlled config Implem Question OSLC RM Spec 2. 0 Answer PLM Reference model Answer How are groups of Requirements organised ? Identifying as a group URI of the Requirements collection Dcterm: “Selected requirements for HSUV release XYZ” Sys. ML package holds the Requirements as a container (as opposed to a collection) 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 Identify interdependency Any sub-tree denotes a group 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 “is. Composed. By” 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('', 'is. Composed. Of', '', #820, #4520); Sys. ML does not have an external class for composition Uses: URI (not titles) (Uses is not well defined e. g. to mean “is. Composedby” Uses is a reference to another resource (as opposed to the strong decomposition inherent in UML) #36=EXTERNAL_CLASS('http: //www. omg. org/spec/Sys. ML/Current/ Sys. ML-profile#Derive. Reqt', 'The "derive requirement" relationship relates a derived requirement to its source requirement. ', #34); Open set (not supported) Tracelink here #1230=REQUIREMENT_COLLECTION_RELATIONSHIP('', 'is. Comp e. g. for an external link OSLC PLM workgroup workings #38=EXTERNAL_CLASS('http: //www. omg. org/spec/Sys. ML/Current/ Sys. ML-profile#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); “the descriptor is. Composed. Of is optional and arbitrary is. Composed. Of is derived from the decomposition paradigm of Sys. Ml modeling. osed. Of', '', #720, #1220) 8

CR System or product context RM Context 1 of 2 Req Controlled config Implem Question OSLC RM Spec 2. 0 Answer PLM 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 ? FILE_SCHEMA (('AP 233_SYSTEMS_ENGINEERING_ARM_LF')); What constrains the context description ? #20=ACTIVITY_METHOD('XSLT_Extract', 'XSLT Extract of STEP Part 21 Data File from Topcased Sys. ML XMI', 'For initial creation of dataset'); In what context is a requirement valid ? Valid everywhere See above Qualified by associations e. g. Query project name in a WI OSLC PLM workgroup workings 9

CR RM Context 2 of 2 System or product context Req Controlled config Implem Question OSLC RM Spec 2. 0 Answer PLM 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', 'Hybrid. SUV System'); #23610=SYSTEM_VERSION('1', 'Hybrid. SUV 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, Doors 10 using dcterms: subject (today changing a tag changes a requirement) (lose ability to look at history as not separately maintained #114700=REQUIREMENT_ASSIGNMENT('114700', 'Satisfy 3', #1820, #30120); Where the associated reference already sits in a system structure OSLC PLM workgroup workings 10

CM Spec analysis OSLC PLM workgroup workings 11

CR Question CM 1 of 2 OSLC CM Spec 2. 0 Answer PLM Reference model. System Answer or product context Req Controlled config Implem 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. AP 233 and AP 239 have the possibility How is a CR uniquely identified Globally 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 (('AP 233_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 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 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 OSLC PLM workgroup workings 12

CR CR 2 of 2 System or product context Req Controlled config Implem Question OSLC CM Spec 2. 0 Answer PLM Reference model Answer How are groups of CR organised ? Identifying as a group By a common attribute or through association with say back to another OSLC resource like single Requirement CRs can be grouped for implementation as a change activity and an effectivity AP 239 has effectivity parameters 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 oslc_cm: related. Change. Request (valid via tags Check in AP 233 / AP 239 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 OSLC PLM workgroup impact, related resource. These property workings relationships can be used to understand the e. g. oslc_cm: implements. Requirement OSLC lacks the explicit “is. Composed. By” 13

CR System or product context CR Context 1 of 2 Req Controlled config Implem Question OSLC CM Spec 2. 0 Answer PLM 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 ? FILE_SCHEMA (('AP 233_SYSTEMS_ENGINEERING_ARM_LF')); AP 233 WORK REQUEST / WORK ORDER CM Spec dcterms AP 239 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 Sys. ML XMI', 'For initial creation of dataset'); In what context is a requirement valid ? Valid everywhere See above Qualified by associations e. g. Query project name in a WI OSLC PLM workgroup workings 14

l CR classification is optional ¡ Dcterms: subject OSLC PLM workgroup workings 15

CR CR Context 2 of 2 System or product context Req Controlled config Implem Question OSLC CM Spec 2. 0 Answer PLM 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', 'Hybrid. SUV', 'Hybrid SUV System'); #23610=SYSTEM_VERSION('1', 'Hybrid. SUV System Element Version', #23600); As a context link e. g relation from dc As 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 attribute Locate via Product or Product View Definition OSLC PLM workgroup workings 16

PLM Resource requirements OSLC PLM workgroup workings 17

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

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

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

Method applied OSLC PLM workgroup workings 21

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

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

Workings OSLC PLM workgroup workings 24

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

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

http: //openservices. net/bin/view/Main/Cm. Specification. V 2 l Set of 6 states ¡ “State l Set predicate properties of relationships ¡ “Relationship properties: OSLC PLM workgroup workings 27

Working notes 22/3 l 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 l 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 28

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

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

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

Version comments (noted item 15/3 l 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/ OSLC PLM workgroup workings 32

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

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

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

Backup / reference OSLC PLM workgroup workings 36

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

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 38