Business interoperability interface

Last updated November 15, 2023

A business interoperability interface (BII) is an interface that enables business interoperability between organizational systems. The term was coined by the European Commission in the European Interoperability Framework^[1] where such interfaces are recommended to improve the interoperability of public administrations that internally use different standards.

Though the BII description of the European Commission remains vague, the following requirements are described: The BII should describe entry and exit points to the internal business processes of an organization and it should describe the contribution and commitments the collaboration partners require from each other in a formal way. Furthermore, the BII should enable the enactment of collaborative business processes and interconnect the business processes of different organizations. This description implies that the main objective of the BII is to describe to collaboration partners how they can interact with an organization.

Interface

An interface represents the point of interconnection between two systems or subsystems. Since collaborative business always comprises interactions between organizational systems (e. g. enterprises or departments), interfaces are an essential element in the development of collaborative business processes. In the context of organizations working together, interface descriptions should describe those characteristics of a system that are relevant for adjacent systems. While interfaces in information systems formerly concentrated on technical aspects, e.g. by describing Application Programming Interfaces, recent developments like Service-oriented Architecture shifted the attention to conceptual interfaces aiming at a business-level description of services and organizational boundaries.

Business interoperability

In a similar vein it was argued, that previous interoperability definitions focused too much on technical aspects. In consequence, the term Business Interoperability was proposed, for example defined as "the organizational and operational ability of an enterprise to cooperate with its business partners and to efficiently establish, conduct and develop IT-supported business relationships with the objective to create value".^[2] Interoperability is usually understood as the capability of autonomous systems "to exchange information and be able to use it",^[3] or simply put: the capability of an autonomous system to work together or to collaborate. Since "working together" of autonomous organizations means that they execute a collaborative business process, Business Interoperability can also be defined as
... the capability of autonomous organizations to execute a collaborative business process among them.^[4]

Definition

Based on the definitions of business interoperability and interface, the term BII can be defined as follows:

The Business Interoperability Interface of an organization comprises all information that is relevant for partner organizations in order to enact a collaborative business process with the organization. The interface comprises those elements of a collaborative business process, which are provided by the organization itself, as well as the elements, the organization expects from partner organizations.^[5]

The BII contents are not restricted to process descriptions: in order to enact a collaborative business process, the collaboration partners do not only need to know the sequence in which activities are executed but also require complementary information like organizational roles, specifics of individual activities or document types. Likewise, the description of the BII should cover different levels of technical granularity, since the systematic enactment of collaborative business processes requires models on both the business and the technical level.

Implementations

An EU-research project, aiming at improving interoperability between European public administrations, delivered a proposal for designing and implementing a Business Interoperability Interface, which was later refined in scientific publications.^[6]

The illustration summarizes the idea of this BII implementation: Organization A and B each has an internal/private view on its information system. From this internal model, they derive a view for their collaboration partner. For example, in the public process of Organization A, only those activities of the private process from Organization A are comprised which are relevant for the collaboration partner (i.e. Organization B). All these public elements are then bundled in the BII where a collaboration partner can read them. If the elements of adjacent BII-elements fit together and all collaboration partners agreed on how to interpret them, they are also called global elements.

The BII described there tackles four enterprise dimensions: In the organization dimension, roles, units and other organization elements relevant for the collaboration are described and related to internal elements. This ensures for example, that the collaboration partners have a common understanding of the interacting roles. In the data dimension, document types used in the collaboration are defined and related to internally used document types. In the function dimension, business functions and services offered in the collaboration are described. In the process dimension, the processes that each organization offers are described, as well as how these public processes are related to adjacent processes of partner organizations.

Related Research Articles

<span class="mw-page-title-main">Interoperability</span> Ability of systems to work with each other

Interoperability is a characteristic of a product or system to work with other products or systems. While the term was initially defined for information technology or systems engineering services to allow for information exchange, a broader definition takes into account social, political, and organizational factors that impact system-to-system performance.

In software engineering, service-oriented architecture (SOA) is an architectural style that focuses on discrete services instead of a monolithic design. By consequence, it is also applied in the field of software design where services are provided to the other components by application components, through a communication protocol over a network. A service is a discrete unit of functionality that can be accessed remotely and acted upon and updated independently, such as retrieving a credit card statement online. SOA is also intended to be independent of vendors, products and technologies.

<span class="mw-page-title-main">Business process modeling</span> Activity of representing processes of an enterprise

Business process modeling (BPM) in business process management and systems engineering is the activity of representing processes of an enterprise, so that the current business processes may be analyzed, improved, and automated. BPM is typically performed by business analysts, who provide expertise in the modeling discipline; by subject matter experts, who have specialized knowledge of the processes being modeled; or more commonly by a team comprising both. Alternatively, the process model can be derived directly from events' logs using process mining tools.

Enterprise architecture (EA) is a business function concerned with the structures and behaviours of a business, especially business roles and processes that create and use business data. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes."

Enterprise content management (ECM) extends the concept of content management by adding a timeline for each content item and, possibly, enforcing processes for its creation, approval, and distribution. Systems using ECM generally provide a secure repository for managed items, analog or digital. They also include one methods for importing content to bring manage new items, and several presentation methods to make items available for use. Although ECM content may be protected by digital rights management (DRM), it is not required. ECM is distinguished from general content management by its cognizance of the processes and procedures of the enterprise for which it is created.

The ARIS concept by August-Wilhelm Scheer aims to ensure that an enterprise information system can completely meet its requirements.

The Department of Defense Architecture Framework (DoDAF) is an architecture framework for the United States Department of Defense (DoD) that provides visualization infrastructure for specific stakeholders concerns through viewpoints organized by various views. These views are artifacts for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through tabular, structural, behavioral, ontological, pictorial, temporal, graphical, probabilistic, or alternative conceptual means. The current release is DoDAF 2.02.

The viable system model (VSM) is a model of the organizational structure of any autonomous system capable of producing itself. It is an implementation of viable system theory. At the biological level, this model is correspondent to autopoiesis.

A system architecture is the conceptual model that defines the structure, behavior, and more views of a system. An architecture description is a formal description and representation of a system, organized in a way that supports reasoning about the structures and behaviors of the system.

The British Ministry of Defence Architecture Framework (MODAF) was an architecture framework which defined a standardised way of conducting enterprise architecture, originally developed by the UK Ministry of Defence. It has since been replaced with the NATO Architecture Framework.

Data architecture consist of models, policies, rules, and standards that govern which data is collected and how it is stored, arranged, integrated, and put to use in data systems and in organizations. Data is usually one of several architecture domains that form the pillars of an enterprise architecture or solution architecture.

The IDEAS Group is the International Defence Enterprise Architecture Specification for exchange Group. The deliverable of the project is a data exchange format for military Enterprise Architectures. The scope is four nation and covers MODAF (UK), DoDAF (US), DNDAF (Canada) and the Australian Defence Architecture Framework (AUSDAF). The initial scope for exchange is the architectural data required to support coalition operations planning, including:

Reference Model of Open Distributed Processing (RM-ODP) is a reference model in computer science, which provides a co-ordinating framework for the standardization of open distributed processing (ODP). It supports distribution, interworking, platform and technology independence, and portability, together with an enterprise architecture framework for the specification of ODP systems.

Frameworx is an enterprise architecture framework geared towards communications service providers.

Capability management is a high-level management function, with particular application in the context of defense.

ArchiMate is an open and independent enterprise architecture modeling language to support the description, analysis and visualization of architecture within and across business domains in an unambiguous way.

A view model or viewpoints framework in systems engineering, software engineering, and enterprise engineering is a framework which defines a coherent set of views to be used in the construction of a system architecture, software architecture, or enterprise architecture. A view is a representation of the whole system from the perspective of a related set of concerns.

Operational View (OV) is one of the basic views defined in the enterprise architecture (EA) of the Department of Defense Architecture Framework V1.5 (DoDAF) and is related with concept of operations. Under DODAF 2, which became operational in 2009, the collections of views are now termed 'viewpoints' and no longer views.

The Architecture of Interoperable Information Systems (AIOS) is a reference architecture for the development of interoperable enterprise information systems. If enterprises or public administrations want to engage in automated business processes with other organizations, their IT systems must be able to work together, i.e. they need to be interoperable. The AIOS represents a generic building plan for these organizations to develop interoperable information systems by systematically adjusting and extending their internal information systems. The AIOS was described in a doctoral thesis and is based on the results of various research projects on interoperability. It is independent from specific products or vendors but describes generically the different layers, views, relationships and technical means needed to efficiently establish interoperable information systems. To this aim it combines concepts from service-oriented architecture, Collaborative Business and Business Process Modelling. It can be seen as complementary to ARIS, a well-known architecture for internal information systems and business processes.

Manufacturing Enterprise Solutions Association International is a worldwide not-for-profit community of manufacturing companies, information technology hardware and software suppliers, system integrators, consulting service providers, analysts, editors, academics, and students. MESA's goal is to help member companies improve business results and production operations through application and implementation of information technology and best management practices.

References

↑ European Commission (2004): European Interoperability Framework for pan-European eGovernment Services – Version 1.0. Archived June 14, 2009, at the Wayback Machine Retrieved 2010-07-07.
↑ Legner, Christine; Wende, Kristin (2006): Towards an Excellence Framework for Business Interoperability Archived July 25, 2011, at the Wayback Machine . Proceedings of the 19th Bled eConference eValues. Bled, Slovenia.
↑ Institute of Electrical and Electronics Engineers. IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries. New York, NY: 1990.
↑ Ziemann (2010): Architecture of Interoperable Information Systems - An enterprise Model-based Approach for Describing and Enacting Collaborative Business Processes. Logos, 2010.
↑ Ziemann, Joerg; Loos, Peter (2009): Transforming cross-organizational processes between European Administrations – Towards a comprehensive Business Interoperability Interface. In: Weerakkody, V.; Janssen, M.; Dwivedi, Y. (Eds.): Handbook of Research on ICT-Enabled Transformational Government: A Global Perspective. ISBN 978-1-60566-390-6, pp. 93–116
↑ R4eGov IOP Architecture and IOP Lifecycle (Version 1). Deliverable WP4-D7, 2008. R4eGov – Towards e-Administration in the large, project number IST-2004-026650.

This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.

[1] European Commission (2004): European Interoperability Framework for pan-European eGovernment Services – Version 1.0. Archived June 14, 2009, at the Wayback Machine Retrieved 2010-07-07.

[2] Legner, Christine; Wende, Kristin (2006): Towards an Excellence Framework for Business Interoperability Archived July 25, 2011, at the Wayback Machine . Proceedings of the 19th Bled eConference eValues. Bled, Slovenia.

[3] Institute of Electrical and Electronics Engineers. IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries. New York, NY: 1990.

[4] Ziemann (2010): Architecture of Interoperable Information Systems - An enterprise Model-based Approach for Describing and Enacting Collaborative Business Processes. Logos, 2010.

[5] Ziemann, Joerg; Loos, Peter (2009): Transforming cross-organizational processes between European Administrations – Towards a comprehensive Business Interoperability Interface. In: Weerakkody, V.; Janssen, M.; Dwivedi, Y. (Eds.): Handbook of Research on ICT-Enabled Transformational Government: A Global Perspective. ISBN 978-1-60566-390-6, pp. 93–116

[6] R4eGov IOP Architecture and IOP Lifecycle (Version 1). Deliverable WP4-D7, 2008. R4eGov – Towards e-Administration in the large, project number IST-2004-026650.

[1]

[2]

[3]

[4]

[5]

[6]