Travis Cox from Inductive Automation, Arlen Nipper from Cirrus Link Solutions, and Tom Hechtman from Sepasoft present a variety of IIoT architectures utilizing the Ignition platform and the MQTT protocol that can supercharge your applications, get your enterprise more connected, and help you do more with your data.

2. Presenter
Travis Cox
Co-Director of Sales Engineering,
Inductive Automation

3. Agenda
• Introduction to Ignition, Sepasoft & Cirrus Link
• Where and How to Implement IIoT
• MQTT and Other Common Elements
• Three IIoT Use Cases:
○ Companies Getting Into Industry 4.0
○ OEMs Providing Services to Remotely Troubleshoot
Machines
○ Corporate MES
• Conclusion/Q&A

4. About Inductive Automation
• Founded in 2003
• HMI, SCADA, MES, and IIoT software
• Installed in 100 countries
• Over 1,700 integrators
• Used by 48% of Fortune 100 companies
Learn more at: inductiveautomation.com/about

5. Used by Major Companies Worldwide

6. One Universal Platform for HMI/SCADA, MES & IIoT:
• Unlimited licensing model
• Cross-platform compatibility
• Based on IT-standard technologies
• Scalable server-client architecture
• Web-based & web-managed
• Web-launched on desktop or mobile
• Modular configurability
• Rapid development & deployment
Ignition: Industrial Application Platform

7. Co-Presenters
Tom Hechtman
Founder and
President, Sepasoft
Arlen Nipper
CTO and Co-Founder,
Cirrus Link Solutions

8. • Incorporated in 2003
• 600+ MES implementations worldwide
• 200+ companies use Sepasoft software
• 27 MES-Certified System Integrator companies
• MES solutions for automotive, pharmaceutical,
food & beverage, mining, steel, other industries
• MES solutions for batch, discrete and continuous
type manufacturing operations
• Inductive Automation Strategic Third-Party Module
Partner for MES Modules
About Sepasoft

9. • Founded in 2012
• Over 30 years of SCADA and Telemetry experience
• Creates industrial software focused on
implementing MQTT applications and architectures
bridging the gap between OT & IT
• Integral in the creation and continued growth of
the MQTT protocol
• Developed Sparkplug specification and contributed it to
Eclipse Foundation, now part of Eclipse Tahu project
• Inductive Automation Strategic Third-Party
Module Partner for MQTT and Cloud Modules
About Cirrus Link Solutions

10. Most manufacturers understand why they should
implement IIoT solutions (get far more data, at far
greater speeds, far more efficiently), but they often
struggle to answer how and where …
The Industrial Internet of Things

11. Practical challenges and concerns like these often slow down IIoT
projects – or stop them altogether.
• Extremely high costs
• Maintenance
• Security
• Lack of IT infrastructure
• Legacy devices still in use
• No effective way to move data to a central location
• Separate control networks
Common Obstacles

12. • Despite the obstacles, there are proven ways to build cost-
effective enterprise IIoT applications.
• Today we will look at three different IIoT architectures based on
actual use cases.
• Get more power out of applications, get the enterprise more
connected, and do more with data.
• Commonality: All three solutions utilize the Ignition platform and
the MQTT protocol.
Proven Solutions

13. • De facto standard messaging protocol for IoT
• Very low bandwidth
• Reporting by exception
• Bidirectional
• Stateful awareness
• Secure (TLS)
• Single source of truth
MQTT Benefits

14. By leveraging MQTT on the Ignition
platform, you can:
• Decouple devices from
applications
• Push polling to the edge of
the network
• Make data instantly accessible
to the entire enterprise without
straining bandwidth
Ignition and MQTT

15. From Coupled to Decoupled

16. From Coupled to Decoupled

17. • Installing full solutions at each location would get very expensive
• Instead, you can bring info from other locations up to a central system
• We’ll show you architectures that allow you to do this cost-effectively
Affordably Leverage Data From Multiple Sites

18. • Edge gateways bridge legacy devices to new devices or to MQTT
• Adding even a few edge gateways can provide a lot of value to your
existing architecture
• Add edge gateways at other sites to enable complete solutions for
OEE and other applications
Add Edge Gateways

19. • Sepasoft MES supports zero gaps in OEE data
• MQTT Transmission Module supports store-and-forward
functionality
• MQTT modules support notification of historical tag value updates
MQTT-MES Integration

20. Three IIoT Use Cases
1. Companies Getting Into Industry 4.0 (Arlen)
2. OEMs Providing Services to Remotely Troubleshoot Machines
(Travis)
3. Corporate MES (Tom)

21. • Large manufacturing company with many plants around the world
• Wanted access to data in order to participate in Industry 4.0
• Tightly coupled architecture
• 80%-90% of machine data stranded in machines
1. Companies Getting Into Industry 4.0 – The Problem

22. Machine 1
Machine 2
Machine 3
Machine “n”
Polling
Engine
Protocol A
Protocol B
Protocol C
Protocol “n”
Operations
(SCADA)
MES
Cloud
Services
On Premise
Machine
Learning
Lambda’s
?
?
?
1. Companies Getting Into Industry 4.0 – The Old Way

23. 1. Companies Getting Into Industry 4.0 – The Solution

24. Three IIoT Use Cases
1. Companies Getting Into Industry 4.0 (Arlen)
2. OEMs Providing Services to Remotely Troubleshoot Machines
(Travis)
3. Corporate MES (Tom)

25. • This OEM makes machines that other companies use as a critical
part of their manufacturing process.
• Customers lack the deep expertise to troubleshoot the machines.
• The OEM is trying to troubleshoot their machines remotely, but
their old way of doing that had many flaws.
2. OEMs Remotely Troubleshooting Machines – The Problem

26. 2. OEMs Remotely Troubleshooting Machines – The Old Way

27. 2. OEMs Remotely Troubleshooting Machines – The Solution

28. Three IIoT Use Cases
1. Companies Getting Into Industry 4.0 (Arlen)
2. OEMs Providing Services to Remotely Troubleshoot Machines
(Travis)
3. Corporate MES (Tom)

29. • Large company running OEE across many locations
• Putting in full OEE at each site is a non-starter so they deployed
an OEE solution at a corporate location
• Corporate OEE directly connected to controllers
• Losing connection means losing OEE data — and the system
loses credibility
3. Corporate MES – The Problem

30. Solution #1 - Before3. Corporate MES – The Old Way

31. Solution #1 - After3. Corporate MES – The Solution

32. Demo: Filling In OEE Data Gaps

33. • Decouple intelligent devices from applications with Ignition & MQTT
• Bridge old & new technologies using edge gateways
• Leverage data & resources efficiently across multiple sites
• Fill in data gaps with tightly integrated MES modules & MQTT modules
• Plug-and-play, self-learning technology makes expansion easy and saves
vast amounts of time
• Practical migration strategy for existing resources
• Leverage machine learning & analytics for better performance & decision-
making
Recap

34. To summarize, do you have any closing comments about
building practical IIoT solutions?
Closing Discussion

35. Inductive Automation
inductiveautomation.com
1-800-266-7798
Cirrus Link
cirrus-link.com
844-924-7787
Sepasoft
sepasoft.com
800-207-5506
To Learn More

37. Sept. 17-19, 2018
Virtual Tickets on sale at:
icc.inductiveautomation.com

38. Jim Meisler x227
Vannessa Garcia x231
Vivian Mudge x253
Account Executives:
Myron Hoertling x224
Shane Miller x218
Ramin Rofagha x251
Maria Chinappi x264
Lester Ares x214
Call us at:
800-266-7798
Co-Presenters
Tom Hechtman: tom.hechtman@sepasoft.com
Arlen Nipper: arlen.nipper@cirrus-link.com
Director of Sales: Melanie Hottman x247
Kristen Azure x260
Questions & Comments