Recommendations from PLCS TOG Meeting Filton UK 23

  • Slides: 10
Download presentation
Recommendations from PLCS TOG Meeting Filton, UK 23 -24 Aug 2011

Recommendations from PLCS TOG Meeting Filton, UK 23 -24 Aug 2011

Objectives v to review the new approach to building DEXs and make recommendations to

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

Attendees v v v v v Tor Arne Irgens – NDLO (Chair) Jim Illbach

Attendees v v v v v Tor Arne Irgens – NDLO (Chair) Jim Illbach – Boeing (Host) Phil Rutland – UK Mo. D 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 PLCS Inc. (c) 2002 3

Naming conventions v v PLCS - everything to do with PLCS AP 239 ed

Naming conventions v v PLCS - everything to do with PLCS AP 239 ed 2 - the ISO standard PLCSlib - new version of Dexlib that has been prototyped PLCS Sys. ML model - the implementation model PLCS Inc. (c) 2002 4

What was shown v PLCSlib v v v Sys. ML based development environment and

What was shown v PLCSlib v v v Sys. ML 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: v v v v Maintenance & Repair DEX A set of templates A set of reference data XML Schema derived from PLCS Sys. ML 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 PLCS Inc. (c) 2002 5

Process of evaluation v v Identified critical / key stakeholder requirements Grouped according to

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

Stakeholder requirements - Addressed by PLCSlib ü It should be easy to go from

Stakeholder requirements - Addressed by PLCSlib ü 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 bandwidth and processing requirements for creation and consumption ü Support the semantic content of AP 239 ed 2 and its common components with AP 233 ü Not necessary to explicitly map from DEXlib DEXs to PLCSlib DEXs PLCS Inc. (c) 2002 7

Stakeholder requirements - Future considerations v Resulting published DEXs should be usable/accessible/discrete packages v

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

TOG recommendations to TC: What v To adopt the new Sys. ML approach v

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

Plan v v v Release into PLCSlib public domain Provide further training Develop some

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