From New World Encyclopedia

Interoperability refers to the ability of diverse systems and organizations to work together (inter-operate). The term is often used in terms of technical systems engineering, or alternatively in a broader sense that accounts for social, political, and organizational factors that impact system to system performance. "Interop" is also the name of several annual networking product trade shows.

Interoperability makes communication and data exchange between systems possible, and it is vital for system integration or collaboration of sub-systems. Today, system integration is rapidly taking place at various levels and in various fields. Interoperability becomes an issue when economic interests of developers and the public are in conflict. For example, the European Commission accused Microsoft of abusing market power by developing systems that were not interoperable with non-Microsoft systems.

One successful example of interoperability is the development of MARC standards (standards for MAchine-Readable Cataloging) across library communities. In 1968, the Library of Congress (U.S.) developed the standards for electronic bibliographic information, which became the international standard for inter-library operations.


The IEEE (Institute of Electrical and Electronics Engineers) defines interoperability as:

the ability of two or more systems or components to exchange information and to use the information that has been exchanged.[1]

To exchange information or data, two or more systems must be compatible at some level. If information or data was generated in one information system and another system could not read or retrieve it in a meaningful way, those two systems are not interoperable. Communication and exchange of data are possible only when two or more systems are interoperable.

Interoperability exists in various ways: Hardware, software, technology, metadata, and others. In today's information environment, it is important to set common standards that all system producers can comply with in a given field.

Many organizations are dedicated to interoperability. All have in common that they want to push the development of the world wide web towards the semantic web. Some concentrate on eGovernment, eBusiness or data exchange in general. In Europe, for instance, the European Commission and its IDABC (Interoperable Delivery of European eGovernment Services to public Administrations, Businesses and Citizens) program issue the European Interoperability Framework. They also initiated the Semantic Interoperability Centre Europe (SEMIC.EU). In the United States, the government service provides an environment for component development, sharing, registration, and reuse.


In telecommunication, the term can be defined as:

  1. The ability of systems, units, or forces to provide services to and accept services from other systems, units or forces and to use the services exchanged to enable them to operate effectively together.
  2. The condition achieved among communications-electronics systems or items of communications-electronics equipment when information or services can be exchanged directly and satisfactorily between them and/or their users. The degree of interoperability should be defined when referring to specific cases (Federal Standard 1037C and from the Department of Defense Dictionary of Military and Associated Terms in support of MIL-STD-188).

In two-way radio, interoperability is composed of three dimensions:

  • Compatible communications paths (compatible frequencies, equipment and signaling)
  • Radio system coverage or adequate signal strength
  • Scalable capacity


Interoperability: playing the two role network game, when one of the player clients (top left) runs under Sun Microsystems and another under GNU Classpath with JamVM. The applications execute the same bytecode and interoperate using the standard RMI-IIOP messages for communication.

With respect to software, the term interoperability is used to describe the capability of different programs to exchange data via a common set of exchange formats, to read and write the same file formats, and to use the same protocols. (The ability to execute the same binary code on different processor platforms is "not" contemplated by the definition of interoperability.) The lack of interoperability can be a consequence of a lack of attention to standardization during the design of a program. Indeed, interoperability is not taken for granted in the non-standards-based portion of the computing world.

According to ISO/IEC 2382-01, Information Technology Vocabulary, Fundamental Terms, interoperability is defined as follows: "The capability to communicate, execute programs, or transfer data among various functional units in a manner that requires the user to have little or no knowledge of the unique characteristics of those units."[2]

Note that the definition is somewhat ambiguous because the user of a program can be another program and, if the latter is a portion of the set of program that is required to be interoperable, it might well be that it does need to have knowledge of the characteristics of other units. This definition focuses on the technical side of interoperability. On the other hand, it has also been pointed out that interoperability is often more of an organizational issue. Interoperability raises issues of ownership, labor relations, and usability. In this context, a more apt definition is captured in the term "business process interoperability."

Interoperability can have important economic consequences, such as network externalities. If competitors' products are not interoperable (due to causes such as patents, trade secrets, or coordination failures), the result may well be monopoly or market failure. For this reason, it may be prudent for user communities or governments to take steps to encourage interoperability in various situations. In the United Kingdom, for example, there is an eGovernment-based interoperability initiative called e-GIF. As far as user communities are concerned, Neutral Third Party is currently creating standards for business process interoperability.

Medical industry

New technologies are being introduced in hospitals and labs at an ever-increasing rate, and many of these innovations have the potential to interact effectively if they can be integrated effectively. The need for “plug-and-play” interoperability—the ability to take a medical device out of its box and easily make it work with one’s other devices—has attracted great attention from both health care providers and the health care industry.

Conditions in the biomedical industry are still in the process of becoming conducive to the development of interoperable systems. A potential market of interested hospitals exists, and standards for interoperability are being developed. Nevertheless, it seems that current business conditions do not encourage manufacturers to pursue interoperability. Only sixteen to twenty percent of hospitals, for example, use electronic medical records (EMR). With such a low rate of EMR adoption, most manufacturers can get away with not investing in interoperability. In fact, not pursuing interoperability allows some of them to tout the inter-compatibility of their own products while excluding competitors. By promoting EMR adoption, companies such as Intel hope to create an environment in which hospitals will have the collective leverage to demand interoperable products.


eGovernment interoperability refers to the collaboration of cross-border services for citizens, businesses and public administration. Exchanging data can be challenging due to language barriers, different specifications of formats and varieties of categorizations.

If data is interpreted differently, collaboration is limited and inefficient. Thus eGovernment applications must exchange data in a semantically interoperable manner.

Public safety

Interoperability is an important issue for law enforcement, fire fighting, EMS (Emergency medical services), Earthquake Early Warning, and other public health and safety departments, because first responders need to be able to communicate during wide-scale emergencies. Traditionally, agencies could not exchange information because they operated on widely disparate hardware that was incompatible. Agencies' information systems such as computer-aided dispatch systems (CAD) and records management systems (RMS) functioned largely in isolation, so-called "information islands." Agencies tried to bridge this isolation with inefficient, stop-gap methods while large agencies began implementing limited interoperable systems. These approaches were inadequate and the nation's lack of interoperability in the public safety realm become evident during the September 11 attacks on the Pentagon and World Trade Center (New York City) structures in 2001. Further evidence of a lack of interoperability surfaced when agencies tackled the aftermath of the Hurricane Katrina disaster in the U.S. in 2005.

In contrast to the overall national picture, some states, including Utah, have already made great strides forward. The Utah Highway Patrol and other departments in Utah have created a statewide data-sharing network using technology from a company based in Bountiful, Utah, FATPOT Technologies.

The State of Washington seeks to enhance interoperability statewide. The State Interoperability Executive Committee (SIEC), established by the legislature in 2003, works to assist emergency responder agencies (police, fire, sheriff, medical, hazmat, and so on) at all levels of government (city, county, state, tribal, federal) to define interoperability for their local region.

The U.S. government is making a concerted effort to overcome the nation's lack of public safety interoperability. The Department of Homeland Security's Office for Interoperability and Compatibility (OIC) is pursuing the SAFECOM and CADIP programs, which are designed to help agencies as they integrate their CAD and other IT systems.

The OIC launched CADIP in August 2007. This project will partner the OIC with agencies in several locations, including Silicon Valley. This program will use case studies to identify the best practices and challenges associated with linking CAD systems across jurisdictional boundaries. These lessons will create the tools and resources public safety agencies can use to build interoperable CAD systems and communicate across local, state, and federal boundaries.

In countries such as Japan, Taiwan, and Mexico, where earthquakes are frequent, Earthquake Warning Systems have been established.[3] An Earthquake Warning System is a system of accelerometers, communication, computers, and alarms that is devised for regional notification of a substantial earthquake while it is in progress. This is not the same as earthquake prediction, which is currently incapable of producing actionable event warnings. Japan has some of the most advanced systems in the world, one of which was put to practical use in 2006; its ability to warn the general public was installed on October 1, 2007.[4] When the sign of Earthquake is detected, the warnings are immediately issued by the Japan Meteorological Agency. The warning is then transmitted to all key agencies in the area and broadcast through TV, radio, cellular phone, internet, home intercom, and other communication medium.

The purpose of an Earthquake Early Warning is to mitigate damages by an earthquake. They allow people to take measures to protect themselves at home or at work. Since time is a crucial factor, all networks must be interoperatable with maximum speed and efficiency.

Library and information science

In the latter half of the twentieth century, libraries conducted massive data migration from the traditional card system (bibliographic information about a book is written an index card) to computerized information systems. The Library of Congress (U.S.) took the lead in setting the standard by starting the MARC Standards (standards for MAchine-Readable Cataloging) project in 1965. The Library of Congress, led by a project leader Henriette Avram, completed the project in 1968. MARC standards provide the protocol by which computers read, interpret, exchange, and use bibliographic information. Furthermore, MARC standards also became the international standard. Thus, billions of bibliographic items of information in tens of thousands of libraries now exist in a computer based information system with a uniform format.

Achieving software interoperability

Software Interoperability is achieved through five interrelated ways:

  1. Product testing
    Products produced to a common standard, or to a sub-profile thereof, depend on clarity of the standards, but there may be discrepancies in their implementations that system or unit testing may not uncover. This requires that systems formally be tested in a production scenario—as they will be finally implemented—to ensure they actually will intercommunicate as advertised, that is, they are interoperable. Interoperable product testing is different from conformance-based product testing as conformance to a standard does not necessarily engender interoperability with another product which is also tested for conformance.
  2. Product engineering
    Implements the common standard, or a sub-profile thereof, as defined by the industry/community partnerships with the specific intention of achieving interoperability with other software implementations also following the same standard or sub-profile thereof.
  3. Industry/community partnership
    Industry/community partnerships, either domestic or international, sponsor standard workgroups with the purpose to define a common standard that may be used to allow software systems to intercommunicate for a defined purpose. At times an industry/community will sub-profile an existing standard produced by another organization to reduce options and thus making interoperability more achievable for implementations.
  4. Common technology and IP
    The use of a common technology or IP may speed up and reduce complexity of interoperability by reducing variability between components from different sets of separately developed software products and thus allowing them to intercommunicate more readily. This technique has some of the same technical results as using a common vendor product to produce interoperability. The common technology can come through 3rd party libraries or open source developments.
  5. Standard implementation
    Software interoperability requires a common agreement that is normally arrived at via a industrial, national, or international standard.

Each of these has an important role in reducing variability in intercommunication software and enhancing a common understanding of the end goal to be achieved.

Interoperability as a question of power and market dominance

Interoperability tends to be regarded as an issue for experts and its implications for daily living are sometimes underrated. The case of Microsoft vs. the European Commission shows how interoperability concerns important questions of power relationships. In 2004, the European Commission found that Microsoft had abused its market power by deliberately restricting interoperability between Windows work group servers and non-Microsoft work group servers. By doing so, Microsoft was able to protect its dominant market position for work group server operating systems, the heart of corporate IT networks. Microsoft was ordered to disclose complete and accurate interface documentation, which will enable rival vendors to compete on an equal footing (“the interoperability remedy”). As of June 2005 the Commission is market testing a new proposal by Microsoft to do this, having rejected previous proposals as insufficient.

Recent Microsoft efforts around interoperability may indicate a shift in their approach and level of commitment to interoperability. These efforts including the migration of Microsoft Office file formats to ECMA Office Open XML, and several partner interoperability agreements, most notably their recent collaboration agreement with Novell.[5]

Interoperability has also surfaced in the Software patent debate in the European Parliament (June/July 2005). Critics claim that because patents on techniques required for interoperability are kept under RAND (reasonable and non discriminatory licensing) conditions, customers will have to pay license fees twice: Once for the product and, in the appropriate case, once for the patent protected program the product uses.

See also

  • Standardization


  1. Institute of Electrical and Electronics Engineers, IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries (New York, NY: 1990).
  2. ISO, IEC, Proposed Draft Technical Report for: ISO/IEC xxxxx, Information technology; Learning, education, and training; Management and delivery; Specification and use of extensions and profiles. Retrieved October 11, 2008.
  3. David Talbot, A technology review, Massachusetts Institute of Technology.
  4. Japan Meteorological Agency, What is the Earthquake Early Warning? Retrieved October 10, 2008.
  5. Microsoft, Microsoft and Novell Announce Broad Collaboration on Windows and Linux Interoperability and Support Companies also announce a patent agreement covering proprietary and open source products. Retrieved October 10, 2008.

ISBN links support NWE through referral fees

  • Branscomb, Lewis M., and James Keller. Converging Infrastructures Intelligent Transportation and the National Information Infrastructure. Cambridge, MA: MIT Press, 1996.
  • Faith, G. Ryan, Vincent Sabathier, and Lyn Wigbels. Interoperability and Space Exploration A Report of the Human Space Exploration Initiative at the Center for Strategic and International Studies. Washington, D.C.: HSEI, 2007. Retrieved October 10, 2008.
  • "Inside PC Labs—There's a Renaissance Going on in the Wireless LAN Arena, but Interoperability Among Product Manufacturers Isn't Perfect yet." PC Magazine. 20 (5): 61.
  • Japan Meteorological Agency. What is the Earthquake Early Warning? Retrieved October 10, 2008.
  • Leebaert, Derek. The Future of the Electronic Marketplace. Cambridge, MA: MIT Press, 1998.
  • National Institute of Justice (U.S.). Public Safety Communications and Interoperability. In Short, Toward Criminal Justice Solutions. Washington, D.C.: U.S. Dept. of Justice, Office of Justice Programs, National Institute of Justice, 2007.
  • Panetto, Herve. Interoperability of Enterprise Software and Applications. Paris: Hermes Science Publ, 2005.
  • Searle, Jonathan, and John Brennan. General Interoperability Concepts. Ft. Belvoir: Defense Technical Information Center, 2006. Retrieved October 10, 2008.
  • Searle, Jonathan, and John Brennan. Interoperability Architectures. Ft. Belvoir: Defense Technical Information Center, 2006. Retrieved October 10, 2008.
  • Talbot, David. A technology review. MIT. Retrieved October 10, 2008.
  • Tennant, R.2003. "Digital Libraries The Engine of Interoperability." Library Journal 128: 33.

External links

All links retrieved March 4, 2018.


New World Encyclopedia writers and editors rewrote and completed the Wikipedia article in accordance with New World Encyclopedia standards. This article abides by terms of the Creative Commons CC-by-sa 3.0 License (CC-by-sa), which may be used and disseminated with proper attribution. Credit is due under the terms of this license that can reference both the New World Encyclopedia contributors and the selfless volunteer contributors of the Wikimedia Foundation. To cite this article click here for a list of acceptable citing formats.The history of earlier contributions by wikipedians is accessible to researchers here:

The history of this article since it was imported to New World Encyclopedia:

Note: Some restrictions may apply to use of individual images which are separately licensed.