Enterprise interoperability framework

The enterprise interoperability framework is used as a guideline for collecting and structuring knowledge/solution for enterprise interoperability. The framework defines the domains and sub-domains for interoperability research and development in order to identify a set of pieces of knowledge for solving enterprise interoperability problems by removing barriers to interoperability.

## Contents

* 1 Existing interoperability frameworks
* 2 Use
* 3 References
* 4 External links

## Existing interoperability frameworks

Some existing works on interoperability have been carried out to define interoperability framework or reference models, in particular, the LISI[1] reference model, European Interoperability Framework (EIF),[2] IDEAS interoperability framework,[3] ATHENA interoperability framework,[4] and E-Health Interoperability Framework.[5] These existing approaches constitute the basis for the enterprise interoperability framework.

Existing interoperability frameworks do not explicitly address barriers to interoperability, which is a basic assumption of this research; they are not aimed at structuring interoperability knowledge with respect to their ability to remove various barriers.

The enterprise Interoperability framework has three basic dimensions:

1. Interoperability concerns define the content (or aspect) of interoperation that may take place at various levels of the enterprise. In the domain of Enterprise Interoperability, the following four interoperability concerns are identified: data, service, process, and business.[6] Interoperability concerns: data, service, process, and business
2. Interoperability barriers: Interoperability barrier is a fundamental concept in defining the interoperability domain. Many interoperability issues are specific to particular application domains. These can be things like support for particular attributes or particular access control regimes. Nevertheless, general barriers and problems of interoperability can be identified; and most of them being already addressed,[2][7][8] Consequently, the objective is to identify common barriers to interoperability. By the term ‘barrier’ we mean an ‘incompatibility’ or ‘mismatch’ which obstructs the sharing and exchanging of information. Three categories of barriers are identified: conceptual, technological and organisational.
3. Interoperability approaches represent the different ways in which barriers can be removed (integrated, unified, and federated)

Basic Approaches to Develop Interoperability

The framework with its three basic dimensions is shown.

Enterprise interoperability framework

## Use

The Enterprise Interoperability Framework allows to:

* Capture and structure interoperability knowledge/solutions in the framework through a barrier-driven approach
* Provide support to enterprise interoperability engineers and industry end users to carry out their interoperability projects.

The enterprise interoperability framework not only aims at structuring concepts, defining research domain and capturing knowledge but also at helping industries to solve their interoperability problems. When carrying out an interoperability project involving two particular enterprises, interoperability concerns and interoperability barriers between the two enterprises will be identified first and mapped to this Enterprise Interoperability Framework.

Using the framework, existing interoperability degrees can be characterized and targeted interoperability degrees can be defined as the objective to meet. Then knowledge/solutions associated with the barriers and concerns can be searched in the framework, and solutions found will be proposed to users for possible adaptation and/or combination with other solutions to remove the identified barriers so that the required interoperability can be established.

## References

1. ↑ C4ISR (1998), Architecture Working Group (AWG), Levels of Information Systems Interoperability (LISI), 30 March 1998.
2. ↑ 2.0 2.1 EIF: European Interoperability Framework, Write Paper, Brussels, 18, Feb. 2004, http://www.comptia.org
3. ↑ IDEAS (2003), IDEAS Project Deliverables (WP1-WP7), Public reports, www.ideas-road map.net.
4. ↑ ATHENA (2003): Advanced Technologies for Interoperability of Heterogeneous Enterprise Networks and their Applications, FP6-2002-IST-1, Integrated Project Proposal, April 2003. Deriverable.
5. ↑ NEHTA (2006), Towards a Health Interop Framework, ("Towards a Health Interop Framework". http://www.providersedge.com/ehdocs/ehr_articles/Towards_an_Interoperability_Framework.pdf. .
6. ↑ C. Guglielmina and A. Berre, Project A4 (Slide presentation), ATHENA Intermediate Audit 29.-30. September 2005, Athens, Greece.
7. ↑ Kasunic, M., Anderson, W.,: Measuring systems interoperability: challenges and opportunities, Software engineering measurement and analysis initiative, April 2004
8. ↑ ERISA (The European Regional Information Society Association), A guide to Interoperability for Regional Initiatives, Brussels, September 2004.

## External links

* INTEROP-VLab
* DI.2.Enterprise Interoperability Framework and knowledge corpus
* DI.3.Enterprise Interoperability Framework and knowledge corpus

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Enterprise interoperability framework. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Enterprise_interoperability_framework&oldid=259976"