American Council for Technology (ACT) - Industry Advisory Council (IAC) Planning and Architecture Shared

Interest GroupPresentation

IT Architecture FrameworksKey Component to

Interoperability Accomplishment

12 November 2014

Walt OkonProfessor, Information Technology

Science, Technology, and Business DivisionNorthern Virginia Community College-NOVA

Alexandria Campus, Virginiawokon@nvcc.edu

walt.okon@verizon.netPhone: 703-644-6257

Cell: 571-488-5173

Through Constructive Collaboration DoD Architecture Framework will Deliver Interoperability for Shared

Systems and Services

Premise

The US Government has not defined or mandated a Architecture

Framework and Methodology to achieve Interoperability for Shared

Systems and Services

Problem Statement

• Chief Engineers, Chief Architects, and systems designers and developers agree an Architecture Framework is essential to achieving integration and interoperability across systems and services for the US Government.

• A single Architecture Framework will enable designers and developers to build in integration and interoperability.

• DoD Architecture Framework (DoDAF) is the widely used engineering centric framework and it is being used through the world in centers of excellence.

• Four other architecture frameworks are on the market causing confusion, frustration, and increased cost expenditures.

Today's Environment

DoD’s DoDAF Direction

Why and When: Historical Development of AF’s.

C4ISRArchitecture Framework v1.0

C4ISRArchitecture Framework v2.0

DoDAFv1.0

MODAFv1.0

1996

1997

2003

2005

DoDAFv1.5

2007

MODAFv1.1

2007

NAFv1.0

2005

Scope of UPDM 1.0Approved Sept 2008

MODAF Meta-Model (M3) expressed using UML Notation

MODAFv1.2

2008

NAFv3.1

2007

DoDAFV2.0

2009

2008

Scope of UPDM 2.0ETC June 2011

DNDAFv1.8 UAF

v1.0

2015?

DoDAFV2.02

2012

7

OVERALL ARCHITECTURE FRAMEWORK CONVERGENCE VISION

DoDAFv1.5

1995

C4ISR F/W v1.0

DoDAFv2.0

UAFv2.05

2003 2007

• JCIDS & NR-KPP• Applicability beyond

C4ISR• Use-based• Integrated

Architecture

• JCIDS & NR-KPP• Applicability beyond

C4ISR• Use-based• Integrated

Architecture

2009 2010 2012 2014

DoDAFv2.01v2.02

DoDAFv2.03

DoDAF/DNDAFv2.04

1997 20162013

• Joint Interoperability

• Joint Interoperability

DoDAF v1.0

C4ISR F/W v2.0

• Net-centricity and SoA

• SvcV views

• Net-centricity and SoA

• SvcV views

• 26 AV/OV/SV/TV views• Linked to I&S policies• CADM 2.0

• 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

• 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

• Urgent CRs• 52 1 XSD• IDEAS

Foundation v1.0 fixes

• Urgent CRs

• TECHEDITS

• DM2 OWL

• Urgent CRs

• TECHEDITS

• DM2 OWL

• Federal Common Approach

• DNDAF Security Views

• Federal Common Approach

• DNDAF Security Views

• MODEM – DM2 Harmonization (IDEAS Domain Level)

• NATO NAF• UDAF

• MODEM – DM2 Harmonization (IDEAS Domain Level)

• NATO NAF• UDAF

• Standardization, e.g.,

• ISO• OMG• OASIS

• Standardization, e.g.,

• ISO• OMG• OASIS

UAF

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

Unified Direction of USG and NATOAchieving Strategic Goals and Capability

US Government OMB Direction

Strategy

Business

Information & Data

Applications & Services

Technology Infrastructure

PRM

BRM

DRM

SRM

TRM

Integrating theFederal EAFramework

and ReferenceModels

FEAF-II

Dr Scott BernardFederal Chief Enterprise ArchitectOMB Lead for IT Shared Services

Executive Office of the President

Office of Management and Budget

U.S. Federal Enterprise Architecture

Commodity IT Services• Hosting (Networks, Systems, Apps)• Help Desks / Fusion Centers• E-Mail • Collaboration Solutions• Mobile Solutions• Websites & Content Management• Data Warehouses• Inventory Management• Account Management• Contracting and Acquisition• Print Management

Common Approach to

Federal Enterprise Architecture

Using EA to Design Future-Ready Agencies

FEA II and DoDAF 2.02 Merge

Strategic Goals

Enabling Applications

BusinessServices

Host Infrastructure

Data and Information

Se

cu

rity

Co

ntr

ols

(SR

M) (PRM)

(BRM)

(DRM)

(IRM)

(ARM)

Office Of Management and Budget

Draft Laws–Executive Orders Controls Budget/Funding Office of the Federal CIO Federal Chief Architect Architecture required-

money/budget

Changes in Approach

Strategy

Business

Information & Data

Applications & Services

Technology Infrastructure

PRM

BRM

DRM

SRM

TRM

Integrating theFederal EAFramework

and ReferenceModels

Strategic Goals

Enabling Applications

BusinessServices

Host Infrastructure

Data and Information

Secu

rity

Co

ntr

ols

(SRM

) (PRM)

(BRM)

(DRM)

(TRM)Curr

ent V

iew

s Future Views

Enterprise Plan

Transition Plan

Governance

Standards

Framew

ork

UseMissionSuccess

AuthoritativeReference

Reso

urce

Opti

miz

ation Functional

Integration

Common Approach to Federal EAFEAF-II

Briefed by Dr. Bernard

OMB Desired Delivery

IT Reform Agenda

Shared Services StrategyCloud Computing

Strategy

Common Approach to Federal EA

IaaS PaaS SaaSLight Apps

Security

Cloud Computing Reference Architecture (NIST)

Shared Services / Cloud Solutions

FEAF-II / FEAv2 DODAFv2.0 Other EA

Polic

yA

ppro

ach

Deliv

ery

Data Center Consolidation

Shared Service/Cloud Computing Implementation Architecture

Briefed by Dr. Bernard

DesignArtifact Set8 Perspectives /

52 Elective)

Analysis(A-11 Exhibit 53 & 300)

Reference Models

(CRM - PRM, BRM, DRM, ARM, IRM, SRM)

DesignArtifact Set6 Domains with 6 Required, and 42 Elective artifacts

Analysis(A-11/Exhibit 53 & 300)

Reference Models

(CRM - PRM, BRM, DRM, ARM, IRM, SRM)

Annual Enterprise Roadmap(High Level Agency-Wide Current EA Project & Program Summary / 3-Yr Future Summary /

Transition Plan)

Annual EA Program Assessment(EA Program Maturity / EA Project Value)

Common Approach to Federal Enterprise Architecture (FEA)

Approach 1 - FEAF v2.0 Approach 2 - DODAF v2.02

Agency EA Repository / Inventory DOD EA Repository / Inventory

Solution Architecture ProjectsCollaborative Planning Method - CPM (5

Phases)

Solutions Architecture Projects DODAF Method (6 Phases)

Annual Agency IRM Strategic Plan (per A-130)

EA

R

eportin

g

Federal-Wide Reference Architectures / Standards

U.S. Federal Enterprise Architecture

EA

Activ

ities O

ther

Govern

ance

A

reas

Briefed by Dr. Bernard

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 (ISO/OMG) DoDAF DM2 and MODEM will be Harmonized

Unified Architecture Framework

DoDAF Sunsets and Unified Architecture Framework Emerges

15

Common Approach To Federal Enterprise Architecture

FUTURE FIRST

“Future First” aligns with the Common Approach to Federal Enterprise Architecture and brings together the areas of design, analysis, projects, standards, reporting and governance.

This provides “Full SpectrumE-Governance”.

1

May 2, 2012

Current Engagements:OMG

PM-ISEFederal Chief Architect

Constructive Collaboration

Current Engagements:OMG

Constructive Collaboration

DoD CIO Representative –Len LevineOMG Representative –Richard Soley, Victor Harrison Sr. Vice PresidentModelDriven –Cory CasanaveOMG UPDM Design Team – Matthew Hause

Solutions5

Standards Organizations3

2a

Services and Support

4

Com-munity of

Interest 1

Com-munity of

Interest 2

Com-munity of

Interest 3

Com-munity of Interest 4

Com-munity of Interest “n”

Com-munity of Interest “n” +

“m”

Com-munity of Interest 5

Information Sharing Communit

y

Com-munity of Interest 6

Stakeholders1a• U.S. Government Agencies• State, and Tribal Agencies• International Agencies• Academic Institutions• Commercial

• OMG• OASIS• W3C• Others

Requirements

Pluggable--• Taxonomies,

Vocabulary mappings,

• and context ontologies

• Protocols• Security Policies• Data Connectors &

Mappings Late binding, injection, loose coupled, Choreography

Leadership• Steering Committee• Coordination and Prioritization• Testbeds and outcomes• Funding and Membership

• Reference Implementations• Specifications of usage• Testbeds• Training

Standards

Suppliers1b• Commercial• Governmental• Individual

Deliver Productized

Approve on behalf of the ISC the publication of

Basis for defining

Collaborative Deliver

y of

Needs and opportunities

Coordination of Direction

Opportunities and Capabilities

Funding and membership

• Funding• Productization and Delivery

Needs

Participation

Capabilities

2b

Productization

PrinciplesSpecificatio

ns

CONOPS

Current Engagements:PM-ISE

Constructive Collaboration

PM-ISE – Kshemendra Paul, Program ManagerPamela Wise-Martinez Vijay MehraRalph E CorbittAshwini JarralMark E. Reichardt

August 12, 2014

Using Information Sharing Environment Interoperability Framework (I2F)

Making Interoperability Common

with Enterprise Architecture

The Office of the Program Manager for Information Sharing Environment

• Increase Information/ Intelligence Sharing

• Reduce Total Cost of Operations

• Shared Services

DesiredOutcomes

PriorityObjectives

NationalStrategy2012

GovernmentAuthorities

StakeholderInputs

Interoperability Safeguarding Search & Discovery Access & Retrieval Dissemination

Defense Law Enforcement Foreign Affairs Homeland Security Intelligence

Interoperability Requirements Operational Capabilities Exchange Patterns Technical Capabilities Technical Standards

Reference Models Exchange Specifications Technical Specifications

FEAF DoDAF PAG

Enables

Constraints/Environment

Federal SLT Private Int’l

Stakeholders

Communities

TOGAF GRA

Architecture Frameworks

Captured

In

GETTING ON THE SAME PAGE (DEFINITIONS)

What is Information Interoperability?

The ability to transfer and use information in a uniform and efficient manner across multiple organizations and information technology systems

Australian Information Interoperability Framework (2006)

In other words

It’s the ability of two or more systems or components to exchange information and to use the information that has been exchanged

• PM-ISE mission established in EO1356, EO1388 details the strengthening for information sharing.  PM-ISE initiatives are reinforce on standards, interoperability, and architecture etc…

• DODAF have been huge undertaking but or not directive within whole of government, the need for a unified architecture approach would go far in solving interoperability. • Federal Enterprise Architecture Common Approach, lots of goodness, links some DODAF artifacts, but not Directive/Policy • FEAF – Policy is in the Agency Requirements to Deliver Transition Roadmaps each April. Supportive, but does not achieve the goals of A119

• Under the OMG process the UPDM is a normative specification for modeling DODAF -  Supports A119 “use of consensus based standards”

• I2F provides definitions, and guidance for implementation, but is not Policy

Collaboration Agreements

• I2F supports Architecture Framework Interoperability via the Architecture Grid Alignment tools, and builds common practices for Interoperable Architecture Design

• Need practical next steps to achieve Framework Interoperability?

• Architecture Frameworks alone do not achieve interoperability

• Federal Workgroup maybe the best approach to achieve Framework Interoperability

• Standards Coordination Council has ownership of the I2F to operationalize whitespace and other activities, but are not on hook to improve architecture efforts or other nascent thoughts here

Collaboration Agreements

Develop a Constructive Collaboration Team to deliver

Unified Architecture Framework and Methodology mandated by US

Government Policy will result in Interoperability for Shared Systems

and Services

Solution Direction

WHO ARE THE PLAYERS?

• Government:• Federal CIO and Federal Chief Architect• Department CIOs and Chief Architects

• Industry:• ACT- IAC - IAC Planning and Architecture SIG • NDIA

• Academia:• National Defense University• Penn State University - FEPO• George Mason University• NOVA

• International Standards Organizations• OMG – UPDM• OASIS

Walt Okon

Air Force Officer CC, Eng, ATC, Computers

Civ –DISA StratPlans, Eng, System Eng

Civ - DoD CIO DoDAF, DARS, Standards

Retired Adjunct Professor

Vision and Objective • Deliver Interoperability for Shared Systems and Services • Constructive Facilitation resulting in Collaboration

• Guide and enable Government, Industry, and Academia