Mr' Francis H' Carr

1
Simulation Services for ABCS 7.0 Enhancing
WarfighterCapabilities for the FuturePaper
02S-SIW-096SISO Spring 2002 Simulation
Interoperability Workshop 14 March 2002
Presented for Army Modeling and Simulation
Office (AMSO) Officer Professional Development
(OPD) December 6, 2001

• Mr. Francis H. Carr
• The MITRE CorporationSimulation - C4I
  Interoperability Overarching IPT (SIMCI OIPT)
• [phone] carr_at_mitre.org

LTC Kenneth Wilson U.S. Army Modeling and
Simulation Office [phone]
kenneth.wilson_at_hqda.army.mil
2
Overall Outline

• SIMCI Organization
• Simulation Services for ABCS Task
• ABCS Architecture
• Legacy Systems
• ABCS 6.X Overview
• Transition from 6.X to 7.0
• MS in ABCS 6.X
• Overview of ABCS 7.0 Architecture
• Simulation Services in ABCS 7.0

Legend ABCS - Army Battle Command
System SSEI - System of Systems Engineering
Integration PEO C3T Program Executive Office
Command, Control, and Communications Technology
3
SIMCI OIPTs Approach to Interoperability
Interoperability of Legacy and Future Systems
Shared Solutions
A. Processes For Alignment
E. Reusable Component Interfaces
Simulation Services for ABCS 7.0
C. Common Standards
D. Common Data/Object Models
B. Alignment of Architectures
4
SIMCI Simulation Services for ABCS 7.0

• Problem
• Interface architectures are needed
• Provide seamless interoperability between ABCS
  and MS
• SIMCI OIPT requires adequate representation on
  the ABCS 7.0 SSEI board
• Ensure SIMCI architecture in line with the ABCS
  7.0 architecture and beyond.
• Task Concept
• Develop SIMCI OIPT representation and vision on
  the ABCS 7.0 SSEI WGs
• Produce Interoperability Integration
  Requirements for ABCS 7.0 systems
• Influence ABCS 7.0 Specifications, Standards,
  Interface APIs, ultimately ABCS Components
• Develop common standards to support
  interoperability
• Examples include interface components, data
  models, data elements, and terminology (BML) to
  support data exchange among components.

5
Army Battle Command Systems (ABCS) The Big
Picture

• Commander-centered.
• Will allow the commander to clearly see
• and understand his battlespace.

Air Force
Navy
Theater Battle Mgt Control System (TBMCS)
Joint Maritime Command Info System (JMCIS)
ISYSCON
GCCS COE
DTSS
IMETS
A2C2
Tactical Combat Operation System (TCO)
Army Battle Command System (ABCS)
Platforms
ABCS
Global C2 System
AFATDS
Army
Marine Corps
AMDWS
Radios
AGCCS
MCS
FBCB2
ASAS
CSSCS
Legend ABCS - Army Battle Command
System AFATDS - Advanced Field Artillery Tactical
Data System AGCCS- Army Global Command and
Control System AMDWS - Air Missile Defense
Workstation ASAS - All Source Analysis
System CSSCS - Combat Service Support Control
System DTSS - Digital Topographic Support
System FBCB2 - Force XXI Battle Command --
Brigade and Below GCCS - Global Command and
Control System IMETS - Integrated Meteorological
System ISYSCON - Integrated Systems Control MCS -
Maneuver Control System
Common
SATCOM
Base Operations
Telemedicine
Simulations
Sensors
UAV
6
Evolution of ABCS 6.X (Feb 00)

• Integrated EBC in TOC server allows direct
  exchange of SA with CTP- Increases
  Synchronization
• BFAs Terrain Evaluation Mapping functionality
  moved to CTP on JMTK - Increases Consistency
• FBCB2s on TI able to communicate directly with
  BFAs on LAN in TOC - Increases
  Interoperability/Mobility

TOC
SA
CTP
USMTF/DMS EMail
Unicast and Multicast JVMF
FBCB2
BFA X
BFA Y

• Common Products
• TOC Server with EBC
• Common Look Feel
• CTP/JCDB/SR
• BFA Applications

• Common Products
• TOC Server with EBC
• Common Look Feel
• CTP/JCDB/SR
• BFA Applications

Important Step in the Spiral to move BFA
applications to common products/build TOC server
7
Notional C4I - Sim Architecture
Simulation(s) Network
C4I System(s) Network
Military Service Messages (USMTF, JVMF, OTH-Gold)
Simulation Protocol Interactions (DIS, ALSP, HLA)
Database Updates (JCDB, TDBM)
Simulation Communications Mechanisms DIS
Distributed Interactive Simulation Protocol ALSP
Aggregate Level Simulation Protocol HLA High
Level Architecture
8
ABCS 7.0 Design Tenets

• There will be a separate, dedicated TOC Server to
  simplify the administration of the Command Post.
• The architecture will have a web-based approach
  to allow for laptops to join the TOC, and leave
  and join again.
• Provide wireless LAN capability to provide more
  dynamic operations.
• Plan for the introduction of Gapfiller based
  SATCOM capabilities.
• Simplifying Situational Awareness data
  distribution approach using IP-based network
• Plan for the introduction of WIN-T
  capabilities.

9
Summary

• To in ABCS 7.0
• Dedicated central TOC Server with back-up for
  COOP
• Central database with back-up for COOP
• IP Compliant Multicast SA
• XML based data distribution
• Light Client support engineered into the
  architecture

• From in ABCS 6.2
• Any BFA as server
• Weak, non-central database
• Multiple database updates
• CPU intensive EBC pushed SA non-standard
  architecture
• Light clients with limited server support

ABCS 7 is Evolutionary not revolutionary
10
Notional ABCS 7.0 Architecture
TOC Server
Enterprise Information Services
Legacy
Missing BFA, Products, JCDB Mirroring, and State
Other Information Servers
IM
Business Logic
CTP
Application Server Container
Transport Services
Live Feed
multicast
User Application
JCDB Access
XML
. . .
. . .
. . .
CMP
ABCS 6.X
State
TDDM
User Application
COMM
Policy
FBCB2
EBC
JCDB
Web Container
User Application
http
DMS
HTML XML
Common Support Services
GBS
Windows
Directory services, Distributed Computing,
Messaging
Solaris
Note EBC may be replaced, no longer desired
by PM FBCB2 in 7.0 Not exhaustive list
11
ABCS Past, Present, and Future
Centralized Model ABCS TOC Server
provides common services
ABCS 6.2
ABCS 7.0
Inter-TOC Network
BAS
BAS
Light Client
Common Svcs
Common Svcs
Inter-TOC Network
BAS
TOC Server
BAS
BAS
BAS
Peer-2-Peer Model Everyone is a server
BAS
Common Svcs
BAS
Common Svcs
BAS
Common Svcs
Light Client
Component Model TOC Server hosts the BAS
Components
ABCS 8.0
Integrated Model Server hosts integrated BAS
Systems
ABCS 9.0 (FCS)
Inter-TOC Network
Inter-TOC Network
BAS
Server
BAS
TOCServer
BAS
BAS
BAS
BAS
BAS
BAS
BAS
BAS
Light Client
Light Client
Light Client
Light Client
Light Client
Light Client
12
Potential Interface Migration
Simulation Protocol Interactions (DIS, ALSP, HLA)
ABCS 7.0
C4I Sim Interface
Inter-TOC Network
Light Client
BAS
TOC Server
BAS
BAS
Potential Interface Implementations
BAS
Light Client
13
Background for ABCS Foundation Products
Requirements
Army COE Foundation Products
Interfaces ETSIU Enhanced Tactical Simulation
Interface Unit DLRC Digitized Leadership
Reaction Course RTM Run Time Manager DCM Data
Collection Manager EPIU Enhanced Protocol
Interface Unit Foundation Products CMP Common
Message Processor C2R Command Control
Registry JCDB Joint Common Database JMTK Joint
Mapping Toolkit
Legacy Interfaces
14
Input to ABCS 7.0 System Software Specification

• Data Initialization and Maintenance
• User Interface Integration
• Technical Documentation
• Multiple Instances
• Expanded Data Repository APIs
• Data Dissemination of Simulated Data

ABCS MS Interface Requirement Categories

• Request for Input Oct 2001
• 11 Document Change Requests Returned
• 33 Additional Proposed Requirements, 3
  Overarching Comments
• Considers Legacy Experiences, Current
  Capabilities, Future Needs

15
Data Initialization and Maintenance

• Substantial Time and Resource to Synchronize
• E.g. UTO, UOB, resource amounts, locations,
  Orders
• Problem Shared by ABCS Systems
• PEO C3T established Repository of ABCS Data
  (ROAD) Working Group
• Solve the urgent 6.X data products problem now
• Begin development of simulation
  interfaces--integrated solution for training and
  real-world missions

• Risks (based on Current Draft Proposal)
• May rely on TI, NIPRNET, SIPRNET connections
• Scope not to include BAS specific loads (only
  part of JCDB)
• Exercise/Training needs rapid, repeatable,
  configurable loads

16
User Interface Integration

• ABCS Interface modification constrained
• Dont do it, or we dont want to train with it.
• Training requires special components
• User Interaction with Simulations
• Battle Management Language (BML)
• Data Collection Tools
• After-Action Review, Training Assessment

17
Multiple Instances

• Key ABCS Components only support single Instances
• CTP/JMTK, Overlay Manager, UOB Tool
• Limits Reuse of Core Foundation Products
• MS Contributions of Tactical Decision Aids
  (TDAs)
• Introduction of Thin Client Architecture
• Not Consistent Across Services
• DMSO Sponsored work with Course of Action (COA)
  application
• NRL developed, JTLS Federation, COE COP based

18
Data Dissemination

• Basic Capability to Exchange Data between MS
  ABCS
• Requirements ensure capabilities remain
• Introduce use of Simulated data to Live
  databases
• Potential impact to future COA tool development
• Protect against impact of Profiles,
  Publish/Subscribe
• Compel Architecture that considers MS Interfaces

19
Summary

• Actively participating in ABCS Future Design
  Dev.
• Participating in SSEI Foundation Products
  activities
• Provided working set of Input Requirements
• Will continue to evolve with ABCS Architecture
• MS Requirements need consideration
• Integration into all areas of OA/SA/TA
• Future MS Interfaces may differ in Architecture
• Will rely on core Common Software components

20
Backup Slides
21
C4I - Sim Architecture

• Message Based
• Peer to Peer (or Hierarchical) Messaging
• Significant Translation
• Limited Information
• Database (JCDB/TDBM) Updates
• TOC to TOC Transactions
• Limited Translation
• Order Processing
• Major Translation
• Limited MS Responsiveness

22
The Problem
Interoperability Necessary for Army Transformation
Full Interoperability is unattainable without
common solutions for...

• Reasons to link Simulations-to-C4I
• Train as you fight!
• Embedded Training (individual collective)
• Course of Action Analysis
• Mission Planning / Rehearsal
• Operational AAR
• SMART

23
DUSA(OR) DISC4 Integration of Army MS and
C4I Systems Memo

Create an
IPT

co-chaired by the Project Manager,
C4I Simulation Systems and a Chief, Readiness
and Engineering, Program Executive Office for
Command, Control, and Communications

Systems
that will focus on
improving Simulation-to-C4I
Integration
by folding
common C4I components
into
the interfaces that link simulations and C4I
systems,
as well as
how best to
align the data models
used

by the MS and C4I communities.

1 November 1999
PM C4I Simulation Systems was renamed PM
Simulation Technology Integration in August 1999
24
SIMCI Overarching IPT (OIPT) Organization Chart,
including POCs
As of 14 Jan 2002
TEMO
OIPT Co-Chairs
STRICOM PM STI
PEO-C3S REO
ACR
DCSPRO DOI
TRAC
Mr. Dick Koval
LTC Michael Landers
RDA
TPIO STE
ERDC TEC
AMSO
Mr. Michael Tavares
Mr. Ernest Vanhoose
SIMCI OIPT Primary Membership
ALL
Mr. Bruce Uphoff
LTC Ken Wilson
AMSO SCC
TPIO TD
New
Mr. Bruce Uphoff
Mr. Frank Hugelman
TPIO ABCS
TRADOC DCSSA
Ms. Tonya McCree,
ATEC
Mr. Matt Arnold
Mr. Steve Chizmar
Mr. Bob Halle
Council of Architects
Mr. Dick Brown
TRADOC DCSCD
DISC4
PEO STAMIS
Ms. Sara Wilson
CECOM RDEC
PEO IEWS
Working Groups
ATSC
Dr. Michael Hieb, AMSO/DISC4 Architect Mr. Bill
Sudnikovich, CECOM Architect Mr. Steve Whitson,
CTSF Architect Mr. Ron Sprinkle, STRICOM
Architect
Ms. Leslie Winters
MAJ Jim Blalock
Mr. Chandu Sheth
Mr. Paul Howe
Mr. Michael Ryan
Signal Center
COE Consortium
Future Research Initiatives
Business Model / Certification
TBD
Requirements Synchronization
Mr. Stephen Whitson, MITRE
Dr. Michael Hieb, AB Technologies
Mr. Dick Brown, TPIO ABCS
Mr. Thomas Kelso, PM STI
25
Simulation-to-C4I Interoperability (SIMCI) OIPT
Charter

• MISSION
• Provide recommendations on Army level policy to
  the AMSEC for improving interoperability between
  the Models and Simulations (MS) and Command,
  Control, Communications, Computers, and
  Intelligence (C4I) Domains.
• OBJECTIVES
• Seamless interoperability between MS and C4I
  systems.
• Alignment of MS and C4I standards,
  architectures, and common C4I components.
• Identification of requirements for simulations
  and C4I to support interoperability
• IPT MEMBERS
• Co-Chairs STRICOM, PM STI PEO-C3S, Chief of
  Readiness Engineering

Charter
Signed in
May 2000
By ODUSA-OR ODISC4
AMSAA AMSO Army MS C4I Integration
SCC ATEC CECOM RDEC (RDA) DOI (formerly ADO)
DISC4 PEO Aviation PEO-GCSS PEO-IEWS PEO-STAMIS SM
DC
TPIO-ABCS TPIO-STE (TEMO) TPIO-TD TRAC TRADOC
DCSCD (ACR)
IPT Secretary - PM STI
26
ABCS 6.0 Support of Operational Concepts

• Execution/Operational Tempo
• Consistent CTP across BFAs/echelons allow
  adapting to emerging conditions
• Digital Map Distribution
• Operational Flexibility
• Allows UTO Changes
• Automated address assignment within
  pre-determined nodes
• Preplanning organization changes BN above
• Flexible company level assignment
• Commanders Intent
• Interoperability between BVTC and Collaborative
  tools
• Whiteboard, Chat, Audio
• Planning COAs
• Common Look and Feel
• Standard Symbology
• CDR Filter Common Tactical Picture (CTP)
• Detailed Icons Slant Reports

27
The Elements of ABCS
Commanders Primary Battle Command Tools
Supporting Software/Modules
GCCS
Strategic
Interoperable with Joint and Combined Systems
AGCCS
Operational
A B C S
IMETS
Tactical
TAIS
ISYSCON
Legend ABCS - Army Battle Command
System AFATDS - Advanced Field Artillery Tactical
Data System AGCCS- Army Global Command and
Control System AMDWS - Air Missile Defense
Workstation ASAS - All Source Analysis
System CSSCS - Combat Service Support Control
System DTSS - Digital Topographic Support
System FBCB2 - Force XXI Battle Command --
Brigade and Below GCCS - Global Command and
Control System ICS3 - Integrated Combat Service
Support System IMETS - Integrated Meteorological
System ISYSCON - Integrated Systems Control MCS -
Maneuver Control System TAIS - Tactical Airspace
Integration System TI - Tactical Internet
DTSS
MCS
ASAS
AMDWS
CSSCS
AFATDS
TI
FBCB2
Communications (Warfighter Information Network -
Tactical (WIN-T))
(ICS3)
28
ABCS 7.0 Composition

• Extend ABCS Capabilities
• Through
• Optional Web-based Interfaces
• (IDM-T, COTS)

EXTENSIONS
Technology Insertion

• Improve Initialization, Administration, Data
  Distribution, Operability, Stability, and
  Performance

Fix ABCS 6.2 Problems, Enhance Performance,
Improve Reliability
IMPROVEMENT
BASELINE
Achieve Affordability By Minimizing Impact to
BFAs
Retain Current ABCS 6.2 Capabilities And
Interfaces while porting ABCS to more affordable
COTS Hardware and Software
29
ABCS 7.0 Design Goals - Baseline

• Preserve existing client software interfaces
  (e.g. API specifications) to the extent possible
• Provide Joint and Intra-Army message level
  interoperability with ABCS 6.2 TOCs

30
ABCS 7.0 Design Goals - Improvements

• Provide a separate, dedicated TOC Server
• Reduce complexity, memory, hard drive and
  processing requirements of BAS systems by
  eliminating the need for a BAS to assume the TOC
  Server Function
• Migration path to an integrated BAS architecture
• Exploit COTS server technology to provide dual
  independent TOC Server and BAS functionality in a
  small form factor
• Provide better support for the ABCS Light
  platforms
• Provide data communication via web enabling
  technology (XML, URL)
• Allows a user with a laptop or other light client
  to enter a TOC, plug in, download and upload
  information, perform operations leave and
  re-enter in the same or different TOC
• Laptop technology is a smaller form factor,
  easily deployed, with internal batteries for
  improved operational availability

31
ABCS 7.0 Design Goals - Improvements

• Engineer in versioning to support forward
  interoperability -An updated message Header is a
  key capability
• Provide wireless LAN capability
• Improve data dissemination process of the
  OPORD/OPLAN throughout the architecture to
  provide
• Formatting, matrices, and all the attributes of
  features
• Large Size (Greater than 6000 characters per
  annex)
• Associate overlays to orders
• Revision and recovery scheme
• Introduce a new data radio capability (EPLRS
  V11,Mode4) to provide over a 200 increase in
  data rate and supports a larger force structure.

32
ABCS 7.0 Design Goals - Extensions

• Make Situational Awareness Architecture IP
  Compliant in the Lower Tactical Internet
• improved operational flexibility
• eliminate INC agents and hundreds of SA servers
  to configure
• provides multi-point SA capability ( entity
  information)
• no fire areas, minefields, NBC contamination
  areas, ..
• Enhanced Security Capability includes
• TOC servers will be issued certificates
• Clients can verify authenticity of TOC Server
• Servers can authenticate each other
• Simplify training and improve operational
  flexibility by eliminating the requirement to
  deploy a Signal Corps operated Network Control
  Station.

33
Interface Implementation Options

• Option 1 TOC Server Peer
• XML based Message DB Transactions (?)
• Process Acknowledge TOC status protocol msgs
• Rik Cost of TOC Server HW, SW Licenses

• Option 2 BAS Client
• Message based transactions DB Transactions (?)
• Process Acknowledge BAS Client status protocol
  msgs
• Rik Cost of BAS Client HW, SW Licenses
• Risk Impact of User Profile on Publish/Subscribe

• Option 3 Light Client
• Message based transactions DB Transactions (?)
• Process Acknowledge Light Client status
  protocol msgs
• Risk Impact of User Profile on Publish/Subscribe