1. Warfighting Integration Vision
Source: SAF/CIO A6 Update for SECAF and CSAF, 2 November 2010
Brig Gen Bob Ranck
Warfighter Systems Integration
SAF/A6W

2. Our Shared Goal
Mission assurance by providing joint force commanders network enabled operational capability to…
See with clarity
Network with assurance
Communicate with certainty
Navigate with accuracy
Strike with precision
Source: 2010 QDR and AFNet Roadmap
Improve Capabilities, Flexibility & Robustness of Forces Across the Domain

3. Closing the seams between sensors, decision makers, and shooters
WFI Vision
Enable the Joint fight by making authoritative information from any system available to the warfighter
Synthesizing information and coordinating capabilities to produce effects in any domain
All data belongs to the enterprise and informs the Joint Force Commander
Source: Issue Paper on Warfighting Integration , 3 Feb 11
Baked in, not bolted on
Institutionalize WFI functions and processes across the AF
Partner with lead integrators and stakeholders
Closing the seams between sensors, decision makers, and shooters

4. Institutionalizing Warfighting Integration is Key to Success
WFI…How Do We Get There?
Effective Warfighting Integration is a Team Sport
Warfighting Integration Strategy and Principles
Strategy and Operational Art are Built Upon Information
Information Belongs to the Enterprise
Timely Authoritative Data Available to all Domains, Platforms, Participants
Focus on Warfighter Needs
Inform Planning, Requirements, Program and Acquisition Processes
Integrate Modeling & Simulation
Steer thru WFI GOSG; Feedback thru Net Centric CPM
Source: SAF/CIO A6 Update for SECAF and CSAF, 2 November 2010
We’ve made tremendous progress in improving warfighting integration, most notably by shortening the kill chain through improved machine-to-machine integration, but much work remains to be done. Ensuring integration of our 5th generation fighters and legacy platforms into a standardized aerial layer network stand out as a key example. In order to tackle integration in a systematic fashion, we need to address the subject up front, not after the fact. Integration can’t be viewed as a job for the CIO A6. It must be a foundational consideration in our requirements, acquisition, planning, and programming processes. In the same way we’ve learned to think “joint,” we need to think “integrated.”
Warfighting Integration strategy is essential to developing systems, processes, and services totally integrated within and across our Service Core Functions. In addition, we must be integrated with our sister services and coalition partners.
A6 is leveraging the CPM process to balance programs to achieve effectiveness and efficiency. We achieve effectiveness by developing programs jointly and integrated with current systems and future architectures. We achieve efficiency by identifying redundant systems and proving interoperability through tests before delivery.
We are working with the Requirements and Acquisition community to instill the mentality of “born integrated” in every requirement, program, system, and service.
The formation of the new WFI General Officer Steering Group as directed at CORONA will further enhance net-centric integration and interoperability.
Institutionalizing Warfighter integration is key to success.
Institutionalizing Warfighting Integration is Key to Success

5. Key to Institutionalizing Warfighting Integration
Serve as an executive communication tool and help leadership succinctly and accurately calibrate senior leader guidance aligned with the roles, priorities and tasks of the Warfighting Systems Integrator
Reflect the realignment of C2, cyber, and WFI functions directed at CORONA Fall 2009
Provide informed guidance in support of the Warfighting Integration General Officer Steering Group (GOSG)
Help create more synchronization of effort among key stakeholder organizations
Illuminate existing and emerging senior leadership priorities

6. Institutionalized Integration Through Visual Mapping
Visualizing WFI
The A6 VIM initiative is designed to generate a series of 18 inter-related strategic information MAPs expressly engineered to create and sustain one shared vision across the entire SAF/CIO-A6 staff, as well as internal and external organization stakeholders, plus ensure alignment with SECAF/CSAF needs
The VIMs are a style of information representation that aids an audience’s ability to build a consensus view of complex strategies, initiatives, or projects in a unique and visually compelling form. VIMs succinctly replace complex PowerPoint Presentations and White Papers using Visual Metaphor Maps that tell a story. (Common examples of simple visual metaphors are an umbrella as protection or all encompassing, rabbit and tortoise for speed, skull and crossed bones for death, danger or poison).
Institutionalized Integration Through Visual Mapping

7. WARFIGHTING INTEGRATION
Core Function Integration
WARFIGHTING INTEGRATION
SPEC OPS
NDO
AIR
SPACE
CYBER
GPA
RGM C2 PR BP
ACS
GIISR
Source: Net-Centric Capability Portfolio Management, 27 Jan 11; A6WS Strategy Division WFI Roadmap Brief, 16 Feb 11.
WFI – enabling net-centric operations across the AF enterprise
Shape & drive Planning, Requirements, Programs & Acquisition to maximize warfighting capabilities and assure our ability to dominate the air, space, and cyber domains

8. Charting the Course Strategy Leveraging CPM
AF Net-Centric strategy nested in joint Net-Centric strategy
Codifies & defends Portfolio across PPBE, DAS, JCIDS
Largest contributor to DoD Net- Centric capability
~$4B in AF Net-Centric capability re-prioritized during last 4 PBRs
12 PBR: ~$1.1B over FYDP in play
Shape and drive requirements, programming and acquisition to create and sustain a robust net- centric operating environment
WFI Decision Support Tool underpinned by architecture and authoritative data to inform and influence corporate investment decisions
Source: SAF/CIO A6 Update for SECAF and CSAF, 2 November 2010
Acronym: DAS – Defense Acquisition System
Coherent, fully vetted Net-Centric (NC) Strategy required to better frame and support AF planning, programming, and budgeting decisions
Collaborating with A8, A2, A3/5 and lead commands to resurrect and update the C4ISR Roadmap initiated by XI back in 2006
  The “reinvigorated” roadmap will capture and illustrate current (FY13) Service Core Function program baselines and model capabilities programmed over the FYDP
Models of each of our Capability Portfolios, tied to our Enterprise Architecture and underpinned by financial data and timelines will better illustrate program dependencies and primary/secondary/tertiary effects in support of Portfolio Managers defending AF programs and/or weighing alternatives during POM development and subsequent program reviews
SAF/CIO A6 is leveraging Capability Portfolio Management (CPM) to enable a Net-Centric Strategy with dedicated resources to staff and support a fully functional CPM to balance the Air Force’s NC capabilities. CPMs are aligned to DoD Joint Capability Areas and, in the AF, ensure support to our Service Core Functions to ensure our mission areas are effectively/efficiently covered.
We are developing an annual AF NC strategy to synchronize AF’s NC JCIDS, PPBE, and acquisition efforts
We believe this approach will help us better map this critical Joint Capability Area to our Air Force SCFs, while also reducing our exposure to OSD programming adjustments during Program and Budget Review.
12 PBR: Potential for reprogramming ~$1.1B in Net-Centric capabilities over FYDP
- Net-Centric bills to the AF to provide capability that is seen as not timely enough in our POM submission
- Reprogramming or delays in our Net-Centric portfolio due to fact-of-life changes in programs

9. Leverage Modeling & Simulation
Formal Interoperability Assessments/Evaluations
Test before fielding
Not duplicative, additive; compliance only a first step
Field interoperable systems at the ‘First Pass’
Focus on mission rehearsal and training
System-of-Systems (SoS)
Integrated mission threads based on cross- platform OV’s/SV’s
Work with NR KPP experts from cradle to grave
 - We are teaming with SAF/AQ to adopt an enterprise view of CIO policy in AFI to enable Acquisition mission success by providing CIO Compliance Requirements integration early and throughout the IT Acquisition Lifecycle.
The bottom-line of what we’re trying to do is collapse both ends of the acquisition process depicted here and focus on what’s really important—developing the right technology for the warfighter to use
-At the heart of doing this is DEFINING THE FOUNDATIONAL REQUIREMENT—that allows us to exploit capabilities and get that capability to the warfighter more quickly
- Over the years it was recognized that stove-piped polices was levied on acquisition and sustainment programs – hard to use, hard to manage. Along with updating AFI , we also are teaming with SAF/AQ on AFPAM to provide program tailoring and best practices to streamline and execute programs as efficiently as possible.
Possible Question: Why is this necessary? Answer – Often IT considerations are sort of an after thought in the development of major weapons systems. Ideally this effort will result in a more deliberate consideration of IT requirements throughout the acquisition process. NR
KPP
Operationally relevant, LVC testing
Capabilities that work
WFI – Enhance interoperability before system fielding

10. WFI GOSG WFI GOSG JCIDS CPM AFCS AQ CSAF DAWG JROC DAB DoD CIO
Service
VCS
SAF/US
JROC
VCS
3 Star
Programmers
AF/A3/5/8, SAF/A6
DAB
Svc SEC
SAF/AQ
DoD CIO
Exec Board
SAF/CIO A6
C2CIB
SAF/A6-2
AFROC
ITAB
SAF/A6-2
AFROCC
Panels
5 Mission
9 Mission Support
SSG
SAF/A6W
OIPT
SAF/AQI
JC2 CPM
JCD/JCCD
JFCOM J8
Joint
Warfighter
Talks
WFI GOSG
COCOM
Operations
WFI Board

11. Partnering Opportunities
Partner with Core Function Lead Integrators to incorporate WFI into Core Function Master Plans
Integration within each Core Function
Integration between Core Functions
Support WFI institutionalization
Partner with stakeholders to develop a holistic approach to ALN
Expand beyond anti-access
Architecture and CONOPS drive requirements
Move from “Marconi” to “Google”
Source: SAF/CIO A6 AFCEA Cyberspace, 10 Feb 11

12. Partnering Opportunities
CFLIs and A6W Integration
Incomplete Integration?
Thorough Integration?
Emerging Issues?
Big Rocks
Institutionalize WFI Principles
Data and Infrastructure Standards
JALN / ALN / Purple Rain
1553 Bus
AOC/DCGS
Source: SAF/CIO A6 AFCEA Cyberspace, 10 Feb 11

13. Single Integrated Network Environment (SINE) - AFSPC
Space Layer - AFSPC
Single Integrated Network Environment (SINE) - AFSPC
Commercial
MUOS
WGS
AEHF
Space
Net Enabled ISR
RQ-4
High
Federal / Next Generation
Air Traffic Systems
A6 and FAA
High Alt Gateway Relay
Net Enabled Nuclear Response
High Capacity Backbone
Voice
Link-16
VMF
SADL
B-52
Aerial Layer - ACC
E-3
B-52
E-2
MQ-1/9
F-15E
F/A-18
B-1
KC-135
B-2
C-17
Legacy TDLs
Net Enabled C2 ISR
F-22
EC-130
Advanced TDLs
RC-135
F-15C
Net Enabled MAF
E-8
ERMP
F-35
F-35
Source: Air Force Aerial Layer Networking, 21 Jan 11
[Placeholder: WARCAP video of JALN OV-1]
Joint Vision of JALN is what we are working towards
F-16
Medium
Mid Alt GatewayRelay
A-10
Low
Net Enabled
Attack / Weapons
Net Enabled SOF
ASOC
Tact’l Net Ops
H-60
CAOC
DCGS
JFACC
Op Net Mgt
Surface Layer – Joint Std
ADC II
CRC
Tact’l Net Ops X
Data Standards - JROCM XX
TOC
DCGS
JFLCC
Op Net Mgt
Data Standards – US(M)
Permissive
JFMCC
Op Net Mgt
Contested
Anti-access

14. Source: SAF/CIO A6 Update for SECAF and CSAF, 2 November 2010

15. Joint Aerial Layer Network
Commercial
MUOS
WGS
AEHF
Space
Net Enabled ISR
RQ-4
High
High Alt Gateway Relay
Net Enabled Nuclear Response
High Capacity Backbone
Voice
Link-16
VMF
SADL
B-52
E-3
B-52
E-2
MQ-1/9
F-15E
F/A-18
B-1
KC-135
B-2
C-17
Legacy TDLs
Net Enabled C2 ISR
F-22
EC-130
Advanced TDLs
Net Enabled MAF
RC-135
F-15C
E-8
ERMP
F-35
F-35
Source: Air Force Aerial Layer Networking, 21 Jan 11
[Placeholder: WARCAP video of JALN OV-1]
Joint Vision of JALN is what we are working towards
F-16
Medium
Mid Alt GatewayRelay
A-10
Low
Net Enabled
Attack / Weapons
Net Enabled SOF
ASOC
Tact’l Net Ops
H-60
CAOC
DCGS
JFACC
Op Net Mgt
ADC II
CRC
Tact’l Net Ops X XX
TOC
DCGS
JFLCC
Op Net Mgt
Permissive
JFMCC
Op Net Mgt
Contested
Anti-access

16. What’s in Play Video
Source: SAF/CIO A6 CAG
“What’s in Play” video

17. Operational Relationships Programmatic Relationships
Core Function
Panel
Cyberspace Superiority
Capability Portfolio
CYBERSPACE SUPERIORITY
NET-CENTRIC
Operational Relationships
27445F – FIGHTER TACTICAL DATA LINK
PE of Interest
33140F – INFORMATION SYSTEMS SECURITY PROGRAM
53120F – COMMUNICATIONS SECURITY (USAFR)
Programmatic Relationships
33140 PEM Contacts
B-2
BC9000 – Scope Edge
BQQ000 – Technology Development
BQY000 – Simulator Training
AAJ000 – Cmbt Info Transport
B-52
BDU000 – Air Ground COMSEC
BQR000 – Concept Refinement
BR0000 – ITS Inc 2-2nd Gen
AAW000 – Comm Security
BA4000 – Computer Security
BDV000 – Space COMSEC
BQS000 – AF Key Mgmt Infra
Expeditionary Comm & Infrastructure
AC9000 – Info Security
BA5000 – AF Electronic Key
BQK000 – Combat Key Generator
BQT000 – In-line Network Encrypt
Fixed Base Comm & Infrastructure
AEHF
BA6000 – Information Assurance
BQL000 – Vinson/ANDVY Crypto
BQU000 – Link Encryption Family
KC-135
AFNETOPS In Transition
BAF000 – Info Assurance RDTE
BQM000 – Space TTA Crypto
BQV000 – Computer Network
Network Ops Warfare Systems
AWACS
BBR000 – Crypto Mod IFF
BQO000 – Space Mission Data
BQW000 – Certified Workforce
NORTHCOM / NORAD
AZJ000 – Cryptographic Modern
BBT000 – Crypto Mod KG-3X
BQP000 – Remote Re-Key (RRK)
BQX000 – COMSEC Management
Space Comm Infrastructure
Attachments
Tags
Details
Interactive OV
Supporting PE Info
File Name Size Modified Location
33140 Slide 6.jpg 136KB Feb 14, Internal
33140.pptx 7194KB Feb 16, Internal

18. Acquisition & CIO Process Integration
As-Is
Acquisition & CIO Process Integration
To-Be
Acquisition Community
CIO Community
AQ & CIO Process Integration
 - We are teaming with SAF/AQ to adopt an enterprise view of CIO policy in AFI to enable Acquisition mission success by providing CIO Compliance Requirements integration early and throughout the IT Acquisition Lifecycle.
The bottom-line of what we’re trying to do is collapse both ends of the acquisition process depicted here and focus on what’s really important—developing the right technology for the warfighter to use
-At the heart of doing this is DEFINING THE FOUNDATIONAL REQUIREMENT—that allows us to exploit capabilities and get that capability to the warfighter more quickly
- Over the years it was recognized that stove-piped polices was levied on acquisition and sustainment programs – hard to use, hard to manage. Along with updating AFI , we also are teaming with SAF/AQ on AFPAM to provide program tailoring and best practices to streamline and execute programs as efficiently as possible.
Possible Question: Why is this necessary? Answer – Often IT considerations are sort of an after thought in the development of major weapons systems. Ideally this effort will result in a more deliberate consideration of IT requirements throughout the acquisition process.
Warfighting Integration -- baked in, not bolted on

19. Our Priorities Institutionalize Warfighting Integration
Build WFI Strategy
Advertise WFI Principles
Improve Planning, Requirements, Programming and AQ Processes
Govern through WFI GOSG
Interoperability of Aerial Layer Network (ALN)
Senior Leader Communications Systems
Source: SAF/CIO A6 AFCEA Cyberspace, 10 Feb 11
Institutionalize Warfighting Integration
Govern through WFI GOSG
Improve Req / AQ Processes
Build Warfighting Integration Strategy
Interoperability of Aerial Layer Network (ALN)
Future Airborne Capability Environment (FACE) Architecture
Universal Networking Interface (UNI) / Airborne Networking GIG Interface (ANGI)
Multi-Functional Advanced Data Link (MADL) / Link-16 / Tactical Targeting Network Technology (TTNT) / Joint Tactical Radio System (JTRS)
Senior Leader Communications Systems
Secure-Video Teleconference / Defense Info Switched Network (DISN) / Defense Red Switch Network (DRSN) / Go-go Wi-Fi access
- Establishing a standard gateway allows us to force interoperability on the aircraft end. We have developed a standard architecture that can deliver all these services at multiple classification levels.
Aerial Layer Network
Mobile adhoc networking and radio aware routing techniques… Things link effective compression and quality of service will be key to delivering the kind of performance required to gain the confidence of the operators
Need help with establishing standards which effectively utilize the limited bandwidth we have
Key attribute is defending the aircraft from IA attack by concentrating the defenses in the gateway, obviating the need to deal with integrating firewalls and intrusion detection on every aircraft
FACE
-- Refining FACE architecture and the interfaces to platform mission computers, displays, sensors, and networks
DoD-led consortium
Designed to achieve interoperability via common standards
Airborne Network GIG Interface
Concept of developing standard gateways for use by aircraft. Just like the web transformed our mission effectiveness on the ground, extending the GIG to the airborne environment for potential benefits is in high demand.
Currently, each platform develops their own approaches and architectures to support connectivity and access to secure voice, data, and/or video service which is duplicative and an interoperability nightmare.
Senior Leader C3 Systems - Airborne – This is the suite of communications capabilities we provide to the President/Vice President, SECSTATE, SECDEF, DNI, SEC Homeland Security, CJCS, and COCOMs. There is no higher priority than ensuring effective communications between the Nation’s most senior leaders.
We used to use the STU-III that was designed by the military for a range of conditions. Then we adopted COTS solution – the Secure Telephone Instrument (STE). STE was designed to operate primarily in the pristine ISDN ground environment – not over INMARSAT. The result is incidents that get worked at the highest levels.
Secure voice is our number 1 priority. We do not have a standard secure voice instrument that is suitable for use in the airborne environment.
We need standards for secure services including voice for mobile users that account for the range of environments. We also would like standards which generate commercial products that are suitable for FAA airworthiness certification.
Secure VTC
We need standards that make VTC viable over smaller SATCOM links including compression and quality of service. Standards that make it possible to do Net Meeting should be applied in a more bandwidth constrained environment.
Capability that senior leaders need to do their missions. We have basically adopted ground based VTC solutions to the aircraft. They are bandwidth intensive ( k) to achieve quality expected.
- We deliver voice, data, and VTC capabilities across multiple classifications required by airborne senior leaders to perform their jobs. The big effort now is the transition of the voice infrastructure to VOIP/VOSIP. Testing has shown that more effective Codecs are required by low bandwidth connection between the aircraft and the ground – then we have to convert to ground standard. Why don’t we have a standard that senses the access appliance being used and taylor content based on the bandwidth available?
Defense Information Systems Network (DISN) internet connectivity:
Go-go Wi-Fi on USAF platforms: USAF doesn’t utilize any Wi-Fi capability on SLC3S aircraft. The current issue is how to secure a Wi-Fi network that’s in close proximity to other classified networks. We require standards that will allow NSA to allow unclassified Wi-Fi access while not compromising classified networks in close proximity – that means a standard for securing wireless.