Proposed PLCS TC Organization and Functional Responsibilities Revision 2 050210

1. Proposed PLCS TC Organization and Functional Responsibilities Revision 2 050210

2. PLCS TC Organization and Participants • Hierarchical Functional Responsibility Agenda

3. ChairSecretariat1 Voting Member per CompanyTechnical LeadImplementers Forum Lead 1 Secretariat OASIS TC Technical Oversight Pilots/Projects Quality Assurance LeadTesters Norwegian PilotUK MOD PilotSwedish PilotOthers Lead (Information Architect)2 Tool Experts2 Business Experts Secretariat PLCS TC Organization and Participants OASIS TC Management Technical Development Oversight for DEX, Capabilities, and Reference Data and other documentation Related, independent Projects/Pilots established for a business need. Efforts are shared with PLCS TC Ensures material submitted for OASIS balloting meet requirements. Works closely with Implementers Forum

4. ChairSecretariat1 Voting Member per CompanyTechnical LeadImplementers Forum Lead 1 Secretariat OASIS TC Technical Oversight Pilots/Projects Quality Assurance LeadTesters Norwegian PilotUK MOD PilotSwedish PilotOthers Lead (Information Architect)2 Tool Experts2 Business Experts Implementers Forum LeadSoftware Product VendorsImplementersIntegrators Secretariat DEX 0 Development Team DEX 1 Development Team Pilot/Project Test Runs DEX 2 Development Team DEX X Development Team DEX Y Development Team Infrastructure / Tool Team Information Architect1 Tool Expert DEX Development Teams 1 Team Lead 1 Modeler 1 Business Expert PLCS TC Organization

5. 1 Secretariat OASIS TC Secretariat ChairSecretariat1 Voting Member per CompanyTechnical LeadImplementers Forum Lead • Publish AP239 as IS • Monitor and Maintain AP239 • PLCS TC Administration • PLCS TC Work Programme Management • Balloting within PLCS TC • Publishing within OASIS • Communications • Marketing Organization Functionality – OASIS TC

6. Technical Oversight Lead (Information Architect)2 Tool Experts2 Business Experts • Provide Technical Oversight for DEX, Capability, and Reference Data Development • Establish and maintain documentation • Review DEXs, capabilities and reference data • Harmonize with established SC4 and related standards Organization Functionality – Technical Oversight

7. Technical Oversight Lead (Information Architect)2 Tool Experts2 Business Experts DEX Development Teams 1 Team Lead 1 Modeler 1 Business Expert • Develop Capabilities • Develop DEX Packages • Develop Reference Data • Develop Rules Organization Functionality – DEX Development Teams

8. Technical Oversight Infrastructure/Tool Team Information Architect1 Tool Expert Lead (Information Architect)2 Tool Experts2 Business Experts • DEXLib Infrastructure • DEX specification template • Reference Data Library Infrastructure • DEXLib Tools Organization Functionality – Infrastructure/Tool Team

9. Quality Assurance LeadTesters • Establish Quality Framework • Establish and Liaison with Implementers Forum • Ensure submissions meet requirements for OASIS Balloting • Verify and Validate DEX Team Testing Organization Functionality – Quality Assurance

10. Implementers Forum Quality Assurance LeadSoftware Product VendorsImplementersIntegrators LeadTesters • Testing • Reuse of solutions • Review and recommend changes Organization Functionality – Implementers Forum

11. Pilots/Projects Norwegian PilotUK MOD PilotSwedish PilotOthers • Establish DEX Development Teams under Technical Oversight • Establish Pilot Test runs with Implementers Forum • Development of non-OASIS documentation • Share results and lessons learned Organization Functionality – Pilots/Projects

12. PLCS TC Organization Summary ChairSecretariat1 Voting Member per CompanyTechnical LeadImplementers Forum Lead 1 Secretariat OASIS TC Technical Oversight Pilots/Projects Quality Assurance LeadTesters Norwegian PilotUK MOD PilotSwedish PilotOthers Lead (Information Architect)2 Tool Experts2 Business Experts Secretariat • Publish AP239 as IS • Monitor and Maintain AP239 • Balloting within PLCS TC • Publishing within OASIS • PLCS TC Administration • PLCS TC Work Programme Management • Communications • Marketing • Provide Technical Oversight for DEX, Capability, and Reference Data Development • Establish and maintain documentation • Review DEXs, capabilities and reference data • Harmonize with established SC4 and related standards • Establish DEX Development Teams under Technical Oversight • Establish Pilot Test runs with Implementers Forum • Development of non-OASIS documentation • Share results and lessons learned • Establish Quality Framework • Establish and Liaison with Implementers Forum • Ensure submissions meet requirements for OASIS Balloting • Verify and Validate DEX Team Testing

13. The END! Or, just the Beginning?

14. 1 Secretariat OASIS TC Secretariat ChairSecretariat1 Voting Member per CompanyTechnical LeadImplementers Forum Lead • Publish AP239 as IS • Prepare resolution programme • Submit to ISO for publication • Issue as IS • Monitor and Maintain AP239 • Implement change programme • Monitor SC4 modules for input on AP239 • Submission of change requirements to SC4 Organization Functionality – OASIS TC

15. ChairSecretariat1 Voting Member per CompanyTechnical LeadImplementers Forum Lead 1 Secretariat OASIS TC Secretariat • PLCS TC Administration • Meetings and conference calls • Identify potential future DEXs • Develop Business Ontology • OASIS exploders • OASIS PLCS TC Website • Administration of DEXs, capabilities, reference data, documentation tool through the ballot process Organization Functionality – OASIS TC

16. ChairSecretariat1 Voting Member per CompanyTechnical LeadImplementers Forum Lead 1 Secretariat OASIS TC Secretariat • Balloting within PLCS TC • Rules for approval of methods • Agree process for review / ballot / update / maintenance of technical documentation • Review DEXs and Reference Data submitted for OASIS standards • PLCS TC balloting, OASIS balloting, publishing and regular reporting to OASIS members Organization Functionality – OASIS TC

17. ChairSecretariat1 Voting Member per CompanyTechnical LeadImplementers Forum Lead 1 Secretariat OASIS TC Secretariat • Publishing within OASIS • Procedures for publishing • Agree with OASIS how the DEXs are to be published, i.e. what format. • Agree with OASIS how to publish Reference data • Publish • DEXs as OASIS standards • Core PLCS Reference Data • Business domain extensions as standardized extensions to PLCS Reference Data Organization Functionality – OASIS TC

18. ChairSecretariat1 Voting Member per CompanyTechnical LeadImplementers Forum Lead 1 Secretariat OASIS TC Secretariat • PLCS TC Work Programme Management • Agreed programme of work • Establish resource requirement • Agreed prioritization of tasks and resources • Agreed allocation of programme tasks • Establish and maintain a detailed project plan • Manage activities described in the project plan • Recommend additional activities • Identify actions relevant for the OASIS TC scope • Track progress Organization Functionality – OASIS TC

19. ChairSecretariat1 Voting Member per CompanyTechnical LeadImplementers Forum Lead 1 Secretariat OASIS TC Secretariat • Communications • SC4 AP239 relevant working groups • OASIS PLCS Teams • Implementers Forum • Pilots/Projects • Marketing • Promotion • Maintain library of success stories • Maintain library of presentations for PLCS member reference • Outreach needed to spread word on PLCS value Organization Functionality – OASIS TC

20. Technical Oversight Lead (Information Architect)2 Tool Experts2 Business Experts • Provide Technical Oversight for DEX, Capability, and Reference Data Development • Administer the Technical Development work programme • Establish a standardized, stable Business Ontology for PLCS • Consolidate existing Reference Data files to establish baseline core • Agree DEX and Reference Data development processes • Establish API for PLCS • Specify a representation of a thesaurus of business concepts reflecting business terms • Incorporate the recommendations from the series of DEX Sync Workshops • Agree how Reference Data will be maintained • Develop Rule types for DEXs and capabilities Organization Functionality – Technical

21. Technical Oversight Lead (Information Architect)2 Tool Experts2 Business Experts • Establish and maintain development documentation guidance • Format and content • Rules • Guidelines • Capabilities, Data Exchange Sets, and Reference Data • Mapping • Testing and Test documentation • Business Concepts • Translators • Conformance Guidance/Requirements Organization Functionality – Technical

22. Technical Oversight Lead (Information Architect)2 Tool Experts2 Business Experts • Establish and maintain usage documentation guidance • Business user guidance • Software implementer guidance • Contract managers guidance • Specialisation pruning of DEXs Organization Functionality – Technical

23. Technical Oversight Lead (Information Architect)2 Tool Experts2 Business Experts • Review DEXs, capabilities, and reference data • Reduce duplicate development and improve interoperability • Ensure submissions meet OASIS ballot requirements • Harmonization within PLCS TC of • Reference data • Interpretations / mapping solutions • Translators • Mappings • Projects • Impact of SC4 module changes on DEXs Organization Functionality – Technical

24. Technical Oversight Lead (Information Architect)2 Tool Experts2 Business Experts • Harmonize with established SC4 and related standards • Harmonisation with SC4 standards • 10303 STEP APs • 13584 PLIB • 15926 Oil & Gas • Harmonisation with other standards • ASD (AECMA) 1000D and 2000M • MIP • OAGIS 9 • OMG • SCORM • UK MOD 00-60 • W3C Organization Functionality – Technical

25. DEX Development Teams 1 Team Lead 1 Modeler 1 Business Expert Technical Oversight Lead (Information Architect)2 Tool Experts2 Business Experts • Develop Capabilities • Develop new capabilities as required • Enable representation of instantiation capabilities • Set up a review structure for capabilities Organization Functionality – Technical

26. DEX Development Teams 1 Team Lead 1 Modeler 1 Business Expert Technical Oversight Lead (Information Architect)2 Tool Experts2 Business Experts • Develop DEX Packages • Develop DEX Documentation • Develop Implementation options • Capabilities • Business concepts • DEX Documentation • Reference data • Prune of long forms • Develop a ‘core’ capability set • Initial testing using DEX developed test data • Re-develop initial set of DEXs i.a.w. common agreements) • Incorporate new Reference Data Organization Functionality – Technical

27. DEX Development Teams 1 Team Lead 1 Modeler 1 Business Expert Technical Oversight Lead (Information Architect)2 Tool Experts2 Business Experts • Develop Reference Data • Populate RDL services • Propose reference data from pilot sources • Instantiate reference data • Link with other standards • Develop a programme to monitor the resolution of ballot comments • Develop Rules Organization Functionality – Technical

28. Technical Oversight Infrastructure/Tool Team Information Architect1 Tool Expert Lead (Information Architect)2 Tool Experts2 Business Experts • DEXLib Infrastructure • Develop the DEXLib architecture and a framework explanation • Enhance user friendliness • Indexing mechanism • From the Business Concepts to DEX capabilities • From terminology dictionary to DEXlib • Develop Thesaurus Tool for extracting semantics/definitions • Expand the introduction to DEXLib • Extend existing DEXLib functionality to activate and complete scripts with information • Develop template for exchange agreements as part of each specific DEX • DEXlib publication environment Organization Functionality – Technical

29. Technical Oversight Infrastructure/Tool Team Information Architect1 Tool Expert Lead (Information Architect)2 Tool Experts2 Business Experts • DEXLib Infrastructure (cont’d) • Continue to maintain DEXLib on Source Forge • Maintain an HTML mirror of DEXLib for non- developers • Allow an XML view facility in browsers (other than Internet Explorer) • Extend DEXLib to allow HTML publications • Extend DEXLib to allow individual (or sets of) DEXs to be published as a standalone package electronically and on paper Organization Functionality – Technical

30. Technical Oversight Infrastructure/Tool Team Information Architect1 Tool Expert Lead (Information Architect)2 Tool Experts2 Business Experts • DEX specification template • Develop an agreed DEX template for acceptance by OASIS based on the example DEX “Assembly part list” to DEXLib Organization Functionality – Technical

31. Technical Oversight Infrastructure/Tool Team Information Architect1 Tool Expert Lead (Information Architect)2 Tool Experts2 Business Experts • Reference Data Library Infrastructure • Define reference data architecture • Establish a PLCS web server • Develop Pilot RDL service • Agree and standardised RDL services • Develop industrial strength RDL services • Define management of RDL services • Publish OWL files on the PLCS Web server • Establish PLCS RDL server accessed via APIs from translators • Establish a better development environment for reference data consolidation and management • User-friendly interface to reference data library from DEXLib Organization Functionality – Technical

32. Technical Oversight Infrastructure/Tool Team Information Architect1 Tool Expert Lead (Information Architect)2 Tool Experts2 Business Experts • DEXLib Tools • Develop and maintain tools supporting DEX, Capability and Reference Data development • Tools for the revised DEX architecture containing • business concepts • specializations of generic capabilities and DEXs • rules • Establish tools to develop / view the test data and validate test results • Tool for Work Progress tracking in DEXLib • Tool for converting existing Part 28 file to Part 21 file • Extend DEXlib tool set • User friendly front end • Develop terminology dictionary • Interface to reference data • Allow publication of DEXs and Reference Data • Develop templates for main rule types • Develop scripts for business concepts, using rule templates Organization Functionality – Technical

33. Quality Assurance LeadTesters • Establish Quality Framework • Review Framework for Quality • Editing and approval of DEXs • Establish and Liaison with Implementers Forum • Ensure submissions meet requirements for OASIS Balloting • Verify and Validate DEX Team Testing Organization Functionality – Quality Assurance

34. Implementers Forum Quality Assurance LeadSoftware Product VendorsImplementersIntegrators LeadTesters • Testing • Define new or identify existing industrial strength test data • Develop implementer’s test tools • Test DEXs • Test interoperability by round robin test rallies • Reuse of solutions • Establish library of “Lessons Learned” Organization Functionality – Implementers Forum

35. Implementers Forum Quality Assurance LeadSoftware Product VendorsImplementersIntegrators LeadTesters • Review and recommend changes • Capabilities, DEXs, and Reference Data • Business concepts • Harmonization • Establish guidelines for the implementers • Raise harmonization issues and recommend changes for • Capabilities, DEXs, and Reference Data • Interpretations / mapping solutions • Mappings • Projects/pilots • Translators Organization Functionality – Implementers Forum

36. Pilots/Projects Norwegian PilotUK MOD PilotSwedish PilotOthers • Establish DEX Development Teams under Technical Oversight • Establish Pilot Test runs with Implementers Forum • Development of non-OASIS documentation • Capabilities, DEXs, and Reference Data • Guidelines • Share results and lessons learned • Implementers Forum • OASIS TC • Other DEX Development Teams • Quality Assurance • Technical Oversight Organization Functionality – Pilots/Projects

37. Develop a data exchange template • A "data exchange contract" shall require • Identification of the specific DEX(es) that shall exchange the business data – to enable conformance testing • Identification of standards used, and the resulting usage of reference data • Involved parties need to agree what is their recognized identifier. A text shall be added in the exchange agreement to note the “preferred” option as the one to be used for globally unique identifiers, e.g. for identifiers that may be used for data merge. • Reference Data Library • Class of class definitions in PLCS/OASIS RDL may be needed for contracting purposes. How to define class of class in OWL shall be investigated • Separate OWL project files shall be defined for representation of specific projects and their local terms • Develop DEXs for business implementation • Input recommendations from the synchronisation workshops • Rules shall be uniquely enumerated (in capabilities etc) to allow normative reference to them • Rules shall be placed at the lowest possible level, i.e. in capabilities, without mandating PLCS global rules. Experience will show where the lowest level is. • Expand the introduction to DEXLib. Shall include information as • Data exchange architecture • Reference data • Global identifiers • Rules • Graphical presentation of information in DEXLib shall be considered • User-friendly interface to reference data library from DEXLib • Graphical representation of reference data hierarchy HTML version Measures of Goodness