1 / 16

DEX Project Proposal 23 May 2006 TOG

DEX Project Proposal 23 May 2006 TOG. Motivation. Uncoordinated / piece-meal approach lead to rework, inefficiencies, instability and no final delivery Coordinated project to complete what we started Can be built on / used by others. Project Objectives.

barr
Download Presentation

DEX Project Proposal 23 May 2006 TOG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DEX Project Proposal 23 May 2006 TOG

  2. Motivation • Uncoordinated / piece-meal approach lead to rework, inefficiencies, instability and no final delivery • Coordinated project to complete what we started • Can be built on / used by others PLCS Inc. (c) 2002

  3. Project Objectives • Develop a core set of capabilities + ref data for use in business deployments • Develop and publish two sets of DEXs (generic + business) and related capabilities • Test and deploy PLCS Inc. (c) 2002

  4. Project Approach • It would be nice to have: • A coherent international project • One central Contract • Dedicated resources • Full time Project Manager • Direct costs covered centrally • Pragmatic approach: • A coherent work plan • National contracts • Direct costs for standardization to be factored in to the work on contract • TOG suggestion: • A set of national awarded contracts addressing the coherent work plan managed by a dedicated person • Direct costs factored into the contracts PLCS Inc. (c) 2002

  5. Short term: Project Phases & Milestones • Phase 0 – Establish the project • Establish the project • Phase I - Develop a core set of capabilities and two sets (generic and business) of DEXs • M1 - Necessary DEXLib infrastructure established • M2 - Core capabilities + ref data ready for review • M3 - DEX(s) to be developed for publication decided • M4 - Capabilities used in chosen DEX(s) ready for review • M5 - Prioritized DEX(s) ready for review • M6 - DEX(s) reviewed • M7 - Software vendors / implementations identified for implementer forum participation • Phase II – Test and deploy • M1 - Test data for DEX(s) from Phase I established • M2 - Implementers Forum established • M3 - Testing environment established • M4 – Applications implemented DEX(s) from Phase I • M5 - First test rally established • M6 - DEX(s), capabilities and reference data from Phase I balloted & standardized PLCS Inc. (c) 2002

  6. Medium term: Project Phases & Milestones • Phase III – Service Oriented Architecture • M1 - Web services for templates defined • M2 - Business level services defined • Phase IV – More DEXs • Additional DEXs identified • DEXs published • Phase V – ISO 10303 239 - Maintenance PLCS Inc. (c) 2002

  7. Project Phases and Schedule Phase 0 - Establish the project Phase I - Develop a core set of capabilities and two sets (generic and business) of DEXs Phase II - Test and deploy Phase III – Service Oriented Architecture Phase IV - More DEXS Phase V – ISO 10303-239 maintenance PLCS Inc. (c) 2002

  8. Main activities – Phase 0 • Establish the project • Agree scope, budget and schedule • Identify a project leader • Identify resources • Phase 1 will start when deliverables from Phase 0 are completed. PLCS Inc. (c) 2002

  9. Costs – Phase IDevelopment PLCS Inc. (c) 2002

  10. Costs – Phase IITest and deployment PLCS Inc. (c) 2002

  11. Main activities – Phase IIIService Oriented Architecture • Specify template based web services • Based on templates • Test template based web services • Develop test specification • Develop a client to use to test / validate services • Specify business level web services • Based on business process models • Test business level web services • Develop test specification • Develop a client to use to test / validate services PLCS Inc. (c) 2002

  12. Main activities – Phase IVAdditional DEXs • Define DEXs to be developed • Develop outstanding capabilities + ref data • Develop DEXs + ref data • Review DEXs + capabilities • Test DEXs + capabilities • Ballot PLCS Inc. (c) 2002

  13. Main Activities – Phase VISO 10303-239 - maintenance • Address PLCS SEDS • Review modified modules • Adopt new modules (risk, descriptors) • Develop new AP • Submit for ISO Ballot • Publish PLCS Inc. (c) 2002

  14. Steering Committee • The Steering Committee should comprise of those paying • CDIP: • Tor Arne Irgens (NDLO) • Martin Gibson (UK MoD) • Mats Elgh (FMV) • US DoD ? • Howard Mason (Chair of PLCS TC) PLCS Inc. (c) 2002

  15. The Team (proposal) • Project manager? • Trine Hansen (DNV) • Leif Gyllström (Combitech) • Rob Bodington (Eurostep) • Sean Barker (BAE System) • Tim Turner (LSC) • Per-Åke Ling (Eurostep) • Johan Nilsson (Eurostep) • Mike Ward (Eurostep) • Peter Bergström (Eurostep) • Väino Tarandi (Eurostep) • Tore Christiansen (DNV) • Fredrik Axelson (Combitech) • Mats Nilsson (FMV) PLCS Inc. (c) 2002

  16. Reference data ‘Taxonomies’ Capability Generic DEX(PLCS upper level business ontology) AP239 Business DEX PLCS foundation ref data PLCS ARM PLCS business Business DEX Phase I Business DEX Business DEX Each ’oval’ represents an OWL reference data file PLCS Inc. (c) 2002

More Related