Dr Rob Bodington Eurostep

PLCSlib - background

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

Historical tour What is a DEX Real example

History

2005 ISO 10303-239 edition1 DEXlib

DEXs, ISO 10303-28 XML Schema,

2010 ISO 10303-239 edition2 PLCSlib developed

2012 PLCSlib adopted by OASIS PLCS TC

DEXS PLCS PSM XML Schema

PLCS Background: Where we were 2005-2010

Business need Clear business requirement for the use of PLCS Has traction in terms of customer requests

Norway’s NDLO, UK MOD, NATO, USAF, US NAVSEA, US Army, Sweden’s FMV, France’s SIMMT etc.

Implementations Notable implementation successes

Some industrial deployments/pilots BAE Systems, Volvo, Airbus, Boeing, FMV, Kongsberg, Kockums, UK MoD, AM General, ….

Used live from Afghanistan Some commercial tool support

PLCS as a standard - ISO 10303-239 Has a second edition in preparation

Small increase in scope Greater compatibility with Systems Engineering and PLM ISO standards

…. the PLCS model satisfies a business need

… the implementations have delivered real business value

… but requires experts and in-depth knowledge

PLCS Background: Where we were 2005-2010

PLCS as OASIS standards Many DEXs but only one DEX as OASIS standard

But standardized components e.g. templates + ref data

Focus on Business DEXs rather than standard DEXs Built from standardized components

Take up Limited take up by COTS software providers, systems integrators, OEMS Limited number of experts

Technology Does not use mainstream software technology and practices Comprehensive but complex information model Inefficient implementations

ISO 10303-28 XML Schema for PLCS overly complex, redundant entities and attributes in the model that lead to large file size and a complex model

Hence ….. need to remove barriers to PLCS exploitation

Opportunities

Experience Experience available from:

Specifying data exchanges Production level implementations

New Technology Since PLCS project, newer technologies that address some of the core needs “Out of the Box”

have matured so enables reduction in bespoke technologies OMG Model Driven Architecture / Enterprise Architecture approaches OMG UML is closer to EXPRESS in its declarative capability and is far more widely adopted OMG SysML is a UML profile that provides the full capabilities required by the DEX specification process

STEP developments AP242 requirements for a business object model

Advantage Take advantage of experience and new technology to:

Exploit mainstream technology Integrate PLCS into an Architecture Framework approach Provide higher level perspective on the information model Make the information model easier to implement and understand Make it easier to specify data exchanges Hence enables quality improvement

Challenges addressed: 2010 - 2012

Business challenges To make DEXs more understandable to business & technical users To align with Enterprise Architecture approaches To make the standard easier to understand

To determine whether PLCS meets project needs/requirements To make it easier to specify standards based exchanges To make Data Exchange Specification(DEX) development easier and faster

Technical challenges To move the standard to use mainstream technology

UML technologies versus EXPRESS + OASIS PLCS TC e.g templates bespoke technology XML technologies used the way implementers expect

To support both file based and service based exchanges To make implementation quicker To make the resulting exchange capability more efficient

Project challenge Do the above without changing the standard core of PLCS because it has been

demonstrated to deliver real business value

Achievements

Integrated set of PLCS information: PLCSlib Managed by: OASIS PLCS TC:

https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=plcs

Developed as an open source Sourceforge project: https://sourceforge.net/projects/plcslib/

Published daily: http://www.plcs.org/plcslib/

Training Videos http://plcslib.sourceforge.net/docs/plcslib_videos/

Technology Adoption of OMG’s SysML Improved XML Schema + use of Schematron

Information Model UML Concept model Implementation model – PSM

Derived from AP239 ed2 Aligned with AP242 Business Object Model EXPRESS SysML XML Schema + Schematron

OWL based reference data

DEX architecting tools SysML based templates & DEXs

Status

DEXlib is to be deprecated OASIS PLCS TC focus is on PLCSlib

All future development will be based on PLCSlib components Exchanges based on the PLCS PSM – XML Schema

PLCS PSM to be published as an OASIS standard A number of DEXs been developed using new approach

Modelling & simulation management Maintenance feedback Maintenance & Repair Long term archiving of product design data

Topics

Historical tour What is a DEX Real example

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

Historical tour What is a DEX Real example

C O P Y R I G H T E U R O S T E P G R O U P

UK Ministry of Defence project:» Partners:

− UK Ministry of Defence− LOG NEC Delivery Partner (Boeing Defense UK), Eurostep,

Rolls-Royce

C O P Y R I G H T E U R O S T E P G R O U P

?

ISO 10303-

239

?

LITS

PLCS translator

PLCS translator

ISO 10303-

239

PLCS translator

?

ISO 10303-

239

PLCS translator

Turbounion RB199

LITS extract

Front line maintenance

Servicing and availability management

RAF Scenario

C O P Y R I G H T E U R O S T E P G R O U P

ROCET PLCS pilot 2010» Based on:

− UK Defence DEXs− Ap239 ed1 / DEXlib

» Used EXPRESS technology for translators

» Issues:− File size too large − Poor signal to noise ratio caused by /IGNORE− XML Schema complexity− Difficult to “debug” XML files

C O P Y R I G H T E U R O S T E P G R O U P

Evaluation environmentDeveloped using Eurostep’s PLCS Java toolbox

Developed using XML Beans Java

Developed using XSLT

Compare

C O P Y R I G H T E U R O S T E P G R O U P

Results

Schema OASIS templates Business templates

Total Templates

AP239 P28 12 7 19PLCS PSM 9 4 13

MoD_EAM_Extract 6%

AP239 P2885%

PLCS PSM9%

File size

MoD_EAM_Extract AP239 P28PLCS PSM

MoD_EAM_Extract

15%

AP239 P2858%

PLCS PSM27%

XML Element Type count

MoD_EAM_Extract AP239 P28PLCS PSM

Schema Total XML Elements

Total XML Attributes

Total XML Element types

Total XML attributes: /IGNORE

Total XMLattributes: /NULL

MoD_EAM_Extract 3,081 1 27 0 0AP239 P28 45,266 32,896 105 9,601 288PLCS PSM 5,260 4,079 48 0 0PLCS PSM MultId 6,017 3,876 53 0 0PLCS PSM ShortName 5,260 4,079 48 0 0

Schema File size Indented XML

File size no indentation

File size compressed

MoD_EAM_Extract 249,119 132,171 5,176AP239 P28 2,108,270 1,972,220 61,260AP239 P21 429,395 41,540PLCS PSM 317,136 218,786 11,628PLCS PSM MultId 352,796 236,680 14,603PLCS PSM ShortName 225,832 134,427 11,319

Note: Results based on PLCS PSM Q1 2012 – prior to 242 harmonization

C O P Y R I G H T E U R O S T E P G R O U P

Results

Schema File size Indented XML

File size no indentation

File size compressed

MoD_EAM_Extract 11.8% 6.7% 8.4%

AP239 P28 100.0% 100.0% 100.0%

PLCS PSM 15.0% 11.1% 19.0%

PLCS PSM MultId 16.7% 12.0% 23.8%

PLCS PSM ShortName 10.7% 6.8% 18.5%

Schema File size Indented XML

File size no indentation

File size compressed

MoD_EAM_Extract 100.0% 100% 100.0%

AP239 P28 846.3% 1492.2% 1183.5%

PLCS PSM 127.3% 165.5% 224.7%

PLCS PSM MultId 141.6% 179.1% 282.1%

PLCS PSM ShortName 90.7% 101.7% 218.7%

Note: Results based on PLCS PSM Q1 2012 – prior to 242 harmonization

C O P Y R I G H T E U R O S T E P G R O U P

Conclusion» The PSM XML is significantly smaller than the AP239 P28 file and comparable to the

bespoke E&AM schema exchange

» The PSM XML is easily processed by off the shelf XML technology− XSLT− XML Schema, Schematron− Java, .NET

» Validation of the XML data, both syntactically and semantically can be done with a combination of − XML Schema− Schematron

» DEX development and deployment is readily achieved by use of mainstream COTS software

» Post project:− PLCS PSM and PLCSlib accepted by OASIS PLCS TC− Migration from DEXlib to PLCSlib agreed

C O P Y R I G H T E U R O S T E P G R O U P

Conclusions» PLCS works» PLCS is delivering business values» The new approach makes PLCS more accessible

Challenges addressed: 2010 - 2012

Business challenges To make DEXs more understandable to business & technical users To align with Enterprise Architecture approaches To make the standard easier to understand

To determine whether PLCS meets project needs/requirements To make it easier to specify standards based exchanges To make Data Exchange Specification(DEX) development easier and faster

Technical challenges To move the standard to use mainstream technology

UML technologies versus EXPRESS + OASIS PLCS TC e.g templates bespoke technology XML technologies used the way implementers expect

To support both file based and service based exchanges To make implementation quicker To make the resulting exchange capability more efficient

Project challenge Do the above without changing the standard core of PLCS because it has been

demonstrated to deliver real business value

Integrated set of PLCS information: PLCSlib

Managed by: OASIS PLCS TC: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=plcs

Developed as an open source Sourceforge project: https://sourceforge.net/projects/plcslib/

Published daily: http://www.plcs.org/plcslib/

Training Videos http://plcslib.sourceforge.net/docs/plcslib_videos/

AP239 ed2 Summary of changes

Used latest editions of modules

Extended Selects

Added: System / non abstract Product Analysis Validation & verification Risk

Created: Collection Product Environment Same-as Conditional effectivity Identification relations

Modified: Message Observation Resources Product category – removed from modules Justification – added assumption