OSLC PLM Reference model April 20111 Summary of the OSLC PLM Reference Model V0.4 April 4th 2011...

OSLC PLM Reference model April 2011 1

Summary of the OSLC PLM Reference Model

V0.4April 4th 2011

Gray BachelorMike Loeffler

OSLC PLM Workgroup


Acknowledgements

OSLC PLM Workgroup Mike Loeffler Gray Bachelor


Contents

BackgroundMotivationPLM Reference Model (proposed)

overviewAnalysis of the OSLC Specs and PLM

Reference Model in the content of the selected Scenario

Next steps


Background

Open Services for Lifecycle Collaboration are community developed interface specifications

The OSLC PLM Workgroup aims to promote and pursue the use of the OSLC Resource models (Specs) to support collaboration between Software Application Lifecycle Managementand Product Lifecycle Management

Due to the lack of available and agreed reference or domain information the PLM Workgroup sponsored work to support investigation and subsequent recommendation by selecting and building up a representative scenario and PLM Reference model

The current focus is on analysis and comparison with the aim of publishing some findings that can guide current usage and potential extensions


PLM Reference Model


Overview of the PLM Reference Model

The objective of the model is to provide a representative description of PLM information related to the scenario

Certain standard representations have been selected to address the concerns of Scenario #1 SysML and STEP

Due to their ability to represent aspects of context, requirements and system implementation

Due to the motive to support modelling


The PLM reference model to support Scenario #1

Primary concerns CR – Change Request Req – Requirement Context – Product and System context e.g. classification,

configuration, effectivity Implem – Product and System implementation in models and

documents

CR

Req Implem

System or product context

Controlled config


Overview of the PLM Reference Model content

Based on the OMG SysML education example with enhancements for PLM

Main elements SysML model representations

Requirements Diagram Block diagrams

STEP text, xml and OWL representations Example instance

Hybrid SUV Based upon the OMG SysML model with extensions to

support the scenario and to provide a viable reference model


The main concepts supported

Product identity Notation of versions Structure of Requirements Structure of representations of the implemented

system A Requirement is “Satisfied by” an

implementation Handling of variants by way of optional

combinations of requirements and system implementation content


Key Configuration Capabilities of the Model Revision Effectivity

In process while a change is taking place, part of the model is in a state of change, other parts are in released state

Revision effectivity can return both the current working version of the complete model as well as the currently released version of the model

Variant Effectivity Variant effectivity can return the model configured to represent

either the US variant or the EU variant

Baselines A baseline in PLM is a special locked (released) version that

cannot be further changed (a “stubbed branch”)


The OSLC PLM Reference Model is based upon the OMG SUV SysML example

The model supports multiple system view points Requirements structure Operating context (Domain) Use-cases Functional breakdown State machine

The model has been extended to support PLM context Additional Software components


What do we mean by context ? Context is the needed or prevailing conditions for an

activity or artefact to be valid Referring to a product or system this is the relevant

environment and configuration, typically consists of a combination of Organisational ownership Product family and product line membership Product identity and release Configuration of content or capability

E.g. by way of parameters Effectivity and applicability

Revisions


Summary of the enhancements made to OMG Hybrid SUV exampleBase OMG SysML model Extension for OSLC PLM Reference Model Notes

Automotive Domain Breakdown diagram

1. Automotive domain block is versioned Container not versioned in the model (How implemented in Topcased)

Operational Use case diagram

No change Not include on-boarding of energy e.g fuel or battery charging

Diagram HSUV Specification

Requirements diagram

1. Version annotation to each element – requirement, block

2. Variant requirements

3. Variant requirements associated with implementation variants

4. Variant expressions

1. Satisfies by was in separate diagram

2. There is no recognised standard for variant expressions

HSUV Breakdown (Block) diagrams

1. Versioning at the block level

2. Block level annotation for the xml extract

Power Sub-system Block Definition Diagram (BDD)

& Internal Block Diagrams (IBD)

Three variants with appropriate decomposition


2. Alternative implementation of the Power Control Unit block

The IBD is named Combined Motor Generator

Power Control Unit Breakdown diagrams

1. Break out the Calibration and Software to be part of the assembly


To reflect current practice. Compatibility not addressed e.g. effectivity or explicitly


OSLC PLM Reference Model Available diagrams and variants to support the SE Scenario #1 based upon the base OMG SysML diagrams [Block] HybridSUV

[Block] PowerSubsystem o PowerControlUnit Breakdown id=AMG60107 version=001 o Fuel Flow Rate Determination o Alternative 1 - Combined Motor Generator id=AMG60107 version=001 [Block] PowerSubsystem o Alternative 1 - Combined Motor Generator id=AMG60107 version=002 o PowerControlUnit Breakdown id=AMG60107 version=002 [Block] PowerSubsystem o Alternative 1 - Combined Motor Generator id=AMG60107 version=003 o PowerControlUnit Breakdown id=AMG60107 version=003 PowerSubsystem Fuel Flow Definition

Operational Use Cases HybridSUV Breakdown PowerSubsystem Breakdown id=AMG60104 version=003 HSUVExample Breakdown HSUV Specification PowerSubsystem Breakdown id=AMG60104 version=002 Automotive Domain Breakdown PowerSubsystem Breakdown id=AMG60104 version=001 Requirements Derivation Acceleration Requirement Refinement and VerificationWhen comparing the original OMG SysML HSUV diagrams note 1) additional diagrams have been created to simplify understanding the scenario2) additional diagram variants have been created to show the progression of the scenario

2

2

2

2

2

2


OSLC PLM Reference Model Available diagrams and variants to support the SE Scenario #1 showing the new diagrams – pre condition [Model] HSUVExample_AMG54556_001 * [Package] HSUVExample_AMG54556_001 o [Test Case] SAE J1491 Max Acceleration + [State Machine] SAE J1491 # SAE J1491 + SAE J1491 o [Block] HSUVExample + [Block] HybridSUV # [Block] PowerSubsystem * [Block] PowerControlUnit o PowerControlUnit id=AMG60107 version=001 * PowerSubsystem id=AMG60104 version=001 # HybridSUV id=AMG60112 version=001 + [Requirement] HSUV Specification # [Requirement] Eco-Friendliness * Eco-Friendliness id=REQ-020181 version=A # [Requirement] Performance * [Requirement] Acceleration o Acceleration Requirement Refinement and Verification * Performance id=REQ-020145 version=A # [Requirement] Qualification * Qualification id=REQ-020162 version=A # [Requirement] Capacity * Capacity id=REQ-020172 version=A # HSUV Specification id=AKY251614 version=A # Requirements Derivation + HSUVExample id=AMG54556 version=001 o Automotive Domain Breakdown o Operational Use Cases

When comparing the original OMG SysML HSUV diagrams note 1) additional diagrams have been created to simplify understanding the scenario2) additional diagram variants have been created to show the progression of the scenario

1


Not used today

The OMG SUV model has additional content which is not used today within the PLM Reference Model


Basis of the OSLC PLM Reference Model


STEP supports PLM representation of System & Product decomposition

e.g. AP233


PLM Reference model can be further built out to support model driven development

SysML Diagram

StructureDiagram

BehaviorDiagram

Use CaseDiagram

ActivityDiagram

AssemblyDiagram

SequenceDiagram

InteractionOverviewDiagram

State MachineDiagram

TimingDiagram

ParametricDiagram

RequirementDiagram

ClassDiagram

Modified from UML 2

New diagram type

Base diagram from OMG

Applied in the PLM Reference Model


Our constructs and concepts span SysML and AP233 OMG sponsored a mapping

between SysML and AP233 Started in 2009 Last update 7/10

Detailed OMG asset of side by side comparison

Use cases Requirements Blocks Value properties Activities Constraint blocks State machines Packages and metadata

XML/xmi assets for requirements and system structure

Path to RDF/OWL http://www.omgwiki.org/OMGSysML/doku.php?id=s

ysml-ap233:mapping_between_sysml_and_ap233#interactions_mapping

http://www.omgwiki.org/OMGSysML/doku.php?id=sysml-ap233:mapping_between_sysml_and_ap233#interactions_mapping




E.g. SysML to AP233 mapping for RequirementsSysML AP233

Requirement Requirement_view_definition → Requirement_version → Requirement

Containment Requirement_collection_relationship

Allocate View_definition_relationship + Classification (‘Allocate’)

Satisfy Requirement_satisfied_by

Verify, Refine View_definition_relationship where one end must be a requirement

Copy, Derive Requirement_view_definition_relationship + Classification (‘Copy’, ‘Refine’)

Trace View_definition_relationship + Classification (’Trace’)

Trace between Requirements

Tracing_relationship

Text Requirement View Definition ← Single_property_is_definition → Property_representation → Representation → String_representation_item


For more information

Open Services for Lifecycle Collaboration PLM Workgroup http://open-services.net/bin/view/Main/PlmHome

Contacts Gray Bachelor, IBM Mike Loeffler, GM

http://open-services.net/bin/view/Main/PlmHome




Changes

V0.1 Draft 22/2V0.2 Posted to wikiV0.3 Add variant handling pageV0.4 Add the list of diagrams

OSLC PLM Reference model April 20111 Summary of the OSLC PLM Reference Model V0.4 April 4th 2011...

Documents

Transcript of OSLC PLM Reference model April 20111 Summary of the OSLC PLM Reference Model V0.4 April 4th 2011...