Post on 24-Jan-2016
description
DEX Project Proposal23 May 2006TOG
2PLCS Inc. (c) 2002
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
3PLCS Inc. (c) 2002
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
4PLCS Inc. (c) 2002
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
5PLCS Inc. (c) 2002
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
6PLCS Inc. (c) 2002
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
7PLCS Inc. (c) 2002
Project Phases and Schedule
Phase
Months
1 2 3 4 5 6 7 8 9 10 11 12
0 X
I X X X X X X X X
II X X X X X X X X
III
IV
V
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
8PLCS Inc. (c) 2002
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.
9PLCS Inc. (c) 2002
Costs – Phase IDevelopment
# Activity Costs [hours]
1 Project management 500
2 Kick-off workshop 200
3 Establish TOG support management 100
4 DEXLib infrastructure 2310
5 DEXLib Help section 300
6 Develop Core capabilities + ref data 1860
9 Decide which DEXs to be standardized (in this project) 10
10 Develop capabilities for completion of 2 sets of DEXs 460
11 Review and update capabilities for completion of 2 sets of DEXs 40
12 Develop 2 sets of DEXs + ref data 560
13 Reference data content 140
14 Review the 2 sets of DEXs 120
15 Preparation for establishing Implementers Forum 100
TOTAL 6700
10PLCS Inc. (c) 2002
Costs – Phase IITest and deployment
# Activity Costs [hours]
1 Project management 100
2 Establish Implementers Forum 200
3 Develop test data 200
4 Implementing testing tool support 400
5 Implement applications using DEXs developed in Phase I
-
6 Test DEXs developed in Phase I 160
7 Ballot & publish capabilities developed in Phase I 40
8 Ballot & publish DEXs developed in Phase I 40
9 Ballot & publish Reference data developed in Phase I 40
TOTAL 1180
11PLCS Inc. (c) 2002
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
12PLCS Inc. (c) 2002
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
13PLCS Inc. (c) 2002
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
14PLCS Inc. (c) 2002
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)
15PLCS Inc. (c) 2002
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)
16PLCS Inc. (c) 2002
Business DEX
Business DEX
Reference data ‘Taxonomies’
PLCS foundation
ref data
PLCS business
PLCS ARM
CapabilityAP239 Generic DEX(PLCS upper level business ontology)
Business DEX
Business DEX
Each ’oval’ represents an OWL reference data file
Phase I