1. Unified Architecture Framework NATO Architecture CaT Introduction
Mr. Walt Okon
Senior Architect Engineer
DoD Chief Information Officer Office
Architecture and Interoperability Directorate
10-11 September 2012

2. Unified Architecture Framework Agenda - 10 September 2012
0900-Welcome; US Host
Introductions of Participants
Unified Architecture Framework Strategic Direction (Walt Okon)
Mission Statement and Workshop Objectives
Review London Meeting
UAF IDEAS Meeting
High-level Agreement
Harmonization of Frameworks
4 Action Items (Letter of Strategic Intent, Master Brief, Roadmap, Agenda)
1000-IDEAS Group Members present their Architecture Framework and direction (USA, UK, Canada, Sweden, Australia)
USA on DoDAF-MD2
BREAK
UK-MODAF
–Canada-DNDAF
– Lunch (On-site cafeteria)
– Sweden
Australia
Break
NATO – NAF
–Other Nations as desired

3. Unified Architecture Framework Agenda – 11 September 2012
0900- Review First-Day Progress
0930- Education:
BORO/IDEAS Method – Chris Partridge
IDEAS Foundation – Ian Bailey
BREAK
Common Patterns (Whole Parts, Overlaps, Resource Flows) – Dave McDaniel
Lunch (On-site cafeteria)
Unified Architecture Framework (UAF) Master Brief – Walt Okon
* Roadmap to incremental convergence under the UAF
* Core set of NATO-critical items for initial increments
Break
UAF Roadmap Presentation – Steve Challinor
Prepare out brief topics for CaT Presentation

4. Unified Architecture Framework Introductions
Introductions of Participants

5. Unified Architecture Framework
Unified Architecture Framework Strategic Direction
Mission Statement and Workshop Objectives
Mr. Walt Okon
Senior Architect Engineer
DoD Chief Information Officer Office

6. Unified Architecture Framework
Unified Architecture Framework Strategic Direction
Move towards a Single Architecture Framework to achieve Interoperability
Development of the AMN architecture in 2010
Development of Unified Profile for DoDAF and MODAF (UPDM) Versions 1.0, 2.0, and 3.0
Meeting at Object Management Group (OMG) March 2012
Ideas Meeting in June 2012
Plan for NATO CAT workshop 10/11 Sept 2012
Launchpad for Unified Architecture Framework (UAF)

7. 4.1 ARCHITECTURE FRAMEWORKS
Reference Document 3195
development of the AMN architecture in 2010 – Lessons Learned
Torsten Graeber, NATO C3 Agency
June 2011
The Hague

8. 4.1 ARCHITECTURE FRAMEWORKS
4.1.2 Observations [Need for a Unified Architecture Framework]
Differences in DoDAF, MODAF, and NAF make it difficult to match the meta-model one to one.
some of the concepts in the frameworks have the same name but different definitions, i.e. different semantics.
Difficult to cross-walk the concepts between the different frameworks leads to miscommunication between architects using different frameworks.

9. Elements of Quality Architecture
Policy, Direction, Guidance
Single Architecture Framework
Architecture Exchange
Architecture Tools
Trained/Certified Architects
Enabling efficient and effective acquisition of hardware, software and services used by DoD in missions deliverables.
Unified Architecture Framework 9

10. Unified Architecture Framework
Mission Statement
and
Workshop Objectives

11. Unified Architecture Framework
Mission Statement:
To achieve a Unified Architecture Framework to support design, development, and delivery of IT architecture that can be exchanged and shared for assured interoperability.
Workshop Objectives:
To understand the criticality need for a unified framework.
To understand the information sharing movement
To achieve unity and commitment to a strategic direction
To know the direction forward to achieve a unified architecture framework

12. Unified Architecture Framework
National IT Architecture Movement in the United States across all Government Departments, Agencies, and Organizations
Federal, State, and Local
Industry
Academia (Colleges and Universities)

13. Common Approach Increasing Shared Approaches
To Information Technology Services
Implements Governance Process
Provides Authority to the Common Approach to a Unified Architecture Framework
Provides Standards Methods and Tools
Design and Implement Shared Services
Design architectures that facilitates interoperability and information-sharing

14. Collaborative Planning Methodology
CPM consists of two phases: (1) Organize and Plan and (2) Implement and Measure:
Facilitate collaboration between mission partners; Step 1
Planners specifically support investment, procurement, implementation, and performance measurement actions and decisions Step 2.
Work with mission partners to clearly define system interoperability needs and how those benefits will be measured (Step 3).
Helps planners support mission partners as they make decisions actions for their mission (Step 4).
Provides planners with guidance in measuring the actual performance changes that have (Step 5).

15. Collaborative Planning Methodology
1a. Identify and Assess Leadership and Stakeholder Needs
2a. Identify Organizations with Similar Needs
3a. Formalize Planning Team and Launch Planning
4a. Define Funding Strategy and Make Decision
5a. Operate with the New Capabilities
1b. Analyze Needs in Context of Drivers
2b. Analyze Opportunities to Leverage
3b. Define Requirements
4b. Conduct Procurement Activities
5b. Measure Performance Against Metrics
1c. Validate and Prioritize Needs
2c. Determine Whether to Leverage
3c. Define the Architecture
4c. Execute the Modernization Roadmap
5c. Analyze and Provide Feedback
1d. Identify and Initiate Governance
3d. Integrate with Other Plans
3e. Update Enterprise Modernization Roadmap

16. Architecture Framework Convergence Vision
DoDAF
v1.5
1995
C4ISR F/W v1.0
v2.0
UDAF
v2.05
2003
2007
JCIDS & NR-KPP
Applicability beyond C4ISR
Use-based
Integrated Architecture
2009
2010
2012
2014
v2.01
v2.02
v2.03
DoDAF/DNDAF
v2.04
1997
2016
2013
Joint Interoperability
DoDAF v1.0
C4ISR F/W v2.0
Net-centricity and SoA
SvcV views
26 AV/OV/SV/TV views
Linked to I&S policies
CADM 2.0
Fit-for-purpose
Data-centric architecture
Improved models of systems, services, capabilities, rules, measures
DoDAF Meta Model (DM2) based on IDEAS
Urgent CRs
52  1 XSD
IDEAS Foundation v1.0 fixes
TECHEDITS
DM2 OWL
Federal Common Approach
DNDAF Security Views
MODEM – DM2 Harmonization (IDEAS Domain Level)
NATO NAF
Standardization, e.g.,
ISO
OMG
OASIS
Framework Objective:
Achieve a single integrated Architecture Framework for interoperability.
Achieve a US, Canada, and United Kingdom single Framework with a common Data Meta Model
Achieve alignment with the US Government Common Approach to Enterprise Architecture
19 June 2012 16 16

17. Unified Architecture Framework
Unified Architecture Framework Strategic Direction
Mission Statement and Workshop Objectives
Mr. Walt Okon
Senior Architect Engineer
DoD Chief Information Officer Office