A C2IEDM Based Approach to C4I and Simulation Initialization and Synchronization 05FSIW068

1
A C2IEDM Based Approach to C4I and
SimulationInitialization and Synchronization05F-
SIW-068

• Bruce W. Carlton
• Gary J. Farmer
• Roy O. Scrudder
• Applied Research Laboratories
• The University of Texas in Austin
• 10000 Burnet Road
• Austin, TX 78758
• 512-835-3120, 512-835-3481,512-835-3857
• bcarlton_at_arlut.utexas.edu, farmer_at_arlut.utexas.edu
  , scrudder_at_arlut.utexas.edu

2
Objective

• Over the next 20-25 minutes, explain the main
  points of our paper in an effort to motivate you
  to read the details in the paper itself.

3
Agenda

• Introduction- Simulation and C4I Data
  Interoperability
• Army C4I and Simulation Initialization System
  (ACSIS)
• JWARS-GCCS Course of Action (COA) Execution
  Monitoring and Alert System project
• Mapping ACSIS Data Elements to the C2IEDM
• ACSIS-C2IEDM Mappings for Army UOB Data
• ACSIS-C2IEDM Mappings for Army, Joint, Equipment
  and Logistics Materiel Data
• ACSIS ABCS Network Data Element Extensions to the
  C2IEDM
• Conclusions

4
Simulation and C4I Data Interoperability

• Todays operational environment across the Joint,
  Interagency, and Multinational (JIM) communities
  consists of many disparate C4I, Modeling and
  Simulation (MS), and reference databases.
• In many cases, these disparate databases use
  different semantics, syntax, and naming
  conventions for the same or similar data element.
  These systems also use many different data file
  formats (ASCII text, binary, etc.) and database
  formats (Oracle, MySQL, DB2, Imformix, etc.)
• The Net-Centric Data Strategy, including the
  development of data standards, standard
  information exchange data models, and data
  mediation services implemented within the
  GIG/NCES environment, will be the key to
  achieving data interoperability.

Data Interoperability is the key to System
Interoperability
5
Categories of Initialization Data

• Unit Order of Battle (UOB) data
• Electronic Order of Battle (EOB) data
• Geospatial, Environmental, Terrain data
• Intelligence data
• Facilities and Infrastructure data
• Characteristic and Performance (CP) data
• Weapon Effects Data
• Doctrine and Tactics, Techniques, and Procedures
  (TTPs) data
• Human Behavior and Performance data
• Battle Management data

6
C2 Information Exchange Data Model
The C2IEDM developed by warfighters to meet
their information needs and configuration
managed by the Multilateral Interoperability
Program (MIP).

• C2IEDM is first and foremost a foundation for C2
  information exchange.
• Since information exchange requirements (IERs)
  change over time, there was a need to design a
  flexible generic model that could adapt over time
  to changing information needs.
• Defines the standard elements of information
  (data) that form the basis for interoperability
  between those automated C2 Information Systems
  (C2ISs) that accommodate the model's information
  structure.
• The C2IEDM is a neutral language with XML tags
  already in the DoD XML Registry upon which a
  standard C2 data interchange format (DIF) has
  been built.

7
Army C4I and Simulation Initialization System
(ACSIS)
8
Army C4I and Simulation Initialization System
Reference Data Sources
Today, the ACSIS Database includes the Unit Order
of Battle (UOB) and the Electronic Order of
Battle (EOB) initialization data that is common
to both Army C4I systems and simulations.

• DMSOs ACSIS Authoritative Data Source Update
  Process (AADS-UP)
• Provides and updates UOB and MTOE data to the
  ACSIS DB from DoD reference data sources.

• ACSIS Tool Suite
• Builds operational and exercise-specific Unit
  Task Organizations (UTO).
• Extracts ACSIS data and generates additional
  network configuration and addressing data.
• Identifies and fixes data integrity problems.
• Produces accurate and synchronized C4I and
  Simulation Initialization data products from a
  single data set based on a mission-specific UTO.

9
JWARS-GCCS COAMonitoring and Alert System
GIG
TDBM (Tracks)
C4I
TDBM Server
TDBM Monitor
TBMCS (ATO)
Situation Monitor
C4I Gateway
TBMCS Server
TBMCS Monitor
GIG
ACSIS DBMS
Web Registry
GIG
ACSIS Service
JWARS
JWARS
10
Development of an ACSIS-C2IEDM Integrated Data
Model

• JWARS team conveyed their initialization data
  requirements to the ACSIS team by designating the
  appropriate C2IEDM entities and attributes, or
  extensions to the C2IEDM, for which ACSIS would
  be required to provide data.
• The ACSIS team then mapped the appropriate ACSIS
  data elements to these designated C2IEDM data
  elements.
• Added 33 C2IEDM entities and 8 database views to
  the ACSIS database schema to support Joint
  material and to facilitate ACSIS-to-C2IEDM
  mappings.
• The result was an integrated ACSIS-C2IEDM data
  model that could be used by the ACSIS Web Service
  to select the appropriate data from the ACSIS
  database, perform any necessary translations, and
  generate a C2IEDM XML SOAP data message to
  provide initialization data to JWARS for an
  exercise-specific UTO.

11
ACSIS Web Service
Interface Tier
Web service with SOAP C2IEDM based XML data
messaging using Document Literal Encoding. UDDI
server with registered ACSIS Web Service.
Business Logic Tier

• Select appropriate data from the database
• Filter by UTO, filter out lower echelon units,
  etc.
• Data set is transferred to an XML document that,
  through an XSLT transform, generates a string
  with XML data compliant to the IDA C2IEDM XML
  schema.

Data Tier
ACSIS Database (Oracle 9i) ACSIS-C2IEDM
integrated database schema
12
ACSIS for Unit Task Organization (UTO)
13
C2IEDM for Unit Task Organization (UTO)
OBJECT-ITEM
object-item-id object-item-name ..
ORGANIZATION
organization-id organization-nickname-name ..
ORGANIZATION-STRUCTURE
UNIT
organization-structure-root-organization-id organi
zation-structure-index ..
unit-id unit-formal-abbreviated-name
ORGANIZATION-STRUCTURE-DETAIL
OBJECT-ITEM-ASSOCIATION
organization-structure-root-organization-id organi
zation-structure-index organization-structure-deta
il-index object-item-association-subject-object-it
em-id object-item-association-object-object-item-i
d object-item-association-index
object-item-association-subject-object-item-id obj
ect-item-association-object-object-item-id object-
item-association-index object-item-association-cat
egory-code object-item-association-subcategory-cod
e ..
14
ACSIS for Materiel
MATITEM_HOLDINGS
MATERIEL
MAT_ITEM (TYPE)
MAT_ITM_INDX ORG_EwID UTO_INDX UTO_VERSION MATIHLD
NG_QTY MATIHLDNG_OPL_QTY MATITM_AUTH_QTY ..
MATERIEL_ID PARENT_MATERIEL_ID ORG_EwID UTO_INDX U
TO_VERSION MAT_ITM_INDX MATERIEL_TYPE (P or E) ..
MAT_ITM_INDX MATITM_NAME MATITEM_SUP_CLASS MATITM_
CAT_CD LIN_ID NSN ..
PLATFORM
EQUIPMENT
PLATFORM_ID PLATFORM_NM PLATFORM_TYPE_ID ..
EQUIPMENT_ID EQUIPMENT_TYPE
NOTIONAL_ORG
ORG_EwID ORG_NAME ..
15
C2IEDM for Materiel
HOLDING
object-item-id object-type-id holding-index holdin
g-operational-quantity holding-total-quantity repo
rting-data-id
OBJECT-TYPE
OBJECT-ITEM
object-type-id object-type-name object-type-catego
ry-code ..
object-item-id object-item-name ..
OBJECT-ITEM-TYPE
object-item-id object-item-name ..
MATERIEL-TYPE
MATERIEL
materiel-type-id materiel-type-reportable-item-tex
t materiel-type-category-code materiel-type-stock-
number-text materiel-type-supply-class-code ..
materiel-id materiel-serial-number-text ..
CONSUMABLE-MATERIEL-TYPE
EQUIPMENT-TYPE
consumable-materiel-type-id consumable-materiel-ty
pe-category-code consumable-materiel-type-subcateg
ory-code ..
equipment-type-id equipment-type-category-code ..
16
Mappings and Translations of Legacy Database
Schemas to the C2IEDM

• Step 1. One-to-one semantic mapping to C2IEDM
  core code attribute domain values
  (enumerations) perform syntax translation.
• Step 2. Add domain values to C2IEDM core domain
  value set (enumerations).
• Step 3. One-to-one semantic mapping to C2IEDM
  core attributes perform syntax translation.
• Step 4. Add an attribute to an existing C2IEDM
  core entity.
• Step 5. Add an entity with attributes to the
  core C2IEDM.

C2IEDM v6.1 194 Entities 785 Attributes 264
code Attributes with a domain value set. (33)
17
C2IEDMmateriel-type-supply-class-codedomain
values
18
ACSIS MATITEM_SUP_CLASS
19
ACSIS MATITEM_SUP_CLASS (cont.)
20
C2IEDM Networkwith ABCS network extensions
OBJECT-ITEM
OBJECT-ITEM-ADDRESS
ADDRESS
object-item-id object-item-name object-item-catego
ry-code ..
object-item-id address-id object-item-address-inde
x object-item-address-call-sign-text ..
address-id address-category-code address-place-nam
e-text
FACILITY
ELECTRONIC-ADDRESS
NETWORK-SERVICE
facility-id facility-category-code ..
address-id electronic-address-name network-id netw
ork-service-index electronic-address-type-code
network-id network-service-index network-service-c
ategory-code network-service-subcategory-code
NETWORK
BC GROUP MC GROUP SUBNET EPLRS SINCGARS NTDR SAT U
HF HF JTR NCS
network-id network-category-code network-subcatego
ry-code network-architecture-code network-abcs-typ
e-code ..
URN IP ADDRESS NETMASK EMAIL ADDRESS EPLRS RSID
21
Conclusions

• During the JWARS-GCCS project the ACSIS team
  found that the core C2IEDM was sufficient to
  accommodate UOB initialization data, including
  organization, materiel, and logistical data.
• The core C2IEDM is not difficult to map to or
  extend when necessary.
• ABCS network data element extensions.
• Web services requires agreements on standards and
  protocols.
• SOAP XML message encoding technique used, such as
  Document Literal, or Remote Procedure Call
  Literal, or others.
• Exchange of large amounts of data with SOAP XML
  messaging will require highly-efficient
  compression technologies.
• As more Army, Joint, and Coalition C4ISR systems
  adopt the C2IEDM or JC3IEDM, C4ISR systems with
  integrated or embedded models and simulations
  (MS) will begin to migrate their legacy database
  schemas to the C2IEDM standard and less data
  translation and mediation will be required. New
  system database designs should include the
  standard at their inception.