Search

This paper describes how, through the utilization of the Ontology Definition Metamodel (ODM), a profile for expressing OWL constructs in UML, one can combine the power of semantic modeling done in OWL with the substantive advantages associated with the Model Driven Architecture (MDA) software design approach, namely, the reduction in cost and time required to update and maintain complex information models, and the improved quality of their physical implementations. Taking the Multilateral Interoperability Programme's Joint Consultation, Command and Control Information Exchange Data Model (JC3IEDM) as an example of an existing C2 specification written in an Entity Relationship (ER) modeling language, the authors present a detailed workflow that encompasses (a) a methodology for translating existing ER specifications into OWL equivalents, (b) the subsequent conversion of the resulting JC3IEDM OWL ontology into a UML model that uses the ODM profile, (c) the use of the resulting UML model as a Platform Independent Model (PIM), (d) the generation of Platform Specific Models (PSMs) via the application of Query/View/Transformation (QVT) scripts to the JC3IEDM PIM, and (e) the final generation of executable code out of the respective PSMs. The authors also highlight some of the additional benefits of migrating to OWL as the modeling language for information models, namely, the potential for leveraging the inferencing capabilities of ontology languages, as well as for formalizing rule models associated with information models.

The success of Net-Centric Operations and Warfare (NCOW) depends upon the ability of net-centric environment (NCE) users both human and automated to readily discover useful information and services. Effective discovery requires, in turn, good semantic metadata tagging (i.e., indexing the functions of the services). Good tagging reflects the contextual relationships among the discoverable artifacts. It derives its value from the soundness and intuitiveness of its underlying approach to information and services classification. Unfortunately, classification soundness is mostly in the eye of the beholder, particularly for services that can be deployed for many different purposes, and not all necessarily foreseen by their initial developers. Ultimately, therefore, what is needed for more rapid and effective tagging and discovery is a services classification approach that accommodates multiple perspectives as to what constitutes a natural and intuitive characterization, plus tools that enable NCE users to take advantage of these capabilities without being overwhelmed by the sheer multiplicity of different classification perspectives. This paper presents a proposed structure for the semantic metadata that we believe will facilitate service and information discovery in the NCE, and will easily accommodate use by intelligent agents., The original document contains color images. Presented at the Command and Control Research and Technology Symposium (2006 CCRTS) held in San Diego, CA on 20-22 Jun 2006. Published in the Proceedings of the the Command and Control Research and Technology Symposium (2006 CCRTS) Jun 2006.

This document was prepared under the Task Order Object Oriented C2 Models for the Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (C31), in support of specific requirements identified by Department of the Army, Office of the Chief Information Officer (CIO/G-6). It was performed in response to a task objective to assess the alignment of data representations between representative Army C41 and modeling and simulation (M&S) systems. Interoperability between Command Control Communications Computers and Intelligence (C41) and Modeling and Simulation (M&S) systems is one of the greatest challenges to the M&S community today. Simulations are a cost-effective component of Army force training and provide testing environments for new systems. Simulations fill a void created when exercises are impractical thereby increasing warfighter preparedness. But training on C41 systems requires an interface between these systems and the simulation system. To use simulations with C41 systems the Army has been developing point-to-point software interlaces. These ad hoc interfaces have failed to yield insights into C41/M&S interoperability. Lacking such insights each software interface is a largely independent effort that wastefully re-implements portions of previous interfaces., The original document contains color images. Task BC-5-1943.

Interoperability between Command, Control, Communications, Computers, and Intelligence (C4I) and Modeling & Simulation (M&S) systems is an unrealized goal with great potential. Interoperability can facilitate training, simulation-based acquisition, mission planning and rehearsal, and course of action development and analysis. Recent interoperability research has concentrated on general-purpose approaches that can provide standards and reuse across a wide range of systems. One important component of interoperability is data model alignment, the degree to which the data models of two systems use the same elements. This paper presents a rigorous definition of data model alignment and uses it to assess the degree of alignment between the Army Integrated Core Data Model (AICDM) and the standard objects defined by the Object Management Standards Category (OMSC), two important emerging standards in the C4I and M&S communities, respectively. This assessment is used to make recommendations on changes to each model that would promote interoperability. The conclusion is that the OMSC standard objects need considerable work to model C4I data., The original document contains color images.