IoT Track and Trace Standard Developing

Oct. 17, 2018
Emerging from the Industrial Internet Consortium’s Track and Trace Testbed is a set of requirements for a vendor-independent metamodel for data generated by hardware sensors.

Photo: Bosch's Dirk Slama (left) and the IIC's Dr. Richard Soley at the IoTSWC 2018 event.

The Industrial Internet Consortium’s (IIC) Testbeds address a variety of industrial applications, from bleeding edge ideas still under development, like deep learning, to ideas that have become standards with products hitting the market, like Time Sensitive Networking. As such, the testbeds have always figured prominently into the IIC’s annual Internet of Things Solutions World Congress (IoTSWC), and this year was no exception.

Richard Soley, executive director of the IIC, said at the lastest event that because it’s clear no single company will win the IoT race alone, the IIC’s testbeds play a key role in establishing future technology standards and driving multi-vendor interoperability. "And the requirements for a new IoT standard have just been generated by the Track and Trace Testbed,” he added.

The requirements for this standard can be found in the “Simple Electronic Notation for Sensor Reporting (SENSR)” RFP created by the Object Management Group, which manages the IIC. The RFP solicits proposals for a metamodel suitable for describing serialized data streams emitted by sensors, and how that data should be interpreted. The metamodel envisioned will allow the production of tools to enable automated, unambiguous interpretation of the emitted sensor data through configuration of a system, or production of code for execution.

The testbed began as an application for power tool fleet management and forklift tracking in manufacturing facilities, said Dirk Slama, director of business development at Bosch Software Innovations, which is a member of the Track and Trace Testbed along with Cisco and SAP. Bosch wanted to have this tracking capability across its 270 factories worldwide to locate equipment, and to extend this capability to its suppliers and customers, Slama added.

Through work done in the testbed, the participants realized sensor manufacturers needed to be able to publish the required interpretation of their data via an electronic data sheet. With this need in mind, the RFP seeks specification proposals that provide a platform and vendor-independent metamodel for describing available data provided by hardware sensors, as well as an optional library of data types to facilitate the sharing of interpretations.

This RFP was published “to have sensor vendors work together to really make this [capability] plug-and-play and move [it] beyond the testbed,” said Soley.

The IIC currently maintains more than 40 relationships with government entities, standards bodies and open-source organizations, such as AVNU, EdgeX Foundry, IOTA, IEEE, ISA, MESA, OASIS and Plattform Industrie 4.0, to advance the work of the testbeds into standards and widely available technological capabilities, Soley said. As an example of what these relationships produce, he referenced IIC’s recent work with the Eclipse Foundation on the Production Performance Management Protocol (PPMP) to create a lightweight protocol based on JSON.

According to the Eclipse Foundation, machine data is currently provided via modern protocols such as OPC UA or proprietary access methods, but it is not provided in a common and easily accessible format that can do performance analysis and optimization. This makes holistic process improvement unfeasible for many organizations, especially smaller ones. The PPMP specifies a format that allows capture of the data required to do performance analysis of production facilities. It allows monitoring of backends to collect and evaluate key metrics of machines in the context of a production process.

PPMP is recognized by Microsoft Azure along with with OPC UA and Profinet, and is currently being used by manufacturing micro testbeds from the IIC’s German regional team, Soley said.

About the Author

David Greenfield, editor in chief | Editor in Chief

David Greenfield joined Automation World in June 2011. Bringing a wealth of industry knowledge and media experience to his position, David’s contributions can be found in AW’s print and online editions and custom projects. Earlier in his career, David was Editorial Director of Design News at UBM Electronics, and prior to joining UBM, he was Editorial Director of Control Engineering at Reed Business Information, where he also worked on Manufacturing Business Technology as Publisher. 

Sponsored Recommendations

Rock Quarry Implements Ignition to Improve Visibility, Safety & Decision-Making

George Reed, with the help of Factory Technologies, was looking to further automate the processes at its quarries and make Ignition an organization-wide standard.

Water Infrastructure Company Replaces Point-To-Point VPN With MQTT

Goodnight Midstream chose Ignition because it could fulfill several requirements: data mining and business intelligence work on the system backend; powerful Linux-based edge deployments...

The Purdue Model And Ignition

In the automation world, the Purdue Model (also known as the Purdue reference model, Purdue network model, ISA 95, or the Automation Pyramid) is a well-known architectural framework...

Creating A Digital Transformation Roadmap Using A Unified Namespace

Digital Transformation has become one of the most popular buzzwords in the automation industry, often used to describe any digital improvements to industrial technology. But what...