1. UPDM – Unified Profile for DoDAF/MODAF
Graham Bleakley, Matthew Hause, Jim Rice
UPDM Co-Chairs
UPDM Group
88Solutions Adaptive Atego ASMG Axway Software BAE Systems DoD DND
Mega Mitre MOD NIST Northrop Grumman No Magic Inc Raytheon Rolls Royce Sparx Systems Selex SI Thales Unisys VisumPoint LLC
Everware-CBDI Generic General Dynamics IBM L3Comms Lockheed Martin Co

2. Agenda DoD support for UPDM effort Current status Future Plans
World-wide use of UPDM
Future Plans
UPDM 2.1
PES Support
Wider use of DoDAF 2.0 and UPDM
DoD Feedback
AOB?

3. DoD Support for UPDM Effort
Thank you for your on-going support
Involvement of DoD personnel and contractors:
Ensures that UPDM implements a conformant DoDAF 2.0
Provides a faster means of direct feedback to the DoDAF 2.0 effort
Promotes better understanding for both groups
Lends credibility to the UPDM effort
Ensures that interchange stays front and center on the OMG agenda
Motivates our organizations to fund our involvement in UPDM
Future Support
Hopefully will continue at current levels

4. UPDM Team Members
US DoD Liaison - DoD/DISA, OSD CIO, Mitre, Silver Bullet
UK MOD Liaison - UK MOD, ModelFutures
Canada DND Liaison – DND and ASMG Ltd
NATO – Generic AB on behalf of SwAF and on contract by FMV
Tool Vendors – Adaptive, Atego (Co-Chair), IBM (Co-Chair), Mega, NoMagic (Co-Chair), Sparx Systems, Visumpoint
Aerospace – BAE Systems, General Dynamics, L3 Communications, Lockheed Martin, Northrop Grumman, Raytheon, Rolls-Royce, Selex SI, Thales, Unisys
Advisors – Decisive Analytics
New members: 88solutions, Axway Software, Everware-CBDI, NIST
Distributed multi national team (US, UK, France, Sweden, Lithuania, Australia, Canada, Thailand, Italy)

5. UPDM 1.1 Status UPDM 1.1 is complete
UPDM 1.1 supports DoDAF 1.5 & MODAF 1.2
UPDM 1.1 is a DoD mandated standard
UPDM 1.1 has been voted on and approved by the OMG Board of Directors
Tools supporting UPDM 1.1 are available now from Atego, IBM, No Magic and Sparx.
Submission to ISO harvesting or fast-track is currently under way
Should complete within 3-6 months

6. DoDAF 2.0 Signed and Released in June 2009
UPDM 2.0 Roadmap - Status
DoDAF 2.0 Signed and Released in June 2009
UPDM 2.0 RFP Issued Sept 2009
UPDM 2.0 Submission Sept 2010
UPDM 2.0 FTF completion/submission in June 2011
UPDM 2.0 tools supporting DoDAF 2.0 will be available after this date
Beta versions available now

7. UPDM 2.0 Roadmap – Remaining Work
UPDM 2.0 Domain meta-model
Specification Template
Tested this week and complete
Completed by the end of the week
Documents were generated and differences noted
UPDM 2.0 profile
Issue List and Ballots
26 issues in total
Ballot 1 will be generated by mid-April
UPDM 2.0 Specification front material
Ballot 2 will be generated by end of April
Completed by end of March
Mapping Tables
UPDM 2.0 XMI files
Completed by mid-April
Completed by the end of March
Submission Date
UPDM 2.0 Sample problem
May 22nd, 2011
Completed by the end of April

8. World-wide Adoption of UPDM
Organizations within the following countries are investigating or have adopted UPDM.
United States
Norway
Australia
Great Britain
NATO
India
France
Italy
Germany
Sweden
Holland
Lithuania
Canada
Israel
Etc.
Use of UPDM for non-military applications
Disaster planning, event planning, space missions: satellites, manned missions, non-military government departments, humanitarian relief operations, industry infrastructure planning, banking, European research project, etc.
All of the above cited standardization and interchange as essential reasons for considering UPDM

9. UPDM 2.1 Roadmap Submit UPDM 2.1 RFP September 2011
UPDM 2.1 Submission March 2012
UPDM 2.1 FTF completion/submission in September 2012
Expected target DoDAF 2.04/2.03
MODAF 1.3 unlikely to be completed by then
DNDAF 1.7 may also be required by the Canadians
BPMN profile should be complete so could also be a candidate for inclusion
PES Support
Priorities will be based on demand and participation

10. DoDAF 2.0 and PES
DoD has a vision of federated architectures that are linked together
Exchange of DoDAF models with DoD is via the PES
PES:-Physical Exchange Specification, XML based file format
Based on DM2 data dictionary mapping, defines all the elements that appear in all the views:- Approx 15,000 cells
Federated/Integrated
Joint Architectures
Federation/Integration
Methodology
Useful
Analytical
Information
PPBE
JCIDS
Investment
Reviews
Acquisition
Decision
Support
Tools,
Repositories,
and Registries

11. Interchange and interoperability
DoD plans to use PES as a means to exchange non UML models and put them into repositories
PES Support in UPDM
Mapping in UPDM 2.0
Projected defined and supported in UPDM 2.1
This is planned to be included in the UPDM 2.1 RFP
Historically UML modelling tools used XMI which has led to integrations being developed as point to point solutions
OMG Model Interchange Working Group (MIWG) developing common XMI interchange between UML tool vendors

12. MIWG Results MIWG kickoff over 2 years ago (Dec ‘ 08)
Finishing 16 test cases for UML and SysML
General exchange capability demonstrated among vendors, but some issues remain
Vendors continue to update their tools to address interchange issues
Refinements to UML spec identified to reduce ambiguity and correct errors
Guidelines being established for vendor interoperability
Test coverage reflects most of the commonly used UML/SysML features by end of Phase 2 Testing
Copyright © by Object Management Group.

13. Wider Use of DoDAF 2.0 and UPDM
US OMB (unofficially) considering wider adoption of DoDAF 2.0 in federal Govt
Fits in well with current use of UPDM in non-military applications
UPDM well placed in OMG to collaborate with Model for Performance-driven Government (MPG) group to create CA-FEA standard
Would require a name change for UPDM

14. Discussion
Feedback?
Questions?