PLCSlib Overview PLCSlib Acknowledgements Norwegian Defence Logistics Organisation UK MoD Defence Equipment and Support DEampS Swedens FMV French MoD SIMMT Boeing ID: 704794
Download Presentation The PPT/PDF document "Dr Rob Bodington Eurostep" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Dr Rob Bodington Eurostep
PLCSlib - OverviewSlide2
PLCSlib - AcknowledgementsNorwegian 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)Slide3
TopicsTechnical drivers
Information architecture overview
Information layer
Exchange layer
Business / Domain layer
Applicability of approach to AP242 BOMSlide4
TopicsTechnical drivers
Information architecture overview
Information layer
Exchange layer
Business / Domain layer
Applicability of approach to AP242 BOMSlide5
Technical driversCore information model that is:
Founded in AP239 ed2 ARM
Easier to understand,
E
asier 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 toolsSlide6
TopicsTechnical drivers
Information architecture overview
Information layer
Exchange layer
Business / Domain layer
Applicability of approach to AP242 BOMSlide7
PLCS Information Architecture
ISO 10303-239
ARM 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. Data
Maps
Maps
Specializes
references
Concept model
Schematron
rulesSlide8
TopicsTechnical drivers
Information architecture overview
Information layer
Exchange layer
Business / Domain layer
Applicability of approach to AP242 BOMSlide9
Core information model
ISO 10303-239
ARM 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 EXPRESS
SysML reflects XSD encapsulation
SysML 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 PSM
XSD uses same approach as Ap242Slide10
Core information model
ISO 10303-239
ARM 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
rulesSlide11
Scope of PLCS: Concept modelhttp://docs.oasis-open.org/plcs/plcslib/v1.0/cs01/data/PLCS/concept_model/model_base.html
Slide12
Scope of PLCS and supported historieshttp://docs.oasis-open.org/plcs/plcslib/v1.0/cs01/data/PLCS/concept_model/model_base.html
Design and Individual
Configurations
Activities
performed by people and product
States
failure &
operational
Change ManagementSlide13
Core information model
ISO 10303-239
ARM 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 EXPRESS
SysML reflects XSD encapsulation
SysML enables formal mapping to domain model
PLCS PSM XML Schema
Transformed
Schematron
rulesSlide14
PLCS PSMhttp://docs.oasis-open.org/plcs/plcslib/v1.0/cs01/data/PLCS/psm_model/model_base.html
Aligned with AP242 BOM
EXPRESS -> SysML
SysML
Represent encapsulations
Enables mapping via parametric diagrams
Easier to view/navigate model than STEPmod based APSlide15
Core information model
ISO 10303-239
ARM 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
rulesSlide16
PLCS PSMhttp://
docs.oasis-open.org/plcs/plcslib/v1.0/cs01/data/PLCS/psm_model/refdata/plcs-psm-en.owl
OWL converted from PSM forms “upper” ontology
Domain specific class are specializations of “upper” ontology
. E.g.
Date / times
Idenitifiers
Activities
Properties
UnitsSlide17
Reference Data
Meta data
SKOS
Dublin Core
PLCS
model
plcs-psm-en.owl
plcs-psm-sv.owl
PLCS
ref
data
plcs-rdl-en.owl
plcs-rdl-sv.owl
Domain
ref
data
<domain>-
en.owl
<domain>-
sv.owl
imports
imports
imports
Business Objects Templates
Business process
PLCS PSM XSD
PLCS PSMSlide18Slide19
TopicsTechnical drivers
Information architecture overview
Information layer
Exchange layer
Business / Domain layer
Applicability of approach to AP242 BOMSlide20
Core information model
ISO 10303-239
ARM 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 PSM
XSD uses same approach as Ap242Slide21
PLCS PSM XSDhttp://docs.oasis-open.org/plcs/plcslib/v1.0/cs01/data/PLCS/psm_model/plcs_psm.xsd
http://
docs.oasis-open.org/plcs/plcslib/v1.0/cs01/data/PLCS/psm_model/common.xsd
Aligned with AP242 BOM
Schematron
+ XSD used for data validation
XSD intended to be
e
asier to use than P28 XSD
Encapsulation of assignments, relationships Slide22
Core information model
ISO 10303-239
ARM 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 EXPRESS
SysML reflects XSD encapsulation
SysML 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 PSM
XSD uses same approach as Ap242Slide23
TopicsTechnical drivers
Information architecture overview
Information layer
Exchange layer
Business / Domain layer
Applicability of approach to AP242 BOMSlide24
Templates & Business / Domain model
ISO 10303-239
ARM 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. Data
Maps
Maps
Specializes
references
Concept model
Schematron
rulesSlide25
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 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
a
re computer
interpretable
and
can be the basis for code generationSlide26
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 PSMSlide27
SysML Block definition diagramSlide28
SysML Block definition diagram
SysML Block: Business object representing pattern of
objects: A
template
Pattern of
PLCS PSM objects
to be instantiated by the templateSlide29
SysML Block definition diagram
Template: SysML Block
Template: Parametric Diagram
Template:
Output ports
Template:
Public properties
Template: C
onstraints
Template:
Private properties
Pattern of
PLCS PSM objects
to be instantiated by the
template defined by parametric diagramSlide30
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 hoursSlide31
Business Objects Model
PLCS PSM XSD
maps
Templates
Transformed
maps
PLCS PSM
Organization A
Organization B
specifies
Exchange process
System model
System model
Ref. Data
uses
specializes
Translator
Translator
System A
System
B
Data Exchange Specification (DEX)
maps
maps
1) Why exchange data?
2) What data to be exchanged?
3) How to exchange data?
ReferencesSlide32
TopicsTechnical 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 thatSlide33
PLCS Information Architecture
ISO 10303-239
ARM 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. Data
Maps
Maps
Specializes
references
Concept model
Schematron
rulesSlide34
AP242 PLCSlib Information Architecturehttp://www.plcs.org/STEPlib/242lib.html
ISO
10303-242
ARM EXPRESS
ISO
10303-242
BOM
EXPRESS
ISO 10303-242
BOM SysML
PLCS PSM OWL
ISO 10303-242
XML
Schema
Maps
Transformed
Transformed
Exchange layer
“Core/standard” Information layer
“Business/Domain” layer
Business/Domain model
Maps
Templates
OWL
Ref. Data
Maps
Maps
Specializes
referencesSlide35
AP242 PLCSlib Information Architecturehttp://www.plcs.org/STEPlib/242lib.html
ISO
10303-242
ARM EXPRESS
ISO
10303-242
BOM
EXPRESS
ISO 10303-242
BOM SysML
PLCS PSM OWL
ISO 10303-242
XML
Schema
Maps
Transformed
Transformed
Exchange layer
“Core/standard” Information layer
“Business/Domain” layer
Business/Domain model
Maps
Templates
OWL
Ref. Data
Maps
Maps
Specializes
references
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
ViewDefinitionContextSlide36
ISO 10303-242
BOM SysML
ISO 10303-242 BOM SysML
Block Definition diagram
Direct equivalent of PSM EXPRESS
SysML reflects XSD encapsulation
SysML reflects EXPRESS rules in OCL
See:
http
://
www.plcs.org/STEPlib/242lib.html
Slide37
ISO 10303-242
Part Template as per PLCS Part templates
See:
http
://
www.plcs.org/STEPlib/242lib.html
Slide38
ObservationGeneration 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 encapsulationSlide39
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;Slide40
ConclusionPLCSlib 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.