Dr Rob Bodington Eurostep PLCSlib - Overview Dr Rob Bodington Eurostep

PLCSlib - Acknowledgements Norwegian Defence Logistics Organisation UK MoD Defence Equipment and Support (DE&S) Sweden’s FMV French MoD - SIMMT Boeing BAE Systems Rolls Royce Black & Rossi DNV Eurostep CRESCENDO Project (EU R&D project) LOTAR project RASSC project (UK TSB R&D project)

Topics Technical drivers Information architecture overview Information layer Exchange layer Business / Domain layer Applicability of approach to AP242 BOM

Topics Technical drivers Information architecture overview Information layer Exchange layer Business / Domain layer Applicability of approach to AP242 BOM

Technical drivers Core information model that is: Founded in AP239 ed2 ARM Easier to understand, Easier to access Easier to implement “Formal” mechanism for semantic extension of core information model “Formal” reusable approach to mapping business objects/concepts to the Core information model Using COTS tools / Mainstream standard technologies Avoid bespoke where possible UML almost good enough – but not quite. SysML provides required capability with out extensions and extensive COTS tools

Topics Technical drivers Information architecture overview Information layer Exchange layer Business / Domain layer Applicability of approach to AP242 BOM

PLCS Information Architecture “Business/Domain” layer Business/Domain model Maps Templates references Maps OWL Ref. Data Concept model Specializes Maps “Core/standard” Information layer PLCS PSM SysML ISO 10303-239 ARM EXPRESS PLCS PSM OWL Transformed PLCS PSM EXPRESS Transformed Transformed Transformed Exchange layer PLCS PSM XML Schema Schematron rules

Topics Technical drivers Information architecture overview Information layer Exchange layer Business / Domain layer Applicability of approach to AP242 BOM

Core information model “Business/Domain” layer Conceptual overview of PLCS model. UML model Automated transformation (REEPER) based on ISO 10303-26 Transformation maintains scope of ARM, but simplifies. Similar approach to AP242 BOM. I.e. simplify Id/Classification/Properties/Encapsulation of assignment/relationships Direct equivalent of PSM EXPRESS SysML reflects XSD encapsulation SysML enables formal mapping to domain model OWL ontology based on PSM Blocks that are “Classifiable” or “Equivalent” Concept model “Core/standard” Information layer PLCS PSM SysML ISO 10303-239 ARM EXPRESS PLCS PSM OWL Transformed PLCS PSM EXPRESS Transformed Transformed Transformed Exchange layer XML Schema derived from PLCS PSM XSD uses same approach as Ap242 PLCS PSM XML Schema Schematron rules

Core information model “Business/Domain” layer Conceptual overview of PLCS model. UML model Concept model “Core/standard” Information layer PLCS PSM SysML ISO 10303-239 ARM EXPRESS Transformed PLCS PSM EXPRESS Transformed Transformed PLCS PSM OWL Transformed Exchange layer PLCS PSM XML Schema Schematron rules

Scope of PLCS: Concept model http://docs. oasis-open

Scope of PLCS and supported histories http://docs. oasis-open Design and Individual Configurations Activities performed by people and product States failure & operational Change Management

Core information model “Business/Domain” layer Automated transformation (REEPER) based on ISO 10303-26 Transformation maintains scope of ARM, but simplifies. Similar approach to AP242 BOM. I.e. simplify Id/Classification/Properties/Encapsulation of assignment/relationships Direct equivalent of PSM EXPRESS SysML reflects XSD encapsulation SysML enables formal mapping to domain model Concept model “Core/standard” Information layer PLCS PSM SysML ISO 10303-239 ARM EXPRESS Transformed PLCS PSM EXPRESS Transformed Transformed PLCS PSM OWL Transformed Exchange layer PLCS PSM XML Schema Schematron rules

PLCS PSM http://docs. oasis-open. org/plcs/plcslib/v1 Aligned with AP242 BOM EXPRESS -> SysML SysML Represent encapsulations Enables mapping via parametric diagrams Easier to view/navigate model than STEPmod based AP

Core information model “Business/Domain” layer OWL ontology based on PSM Blocks that are “Classifiable” or “Equivalent” Concept model “Core/standard” Information layer PLCS PSM SysML ISO 10303-239 ARM EXPRESS Transformed PLCS PSM EXPRESS Transformed Transformed PLCS PSM OWL Transformed Exchange layer PLCS PSM XML Schema Schematron rules

PLCS PSM http://docs. oasis-open. org/plcs/plcslib/v1 OWL converted from PSM forms “upper” ontology Domain specific class are specializations of “upper” ontology. E.g. Date / times Idenitifiers Activities Properties Units

Domain ref <domain>-en.owl <domain>-sv.owl PLCS ref Reference Data Business Objects Templates Business process PLCS PSM XSD PLCS PSM Domain ref data <domain>-en.owl <domain>-sv.owl imports PLCS ref data plcs-rdl-en.owl plcs-rdl-sv.owl imports PLCS model plcs-psm-en.owl plcs-psm-sv.owl imports Meta data SKOS Dublin Core

Topics Technical drivers Information architecture overview Information layer Exchange layer Business / Domain layer Applicability of approach to AP242 BOM

Core information model “Business/Domain” layer Concept model “Core/standard” Information layer PLCS PSM SysML ISO 10303-239 ARM EXPRESS Transformed PLCS PSM EXPRESS Transformed Transformed PLCS PSM OWL Transformed Exchange layer XML Schema derived from PLCS PSM XSD uses same approach as Ap242 PLCS PSM XML Schema Schematron rules

PLCS PSM XSD http://docs. oasis-open. org/plcs/plcslib/v1 Aligned with AP242 BOM Schematron + XSD used for data validation XSD intended to be easier to use than P28 XSD Encapsulation of assignments, relationships

Core information model “Business/Domain” layer Conceptual overview of PLCS model. UML model Automated transformation (REEPER) based on ISO 10303-26 Transformation maintains scope of ARM, but simplifies. Similar approach to AP242 BOM. I.e. simplify Id/Classification/Properties/Encapsulation of assignment/relationships Direct equivalent of PSM EXPRESS SysML reflects XSD encapsulation SysML enables formal mapping to domain model OWL ontology based on PSM Blocks that are “Classifiable” or “Equivalent” Concept model “Core/standard” Information layer PLCS PSM SysML ISO 10303-239 ARM EXPRESS PLCS PSM OWL Transformed PLCS PSM EXPRESS Transformed Transformed Transformed Exchange layer XML Schema derived from PLCS PSM XSD uses same approach as Ap242 PLCS PSM XML Schema Schematron rules

Topics Technical drivers Information architecture overview Information layer Exchange layer Business / Domain layer Applicability of approach to AP242 BOM

Templates & Business / Domain model “Business/Domain” layer Business/Domain model Maps Templates references Maps OWL Ref. Data Concept model Specializes Maps “Core/standard” Information layer PLCS PSM SysML ISO 10303-239 ARM EXPRESS PLCS PSM OWL Transformed PLCS PSM EXPRESS Transformed Transformed Transformed Exchange layer PLCS PSM XML Schema Schematron rules

Templates & Business / Domain model http://docs. oasis-open Use SysML Blocks to represent Business / Domain Objects Use SysML Parametric diagrams to map Business / Domain Objects to PLCS PSM SysML Templates are SysML Blocks therefore reusable in multiple models. Ensures consistency of mapping. E.g. “Standard Part” + mapping can be used in multiple Business DEXs Parametric diagrams: provide an unambiguous specification of how the business/domain objects are mapped are computer interpretable and can be the basis for code generation

Why templates? Model business objects. Formally map to PLCS PSM Formally define repeatable patterns Allow code to generated from the templates Business Objects Templates Templates PLCS PSM

SysML Block definition diagram

SysML Block definition diagram SysML Block: Business object representing pattern of objects: A template Pattern of PLCS PSM objects to be instantiated by the template

SysML Block definition diagram Template: SysML Block Template: Constraints Template: Output ports Template: Public properties Template: Private properties Template: Parametric Diagram Pattern of PLCS PSM objects to be instantiated by the template defined by parametric diagram

Consumption of life (DEX) Organization B Organization A Consumption of life (DEX) Organization B Data exchange Bike identification Part No / S.No / Stock No Life properties Cycling hours Product operator Product maintainer Translator Translator System A System B

2) What data to be exchanged? 1) Why exchange data? Organization A Data Exchange Specification (DEX) Organization B Business Objects Model Exchange process specifies maps Templates Ref. Data maps PLCS PSM uses specializes maps maps Transformed System model System model PLCS PSM XSD References Translator Translator System A 3) How to exchange data? 2) What data to be exchanged? 1) Why exchange data? System B

Topics Technical drivers Information architecture overview Information layer Exchange layer Business / Domain layer Applicability of approach to AP242 BOM This is for illustrating the art of the possible and to provide input for next weeks workshop. They are not intended be anything other than that

PLCS Information Architecture “Business/Domain” layer Business/Domain model Maps Templates references Maps OWL Ref. Data Concept model Specializes Maps “Core/standard” Information layer PLCS PSM SysML ISO 10303-239 ARM EXPRESS PLCS PSM OWL Transformed PLCS PSM EXPRESS Transformed Transformed Transformed Exchange layer PLCS PSM XML Schema Schematron rules

“Business/Domain” layer “Core/standard” Information layer AP242 PLCSlib Information Architecture http://www.plcs.org/STEPlib/242lib.html “Business/Domain” layer Business/Domain model Maps Templates references Maps OWL Ref. Data Specializes Maps “Core/standard” Information layer ISO 10303-242 BOM SysML ISO 10303-242 ARM EXPRESS PLCS PSM OWL Maps ISO 10303-242 BOM EXPRESS Transformed Transformed Exchange layer ISO 10303-242 XML Schema

“Business/Domain” layer “Core/standard” Information layer AP242 PLCSlib Information Architecture http://www.plcs.org/STEPlib/242lib.html As an exercise to investigate applicability of approach to AP242 we did the following: Ran REEPER on AP242 BOM EXPRESS to generate BOM SysML Drew a subset of SysML Block Diagrams in Magicdraw Developed Templates for part using same scope of PLCS Part Assembly Template. Classifier DatedEffectivity Descriptor Indentification Name Part PartAssembly ViewDefinitionContext “Business/Domain” layer Business/Domain model Maps Templates references Maps OWL Ref. Data Specializes Maps “Core/standard” Information layer ISO 10303-242 BOM SysML ISO 10303-242 ARM EXPRESS PLCS PSM OWL Maps ISO 10303-242 BOM EXPRESS Transformed Transformed Exchange layer ISO 10303-242 XML Schema

See: http://www.plcs.org/STEPlib/242lib.html Direct equivalent of PSM EXPRESS SysML reflects XSD encapsulation ISO 10303-242 BOM SysML ISO 10303-242 BOM SysML Block Definition diagram SysML reflects EXPRESS rules in OCL See: http://www.plcs.org/STEPlib/242lib.html

ISO 10303-242 Part Template as per PLCS Part templates See: http://www.plcs.org/STEPlib/242lib.html

Observation Generation of SysML Blocks from AP242 BOM was an automated process using REEPER. 99% converted. Some minor issues to be addressed We were able to reuse some of the PLCS reference data EXPRESS rules can be represented as OCL constraints. A manual process Not all 242 rules have been converted SysML reflects the encapsulation. For code generation of SysML this required addition of EXPRESS rules Issue against AP242 BOM re encapsulation

Encapsulation ENTITY ActivityMethodAssignment; id : OPTIONAL IdentifierSelect; description : OPTIONAL DescriptorSelect; classifiedAs : OPTIONAL SET[1:?] OF Classification; role : ClassSelect; assignedActivityMethod : ActivityMethod; (* RBN assignedTo : SET[1:?] OF ActivityMethodAssignmentSelect; http://www.wikistep.org/bugzilla/show_bug.cgi?id=5067 *) assignedTo : ActivityMethodAssignmentSelect; WHERE (* RBN Encapsulate into assignedTo attribute https://sourceforge.net/p/plcslib/plcs-psmmodel/205/*) encapsulateInto: EXISTS(assignedTo); END_ENTITY; ENTITY ActivityMethodRelationship; relationType : ClassSelect; relating : ActivityMethod; related : ActivityMethod; WR1: relating :<>: related; (* RBN Encapsulate into relating attribute https://sourceforge.net/p/plcslib/plcs-psmmodel/205/*) encapsulateInto: EXISTS(relating);

Conclusion PLCSlib publication environment is targeted at PLCS PSM – hence some work will be required to adopt it to AP242. The experiment shows that the use of the SysML approach to author templates and illustrate the AP242 BOM as a SysML Block Definition diagram is straightforward.