Dr Rob Bodington Eurostep

PLCSlib - Overview

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

ISO 10303-239ARM EXPRESS

PLCS PSM EXPRESS

PLCS PSM SysML

PLCS PSM OWL

PLCS PSM XML Schema

Transformed Transformed

Transformed

Transformed

Exchange layer

“Core/standard” Information layer

“Business/Domain” layer

Business/Domain model

Maps Templates OWL

Ref. DataMaps

Maps

Specializes

references

Concept model

Schematron rules

Topics

Technical drivers Information architecture overview

Information layer Exchange layer Business / Domain layer

Applicability of approach to AP242 BOM

Core information model

ISO 10303-239ARM EXPRESS

PLCS PSM EXPRESS

PLCS PSM SysML

PLCS PSM OWL

Transformed Transformed Transformed

Exchange layer

“Core/standard” Information layer

“Business/Domain” layer

Concept model

Conceptual overview of PLCS model. UML model

Transformation maintains scope of ARM, but simplifies.Similar approach to AP242 BOM. I.e. simplify Id/Classification/Properties/Encapsulation of assignment/relationships

Automated transformation(REEPER) based on ISO 10303-26

Direct equivalent of PSM EXPRESSSysML reflects XSD encapsulationSysML enables formal mapping to domain model

OWL ontology based on PSM Blocks that are “Classifiable” or “Equivalent”

PLCS PSM XML Schema

Transformed

Schematron rules

XML Schema derived from PLCS PSMXSD uses same approach as Ap242

Core information model

ISO 10303-239ARM EXPRESS

PLCS PSM EXPRESS

PLCS PSM SysML

PLCS PSM OWL

Transformed Transformed Transformed

Exchange layer

“Core/standard” Information layer

“Business/Domain” layer

Concept model

Conceptual overview of PLCS model. UML model

PLCS PSM XML Schema

Transformed

Schematron rules

Scope of PLCS: Concept modelhttp://docs.oasis-open.org/plcs/plcslib/v1.0/cs01/data/PLCS/concept_model/model_base.html

Scope of PLCS and supported historieshttp://docs.oasis-open.org/plcs/plcslib/v1.0/cs01/data/PLCS/concept_model/model_base.html

Design and IndividualConfigurationsActivities

performed by people

and product

Statesfailure &

operational

Change Management

Core information model

ISO 10303-239ARM EXPRESS

PLCS PSM EXPRESS

PLCS PSM SysML

PLCS PSM OWL

Transformed Transformed Transformed

Exchange layer

“Core/standard” Information layer

“Business/Domain” layer

Concept model

Transformation maintains scope of ARM, but simplifies.Similar approach to AP242 BOM. I.e. simplify Id/Classification/Properties/Encapsulation of assignment/relationships

Automated transformation(REEPER) based on ISO 10303-26

Direct equivalent of PSM EXPRESSSysML reflects XSD encapsulationSysML enables formal mapping to domain model

PLCS PSM XML Schema

Transformed

Schematron rules

PLCS PSMhttp://docs.oasis-open.org/plcs/plcslib/v1.0/cs01/data/PLCS/psm_model/model_base.html

Click icon to add clip art Aligned with AP242 BOM

EXPRESS -> SysMLSysML

Represent encapsulations Enables mapping via parametric diagrams

Easier to view/navigate model than STEPmod based AP

Core information model

ISO 10303-239ARM EXPRESS

PLCS PSM EXPRESS

PLCS PSM SysML

PLCS PSM OWL

Transformed Transformed Transformed

Exchange layer

“Core/standard” Information layer

“Business/Domain” layer

Concept model

OWL ontology based on PSM Blocks that are “Classifiable” or “Equivalent”

PLCS PSM XML Schema

Transformed

Schematron rules

PLCS PSMhttp://docs.oasis-open.org/plcs/plcslib/v1.0/cs01/data/PLCS/psm_model/refdata/plcs-psm-en.owl

Click icon to add clip art OWL converted from PSM forms “upper” ontology

Domain specific class are specializations of “upper” ontology. E.g.

Date / times Idenitifiers Activities Properties Units

Reference Data

Meta dataSKOS Dublin Core

PLCSmodel plcs-psm-en.owl plcs-psm-sv.owl

PLCSref data

plcs-rdl-en.owl plcs-rdl-sv.owl

Domainref data <domain>-en.owl <domain>-sv.owl

imports

imports

imports

Business Objects

Templates

Business process

PLCS PSM XSD

PLCS PSM

Topics

Technical drivers Information architecture overview

Information layer Exchange layer Business / Domain layer

Applicability of approach to AP242 BOM

Core information model

ISO 10303-239ARM EXPRESS

PLCS PSM EXPRESS

PLCS PSM SysML

PLCS PSM OWL

Transformed Transformed Transformed

Exchange layer

“Core/standard” Information layer

“Business/Domain” layer

Concept model

PLCS PSM XML Schema

Transformed

Schematron rules

XML Schema derived from PLCS PSMXSD uses same approach as Ap242

PLCS PSM XSDhttp://docs.oasis-open.org/plcs/plcslib/v1.0/cs01/data/PLCS/psm_model/plcs_psm.xsdhttp://docs.oasis-open.org/plcs/plcslib/v1.0/cs01/data/PLCS/psm_model/common.xsd

Aligned with AP242 BOMSchematron + XSD used for

data validationXSD intended to be easier to

use than P28 XSDEncapsulation of assignments,

relationships

Core information model

ISO 10303-239ARM EXPRESS

PLCS PSM EXPRESS

PLCS PSM SysML

PLCS PSM OWL

Transformed Transformed Transformed

Exchange layer

“Core/standard” Information layer

“Business/Domain” layer

Concept model

Conceptual overview of PLCS model. UML model

Transformation maintains scope of ARM, but simplifies.Similar approach to AP242 BOM. I.e. simplify Id/Classification/Properties/Encapsulation of assignment/relationships

Automated transformation(REEPER) based on ISO 10303-26

Direct equivalent of PSM EXPRESSSysML reflects XSD encapsulationSysML enables formal mapping to domain model

OWL ontology based on PSM Blocks that are “Classifiable” or “Equivalent”

PLCS PSM XML Schema

Transformed

Schematron rules

XML Schema derived from PLCS PSMXSD uses same approach as Ap242

Topics

Technical drivers Information architecture overview

Information layer Exchange layer Business / Domain layer

Applicability of approach to AP242 BOM

Templates & Business / Domain model

ISO 10303-239ARM EXPRESS

PLCS PSM EXPRESS

PLCS PSM SysML

PLCS PSM OWL

PLCS PSM XML Schema

Transformed Transformed

Transformed

Transformed

Exchange layer

“Core/standard” Information layer

“Business/Domain” layer

Business/Domain model

Maps Templates OWL

Ref. DataMaps

Maps

Specializes

references

Concept model

Schematron rules

Templates & Business / Domain modelhttp://docs.oasis-open.org/plcs/plcslib/v1.0/cs01/sys/template_index_base.html

Use SysML Blocks to represent Business / Domain ObjectsUse 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 diagramTemplate: SysML Block

Template: Parametric Diagram

Template: Output ports

Template: Public properties

Template: Constraints

Template: Private properties

Pattern of PLCS PSM objects to be instantiated by the template defined by parametric diagram

Organization A Organization B

Translator Translator

System A System B

Consumption of life (DEX)

Data exchange

Product operator

Product maintainer

Bike identification• Part No / S.No / Stock No

Life properties• Cycling hours

Business Objects Model

PLCS PSM XSD

maps

Templates

Transformed

maps

PLCS PSM

Organization A Organization B

specifiesExchange process

System modelSystem model

Ref. Datauses

specializes

Translator Translator

System A System B

Data Exchange Specification (DEX)

mapsmaps

1) Why exchange data?2) What data to be exchanged?3) How to exchange data?

References

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

ISO 10303-239ARM EXPRESS

PLCS PSM EXPRESS

PLCS PSM SysML

PLCS PSM OWL

PLCS PSM XML Schema

Transformed Transformed

Transformed

Transformed

Exchange layer

“Core/standard” Information layer

“Business/Domain” layer

Business/Domain model

Maps Templates OWL

Ref. DataMaps

Maps

Specializes

references

Concept model

Schematron rules

AP242 PLCSlib Information Architecturehttp://www.plcs.org/STEPlib/242lib.html

ISO 10303-242ARM EXPRESS

ISO 10303-242BOM EXPRESS

ISO 10303-242BOM SysML

PLCS PSM OWL

ISO 10303-242XML Schema

Maps Transformed

TransformedExchange layer

“Core/standard” Information layer

“Business/Domain” layer

Business/Domain model

Maps Templates OWL

Ref. DataMaps

Maps

Specializes

references

AP242 PLCSlib Information Architecturehttp://www.plcs.org/STEPlib/242lib.html

ISO 10303-242ARM EXPRESS

ISO 10303-242BOM EXPRESS

ISO 10303-242BOM SysML

PLCS PSM OWL

ISO 10303-242XML Schema

Maps Transformed

TransformedExchange layer

“Core/standard” Information layer

“Business/Domain” layer

Business/Domain model

Maps Templates OWL

Ref. DataMaps

Maps

Specializes

references

As an exercise to investigate applicability of approach to AP242 we did the following:1) Ran REEPER on AP242 BOM EXPRESS to generate BOM

SysML2) Drew a subset of SysML Block Diagrams in Magicdraw3) Developed Templates for part using same scope of PLCS

Part Assembly Template. • Classifier• DatedEffectivity• Descriptor• Indentification• Name• Part• PartAssembly• ViewDefinitionContext

ISO 10303-242BOM SysML

ISO 10303-242 BOM SysML Block Definition diagram

Direct equivalent of PSM EXPRESSSysML reflects XSD encapsulation

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; id : OPTIONAL IdentifierSelect; description : OPTIONAL DescriptorSelect; classifiedAs : OPTIONAL SET[1:?] OF Classification; relationType : ClassSelect; relating : ActivityMethod; related : ActivityMethod;WHERE WR1: relating :<>: related;(* RBN Encapsulate into relating attribute https://sourceforge.net/p/plcslib/plcs-psmmodel/205/*) encapsulateInto: EXISTS(relating);END_ENTITY;

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.