1. Levels of Conceptual Interoperability

The resulting challenges have produced layered views. Petty and Weisel distinguish between the idea of interoperability, coping with the technical challenges, and composability, dealing with modeling issues. Research at the Virginia Modeling, Analysis and Simulation Center (VMASC) refined these layers to define the "Levels of Conceptual Interoperability Model (LCIM)," This definition has undergone gradual improvement since the first discussion in.^[1] The current version of LCIM was first documented by Turnitsa in.^[2]

The different levels are characterized as follows: https://handwiki.org/wiki/index.php?curid=1306606

• Level 0: Stand-alone systems have No Interoperability.
• Level 1: On the level of Technical Interoperability, a communication protocol exists for exchanging data between participating systems. On this level, a communication infrastructure is established allowing systems to exchange bits and bytes, and the underlying networks and protocols are unambiguously defined. This level ensures common understanding of signals.
• Level 2: The Syntactic Interoperability level introduces a common structure to exchange information; i.e., a common data format is applied. On this level, a common protocol to structure the data is used; the format of the information exchange is unambiguously defined. This layer defines structure and ensures the common understanding of symbols.
• Level 3: If a common information exchange reference model is used, the level of Semantic Interoperability is reached. On this level, the meaning of the data is shared; the content of the information exchange requests are unambiguously defined. This layer defines (word) meaning. There is a related but slightly different interpretation of the phrase semantic interoperability, which is closer to what is here termed Conceptual Interoperability, i.e. information in a form whose meaning is independent of the application generating or using it. This layer ensures the common understanding of terms.
• Level 4: Pragmatic Interoperability is reached when the interoperating systems are aware of the methods and procedures that each system is employing. In other words, the use of the data – or the context of its application – is understood by the participating systems; the context in which the information is exchanged is unambiguously defined. This layer puts the (word) meaning into context, it ensures the common understanding of the use of terms, in particular to represent functions and parameters.
• Level 5: As a system operates on data over time, the state of that system will change, and this includes the assumptions and constraints that affect its data interchange. If systems have attained Dynamic Interoperability, they are able to comprehend the state changes that occur in the assumptions and constraints that each is making over time, and they are able to take advantage of those changes. When interested specifically in the effects of operations, this becomes increasingly important; the effect of the information exchange within the participating systems is unambiguously defined. This layer therefore ensures a common understanding of effects, in term of state changes, out parameters generated, etc.
• Level 6: Finally, if the conceptual model – i.e. the assumptions and constraints of the meaningful abstraction of reality – are aligned, the highest level of interoperability is reached: Conceptual Interoperability. This requires that conceptual models are documented based on engineering methods enabling their interpretation and evaluation by other engineers. In essence, this requires a "fully specified, but implementation independent model" as requested by Davis and Anderson; this is not simply text describing the conceptual idea. This level ensures that the underlying levels follow the same theory.

The LCIM shows that a layered approach to support composable services is necessary. The WS standards described earlier are not able to manage all levels, in particular not with the M&S specific upper layers. It is worth mentioning, however, that the LCIM focuses on technical support by information systems, such as command and control information systems in the military context. As Alberts and Hayes point out in,^[3] the organizational and social aspects are often even more important. Tolk proposes such a layered framework for measures of merits dealing with questions like tactical or strategic alignment of objectives or even political will of coalition partners in.^[4] Within this contribution, however, the focus will be on the information system aspects.

Page et al.^[5] suggest defining composability as the realm of the model and interoperability as the realm of the software implementation of the model. In addition, their research introduces integratability coping with the hardware-side and configuration side of connectivity. The author supports this categorization and recommends the following distinction when dealing with issues of simulation system interoperability, to include meaningful simulation-to-simulation system interoperation:

• Integratability contends with the physical/ technical realms of connections between systems, which include hardware and firmware, protocols, etc.
• Interoperability contends with the software- and implementation details of interoperations, including exchange of data elements based on a common data interpretation, etc.
• Composability contends with the alignment of issues on the modeling level. The underlying models are purposeful abstractions of reality used for the conceptualization being implemented by the resulting simulation systems.

This ideas complement the LCIM. The LCIM has been successfully applied not only in the domain of Modeling & Simulation, but generally in model-based interoperability challenges. It should be pointed out that the LCIM can be used in descriptive and in prescriptive mode.^[6] It was recently recommended to extend the LCIM to an Interoperability Maturity Matrix.^[7]

2. Composability as a Grand Challenge

During an ACM SIGSIM and SCS sponsored expert discussion during the SCS Spring Simulation Multiconference in San Diego, CA, on April 11, 2013, Professor Tolk addressed Composability as a Grand Challenge of Modeling & Simulation when we are thinking about M&S and Cloud-based Simulation. He proposed the following two definitions:

• Interoperability: the ability to exchange usable data between two systems and to invoke their services using the appropriate input parameters!
• Composability: the consistent representation of truth regarding the same objects as represented in the participating systems!

He referred to the latest work of his research team that utilizes Model Theory ^[8]

3. Applications

The LCIM in this form or slight variations thereof has been applied not only in simulation, but in many other domains as well. Examples are given in more than 500 journal articles, book chapters, and conference papers referencing the LCIM ideas, such as:

Health and Human Sciences (http://aspe.hhs.gov/sp/reports/2010/erpreqlim/report.shtml);

Medical Simulation: Weininger, S., Jaffe, M.B., Robkin, M., Rausch, T., Arney, D. and Goldman, J.M., 2016. The importance of state and context in safe interoperable medical systems. IEEE Journal of Translational Engineering in Health and Medicine, 4, pp.1-10.

Internet of Things: Kolbe, Niklas, Jérémy Robert, Sylvain Kubler, and Yves Le Traon. "PROFICIENT: Productivity Tool for Semantic Interoperability in an Open IoT Ecosystem." In Proceedings of the 14th EAI International Conference on Mobile and Ubiquitous Systems: Computing, Networking and Services. 2017.

Department of Energy SmartGrid (http://www.gridwiseac.org/pdfs/interopframework_v1_1.pdf);

Enterprise Interoperability Panetto, Hervé; Molina, Arturo (September 2008). "Enterprise integration and interoperability in manufacturing systems: Trends and issues". Computers in Industry 59 (7): 641–646. doi:10.1016/j.compind.2007.12.010. ;

Geographic Information Systems Manso, Miguel-Ángel; Wachowicz, Monica (2009). "GIS Design: A Review of Current Issues in Interoperability". Geography Compass 3 (3): 1105–1124. doi:10.1111/j.1749-8198.2009.00241.x. ;

Digital Library Ecosystem "Applying the Levels of Conceptual Interoperability Model to a Digital Library Ecosystem – a Case Study". DCMI International Conference on Dublin Core and Metadata Applications: 62–72. http://dcpapers.dublincore.org/pubs/article/viewFile/3851/2036. ;

Adaptive Instructional Systems; Workshop Proceedings of the 2nd AIS Standards Workshop. Opening Address: Understanding the AIS Problem Space, by Dr. Robert Sottilare

and more.