Integrating Information Technology and Operational Technology Systems through an Industrial Business Process Twin Approach

Core Concepts

By introducing an Industrial Business Process Twin (IBPT) entity as an intermediary between IT and OT components, the proposed approach eliminates potentially conflicting communication channels within the organization's structure during the system design phase.

Abstract

The paper investigates the effects of the IBPT approach during the design phase of IT/OT integrated systems. The key contributions are:

The IBPT concept acts as an intermediary between the realms of IT and OT, decoupling the two worlds and allowing for integration of components from different manufacturers and platforms.

By eliminating direct interfaces between IT and OT components in the system design, the IBPT approach also eliminates potentially conflicting communication channels within the organization's structure, as per Conway's law.

The authors develop a RAMI4.0-compliant model of an Industry 4.0 scenario involving geographically distributed robot cells playing the game of Nine Men's Morris. This scenario demonstrates the four essential Industry 4.0 design principles.

Analysis of the resulting RAMI4.0 model shows that no direct IT/OT interfaces exist, confirming the elimination of potentially conflicting communication channels within the organization.

The RAMI Toolbox is utilized to enable a model-based systems engineering approach and ensure RAMI4.0 compatibility.

Stats

"The four Industry 4.0 design principles information transparency, technical assistance, interconnection, and decentralized decisions pose challenges in integrating information technology (IT) and operational technology (OT) solutions in industrial systems."
"Conway's law, originally introduced in [6] and later supported by evidence under the term "mirroring hypotheses" in [17], illustrates how these conflicting communication channels are reflected in the system design."
"By eliminating interfaces between IT and OT components in the system design, this approach is therefore eliminating conflicting communication channels within the organization's communication structure."

Quotes

"Conway's law, originally introduced in [6] and later supported by evidence under the term "mirroring hypotheses" in [17], illustrates how these conflicting communication channels are reflected in the system design, as shown on the left-hand side of Fig. 1."
"By eliminating interfaces between IT and OT components in the system design, this approach is therefore eliminating conflicting communication channels within the organization's communication structure."

Key Insights Distilled From

IT/OT Integration by Design

by Geor... at arxiv.org 04-17-2024

https://arxiv.org/pdf/2305.19735.pdf

Deeper Inquiries

How can the proposed IBPT approach be extended to address the life-cycle aspects of IT/OT integrated systems, beyond the design phase?

The IBPT approach can be extended to address the life-cycle aspects of IT/OT integrated systems by incorporating the concept of Digital Twins (DTs) throughout the system's operational phases. During the design phase, the IBPT entity acts as an intermediary between IT and OT components, abstracting interactions to the level of business logic. To extend this approach beyond the design phase, the IBPT can continue to function as a central orchestrator, ensuring seamless communication and coordination between IT and OT systems during the system's entire life cycle.
One way to achieve this extension is by integrating the IBPT entity with the concept of Asset Administration Shells (AASs) as defined in the Industry 4.0 framework. AASs provide a standardized way to represent physical assets and their digital counterparts, enabling seamless integration and communication between IT and OT systems. By aligning the IBPT concept with AAS specifications, the IBPT can facilitate data exchange, monitoring, and control of assets throughout their life cycle, ensuring consistency and efficiency in IT/OT integration.
Furthermore, the IBPT can be designed to capture and store data generated during the system's operation, enabling real-time monitoring, analysis, and optimization of processes. By creating a feedback loop between the IBPT and the integrated systems, continuous improvement and adaptation can be achieved, addressing the evolving requirements and challenges faced during the system's life cycle.

How can the IBPT concept be realized as an Industry 4.0 component compliant with the Asset Administration Shell specification?

To realize the IBPT concept as an Industry 4.0 component compliant with the Asset Administration Shell (AAS) specification, several key steps need to be taken:

Data Modeling: Develop a comprehensive data model that aligns with the AAS specification, defining the structure and attributes of the IBPT entity and its interactions with IT and OT components.

Interface Standardization: Implement standardized interfaces based on the AAS specification to enable seamless communication and data exchange between the IBPT and other components within the system.

Security and Privacy: Ensure that the IBPT component adheres to the security and privacy requirements outlined in the AAS specification, safeguarding sensitive data and maintaining the integrity of the system.

Lifecycle Management: Incorporate features that support the management of the IBPT component throughout its life cycle, including deployment, operation, maintenance, and decommissioning, in alignment with AAS principles.

Interoperability: Verify that the IBPT component can interoperate with other Industry 4.0 components and systems, following the interoperability guidelines set forth in the AAS specification.

By integrating these elements into the design and implementation of the IBPT concept, it can effectively function as an Industry 4.0 component compliant with the Asset Administration Shell specification, facilitating seamless integration and communication within IT/OT integrated systems.

What empirical evidence can be gathered to further validate the connection between the system design and the organization's communication structure, as per Conway's law?

To gather empirical evidence validating the connection between the system design and the organization's communication structure, as per Conway's law, the following research methodologies can be employed:

Case Studies: Conduct in-depth case studies within organizations implementing IT/OT integrated systems to analyze how the system design reflects the communication structure. By comparing the system architecture with the organization's communication patterns, insights can be gained into the alignment between the two.

Surveys and Interviews: Administer surveys and interviews to stakeholders involved in IT/OT integration projects to gather feedback on how the system design influences communication channels within the organization. Quantitative and qualitative data can be collected to identify correlations and patterns.

Observational Studies: Observe the interactions and collaborations between IT and OT teams during system design and implementation phases. By documenting communication channels, decision-making processes, and conflicts, empirical evidence can be gathered to validate Conway's law in action.

Network Analysis: Utilize network analysis techniques to map out the communication structures within the organization and compare them with the system design interfaces. By visualizing the communication networks and system architectures, empirical evidence can be obtained to support the connection between the two.

By employing a combination of these research methods, empirical evidence can be gathered to validate the relationship between system design and the organization's communication structure, providing insights into how Conway's law manifests in the context of IT/OT integration.