The Army C4IM

1
The Army C4I-MS Reference Object Model (C-ROM)
Phase I Development

• Dr. Brian A. Haugh
• Dr. Francisco Loaiza
• Dr. Richard Morton
• Dr. Steven P. Wartik
• Institute for Defense Analysesbhaugh_at_ida.org,
  floaiza_at_ida.org, morton_at_ida.org, swartik_at_ida.org

2
Outline

• Introduction
• C-ROM UML Model
• Mappings from JCDB to C-ROM
• C-ROM Modeling Issues
• Summary

3
Introduction C-ROM Requirements

• Facilitates C4I-MS Data Interoperation sharing
  data seamlessly
• Minimizes translation costs and errors
• Promotes reuse of software components
• Aligns to the Joint Common Data Base (JCDB)
• Applicable to Joint Combined/Coalition Forces
• Supports embedded simulation capability in future
  C2 systems
• In the Unified Modeling Language (UML) format

4
Introduction C-ROM Phases

• Phase I (1st Year) Organization and Material
• Phase II (2nd Year) Features, Facilities and
  Persons may be delayed due to funding
• Phase III (3rd Year) Planning and Battle
  Management Language (BML)

5
Introduction C-ROM Products

• Reference Object Model
• Rational Rose UML model w/ classes, attributes,
  and relationships in class diagrams
• Reference Set of Codes
• Single set of values for all the
  enumerated/coded attributes in the C-ROM,
• Mappings
• From the JCDB Data Model into the C-ROM
• From the LC2IEDM into the C-ROM
• Data Dictionary

6
Outline

• Introduction
• C-ROM UML Model
• Mappings from JCDB to C-ROM
• C-ROM Modeling Issues
• Summary

7
C-ROM UML Model - packages

• HighLevelClasses Object ObjectType classes
  top-level hierarchy and associations
• Materiel equipment and consumables
• Organization military and civilian
• Capability e.g., mobility, fires, mission
• EnemyObjects required by the JCDB
• Location - e.g. points, areas of Unit locations
• OtherModelAreas for later phases.

8
C-ROM HighLevelClasses
Object First-Level Hierarchy Class Diagram
Subclass attributes suppressed
9
ObjectType First-Level Hierarchy
Subclass attributes suppressed
10
Holdings of ObjectTypes by Objects
Class attributes suppressed
11
Object-Object Associations
All attributes suppressed
12
Establishments
All attributes suppressed
13
Establishments
All attributes suppressed
14
Establishments
All attributes suppressed
15
C-ROM OrganizationType Hierarchy
Subclass attributes suppressed
16
GovernmentOrganizationType
17
MilitaryOrganizationType
18
OrganizationHierarchy
Subclassesincluded for symmetry have no
attributes
19
MilitaryOrganization
Classes included for symmetry have no attributes
20
C-ROM MaterielType Hierarchy
Subclass attributes suppressed
21
EquipmentType Hierarchy
Subclass attributes suppressed
22
PlatformType Hierarchy
Subclass attributes suppressed
23
EquipmentType Attributes
24
Materiel Hierarchy
Equipment attributes suppressed
25
Equipment Hierarchy
Subclassesincluded for symmetry have no
attributes
26
Platform Hierarchy Attributes
27
C-ROM Capability
All attributes suppressed
28
Outline

• Introduction
• C-ROM UML Model
• Mappings from JCDB to C-ROM
• C-ROM Modeling Issues
• Summary

29
Mappings from JCDB to C-ROM

• Entity Mappings
• Identify corresponding C-ROM entities
• Attribute Mappings
• Identify principal corresponding attribute
• Code Mappings
• Identify principal corresponding code values
• Identify other attribute values as required

30
Entity Attribute Mappings
31
Coded Domain Mappings
JDM Entity ORGANIZATION-MATERIEL Maps to Object
and ObjectAssociation. JDM Attribute association
type code Maps to ObjectAssociation.categoryCode.
32
Outline

• Introduction
• C-ROM UML Model
• Mappings from JCDB to C-ROM
• C-ROM Modeling Issues
• Summary

33
C-ROM Modeling Issues

• Enemy Object Attributes
• Where to place these JCDB specific attributes?
• Association Modeling
• Subclassing or Combined Associations?
• Explicit Association Attributes or Operations?
• Source Annotations stereotypes for sources
• Parallel Type Item Hierarchies
• Physical Entity Attributes - where should these
  be placed?
• Platforms - modeled as a type of equipment

34
Outline

• Introduction
• C-ROM UML Model
• Mappings from JCDB to C-ROM
• C-ROM Modeling Issues
• Summary

35
Summary

• C4I-MS needs improved interoperability
• C-ROM - a basis for future data interoperability
• Draft Phase I C-ROM - under final review
• Covers areas of Materiel and Organization
• Includes NATO and ABCS (JCDB) requirements
• Includes relevant RPR FOM platform elements
• Community input is essential - for C-ROM WG
  contact Monica Stapleton at CECOMmstapleton_at_mitr
  e.org
• Final products will be posted on SIMCI website
  https//simci.army.mil