CM Spec analysis
Markup from discussion 15/3 and
22/3
OSLC PLM workgroup workings 1
Summary of the scenario by way of the
key business entities & their relationships
Pre-condition (Before Is based
upon or
CR
* Assuming basic triaging applies to* At some context
has been done prior to the version V’
start of the scenario System or
product context
Controlled config
Req Implem
Post-condition (After
Is implemented At some new
by context version V’’
CR System or
System or
product context
product context
Controlled config
Controlled config
Req Implem
Req Implem
Updated to achieve
the CR
OSLC PLM workgroup workings 2
STEP supports PLM representation of
System & Product decomposition
e.g. AP233
OSLC PLM workgroup workings 3
PLM Reference model can be further built
out to support model driven development
SysML Diagram
Structure Parametric Requirement Behavior
Diagram Diagram Diagram Diagram
Class Assembly Activity Timing Use Case
Diagram Diagram Diagram Diagram Diagram
Sequence State Machine
Diagram Diagram
Modified from UML 2
New diagram type Interaction
Overview
Diagram
Applied in the PLM Reference Model
Base diagram from OMG OSLC PLM workgroup workings 4
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 5
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
OSLC PLM workgroup workings 6
http://open-services.net/bin/view/Main/CmSpecificationV2
Set of 6 states
“State predicate properties
Set of relationships
“Relationship properties:
OSLC PLM workgroup workings 7
CR
Question OSLC CM Answer PLM Reference model Answer
System or
product context
CM 1 of 2
How is a CR defined ? CR is a type. A CR resource has
a shape which prescribe a set of
Req
Controlled config Implem
CR is not currently addressed in the PLM Reference
Model. AP233 and AP239 have the possibility
mandatory attributes
How is a CR uniquely identified Globally by a URI. Within the By a CR id within an enterprise or container scope
service provider by a dcterms (repository)
identifier within a given
container scope (relative to)
What determines the rules for CM Spec 2.0 FILE_SCHEMA
representing a CR ? Model rules (RDF) (('AP233_SYSTEMS_ENGINEERING_ARM_LF')); (To
Resource shape per scenario validate)
(Create, Query, Instance state
What is the visibility of the CR Global ? Header includes the names, time stamp, org
description ?
How is CR meta-data defined ? Title and identifier are In the PM Schema
E.g. organisational ownership mandatory plus optional ID, name and description see Work Request / Work
properties defined by service Order page
provider
How is the relationship between Named optional relationship Activity method assignment
CR and other resources defined properties available for use Affected items assignment
?
How to version a CR ? Dcterms: Modified date changes ITEM & ITEM_VERSION associated with a
the http header etag VIEW_DESCRIPTION
OSLC PLM workgroup workings 8
CR
System or
product context
CR 2 of 2 Req
Controlled config Implem
Question OSLC Answer PLM Reference model Answer
How are groups of CR By a common attribute or through association CRs can be grouped for implementation as a
organised ? with say back to another OSLC resource like change activity and an effectivity
Identifying as a group single Requirement AP239 has effectivity parameters
Treat as a group e.g. oslc_cm:relatedChangeRequest (valid via tags Check in AP233 / AP239
Approve, implement,
assign to a block or an e.g. oslc_cm:implementsRequirement
organisational unit as
group e.g. a black box
approach “satisfiedby” OSLC lacks the explicit “isComposedBy”
Short hand
Identify 3 types
interdependency * 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 property
impact, related resource. These workgroup workings 9
relationships can be used to understand the
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 10
PLM CR rel
Activity method assignment
Affected items assignment
OSLC PLM workgroup workings 11
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/
OSLC PLM workgroup workings 12
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 13
CR
System or
product context
CR Context 1 of 2 Req
Controlled config Implem
Question OSLC Answer PLM Reference model Answer
How is the root context Service Provider (may not be the STEP Filename and date created (as a
defined ? authority snapshot for data exchange
(Using a tiering concept for
context Organisation
? Have parts been assigned to blocks ?
What constraints the CR CM Spec FILE_SCHEMA
(('AP233_SYSTEMS_ENGINEERING_ARM_LF'));
context description ? dcterms 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 Valid everywhere See above
requirement valid ?
Qualified by associations e.g. Query
project name in a WI
OSLC PLM workgroup workings 14
CR classification is optional
Dcterms: subject
OSLC PLM workgroup workings 15
CR
System or
product context
CR Context 2 of 2 Req
Controlled config Implem
Question OSLC Answer PLM Reference model Answer
How is project, product or As a property named as affected items or Identity, name and a version in reality this as
system context defined ? reference Product or Product Version an entry point to a config
identity, as an extension; or a link to #23600=SYSTEM('23600','HybridSUV','Hybrid
relevant context resource SUV System');
#23610=SYSTEM_VERSION('1','HybridSUV
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 Not available except by tags or attributes Use the PRT or PRODUCT or SYSTEM
coding and classification to a thing – tags or attributes (see note structure to define a taxonomy and then
supported ? below about requirements specifically create associations
How is a CR associated with Through a CR attribute Locate via Product or Product View Definition
a project, product or system
coding & classification ?
OSLC PLM workgroup workings 16
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 17
Additional comments 22/3
How user engage with context e.g. to
assign
How align or synchronise across tools ?
OSLC PLM workgroup workings 18
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 19
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 20