Transcript Slide 1

Battle Command
Migration
“Partnering Day”
15 November 05
Paul Manz
Technical Director
PM Ground Combat C2
[email protected]
Purpose
• Present an initial overview of Battle Command (BC) migration
beyond ABCS 6.4 for near and mid-term
– Define technical vision for future BC systems
– Maintain relevance of fielded ABCS systems via key
technology insertions
– Maximize ROI by leveraging today’s capabilities into
tomorrow
• Establish a system of systems perspective:
– Across all PEO C3T programs and Joint Interfaces
– Technology improvements for interoperability and integration
– Goal is life-cycle cost reduction
Provide a System of Systems Path Forward
2
Army Battle Command Systems (ABCS)
IMETS
Integrated Meteorological
Environmental Terrain System
MCS
Maneuver Control System
ABCS
Information
Server
ASAS
All-Source
Analysis System
FBCB2
Force XXI Battle
Command - Brigade
and Below
GCCS-A
Global Command
and Control
System - Army
DTSS
Digital Topographic
Support System
JTF HQS
BCS3
TAIS
Tactical Airspace
Integration System
Battle Command
Sustainment Support
System
AMDWS
Air and Missile
Defense
Workstation
AIS
Tactical Operation
Centers
A FAMILY OF SYSTEMS
AFATDS
Advanced Field
Artillery Tactical
Data System
3
Developing the ABCS 6.4 Solution
Warfighter Perspective &
User Feedback
Graphic Control Measures
(GCMs,FSCM,Capability Overlays)
“Good Enough”
69 “Good Enough”
Operational Requirements
•Display overlays on COP
•Display the following on the COP:
Friendly Locations
• Range fans and Dead Spaces
“Good Enough”
• Sensor Coverage
• FS Control Measures and targets (dynamic transition from planned to
•Division and Above
•View/Display and disseminate part of active)
the COP (Platform, unit, joint,
• Scalable Icons/ Graphics
coalition, neutral, unknowns)
• Obstacles SA and overlays
•Tailorable/ filters by task organization (GCCS-A/Apr 04)/ scalable and
• Obstacles Status (status, #, active, inactive, breach lanes)
1 up/ 2 down/ flank
•Turn On / Off Overlays as needed
•Tailorable/ filters by Geographical/ •Based
scalable
onarea
2525B (current subset)
•See 50% of all automated Blue Force
trackingMapping
systems
•Common
tool kit (currently JMTK going to CJMTK); must have
(reported every 5 min. ground and every
min.
aviation)
ability1to
exchange
between ABCS systems w/out manual translation or re•See 85% of all reported (automatic/manual)
Blue Force locations
entry of data
•Selectively aggregate/ disaggregate•Ability
by Task
organization
to have
seamless exchange of graphics and overlays between Army
•Drill down/ hierarchical displays byand
keyJoint.
leader(AFATDS,
and CP location
AMDPCS,TAIS to TBMCS currently seamless. GCCSA/C2PC graphics resolved Apr 04)
•Manual update capability
•Air Tracks (fixed wing and rotary)
•Visual alert on loss of network connectivity
•Visual indication of non reporting units (GCCS-A with work-a-round)
TSM & PM technical
feasibility review
Commander's
Need
BOS
866 Technical Supporting
Reqts derived & prioritized
Top 7
CDRr's
Need
ORD
Rqmnt
#
4.1.19.1.
1.
ORD
Requirement
Block V - Use voice through the computer.
Collaboration
Short
Name
Blk MCS
Good
# Enough
PdM
MCS
Good
Enough
TSM
System
Delta
TSM
Depen
-dency
C2
Commander's SITREPs
C2
CDRs Critical Info
Requirements (CCIR)
(Alert)
Block VI -Ability to chat both horizontally
and vertically amongst the various
automated command and control systems
on the battlefield.
4.1.19.1.
3
Block VI - Provide collaboration capability
to support dismounted forces
Collaboration
Bandwidth
Unknown
manageme
nt
MCS VI
VI
Collaboration
tool shall include
chat both
horizontally and
vertically
Bandwidth
Unknown
manageme
nt
4.1.19.1.
4
Collaboration
FRAGOs
MCS-toMCS
A
Bandwidth
Not scheduled
manageme until Block VI
nt
B
NA
ORD
Requirement
Block
#
Good
Enough
System
Delta
4.a(13)Provide common COTS system III &IV
utilities and office automation tools that
assist users in presenting and sharing
data 5.c(6) GCCS-A will be capable
of transmitting and receiving data
(using the US Message Text Format
(USMTF) and Joint Variable Message
Format (JVMF) rules and standards)
with other ABCS and Joint systems via
the Common Message Processor.
The objective data transfer method
with other C2 systems will be direct
data exchange IAW the DII COE and
the JCDB
In Blk III SITREPS can be
created and sent via e-mail. In
Blk IV, SITREPS can also be
created and distributed via
CMP.
This requirement is not specifically
addressed in the GCCS-A ORD.
There are requirements reference
alerts and providing the Commander
Intelligence
Information. (4.a(16)
Post-Jan
Incorporate and use the Defense
GCCS-A is adding the MCSLight capability to the Block IV
baseline. An alert capability is
not included and is beyond good
enough.
IV
Dependency
15-Jan Post-Jan 30 AprMessage System (DMS) for record
traffic. Rationale: Users must be
04 alerted when critical information is
x
received. Information and messages
must be processed using DoD
standard systems.
MCS-Light must make the application available for integration into the GCCS-A baseline by Nov 03.
Change in mission,
4a(1)
intent, task
KPP
organization, priorities;
available
for planning
x
on receipt and display
(textually and
graphically) on COP for
execution; requires
alert on receipt and
x
effective date/time on
all products. FRAGO
graphics are autoposted to COP display
with effective DTG
x
noted.
INTEROPERABILITY WITH JOINT,
III &IV
SERVICE AND ARMY SYSTEMS:
GCCS-A must interoperate and
exchange CTP data and satisfy critical
IERs (See Appendix F), with GCCS
and ABCS. The CTP data set
contains critical C2 and SA data
including plans and orders, friendly
and enemy unit locations and status,
deployment and resource data on
friendly units, and battlefield geometry.
Blk III uses the MCS-Light
OPORD templates to Build
Orders. These are Word
Templates that can be shared
via e-mail or web capabilities.
Blk IV will add the MCS-Light
Plan Manager application to the
GCCS-A software baseline.
Estimate of the unit's
4.a(5)
capability to complete x
the mission (current
and future) IAW METTTC (a predictive
capability tied to CCIR
x
and the DSM - allowing
rapid comparison to the
plan). Access to COA
evaluation, war gaming
and rehearsal tools.
Information
on current
x
Force Protection
measures and status.
The requirement for a running
NA
estimate is not specifically addressed
in the ORD. There is a requirement to
provide COA tools.
An automated capability is not
planned for Blk 4. Users can
utilize CCIR tracker and Sync
matrix capabilities to do manual
tracking.
MCS-Light must make the application available for integration into the GCCS-A baseline by Nov 03. GCCS-A currently only distributes 0rders as Word documents. With the VMF injector and the CMP capabilities be
Collaboration
4.1.19.1.
5
Block VI. Video-teleconferencing
capability. It is envision that VTC
capability will not be required below
Division.
4.1.21.3
Block V - Provide electronic mail capability MCS V Provide
MCS VI Provide
Video
Teleconferencin
g
VI
V
Bandwidth
Not scheduled
C2
Running Estimate
manageme until Block VI
B
nt
5 of 8 G
3 of 8 B
electronic mail.
Unknown
Collaboration
A
4.1.2.1.1
4.1.21
Summary: Send and receive
messages (includes rqmnt to send
and receive SITREPs).
N/A
IV
Commander's
SITREPs
4.1.1
Current
Enemy
Situation
Constrained
by OIF Driven
Schedules
B
A
MCS VI
VI
Collaboration
capability will be
capable of being
used on the
move
. Block VI - Allow multiple sites of up to 23 MCS VI Allow up VI
workstations to be tied in on a session,
to 23 stations to
dependent on hardware and bandwidth
simultaneously
collaborate
PIR, FFIR, and EEFI.
Commander requires
an automated alert
when the CCIR has
been met. Feeds the
Running Estimate.
TSM Comment BLK 29-Sep
MCS V Provide
V
voice over
computer
collaboration tool
C2
4.1.19.1.
2
Collaboration
ORD
Definitions
Requirement
#
Information IAW the
4a(13) &
unit SOP (normally
5.c.(6)
consisting of unit status
regarding operational
capability including
personnel, pacing item
maintenance, key items
of supply and
equipment and unit
locations)
Display the Common Operational Picture
MCS Display
(KPP1). MCS will provide the Common
COP
Operational Picture to enable commanders
to visualize the battlespace and apply
analysis, estimates, judgment and
information from other units/agencies in
order to develop situational understanding
and the commander's vision for execution
of combat operations (see FM 3-0,
Operations, pg. 5-3). MCS will provide the
Common Operational Picture to enable the
staff to monitor execution of the
commander’s battle plan, make minor
adjustments, and provide
recommendations to the commander. The
Common Operational Picture consists of,
at a minimum, the friendly
location/situation, enemy location/situation,
and combined arms graphics and overlays
(maneuver control graphics and specified
mission essential fire support coordination
measures, unit symbols, and mission
graphics).
IV,
V, VI
T:GCCS-A
& ASAS,
T/R:
FBCB2
AMDWS,
CSSCS, &
AFATDS
ORD requirement
is GE. Green to
EPLRS equipped
FBCB2, Black to
BFT.
A
1
MCS
Dependency
Display Only
Block IV
A
x
CAPES will provide the capability to do COAs, but the capability to do running estimates against the products produced by CAPES will not be part of Blk IV.
ABCS 6.4 software delivery
to system test in April ‘04
Field ABCS 6.4
across force within 48 months…
4
Current ABCS Product-Centric
System Implementation
Presentation Services
Visualization
Stovepipe
BFA user
interface
Role Based Presentation
Application Services
Others
Planning/Execution
Air Defense Planning
MVR Planning
Air Defense Control
COA & Wargaming
Tactical Logistics
Airspace Control
Rehearsal/AAR
Movement Tracking
Airspace Planning
Comms NW Planning
Logistics Planning
Fire & Effects Control
Comms NW Status
Readiness Status
NBC
Combat Power
Engineer
Maps/Overlays
Overlay Management
Symbology
BFA specific
instrastrucure
BFA specific
implementations
of common reqts
Terrain Analysis
COP/SA
Fire & Effects Planning
Internet Services
PM Intel & Effects
PM WIN-T
PM ATC
PM EIS
PM GCC2 migrating
to EIS
PM Intel & Effects
migrating to
DCGS-A
Task Organization
Training
Stovepipe BFA
implementation
of common
Requirements
Reports
L2-4 Fusion
Weather
BFA unique
applications
Infrastructure Services
PM AMDWS/ToC
PM GCC2
Data Initialization &
Loading
OPORD/PLAN
System Services
Web Server
OS/File System
Web Portal/
Collaboration Server
Info Assurance
Authentication,
Encryption
Collaboration
Auditing
Messaging &
Mediation
Pub & Sub
C2 Messaging
Email Server
Mapping
Conferencing, Chat,
Whiteboard
Storage
Map Engine
Data Model
DB/Data Store
Data Distribution
Network & Discovery
Services
Enterprise Mgmt Svc
DNS, DHCP, NTP
*User Account/
Role Manager
Directory
System Manager
Discovery
Alerts and
Notifications
*Service Registry
Failover
Independent
Infrastructure
X 10
Symbology Rendering
Stovepipe
platforms/HW,
OS and SW
environments
5
What Have We Learned?
• Disparate data formats
• Interoperability
• Utilization of Bandwidth
• Collaboration
• Difficult to configure
• Too many systems to train
• Stovepipe Design
– Different user interface for each system
– Many servers providing similar functionality
– More expensive to maintain
– Training impacts
Must leverage current capability to address these issues as
ABCS evolves toward JC2 and FCS.
6
What Happened since Good Enough?
JTCW
ABCS
“Good Enough”
C2PC
JBC-P
Joint Web
COP
DACT
FBCB2
FCS
CPoF
JC2
GCCS-A
WEEMC
Various
NCES
Horizontal
Fusion
(18th ABN &
JBFSA)
GCCS-M
Need to incorporate initiatives into ABCS. Must
maintain compatibility with ABCS 6.4.
7
Path Forward
Today
Near-Term
Future
GCCS
JC2
XXX
ABCS 6.4
+
ABCS
JC2
with
technology
insertions
XX
X
FBCB2
X
FBCB2
UA
FCS BC
JBC-P
Migration Plan under development
8
Migration Plan
Key Drivers and Goals
Army at War
Modularity
Goals
Joint
Migration Plan
ABCS
Sustainment
Team produces requirements,
architecture, and schedule
NetCentricity
• Lower lifecycle cost
• Reduce Complexity
• Smaller footprint
• Common User
Interface
• Reduced training and
cognitive burden
• Fewer soldiers
needed to
run/maintain the
System of Systems
Technology
Insertions
9
BC System Convergence Vision
Cap Block 1
In-Svc 06-09
GCCS-A
C2PC
MCS
CPOF
TAIS
AFATDS
AMDPCS
BCS3
ASAS-L
IMETS
Cap Block 2
In-Svc 08-11
Cap Block 3
In-Svc 10-13
Cap Block 4
In-Svc 12-15
Cap Block 5
Cap Block 6
JC2v5
In-Svc 14-17
In-Svc 16-19
JC2v1
JTCW
TAIS
AFATDS
AMDPCS
BCS3
ASAS-L or
DCGS-A
JC2v2
JC2v3
JC2v4
AFATDS
AMDPCS
BCS3
AFATDS
AMDPCS
BCS3
AFATDS
AMDPCS
BCS3
DCGS-A
(ISR comp.)
(ISR comp.)
DTSS
FBCB2
DTSS
JBC-P
DTSS
JBC-P
ISYSCON
ISYSCON or
WIN-T
AIS
PASS B1, IDM-T
TOC Srvr
PASS B2, IDM-T
(C2IEDM)
FCS Sp 1eval
DCGS-A
(ISR comp.)
J-GES
JBC-P
ISYSCONv4 or
WIN-T
TOC Srvr
PASS B3, IDM-T
(JC3IEDM)
(Sp 4)
DCGS-A
(ISR comp.)
J-GES
J-GES
JBC-P
WIN-T
TOC Srvr
PASS B4, IDM-T
(JBCIEDMv1)
FCS Sp 1
FCS BC
FCS Sp 2
JBC-P
WIN-T
TOC Srvr
WIN-T
PASS B5, IDM-T
(JBCIEDMv2)
TOC Srvr
PASS B5, IDM-T
(JBCIEDMv3)
FCS Sp 3
ABCS 6.4
Transition A
Transition B
Transition C
Transition D
Transition E
10
Layered Approach to
BC Software Architecture
OSI Layers
TCP/IP Layers
User-Centric Design, Common
Role-based User Interface
Application
Presentation
Application
Network
Transport
Network
Physical
Network
Access
Battle
Command
Services
Messaging, Collaboration,
Discovery, IA, Data
Dissemination, Comms
Network Management, QOS,
Real-time Services
Data Link
Presentation
Services
(HCI)
Mapping/Overlays, Planning,
Logistics, Airspace Mgmt &
Deconfliction, Attack Analysis,
Weapons Management,
Target/Effects Queuing
Session
Transport
C2 Layers
LAN, Hardware (including
servers) Routers, Hubs,
Switches, Routing Protocols
Network
Infrastructure
Services
Reduce cognitive burden by automating Battle Command
and Network Infrastructure Services.
11
BC Path Forward
Near-Term Thrusts
• Consolidation Of Servers/Services
– Reduce Server Duplication
– Centralize Servers/Service
• “C2 Bridge To The Future”
– Expose ABCS Capabilities As Services
– Leverage Middleware Services Compliant with NCES
– Positions BC Server For Transition To JC2 And FCS
Spirals
• Common Presentation Services
– Leverage CPOF HCI “Goodness”
– Role-Based User-Centric Design
12
Cleaning Up
Product-Centric Issues
Current
Near Term
• Complex
Drives the need for*:
• Duplicative Unique Stovepipes
• Consistent Acquisition Strategy & Management
Practices
• Heavy Training Burden
• Product-Centric Systems Engineering and
Acquisition
• Unified Systems Engineering and Integration
• Common Architecture, Software and Hardware
Solutions
• Usability Strategy and Solutions
13
Server Consolidation
14
Application Consolidation on
JTCW Framework
GCCS-A
Strategic
Strategic
JC2
BCS3 EIS app
BCS3
CPOF
JTCW
Tactical
BC Server
Tactical
MCS
Common
JTCW Client
ISYSCON
AFATDS unique
technical fire control
AFATDS
• Common Role-based
User Interface
AMDWS unique
• Common Hardware,
Software, and
Architecture
AD mgmt
C-RAM
AMDWS
TAIS
TAIS
• Infrastructure and
Application Service
Consolidation
TAIS unique
Airspace Mgmt
TAIS
AMPS unique
functions
AMPS
Platform
Platform
FBCB2
TIMS
JBC-P
15
What is CPOF?
$62M being
Invested by DARPA
Since 1998
CPOF
Servers
CPOF Workstation
• An executive level decision support system that provides
situational awareness and collaborative tools to support decision
making, planning, rehearsal and execution management.
• Designed to allow operators to interactively collaborate, and
share workspaces and plans.
May04 MOA Between
Army and DARPA
CPOF Network Fielded
to 1st CAV and 3ID
"We do virtually every rehearsal using the CPOF
tool." MG Peter Chiarelli
PM GC C2 Actively Working Transition To Support Apr06 Handoff
16
Objective ABCS
Service-Based Framework
Presentation Services
Visualization
Role Based Presentation
Common
User Interface
Validated by
Usability
Analysis
Application Services
Others
Planning/Execution
Air Defense Planning
MVR Planning
Air Defense Control
COA & Wargaming
Tactical Logistics
Airspace Control
Rehearsal/AAR
Movement Tracking
Airspace Planning
Comms NW Planning
Logistics Planning
Fire & Effects Control
Comms NW Status
Readiness Status
NBC
Combat Power
Engineer
Maps/Overlays
Overlay Management
Common
infrastructure &
application services
Common BFA
service & BFA
unique extensions
Shared service
provided by system
external to ABCS
Symbology
Terrain Analysis
COP/SA
Data Initialization &
Loading
OPORD/PLAN
Fire & Effects Planning
Task Organization
Training
Reports
Common
Service
Implementation
of BFA
functions
L2-4 Fusion
Weather
Limited BFA
unique
extensions
Infrastructure Services
Internet Services
System Services
Web Server
OS/File System
Web Portal/
Collaboration Server
Info Assurance
Authentication,
Encryption
Collaboration
Auditing
Messaging &
Mediation
Pub & Sub
C2 Messaging
Email Server
Mapping
Conferencing, Chat,
Whiteboard
Map Engine
Storage
Data Model
DB/Data Store
Data Distribution
Symbology Rnedering
Network & Discovery
Services
Enterprise Mgmt Svc
DNS, DHCP, NTP
*User Account/
Role Manager
Directory
System Manager
Discovery
Alerts and
Notifications
*Service Registry
Failover
Common
service based
joint
Infrastructure
Common
platforms/HW,
OS and SW
environment
hosting BFA
services
17
Where We’re Headed
• Single Authority for Battle Command Systems
Engineering
• Single Army/Marine Corps Land/Littoral C2 Solution
• Maximizing commonality of architecture and services
• Taking advantage of communications and network
infrastructure
• Incorporation of usability engineering in a common
presentation layer design
Translating BC Vision into a Viable System Architecture
Leveraging ABCS 6.4 Capabilities
18