1. Battle Command Migration
“Partnering Day”
15 November 05
Paul Manz
Technical Director
PM Ground Combat C2

2. Provide a System of Systems Path Forward
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

3. Army Battle Command Systems (ABCS)
IMETS
Integrated Meteorological
Environmental Terrain System
MCS
Maneuver Control System
AIS
ABCS Information Server
FBCB2
Force XXI Battle
Command - Brigade
and Below
ASAS
All-Source
Analysis System
GCCS-A
Global Command
and Control
System - Army
DTSS
Digital Topographic
Support System
JTF HQS
BCS3
Battle Command Sustainment Support System
TAIS
Tactical Airspace
Integration System
AFATDS
Advanced Field
Artillery Tactical
Data System
AMDWS
Air and Missile Defense Workstation
Tactical Operation
Centers
A FAMILY OF SYSTEMS

4. Developing the ABCS 6.4 Solution
Warfighter Perspective &
User Feedback
69 “Good Enough”
Operational Requirements
TSM & PM technical
feasibility review
866 Technical Supporting
Reqts derived & prioritized
ABCS 6.4 software delivery
to system test in April ‘04
Constrained by OIF Driven Schedules
Field ABCS 6.4
across force within 48 months…

5. Current ABCS Product-Centric System Implementation

6. 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.

7. What Happened since Good Enough?
ABCS “Good Enough”
JTCW
Joint Web COP
DACT
C2PC
JBC-P
FBCB2
FCS
CPoF
WEEMC
JC2
Various NCES
Horizontal Fusion
(18th ABN & JBFSA)
GCCS-A
GCCS-M
Need to incorporate initiatives into ABCS. Must maintain compatibility with ABCS 6.4.

8. Migration Plan under development
Path Forward
Today
Near-Term
Future
GCCS
JC2 +
ABCS
with
technology
insertions
XXX
ABCS 6.4
JC2 XX X X UA
FBCB2
FBCB2
FCS BC
JBC-P
Migration Plan under development

9. Migration Plan Key Drivers and Goals
Army at War
Modularity
Goals
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
Joint
Migration Plan
Team produces requirements,
architecture, and schedule
ABCS Sustainment
NetCentricity
Technology Insertions

10. BC System Convergence Vision
Cap Block 1
In-Svc 06-09
TAIS
Transition A
Transition B
Transition C
MCS
C2PC
AFATDS
AMDPCS
BCS3
AIS
PASS B1, IDM-T
GCCS-A
ISYSCON
Transition D
Transition E
ABCS 6.4
FBCB2
Cap Block 6
In-Svc 16-19
TOC Srvr
PASS B5, IDM-T
(JBCIEDMv3)
JC2v5
FCS BC
(Sp 4)
WIN-T
JBC-P
ASAS-L
IMETS
Cap Block 4
In-Svc 12-15
FCS Sp 2
PASS B4, IDM-T
(JBCIEDMv1)
JC2v3
DCGS-A
(ISR comp.)
Cap Block 5
In-Svc 14-17
FCS Sp 3
(JBCIEDMv2)
JC2v4
Cap Block 3
In-Svc 10-13
FCS Sp 1
PASS B3, IDM-T
(JC3IEDM)
JC2v2
ISYSCONv4 or
Cap Block 2
In-Svc 08-11
JTCW
FCS Sp 1eval
PASS B2, IDM-T
(C2IEDM)
JC2v1
ISYSCON or
ASAS-L or
CPOF
DTSS
J-GES

11. Layered Approach to BC Software Architecture
OSI Layers
TCP/IP Layers
C2 Layers
Presentation Services
User-Centric Design, Common Role-based User Interface
Application
Presentation
Session
Transport
Network
Data Link
Physical
Application
(HCI)
Mapping/Overlays, Planning, Logistics, Airspace Mgmt & Deconfliction, Attack Analysis, Weapons Management, Target/Effects Queuing
Battle Command Services
Transport
Messaging, Collaboration, Discovery, IA, Data Dissemination, Comms
Network
Network Infrastructure Services
Network Management, QOS, Real-time Services
Network Access
LAN, Hardware (including servers) Routers, Hubs, Switches, Routing Protocols
Reduce cognitive burden by automating Battle Command and Network Infrastructure Services.

12. 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
Bottom Line
Users are burdened with too many (in terms of quality) and too varied (in terms of construction and operation) BC machines and supporting information services.
Simplification is the key to enhancing today’s system is better integration, better interoperability and reduced administration and management burden.
Architecture simplification is a must to achieve this goal.
Consolidation of Server/Services
The Consolidation of Server/Services is at the heart of simplification.
Servers/Services refer to both physical boxes and software capabilities.
Bridge to the future
The architectural paradigm needed is one where our enterprise and system architectures are equivalent to that of our forces architecture (i.e., “Modularity”).
Viewing our systems in terms of services, versus BFA or BOS, put us onto the road of architecture “Modularity”.
A service oriented view is in line with
Current software industry direction,
NCES future direction, and
The most architecture tenets of FCS
The stated direction of the JC2 program, which is a big driver.

13. Cleaning Up Product-Centric Issues
Current
Near Term
Complex
Duplicative Unique Stovepipes
Heavy Training Burden
Product-Centric Systems Engineering and Acquisition
Drives the need for*:
Consistent Acquisition Strategy & Management Practices
Unified Systems Engineering and Integration
Common Architecture, Software and Hardware Solutions
Usability Strategy and Solutions

14. Server Consolidation

15. Application Consolidation on JTCW Framework
Strategic
GCCS-A
Strategic
Application/injector
JC2
BCS3 EIS app
BCS3
Application/injector
CPOF
Application/injector
Tactical
JTCW
Tactical
BC Server
Application/injector
MCS
Common
JTCW Client
Application/injector
ISYSCON
Application/injector
AFATDS unique technical fire control
AFATDS
Application/injector
Common Role-based User Interface
Common Hardware, Software, and Architecture
Infrastructure and Application Service Consolidation
Application/injector
AMDWS unique
AD mgmt
C-RAM
Single core Joint baseline for Strategic, Tactical and Platform levels
Validated by architectural assessment to ensure scaleability, supportability, ability to meet quality attributes
Capitalizes on best of breed solutions built on a common framework
Consolidation of duplicative services across the architecture with distribution based on performance requirements
Establishment of managed process at SoS and product level to measure progress via metrics, architectural documentation, etc.
Usability focus early on
AMDWS
TAIS
TAIS
TAIS unique
Airspace Mgmt
TAIS
AMPS unique
functions
AMPS
Platform
Platform
FBCB2
TIMS
JBC-P

16. 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.
CPOF Network Fielded
to 1st CAV and 3ID
May04 MOA Between
Army and DARPA
"We do virtually every rehearsal using the CPOF
tool." MG Peter Chiarelli
PM GC C2 Actively Working Transition To Support Apr06 Handoff

17. Objective ABCS Service-Based Framework

18. 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