1 / 23

Summary of the OSLC PLM Reference Model

Summary of the OSLC PLM Reference Model. V0.4 April 4th 2011 Gray Bachelor Mike Loeffler OSLC PLM Workgroup. Acknowledgements. OSLC PLM Workgroup Mike Loeffler Gray Bachelor. Contents. Background Motivation PLM Reference Model (proposed) overview

luna
Download Presentation

Summary of the OSLC PLM Reference Model

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Summary of the OSLC PLM Reference Model V0.4 April 4th 2011 Gray Bachelor Mike Loeffler OSLC PLM Workgroup OSLC PLM Reference model April 2011

  2. Acknowledgements • OSLC PLM Workgroup • Mike Loeffler • Gray Bachelor OSLC PLM Reference model April 2011

  3. Contents • Background • Motivation • PLM Reference Model (proposed) overview • Analysis of the OSLC Specs and PLM Reference Model in the content of the selected Scenario • Next steps OSLC PLM Reference model April 2011

  4. 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 Management and 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 OSLC PLM Reference model April 2011

  5. PLM Reference Model OSLC PLM Reference model April 2011

  6. 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 OSLC PLM Reference model April 2011

  7. 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 System or product context Controlled config Req Implem OSLC PLM Reference model April 2011

  8. 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 OSLC PLM Reference model April 2011

  9. 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 OSLC PLM Reference model April 2011

  10. 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”) OSLC PLM Reference model April 2011

  11. 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 OSLC PLM Reference model April 2011

  12. 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 OSLC PLM Reference model April 2011

  13. Summary of the enhancements made to OMG Hybrid SUV example OSLC PLM Reference model April 2011

  14. 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 Verification 2 2 2 2 2 2 • When comparing the original OMG SysML HSUV diagrams note • additional diagrams have been created to simplify understanding the scenario • additional diagram variants have been created to show the progression of the scenario OSLC PLM Reference model April 2011

  15. 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 1 • When comparing the original OMG SysML HSUV diagrams note • additional diagrams have been created to simplify understanding the scenario • additional diagram variants have been created to show the progression of the scenario OSLC PLM Reference model April 2011

  16. Not used today • The OMG SUV model has additional content which is not used today within the PLM Reference Model OSLC PLM Reference model April 2011

  17. Basis of the OSLC PLM Reference Model OSLC PLM Reference model April 2011

  18. STEP supports PLM representation of System & Product decomposition e.g. AP233 OSLC PLM Reference model April 2011

  19. 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 Reference model April 2011

  20. 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=sysml-ap233:mapping_between_sysml_and_ap233#interactions_mapping Our constructs and concepts span SysML and AP233 OSLC PLM Reference model April 2011

  21. E.g. SysML to AP233 mapping for Requirements OSLC PLM Reference model April 2011

  22. 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 OSLC PLM Reference model April 2011

  23. Changes • V0.1 Draft 22/2 • V0.2 Posted to wiki • V0.3 Add variant handling page • V0.4 Add the list of diagrams OSLC PLM Reference model April 2011

More Related