The Levels of Conceptual Interoperability Model: Applying Systems Engineering Principles to M&S

This paper describes the use of the Levels of Conceptual Interoperability Model (LCIM) as a framework for conceptual modeling and its descriptive and prescriptive uses. LCIM is applied to show its potential and shortcomings in the current simulation interoperability approaches, in particular the High Level Architecture (HLA) and Base Object Models (BOM). It emphasizes the need to apply rigorous engineering methods and principles and replace ad-hoc approaches.

💡 Research Summary

The paper positions the Levels of Conceptual Interoperability Model (LCIM) as a rigorous engineering framework for assessing and guiding interoperability in modeling and simulation (M&S). LCIM defines seven hierarchical levels—No Interoperability, Technical, Information, Semantic, Pragmatic, Conceptual, and Full—each associated with specific artifacts such as protocols, data schemas, ontologies, policy agreements, design principles, and strategic alignment. The authors distinguish two modes of LCIM use: a descriptive mode that objectively maps existing systems onto the model to reveal gaps, and a prescriptive mode that sets target levels and enumerates the concrete deliverables required to move upward.

Applying this framework to the two dominant M&S standards, the High Level Architecture (HLA) and Base Object Models (BOM), the authors find that HLA primarily addresses the Technical and Information levels, standardizing data exchange formats and communication services but stopping short of semantic alignment or policy coordination. BOM extends further, attempting to capture semantic and pragmatic aspects through reusable object definitions, yet it still falls short of the higher Conceptual and Full levels where strategic intent, governance, and continuous alignment are required.

The paper argues that these shortcomings stem from an ad‑hoc development culture that neglects core systems‑engineering practices such as requirements‑driven design, model‑based development, and systematic verification. By embedding LCIM into the full systems‑engineering lifecycle—eliciting interoperability requirements early, modeling semantics and pragmatics with ontologies and policy documents during design, automatically generating code from these models, and executing level‑specific test suites during verification—developers can reduce rework and ensure that each successive LCIM level is truly achieved.

Practical challenges identified include managing the complexity of multi‑domain ontologies, reconciling conflicting policies, and maintaining the meta‑model as systems evolve. The authors propose meta‑model‑driven governance platforms and collaborative tooling to address these issues. In conclusion, LCIM is presented not merely as a diagnostic checklist but as a prescriptive, lifecycle‑integrated methodology that can transform the current HLA‑ and BOM‑centric, largely technical interoperability approaches into a disciplined, repeatable engineering process capable of delivering true strategic interoperability across heterogeneous simulation environments.