2. 20-Year Anniversary of the Genesis of MQTT
Andy Stanford-Clark
CTO-IBM UK
Arlen Nipper
President and CTO - Cirrus Link

3. ( or how Andy and Arlen were planning for world domination ….. )
The MQTT Story
( or how Andy and Arlen were planning for world domination ….. )
Arlen
Andy
Arlen had been in the SCADA/protocol industry for 20 years prior to working on MQTT. Short background of Arlen’s experience to this point.
Andy had been in IT for ?? years prior to working on MQTT. Short background on Andy’s experience to this point.
The ultimate in OT/IT convergence.
MQTT

4. The opportunity Consumers Data Producers SCADA Flow Computers
PLCs/RTUS
Steve Koenig at Phillips 66 wanted a “Better Way” to utilize his new TCP/IP based VSAT system.
Both Arcom Control Systems and IBM were engaged with Phillips 66 on different projects.
We should also mention the valuable contribution of Sherman Blalock at Williams Energy

5. The Argo Project (circa 1998)
Tim Holloway was an IBM Fellow at the Hursley Lab in the UK. He was formulating a vision of how Message Oriented Middleware could be applied to Operational Technology.

6. The Argo project

7. MQIowp kickoff meeting
Before doing any design we needed a Really Cool name!
OTWP - on the wire protocol
MQIowp - MQ Integrator on the wire protocol (????)
MQIsdp - MQ Integrator scada device protocol (??)
MQIPDP – MQ Integrator pervasive device protocol (?)
MQTT - MQ Telemetry Transport
After meeting with Tim initially I returned to Hursley when Andy got back from his US Olympics assignment and we had our first face to face meeting to kick of the development project. First thing is that we needed a name:
This is where Andy and Arlen first starting to compare notes on their previous industry experience and then try to figure out how to best combine it to meet the requirements for the Phillips 66 project.

8. Design Goals and Considerations
Simple
Efficient
Stateful
Open
MQTT is great because it left a LOT of stuff out!
Built on top of TCP/IP, not UDP.
Security was not defined.
No required Payload was specified.
Just discuss our initial development efforts…
Simple – it had to run on an 8bit microprocessor with 64KB of RAM
Efficient - each byte cost 5 cents. For some LEO/GEO VSAT installs this could result in $1M/year in cost saving.
TCP vs UDP – in 1998 most operations teams didn’t even know what TCP/IP was – we all still had RS-232 ports on our laptops!!!
Define a payload format or not
Ended up with a simple set of message transport VERBS: CONNECT, SUBSCRIBE, PUBLISH, PING, DISCONNECT
Stateful - Connection state was a must have and we figured out we could NOT rely on TCP/IP level socket state.
Open – If the spec had not been open we all wouldn’t be here today

9. First Implementations: Christmas Lights, MQTT Mousetraps, Tweeting Ferry

10. The 10th Anniversary Party
Nick, Dave, and Ian have all continued to contribute to the MQTT ecosystem….
More on what Nick O’Leary and Dave Conway-Jones have developed later in this presentation.

11. Standards and Tools
This is where MQTT really started to gain traction….
Roger Light developed Mosquitto – first open source implementation of an MQTT Server
Scott de Deugd from IBM was a key individual that kicked off both the Eclipse Paho project as well as getting MQTT into the OASIS standards organization.
Node-RED started life in early 2013 as a side-project by Nick O’Leary and Dave Conway-Jones of IBM’s Emerging Technology Services group.
HTTP and HTML help fuel the internet of people….. MQTT and Sparkplug is fueling the IIoT

12. MQTT 5.0
Backwards compatibility Additional capabilities….. Andy take it from here

13. Cirrus Link Ignition Modules
MQTT Distributor Module
MQTT Engine Module
MQTT Transmission Module
EFM Emerson ROC
Module
AWS Injector
Module
Azure Injector
Module
I’ll just go thru a brief description of each of our modules.
Do we want to include RECORDER and/or EXPORTER ??

14. Sparkplug goes to Eclipse Tahu
The Open Source Eclipse Tahu project consists of three major components:
The Sparkplug Specification
Client library implementations initially in the following programming languages: C
Java
JavaScript
Python
Reference implementations of Sparkplug applications using the client libraries.

15. New Modules & Features EFM Emerson ROC Module MQTT Recorder Module
MQTT Transmission now let’s customers create custom RECORD objects.
MQTT Engine now exposes historical tag history to other registered Ignition modules. This was developed for the SepaSoft MES suite.

16. Putting it all together – from Chip to Cloud to Application The IBM Watson IoT ecosystem helps companies build and deploy IoT end to end

17. IBM Watson Internet of Things

18. Watson IoT Platform

19. IBM Watson IoT and Industry Innovation Enabling new business models with integrated solutions built on Watson IoT Platform