Access Official Technical PDF

Share Summary:LinkedInEmail

Industrial IoT standards help engineers connect devices, platforms and applications that may rely on different communications technologies. In industrial environments, this interoperability matters because sensor and machine data often needs to move across equipment, gateways and software systems before it can support monitoring or process control. Standards provide shared approaches to communication and information exchange, helping reduce the barriers created by isolated technology systems.

Work described by ETSI in 2018 illustrates how this standards landscape was developing. Activities included machine-to-machine (M2M) platforms, semantic models, security and work to connect industrial technologies with wider Internet of Things (IoT) systems. For automation teams, the practical lesson is that connectivity alone is not enough: systems also need common ways to exchange, secure and interpret information.

Why industrial IoT standards matter

Industrial IoT applications bring together devices, networks and services that may have been designed independently. A connected sensor can produce data, but other systems must be able to receive and make sense of it. Without agreed interfaces and information structures, integrating devices and applications across technology boundaries can be difficult.

Standards support a more consistent basis for this exchange. They can help organizations develop platforms and applications without requiring every connected device to use the same underlying communications technology. This is relevant to industrial process monitoring as well as wider connected applications, including smart grids, buildings and cities.

For system integrators and plant teams, standardization is therefore an architectural consideration. It can influence how devices connect to gateways, how platforms expose data and how an application communicates with systems beyond its original technology environment.

oneM2M and platform interoperability

ETSI is a founding partner of oneM2M, an initiative developing specifications for IoT platforms. The goal is to support connections between devices and services regardless of the underlying technology. The platform approach includes deployment options such as cloud or enterprise systems, gateways, edge devices and user devices.

In 2018, oneM2M Release 3 focused in part on interworking between industrial technologies and improved support for mobile IoT technologies standardized by 3GPP. The release also included a common interworking framework, security enhancements, transaction management and conformance tests and tools for developers.

One notable area was semantic interworking between proprietary technology “islands.” In practice, this addresses a challenge familiar to automation projects: systems may be able to communicate at a basic level but still use different meanings or structures for the information they exchange. A common framework can help bridge those differences, particularly where applications span multiple domains.

Shared meaning for industrial data

Interoperability depends not only on moving data but also on describing it consistently. ETSI’s SmartM2M committee worked on SAREF, a smart applications reference ontology intended to help connected devices exchange information through oneM2M-compliant platforms. During 2018, SAREF’s applicability was extended to areas including industrial and manufacturing applications.

An ontology provides a structured way to describe concepts and relationships. In an industrial context, shared descriptions can help applications interpret information from different sources rather than treating every data point as an isolated value. This complements communication standards: the network carries the information, while shared models help define what that information represents.

ETSI’s work on Context Information Management addressed a related need: recording data with its source, meaning and accuracy, then transferring it without misinterpretation. The NGSI-LD specification defined an API for applications to provide, consume and subscribe to context information across different scenarios and stakeholders. Its use of relationships between entities offers a way to describe connected “things” and their context, rather than relying only on disconnected data fields.

Security must be part of the architecture

As industrial devices and services become more connected, security and privacy are important considerations alongside interoperability. Standards work described in the 2018 report included security specifications for distributed systems and guidance on cyber defence. Attribute-Based Encryption, for example, was addressed as a way to combine access control with encryption to protect personal data in distributed environments such as IoT systems.

Other work focused on security monitoring and management. ETSI’s Information Security Indicators group published specifications addressing organization-wide security information and event management, along with indicators for assessing the maturity of security event detection tools and processes. These activities underline the need to consider not only device protection but also how security events are monitored, investigated and managed across an organization.

For automation decision-makers, the source does not prescribe a particular security design for a plant. It does, however, show that security concerns are being addressed across standards activity, from data protection and system interfaces to monitoring and incident response.

Applying standards in automation projects

Standards do not remove the need for engineering decisions. They can, however, give project teams a shared foundation for evaluating integration choices. When planning a connected system, consider:

  • Interfaces: Identify how devices, gateways and platforms exchange information, including how systems interwork across technology boundaries.
  • Data meaning: Check whether information models or shared descriptions can help applications interpret data consistently.
  • Deployment: Consider where platform functions reside, including cloud, enterprise, gateway or edge-device options.
  • Security: Include data protection and security monitoring in the architecture, rather than treating them as separate from connectivity.
  • Conformance: Use applicable tests and developer tools to help assess whether implementations meet relevant specifications.

The appropriate standards and implementation choices depend on the application and systems involved. The value of a standards-based approach is that it gives organizations a common reference point as they bring together devices, data and services.

Conclusion: design for connected operations

Industrial IoT standards address several connected requirements: communication between systems, interoperability across technology domains, consistent interpretation of data and security. Initiatives such as oneM2M, SAREF and NGSI-LD illustrate different parts of that foundation, from platform interworking to shared information models and context management.

For industrial automation teams, the practical implication is to treat standards as part of system architecture and integration planning. A connected operation depends not just on devices being online, but on systems being able to exchange information reliably and understand what it means.

Access Official Technical PDF

About The Author