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

Slides:



Advertisements
Similar presentations
Module N° 4 – ICAO SSP framework
Advertisements

Slide 1 Presentation of the example business concept – DNV Exchange architecture - DNV Summary / issues from last workshop - DNV Presentation of Swedish.
C O P Y R I G H T E U R O S T E P G R O U P Changes to ISO Rob Bodington, Phil Spiby.
OVERVIEW OF Ian Glendinning Target Training Room Target Plaza South 1000 Nicollet Mall Minneapolis, MN September 20-21, 2007 ISO Training -
Quality Label and Certification Processes Vienna Summit 11 April 2014 Karima Bourquard Director of Interoperability IHE-Europe.
PLCS Implementor Forum February 25, Topics  Objectives  How the PLCS-IF will work  Membership and Organization.
ISO TC184/SC4 Future architecture Rotterdam Progress on the Future SC4 Architecture PWI Friday 13 th November 2009.
All Presentation Material Copyright Eurostep Group AB ® On Reference Data Libraries for Product Life Cycle Support David Price 6th NASA-ESA Workshop on.
DEX Publication Project OASIS PLCS TC Telecon 29 April 2008 Trine Hansen.
Project 1 Introduction to HTML.
IRS XML Standards & Tax Return Data Strategy For External Discussion June 30, 2010.
1 Proposed PLCS TC Organization and Functional Responsibilities Revision
DCMO - CIO Architecture Federation Pilot Larry Singer 5 January, 2012.
1st Project Introduction to HTML.
Product Life Cycle Support (PLCS) The Information Backbone to transform the Logistics Enterprise PLCSlib status PLCS OASIS TOG Filton, UK Rob.
Proposed TC Issues Process Martin Chapman. Purpose An issues driven process helps to 1.Untangle un-conflate problems 2.Narrow focus to solving particular.
Web Development Process Description
Presented by Mats Nilsson – Swedish Defense Materiel Administration (FMV) at the OASIS PLCS TC 45’th meeting Proposal for increased efficiency.
OData Technical Committee Kick-off July 26, 2012.
OASIS DEX workshop “Reference data” 3 February Oslo Trine Hansen - DNV.
Cybersecurity: Engineering a Secure Information Technology Organization, 1st Edition Chapter 7 Software Supporting Processes and Software Reuse.
SIUE Injury Tracking System Project Plan. Team Members: Robbie Marsh Robbie Marsh –Project Manager/Webmaster Ken Metcalf Ken Metcalf –Lead Programmer.
SDMX and DDI Working Together Technical Workshop 5-7 June 2013
PCA and ISO are true! Welcome! Thore Langeland, Ph. D. Chairman of PCA Americas PCA Forum and Member Meeting Hosted by Bechtel, Houston.
1 © Quality House QUALITY HOUSE The best testing partner in Bulgaria.
CF Conventions Support at BADC Alison Pamment Roy Lowry (BODC)
Second Annual Japan CDISC Group (JCG) Meeting 28 January 2004 Julie Evans Director, Technical Services.
1 Synchronize work on DEXs and reference data between PLCS pilots and OASIS/PLCS - Proposed PLCS TC Organization and Functional Responsibilities.
InWEnt | Qualified to shape the future1 Internet based Human Resource Development Management Platform Human Resource Development Programme in Natural Disaster.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
1 Sharing Advisory Board Report year 2009/2010 Taskforce MSIS 2010.
Federal XML Naming and Design Rules and Guidelines Mark Crawford.
Interim Solution What it is and how to to use it 21 June 2012.
19/10/20151 Semantic WEB Scientific Data Integration Vladimir Serebryakov Computing Centre of the Russian Academy of Science Proposal: SkTech.RC/IT/Madnick.
1 Schema Registries Steven Hughes, Lou Reich, Dan Crichton NASA 21 October 2015.
ISO edition 2 Publication plan R. Bodington Eurostep Limited ISO edition 2.
Overview of ISO NP Stella G Dextre Clarke Convenor, IDT/2/2 Working Group of BSI and Project Leader for ISO NP
- Sponsored by UK MOD ISO edition 2 Rob Bodington, Phil Spiby.
S&I Integration with NIEM (DRAFT) Standards Development Support June 8, 2011.
PLCS DEXs Trine Hansen DNV 20 April Content OASIS / PLCS Organization PLCS DEXs DEX architecture Process – define and verify capabilities Way forward.
Overview of SC 32/WG 2 Standards Projects Supporting Semantics Management Open Forum 2005 on Metadata Registries 14:45 to 15:30 13 April 2005 Larry Fitzwater.
Regional Seminar on Promotion and Utilization of Census Results and on the Revision on the United Nations Principles and Recommendations for Population.
Consultative process for finalizing the Guidance Document to facilitate the implementation of the clearing-house mechanism regional and national nodes.
Consultant Advance Research Team. Outline UNDERSTANDING M&E DATA NEEDS PEOPLE, PARTNERSHIP AND PLANNING 1.Organizational structures with HIV M&E functions.
STEP Tutorial: “ Fundamentals of STEP” David Briggs, Boeing January 16, 2001 ® PDES, Inc NASA STEP Workshop step.nasa.gov.
DEX Publication Project OASIS PLCS TC Telecon 22 January 2008 Trine Hansen.
DEX 7 – Operational Feedback Business Need Introduction This exchange enables the transmission of information on the condition and usage of a supported.
Synchronise work on DEXs and reference data between PLCS pilots and OASIS/PLCS Workshop #3 10 – 11 November 2004.
1 Item 2.1.b of the agenda IT Governance in the ESS and related issues Renewal of mandates STNE Adam WROŃSKI Eurostat, Unit B5.
DEX Publication Project OASIS PLCS TC Face to Face meeting 10 March 2008 Trine Hansen.
Product Life Cycle Support (PLCS) The Information Backbone to transform the Logistics Enterprise Some suggestions for the PLCS OASIS TC / Implementers.
Synchronize work on DEXs and reference data between PLCS pilots and OASIS/PLCS - Background, Lessons learned, Conclusions, Recommendations, Plan forward.
Briefing and Planning meeting on INSPIRE validator implementation – Discussion 16/12/2015.
Eurostat Sharing data validation services Item 5.1 of the agenda.
Slide 1 Copyright, Norwegian Defence Logistics Organization PLCS staging area Support for data exchange Jochen Haenisch
Dr. Trevor Smith Chair ISO/TC 176 Quality Management & Quality Assurance Worldwide Quality Director Global Manufacturing & Logistics Eastman Kodak Company.
Overview: Spatial Data Standards for Facilities, Infrastructure and Environment (SDSFIE) Services Support FGDC Coordination Group Meeting 6 February 2007.
Slide 1 PDT Europe 2014, October 2014, Paris 1 AeroSpace and Defence Industries Association of Europe Through Life Cycle Interoperability as developed.
International Workshop 28 Jan – 2 Feb 2011 Phoenix, AZ, USA Modeling Standards Activity Team Model-based Systems Engineering (MBSE) Initiative Roger Burkhart.
Agenda Federated Enterprise Architecture Vision
Status DEX Publication Project
Project 1 Introduction to HTML.
Validation & conformity testing
Operational Feedback DEX Status Jan 04
PLCS, a strategic enabler for Enterprise Through Life-cycle Interoperability by Yves Baudier (Airbus) May 17 & 18, 2018 (Paris) – -
SISAI STATISTICAL INFORMATION SYSTEMS ARCHITECTURE AND INTEGRATION
ESS.VIP VALIDATION An ESS.VIP project for mutual benefits
Rob Bodington, Phil Spiby
Proposed PLCS TC Organization
Presentation transcript:

1 Proposed PLCS TC Organization and Functional Responsibilities Revision

2 Agenda PLCS TC Organization and Participants Hierarchical Functional Responsibility

3 OASIS TC Chair Secretariat 1 Voting Member per Company Technical Lead Implementers Forum Lead PLCS TC Organization and Participants Technical Oversight Lead (Information Architect) 2 Tool Experts 2 Business Experts Secretariat 1 Secretariat Quality Assurance Lead Testers Pilots/Projects Norwegian Pilot UK MOD Pilot Swedish Pilot Others 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 Quality Assurance Lead Testers OASIS TC Chair Secretariat 1 Voting Member per Company Technical Lead Implementers Forum Lead PLCS TC Organization Technical Oversight Lead (Information Architect) 2 Tool Experts 2 Business Experts DEX Development Teams 1 Team Lead 1 Modeler 1 Business Expert Implementers Forum Lead Software Product Vendors Implementers Integrators Infrastructure / Tool Team Information Architect 1 Tool Expert Secretariat 1 Secretariat Pilot/Project Test Runs Pilots/Projects Norwegian Pilot UK MOD Pilot Swedish Pilot Others DEX 0 Development Team DEX 1 Development Team DEX 2 Development Team DEX X Development Team DEX Y Development Team Reporting

5 Organization Functionality – OASIS TC 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 OASIS TC Secretariat 1 Secretariat Chair Secretariat 1 Voting Member per Company Technical Lead Implementers Forum Lead

6 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 Technical Oversight Lead (Information Architect) 2 Tool Experts 2 Business Experts

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

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

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

10 Organization Functionality – Implementers Forum Testing Reuse of solutions Review and recommend changes Implementers Forum Lead Software Product Vendors Implementers Integrators Quality Assurance Lead Testers

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

12 OASIS TC Chair Secretariat 1 Voting Member per Company Technical Lead Implementers Forum Lead PLCS TC Organization Summary Technical Oversight Lead (Information Architect) 2 Tool Experts 2 Business Experts Secretariat 1 Secretariat Quality Assurance Lead Testers Pilots/Projects Norwegian Pilot UK MOD Pilot Swedish Pilot Others 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

14 Organization Functionality – OASIS TC Monitor and Maintain AP239 –Implement change programme –Monitor SC4 modules for input on AP239 –Submission of change requirements to SC4 OASIS TC Secretariat 1 Secretariat Chair Secretariat 1 Voting Member per Company Technical Lead Implementers Forum Lead

15 Organization Functionality – OASIS TC 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 OASIS TC Secretariat 1 Secretariat Chair Secretariat 1 Voting Member per Company Technical Lead Implementers Forum Lead

16 Organization Functionality – OASIS TC 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 OASIS TC Secretariat 1 Secretariat Chair Secretariat 1 Voting Member per Company Technical Lead Implementers Forum Lead

17 Organization Functionality – OASIS TC 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 OASIS TC Secretariat 1 Secretariat Chair Secretariat 1 Voting Member per Company Technical Lead Implementers Forum Lead

18 Organization Functionality – OASIS TC 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 OASIS TC Secretariat 1 Secretariat Chair Secretariat 1 Voting Member per Company Technical Lead Implementers Forum Lead

19 Organization Functionality – OASIS TC 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 OASIS TC Secretariat 1 Secretariat Chair Secretariat 1 Voting Member per Company Technical Lead Implementers Forum Lead

20 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 Technical Oversight Lead (Information Architect) 2 Tool Experts 2 Business Experts

21 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 Technical Oversight Lead (Information Architect) 2 Tool Experts 2 Business Experts

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

23 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 Technical Oversight Lead (Information Architect) 2 Tool Experts 2 Business Experts

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

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

26 Organization Functionality – Technical 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 Technical Oversight Lead (Information Architect) 2 Tool Experts 2 Business Experts DEX Development Teams 1 Team Lead 1 Modeler 1 Business Expert

27 Organization Functionality – Technical 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 Technical Oversight Lead (Information Architect) 2 Tool Experts 2 Business Experts DEX Development Teams 1 Team Lead 1 Modeler 1 Business Expert

28 Organization Functionality – Technical 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 Technical Oversight Lead (Information Architect) 2 Tool Experts 2 Business Experts Infrastructure/Tool Team Information Architect 1 Tool Expert

29 Organization Functionality – Technical 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 Technical Oversight Lead (Information Architect) 2 Tool Experts 2 Business Experts Infrastructure/Tool Team Information Architect 1 Tool Expert

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

31 Organization Functionality – Technical 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 Technical Oversight Lead (Information Architect) 2 Tool Experts 2 Business Experts Infrastructure/Tool Team Information Architect 1 Tool Expert

32 Organization Functionality – Technical 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 Technical Oversight Lead (Information Architect) 2 Tool Experts 2 Business Experts Infrastructure/Tool Team Information Architect 1 Tool Expert

33 Organization Functionality – Quality Assurance 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 Quality Assurance Lead Testers

34 Organization Functionality – Implementers Forum 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” Implementers Forum Lead Software Product Vendors Implementers Integrators Quality Assurance Lead Testers

35 Organization Functionality – Implementers Forum 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 Implementers Forum Lead Software Product Vendors Implementers Integrators Quality Assurance Lead Testers

36 Organization Functionality – Pilots/Projects 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 Pilots/Projects Norwegian Pilot UK MOD Pilot Swedish Pilot Others

37 Measures of Goodness 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

38 Measures of Goodness 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