Minutes from PLCS TOG Meeting Filton UK 8

Minutes from PLCS TOG Meeting Filton, UK 8 -9 March 2012

Attendees name organisation Dates attended Phil Rutland UK Mo. D 8/9 Gav King UK Mo. D 8/9 Tony Armstrong UK Mo. D 8/9 Malcolm Button UK Mo. D 8/9 Rob Bodington Eurostep 8/9 Phil Spiby Eurostep 8/9 Mike Day Rolls Royce 8/9 Deb Ham Rolls Royce 8/9 Des Willans Boeing UK Defence 8/9 Trine Hansen DNV 9 Fredrik Lied Larsen DNV 8/9 Tor Arne Irgens NDLO 8/9 Scott Motquin LOGSA 8/9 Mats Nilsson FMV 8/9 James Nyambayo LSC 8/9 2

Implementers forum outline from Scots presentation 1 of 3 PLCS Implementors Forum - Purpose Reduce barriers to and risk of implementations Provide feedback to PLCS standards developers based on experience of implementation Verify software implementation supports specific DEX capabilities Verify interoperability of PLCS software Publish recommended practices to PLCS community Define Conformance & Compliance PLCS IF Phase Approach Phase I – Concept Phase II – Design Phase III - Development Phase IV – Sustainment PLCS-IF Completed Efforts Concept of Operations (CONOPS) Provides high level description of PLCS-IF requirements, processes, roles, and responsibilities Provides principles and practices envisioned to support DEX testing Workshops held in Charleston, SC Input from domestic and international stakeholders Input from industry and governmen PLCS Inc. (c) 2002 3

Implementers forum outline from Scots presentation 2 of 3 PLCS-IF Current Efforts Major Deliverables Software Design Description (SDD) Public and Private Webpages Public, Forum. . (test cases, lessons learned, best practices, etc) Private, Test result, member only information Provides detailed design principles required to implement CONOPS PLCS Tool Kits Surveys Demonstration Evaluation “Hello World” Business DEX Bill of Material Test & Sample Data PLCSlib Strategic Communication Plan PLCS Inc. (c) 2002 4

Implementers forum outline from Scots presentation 3 of 3 PLCS-IF Next Steps Development Phase Build Develop Public and Private web portal (technical infrastructure) Phased approach Secure logon Syntax and Structure checking Semantic analysis Identify Business Test Case Test Phase Gather test data (from business test cases) Demonstrate/Verify system Develop Usage Guide Potential Deliverable Software Development Plan Prototype Sustainment Phase Provide program management activities to maintain test environment Provide testing documentation Monitor and promote forum participation Promote usage of PLCS Coordination of testing PLCS Inc. (c) 2002 5

Reference Data (to be updated) PLCS Inc. (c) 2002 6

Artifacts to be standardized artifacts Arena for standardisation Arena for governance infrastructure ISO 10303 AP 239 Activity model ISO TC 184 SC 4 ISO PLCS PSM Express PLCS PSM Sys. ML XMI PLCS PSM RD PLCS PSM XSD OASIS Std OASIS PLCS TC PLCSLib Templates DEXs OASIS TC Spec OASIS PLCS TC PLCSLib PLCS RD OASIS TC Spec OASIS PLCS TC PLCSLib Web services OASIS TC Spec OASIS PLCS TC tbd Business domain Templates Domain domain PLCSLib Business domain DEXs Domain domain PLCSLib Business domain RD Domain domain PLCSLib and assosiated tools NA PLCS TOG Claim of SW vendor to PLCS conformance/compliance (e. g. Adaptors/repositories/applications) IF 7

Recommendations to TC 1 of 2 1. Confirm recommendation that all future development be done using PLCSlib 2. Recommend acceptance of proposed changes to PLCS PSM, and corresponding PLCS PSM Reference Data v 3. Some issues to be addressed Recommend acceptance of XML Schema in principle, but recommend that it reviewed further – 2 weeks v Some issues to be addressed 4. Recommend that the harmonized PSM is frozen be end March 2012. Further harmonization with AP 242 should continue and changes proposed will be considered for incorporation at a later date. 5. Recommend PLCS PSM, XML Schema and PLCS PSM Reference Data are put forward for standardization as OASIS standards 6. Recommended that the PLCSlib templates, PLCS ref. data and exemplar DEX are reviewed and then the template and ref data standardized as OASIS Committee Specifications PLCS Inc. (c) 2002 8

Recommendations to TC 2 of 2 PLCS Implementers Forum 1. 2. 3. The IF is very welcome but the relationship between the TC and the IF needs to be strengthened Concern that a single proprietary piece of software will be used as the reference There is not a clear relationship between the IF, the TC and TOG. 1. 2. The purpose of the TOG and the TC is partially duplicated by the IF. This should be clarified. Is the IF focused on: 1. 2. 3. Recommend that there is one set of Model Usage Guidance 1. 2. 3. 4. 5. 6. Interoperability conformance of PLCS implementations or “the goodness” of DEX PLCSIF use PLCSlib, with all Model Usage Guidance developed using PLCSlib The governance procedure for the usage guidance should be the same as the rest of PLCSlib Recommend that the usage guide should be an informative annex to the PLCSlib standards Recommend that the PLCSIF publish the exemplar DEXs on PLCSlib The TC needs to clarify what our expectations are of the IF Suggest a (2 day) workshop for the TC to address this issue. The IF should be invited. PLCS Inc. (c) 2002 9