JC3IEDM

JC3IEDM, or Joint Command, Control and Consultation Information Exchange Data Model is an evolution of the C2IEDM standard that includes joint operational concepts, just as the Land Command and Control Information Exchange Data Model (LC2IEDM) was extended to become C2IEDM. The program is managed by the Multilateral Interoperability Programme (MIP).

THE JOINT C3 INFORMATION EXCHANGE DATA MODEL

The document specifying the Joint C3 Information Exchange Data Model, produced by the MIP-NATO Management Board (MNMB), documents the JC3IEDM specification, its purpose, its history, and related information. It can be used with citation to the MNMB.

According to the JC3IEDM Main document: "The overall goal is to specify the minimum set of data that needs to beexchanged in coalition or multinational operations. Each nation, agency or community ofinterest is free to expand its own data dictionary to accommodate its additionalinformation exchange requirements with the understanding that the added specificationswill be valid only for the participating nation, agency or community of interest. Anyaddition that is deemed to be of general interest may be submitted as a change proposalwithin the configuration control process to be considered for inclusion in the next versionof the specification."

"JC3IEDM is intended to represent the core of the data identified for exchange across multiple functional areas and multiple views of the requirements. Toward that end, it lays down a common approach to describing the information to be exchanged in a command and control (C2) environment.
# The structure should be sufficiently generic to accommodate joint, land, sea, and air environmental concerns.
# The data model describes all objects of interest in the sphere of operations, e.g., organizations, persons, equipment, facilities, geographic features, weather phenomena, and military control measures such as boundaries.
# Objects of interest may be generic in terms of a class or a type and specific in terms of an individually identified item. All object items must be classified as being of some type (e.g. a specific tank that is identified by serial number WS62105B is an item of type "Challenger" that is a heavy UK main battle tank).
# An object must have the capability to perform a function or to achieve an end. Thus, a description of capability is needed to give meaning to the value of objects in the sphere of operations.
# It should be possible to assign a location to any item in the sphere of operations. In addition, various geometric shapes need to be represented in order to allow commanders to plan, direct, and monitor operations. Examples include boundaries, corridors, restricted areas, minefields, and any other control measures needed by commanders and their staffs.
# Several aspects of status of items need to be maintained.
# The model must permit a description of the composition of a type object in terms of other type objects. Such concepts include tables of organizations, equipment, or personnel.
# The model must reflect information about what is held, owned or possessed in terms of types by a specific object item.
# There is a need to record relationships between pairs of items. Key among these is the specification of unit task organizations and orders of battle.
# The model must support the specification of current, past, and future role of objects as part of plans, orders, and events.
# The same data structure should be used to record information for all objects, regardless of their hostility status.
# Provision must be made for the identification of sources of information, the effective and reporting times, and an indication of the validity of the data."

External links

* [http://www.mip-site.org/035_Public_Organ_DMWG.htm MIP site: Data Modelling Working Group]
* [http://www.mip-site.org/publicsite/04-Baseline_3.0/JC3IEDM-Joint_C3_Information_Exchange_Data_Model/ Files comprising the JC3IEDM specification]
* [http://www.mip-site.org/publicsite/04-Baseline_3.0/JC3IEDM-Joint_C3_Information_Exchange_Data_Model/HTML-Browser/index.html HTML version of the JC3IEDM specification]