1. “Unified” (Common) Architecture Framework (UAF) Joint Project
Draft
Preliminary Discussion
with ISO TC 184-SC4 PPC

2. BACKGROUND
Major Transformation Efforts on-going in Government, Industry and Business
Reducing Cost is a Major Driver
Increased Strong Emphasis on Information Sharing and Interoperability
UNCLASSIFIED

3. Need for New Standard Reduce Implementation Cost
Facilitate Interoperability
Achieve Collaboration With Key Standards Developers
UNCLASSIFIED

4. Joint Project to Build a New Standard
Collaborative Project to Jointly Produce, Publish, and Co-Brand a New Specification
Involve Key Standards Developers Related to Information Sharing and Interoperability
ISO TC 184-SC4
OASIS
OMG
Others [ INCOSE? / JTC1-SC7? / IEEE ? ]
Use DoDAF/ MODAF/ DINDAF/ NAF, et al, as starting point
Harmonized Version of DoDAF
Existing Artifacts, Definitions, Base Models
UNCLASSIFIED

5. New Transformation Occurring
Federal, DoD, and IC Communities
Major Transformation of Policies, Organizations and Activities
“Efficiencies Study”
JIE
IC ITE
Fusion of DoD and IC community architecture and standards activities
Unified Common Approach
Joint Governance
Single Registry
UNCLASSIFIED

6. Existing DoD CIO Governance
Color coding indicates related functions
CIO Executive Board
NLCC EB
CIO EB Secretariat
NLCC SSG
Spectrum Council
ASRG
JIE EXCOM
IASL
MILDEP CIO Council
GIG Waiver Panel
Identity Mgt Council
Interoperability Steering Group
IASRG
SATCOM
C2CIB
C2 DSSC
ESRG
Aligned /chartered under CIO Executive Board
UNCLASSIFIED 6

7. Executive Steering Group
IT Standards
Okon
Okon
Executive Steering Group
IT Standards Oversight Panel
Okon
Okon
UNCLASSIFIED
UNCLASSIFIED 7

8. Unified Architecture Framework (UAF)
Information Environment (IE)
Joint Information Environment (JIE)
Strategic Direction
Mission Statement
Objectives
Unified Architecture Framework
UNCLASSIFIED

9. Conceptual Depiction of DoD IE Information Environment
The DoD IE uses this conceptual depiction to describe the IE in providing guidance and direction
Enables an IE that is capable of delivering capabilities to end users through IE services.
UNCLASSIFIED

10. UNCLASSIFIED

11. Vendor Tools are Necessary
Architecture Tools
Guidance
DoDAF v2.0
Federated Architecture Strategy
DoD IEA
DoD Tools
DoD Architecture Registry System (DARS)
DoD IT Standards Registry (DISR)
Enhanced Information Support Plan (E-ISP Tool)
Joint C4I Program Assessment Tool - Empowered
GIG Technical Guidance (GTG) Tool
Meta Data Repository (MDR)
Vendor Tools are Necessary
UNCLASSIFIED

12. Elements of Quality Architecture
UNCLASSIFIED

13. Elements of Quality Architecture
Single Architecture Framework
Policy, Direction, Guidance
Exchange
Architecture Tools
Certified Architects
Enabling efficient and effective acquisition of hardware, software and services used by DoD and Partners in mission performance.
Unified Architecture Framework
UNCLASSIFIED 13

14. DoDAF V2.0 Viewpoints Fit-For Purpose
Renamed
New
New
New
Overarching aspects of architecture context that relate to all models
All Viewpoint
Articulate the data relationships and alignment structures in the architecture content
Data and Information Viewpoint
Articulate applicable Operational, Business, Technical, and Industry policy, standards, guidance, constraints, and forecasts
Standards Viewpoint
Systems Viewpoint
Articulate the legacy systems or independent systems, their composition, interconnectivity, and context providing for, or supporting, DoD functions
Services Viewpoint
Articulate the performers, activities, services, and their exchanges providing for, or supporting, DoD functions
Operational Viewpoint
Articulate operational scenarios, processes, activities & requirements
Capability Viewpoint
Articulate the capability requirement, delivery timing, and deployed capability
Describes the relationships between operational and capability requirements and the various projects being implemented; Details dependencies between capability management and the Defense Acquisition System process.
Project Viewpoint
New
In DODAF 2.0 we have described an expanded number of viewpoints (categories of models and views expressing differing aspects of a common architecture need) to include those shown on the slide. Some of the viewpoints were introduced in earlier versions of DoDAF, others, such as Project and Capability are new to DoDAF 2.0.
An architecture viewpoint can be displayed in a number of formats, such as dashboards, fusion, textual, composite, or graphs, which represents data and the architecture description which represents an architecture. In DoDAF 2.0, the ability is provided to create an architectural description which can be expressed in many of the same formats normally used for briefing, analysis, and decision-making.
The next few slides present a view of data from an architecture developed for the US Air Force at Arnold Engineering Development Center in Tennessee. This is the Air Force Center for R&D, testing and Analysis of aircraft, engines, and other components. Both Charles and I are using these views today with the permission of the Air Force.
Architecture viewpoints are composed of data that has been organized to facilitate understanding.
UNCLASSIFIED 14 14

15. DoDAF Meta Model (DM2) Purposes
Precise unambiguous definition of DoDAF terms and their inter-relationships
Architecture views (e.g., OV-2) are specified in DM2 terms in addition to their usual narrative text descriptions
Views are rendered from DM2 data
Views can be exchanged as DM2 XML
Defines precision semantics for architecture integration and analysis
Integrated and cross-walked
Analyzed, evaluated, and assessed quantitatively
The overall goals of the DM2 are to, 1) provide a basis for semantic precision in architectural descriptions to support heterogeneous architectural description integration and analysis in support of core process decision making, and 2) provide semantics foris information sharing across the DoD Enterprise Architecture (EA) Community of Interest (COI).
UNCLASSIFIED

16. Why and When: Historical Development of AF’s
C4ISR
Architecture Framework v1.0
Architecture Framework v2.0
DoDAF
v1.0
MODAF
1996
1997
2003
2005
v1.5
2007
v1.1
NAF
Scope of UPDM 1.0
Approved Sept 2008
Meta-Model (M3)
expressed using
UML Notation
v1.2
2008
v3.1
V2.0
2009
Scope of UPDM 2.0
ETC June 2011
DNDAF
v1.8
UAF
v1.0
2015?
DoDAF
V2.02
2012
UNCLASSIFIED

17. Overall architecture framework convergence vision
Unified Direction of USG and NATO Achieving Strategic Goals and Capability
Overall architecture framework convergence vision
DoDAF
v1.5
1995
C4ISR F/W v1.0
v2.0
UAF
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
UDAF
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
UNCLASSIFIED 17 17

18. Unified Architecture Framework
DoD CIO Vision Statement:
Support achieving the DoD CIO Vision to deliver agile and secure information capabilities to enhance combat power and decision making
Move to Single World-Wide Architecture Framework
Coordinate and work with:
UK – MODAF
Canada DNDAF
NATO – NAF
Create an International Standard
UNCLASSIFIED 18

19. Unified Architecture Framework
Unified Architecture Framework Strategic Direction
Move to Single Architecture Framework = 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
Object Management Group (OMG) March 2012
Ideas Meeting in June 2012
NATO CAT workshop 10/11 Sept 2012
NATO Extraordinary Capability Architecture Team, Jan 13
Launchpad for Unified Architecture Framework (UAF)
UNCLASSIFIED

20. 4.1 ARCHITECTURE FRAMEWORKS
Reference Document 3195
development of the AMN architecture in 2010 – Lessons Learned
Torsten Graeber, NATO C3 Agency
Afghan Mission Network (AMN)
June 2011
The Hague
UNCLASSIFIED

21. “4.1 ARCHITECTURE FRAMEWORKS
“Lessons Learned Report” Extract
“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.”
… Results can be fatal!
UNCLASSIFIED

22. Unified Architecture Framework will:
DoDAF will be foundational and enhanced
DoDAF will contain DNDAF Security Views/Models
DoDAF and MODAF will be Harmonized
UAF will be capability focused
DoDAF/UAF will become an international Standard (OASIS/ISO/OMG/etc.)
DoDAF DM2 and MODEM will be Harmonized
DoDAF Sunsets and Unified Architecture Framework Emerges
UNCLASSIFIED

23. Office Of Management and Budget (OMB) AGENCY ENTERPRISE ROADMAPS Walt Okon Senior Architect Engineer Architecture & Infrastructure (A&I) Directorate (703)
UNCLASSIFIED 23

24. Convergence in the US -- Common Approach
Office Of Management and Budget
Convergence in the US -- Common Approach
Documentation section identifies 50 artifacts (what DoDAF calls models)
DoD led the Artifact Working Group that is updating these artifacts
UNCLASSIFIED

25. Common Approach to Federal Enterprise Architecture
OMB Published Federal CIO Memo
Shared Services, 2 May 2012
OMB Published Common Approach
Common Approach to Federal Enterprise Architecture, 2 May 2012
Rewrite-Federal Segment Architecture Methodology (FSAM) to Collaborative Planning Methodology
DoDAF v2.02 Artifacts to Common Approach
OMB Tasking-DoD Enterprise Roadmap,
Provides Standardized method to develop architectures
UNCLASSIFIED

26. FEDERAL COMMON APPROACH with DoDAF 2 Implementation
DoDAF included in Federal Enterprise Architecture Framework (FEAF) 2.0 DRAFT artifact details
DoDAF v2.02 Change 1, Streamlined & Clarified
In DoD:
In JCIDS, acquisition, and systems engineering policies for over a year for all acquisitions
Three milestones including interoperability plan
Systems engineering reviews
Reference architectures using for IEA, JIE, JMTs, WMA, BMA, and I/C JARM – all DoD mission areas
23 Jan 2013
UNCLASSIFIED

27. FY 2015 Information Sharing Environment (ISE) Implementation Guidance
OFFICE OF THE DIRECTOR OF NATIONAL INTELLIGENCE, PROGRAM MANAGER, INFORMATION SHARING ENVIRONMENT, August 14, 2013
MEMORANDUM FOR: SUBJECT: FY 2015 Information Sharing Environment (ISE) Implementation Guidance
This memorandum provides guidance for the Information Sharing Environment and other affected departments and agencies in accordance with the White House memorandum, FY 2014 Programmatic Guidance on Information Sharing and Safeguarding Goals, dated July 23, 2012 and the President’s National Strategy for Information Sharing and Safeguarding, issued December of Together, they reinforce the following goals:
1. Drive collective action through collaboration and accountability
2. Improve information discovery and access through common standards;
3. Optimize mission effectiveness through shared services and interoperability;
4. Strengthen information safeguarding through structural reform, policy, and technical solutions; and
5. Protect privacy, civil rights, and civil liberties through consistency and compliance
Built in consultation with stewards of the Strategy: the Information Sharing and Access Interagency Policy Committee (ISA-IPC), the Senior Information Sharing and Safeguarding Steering Committee (SISSSC) and the Federal Chief Information Officer Council. The guidance is intended to inform agency plans to implement the Strategy and align priorities.
UNCLASSIFIED