I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Headquarters U.S. Air Force

AF Architecting CONOPS, AF Architecting CONOPS, Governance, andGovernance, and

FederationFederation

Lt Col Jerry HuffmanMr. Dennis Dempsey

SAF/A6PA28 April 2010

Report Documentation Page Form ApprovedOMB No. 0704-0188

Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering andmaintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information,including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, ArlingtonVA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if itdoes not display a currently valid OMB control number.

1. REPORT DATE 28 APR 2010 2. REPORT TYPE

3. DATES COVERED 00-00-2010 to 00-00-2010

4. TITLE AND SUBTITLE AF Architecting CONOPS, Governance, and Federation

5a. CONTRACT NUMBER

5b. GRANT NUMBER

5c. PROGRAM ELEMENT NUMBER

6. AUTHOR(S) 5d. PROJECT NUMBER

5e. TASK NUMBER

5f. WORK UNIT NUMBER

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) SAF/A6PA,1800 Air Force Pentagon,Washington,DC,20330-1800

8. PERFORMING ORGANIZATIONREPORT NUMBER

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR’S ACRONYM(S)

11. SPONSOR/MONITOR’S REPORT NUMBER(S)

12. DISTRIBUTION/AVAILABILITY STATEMENT Approved for public release; distribution unlimited

13. SUPPLEMENTARY NOTES Meeting of the Next Generation Air Transportation System (NextGen) Partner Agency Chief/EnterpriseArchitects and Distinguished Colleagues, 28 Apr 2010, Washington, DC

14. ABSTRACT

15. SUBJECT TERMS

16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF ABSTRACT Same as

Report (SAR)

18. NUMBEROF PAGES

23

19a. NAME OFRESPONSIBLE PERSON

a. REPORT unclassified

b. ABSTRACT unclassified

c. THIS PAGE unclassified

Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

AgendaAgenda

USAF Architecture CONOPS and Architecture Governance Process

Architecture Federation

2

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Warfighter IntegrationWarfighter Integration WhatWhat’’s in Plays in Play

3

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

ArchitectingArchitecting ‘‘The ConceptThe Concept’’

Problem Statement:AF leaders make complex decisions on a daily basis affecting the AF Enterprise. However, the second and third order effects of those decisions often impact seemingly disparate portions of the enterprise in fundamental ways (good or bad) that were unforeseen by the decision-maker simply because the relationship data was not available when the decision was made. Architecture can eliminate some of the ‘fog’ of decision-making by defining these relationships in a format the decision-maker can easily understand.

Vision:As leaders of architecture in the Air Force, we deliver timely, relevant, unambiguous information to support informed decision-making by Air Force leaders to maximize military capabilities while optimizing allocation of resources.

End State:The AF architecture capability is integrated into AF decision-making processes

4

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

CONOPS IntroCONOPS Intro

5

Follow this link to explore on the XC Portal Page

Air Force Architecting 

Concept of Operations

Version 1.0December 2009

_____________________

BOBBY W. SMART, SES Director, Policy and Resources Office of Warfighting Integration and Chief Information Officer

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Architecting Architecting ‘‘Critical CapabilitiesCritical Capabilities’’

Functioning Governance CapabilityReliable ProcessesFit-for-purposeFit-for-federation

Optimal Build CapabilityCommon high standardConsistent repeatable processesData is shareable and accurate

Effective Decision-Support CapabilityRequirements drivenCustomer focusedClear scope and purpose

6

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Use, Build, Use, Build, GovernGovern

DoD Context & Rules

AF Context & Rules

MAJCOM Context & Rules

MAJCOM(OTE)

AF Air Staff(Policy and

Governance)

DoD

Program(Execution)

Program Context & Rules

DoD Changes

Air Force Changes

MAJCOM Changes

Program Changes

Decision Making Processes

Architectures Transformations

Architectures assessed as “fit for purpose” and “compliant” to ensure decisions stick and adherence to standards

Fit for purpose

Fit for purpose

Fit for purpose

Fit for purpose

Fit for purpose

Fit for purpose

Compliant

Compliant

Compliant

Fit for purpose Fit for purpose

“Fit for purpose” assessment ensures the quality of data in the architecture supports the decision making process and is good enough to guide the transformation effort.

Compliance assessment ensures that the architectures are complete and adhere to the rules of related architectures and the rules of developing architectures.

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Want to avoidWant to avoid

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Want to enableWant to enable

…Highly cohesive set of capabilities delivered to the field (e.g. MAJCOMs)

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Approval Process Approval Process (Level 2) (Level 2)

SET-UP: Charter and Establish ARB

Respond to ARB participation request (named staff)

Negotiate review plan and date

STARTSTART: Prepare review request package (RRP)

Send RRP to ARB

Create arch review prep package

Generate preliminary findings

Create arch review package

Generate specific criteria

Present Architecture

Generate final rpt

Generate action plan in response to preliminary findings

Receive/review RRP

Negotiate review plan and date

Send arch review prep package

Receive and review arch review package

Post arch review package and confirm meeting

Receive arch review prep package

Send arch review package to ARB

Hold arch review

Coordinate preliminary findings

Schedule approval session

Send final report

Attend approval meet

Schedule approval meet

Attend approval meet

Sign & send

Maintain record

Next Step

One-time initial set-up of Architecture Review Board (ARB)

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Certification Process Certification Process (Level 2) (Level 2)

Negotiate review plan and date

STARTSTART: Prepare certification request package (CRP)

Send CRP to ACR

Create arch certification prep package

Generate preliminary complianc e report

Create arch certification package

Generate specific criteria

Generate final rpt

Generate action plan in response to preliminary complianc e report

Receive/review CRP

Negotiate review plan and date

Send arch certification prep package

Receive and review arch certification package

Post arch certification package

Receive arch certification prep package

Send arch certification package to ACR

Assess arch compliance

Coordinate preliminary complianc e report

Schedule approval session

Send final report

Attend approval meet

Schedule approval meet

Attend approval meet

Sign & send

Maintain record

Generate certificate

Recordcertificate

PublishArchitecture as certified

UseArchitecture

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

AF Compliance AF Compliance ReportsReports

AF Compliance Report Reports on the architecture compliance assessmentContains detailed assessment of the subject’s current degree of compliance and the required actions to achieve full compliance in cases where full compliance has not yet been reached

AF Compliance Reports should be ReviewedApprovedRetained, and Made accessible (e.g., web-posted)Controlled by the Air Force Architecture Certification Authority

AF Architecture Compliance PlansCondition to achieve full certification in the event of non-compliance; will include:

Detailed assessment of the current degree of compliance Key requirements and estimated deadline to achieve compliance Actions needed to achieve compliance and identification of the associated risks and dependencies

NRKPP

ISP

Clinger- Cohen

JCIDSNDAA

FISMA

AF EA

I n t e g r i t y - S e r v i c e - E x c e l l e n c e 13

Operations

Information

Services

Constraints (Drivers and

Input)

Uses and Impacts

Supported Architecture

Supporting Architecture

Subject Architecture

Technology

Standards (Compliance Criteria for

architectures and/or

programs)

Foun

datio

n

Architecture FederationArchitecture Federation

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

AF Architecture AF Architecture Federation GoalsFederation Goals

Improve interoperation with Joint operationsDoD operationsAF operations

Improve investment decisions / resource allocation

Develop mission-focused architectures with meaningful relationships (interdependencies)

Support process improvementservice orientation, and information transparency

14

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Situational Situational assessmentassessment

Operational interdependency focused models are a sound foundation for federating

Operational interdependency focus is based on an “I need/we provide”relationship pairing – i.e. a service focus (process, data, human, ...)Operational interdependency focus yields healthy discussion on interdependent touch-points that are performed for the MISSION

So what? Agreement on the interface!

OperationsOperations

InformationInformation

ServicesServices

Subject Architecture

TechnologyTechnology

Standards (Complian ce Criteria)

Standards (Complian ce Criteria)

ACS

OperationsOperations

InformationInformation

ServicesServices

Subject Architecture

TechnologyTechnology

Standards (Complian ce Criteria)

Standards (Complian ce Criteria)

Logistics Support

OperationsOperations

InformationInformation

ServicesServices

Subject Architecture

TechnologyTechnology

Standards (Complian ce Criteria)

Standards (Complian ce Criteria)

Global Strike

Drop bomb We load and fuel planes

We deliver fuel and bombs

I need Plane loaded and fueled

I needFuel and Bombs to load

Yep, just call this number when you need fuel and bombs loaded!

Right and you just call this number when you need fuel!

So all I have to do is call you?

15

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Making the Connections:Making the Connections: Delivering Capability thru the SeamsDelivering Capability thru the Seams

Logistics Architecture Force Management Architecture

Force Application Architecture Global Strike Architecture

Air and Space Operations Architecture Joint and AF C2 Architecture

Cyber Command Architecture A1 Personnel Architecture

Architecture InterfacePoints

Described as SLAs

Combat Support Processes

Combat Support Information

Combat Support Services

Agile Combat Support Architecture

Combat Support Technology

Combat Support

Standards (Compliance

Criteria)

Com

bat S

uppo

rt E

ffect

s an

d C

apab

ilitie

s

Execute Course of Action

Report on COA

Report on Readiness

Report on Battle space

Load and Fuel Plane

Position Equipment

Position Forces Maintain Network Access

Maneuver Airborne Assets

Define Force Structure

Communicate over LAN

AuthenticateUser

Find GFM Service

Communicate wirelessly

Deliver Material to Depot

Recover Apparatus

Train Maintenance

Staff

Keep Airmen Fit to Fight

??

??

??

??

????

??

????

????

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

A2 A3/5 A8 A9 A1 A4/7 AQ FM

Policy and GovernanceAF EA

DOTMLPF

…

Understand and Reflect

A6AF IT EA

AF IT Infra-

structure

Guide

DOTMLPF

DOTMLPF

DOTMLPF

DOTMLPF

DOTMLPF

DOTMLPF

DOTMLPF

Depth

DOTMLPF

Depth

PG1DOTMLPF

DOTMLPF

PG2DOTMLPF

PGnPG1

DOTMLPF

PG2DOTMLPF

PGnPG1

DOTMLPF

PG2DOTMLPF

PGnPG1

DOTMLPF

PG2DOTMLPF

PGnPG1

DOTMLPF

PG2DOTMLPF

IIBPG1

DOTMLPF

PG2DOTMLPF

PGnPG1

DOTMLPF

PG2DOTMLPF

PGnPG1

DOTMLPF

PG2DOTMLPF

AQP Gn

PG1DOTMLPF

PG2DOTMLPF

PGnDOT

MLPF

ACC AETC AFMC AFRC ASO AFSPC AMC ANG PACAF USAFE

DOTMLPF

PG2DOTMLPF

PGn

BRM SRM DRM TRMPRM ComplianceCriteria

BRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CC

BRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CCBRMSRM

DRMTRM

PRM

CC

DOT

MLPF

BRMSRMDRMTRM

PRM

CCBRMSRMDRMTRM

PRM

CCBRMSRMDRMTRM

PRM

CCBRMSRMDRMTRM

PRM

CCBRMSRMDRMTRM

PRM

CCBRMSRMDRMTRM

PRM

CCBRMSRMDRMTRM

PRM

CCBRMSRMDRMTRM

PRM

CCBRMSRMDRMTRM

PRM

CCBRMSRMDRMTRM

PRM

CC

POM

CPM

d5000

CBP

Air Force Architectures Air Force Architectures (How should they relate in general?)(How should they relate in general?)

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Fit for Federation Fit for Federation Framework (e.g.)Framework (e.g.)

Operations

Information

Services

AF Architecture DescriptionsSupported Architecture

Supporting Architecture

Subject Architecture

Technology

Standards (Compliance Criteria for

architectures and/or

programs)

Foun

datio

n

Architecture Interface Points

Architecture Interface Points

Minimize, generalize, and standardized!Minimize, generalize, and standardized!

18

Architecture Interface Points

Architecture Interface Points

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Fit for Federation Fit for Federation criteriacriteria

General criteria to be appliedapplied to architecture efforts

Purpose has been documented and verified by users and usagesInput has been verified as from authoritative source and authoritative source recordedSupported architecture interface points and associated standards identified, documented and verifiedSupporting architecture interface points identified, documented and negotiated with providerSpecific architecture Standards (Compliance Criteria) established, documented, and verifiedOutput has been verified as fit for use

19

NRKPP

ISP

Clinger- Cohen

JCIDS

NDAA

FISMA

AFEA

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

RRoleoles in Federation:s in Federation: Who is responsible for what?Who is responsible for what?

Architecting organizationsCreate new Architectures that are Fit For Federation (Fit For Federation (akaaka FederateFederate--able) able) out the boxAugment existing architectures to be Fit For FederationFit For FederationGet architectures approvedapprovedGet architectures certifiedcertified

SAF/A6PAIt is SAF/A6PA’s role to “Federate” the AFSAF/A6PA will federate any architecture that is formally certified

20

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Fit For Federation EnablesFit For Federation Enables

Lower cost of integration and interoperability

Improved efficiencies and operational effectivenessReduced redundancy and improved scalability Process improvement, service orientation, and information transparency

An Interoperable Air ForceWith other services and coalition partnersDefined by operational interdependenciesOverall picture of the Air Force

21

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Institutionalizing Fit Institutionalizing Fit For FederationFor Federation

Fit For Federation will be embedded inAir Force Policy Document – AFPD 33-10Air Force Instruction –AFI 33-401 or substituteAir Force Manual (s) – AFMAM XX-XXX (TBD)Air Force Guidance – AF Architecture Framework

Current state constitutes minor updatesAir Force Instruction – AFI 33-401 (Interim Change 1)

22

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

BackupBackup

23

Questions?