DISTRIBUTION A: Approved for Public Release on March 10, 2015: distribution is unlimited.

AFCEA Aberdeen Luncheon

Army Common Operating Environment (COE) Update

Mr. Phillip Minor, Deputy Director, COE Directorate Assistant Secretary of the Army for Acquisition, Logistics and

Technology (ASA(ALT))

March 11, 2015

Agenda

Background: The Army at a Crossroads in 2010

COE Leadership

The Value Proposition for COE

The Command Post Challenge: How we resolve with COE

The Scope of the COE Challenge

Transition Requirements to the IT Box Framework to Sustain the Effort

Better Buying Power (BBP) 3.0 / Modular Open Systems Architecture (MOSA) and COE Alignment

Army / Industry Shared COE Drivers

The Challenge in Tracking Progress: Achieving Speed

Good News

2

Background: The Army at a Crossroads in 2010

The Army was on two parallel investment / modernization paths which was unsupportable

Budgetary constraints and sustainment costs were drivers for gaining efficiencies and converging to an Army COE

Intent to achieve interoperability on the front end vice back end Intent to reduce testing, as well as developmental and certification efforts, in terms of

time and cost

Stay the course Move to a COE

3

COE is an approved set of computing technologies and standards that enablessecure and interoperable applications to be rapidly developed and executed across a

variety of computing environments (CE) (six) led by Program Executive Offices (PEOs)

• Mobile/Handheld CE - PEO Soldier• Mounted CE - PEO C3T• Command Post CE - PEO IEW&S & PEO C3T• Data Center/Cloud/Generating Force CE - PEO EIS• Sensor CE - PEO IEW&S• Real Time /Safety Critical/Embedded CE - PEO Aviation

4

The Value Proposition for COE

• Achieve agility on how we deliver capabilities to the Warfighter faster (Vice Chief of Staff, 14 Apr 2011)

• Reduce the life cycle cost of development and sustainment of our IT systems (DoD Efficiency Initiatives, 16 Aug 2010)

• Promote an Open Architecture that is standards based which leverages industry’s best practices and productswhile reserving government purpose rights (Directive for Better

Buying Power, 3 Nov 2010)

• Build on a foundation that is cyber hardened and secure(ARCyber Command)

• Achieve simplicity of the Network – ease of use, reduced number of systems, more agile CPs (NCR Key Tasks)

Build Common SW Platforms, mandate reuse, build WidgetsTo replace PORs

EliminateDuplication

ImplementIdentity Mgt, Role Based Access Control

Follow industrymodel, leverage commercial technology

Reduce complexity& footprint

Gain efficiency by establishing common foundations which eliminate duplication and transition PORs to software only; focusing on developing widgets that support Warfighter Functions

5

The Command Post Challenge How we resolve using COE

Software Development Kit: Standardizes key features used to develop, assemble, and configure widgets

Widget: Lightweight, single purpose applications deployed to a server based environment & accessed through a web browser

Ozone Widget Framework: Web/server based environment designed to support the

development & deployment of widgets and mechanisms to support communications between widgets

Command Post “To Be” StateSimplified, reduced cost, agile

Core Services: Contains the fundamental system services that all applications use

The commercial world has shifted focus to small, flexible, mobile code via widgets and other mobile applications

Command Post “As is” StateComplex, costly, inefficient

Recommendation under review

6

The Scope of the COE Challenge

Data based on 28 August 2014 TAB Approved System Migration Binning List

RTSCE44 Primary Systems

M/HH10 Primary SystemsFocused on Mission

Command

DC/C/GF65 Primary Systems

CP CE26 Primary Systems

Sensor38 Primary Systems

Mounted6 Primary Systems

Relationships / Dependencies

• Schedules• Interoperability• Resourcing• Services• Performance• Authority • MDA, APB

7

Transition Requirements to the “IT Box” Framework to Sustain the Effort

IS CDD – Information Systems Capabilities Development Document RDP – Requirements Definition Package

COE will reduce the complexity and footprint of the network

8

Better Buying Power (BBP) 3.0 / Modular Open Systems Architecture and COE Alignment

Problem Statement: Rapid evolution in technology and threats require much fastercycle-times for system fielding and modification. Increased life-expectancy of systems, requires accelerated and cost-effective dexterity to upgrade the technology of systems (HW/SW) while maintaining our capabilities in an era of reduced RDT&E budgets.

• Modular Open Systems Architecture (MOSA) is composed of two key concepts: Modularity + Open Architecture

– Modularity refers to the ability of a system to be implemented in components. The goal of modularity in this context is to have well-defined system components, where such components may be hardware or software, that can be removed and replaced as technology changes with equivalent components at minimal effort and/or cost. (proposed)

– Open Architecture (according to the Contract Guidebook for Program Managers, v1.1, June 2013) is a technical architecture that adopts open standards supporting a modular, loosely coupled and highly cohesive system structure that includes publishing of key interfaces within the system and full design disclosure.

9

Army / Industry Shared COE Drivers

International Data Corporation (IDC)

Both Army and Industry need to:

• Understand and plan for emergent IT

• Track App/Resource usage and adjust

• Maintain interoperable and secure resources

• Benchmark/manage performance (metrics)

• Reduce cost

To this end, Industry substantially invests in:

• Premium Infrastructure & highly qualified Staff

• Cloud to centralize, monitor and tightly control resources (utilizing metrics).

• Standards (track & participate) particularly with respect to Interoperability and Security

• Shared Core ServicesSource: CMU SEI

10

The Challenge in Tracking Progress: Achieving Speed (Notional)

Fielding Stages

Average Time

Days

Weeks

Months

Years

Need orOpportunity

Identified

RequirementEstablished

Funding Secured

ContractAwarded

ProductDeveloped

ProductTested

ProductCertified

ProductDeployed

Pre-CoE Implementation

Cumulative

Post-CoE Implementation

Achieving the goal of rapid development requires addressing all dominant life cycle delays

11

Good News

COE is an Army Priority and is one of six Focused End States in support of the Chief of Staff of the Army’s Mission Command Network 2020 Strategy

COE v3.0 Standards developed Conducted NIE 15.1 CPCE Demo (Unified Data Pilot) COE v1.0 testing April 2015 Key Army Stakeholders fully committed and COE is being Institutionalized

ASA(ALT): The Army Acquisition Executive (AAE) signed a directive to PEOs providing guidance for COE v3.0 implementation

TRADOC: Developed and executing COE Requirements Strategy; and Planning to incorporate COE into the Battle Labs

ATEC: Supported development of testing and certification strategy G-8: Engaged in programming resources for COE and development of COE Business Rules CIO/G-6: Evaluating how to certify COE Army Marketplace requirements; and COE is referenced

throughout the Army Network Campaign Plan CSA: Published 2014 COE Execution Order (EXORD) to synchronize key activities G-3/5/7: Established COE Synchronization Integrated Process Team (IPT) Army Audit Agency (AAA): Conducting audits to identify efficiencies and make recommendations

to enhance implementation Director of Test & Evaluation (DOT&E): Placed COE on Oversight List

12

Questions

Contact Information:

Mr. Phillip MinorDeputy Director, COE Directorate, ASA(ALT)phillip.minor.civ@mail.mil

13

Backup

14

Migrating Programs of Record (PORs) to COE

COE v3

CE Foundation

PoR “A”FunctionalDecomposition

Common Warfighter Function 1Common Warfighter Function 2

Unique Warfighter Function 2bUnique Warfighter Function 3b

Unique Warfighter Function 1b

PoR “B” FunctionalDecomposition

Unique W

arfighterFunction 2a

Unique W

arfighterFunction 3a

Unique W

arfighterFunction 4a

Unique W

arfighterFunction 1a

Unique W

arfighterFunction 2b

Unique W

arfighterFunction 3b

Unique W

arfighterFunction 1b

Common Warfighter Function 1

Common Warfighter Function 2

Common Warfighter Function 1Common Warfighter Function 2

Unique Warfighter Function 2aUnique Warfighter Function 3aUnique Warfighter Function 4a

Unique Warfighter Function 1a

15

Cross-Cutting Capabilities – A capability needed by more than one Computing Environment

ID CCC Formal NameCCC1* Full Motion Video DisseminationCCC2 Unified VoiceCCC3 Common Track ProtocolCCC4 PKI Certificate Validation StrategyCCC5 Common AuthenticationCCC6 Common Chat MessagingCCC7 Common Overlay CCCCCC8 Sensor Alert DistributionCCC9 Assured Position/Navigation/Timing (PNT)

CCC11 Standard and Shareable Geospatial FoundationCCC13 Discovery Services for SensorsCCC14 Email ServicesCCC16 User Authentication via PasswordCCC17 Machine-to-Machine (M2M) MessagingCCC18 Shared Workspace EnvironmentCCC19 Common GUI Framework

* Reference # only – not intended to represent priority

COE TAB Approved Aug 2013In Work

Planned

16

Army and Industry Focus Services Model

• Industry typically has multiple layers of services with APIs, and SDKs for each platform type derived from a common core.

– Scaling services, workflow services, and messaging services are common, incorporated into larger services for large scale computing, databases.

– Handheld/portable services are tailored, simple versions of similar core.– Exposed interfaces are standardized beyond the vendor.

Resilience a must to avoid service outagesSource: CMU SEI

17