Recommendations from PLCS TOG Meeting Filton, UK Aug 2011

Objectives  to review the new approach to building DEXs and make recommendations to the PLCS OASIS Technical Committee as to how to proceed 2 PLCS Inc. (c) 2002

Attendees  Tor Arne Irgens – NDLO (Chair)  Jim Illbach – Boeing (Host)  Phil Rutland – UK MoD  James Nyambayo – LSC  Mats Nilsson – FMV  Fredrik Lied Larsen - DNV  Leif Gylstrom- SAAB  Sean Barker – BAE Systems  Howard Mason – BAE Systems (day 2)  Rob Bodington – Eurostep 3 PLCS Inc. (c) 2002

Naming conventions  PLCS - everything to do with PLCS  AP239ed2 - the ISO standard  PLCSlib - new version of Dexlib that has been prototyped  PLCS SysML model - the implementation model 4 PLCS Inc. (c) 2002

What was shown  PLCSlib  SysML based development environment and model to replace DEXlib & associated tools  Prototyped by Eurostep & DNV under contract to NDLO  Developed further by Eurostep  See slides presented at previous TC meetings for details  PLCSlib based DEX developed by Eurostep under contract to Black & Rossi. Including:  Maintenance & Repair DEX  A set of templates  A set of reference data  XML Schema derived from PLCS SysML model (PLCS PSM)  DEX specific XML Schema – derived from a subset of PLCS PSM  A set of example XML data  Documentation as to how to create a DEX 5 PLCS Inc. (c) 2002

Process of evaluation  Identified critical / key stakeholder requirements  Grouped according to whether Stakeholder requirement:  Has been addressed by PLCSlib  Needs further consideration 6 PLCS Inc. (c) 2002

It should be easy to go from a perceived business need to a deployed solution DEXs + components (DEXs) should be easy to develop / maintain / validate DEXs should be reusable Skills and technologies required to develop/maintain/validate DEXs should be mainstream with a large user base to ensure the persistence of tools and techniques Final result should be easy to use / deploy Resulting solutions should be efficient Resulting data files should be easier to deploy, efficient in use of bandwith and processing requirements for creation and consumption Support the semantic content of AP239ed2 and its common components with AP233 Not necessary to explicitly map from DEXlib DEXs to PLCSlib DEXs 7 PLCS Inc. (c) 2002 Stakeholder requirements - Addressed by PLCSlib

 Resulting published DEXs should be usable/accessible/discrete packages  DEXs should be under effective configuration change management  It must be possible to develop DEXs in a collaborative environment  Requirement to be compatible with existing STEP protocols. That is required information can be transferred in either direction maintaining semantic integrity  Can be published as an ISO STEP standard  Processes should developed to manage the evolution of the PLCS 8 PLCS Inc. (c) 2002 Stakeholder requirements - Future considerations

TOG recommendations to TC: What  To adopt the new SysML approach  To freeze development within DEXlib and focus OASIS PLCS TC efforts on new approach: PLCSlib  That all future OASIS PLCS TC standards will be based on PLCSlib with DEXlib being deprecated  To request that the implementers forum focus their efforts to PLCSlib based implementations  TC support How  PLCSlib is released into the public domain  All stakeholders review the new approach  TOG provides further webinars to explain approach  TOG develop a plan for completion of PLCSlib Include the development and deployment of at least one DEX  TC determine when to shutdown DEXlib 9 PLCS Inc. (c) 2002

Plan  Release into PLCSlib public domain  Provide further training  Develop some PLCSlib DEXs Timescales:  PLCSlib draft released ASAP  PLCSlib baselined and published before Dec 30. Including: Stable PLCS PSM  Use PSM as is, but change Date / Value in XML Set of templates Set of Ref data Exemplar Dex Guidance on development within PLCSlib Develop checklists as we develop the DEXs + components PLCSlib  XSLT environment  DEXpro  Infrastructure setup  CM process 10 PLCS Inc. (c) 2002