|[iot-wg] Sparkplug Working Group initial call - December 3, 2019 @ 9am Pacific/ 12pm Eastern / 7pm Central Europe|
Hold this date for the Webinar: Tuesday,
December 3rd at 9am Pacific / 12:00pm Eastern / 7pm Central Europe
The initial call of the brand new Eclipse SparkplugÂworking group is on December 3rd, and you are invited!ÂPresenters on this webinar will include Arlen Nipper from Cirrus Link, Kevin McClusky from Inductive Automation,Todd Anslinger from Chevron, and Paul Buck from the Eclipse Foundation. During the call, you will learn what we have in store for the Eclipse Sparkplug specification and the Eclipse Tahu project.
To join the call, simply use the following Zoom link:Âhttps://eclipse.zoom.us/j/656188548
It is pretty incredible to realize the adoption of MQTT Sparkplug by the ecosystem of OEM device manufacturers, solution providers and customers that has emerged in the span of just two and a half years since its first release.
The Sparkplug specification and associated reference implementation code have been open source from the day that Cirrus Link released it and made it available on GitHub.ÂFor some in this community, you already know that the Eclipse Paho project is the starting point for the majority of all MQTT development projects across the world. Inductive Automation are the leading contributors into the Eclipse Milo project, one of the few open source implementations of OPC-UA. Therefore, the Eclipse Foundation was a perfect fit for the future of the Sparkplug specification and in July of 2018, Cirrus Link contributed the entire IP portfolio of the Sparkplug specification along with the reference implementation code to open source at the Eclipse Foundation.
The Eclipse Foundation used the initial contribution of the Sparkplug IP to establish the Eclipse Tahu project where the Sparkplug specification and reference implementation code now reside. The next step is to create a Sparkplug Working Group.
The Sparkplug Working Group will promote the "Sparkplug" brand and its value in the marketplace by creating a Sparkplug compatibility logo program and promote the logo. OEMs that fully implement the specification and pass the associate TCK (Test Compatibility Kit) will be entitled to use the logo and trademark on their products and in their marketing materials. Consumers of Sparkplug compatible branded products will have the confidence that the devices and software can be used in their environments and will integrate with their MQTT infrastructure.Â
As explained in the charter, Steering Committee will be established to provide direction to the Sparkplug specification project and the Eclipse Tahu open source project. It will also provide direction on which verticals to focus on and establish and drive a funding model that enables this working group and its community to operate on a sustainable basis.
A Marketing Committee will be established to promote the brand, drive initiatives toÂeducate consumers of the value of using the Sparkplug protocol and OEMs the opportunity of supporting Sparkplug in their devices. This is an area that will require funded initiatives.
The Eclipse Foundation has a robust specification process that will be applied to manage updates to the Sparkplug specification and provide the IP framework required for broad commercial adoption of the specification.Â
Since the release of the Sparkplug B
specification, Cirrus Link has received a large amount of feedback on
additional features and capabilities that customers, OEM device manufacturers,
and solution providers would like to see incorporated into Sparkplug. With the
formation of the Tahu project and the Sparkplug working group, now there is an
open venue to propose, discuss, and implement these new features and
I would like to invite anyone currently using or interested in MQTT and/or Sparkplug to attend this webinar to learn about Tahu and the Sparkplug Working Group and get involved in the future of modern IIoT technology! To stay up to date on the latest developments and activities I would also like to invite everyone to join the Sparkplug Working Group Mailing List: