1 / 25

PLCSlib - background

PLCSlib - background. 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

orenda
Download Presentation

PLCSlib - background

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. PLCSlib - background Dr Rob BodingtonEurostep

  2. 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 • RASSCproject (UK TSB R&D project)

  3. Topics • Historical tour • What is a DEX • Real example

  4. 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

  5. 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

  6. 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

  7. 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

  8. 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

  9. 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

  10. 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

  11. Topics • Historical tour • What is a DEX • Real example

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

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

  14. Topics • Historical tour • What is a DEX • Real example

  15. UK Ministry of Defence project: • Partners: • UK Ministry of Defence • LOG NEC Delivery Partner (Boeing Defense UK), Eurostep, Rolls-Royce

  16. RAF Scenario

  17. 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

  18. Evaluation environment Developed using Eurostep’s PLCS Java toolbox Compare Developed using XML Beans Java Developed using XSLT

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

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

  21. 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

  22. Conclusions • PLCS works • PLCS is delivering business values • The new approach makes PLCS more accessible

  23. 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

  24. 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/

  25. 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

More Related