Analysing the PLM reference model

1
Analysing the PLM reference model

• V0.3
• Gray Bachelor

2
Whats in this document ?

• This is the working material used to identify key
  areas in the PLM Reference Model
• Pose questions
• Show examples
• Utilising the Draft OSLC PLM Reference Model
  based upon the OMG Hybrid SUV model with
  extensions
• Helps identify example of the SysML and STEP
  elements and constructs of relevance to the
  analysis

3
Invitation

• Readers are invited to comment and contribute
  through the OSLC PLM Workgroup or directly to the
  author
• Do additional examples exist ?
• Any feedback on comments ?
• Any answers to the open questions ?

4
Working topics

• STEP file
• Naming conventions
• Requirements
• System
• Other not addressed
• Organisation
• Activity

5
STEP file

• STEP text files (ISO-10303-Part21)
• HEADER
• REQUIREMENT
• CLASSIFICATION_ASSIGNMENT
• SYSTEM
• SYSTEM BREAKDOWN
• SYSTEM ELEMENT
• ORGANIZATION
• APPLIED_ACTIVITY_ASSIGNMENT

6
What is the context of the naming conventions ?

• The container
• Filename, description
• Rules about its content
• FILE_SCHEMA (('AP233_SYSTEMS_ENGINEERING_ARM_LF'))
  
• Description of the overall view
• 1VIEW_DEFINITION_CONTEXT('Requirements_Analysis_
  Process','Concept_stage','')
• The owning org
• 12ORGANIZATION('GM','GM')
• How the data was produced
• 20ACTIVITY_METHOD('XSLT_Extract','XSLT Extract
  of STEP Part 21 Data File from Topcased SysML
  XMI','','For initial creation of dataset')
• When the file was produced
• Date, time
• Specific terms adopted from a consumable
  (include-able source)

7
PLM Reference ModelAdditional relationships
enabling classification

• 34EXTERNAL_CLASS_LIBRARY('http//www.ap233.org/a
  p233-public-information/ap233-reference-data/ap233
  _basic_library','Library of basic concept values
  from AP233')
• 36EXTERNAL_CLASS('http//www.omg.org/spec/SysML/
  Current/SysML-profileDeriveReqt','DeriveReqt','Th
  e "derive requirement" relationship relates a
  derived requirement to its source
  requirement.',34)
• 38EXTERNAL_CLASS('http//www.omg.org/spec/SysML/
  Current/SysML-profileRefine','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)
• 40EXTERNAL_CLASS('http//www.omg.org/spec/SysML/
  Current/SysML-profileSatisfy','Satisfy','The
  satisfy relationship describes how a design or
  implementation model satisfies one or more
  requirements.',34)
• 42EXTERNAL_CLASS('http//www.omg.org/spec/SysML/
  Current/SysML-profileVerify','Verify','The
  verify relationship defines how a test case or
  other model element verifies a requirement.',34)

8
Requirements
9
Types of Requirement in the PLM Reference Model

• Main
• Derived
• Refinement for HSUV Acceleration

10
PLM Reference Model SysML Requirements Diagram
11

• In SysML 1.1 the version is a property
• In topcased this property is not visible on the
  diagram

12
One requirement
Assume this is the id
What is the origin of this ?

• 800REQUIREMENT('R1.0','HSUV Specification','HSUV
  Specification Requirement')
• 810REQUIREMENT_VERSION('1','',800)
• 820REQUIREMENT_VIEW_DEFINITION('1','HSUV
  Specification Requirement View Definition','',1,(
  ),810)

What does the 1 signify ?
Is this 1 in the stp file or what ?
13
A related requirement

• 4500REQUIREMENT('R1.1','Performance','Performanc
  e Requirement')
• 4510REQUIREMENT_VERSION('1','The Hybrid SUV
  shall have the braking, acceleration, and offroad
  capability of a typical SUV, but have
  dramatically better fuel economy.',4500)
• 4520REQUIREMENT_VIEW_DEFINITION('1','Performance
  Requirement View Definition','',1,(),4510)

14
Requirement relationship - isComposedOf

• 4530REQUIREMENT_COLLECTION_RELATIONSHIP('','isCo
  mposedOf','',820,4520)

Just a string ? Does SysML prescribe ?
No text any significance ?
Why Collection instead of REQUIREMENT_VIEW_DEFINIT
ION_RELATIONSHIP
15
Another related requirement

• 1300REQUIREMENT('R1.2','Eco-Friendliness','Eco-F
  riendliness Requirement')
• 1310REQUIREMENT_VERSION('1','',1300)
• 1320REQUIREMENT_VIEW_DEFINITION('1','Eco-Friendl
  iness Requirement View Definition','',1,(),1310)
  
• 1330REQUIREMENT_COLLECTION_RELATIONSHIP('','isCo
  mposedOf','',820,1320)

16

• 1800REQUIREMENT('R1.2.1','Emissions','Emissions
  Requirement')
• 1810REQUIREMENT_VERSION('1','The vehicle shall
  meet Ultra-Low Emissions Vehicle
  standards.',1800)
• 1820REQUIREMENT_VIEW_DEFINITION('1','Emissions
  Requirement View Definition','',1,(),1810)
• 1830REQUIREMENT_COLLECTION_RELATIONSHIP('','isCo
  mposedOf','',1320,1820)
• 2700REQUIREMENT('R1.2.1','Emissions','Emissions
  Requirement')
• 2710REQUIREMENT_VERSION('2','The vehicle shall
  meet Revised 2016 Ultra-Low Emissions Vehicle
  standards.',2700)
• 2712PRODUCT_VERSION_RELATIONSHIP('sequence','Ver
  sion Sequence',1810,2710)
• 2720REQUIREMENT_VIEW_DEFINITION('2','Emissions
  Requirement View Definition','',1,(),2710)
• 2730REQUIREMENT_COLLECTION_RELATIONSHIP('','isCo
  mposedOf','',1320,2720)
• 3600REQUIREMENT('R1.2.1','Emissions','Emissions
  Requirement')
• 3610REQUIREMENT_VERSION('2','The vehicle shall
  meet Revised 2016 Ultra-Low Emissions Vehicle
  standards.',3600)

New construct to add a sequence of versions
Why is derivation used here ?
All 3 versions relate to 1320
17
Alt layout to clarify
sequence
derivation
sequence
18
PLM Reference Model STEP content examples

• Gathered examples
• Requirements

19
PLM Reference ModelRequirement and its
relationships

• 1200REQUIREMENT('R1.2','Eco-Friendliness','Eco-F
  riendliness Requirement')
• 1210REQUIREMENT_VERSION('1','',1200)
• 1220REQUIREMENT_VIEW_DEFINITION('1','Eco-Friendl
  iness Requirement View Definition','',1,(),1210)
  
• 1230REQUIREMENT_COLLECTION_RELATIONSHIP('','isCo
  mposedOf','',720,1220)
• 10700REQUIREMENT_VIEW_DEFINITION_RELATIONSHIP('1
  0700','DeriveReqt','DeriveReqt1',3220,8720)

20
PLM Reference ModelRequirements

• 1700REQUIREMENT('R1.2.1','Emissions','Emissions
  Requirement')
• 1710REQUIREMENT_VERSION('1','The vehicle
  shall meet Ultra-Low Emissions Vehicle
  standards.',1700)
• 1720REQUIREMENT_VIEW_DEFINITION('1','Emissions
  Requirement View Definition','',1,(),1710)
• 1730REQUIREMENT_COLLECTION_RELATIONSHIP('','is
  ComposedOf','',1220,1720)
• 2210REQUIREMENT_VERSION('2','The vehicle
  shall meet Revised 2016 Ultra-Low Emissions
  Vehicle standards.',1700)
• 2220REQUIREMENT_VIEW_DEFINITION('2','Emissions
  Requirement View Definition','',1,(),2210)
• 2230REQUIREMENT_COLLECTION_RELATIONSHIP('','is
  ComposedOf','',1220,2220)

21
PLM Reference ModelRequirements

• 2700REQUIREMENT('R1.2.1','Emissions','Emissions
  Requirement')
• 2710REQUIREMENT_VERSION('2','The vehicle
  shall meet Revised 2016 Ultra-Low Emissions
  Vehicle standards.',2700)
• 2712PRODUCT_VERSION_RELATIONSHIP('sequence','V
  ersion Sequence',1810,2710)
• 2720REQUIREMENT_VIEW_DEFINITION('2','Emission
  s Requirement View Definition','',1,(),2710)
• 2730REQUIREMENT_COLLECTION_RELATIONSHIP('','is
  ComposedOf','',1320,2720)
• 3600REQUIREMENT('R1.2.1','Emissions','Emissio
  ns Requirement')
• 3610REQUIREMENT_VERSION('2','The vehicle
  shall meet Revised 2016 Ultra-Low Emissions
  Vehicle standards.',3600)

22
PLM Reference ModelRequirement Assignment

• 114700REQUIREMENT_ASSIGNMENT('114700','Satisfy3'
  ,1820,30120)
• 114800REQUIREMENT_ASSIGNMENT('114800','Satisf
  y4',2720,69420)
• 115100REQUIREMENT_ASSIGNMENT('115100','Satisf
  y1',11520,30120)
• 115200REQUIREMENT_ASSIGNMENT('115200','Satisf
  y2',3620,84420)

23
PLM Reference ModelClassification Assignment

• 50CLASSIFICATION_ASSIGNMENT(36,(10700,10800,
  10900,11000,11100,11200,11300,11400,11500),'
  DeriveReqt')
• Certain requirements are classified as type
  DeriveReqt (36 above

24
System
25

• Overall
• Power Control Unit system structure (architecture

26
(No Transcript)
27
No. occurring in the assembly

• 23600SYSTEM('23600','HybridSUV','HybridSUV
  System')
• 23610SYSTEM_VERSION('1','HybridSUV System
  Element Version',23600)
• 23620SYSTEM_VIEW_DEFINITION('1','HybridSUV
  System View Definition','',1,(),23610)
• 23640VALUE_WITH_UNIT(2,1)

No. occurring in the assembly
What is the origin ? There is no 2 in the file
28
A related System element

• 30100SYSTEM('30100','PowerSubsystem','PowerSubsy
  stem System')
• 30110SYSTEM_VERSION('1','PowerSubsystem System
  Element Version',30100)
• 30120SYSTEM_VIEW_DEFINITION('1','PowerSubsystem
  System View Definition','',1,(),30110)
• 30130NEXT_ASSEMBLY_USAGE(23620,30120,'',30140
  )
• 30140VALUE_WITH_UNIT(2,1)

Origin ?
Why NEXT ?
29
(No Transcript)
30
(No Transcript)
31
11
Arbitrary ? Or is it based on the External Class ?
How are other interdepencies represented in SysML

• 114700REQUIREMENT_ASSIGNMENT('114700','Satisfy3'
  ,1820,30120)
• 114800REQUIREMENT_ASSIGNMENT('114800','Satisfy4'
  ,2720,69420)
• 115100REQUIREMENT_ASSIGNMENT('115100','Satisfy1'
  ,11520,30120)
• 115200REQUIREMENT_ASSIGNMENT('115200','Satisfy2'
  ,3620,84420)

3 of 4 here
32
PLM Reference Model STEP content examples

• Gathered examples
• System

33
PLM Reference ModelSYSTEM

• 21780SYSTEM('21800','HybridSUV','HybridSUV
  System')
• 21782SYSTEM_VERSION('1','HybridSUV System
  Element Version',21800)
• 21784SYSTEM_VIEW_DEFINITION('1','HybridSUV
  System View Definition','',1,(),21782)
• 21786SYSTEM_BREAKDOWN('21800','HybridSUV','Hybri
  dSUV System Breakdown')
• 21788SYSTEM_BREAKDOWN_VERSION('1','HybridSUV
  System Breakdown Version',21786)
• 21790BREAKDOWN_OF('1','HybridSUV','HybridSUV
  Breakdown',21788,21784)
• 21792SYSTEM_BREAKDOWN_CONTEXT('1','HybridSUV','H
  ybridSUV Breakdown Context',21788,21820)
• 21810SYSTEM_ELEMENT_VERSION('1','HybridSUV
  System Element Version',21800)
• 21820SYSTEM_ELEMENT_DEFINITION('1','HybridSUV
  System Element Definition','',1,(),21810)

34
PLM Reference ModelSystem element and its
relationships

• 26900SYSTEM_ELEMENT('26900','Fuel','Fuel System
  Element')
• 26910SYSTEM_ELEMENT_VERSION('1','Fuel System
  Element Version',26900)
• 26920SYSTEM_ELEMENT_DEFINITION('1','Fuel System
  Element Definition','',1,(),26910)
• 26930SYSTEM_ELEMENT_USAGE('1','','Fuel System
  Element Usage',21820,26920,'Fuel')

35
PLM Reference ModelAdditional
relationshipsREQUIREMENT_VIEW_DEFINITION to
SYSTEM_ELEMENT_DEFINITION

• 94700REQUIREMENT_ASSIGNMENT('94700','Satisfy3',
  1720,27820)
• 94800REQUIREMENT_ASSIGNMENT('94800','Satisfy4',
  2220,67120)
• 95100REQUIREMENT_ASSIGNMENT('95100','Satisfy1',
  9720,27820)

36
Other
37
PLM Reference ModelACTIVITY performed

• 90APPLIED_ACTIVITY_ASSIGNMENT(22,(700,710,72
  0,
• XMI extract from TOPcased

38
PLM Reference ModelORGANISATIONAL ownership

• 80ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNM
  ENT(16,'creator',(700,710,720,

39
Changes

• V0.1 Used during Gray/Ian working session
• V0.2/0.3 Consolidate to post