battle command migration “partnering day” 15 november 05 paul manz technical director pm ground...
TRANSCRIPT
Battle Command Migration
Battle Command Migration
“Partnering Day”15 November 05
Paul ManzTechnical Director
PM Ground Combat [email protected]
2
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)
Tactical OperationCenters
GCCS-AGlobal Command
and ControlSystem - Army
FBCB2Force XXI Battle
Command - Brigadeand Below
DTSSDigital Topographic
Support System
MCSManeuver Control System
BCS3Battle Command
Sustainment SupportSystem
AMDWSAir and Missile
Defense Workstation
ASASAll-Source
Analysis System
TAISTactical Airspace
Integration System
AFATDSAdvanced FieldArtillery Tactical
Data System
IMETSIntegrated Meteorological
Environmental Terrain System
JTF HQS
A FAMILY OF SYSTEMS
AISABCS
Information Server
4
BOSCommander's
NeedDefinitions
ORDRequirement
#
ORDRequirement
Block#
GoodEnough
SystemDelta
Dependency
C2 Commander's SITREPs Information IAW the unit SOP (normally consisting of unit status regarding operational capability including personnel, pacing item maintenance, key items of supply and equipment and unit locations)
4a(13) & 5.c.(6)
4.a(13)Provide common COTS system 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
III &IV In Blk III SITREPS can be created and sent via e-mail. In Blk IV, SITREPS can also be created and distributed via CMP.
C2 CDRs Critical Info Requirements (CCIR) (Alert)
PIR, FFIR, and EEFI. Commander requires an automated alert when the CCIR has been met. Feeds the Running Estimate.
NA 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) Incorporate and use the Defense Message System (DMS) for record traffic. Rationale: Users must be alerted when critical information is received. Information and messages must be processed using DoD standard systems.
IV GCCS-A is adding the MCS-Light capability to the Block IV baseline. An alert capability is not included and is beyond good enough.
MCS-Light must make the application available for integration into the GCCS-A baseline by Nov 03. C2 FRAGOs Change in mission,
intent, task organization, priorities; available for planning on receipt and display (textually and graphically) on COP for execution; requires alert on receipt and effective date/time on all products. FRAGO graphics are auto-posted to COP display with effective DTG noted.
4a(1) KPP
INTEROPERABILITY WITH JOINT, 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.
III &IV 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.
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 being added in Blk IV FRAGOs can be sent either ina USMTK or JVMF format. C2 Running Estimate Estimate of the unit's
capability to complete the mission (current and future) IAW METT-TC (a predictive capability tied to CCIR and the DSM - allowing rapid comparison to the plan). Access to COA evaluation, war gaming and rehearsal tools. Information on current Force Protection measures and status.
4.a(5) The requirement for a running estimate is not specifically addressed in the ORD. There is a requirement to provide COA tools.
NA An automated capability is not planned for Blk 4. Users can utilize CCIR tracker and Sync matrix capabilities to do manual tracking.
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.
Developing the ABCS 6.4 Solution
Warfighter Perspective & User Feedback
Warfighter Perspective & User Feedback
69 “Good Enough”
Operational Requirements
69 “Good Enough”
Operational Requirements
TSM & PM technical feasibility review
TSM & PM technical feasibility review
866 Technical Supporting Reqts derived & prioritized
ABCS 6.4 software delivery to system test in April ‘04
ABCS 6.4 software delivery to system test in April ‘04
30 Apr 04
Top 7CDRr'sNeed
ORDRqmnt
#
ORDRequirement
ShortName
Blk#
MCSGood
Enough
PdMMCSGood
Enough
TSM System
Delta
TSM Depen-dency
TSM Comment BLK 29-Sep 15-Jan Post-Jan
Post-Jan
Collaboration
4.1.19.1.1.
Block V - Use voice through the computer. MCS V Provide voice over computer collaboration tool
V Bandwidth management
Unknown
B x
Collaboration
4.1.19.1.2
Block VI -Ability to chat both horizontally and vertically amongst the various automated command and control systems on the battlefield.
MCS VI Collaboration tool shall include chat both horizontally and vertically
VI Bandwidth management
Unknown
A x
Collaboration
4.1.19.1.3
Block VI - Provide collaboration capability to support dismounted forces
MCS VI Collaboration capability will be capable of being used on the move
VI MCS-to-MCS
A x
Collaboration
4.1.19.1.4
. Block VI - Allow multiple sites of up to 23 workstations to be tied in on a session, dependent on hardware and bandwidth
MCS VI Allow up to 23 stations to simultaneously collaborate
VI Bandwidth management
Not scheduled until Block VI
B x
Collaboration
4.1.19.1.5
Block VI. Video-teleconferencing capability. It is envision that VTC capability will not be required below Division.
MCS VI Provide Video Teleconferencing
VI Bandwidth management
Not scheduled until Block VI
B x
Collaboration
4.1.21.3 Block V - Provide electronic mail capability MCS V Provide electronic mail.
V 5 of 8 G3 of 8 B
Unknown
A x
Commander's SITREPs
4.1.2.1.1
4.1.21
Summary: Send and receive messages (includes rqmnt to send and receive SITREPs).
N/A IV T:GCCS-A & ASAS, T/R: FBCB2 AMDWS, CSSCS, & AFATDS
ORD requirement is GE. Green to EPLRS equipped FBCB2, Black to BFT.
A x
Current Enemy
Situation
4.1.1 Display the Common Operational Picture (KPP1). MCS will provide the Common 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).
MCS Display COP
IV, V, VI
1MCS DependencyDisplay OnlyBlock IV
A x
Field ABCS 6.4 across force within 48 months…
“Good Enough”•Display overlays on COP•Display the following on the COP:
• Range fans and Dead Spaces• Sensor Coverage• FS Control Measures and targets (dynamic transition from planned to active)• Scalable Icons/ Graphics• Obstacles SA and overlays• Obstacles Status (status, #, active, inactive, breach lanes)
•Turn On / Off Overlays as needed•Based on 2525B (current subset)•Common Mapping tool kit (currently JMTK going to CJMTK); must have ability to exchange between ABCS systems w/out manual translation or re-entry of data•Ability to have seamless exchange of graphics and overlays between Army and Joint. (AFATDS, AMDPCS,TAIS to TBMCS currently seamless. GCCS-A/C2PC graphics resolved Apr 04)
Graphic Control Measures Graphic Control Measures ((GCMs,FSCM,CapabilityGCMs,FSCM,Capability Overlays)Overlays)
“Good Enough”
•Division and Above•View/Display and disseminate part of the COP (Platform, unit, joint, coalition, neutral, unknowns) •Tailorable/ filters by task organization (GCCS-A/Apr 04)/ scalable and1 up/ 2 down/ flank•Tailorable/ filters by Geographical/ scalable area•See 50% of all automated Blue Force tracking systems(reported every 5 min. ground and every 1 min. aviation)•See 85% of all reported (automatic/manual) Blue Force locations•Selectively aggregate/ disaggregate by Task organization•Drill down/ hierarchical displays by key leader and CP location•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)
Friendly Locations Friendly Locations
Constrained by OIF Driven Schedules
5
Current ABCS Product-Centric System Implementation
DiscoveryEmail Server
Web Server
Web Portal/Collaboration Server Directory
DNS, DHCP, NTPOS/File System
Conferencing, Chat, Whiteboard
Auditing
*User Account/Role Manager
Pub & Sub
*Service Registry
Authentication, Encryption
Internet Services Network & DiscoveryServicesSystem Services
Data Model
DB/Data Store
Storage
Messaging & Mediation
Info Assurance
Collaboration
Enterprise Mgmt Svc
Alerts andNotifications
System Manager
Data Distribution
Mapping
Map Engine
Symbology Rendering
Failover
C2 Messaging
COP/SA
Overlay Management
Terrain Analysis
Symbology
Maps/Overlays
Fire & Effects Planning
Fire & Effects Control
Airspace Planning
Airspace Control
Air Defense Planning
Air Defense Control
Task Organization
Comms NW Planning
Comms NW Status
COA & Wargaming
Rehearsal/AAR
MVR Planning
Planning/Execution
NBC
Weather
EngineerCombat Power
Readiness Status
Logistics Planning
Tactical Logistics
Others
L2-4 FusionMovement Tracking
Reports
Training
Data Initialization &Loading
OPORD/PLAN
Visualization Role Based Presentation
Presentation Services
BFA specific instrastrucure
BFA specific implementationsof common reqts
PM AMDWS/ToC
PM Intel & Effects
PM GCC2
PM WIN-T
PM ATC
PM GCC2 migrating to EIS
PM Intel & Effects migrating to DCGS-A
PM EIS
BFA specific instrastrucureBFA specific instrastrucure
BFA specific implementationsof common reqts
BFA specific implementationsof common reqts
PM AMDWS/ToCPM AMDWS/ToC
PM Intel & EffectsPM Intel & Effects
PM GCC2PM GCC2
PM WIN-TPM WIN-T
PM ATCPM ATC
PM GCC2 migrating to EIS
PM Intel & Effects migrating to DCGS-A
PM EIS
Independent
Infrastructure
X 10
Stovepipe BFA implementation
of common Requirements
BFA unique applications
Stovepipe BFA user interface
Stovepipe platforms/HW,
OS and SW environments
Application Services
Infrastructure Services
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
DACTC2PC
GCCS-M
JC2
What Happened since Good Enough?
JTCW
CPoF
GCCS-A
ABCS“Good Enough”
Joint WebCOP
FCS
WEEMC
FBCB2JBC-P
Horizontal Fusion
(18th ABN & JBFSA)
VariousNCES
Need to incorporate initiatives into ABCS. Must maintain compatibility with ABCS 6.4.
8
Path Forward Today Future
GCCS
ABCS 6.4
ABCS 6.4
FBCB2
JC2
FCS BC
JBC-P
XXX
XX
X UA
Near-Term
FBCB2
X
JC2+
ABCSwith
technology insertions
Migration Plan under development
9
Migration Plan Key Drivers and Goals
Migration Plan
ModularityArmy at War
Joint
ABCS Sustainment
Technology Insertions
NetCentricity
Team produces requirements, architecture, and schedule
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
10
Cap Block 1
In-Svc 06-09
TAIS
Transition A Transition B Transition C
MCSC2PC
AFATDSAMDPCS
BCS3
AISPASS B1, IDM-T
GCCS-A
ISYSCON
Transition D
Transition E
ABCS 6.4
FBCB2
Cap Block 6
In-Svc 16-19
TOC SrvrPASS B5, IDM-T
(JBCIEDMv3)
JC2v5
FCS BC (Sp 4)
WIN-T
JBC-P
ASAS-LIMETS
Cap Block 4
In-Svc 12-15
FCS Sp 2
AFATDSAMDPCS
BCS3
TOC SrvrPASS B4, IDM-T
(JBCIEDMv1)
JC2v3
WIN-T
JBC-P
DCGS-A(ISR comp.)
Cap Block 5
In-Svc 14-17
FCS Sp 3
AFATDSAMDPCS
BCS3
TOC SrvrPASS B5, IDM-T
(JBCIEDMv2)
JC2v4
WIN-T
JBC-P
DCGS-A(ISR comp.)
Cap Block 3
In-Svc 10-13
FCS Sp 1
AFATDSAMDPCS
BCS3
TOC SrvrPASS B3, IDM-T
(JC3IEDM)
JC2v2
ISYSCONv4 orWIN-T
JBC-P
DCGS-A(ISR comp.)
Cap Block 2
In-Svc 08-11
JTCW
TAIS
FCS Sp 1eval
AFATDSAMDPCS
BCS3
TOC SrvrPASS B2, IDM-T
(C2IEDM)
JC2v1
ISYSCON or
WIN-T
JBC-P
DCGS-A(ISR comp.)
ASAS-L or
CPOF
DTSS DTSSDTSS J-GES J-GES J-GES
BC System Convergence Vision
11
Layered Approach to BC Software Architecture
Application
Presentation
Session
Transport
Network
Data Link
Physical
OSI Layers TCP/IP Layers C2 Layers
Application
Transport
Network
Network Access
Network Infrastructure
Services
Battle Command Services
Presentation Services
LAN, Hardware (including servers) Routers, Hubs,
Switches, Routing Protocols
Messaging, Collaboration, Discovery, IA, Data
Dissemination, Comms
Network Management, QOS, Real-time Services
Mapping/Overlays, Planning, Logistics, Airspace Mgmt &
Deconfliction, Attack Analysis, Weapons Management, Target/Effects Queuing
User-Centric Design, Common Role-based User Interface
Reduce cognitive burden by automating Battle Command and Network Infrastructure Services.
(HCI)
12
BC Path ForwardNear-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
13
Cleaning Up Product-Centric Issues
• 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
Current Near Term
14
Server Consolidation
15
Application Consolidation on JTCW Framework
GCCS-A
FBCB2 JBC-P
AMDWS
TAIS
AFATDS
MCS
BCS3
CPOF
JTCW
AFATDS unique technical fire control
AMDWS unique
AD mgmt
C-RAM
TAIS unique
Airspace Mgmt
Applicatio
n/injecto
rApplication/injector
Application/injector
Application/injector
Application/injectorBCS3 EIS appJC2
BC Server
TAISTAIS
ISYSCON
AMPS
AMPS unique
functions
Application/injector
Applic
atio
n/in
ject
or
TIMS
• Common Role-based User Interface
• Common Hardware, Software, and Architecture
• Infrastructure and Application Service Consolidation
Strategic
Tactical
Platform
Strategic
Tactical
Platform
Common JTCW Client
Applic
ation
/injec
tor
16
What is CPOF?
• 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 BetweenArmy and DARPA
CPOF Network Fielded to 1st CAV and 3ID
$62M being Invested by DARPA
Since 1998
$62M being Invested by DARPA
Since 1998
"We do virtually every rehearsal using the CPOFtool." MG Peter Chiarelli
CPOF Servers
CPOF Workstation
PM GC C2 Actively Working Transition To Support Apr06 Handoff
17
Objective ABCS Service-Based Framework
DiscoveryEmail Server
Web Server
Web Portal/Collaboration Server Directory
DNS, DHCP, NTPOS/File System
Conferencing, Chat, Whiteboard
Auditing
*User Account/Role Manager
Pub & Sub
*Service Registry
Authentication, Encryption
Internet Services Network & DiscoveryServicesSystem Services
Data Model
DB/Data Store
Storage
Messaging & Mediation
Info Assurance
Collaboration
Enterprise Mgmt Svc
Alerts andNotifications
System Manager
Data Distribution
Mapping
Map Engine
Symbology Rnedering
Failover
C2 Messaging
COP/SA
Overlay Management
Terrain Analysis
Symbology
Maps/Overlays
Fire & Effects Planning
Fire & Effects Control
Airspace Planning
Airspace Control
Air Defense Planning
Air Defense Control
Task Organization
Comms NW Planning
Comms NW Status
COA & Wargaming
Rehearsal/AAR
MVR Planning
Planning/Execution
NBC
Weather
EngineerCombat Power
Readiness Status
Logistics Planning
Tactical Logistics
Others
L2-4 FusionMovement Tracking
Reports
Training
Data Initialization &Loading
OPORD/PLAN
Visualization Role Based Presentation
Presentation Services
Common infrastructure & application services
Common infrastructure & application services
Common BFAservice & BFAunique extensions
Common BFAservice & BFAunique extensions
Shared service provided by system external to ABCS
Shared service provided by system external to ABCS
Common service based
joint Infrastructure
Common Service
Implementation of BFA
functions
Limited BFA unique
extensions
Common User Interface Validated by
Usability Analysis
Common platforms/HW,
OS and SW environment hosting BFA
services
Application Services
Infrastructure Services
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