To keep up to date, manufacturing enterprises need to use the latest results from the ICT sector, especially when collaborating with external partners in a supply chain and exchanging products and data. This has led to dealing with an increasing amount of heterogeneous information exchanged between partners including machines (physical means), humans and IT in the Supply Chain of ICT Systems (SC-ICTS). In this context, interoperability management is becoming more and more critical, but paradoxically, it is not yet fully efficiently anticipated, controlled and accompanied to recover from incompatibilities issues or failures. This paper intends to present how enterprise modeling, enterprise interoperability and model driven approaches can lead, together with system engineering architecture, to contribute to developing and improving the interoperability in the SC-ICTs. Model Driven System Engineering Architecture (MDSEA) is based on Enterprise Modeling using GRAI Model and its extensions. It gives enterprise internal developments guidelines, but originally, MDSEA is not the considering interoperability that is required between partners when setting a collaboration in the frame of SC-ICTS. As a result, the MDSEA, extended with interoperability concerns, led to the design of the MDISE (Model Driven Interoperability System Engineering) framework, which capitalizes on the research on enterprise interoperability. To finish, some proposals are made to extend the Model System Tool Box (MSTB) and the use of MDISE for Cyber Physical System (CPS) that are relevant components of SC-ICTS.
A coalition of enterprises wanting to collaborate, and more generally a Collaborative Network of Organizations (CNO), can conceptually be assimilated as a System of Systems (SoS) presenting a number of characteristics to respect all over its life cycle. Interoperability is one of these characteristics (both functional and non-functional), which is from our point of view, essential in order to guarantee the control of the SoS, its behavior and the fulfillment of its mission(s). Moreover, it ensures the reaction of the SoS to deal with some risky situations and with potential local or global deficits during its functioning. In this paper, we propose to determine the relation between the current level of interoperability of the SoS and its functioning whatever may be its situation. A matrix shows how this relation evolves taking into account several characteristics of the SoS, particularly its capacity to respect interoperability requirements (Compatibility, Interoperation, Autonomy and Reversibility) and the so-called analysis perspectives of the SoS: Performance, Integrity and Stability. This relation is requested in order to permit and to guide SoS behavioral simulation currently in development. Thus, a set of indicators is derived and formalized.
International audienceInteroperability is a prerequisite for partners involved in performing collaboration. As a consequence, the lack of interoperability is now considered a major obstacle. The research work presented in this paper aims to develop an approach that allows specifying and verifying a set of interoperability requirements to be satisfied by each partner in the collaborative process prior to process implementation. To enable the verification of these interoperability requirements, it is necessary first and foremost to generate a model of the targeted collaborative process; for this research effort, the standardised language BPMN 2.0 is used. Afterwards, a verification technique must be introduced, and model checking is the preferred option herein. This paper focuses on application of the model checker UPPAAL in order to verify interoperability requirements for the given collaborative process model. At first, this step entails translating the collaborative process model from BPMN into a UPPAAL modelling language called 'Network of Timed Automata'. Second, it becomes necessary to formalise interoperability requirements into properties with the dedicated UPPAAL language, i.e. the temporal logic TCTL