Using UNS to Integrate Operational Technologies in Your Manufacturing Facility

The Unified Namespace (UNS) is a hub-and-spoke-based architecture that uses industry-standard protocols to solve the data integration and communication challenges that exist in life sciences sector manufacturing facilities.  

Instead of integrating systems using point-to-point connections, the hub-and-spoke model enables all systems in the software stack to be connected to the hub. As a result, all equipment, platforms, and systems within the UNS architecture can send (publish) data and receive (subscribe to) data. Even legacy equipment on the factory floor designed to work in isolation can be integrated into a UNS solution, increasing data availability and operational oversight. 

OT Level Focus 

It is at the operational technology (OT) levels of the manufacturing software stack where UNS is at its most effective and can deliver the greatest range of benefits. 

This includes digitalization benefits as other digital transformation projects and initiatives can utilize a UNS architecture to facilitate project success. This leads to further improvements in manufacturing processes, product quality, compliance, productivity, and the way your organization uses data. 

OT Solutions for OT Requirements, IT Solutions for IT Requirements

As a concept, a UNS architecture could be adopted enterprise wide to also include IT-level business systems. Examples include ERP (enterprise resource planning) and CRM (customer relationship management) systems. This is in addition to OT-level systems such as production equipment, shop floor sensors, SCADA systems, PLCs, etc.  

While the scope of UNS has enterprise-wide potential, there are several reasons why this is unlikely to be the best approach:  

• Existence of IT-level integration solutions 

• API integration requirements 

• Industrial-focused integration protocols 

Existence of IT-Level Integration Solutions 

Modern organizations are likely to have already invested in IT-level integration solutions. These solutions will be crucial to operational success. OT-level integration solutions should be designed to co-exist with their IT counterparts. 

API Integration Requirements 

Business systems such as ERP and CRM platforms often only offer API integration options. This works well with IT-level systems, but there are challenges at the OT level.  

Making API integrations work within a UNS architecture is possible, but such integrations require additional considerations. This increases complexity, usually within the adjacent IIoT Platform (companion to the broker). Higher levels of complexity increase the engineering hours required to develop the UNS architecture and, crucially, to maintain it. 

There could be situations where API integrations are unavoidable, even at the OT level. However, they should be implemented judiciously where other options are available. 

Industrial-Focused Integration Protocols 

Developing a UNS architecture involves using industrial data transfer protocols that are compatible with as wide a range of OT technologies and systems as possible. The most common is MQTT, the widely recognized industry standard OT communication protocol. 

MQTT is ideally suited to manufacturing and industrial environments because it is lightweight and works effectively in low-bandwidth, high-latency, and other challenging environments. 

Manufacturers of OT-level equipment and systems increasingly offer MQTT compatibility as standard or as an add-on option, reducing integration complexity. IT-level systems, on the other hand, rarely offer MQTT support. 

Co-Existing Data Transfer and Communication Solutions 

IT-level integration solutions are not suitable for OT environments, but the reverse is true too, i.e., OT integration solutions are not ideal for IT systems.  

The answer is co-existing solutions – a hub-and-spoke data integration and connectivity solution (UNS) for OT systems working alongside IT integration solutions that could potentially also operate on a hub-and-spoke basis. Continuing with the vehicle metaphor, this setup can be described as two hubs on the same axle. 

In practice, equipment, platforms, and systems can be connected as spokes to one or both live data hubs. Not only is this a workable and forward-thinking solution, but it is also the most practical in the real world of pharmaceutical and medical device manufacturing environments. 

Maximize the Potential of UNS in Your Organization 

Manual processes, data silos, and disconnected systems result in productivity, compliance, and quality challenges that directly impact competitiveness and profitability. Digital transformation solutions integrate systems, unleash the power of data, and automate/semi-automate workflows and processes. 

In our whitepaper, Nick Fenlon explains how implementing a UNS architecture will deliver benefits today and provide a solid foundation for future digital transformation progress. 

He also outlines how you can maximize success while helping to bridge the gap between IT and OT in your organization. You can do this by focusing on where UNS can be most effectively and practically implemented – at the OT level of your manufacturing technology stack. Download the whitepaper now.