Source-linked AI summary
The Levels of Conceptual Interoperability Model: Applying Systems Engineering Principles to M&S
Wenguang WANG, Andreas TOLK, Weiping WANG
TL;DR
M&S lacks sufficiently established engineering methods for documenting conceptual models and supporting meaningful interoperability and composability. The paper evaluates LCIM as a framework with descriptive and prescriptive roles and applies it to HLA and BOM. It concludes that LCIM connects conceptual descriptions with technical implementation while exposing limitations in existing approaches.
Problem
Current M&S practices are insufficient for identifying, selecting, and composing models and simulation systems, while meaningful interoperability requires alignment of underlying conceptual models.
Method
The paper evaluates LCIM as a descriptive and prescriptive framework and applies it to interoperability standards, especially HLA and BOM.
Results
LCIM provides a framework spanning what is conceptually modeled to how it is technically implemented, while the HLA and BOM analysis exposes limits in capturing conceptual assumptions and constraints.
Takeaways & Limitations
LCIM supports systematic documentation and analysis of conceptual interoperability beyond technical interoperability.
Takeaways & Limitations
Conceptual interoperability remains difficult because conceptual definitions are not widely standardized and assumptions and constraints are hard to capture, especially in existing systems.
Abstract
from arXiv · showhide
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.
1. INTRODUCTION
The paper argues that M&S needs reproducible engineering frameworks for documenting conceptual models and interoperability. It introduces LCIM as a framework spanning conceptual modeling through technical implementation, with applications to descriptive and prescriptive analysis.
- Motivation: M&S requires engineering methods and documented artifacts to become a scientific discipline and support model and simulation-system selection and composition.The paper contrasts this need with current practices it considers insufficient.
- Conceptual Modeling: Conceptual models represent systems abstractly through artifacts such as languages, figures, and tables, including objectives, inputs, outputs, content, assumptions, and simplifications.
- Conceptual Modeling: Meaningful interoperability and composability require observable properties and processes, a meta-model of expected behavior, and mappings between observations and models.The paper identifies these as three premises for understanding services and systems.
- LCIM Framework: LCIM divides conceptual interoperability into seven levels, L0 through L6, extending from no interoperability toward conceptual interoperability.The model provides a reproducible framework for documenting interoperability beyond technical communication.
- LCIM Framework: LCIM gained recognition beyond simulation interoperability, including applications in system biology and ontology research.
3. DESCRIPTIVE AND PRESCRIPTIVE ROLES
LCIM has descriptive and prescriptive roles: it evaluates existing interoperability and guides proposed systems toward target conceptual interoperability levels. The roles are complementary but remain focused on data exchange and can conflict with existing-system realities.
- Descriptive Role: LCIM's descriptive role analyzes existing systems' interoperability properties and levels, functioning as a documentation and maturity model without prescribing approaches.It evaluates current capabilities and identifies gaps between interoperating systems.
- Prescriptive Role: LCIM's prescriptive role specifies requirements and engineering approaches for proposed systems to reach a target degree of conceptual interoperability.It can guide systems during conceptual modeling before interoperating systems exist.
- Relationship: Both roles rely on mutually supportive LCIM levels, with higher interoperability requiring implementation of lower levels and prescriptive use additionally requiring top-down mappings.The prescriptive role seeks full-spectrum interoperability rather than only a higher-level outcome.
- Limitations: The roles are limited to a data-exchange focus, and conflicts may arise when existing systems do not conform to prescribed interoperability expectations.The paper notes that compelling means may be used in such circumstances by government.
- Relationship: Description evaluates actual approaches and prescription guides proposed designs; together they can assess gaps between interoperability objectives and implemented systems.A from-scratch process can begin with prescription and use description during refinement and implementation.
- Relationship: Descriptive findings may become prescriptive guidance when specific methods prevail and are standardized, while non-standard approaches are generally avoided by prescription.This relationship allows descriptive practice to inform evolving prescriptive recommendations.
4. APPLICATION OF LCIM TOWARD THE COM-POSABLITY OF HLA AND BOM
The LCIM is used to evaluate and improve composability in HLA and BOM by examining relationships across conceptual and implementation artifacts. HLA generally reaches only the syntactic level, while BOM extends interoperability toward conceptual modeling but remains limited by its UML-based representation.
- LCIM’s descriptive and prescriptive roles evaluate existing HLA and BOM composability and recommend solutions for improving both standards.The descriptive role analyzes current systems, while the prescriptive role supports recommendations for more composable designs.
- HLA object-model relationships include composition, extension, transformation, and aggregation.Transformation can convert BOM assemblies into FOM/SOM modules or FOM/SOM, while aggregation concerns MOM relationships to FOMs.
- HLA generally reaches the syntactic interoperability level because OMT specifies exchanged-data structure but not its semantics.RTI implementations operate at the technical level, while FOM/SOM artifacts generally remain syntactic; shared agreement can bring RPR-FOM to the semantic level.
- BOM integrates metadata, conceptual models, mappings, and object-class interfaces to improve HLA composability, interoperability, and reusability.These artifacts connect conceptual models with implementation objects and describe entities, events, behavior, interfaces, mappings, and metadata.
- BOM can reach the dynamic level but not the conceptual level because UML artifacts do not capture conceptual-model assumptions and constraints.The paper presents BOM as the most advanced simulation standard available while identifying this limitation in its conceptual-model coverage.
5. CONCLUSION
LCIM frames meaningful interoperability as alignment between conceptual ideas and technical implementation. Its application to BOM and HLA shows progress beyond pure data exchange, while also identifying limits in the artifacts used to represent conceptual models.
- LCIM specifies interoperability needs across levels from what is modeled conceptually to how it is implemented technically.It requires descriptions of data, their use, and constraints, while supporting semantic loss-free mediation across differing scopes, resolutions, and structures.
- BOM is the first simulation interoperability standard identified as extending beyond pure data-exchange specifications.The paper states that BOM artifacts remain insufficient to support all interoperability levels.