Common Operating Environment, Interoperability, and Command Post - - PowerPoint PPT Presentation

common operating environment interoperability
SMART_READER_LITE
LIVE PREVIEW

Common Operating Environment, Interoperability, and Command Post - - PowerPoint PPT Presentation

Common Operating Environment, Interoperability, and Command Post Modernization (LOEs 2, 3, and 4) 1 CSAs Principles, Characteristics and Requir and R equiremen ements ts Warfighting Technical Network Characteristics of the Principles


slide-1
SLIDE 1

1

Common Operating Environment, Interoperability, and Command Post Modernization (LOEs 2, 3, and 4)

slide-2
SLIDE 2

CSA’s Principles, Characteristics and R and Requir equiremen ements ts

Principles (Why) Warfighting Requirements Characteristics of the Network Technical Network Requirements

Mission: TheArmy must fight and win wars against adversaries… 1st Principles: The Army network must enable:

  • 1. Conduct of War: Execution
  • f expeditionary, world-wide,

Unified Land Operations (ULO) to shape, prevent, and win as a part of UnifiedAction in all domains and all environments (Note 1/2/3/4)

  • 2. Preparation for War:

Execution of Title 10 responsibilities to man, train, and equip the force, and to build and sustain readiness.  Able to fight, shoot, move, communicate, protect, and sustain  Reliably communicate anywhere, anytime, in all domains, in all environments, against any foe  Simple and Intuitive, single mission command suite (Single COP), installed,

  • perated and maintained by

Soldiers  Available, Reliable and Resilient with the ability to

  • perate in all operational

environments against any enemy  Expeditionary and Mobile, voice, data, and video on the move  Standards-based, protected, and dynamic network that is upgradeable over time  Enables the Warfighter to Observe, orient, decide, and act faster than the enemy in the conduct of ULO (Note 4)  Enables use of the network as a weapon system  Enables leaders to lead and fight their formations from anywhere they choose  Must be capable of adequate secure communications, provides voice, data, video in all environments  Capable of providing situational awareness down to Platoon level  Device works anywhere in the world; installed, operated and maintained by Soldiers  Standardized: Runs on a COE, common graphics, applications, and integrated data  Ensures continuous Joint interoperability enabling agile and adaptable operational flexibility  i.e., Enables Rapid T ask Organization and employment

  • f joint capabilities

 Mitigates electronic signature  Accessible to allies and coalition partners

Note 4: ULO – Simultaneous offense, defense, and stability or defense support of civil authorities tasks to seize, retain, and exploit the initiative and consolidate gains to prevent conflict, shape the operational environment and win our nations wars as part of unified action Note 1: Unified Actions Partners – Consisting of Joint, Interagency, Intergovernmental, and Multi- National (JIIM) partners Note 2: Domains – Land, maritime, air, space, cyber Note 3: Environments – Permissive, non- permissive, contested, denied

slide-3
SLIDE 3

Etc… TAIS GCCS-A AMPS AMDWS

  • Different User Interfaces
  • Different Maps
  • Different Training
  • Different Hardware

DCGS-A AFATDS JBC-P CMD WEB TIGR

Missio Mission n Comman Command d Systems Systems

CPOF

Current

  • Common User Interface
  • Single Shareable Geospatial

Foundation

  • Transferable Training
  • Common Hardware

Future

WfF Apps

slide-4
SLIDE 4

CPCE will provide an intuitive user experience for Movement and Maneuver Applications while setting conditions for additional Warfighting Functions to converge from stovepipped systems to integrated applications.

INDUSTRY MODEL

In your pocket On the road In the office/home

INDUSTRY MODEL APPLIED TO ARMY

Dismounted Mounted Command Post

Applications owned developing companies but reside on computing devices Applications developed by original PEOs, but reside on CPCE/MCE

From disparate SW & HW platform s To common SW onto common HW devices

Common Common Oper Operating En ting Envir vironment

  • nment

(COE) (COE)

slide-5
SLIDE 5

5

Hosts COE Applications Expeditionary Agile Scalable Integrated Designs Reduced Footprint Mobile Energy Efficient Formation Appropriate Survivable Future CP Characteristics Current Program of Record Unit Initiatives

Comman Command d Post

  • st Impr

Improvemen ements ts

CPI2 Objective

slide-6
SLIDE 6

UNCLASSIFIED

The Multiple he Multiple Lay Layer ers s to to Inter Interoper

  • perability

bility Challenges Challenges

Integrated Compatible Deconflicted

Large Scale Combat Operations (LSCO) Crisis Response/Limited Contingency

  • Mil. Engagement/Security Coop./Deterrence

Theater Army Division Battalion Brigade Corps Mission Command Intelligence Movement & Maneuver Fires Protection Sustainment Joint  USAF  USMC  USN  SOF Allies/Parnters/Others  ABCANZ  ROK  NATO  Others Inter-Org  USG IA  MN GOV  HN GOV  NGOs

Network enabled full interoperability Effective interaction and complimentary processes Aligned capabilities and procedures, no interaction

Priorities? Non-negotiable Areas? Forcing Functions?

At Echelons? Across the Range of Military Operations (ROMO) Interoperability across the various Warfighting Functions? ABCANZ goal is an integrated 2-star HQ for LSCO NLT 2020 Top Secret Secret SEC//REL Secure UNCLASS Unclassified

At what level is the information protected?

Types of Partners? Levels of Interoperability

2

slide-7
SLIDE 7

UNCLASSIFIED

7

Path F th Forw

  • rwar

ard

WFX 18.4 JWA 18.1 USAREUR Saber Strike All things Pacific JWA 19.1 Army, Joint, Combined Exercises

 MPE Digital COP  MPE Core Services  Digital Fires  ISR/Intel Fusion  Secure Tactical Voice  Key Sustainment Capabilities Cross Functional Teams

Integrated Compatible Deconflicted Determining Levels of Interoperability (Prioritized 1-N List)  MC Interoperability White Paper  Interoperability Proponency  Governance/Framework  Full DOTMLPF-P Analysis CONUS MPE Digital Fires Secure Tactical Voice Key Sustainment Capabilities CTC Rotations Informs longer term efforts Objectives Decision Drivers Key Interoperability Opportunity Events (Campaign of Learning) ISR/Intelligence Fusion All things Pacific

slide-8
SLIDE 8

Start with Software Development Kits (SDK), they describe:

  • CPCE/MCE architecture and components for infrastructure, core utilities and MC
  • applications. Data strategy and the ways to extend it.
  • The strategy to achieve common look and feel with specific examples.
  • How 3rd party developers can work convergence including Data Architecture, User

Interface, Geospatial and HW perspective.

  • Command Post solutions in support of CSA principles, characteristics, and requirements.
  • Interoperability solutions that increase Unified Partner access to Mission Command

Systems.

Ho How Indu w Industr stry y Can Can Par articipa ticipate te