|Home||Internet of Things||Aerospace||Apparel||Energy||Defense||Health Care||Logistics||Manufacturing||Retail|
Working Group Planning Open IIoT Standard
The Eclipse Foundation has launched a working group for the Industrial Internet of Things software standard known as Sparkplug, to ensure the interoperability of IoT systems for energy and gas, automotive and other industrial users.
Feb 17, 2020—
The Eclipse Foundation, an Internet of Things (IoT) open-source software organization, has formed a new working group for the Industrial Internet of Things (IIoT), consisting of end users and technology companies. This open-source group is focused on the Sparkplug specification to make IIoT deployments interoperable for companies in the oil and gas, energy and manufacturing sectors, as well as other industrial sites, and for smart cities.
The Eclipse Foundation, an Ottawa-based, international open-source software non-profit organization, was formed in 2004 to serve as a vendor-neutral, open and transparent community, first for a development tool known as Eclipse IDE. Its working group's founding members include Chevron, security device company Canary, IoT solution providers Cirrus Link and ORing, IoT messaging platform provider HiveMQ and software firm Inductive Automation.
The Sparkplug Working Group will define technical specifications and improve the interoperability and scalability of IIoT solutions, according to Frederic Desbiens, the foundation's IoT and edge-computing program manager. By doing so, he says, the group can provide an overall framework for device interoperability "out of the box" for IIoT products and software. The working group meetings will be virtual.
Sparkplug, originated by Cirrus Link, is designed to work with MQTT, a protocol commonly used in IoT deployments designed for users to create topics for which data can be stored and managed. It has close to 400 open-source projects currently under way, Desbiens says. The Sparkplug open-source specification will provide IoT solutions with a topic name space for IoT data (where data is stored and managed), a payload for each name space, and session management for users of the MQTT protocol widely used in IoT deployments.
In the example of a warehouse using UHF RFID readers to capture ID numbers from tags placed on inventory, the topic name space is the assigned space for data storage (such as inventory management), while the payload is the carrying capacity of that data unit. By assigning name space and payload, the system automatically directs data to the appropriate space and knows what that storage space consists of.
Login and post your comment!
Not a member?
Signup for an account now to access all of the features of RFIDJournal.com!
SEND IT YOUR WAY
RFID JOURNAL EVENTS
ASK THE EXPERTS
Simply enter a question for our experts.
|RFID Journal LIVE!||RFID in Health Care||LIVE! LatAm||LIVE! Brasil||LIVE! Europe||RFID Connect||Virtual Events||RFID Journal Awards||Webinars||Presentations|