JC3IEDM

Last updated

JC3IEDM, or Joint Consultation, Command and Control Information Exchange Data Model is a model that, when implemented, aims to enable the interoperability of systems and projects required to share Command and Control (C2) information. JC3IEDM 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).

Contents

The Joint C3 Information Exchange Data Model

JC3IEDM is produced by the MIP-NATO Management Board (MNMB) and ratified under NATO STANAG 5525. [1] JC3IEDM a fully documented standard for an information exchange data model for the sharing of C2 information.

The overall aim of JC3IEDM is to enable "international interoperability of C2 information systems at all levels from corps to battalion (or lowest appropriate level) in order to support multinational (including NATO), combined and joint operations and the advancement of digitisation in the international arena." [2]

According to JC3IEDM's documentation, [3] this aim is attempted to be achieved by "specifying the minimum set of data that needs to be exchanged in coalition or multinational operations. Each nation, agency or community of interest is free to expand its own data dictionary to accommodate its additional information exchange requirements with the understanding that the added specifications will be valid only for the participating nation, agency or community of interest. Any addition that is deemed to be of general interest may be submitted as a change proposal within the configuration control process to be considered for inclusion in the next version of 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.

  1. The structure should be sufficiently generic to accommodate joint, land, sea, and air environmental concerns.
  2. 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.
  3. 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).
  4. 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.
  5. 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.
  6. Several aspects of status of items need to be maintained.
  7. 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.
  8. The model must reflect information about what is held, owned or possessed in terms of types by a specific object item.
  9. 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.
  10. The model must support the specification of current, past, and future role of objects as part of plans, orders, and events.
  11. The same data structure should be used to record information for all objects, regardless of their hostility status.
  12. 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."

JC3IEDM development history and current maturity

JC3IEDM has been developed from the initial Generic Hub (GH) Data Model, which changed its name to Land C2 Information Exchange Data Model (LC2IEDM) in 1999. Development of the model continued in a Joint context and in November 2003 the C2 Information Exchange Data Model (C2IEDM) Edition 6.1 was released. Additional development to this model, incorporating the NATO Corporate Reference model, resulted in the model changing its name again to JC3IEDM with JC3IEDM Ed 0.5 being issued in December 2004.

Subsequent releases have seen areas of the model developed in greater depth than others and there is variation in the number of sub-types and attributes for each type in the current version. An example is HARBOUR within the FACILITY type which has 43 attributes compared to a VESSEL-TYPE with 12 attributes or a WEAPON-TYPE with 4 attributes. The associated attributes of a certain type also lack support for exploiting with those of other types. For example, VESSEL-TYPE does not support the length or width of a vessel in its attributes but HARBOUR has both maximum vessel length and width attributes.

The UK Ministry of Defence has mandated JC3IEDM as the C2 Information Exchange Model, in Joint Service Publication (JSP) 602:1007, for use on all systems and/or projects exchanging C2 information within and interoperating with the Land Environment at a Strategic and Operational Level. It is strongly recommended for other environments and mandated for all environments at the Tactical level. [4] JSP 602:1005 for Collaborative Services has also mandated JC3IEDM in the tactical domain for all systems/projects providing data sharing collaborative services. [5]

Related Research Articles

Joint Interoperability of Tactical Command and Control Systems or JINTACCS is a United States military program for the development and maintenance of tactical information exchange configuration items (CIs) and operational procedures. It was originated to ensure that the command and control and weapons systems of all US military services and NATO forces would be interoperable.

Configuration management process for maintaining consistency of a product attributes with its design

Configuration management (CM) is a systems engineering process for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its life. The CM process is widely used by military engineering organizations to manage changes throughout the system lifecycle of complex systems, such as weapon systems, military vehicles, and information systems. Outside the military, the CM process is also used with IT service management as defined by ITIL, and with other domain models in the civil engineering and other industrial engineering segments such as roads, bridges, canals, dams, and buildings.

Defense Information Systems Agency United States Department of Defense combat support agency providing information technology and communications support

The Defense Information Systems Agency (DISA), known as the Defense Communications Agency (DCA) until 1991, is a United States Department of Defense (DoD) combat support agency composed of military, federal civilians, and contractors. DISA provides information technology (IT) and communications support to the President, Vice President, Secretary of Defense, the military services, the combatant commands, and any individual or system contributing to the defense of the United States.

Data model abstract model for organizing data; abstract model that organizes elements of data and standardizes how they relate to one another and to properties of the real world entities

A data model is an abstract model that organizes elements of data and standardizes how they relate to one another and to the properties of real-world entities. For instance, a data model may specify that the data element representing a car be composed of a number of other elements which, in turn, represent the color and size of the car and define its owner.

In NATO, a Standardization Agreement defines processes, procedures, terms, and conditions for common military or technical procedures or equipment between the member countries of the alliance. Each NATO state ratifies a STANAG and implements it within their own military. The purpose is to provide common operational and administrative procedures and logistics, so one member nation's military may use the stores and support of another member's military. STANAGs also form the basis for technical interoperability between a wide variety of communication and information systems (CIS) essential for NATO and Allied operations. The Allied Data Publication 34 (ADatP-34) NATO Interoperability Standards and Profiles which is covered by STANAG 5524, maintains a catalogue of relevant information and communication technology standards.

The High Level Architecture (HLA) is a standard for distributed simulation, used when building a simulation for a larger purpose by combining (federating) several simulations. The standard was developed in the 90’s under the leadership of the US Department of Defense and was later transitioned to become an open international IEEE standard. It is a recommended standard within NATO through STANAG 4603. Today the HLA is used in a number of domains including defense and security and civilian applications.

IEC 62056 is a set of standards for electricity metering data exchange by International Electrotechnical Commission.

Department of Defense Architecture Framework

The Department of Defense Architecture Framework (DoDAF) is an architecture framework for the United States Department of Defense (DoD) that provides visualization infrastructure for specific stakeholders concerns through viewpoints organized by various views. These views are artifacts for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through tabular, structural, behavioral, ontological, pictorial, temporal, graphical, probabilistic, or alternative conceptual means.

The Data Distribution Service (DDS) for real-time systems is an Object Management Group (OMG) machine-to-machine standard that aims to enable dependable, high-performance, interoperable, real-time, scalable data exchanges using a publish–subscribe pattern.

XML Information Set is a W3C specification describing an abstract data model of an XML document in terms of a set of information items. The definitions in the XML Information Set specification are meant to be used in other specifications that need to refer to the information in a well-formed XML document.

The IDEAS Group is the International Defence Enterprise Architecture Specification for exchange Group. The deliverable of the project is a data exchange format for military Enterprise Architectures. The scope is four nation and covers MODAF (UK), DoDAF (USA), DNDAF (Canada) and the Australian Defence Architecture Framework (AUSDAF). The initial scope for exchange is the architectural data required to support coalition operations planning -

ANSI/ISA-95, or ISA-95 as it is more commonly referred, is an international standard from the International Society of Automation for developing an automated interface between enterprise and control systems. This standard has been developed for global manufacturers. It was developed to be applied in all industries, and in all sorts of processes, like batch processes, continuous and repetitive processes.

CEN ISO/IEEE 11073 Health informatics - Medical / health device communication standards enable communication between medical, health care and wellness devices and with external computer systems. They provide automatic and detailed electronic data capture of client-related and vital signs information, and of device operational data.

Multilateral Interoperability Programme Multilateral Interoperability Programme (MIP)

The Multilateral Interoperability Programme (MIP) is an effort to deliver an assured capability for interoperability of information to support multinational, combined and joint operations. The MIP goal is to support all levels from corps to battalion. MIP's focus is on command and control systems. MIP is a consortium of 29 NATO and Non-NATO nations that meet quarterly to define interoperability specifications for the exchange information between their national Command and Control systems.


IEC 60870 part 6 is one of the IEC 60870 set of standards which define systems used for telecontrol in electrical engineering and power system automation applications. The IEC Technical Committee 57 have developed part 6 to provide a communication profile for sending basic telecontrol messages between two systems which is compatible with ISO standards and ITU-T recommendations.

The Simulation Interoperability Standards Organization (SISO) is an organization dedicated to the promotion of modeling and simulation interoperability and reuse for the benefit of diverse modeling and simulation communities, including developers, procurers, and users, worldwide.

Requirements Interchange Format XML file format used to exchange requirements and associated metadata between software tools from different vendors

RIF/ReqIF is an XML file format that can be used to exchange requirements, along with its associated metadata, between software tools from different vendors. The requirements exchange format also defines a workflow for transmitting the status of requirements between partners. Although developed in the automotive industry, ReqIF is suitable for lossless exchange of requirements in any industry.

ISO/IEC 19788Information technology – Learning, education and training – Metadata for learning resources is a multi-part standard prepared by subcommittee SC36 of the Joint Technical Committee ISO/IEC JTC1, Information Technology for Learning, Education and Training. This committee was created to deal with the consequences of substantial overlap in areas of standardization done at the International Organization for Standardization (ISO) and the International Electrotechnical Commission.

J2EE Management Specification is a Java specification request (JSR-77) for standardization of J2EE server management. The J2EE Management Specification abstracts the manageable parts of the J2EE architecture and defines an interface for accessing management information. This helps system administrators integrate J2EE servers into a system management environment and also helps application developers create their own management tools from scratch.

Federated Mission Networking

Federated Mission Networking (FMN) is a significant initiative to help ensure interoperability and operational effectiveness of the North Atlantic Treaty Organization, it is a key contribution to the Connected Forces Initiative, helping Allied and Partner forces to better communicate, train and operate together. This includes the NATO Command Structure as well as the NATO Force Structure. The purpose of FMN is ultimately to support Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) and decision-making in operations by enabling a rapid instantiation of mission networks.

References

  1. ↑ MIP. "'True' JC3IEDM ratified as NATO STANAG 5255". MIP. Retrieved 2009-03-11.
  2. ↑ MIP. "'True' MULTILATERAL INTEROPERABILITY PROGRAMME NATO DATA ADMINISTRATION GROUP MEMORANDUM OF AGREEMENT" (PDF). MIP. Archived from the original (PDF) on 2011-07-23. Retrieved 2009-03-11.
  3. ↑ MIP. "'True' JC3IEDM-Main-GBR-DMWG-Edition_3.1b_2007-12-13" (PDF). MIP. Archived from the original (PDF) on June 21, 2015. Retrieved 2009-03-11.
  4. ↑ MOD. "'True' JSP 602 1007 Database Services" (PDF). MOD. Retrieved 2009-03-11.
  5. ↑ MOD. "'True' JSP 602 1005 Collaborative Services" (PDF). MOD. Retrieved 2009-03-11.

Note: Link for Ref 3 is broken. Link for Ref 5 is wrong. As of 05.05.2017 all MIP links are broken and point to different directions.

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.