Figure 2 Approved for public release; distribution is unlimited.
Related Figures (47)
Figure 2. Concept of Information Transfer envisioned by the software developers at the Institute for Defense Analysis (IDA) (From Simaitis, 2004). The C2IEDM models command and control information that combined areas and multiple views of the requirements. Toward that end, it lays down a igure 3. Core Kernel of C2IEDM containing OBJECT-TYPE, OBJECT-ITEM and OBJECT-ITEM-TYPE constructs. (From Johnson, 2004). Figure 4. High level view of the C2IEDM model showing the many to many relationships between the different entities of the model (From Johnson, 2004). OBJECT-TYPE relational tree found in the C2IEDM (From Johnson, 2004). Extended C2IEDM showing the CRBN event (From Johnson, 2004). CRBN-EVENT construct of Extended C2IEDM showing additional detail (From Johnson, 2004). Expansion of several nodes of the CRBN C2IEDM extension (From Johnson, 2004). Pictorial representation of the XBML Testbed (From Heib, 2003). 211. OpenMap™ screen shot from TOPTIVA which uses the C2IEDM data model. Steps in MDA development Process (From Kleppe and others, 2003). the MDA process but it is considered by the OMG to be a model since | ranracante machine langage. Since the OMG stated that code is itself a model, all of the data modeling structure to text documents which makes them well defined. However, XML is The UOB Toolset Components (From Cipparone and Hopkins, 2003) interface depicted in Figure 15, which allows users to retrieve and browse unit and maintaining the data. The data access tool features a graphical user Figure 16. Pictorial representation of part of the UOB Data Model (From Cipparone and Hopkins, 2003). Example enumeration used to specifically define what is allowed within the Unit LevelCode element of the AdministrativeUnitiInformation element. manner. The following is provided to enhance the understanding of the table Table of Correspondences between UOB and C2TEDM After reviewing the schema governing the result document, the XSLT ure 23. Main template used within the XSLT to extract unit information from the C2IEDM. allows them to be passed into other templates. Resource construct found in UOB schema. to the U.S Navy, Air Force, Marines and Coast Guard. The expanded personnel information included in the target VOB schema Expanded Personnel element found in UOB schema. HOLDING construct found within the C2IEDM. PersonnelHoldings template from C2IEDM to UOB XSLT. 129. PersonnelTemplate template called within the PersonnelHoldings template from C2IEDM to UOB XSLT. Equipment construct found in UOB schema version 7.7. Aircraft-Type, etc. Figure 32 shows the MATERIEL-TYPE structure found in the C2IEDM. OBJECT-TYPE/MATERIEL-TYPE construct in C2IEDM. Further subdivisions Equipment-type-category-—code construct found in the C2IEDM. Land-weapon-type-category-—code construct found in the C2IEDM. e 42. The expanded organization-type-category-code found within the ORGANISATION-TYPE structure from the BIXS. Partial tree structure of ORGANISATION-TYPE showing MILORG government-organisation-type-category-code from BIXS. Figure 44. Partial tree structure showing UNIT military-organisation-type- category-code inside of the MILITARY-ORGAINISATION-TYPE element of the C2IEDM. 16. | UNIT-TYPE structure found in the BIXS containing both the unit- type-category-code and the unit-type-size-code. The unit-type-category-code structure found in the BIXS containing the unit description information. Partial template used to extract the unit LevelCode necessary for the UOB result document. done if the unit is being assigned a mission that it was not originally designed for Figure 49. Partial unit-type-size-code structure found within the C2IEDM used to obtain the unit Level Code for the UOB compliant result document. information is extracted and the result document is complete. shows the partial tree structure encompassing the unit-type-size-code ‘e 50. | DMSO’s vision of future interoperability using C2IEDM (From Chaum and others, 2004) ‘Holy Grail” to fix all of the interoperability difficulties within the DoD would be a
