1. Focus Area Forum: Sensor Open Systems Architecture (SOSA) Colonel Michael Schmidt Program Executive Officer for ISR and SOF August 4, 2015
Good morning, I’m Col Mike Schmidt, the Program Executive Officer for ISR and SOF.
Its my privilege to kick off this Industry day and to discuss a renewed interest in a concept that has been around for a some time, open systems approach. My message is very simple:
Leadership recognizes that we cannot continue to do business like we have in the past, relying on Prime contractors to upgrade and modernize our UAS fleet with minimal consideration of interoperability and compatibility with other applications.
There has been some very good work done on open systems standards and processes across the Services. I ask you to consider this work as a starting point going forward but I don’t want to close the door completely on creative thinking and outside-the-box solutions.
We need your help in bringing the smartest people in your industry to help guide us on this path using a consortium or partnership approach. The consortium process opens the door for industry to participate in standardizing sensor architectures, and have that agreed to by industry as a whole and not unique to any one company.
Distribution A

2. ISR & SOF Snapshot ISR – FIND/FIX MOBILITY - INFILTRATE
4/26/2017 2:17 PM
ISR & SOF Snapshot
ISR – FIND/FIX
MOBILITY - INFILTRATE
STRIKE - FINISH
GLOBAL HAWK (WIG)
CV-22 (WIV)
137
MQ-1 (WII)
6/18 (+3)/11 42 44
LIBERTY (WIJ)
183/4
183/4
CRH (WIH)
BSSG (WIJ)
50+ Projects
12/24
MQ-9 (WII)
HC/MC-130J (WIS)
MC-130E/P/H (WIU) 22
RC-26 (WLV) 7
17/2 32 11
AC-130U (WIU)
AC-130J (WIS)
EC-130J (WIU)
U-2 (HBG)
97/28/62/72
Rotary – (WIU)
HH-60, TH-1H & UH-1N/UH-1N Recap
Sensors & FMS
(WIN)
Here’s the ISR & SOF current snapshot
Our mission in the ISR & SOF goes well beyond remotely piloted aircraft to vertical lift platforms, sensors, ground stations and Special Operations Forces support
With almost 1700 people we manage a 15+ billion dollar budget across the active budget years (FY13-15) covering 143 programs and projects, including 32 foreign military sales efforts
The ISR & SOF is the largest acquisition directorate with the most rapidly expanding portfolio in the Life Cycle Management Center.
In the lower right corner you see my favorite reminder of why we do what we do every day in the ISR & SOF. This is a picture of the legacy battlefield airman, carrying 150 pounds of equipment. We are working to physically unburden him by lightening his load to 70 pounds and making him a more effective contributor to the joint fight.
a/c totals (inventory, not DD-250 to date [attrition]):
GH – 6 Block 20, 18 Block 30 (both 30I & 30M) (+3 in production), 11 Block 40
CRH – 112 Planned (zero delivered to date)
CV-22 – 43 Delivered of 50 total (original plan for 52, but have lost 2 in mishaps)
AC-130J – 37 Planned (2 delivered to date)
HC/MC-130 – 36 Delivered to date (12 – HC-130Js, 24 – MC-130Js) of total planned 131 (37 HC, 94 MC)
RC-26 – 11 in inventory
MQ in inventory
MQ-9 – 183 Block 1 in inventory; 4 Block 5 in inventory (being used as test assets); (note: this is not DD:250 to date those numbers are 195/4)
U2 - 32
WIJ:
1. MC-12W Project Liberty: 42
2. RC-135V/W Rivet Joint: 17
3. RC-135S Cobra Ball: 3
4. RC-135U Combat Sent: 2
5. WC-135C/W Constant Phoenix: 2
6. TC-135W Trainer: 3
7. KC-135R Test Tanker II: 1
8. EC-130H Compass Call: 14
WIU
HH-60 OLR: 0/21
AC-130H/U/W: 4/17/12
EC-130J: 7
HC-130N/P: 9/18
MC-130E/H/P: 0/20/11
MC-130J: 19
HC-130J: 11
TH-1H
UH-1N
UH-1N Recap – 72 (FY17: 4, FY18-FY23: 10 ea yr, FY24: 8)
Portfolio Summary
88 Programs, Projects & FMS
5 ACAT I (MQ-9, Global Hawk, CV-22, CRH, HC/MC-130 Recap)
2 ACAT II (C-ABSAA, HHG60-OLR)
31 ACAT III
37 FMS Cases
13 Exemption List
7 QRC/Accelerated Acquisition
1697 Personnel – AFLCMC Assigned
Military 283
Civilian 963
Contractor 357
Other 94
Total 1697
$16B+ in Active Dollars
AFPEO ISR & SOF Vision/Mission:
“One Team, One Source for World Class ISR & SOF Solutions”/“Equip Our ISR & SOF Warfighters to Dominate the Battlespace”
AC-130H (WIU) 14 4
EC-130H
Med Alt UAS (WII) SOF/PR &
Global Hawk (WIG) Rotary (WIU)
BSSG (WIJ) CV-22 (WIV)
Sensors/FMS (WIN) CRH (WIH)
SP Ops/PR (WIS) RC-26 (WLV)
U2 (HBG)
AC-130W
(WIU)
TENCAP (WIR) 12
Battlefield
Airmen
NTNF (WIR)
Cleared for Public Release
88ABW
UNCLASSIFIED

3. ISR & SOF Portfolio Overview
A&AS:
21%
AFPEO ISR & SOF Mission: Develop, acquire, field, modernize and sustain the world’s best network-ready intelligence, special forces, surveillance and reconnaissance capabilities today and tomorrow -- Agility…Innovation…Focus
ACAT I - 5
ACAT II -1
ACAT III - 27
TENCAP - 17
ISR & SOF Locations
In addition to 5 ACAT programs, Big Safari has 34 additional projects.
ISR & SOF provides acquisition support to Tactical Exploitation of National Capabilities (TENCAP). We are currently supporting 17 “Talons”, or projects.
We are also managing two program in the National Technical Nuclear Forensics mission area, Harvester, which is a podded nuclear air sampling capability, and United States Prompt Diagnostics System (USPDS). USPDS is envisioned to be a fully integrated, terrestrially based, geographically dispersed, centrally managed, operational prompt detection and diagnostics system designed to detect, identify, and characterize a limited nuclear event in an urban environment and provide data to support the U.S. Government's attribution of such an event.
FMS - 53
AML Exempt - 29
Big Safari - 34
NTNF – 2
Cleared for Public Release
88ABW

4. ISR and Our Joint Interest
Historically
ISR systems “ mission specific” with distinct targets
“One Trick Pony” vs multi-use platform agnostic
Vendor lock and data rights
Stifle competition
Limited innovation
Overall high life cycle cost
Operationally ISR requires
Means to find difficult targets
Operational flexibility
Responsiveness and interoperability
RAPID INNOVATIVE IDEAS from INDUSTRY
Over the past decade many of our systems have been QRC’d for war. Many of our systems were likewise mission specific with a distinct set of targets in mind. Our priority for capability stifled competition and led to many “one trick pony’s”. The need for open systems architecture took a back seat until recently.
Today a push for Open Systems is paramount. It is being directed from the top, and as you can see from this effort, pushed from the bottom as well. From the size of this forum, I see how important this is to industry as well to the acquisition community.
We need to ensure due diligence in our future designs of ISR systems. The results of this effort (SOSA), should help us keep up with the ever changing and difficult targets, provide more flexible and agile designs, create an industry partnership that is quickly responsive to more innovative ideas.
As you may have notice in the audience, our interest in ISR comes not only from the Air force but also the Army and Navy and other government agencies as well. We all have common elements for how we collect, process, store, and disseminate intelligence.
If we do this right, and design our architecture agnostically with respect to a platform, with scalability in mind, the applicability of this sensor centric effort is huge. We can affect shipboard as well as ground systems designs. It may also effect how we procure facility security equipment as well. My point is this impact this effort has is huge. The tentacles of what it touches are vast if done smartly. That’s why we need you to bring your expertise into the design.
But without going to fast and too far, we have concentrated our efforts on ISR. In this environment we see the common elements across AF, Army and Navy.
Distribution A; AFI Atch 2

5. Quick Comparison Table
OMS
Mission Sensor Interface Centric
Payload Integration
S/W Integration
Service Oriented
UCI Message Model
Java, C++
Isolation
H/W abstraction
Ease of integration
Software re-use
SOSA
Sensor Subsystems Centric
Payload Integration
S/W Integration
Real-time OSs
Electrical/Mechanical
Java, C++
Isolation
H/W abstraction
Ease of integration
Software re-use
FACE
Avionics S/W Centric
S/W Integration
Real-time OSs
Segments (5)
Profiles (4)
UCS Data Model
Java, C++
Isolation
H/W abstraction
Ease of integration
Software re-use
Distribution A; AFI Atch 2

6. Open Architecture Systems
Characteristic
Open Systems
Remarks
Decouple hardware (h/w) and software (s/w)
H/w and s/w can be changed independently of each other.
Enables the system owner to easily upgrade the h/w and s/w.
Decouple s/w modules
S/w components have modularly defined functionality.
Allows the system owner to quickly insert new capabilities.
Defined data model
Data contents and meaning defined in a data model.
Simplifies the process for adding new capabilities.
Interface definition
Hallmark of open systems is the definition of all interfaces.
Essential for open systems. Interfaces are non-proprietary and owned by customer.
Distribution A; AFI Atch 2

7. Open Architecture Systems
Characteristic
Open Systems
Remarks
Standards
Use government or industry defined and controlled standards.
Set of standards chosen is highly dependent upon system environment.
Life cycle development models
Any model may be used—works best with iterative/evolutionary models.
System owners benefit most from iterative/evolutionary approach.
Commercial-of-the-Shelf
Embrace COTS and support COTS dynamic aspects.
OAS leverage COTS and tapping into faster fielding of newer technologies.
Data rights
Owners of the system have the rights necessary to maintain the system.
Ensure interfaces are non-proprietary/owned by systems owner.
Distribution A; AFI Atch 2

8. What Do We Need From Industry?
We are looking for rapid innovation ideas that go beyond the “golden screw” approaches to ISR missions. Ideas that:
Maximize modular design
Maximize reuse of existing designs
Focus on Government and industry peer teaming
Increase business opportunities thru alternative vendor sources
Create a more “Droid Like” business model
To successfully change the services’ inclination toward buying proprietary systems and shift towards the acquisition of open systems, we are taking the lead to address address policy and leadership challenges that have yielded limited success stories to date. We recognize moving to open systems requires strong leadership to overcome preferences for acquiring proprietary systems.
We also recognize that we cannot do this without Industries help. Fundamental elements of open systems approach where we need you help include:
Designing a system with modular components that isolate functionality.
Developing and using open, publicly-available standards for the key interfaces, or connections, between the components
Obtaining data rights to interfaces when open standards are not available.
Distribution A
AFI Attachment 2
Distribution A; AFI Atch 2

9. DELIVER•INNOVATE•GROW
In Closing
ISR/SOF:
Provides Diverse Capability to the Warfighter
Meets urgent needs with speed and discipline
We D.I.G. in:
DELIVER•INNOVATE•GROW
Cleared for Public Release
88ABW
FOUO