In 2022, Döhler South Africa realized they were reaching capacity in their production facility, an impasse that countless growing companies have reached. The question always becomes: make do with too-cramped quarters or invest in a long-term solution?

Döhler — a multinational company that manufactures fruit juices, compounds, flavors, emulsions, and concentrates — chose the latter for their new facility, which specializes in blending and secondary transformation. Located in Paarl, South Africa, the new plant adds tenfold capacity while remaining scalable. “We had to really plan for the future and really give ourselves the capability to grow,” said Dirk Brand, Head of Engineering at Döhler South Africa. “Not only for the next three years, but for the next ten years.”

Integration for a project of this size and complexity has the potential to become a game of compromise, but with the help of INTEG System Integrators, Döhler South Africa successfully implemented a massive manufacturing system built in Ignition — the unlimited industrial automation platform for SCADA, MES, IIoT, and more — that balances a staggering amount of functionality with an intuitive interface.

Greenfield Development

While the sheer scale of this greenfield project might make some blanch, INTEG viewed this as an opportunity to build from a clean slate. “We could start from the beginning and develop the project like we wanted to, in essence,” said Brian Cooper, Managing Director at INTEG. “On a brownfield project, it's difficult to do that. You've got existing standards, you've got existing equipment, and it makes it difficult.”

While the project requirements remained fairly consistent throughout, on a more granular level there were, inevitably, changes every day. “How we thought it was going to work versus how it actually worked at the end were two very different processes,” said Brand.

“During commissioning, it became apparent how easy it is to make changes on the fly and build new functionality within the SCADA system very quickly,” said Tean Butler, Technical Manager at INTEG.

Now complete, the Ignition system — built from the core combination of Ignition’s Perspective, Tag Historian, and Reporting modules along with Sepasoft’s Batch Procedure Module and the Canary Historian — boasts approximately 1.2 million tags on two gateways, as well as sophisticated batching, navigation, interlocking, and ID generation systems.

Architecture

INTEG originally considered a standard Ignition architecture on a single gateway. However, it quickly became evident that the system — which encompasses around 200 routes, 2,000 phases, and 400 equipment modules for 1,800 control modules — required some additional architectural complexity.

The system features a load-sharing, bifold structure to match the plant’s two sections, each with their own separate gateway, tag provider, and Siemens S7-1500 1518 PLC. The first gateway acts as a hub, running Perspective and housing over 600,000 tags, while the second, a “headless” spoke gateway, has over 500,000 tags. Even with Ignition's unlimited licensing model, a tag count this high requires certain considerations. All of those tags are document text exposed within the User-Defined Type (UDT) structures to allow easy access and increased flexibility with the Siemens PLCs.

ISA 88-Compliant MES

Batching integrates everything in the plant. Using Sepasoft’s Batch Procedure Module as the engine, INTEG developed the MES solution to the exacting standards of the food and beverage industry. “We were quite adamant on using a strict ISA 88 standard,” said Brand.

With an ISA 88-compliant project of this size, it was vital to build the plant according to a set standard, which led INTEG to develop an ID generation system. “The ID generation system was built using Ignition and a database system that helped us to always provide a unique code or unique identifier to each and every single component,” said Butler.

The ID generation system works based on an ownership model to ensure proper interlocking throughout the plant, from general capabilities down to phases, then equipment, and finally to control modules. Because every component in the system has a discrete ID, when an operator runs a batch, the system makes all associated equipment unavailable for any other processes.

Döhler’s plant does not function conventionally via SAP recipes; operators have the flexibility to run batches when needed. Each order comprises several batches as it progresses through the plant, the last of which being the transfer to the shipping truck for delivery. “In order to proceed from one station to another, a batch has to be completed,” said Butler. “One new batch cannot start before a previous batch has been executed.”

Every batch must pass quality control (QC) before moving onto the next process, and equipment must be Clean-In-Place (CIP) before it can be used again. To prevent any batches from starting without proper QC and CIP, INTEG used Ignition’s host of scripting functionalities to implement a sophisticated interlocking system.

“As part of the batching standard that we've developed, we've also implemented a unit state,” said Cooper. “The unit state determines whether the equipment is dirty or clean or being washed or CIP'd, and that is used to interlock specific systems or specific equipment.” The batching system makes cleaning in place exceptionally easy because Döhler can create a recipe to run against the CIP process. The Batch Procedure Module collects this information, recognizing which recipes are linked, and then displays the correct recipe for the operator. This, along with the interlocking that extends down to the control-module level, provides the operator with full visibility of the entire plant from the batching engine.

“Everything is linkable. Everything is trackable,” said Brand. “It really does make their life easier.”

Navigation

Döhler’s staff needed an intuitive method for navigating a system this large and complex. INTEG developed the interface with the simple conceit that an operator should be able to reach any part of the system in three clicks. To accomplish this, they implemented what they dubbed the “breadcrumb” system. “The breadcrumb is an easy way of taking you exactly to that specific area,” said Cooper. “It's developed in a logical way, so if you just know the plant and you know where you wanna go, the breadcrumb would easily take you there.”

This type of quick navigation lends itself naturally to acknowledging alarms. Integrating the breadcrumb system with Ignition’s Alarm Notification Module, INTEG created an easy way for operators and maintenance staff to pinpoint alarms. From the system homepage, operators can simply click on the notification in the header, then filter down through the sections of the plant, following visual indicators to specific areas and process cells.

Alternatively, if operators already know what they’re looking for, they can use the search function. The system follows ISA 95 naming conventions, so by either entering the control module prefix or copying and pasting parameters, operators can quickly scan through the available equipment.

High-Performance HMI

During the commissioning phase, Döhler was unsure whether the plant would have a dedicated control room or field-mounted stations. Ultimately, they opted to forgo a large control room, a decision that greatly influenced the HMI design.

With operators not tied to a central area, INTEG aimed to heighten situational awareness with a high-performance HMI. The grayscale palette reserves color for events or notifications that require immediate attention. “It's easy to build a lot of P&ID pictures and confuse the operators,” said Cooper. “So we developed different layers.” As operators drill down through the layers, they go from overview tiles and simple routes to detailed P&ID-style views, giving individual operators the ability to decide which style works best for them.

“You have buttons and options and menus for everything, but the learning curve was a lot shorter than what I imagined it would be,” said Brand. “Operators pick it up quite quickly.” The Ignition HMI standardizes the look and feel across the whole plant, allowing operators to move from one process to another easily. That flexibility extends to process improvement, letting Döhler add new screens to the Ignition application without restarting or reinstalling the system.

Historical Data And Trending

As with any MES application, historical data and traceability are paramount. Using Ignition, Döhler has complete visibility of their data and the tools to perform root-cause analysis. “It's quite easy now to, within the click of a few buttons, know the exact origin of the problem, the resolution of the problem, and what was done to fix it,” said Brand.

This historical data can also be put to more immediate uses like trending. “We realized that it is necessary for operators to be able to pull up trends easily from the user interface,” said Butler. The system allows operators to access the trending tool from any control module faceplate and easily add values from the same pop-up.

Linguistic Diversity And Symbols

South Africa is host to a huge amount of linguistic diversity, with twelve official languages and at least thirty-five languages spoken in the region. In Paarl and the Western Cape area, there are only three dominant languages, but English — which is used exclusively in Döhler’s Ignition system — would still likely be a second language to much of the company’s staff.

Even without this linguistic hurdle, there is an inherent learning curve for a system with this many moving pieces (not to mention routes for moving those pieces). INTEG sidestepped this potential issue by including symbols throughout the screens to clearly indicate each piece of equipment’s capabilities. “Symbols really helped ease the transition for a lot of the operators,” said Brand. “Something like a mixed proof valve might not be something that's familiar to all the operators, but a picture of a valve makes it clear.”

Maintaining consistent symbols from screen to screen has made it simple for operators to connect the physical plant floor with the representation on the HMI. “The operators picked up on a complex system very easily,” said Cooper. “They, in a short period of time, were able to operate the plant and get product out the door.”

A Communal Success

The success of Döhler’s new facility was truly a group effort. “What really impressed me about the INTEG project team is their product knowledge. The experience with similar plants and similar processes, how proactive they were in identifying potential problems and solving [them] before it becomes a problem,” said Brand.

Likewise, INTEG appreciated the two-way communication during development. As Cooper said of Döhler, “They are knowledgeable people. They gave us feedback and input on control philosophies, on control narratives, and on the methodologies that we used to develop this batching system.”

In addition to technical assistance from Inductive Automation, the project also received support from Element8, the Authorized Ignition Distributor for Sub-Saharan Africa. Butler said, “Any project such as this will encounter technical difficulties, but they had our back all the way.”

With scalability built into the system, Döhler is already looking toward future improvements. “There's almost no limit to what Ignition can offer a client,” concluded Butler, adding that Ignition “makes it easy for developers to express themselves more deeply within the SCADA systems.”

Project Scope

• Start Date: March 2023
• Deploy Date: Phase 1: December 2023, Phase 2: May 2024
• Tags: 1,200,000+
• Screens: 80
• Clients: 7
• Alarms: 6,400
• Devices used:
  • Two Siemens S7-1500 1518 CPU
  • 600+ ASi-Valves
  • 200+ IO-Link Instruments
  • 200+ Profinet Remote IO
  • 70+ Flowmeters and Drives
• Architectures used: Hub & Spoke
• Databases used: PostgreSQL for access control, trending tool and materials library. NoSQL for historical data logged.
• Historical data logged: 30,000

Next to the robotic arms, the off-the-shelf miniature smart homes may not appear to be a key part of Clovis Community College’s Automation, Robotics & Mechatronics lab, but this unassuming hardware is providing students and instructors alike with a unique opportunity to build industry-grade automation applications.

Located in Fresno, California, Clovis Community College is well-regarded for its high transfer rate to four-year institutions. Now, by incorporating Ignition into its curriculum, Clovis is giving students in its Automation, Robotics & Mechatronics program the tools to develop a multifaceted skillset suited to both future higher-learning endeavors and local industry.

Project Development

Matthew Graff, Instructor of Automation, Robotics & Mechatronics at Clovis, was approached by a colleague from Texas A&M University about a grant from the National Science Foundation (NSF) to train high school and college students, as well as instructors, about technology related to the Fourth Industrial Revolution. And, unlike programs that are only able to offer exposure to these concepts, this NSF funding would allow Graff to pay his student researchers.

Graff developed what has been dubbed the “Industry 4.0 Project.” The idea was simple: combine Inductive Automation’s Ignition software — an industrial automation platform for SCADA, HMI, IIoT, and more — with accessible hardware so that students could see immediate real-world results and be inspired to pursue careers in automation.

While developing this curriculum, Graff took inspiration from Walker Reynolds' idea of creating a Unified Namespace (UNS) using a Raspberry Pi. “The idea of using really cheap hardware, Raspberry Pi and Arduinos, to run industrial software made a lot of sense for us in the project,” said Graff. “​​We wanted something that would be very much hands-on.”

There was just one problem — Graff had no background in working with Raspberry Pis, so he reached out to Bill Kerney, Computer Science Instructor at Clovis. While Kerney describes himself as “not an Ignition user,” his expertise with Linux provided a complementary skillset. “My role here was as an advisor,” he said. “I was here to supervise the student workers on the project, and so when they got stuck figuring out how to do something, then it was my job to unstick them.”

Educational Engagement Program

While Graff had an easy time acquiring the hardware for the project, budgetary constraints prevented him from purchasing full Ignition licenses. Originally, the labs used Ignition in free trial mode, resetting the license every two hours.

When Graff, who has had frustrating experiences with other software companies, learned about Inductive Automation’s Educational Engagement Program (EEP), he sent an email without expecting much, but was surprised to receive a prompt response. “I just got on the website and said, ‘Hey, I'm interested,’ and within a week, we were talking, person to person,” Graff said. Beyond the licenses, the EEP connected him with experts at Inductive Automation to ensure the Industry 4.0 Project met industry standards.

Graff felt his experience was based on a shared ethos. “There's an understanding from Inductive Automation that there's a need to train employees, and they see us as partners,” he said.

Industry 4.0 Project

In the Industry 4.0 Project, students develop an Ignition system that controls a miniature Keyestudio IoT smart home through a combination of a Raspberry Pi and ESP32 Arduinos. Students first set up an MQTT broker using Cirrus Link’s MQTT Transmission Module, which they connect to their edge devices, meaning the smart homes. Next, students establish a UNS, following the ISA-95 standard, to connect to the MQTT broker. Once all the edge devices are publishing to the specific topics, students use the MQTT Engine Module to subscribe to those topics and bring the data into Ignition, creating tags. With these tags, students can build Perspective views and dashboards to display the real-time data.

The system is built in Perspective, meaning that when Graff gives demonstrations for high school students, he can have the class scan a QR code to gain immediate access to the application through their phones, upending the typical “no phones in class” rule. As Graff sees it, “I think a lot of times, there's the difficulty of how we make technology used for a positive thing.”

And with the combination of Ignition and smart homes, the positive results arrive quickly. “They can open up the box and hopefully within a class period, 45 minutes or an hour, have something working. They're pushing buttons and seeing responses. And so in that, immediately, they're learning some basic things like setup, using the Unified Namespace,” said Graff.

The collegiate counterparts replace the Raspberry Pi with more professional hardware, courtesy of Opto 22. The combination of Ignition and Opto 22’s groov RIO has been inspiring to the Clovis students. “Computer science majors oftentimes will live in this sort of platonic world of ideals and algorithms that are very abstract,” said Kerney. “Getting them to actually turn a motor on or to turn a light on or to open a door is oftentimes just a mind-blowing experience for them.”

Julian Laxamana, a student researcher working on the Industry 4.0 Project, found the ability to bring his programming into a tangible realm extremely gratifying. “It's really easy to have all your data in one place, which is really nuanced because if you make it by scratch, you have to have each computer send data, and you have to get it to show up on some GUI, which is really hard to get set up. But Ignition makes that a lot easier to link up all the data from the sensors to the computer,” said Laxamana.

Laxamana, who had no previous Ignition experience, also integrated the Ignition system with a camera that analyzes its video feed in (almost) real time. “We currently use YOLOv8 to collect data from ESP32 cameras, process it through the Raspberry Pi, and then display it on a web page, which Ignition gets the data from.”

Graff, who has strived to make the Industry 4.0 Project a “student-centered teaching system,” was ecstatic to see his student taking initiative with Ignition, saying, “I just showed Julian a few things. And then the next thing I know, he's brought a video in with object detection that's run on another application.”

Kerney agrees that it’s exciting to see Ignition acting as a catalyst for students. “Most computer science majors, if you told them, ‘Make a smart house that the door opens and closes,’ and has all these sensors, they won't even know where to begin, but with Ignition in it they were able to get this whole system up and running in a pretty fast amount of time.”

Transition To Industry

Entering its second year, the Industry 4.0 Project has already led to real-world success for students.

Gurkaran Singh, a student worker at Clovis studying industrial automation, was one of the main driving forces behind the Industry 4.0 Project, but most of his experience came from working on the project itself. “Before I came to Clovis, I had limited experience in industrial automation. I had only done one PLC programming class, and I had never heard about MQTT or SCADA or Ignition,” said Singh.

Even without prior Ignition experience, between free resources like Inductive University and the Ignition user manual, Singh quickly discovered the breadth of functionality he could develop in the platform. “One thing I really liked about Ignition early on was how easy it was to download and set up on my own personal computer, to begin learning,” he said.

To gain a better understanding of the groov product line, Graff and Singh traveled to Opto 22’s headquarters in Temecula for a four-day training course. During the training, Singh learned about Farm Data Systems (FDS), an integrator specializing in agricultural automation and monitoring, utilizing a combination of Ignition and Opto 22 hardware. FDS uses its Water Informatics product to monitor and control irrigation for thousands of sites. “With Ignition, we've been able to really turn the corner for our customers in terms of giving them many systems and features that they've never had access to before. It's been quite revolutionary for our growers,” said John Williamson, President of FDS.

What piqued Singh’s interest was that FDS’ office was located in Madera, about a 40-minute drive from Clovis’ campus. With guidance from Graff, Singh emailed Williamson, expressing his interest in a job and citing his experience working with Ignition and Opto 22 products in the Industry 4.0 Project. Williamson was impressed and offered Singh a position, saying, “His career objectives were very much in line with what we were doing. So we met in person, and I already knew he could add value on day one. His training at college was really so well suited to the work we're doing here.”

Even in his first few months of employment, Singh is already helping Williamson to design Ignition interfaces based on customer requirements, configure PLCs, and build panels for field deployment in addition to daily concerns like alerts from customer sites. “My day to day over at Farm Data Systems includes configuring Opto 22 products for upcoming projects, monitoring alarms for the products that are already out in the field, trying to troubleshoot any networking issues that we face, and trying to help customers solve those problems,” said Singh.

“It's been really a remarkable experience for us to work with Ignition,” said Williamson. “The product that we bring to the market is just leaps and bounds ahead of anything anybody else can provide to help farmers do their job.”

Real-World Skills

The Industry 4.0 Project helps students build a foundation based on technical experience and critical thinking skills that are so vital in industry. Troubleshooting, in particular, can be the crux of any real-world system. “What we realized with this project is automatically just connecting a bunch of things using standard industrial protocols for Ethernet, there's a bunch of troubleshooting that has to happen even if everything's working,” said Graff.

The combination of software and hardware gives students the space to learn what to do when a system doesn’t work, which can be more valuable long term. “Using hardware, you have the opportunity to make more mistakes. It may be a wiring issue or it could be a software issue such as setting an incorrect IP address. It helps you gain a deeper understanding of the whole system,” said Singh.

Additionally, the project puts many of the automation and computer science concepts taught at Clovis into the context of a complete system. “While working in industrial automation, at some point, you're gonna come across a problem where you need to integrate different devices, using different communication protocols,” said Singh. “Ignition is a really useful tool, in bringing all those different devices from different protocols together and utilizing that data to store, analyze, and generate some useful insights, and even building HMI displays for control.”

“I see Ignition as being a Rosetta Stone, and that's how I describe it to students where it can translate and connect all kinds of components together in a factory,” said Graff.

Sharing This Knowledge

Over the past year, the Industry 4.0 Project has expanded to five other colleges and 10 high schools, with plans to include five additional colleges and seven more high schools in the coming year. For Graff, sharing the project with other schools is about reaching the next generation of engineers. “A lot of high school students don't realize there's jobs related to industrial automation, and they could go into the engineering or computer science pathway,” he said.

“We've had three software engineers working on this project. The first one, Neiro Cabrera, worked on this for about a year and then he transferred to UCLA and then he just recently messaged me and told me that he got a job in a related industry,” said Kerney. “An absolute success story. He worked on this. He got experience in it. He found he loved it.”

This sense of discovery is a sentiment that Singh echoes. “When I first joined the industrial automation program here at Clovis Community College, my career goal was to be on the plant floor,” he said. “Working with this project has exposed me to newer and emerging technologies and broadened my horizon and opened me to a lot more opportunities within the field.”

Clovis does not want to gatekeep this knowledge or technology. In an effort to increase the accessibility of the project, Graff and Kerney set up a Github page that details the hardware and software requirements for the project, along with instructions for configuring components as well as lab exercises and training materials. “We want to share everything we have here,” said Graff. “You can take this and use it in a classroom. Or if you're just someone that wants to have a fun automation project, maybe before you hook up your whole home to be a smart home, you can just get a little $55 home from Amazon and pay $100 for a Raspberry Pi, and you'll be set to go.”

Learn more about Inductive Automation's educational initiatives in the blog post "IA’s Efforts To Shape The Future Of Industrial Automation."

Transcript:

0:00:11.5
Matthew Graff: I'm Matthew Graff. I work here at Clovis Community College. I'm an Instructor of Automation, Robotics, Mechatronics. What we do here in the lab is teach students on industrial automation. So a few years ago, I got contacted from a professor at Texas A&M if I wanted to be involved in a National Science Foundation project. And the project was focusing on training technicians in the Fourth Industrial Revolution. So when the grant was awarded, I let my computer science colleague know that there was a position that he could work on this grant with me. The reason I brought the computer science department in is I had no background in working with something like a Raspberry Pi and so I needed that expertise. We brought in multiple student workers over time and they assisted in getting Ignition on the Raspberry Pi, getting the system working, stuff that a computer science student could do pretty easily, but it was just not the background that myself or students in industrial automation program normally have.

0:01:16.3
Bill Kerney: My name is Bill Kerney. I am an Instructor of Computer Science here at Clovis Community College. I've been working on this project for about two years now. My role here was as an advisor. I was here to supervise the student workers on the project. And so, when they got stuck figuring out how to do something, then it was my job to unstick them.

0:01:35.1
Matthew Graff: We are training high school teachers and college instructors on the Fourth Industrial Revolution system or Industry 4.0 Project. And so what we do is we show the students how to initialize the system and then do some troubleshooting. I've been very impressed working with the Educational Engagement Program with Inductive Automation. Just from the get go, I just got on the website and said, "Hey, I'm interested." And within a week, we were talking person to person going, "Hey, this is what we're trying to do, what we need to accomplish." From there they were able to connect us with others in Inductive Automation to help with the project and give some feedback so that we would be doing stuff to industrial standards.

0:02:17.9
Julian Laxamana: My name is Julian Laxamana. I'm currently a Student Researcher here at Clovis Community College working on the Industry 4.0 Project. I work with the Raspberry Pis and Arduinos to collect data from smart homes and display it on the Ignition webpage.

0:02:31.7
Gurkaran Singh: My name is Gurkaran Singh. I'm a student here at Clovis Community College studying industrial automation. I'm also a student employee. My main focus with the project is to establish MQTT connections between the edge devices and the Ignition SCADA.

0:02:51.1
Matthew Graff: We're focusing a lot on using what Walker Reynolds called a Unified Namespace. And we're using MQTT to move the data around. As we build out the system, we wanted something that literally for around $200 of hardware, someone could learn and experience how to use Ignition. It goes down to just a really simple smart home that they're programming and setting up and configuring a Namespace for. The visualization is a big part. And so, we're using Perspective. One fun story was I was at a high school and I could see the teacher walking around telling students, they're secretly pulling their cell phones out and telling them put away. I turned around and said, "Hey, here's the address. Connect to this and you can connect into the system." And so then they had Perspective running on their phone.

0:03:45.7
Julian Laxamana: We're having the Raspberry Pi run Ignition on a terminal. And then the Arduinos connect the MQTT broker through Namespace and it sends the data through there. And you can connect through your phone or laptop and see the data from the Arduinos, which is really cool. This is the Ignition webpage to control the smart home for this smart home here. So you can set the LED color like here, and then set the yellow LED here, and there's a little door on it.

0:04:19.3
Gurkaran Singh: Basically, we're using Ignition as a MQTT broker, using the MQTT Distributor Module as the broker. And then, we're connecting all the edge devices, which are our smart homes, to the broker, and that's how we're getting the data into Ignition. Once we've got the tags in Ignition, I go ahead and create the UDTs and once they're on, I build the Perspective views. Once we've got the edge devices configured and publishing to the broker, we should be able to see the data come in on the MQTT Engine [Module] on Ignition. So the Namespace that we are using follows a simple structure. We've got a generic name "Smart Company" and then a neighborhood. So for each new neighborhood, we'll increment the number. And for each neighborhood, we've got object detection. You've got smart farms, and then we got smart homes. Under each smart home are all the homes that are currently connected and publishing data. And these are all the tags that are being published. These tags are being used on here on this Perspective view displaying the data such as count, humidity, temperature, and there is some data coming in. The push buttons got motion and there's a touch. We could switch the homes from the smart home number.

0:05:36.0
Gurkaran Singh: This dropdown auto-updates each time a new home disconnects or connects. For troubleshooting the MQTT communications, I use MQTT Explorer connecting to the broker. It's really easy to see all the data come in and confirm that the homes that are actually connected we are able to receive that data on the broker.

0:05:58.8
Matthew Graff: We also didn't want people to have the view that this is just like using cheap off-the-shelf toys and it has nothing related to industrial products. So what we did is we looked out and tried to find a product that would be similar that's being used in industry. We located Opto 22. They have a single board Linux system and we've used that for our college level systems. So we are giving institutions, through our grant, those Opto 22s and they're able to experience both working with cheap system that they could easily buy for a whole classroom, every student, and using industrial system with Opto 22. Having student workers has been helpful because I could see how much they could take on and also discuss with them well, how would we teach other students? Bouncing ideas off of them and trying to create a student-centered approach to teaching. Julian brought a video in from object detection that's run on another application.

0:07:01.1
Julian Laxamana: We currently use YOLOv8 to collect data from ESP32 cameras and then process it through the Raspberry Pi and then that displays it on a webpage, which Ignition gets the data from and displays it on there.

0:07:17.0
Matthew Graff: Working on this project has really exceeded my expectations. Been super impressed with students working at different levels. They generally have brought the project further along than I was able to do just on my own.

0:07:31.2
Gurkaran Singh: Working on this project exposed me to Ignition and Opto 22 and MQTT. I found this local company focused on agricultural monitoring and automation. Their main product was based on Ignition. They were using Opto 22s for their controls and MQTT to transmit all the data. I reached out and expressed my interest and next morning I hear back from the president of the company and my skills aligned with their products, which led me to be able to get a job over there.

0:08:04.1
John Williamson: My name is John Williamson. I am the President of Farm Data Systems. We have about 20 years experience working with farmers to help them improve irrigation management. We've been working with Opto for about eight years now, using their controllers for Ignition. We've been working with them for about six years now, so we've probably done a couple hundred projects already with Ignition. So one of our biggest challenges is building a team of technicians who have capabilities around Ignition and low-voltage electrical systems. But one day Gurkaran contacted us directly, which was really good. We had internships available at the time, but Gurkaran expressed an interest in a full-time position. So I talked to him over the phone and it was very clear his career objectives were very much in line with what we were doing. So we met in-person and I already knew he could add value on day one. His training at college was really so well suited to the work we're doing here. Can't speak highly enough about the program and how well suited it is to our business.

0:09:05.9
Gurkaran Singh: My day to day over at Farm Data System includes configuring Opto 22 products for upcoming projects, monitoring alarms for the products that are already out in the field, trying to troubleshoot any networking issues that we face, and trying to help customers solve those problems. I feel that the skills that I learned working with the Industry 4.0 Project were highly relevant and were really beneficial for me in being able to be successful in my current role.

0:09:38.0
Bill Kerney: We've had software engineers work on this project. The first one, Neiro Cabrera, worked on this for about a year and then he transferred to UCLA and then he just recently messaged me and told me that he got a job in a related industry. So an absolute success story.

0:09:51.5
Julian Laxamana: Working with Ignition and all the software we have now provides a good foundation for me to build other projects in the future.

0:09:58.7
Gurkaran Singh: Learning all these concepts, using hardware as well as software, helped me improve my troubleshooting skills. While using hardware, you have opportunity to make more mistakes. It may be a wiring issue or it could be a software issue such as setting an incorrect IP address. It helps you gain a deeper understanding of the whole system, trying to troubleshoot the issues and fixing the problem.

0:10:24.1
Matthew Graff: Projects really get students excited and so when we use Ignition, we see students, rather than trying to race to the door and leave five minutes early, they stay around for maybe an hour or two extra trying to get their project working.

0:10:42.2
Bill Kerney: One of the things I work on with my students a lot is trying to get them to go out into the real world and interface with the real world. Getting them to actually turn a motor on or to turn a light on or to open a door and things like that is oftentimes just a mind-blowing experience for them.

0:10:56.2
Julian Laxamana: Very cool for students to see their knowledge have a physical effect on the real world.

0:11:01.0
Matthew Graff: I encourage anyone who wants to look at this project go to our GitHub page. This was funded by the National Science Foundation and I just feel like we are obligated and we want to share everything we have here. There's nothing we're hiding, so feel free to use that. You can take this and use it in a classroom, or if you're an engineer and you just wanna poke around, or just someone that wants to have a fun automation project, you can just get a little $55 home from Amazon and pay a $100 for for a Raspberry Pi and you'll be set to go.

Most people think of Ignition as software for SCADA or industrial automation, but there’s a lot more to the platform than that. Ignition is a toolbox for building whatever kind of application your organization needs. Here at Inductive Automation (IA), we have found plenty of everyday uses for Ignition because it allows us to create customized tools that generate tremendous value.

When we recognize the need for a new application, Inductive Automation still evaluates Ignition against other products on the market, but in some cases, using Ignition makes the most sense, whether that is due to our unique requirements or the speed with which an application can be implemented and updated.

In one form or another, everybody at Inductive Automation is impacted by Ignition. Below, discover a few of the ways we leverage our own software platform.

Building Automation System

When IA moved into our 56,000-square-foot headquarters, we inherited an old HVAC system, controlled by commodity HVAC software. Offices were over 10 degrees off setpoint at all times, compressors broke regularly, and heaters constantly reset unbeknownst to the control system, resulting in melted wires and visible damage. The system needed to run 24/7 because some offices would never recover from a shutdown.

It was IA Founder & Executive Chairman of the Board of Directors Steve Hechtman who had the foresight to run the HVAC on Ignition, which was unorthodox, given that specialized HVAC software already existed. His decision, however, proved to be the right one. Commodity HVAC controls would have narrowed the system’s visibility too much to isolate the root cause of each issue. Additionally, this commodity software required an external technician to make changes, resulting in slow, expensive, and sometimes ineffective solutions.

In contrast, Ignition empowered IA staff with its ability to historically log every datapoint, build ad hoc dashboards to investigate issues, and rapidly make changes and refinements. Ignition’s visibility helped us discover thermostats wired to the wrong rooms, incomplete ducting, failing contactors from faulty logic, short-cycling heating and cooling modes that were undetectable in the previous software, and more. Ignition also allowed us to review historical trends and rethink the air handler sequencing to mitigate runaway cooling of interior offices.

Now our HVAC is so efficient and responsive that IA can shut down every night and weekend, resulting in significant energy savings without sacrificing employee comfort during operating hours. Using Ignition on our HVAC also allowed us to test and refine our BACnet Driver before we released it publicly. Overall, the building automation system has given IA the visibility and flexibility to make rapid, informed changes, on our own schedule.

Lobby Sign-In

The Lobby Sign-In application at our Folsom, California headquarters is built in the Ignition Perspective Module, meaning that front desk staff can use iPads to check in guests, vendors, and trainees. The application opens with a “Welcome to Inductive Automation” screen, then gives four option tabs to choose from: Interview, Meeting, Training, and Other.

For in-person training classes, trainees can easily find or input their names. The application saves their information for the week, which makes each subsequent sign-in quicker because they don't have to re-enter their information.

The application efficiently keeps a roster and helps track who is in the building at any given moment, ensuring a secure environment for everyone. One of the application’s standout features is the ability to look up anyone who has checked in on our CRM and generate a lobby sign-in report.

IA’s Sales Engineering Division has made plenty of updates to the application for an easier check-in experience, including the ability to configure different greetings and sign-in methods. They have also uploaded the project to the Ignition Exchange.

Notes App

Sales Engineering is always creating new projects in Ignition and helping integrators build their own solutions. Sales engineers have always had a way of tracking notes, but now with the Notes App, they can derive some analytics from it.

When sales engineers meet with customers, one common question is, “What are the big things you’re seeing? What is trending lately?” The Notes App can create a word cloud based on the terms that sales engineers have recorded from their calls, giving insight into what the Ignition community is interested in. This offers a convenient way to gauge general interest in certain topics right now and over time.

Architecture Builder

Sales engineers build architectures for customers every day. Before they implemented the Architecture Builder, they had to build architectures manually, with basic digital drawing tools. Naturally, because each architecture was essentially drawn by hand, there were variations from engineer to engineer. To solve this problem, the Sales Engineering team needed a way to be consistent, fast, and add additional Ignition-specific context.

The Architecture Builder has a drag & drop editor that allows sales engineers to build out architectures quickly. The application lets engineers move servers around, choose modules, as well as create a bill of materials and pricing quote for the entire architecture. The Architecture Builder gets to a place of real value because more than just giving customers the quote or the architecture, it can additionally provide hardware recommendations based on the architecture and system size.

Zendesk Display Dashboard

IA’s Support Division helps customers with their Ignition systems every day. And Ignition helps Support do that in a number of ways.

The Zendesk Display Dashboard gives Support managers and team leads a quick overview of their teams. They can filter and set audio notifications to check in when a call exceeds 45 minutes to ensure a speedy resolution. The dashboard also shows what Support staff is doing at any given time, whether they are on a call, researching, or just sending an email.

The application has available and unavailable tabs, so managers and leads know who they can assign emergency tickets to. The dashboard is integrated with Slack to display live status, showing who is out sick, in a meeting, or on their lunch break. In any of those cases, instead of being in the available tab, they will be automatically moved to the unavailable tab. These tabs can also be filtered by team, position, or shift.

Project cards display the number of tickets in each respective queue in Zendesk: Open Problem for unassigned tickets; Special for enterprise customers; Tech Triage for tickets that haven't been triaged yet; No-Contract tickets; and Suspended tickets. By clicking on any of these, the application will show general information about the ticket, including the current assignee, subject, time history, and links to any relevant Slack conversations with the Development Division.

Thread & Slack Stats

One of the more difficult tasks that Support has to do is look through thread dumps because they don't always know what these threads are supposed to be doing or what they are responsible for. The Thread Stats feature has collected hundreds of thread dumps and parsed them for key metadata about each thread pool. This gives Support a resource for understanding what normal behavior looks like so they can better identify what is acting abnormally.

Slack Stats is another integration with Slack. When Support staff run into a roadblock while troubleshooting an issue, they reach out to the Dev Slack channel or just start a general support channel to ask questions. This project monitors those individual messages and makes sure they’re being answered in a timely manner. If they haven't received a reply in 30 minutes, it will trigger an alarm.

CRM

A few years after its founding, Inductive Automation was looking at different CRM systems. However, since Ignition's unlimited licensing is so unique, we realized that any other CRM would need to be completely customized to suit our needs. IA decided that building an in-house CRM would provide the exact application that we wanted as well as allow for continual improvement.

These days, Inductive Automation upgrades the CRM to every new version of Ignition, with a dedicated team for implementing updates. Like any company, IA faces a variety of business challenges and having an application built in Ignition lets us solve them faster. IA needs to be agile and this application allows us to be exactly that.

The CRM synthesizes both Ignition visualization modules, with the bulk of the application built in Vision and the executive dashboards in Perspective. The CRM lets the Sales team easily manage not only the organizations and companies that IA does business with, but also quotes, invoices, and license keys.

IA lets the CRM be the single pane of glass that pulls data together into one place, and because it’s built in Ignition, the CRM can integrate with other business intelligence tools as well. The CRM interfaces with our accounting software, our marketing lead generation tool, and helps us stay ADA-compliant. IA uses the CRM not only for our ordering system so the Sales team can create quotes and orders and manage licenses, but also as a reporting tool.

All of our training courses are connected to the CRM. When someone signs up for a training course, the CRM creates the order and registers that person to the class. The CRM also lets us adapt quickly to new situations. For example, when we sell tickets for the Ignition Community Conference, we use the CRM to track attendees’ dietary restrictions.

License Portal

The License Portal fulfills a need that is specific to Inductive Automation. Ignition’s server-centric licensing lets organizations choose the architecture that’s right for them, but it also means that there’s no off-the-shelf solution for managing Ignition licenses.

The application, which is built in Perspective, allows for IA employees, integrators, end users, and Authorized Ignition Distributors to manage Ignition licenses, and view certification statuses, quotes, and invoices. They can search for specific licenses by criteria like license key, location, status or role, edition of Ignition, and more.

The application displays which customer a license is associated with, plus all related modules and activation history as well as all the developers in an organization and their current certification status. Beyond just seeing licenses, the License Portal also gives the ability to add additional context to licenses by setting and/or editing a location, and adding descriptive notes or searchable tags.

The other critical feature of the License Portal is the ability to view quotes, pay invoices, and generate new licenses. This aspect of the application is particularly useful for Ignition distributors around the globe because they can quote and place orders directly through the License Portal. It gives distributors autonomy, which is especially important for locations with dramatic time differences from our headquarters in California. Being able to independently process and order for their customers eliminates the sometimes multi-day process of ordering using the traditional route.

Quoting Tool

Before Inductive Automation acquired the assets of iControls and launched Inductive Automation Australia (IA AU), iControls was the official Ignition distributor in Australia. iControls acted as a middle entity between end users and IA. As a result, they sometimes had difficulties translating quotes to local currencies and different types of markets, due to IA’s unique business model, not to mention various discounts and nuances of licensing. Prior to implementing this application, translating a quote from the IA website required three people to input the exact same data, so IA AU developed the Quoting Tool in Perspective to improve the sales process.

IA AU wanted to keep HubSpot as a single source of truth, integrating it with the Quoting Tool to bring in important pieces of data like company type, certification level, managed accounts, NDAs, and more.

The Quoting Tool lets Sales create a quote by selecting a combination of gateways and edge products in addition to support and training packages, plus an option to add a completely customized product for special cases. The tool also transparently displays the discounts applied to each part of the quote in addition to the exchange rate for the chosen currency. Once the quote is created, it is saved as a searchable template to expedite the process of building complex quotes or updating an existing one.

IA AU also wanted to address the quoting workflow. Each quote enters a track and trace mechanism as it progresses through the various steps of internal review and approval. Once the quote is approved, the document is ready to be deployed and downloaded by the sales representatives to send to the end user. IA AU is currently working to integrate the Architecture Builder with the Quoting Tool to automatically send the quote and architecture diagram together.

The Quoting Tool has provided an easier path for members of the Sales team to do their jobs, reducing mistakes while gathering data and setting goals for continuous improvement.

Share Your Unique Ignition Projects

Inductive Automation has pain points just like any company. Our approach is to look for solutions in the platforms that we already use, but if they lack specific functionality or interoperability, then we leverage Ignition to make the platforms we already have even more effective.

With its open-ended design and inherent flexibility, Ignition can solve pain points for any organization no matter the industry, so we want to hear your success stories. Share your projects with us and let us know how Ignition is helping your business and your customers.

Submit a case study application

Share your project with us on LinkedIn

Transcript:

00:02 
Travis Cox: Most people think of Ignition as a platform for industrial automation or SCADA, but there's a lot more to it than that. At Inductive Automation, we build applications in Ignition for internal use because we can create small, customized tools that generate tremendous value, and once those products are in place, we can roll out improvements quickly. That's not to say we sink a bunch of development time into reinventing the wheel. We still evaluate Ignition versus other products in the market. We just happen to find plenty of use cases where Ignition is the best option. Everybody at Inductive Automation is impacted by Ignition in one way or another, so we're gonna show you some examples of how we use our product and how it gives us value.

00:40 
Kurt Seifert: When we moved into our 56,000-square-foot Folsom headquarters, we inherited a unique and old HVAC system controlled by common HVAC software. Offices were often 10℉ off setpoint, compressors were breaking regularly, heaters were constantly tripping and resetting without the control system knowing as evidenced by melted wires and visible damage. We had to run the system 24 hours a day, seven days a week, because some offices would never recover from shutting down overnight. It was a mess.

01:07 
Mike Hechtman: It was [IA Founder & Executive Chairman of the Board of Directors] Steve Hechtman that had the foresight to run our HVAC on Ignition, which seemed unusual at first, given the specialized HVAC software that already existed. But as we soon discovered, his decision was spot on. Existing HVAC controls run on slow networking and hardware with sluggish screens and historical trending. You either don't have enough information logged or you lose your train of thought waiting for information to load. How do you debug anything with that? How do you get to the root cause? And adjusting controls logic has to be done on some technician's schedule, not our schedule?

01:44 
Mike Hechtman: Often, by the time someone can come out to fix something, you've forgotten the important details. Adding time to a problem is much more expensive than people realize. But with Ignition, we can make changes on the fly. Historically log every data point, calculate and chart how far off setpoint the entire building is. Make ad hoc dashboards to compare this to effects of outside temperature. We can wire inputs to physically verify equipment is running and show this on the HMI. We can investigate any issue as it's happening on our own schedule. We can do anything we dream up. It is empowering.

02:21 
Kurt Seifert: Ignition's visibility helped us investigate and discover thermostats wired to the wrong rooms, incomplete ducting, faulty logic that shortened equipment life, and short cycling of heating and cooling modes, which couldn't be detected in the previous software, and the list goes on. Once all this was handled, Ignition allowed us to review years of historical trends to totally rethink the air-handler sequencing we were provided, at a high level, which helped us solve offices that were often eight degrees under temperature despite minimum airflow. Now our HVAC is so efficient and responsive that we can shut down every night and weekend for significant energy savings without sacrificing employee comfort during open hours.

02:58 
Mike Hechtman: Using Ignition on our HVAC also allowed us to test and refine our BACnet Driver before it reached the public. It's a testing ground for us. If there is ever anything wrong with Ignition, we are gonna feel it in the office. But overall, Ignition gave us the visibility and flexibility to make rapid, informed changes on our own schedule, really challenging the norm, and it was actually a lot of fun.

03:23 
Dara Claiborne: Our Lobby Sign-In application runs on Perspective, which means that we can use iPads upfront to check in guests, vendors, and trainees. The process is pretty simple. The application opens up with a "Welcome to Inductive Automation" screen, and then gives four option tabs to choose from: interview, meeting, training, and other. For in-person training classes, the trainees can find or input their names. The application saves their information for the week, which makes the sign-in process quicker because they don't have to retype all their information. The application as a whole officially keeps a roster and helps us track who is in the building, ensuring a secure environment for everyone.

04:05 
Dara Claiborne: It's really easy to integrate other systems with Ignition, so one of the standout features is the ability to look up anyone who has checked in on our CRM and we can generate a lobby sign-in report. Connor Futa and Chase Dorsey from our Sales Engineering team have made plenty of updates to the application for an easier check-in experience, including the ability to configure the different greetings and sign-in methods for the version that's available on the Ignition Exchange. It's really convenient to have them continually improve the process.

04:39 
Matthew Raybourn: The Sales Engineering Division is always creating new projects in Ignition, like the online Demo Project or helping integrators build their own solutions. The first application I want to talk about is the Notes App. Sales Engineering has always had a way of tracking notes, but now we're trying to drive some analytics from it. When we're meeting with customers, one of the questions Sales Engineering gets asked all the time is, "What are the big things you're seeing? What is trending lately?" The Notes App can create a word cloud based on the terms that we have recorded from our calls, giving us insight into what people are interested in. It gives us an easy way to gauge general interest in certain topics, especially over time. There have been three iterations of this application and you can see the progression through each version. One of the reasons we built this application in Ignition is that we can easily implement changes to better align with how we use it.

05:33 
Matthew Raybourn: The second application that I want to talk about is the Architecture Builder. As sales engineers, we build architectures for customers every day. Before we had this application, we were building architectures manually, using basic digital drawing tools. The problem was that because we were essentially drawing these by hand, there were variations from engineer to engineer. We needed a way to be consistent, fast, and add some additional Ignition-specific context. The Architecture Builder has a drag-and-drop editor that allows us to build out architectures quickly. You can move servers around and click on a server, choose the modules, and create a build of materials for your entire architecture, providing a pricing quote or a build materials. The Architecture Builder gets to a place of real value because we're not just giving customers the quote or the architecture, we can even provide hardware recommendations based on the architecture and system size. The application allows us to be more effective in how we communicate to customers. Both of these applications are relatively simple tools that provide tremendous value. You see that everywhere at Inductive Automation.

06:43 
Corbin Harrell: IA's Support Division works with Ignition every day, helping customers with their own Ignition systems. And Ignition helps us do that. One of the main ways is the Zendesk Display Dashboard. This dashboard gives the managers and team leads a quick overview of their teams, which they can filter, and they can send audio notifications to check in when a call exceeds 45 minutes, so that we can ensure a speedy resolution to the problem. The dashboard also shows what everyone is doing, whether that means they're on a call, researching, or just sending out an email. We have available and unavailable tabs so that we know who we can assign emergency tickets to. The dashboard is integrated with Slack to display live statuses. We can also see who's out sick, in a meeting, or just on lunch. In any of those cases, instead of being in the available tab, they'll be automatically moved to the unavailable tab.

07:31 
Corbin Harrell: These can also be filtered by team, position, or shift. These project cards tell us how many tickets are in their respective queues in Zendesk. This first card is the Open Problem queue for unassigned tickets. This card is for our enterprise customers. Tech Triage for tickets that haven't been triaged yet, No-Contract tickets, and Suspended tickets. Click on any of these and you can see general information about the ticket, including the current assignee, subject, time history, and links to any relevant Slack conversations with the [Software] Development Division. Here on the side, we can look at Thread Stats, which is a pretty new project. One of the more difficult tasks that support has to do is look through thread dumps because we don't always know what these threads are supposed to be doing or what they're responsible for. So we've collected hundreds of thread dumps and parsed them for key metadata about each thread pool.

08:20 
Corbin Harrell: This gives us a resource for understanding what normal behavior looks like so we can better identify when something is acting abnormal. Slack Stats is another integration with Slack. One of the most common Support workflows is that when we run into a roadblock while troubleshooting an issue, we reach out to the Dev Slack channel or just start a general Support channel where we can ask questions. This project monitors those individual messages and makes sure they're being answered in a timely manner. If they haven't gotten a reply yet for 30 minutes, it will trigger an alarm. This project has been a continual work. It's super useful for the Support Division and handles a lot of how we're getting data behind the scenes, but that goes for all Ignition projects, right?

09:01 
Vannessa Garcia: Back when Inductive Automation was only a few years old, we were looking at different CRM systems, but Ignition's unlimited licensing is so unique that if we used any other CRM, we realized that we'd have to completely customize it to suit our needs as a company. We decided that building our own CRM would give us the exact application that we wanted and let us continually improve it. Fast forward to today, Inductive Automation has upgraded our CRM with every new version of Ignition. We have a team that manages the CRM and actively updates it all the time. Like any company, IA faces a variety of business challenges and having an application built in Ignition allows us to solve them faster. We need to be agile, and this application allows us to be exactly that. IA's Chief Technology Evangelist Travis Cox built the original application. The CRM synthesizes both of Ignition's visualization modules, with the bulk of the application built in Vision and executive dashboards built in Perspective.

10:08 
Vannessa Garcia: In Sales, the CRM lets us easily manage not only the organizations and companies that we do business with, but also our quotes, invoices, and license keys. Travis built those executive dashboards for Steve Hechtman, IA Founder & Executive Chairman of the Board of Directors, because Steve wanted a fast way to see data. Since Perspective runs in your browser, that is the fastest way to do it. Building the CRM and Ignition lets us integrate other business intelligence tools as well. The CRM interface is with our accounting software, our marketing lead generation tool, and helps us stay ADA-compliant. All of our training courses are also connected to the CRM. When someone signs up for a training course, CRM creates the order and registers that person to the class. The CRM also lets us adapt quickly to new situations. For example, when we sell tickets for the Ignition Community Conference, we use CRM to track attendees dietary restrictions. What our customers get from Ignition, we get too.

11:18 
Vannessa Garcia: It's a tool to capture and manage data the way we want. We use the CRM not only for our ordering system, so our Sales team can create quotes and orders and manage licenses, but we also use it as a reporting tool. The CRM application really has its fingers in all different parts of the organization. We let CRM be that single pane of glass that pools data together into one place. This is the most important tool we have. We rely on Ignition daily to run our business, so we know firsthand the amount of trust it takes to go all in with Ignition.

12:00 
Yegor Karnaukhov: The License Portal fulfills a need that is specific to Inductive Automation. Ignition's server-centric licensing lets organizations choose the architecture that is right for them, but it also means that there's no off-the-shelf solution for managing Ignition licenses. The application, which is built in Perspective, allows for IA employees, integrators, end users, and Ignition distributors to manage Ignition licenses and view certificate statuses, quotes, and invoices. They can search for specific licenses by criteria like license key, location, status or role, edition of Ignition, and more. The portal displays which customer a license is associated with, plus all related modules and activation history as well as all of the developers and organization and their current certification status. Beyond just seeing licenses, the License Portal also gives the ability to add additional context to licenses by setting and/or editing a location and adding descriptive notes or searchable tags.

13:04 
Yegor Karnaukhov: The other critical feature of the License Portal is the ability to view quotes, pay invoices, and generate new licenses. This aspect of the application is particularly useful for Ignition distributors around the globe because they can quote and place orders directly through the license portal. It gives distributors autonomy and independence, which is especially important for locations with dramatic time differences from our headquarters in California. Being able to process an order on their own for their customers eliminates the sometimes multi-day process of ordering using the traditional route.

13:41 
Francisco Carrión: Before Inductive Automation Australia, when we were still a distributor, we were that middle entity between end users and Inductive. As a result, we sometimes had difficulties translating quotes to local currencies and different types of markets. We had tried another software to handle quoting, but it was really hard to customize because of IA's business model, not to mention the various discounts and nuances of licensing. With our previous setup to translate a quote from IA website, we ended up having three people input the exact same data. So we developed the Quoting Tool in Perspective to improve our sales process. We have used HubSpot as our CRM since the beginning of the operation, which we wanted to keep as our single source of truth.

14:24 
Francisco Carrión: HubSpot integrates with the Quoting Tool to bring in important pieces of data like company type, certification level, managed accounts, NDAs, and more. Then anything that we quote is translated into a deal in HubSpot. The Quoting Tool lets us create a quote by selecting a combination of gateways and edge products in addition to support and training packages. There's even an option to add a completely customized product for special cases. The tool also transparently displays the discounts applied to each part of the quote in addition to the exchange rate for the chosen currency. Once the quote is created, it is digitized as a searchable template to expedite the process of building complex quotes or updating an existing one.

15:06 
William Bowen: We also wanted to address the workflow, so once somebody requests a quote, it goes through an internal review and we keep a track and trace mechanism for the quote as it goes through the various steps for approval. Once the quote is approved, the document is ready to be deployed and downloaded by the sales rep to send to the end user. We haven't automated the delivery yet because for complex architectures we want to attach an architecture diagram, but we are working to integrate the Architecture Builder so soon we'll be able to automatically send the quote and diagram together.

15:36 
Francisco Carrión: The Quoting Tool has provided an easier path for people to do their jobs, an easier way to request, an easier way to review, and an easier way to approve. We are reducing mistakes while gathering data and setting goals for continuous improvement. Sometimes the fear is that you're using Ignition for something that is potentially out there already, and so it's a waste of resources. Our approach is always to look for something in the platforms that we already use, but if they don't have the functionality, or if the data that we want cannot be communicated between platforms, then we leverage Ignition to solve the problem and integrate those softwares. For us, the key word is "orchestration." We are using Ignition to make the platforms we already have even more effective.

16:19 
Travis Cox: Inductive Automation has pain points just like any company, but we address them using Ignition and rely on the customized tools that we built with our own platform. Due to its open-ended design and inherent flexibility, Ignition can solve pain points for any organization no matter the industry. We want to hear your success stories, share your projects with us, and tell us how Ignition is helping you and your customers.

According to Goodnight Midstream’s Chief Information Officer, Kevin Cooper, “For anybody who has done large-scale networks, especially distributed out to edges that are way out in the middle of nowhere, VPN tunnels can be the bane of your existence.”

That’s especially true for Goodnight Midstream, a produced water infrastructure company for oil & gas producers, because unlike traditional methods for produced water transportation, Goodnight Midstream has an extensive network of water-gathering and transportation pipelines across the US. This network allows for saltwater to reach geologically sustainable disposal wells while eliminating greenhouse gas emissions produced by trucks and protecting freshwater resources.

Finding An Alternative To Point-To-Point VPNs

Goodnight Midstream’s SCADA architecture consisted of multiple point-to-point VPN tunnels for securely connecting their facilities and central hub. Managing each VPN connection’s firewall became complex as each required configuration, monitoring, and maintenance. This traditional point-to-point VPN setup also limited the growth of Goodnight Midstream’s infrastructure because of the additional resources necessary to individually connect and reconfigure every existing site to each new VPN. “It was not uncommon for us to come into work in the morning and have seven or eight tickets at the help desk because reports weren't working the way they were supposed to and inevitably we would trace that back to a VPN tunnel,” said Cooper.

Goodnight Midstream’s existing SCADA software provided some challenges for them as well. Simple changes like adding objects in the application screen required users to access the development environment. Moreover, maintaining version consistency — such as performing patch management across endpoints, historians, and data centers — proved cumbersome. If a data center was updated or a patch applied, the endpoints would become “orphaned,” meaning that they were invisible until they could be updated to the matching version. Manually updating each endpoint (over 100 in total) was not only time-consuming but required external contractors, which added to the operational complexity, use of resources, and overall cost.

A Deep Project Scope

These opportunities for improvement prompted Goodnight Midstream to seek help from CSE ICON, a professional services company specializing in customized solutions for industrial automation, SCADA, and Digital Transformation. From the beginning, Goodnight Midstream prepared a robust scope document outlining what they wanted to achieve, including:

• Remove the point-to-point VPNs to decrease complexity and administrative effort.
• Implement MQTT to transfer data faster and benefit from secure Internet connections.
• Replace the existing SCADA system with Ignition.

Goodnight Midstream chose Ignition — an industrial automation platform for SCADA, HMI, IIoT, and more — because it could fulfill several requirements:

• Data mining and business intelligence work on the system backend.
• Powerful Linux-based edge deployments.
• Easy upgrades that could be performed by administrative staff.
• Location data driven by an external database.
• Template support.

There was also the monetary benefit. “Ignition is very cost competitive. When you're looking at what your total cost of software is over time, having Ignition be very robust technologically, but also very affordable is incredibly important,” said Cooper.

Based on Goodnight Midstream's goals, CSE ICON defined the project scope along with the key objectives. The main focus was to design a gateway architecture and implement MQTT in the field to bring data up to the enterprise. To accomplish this, CSE ICON needed to perform:

• Installation and configuration of gateways.
• Installation and configuration of an MQTT broker.
• Creation of UDTs (User Defined Types) and instances for Ignition.
• Migration of data from their existing SCADA system to Ignition.
• Streamlined patch management.

“We felt that Goodnight was very thorough in their scope of work documentation and it made it a lot easier for us to implement the functionality that they required,” said Binh Vu, SCADA Solutions Manager at CSE ICON.

Building A Gateway Architecture With Ignition, MQTT & Moxa

Goodnight Midstream strategically positioned five Windows servers at the enterprise level and approximately 50 Moxa AIG Edge Intelligence Gateway devices — each installed with Ignition Edge — at their facilities. “We chose the Moxa platform because it came out of the box preloaded with Debian, which is Linux for the edge,” said Rick Hornung, Senior Manager of Information Technology at Goodnight Midstream. “Moxa provides a set of tools to manage those endpoints centrally. We were able to leverage that platform because of the portability of Ignition.” This combination of technologies enhanced data processing and communication capabilities at the edge of the network.

Next, the focus shifted to the communication protocol. To make an informed decision about which MQTT broker would best meet the needs of the project, CSE ICON and Goodnight Midstream’s technical staff conducted load testing to assess system performance under varying levels of demand. Goodnight Midstream ultimately implemented the Chariot MQTT broker as the results indicated that Cirrus Link’s cost-effective and easy-to-use broker exceeded the project’s requirements by a wide margin.

UDTs & Alarms Syncing

With the previous system, every tag needed to be manually created, so each facility had its own unique tag list. With the Ignition system, CSE ICON was able to leverage UDTs — an iterative tag data type in Ignition — to standardize tags from the ground up.

To establish a consistent real-time data exchange between client and server, CSE ICON created two types of UDTs, one for a pump and another for a tank, totaling over 100,000 tags, each of which included the OPC (Open Platform Communications) item path. However, there were also disabled tags within the UDTs, which Goodnight Midstream did not want transmitted. Fortunately, MQTT only transmits data when changes occur to minimize data transmission.

In addition to the key objectives, Goodnight Midstream also needed to receive remote alarm notifications from their pipelines at remote mini-hubs, which are manned locations in each field where a trained operator can monitor regional information. To accomplish this, the alarms (and acknowledgements) must stay in sync between the edge-based Ignition deployments at the mini-hubs and the central Ignition system. While this feature was not directly supported by Ignition out of the box, through some clever scripting, CSE ICON was able to successfully extend the system’s functionality.

A System For Data Handling, Alarming & User Interface

The Goodnight Midstream gateway architecture project was initially planned for 12 months. However, due to the database-driven metadata model and the close collaboration between CSE ICON and Goodnight Midstream, the project was completed in just eight months.

“I don't think we pulled a single item out of that scope document,” said Cooper. This was an impressive feat, considering it involved the replacement of Goodnight Midstream’s full architecture. Ignition Edge is now deployed at multiple facilities, pulling data directly from PLCs in addition to a polling gateway at the enterprise level for high-speed cellular-enabled skids (which measure the flow of the pipelines).

Goodnight Midstream no longer needs point-to-point VPNs as all communications are now transmitted through MQTT, complete with TLS setup. Not only is the architecture simplified, the resultant system is more secure, reducing the overall complexity for IT, and allowing for remote acknowledgements from one gateway to another, sent out via Twilio.

“Ignition allowed us to move to MQTT, which is optimized for low-bandwidth connections and allowed us to remove all those VPNs,” said Hornung. “We just pump it out over the networks, over its own secure protocol, and it just dramatically simplified the deployment.”

High Performance As A Standard

Using Ignition’s Perspective Module, CSE ICON designed screens that are responsive to any size, including mobile. “CSE ICON uses a high-performance HMI as a standard for our customers just to help them visualize and understand their data quickly without having a lot of clutter and a lot of other information that may not be necessary,” said Vu.

Additionally, to give an overview of Goodnight Midstream’s extensive pipeline network, the system features an interactive map and pipeline views with real-time mapping. This is particularly useful at the different levels of the architecture. “Using the templates that we have in Ignition, we can distill that information down to a KPI screen for our primary control room, but we can also broaden that view and give a little more information to the mini-hubs, since they're looking at fewer resources, and they can take a more detailed view,” said Cooper.

Enhancing Operational Effectiveness

The new Ignition system allowed Goodnight Midstream to easily overcome many common concerns in the oil & gas industry. “The reservoirs determine where you are, not where you want to be,” said Cooper, emphasizing the extreme temperatures at remote sites (from -40℉ to 120℉!). “The Ignition platform runs well on Linux devices, and when you pair those two things together, a really robust software platform with good hardware choice, [it] allows you to deploy low-power, temperature-stable devices into very harsh environments.”

The dynamic, scalable Ignition system has allowed Goodnight Midstream to use the same platform across their entire operation and primed them for expansion. With the old system, it was necessary to pull up the development environment to add objects to a screen. In contrast, the new Ignition system leverages an automatically populated tree view, which is driven by metadata, allowing Goodnight Midstream to enter new data by simply filling in a database table. The process, which used to take half a day to complete, now takes 15 minutes. This has empowered Goodnight Midstream to add new sites themselves, and the project is expected to grow to 30-50 sites in the near future.

Project Scope

• Start date: 1/2023
• Deploy date: 9/2023
• Tags: ~100,000
• Screens: 83 templated iterations of 12 unique screens
• Clients: Varies throughout the day; anywhere from 3-20
• Alarms: 59 Alarm Pipelines
• Devices:
  • 5 Windows Server machines
  • ~50 MOXA AIGs
• Architectures:
  • Enterprise architecture
    • Database exists only at enterprise
    • No databases on sites
  • 5 gateways at enterprise (Windows Server)
  • ~50 gateways at facilities (Moxa AIG)
• Databases:
  • 4 (MS SQL Server)
    • IgnitionDB
    • IgnitionHistDB
    • IgnitionHistDB_Temp
    • MetadataDB
• Historical data logged:
  • ~20 billion rows
  • ~70k unique tags

Transcript

00:09
Kevin Cooper: My name is Kevin Cooper. I'm the Chief Information Officer here at Goodnight Midstream. Goodnight Midstream provides integrated water management to oil & gas producers. The oil & gas companies will send us their wastewater and if they need water, we will provide it back to them in a reuse capacity. So Goodnight is using its Ignition SCADA system for managing its remote facilities, its remote pads, and all of our remote assets, and feeding that data into our field personnel, our SCADA personnel, our control room, and our engineers. The project that we used CSE ICON to assist us with was to replace Goodnight's existing SCADA system with a new updated and more functional SCADA system.

00:43
Binh Vu: My name is Binh Vu. I am the SCADA Solutions Manager at CSE ICON in charge of all of Ignition projects. CSE ICON is a professional services company, specializing in providing customized solutions for industrial automation, SCADA, and Digital Transformation.

00:56
Kevin Cooper: As part of preparing for this project, we spent a significant amount of time building a very good spec and scope sheet for what we were trying to accomplish. A few of the top features were mobile and desktop access were needed to be very easy to use and responsive. That needed to have a very, extremely robust historian 'cause we mine our data and do quite a bit of data mining and business intelligence work on the backend. The edge deployment needed to be incredibly robust and preferably Linux-based. The upgrade process needed to be very transparent and easy for my admins to be able to support. And the SCADA location data needed to be driven by an external database. And we also needed to be able to do simple templating. So for us to adopt the Ignition platform, these were all important factors.

01:41
Binh Vu: One of CSE ICON's goals was to develop a baseline architecture for using MQTT for our future customers. Main thing is reducing the complexity of the network architecture, so implementing MQTT out into the field to bring the data up into enterprise was a big goal for them. So minimizing the use of the point-to-point VPNs and just making the system more manageable from the IT standpoint.

02:02
Kevin Cooper: Ignition was able to meet these goals for us largely because it is so modular and customizable.

02:08
Binh Vu: Most important module, I'd probably say is the Cirrus Link modules that basically connect all of their remote field devices to the enterprise via MQTT and also the EAM Module as well to allow their SCADA admins to push changes down from the enterprise down to the field devices. They wanted a way to build a responsive HMI for all of their users, from the field level down at the control room, and Perspective to help facilitate building out these screens in a modular way. CSE ICON uses a high-performance HMI as a standard for our customers, just to help them visualize and understand their data quickly without having a lot of clutter and a lot of other information that may not be necessary for their requirements.

02:41
Rick Hornung: My name is Rick Hornung. I'm Senior Manager of Information Technology for Goodnight Midstream. Migrating to Ignition from our previous platform opened up a lot of different end compute options for different operating systems and hardware platforms. We chose the Moxa platform because it came outta the box preloaded with Debian, which is Linux for the edge, which is what we were looking for. And Moxa provides a set of tools to manage those endpoints centrally. We were able to leverage that platform 'cause of the portability of the Ignition platform.

03:09
Kevin Cooper: One of the things that is somewhat specific to oil & gas; you're almost always dealing with really out-of-the-way places. The reservoirs determine where you are, not where you want to be. So you're dealing with extreme hot, you're dealing with extreme cold, and I think that the Ignition platform running well on Linux devices and you pair those two things together — a really robust software platform with good hardware choice — allows you to deploy low-power, temperature-stable devices into very harsh environments.

03:40
Kevin Cooper: And we certainly experience that, we see everything from 120℉ to -40℉ and I'm able to use the same platform across my entire operation. There are a number of things that I think we're incredibly positive about this particular project and one of them is that Ignition is very cost competitive. When you're looking at what your total cost of software is over time, having Ignition be very robust technologically but also very affordable, it's incredibly important. Anybody who has done large-scale networks, especially distributed out to edges that are way out in the middle of nowhere, VPN tunnels can be the bane of your existence.

04:16
Kevin Cooper: Some SCADA systems will require to use VPN to propagate that data transmission from point to point. We had over a 100 of those VPN tunnels. Occasionally they would stick and if a tunnel gets stuck in the up or down situation, then you're not getting traffic and you're not getting volumes. It was not uncommon for us to come into work in the morning and have seven or eight tickets at the help desk because reports weren't working the way they were supposed to. And inevitably we would trace that back to a VPN tunnel. By moving away from VPN and using MQTT as our primary data transmission method, that has fixed all of those problems.

04:51
Rick Hornung: Ignition allowed us to move to MQTT, which is optimized for low-bandwidth connections and allowed us to remove all those VPNs. And we just pump it out over the networks, over its own secure protocol, and it just dramatically simplified the deployment.

05:05
Kevin Cooper: I think that the data resolution has been incredibly important to us because it really allows us to deliver to the business these higher-resolution data points. Previously, let's say a well engineer comes to me and says, "I wanna look at that well and I wanna look at it at like a five second data resolution." Well, I would have to take that entire location and bump it down to five seconds and now your historian is getting flooded with data that you don't really need. Now I can group just a couple of instruments and I can say, "I just want those to poll at five seconds." So I can just run that for a day and I can do things with my data engineers, working with my physical engineers, and give them answers that they couldn't do before.

05:41
Binh Vu: Previously every tag that they had in the system was manually created, so each facility had their own unique tag lists, and managing them was difficult. But by leveraging UDTs, it was standardized from the ground up.

05:54
Kevin Cooper: User response to Ignition: end users obviously are roaming the field, they need something that's very quick and easy, and we've actually developed some screens that are very specific to somebody who's rolling up on a facility needs to see their top five. We also run mini-hubs that are located in each field, where we have a trained person who's watching just their regional information, and then of course the control room's watching everything. Using the templates that we have in Ignition, we can distill that information down to a KPI screen for our primary control room, but we can also broaden that view and give a little more information to the mini-hubs since they're looking at fewer resources, and they can look, take a more detailed view. The way the Ignition is able to display that information makes that very easy and it makes it easy for me to make my customers happy.

06:36
Binh Vu: Now that they've implemented Ignition, their system's easier to manage. They can have a SCADA administrator come in and look at their system and manage it without having to bring in a team of developers to look at their remote facilities.

06:46
Kevin Cooper: What impressed me, and I think my team, about Ignition is we went pretty deep. What do we need? What do we want to do? What are we trying to accomplish? And the scope document that we built was very robust. And the fact that I don't think we pulled a single item out of that scope document and it fit inside of the Ignition platform and went very smoothly and we got what we wanted out of it, although it's what I wanted, I don't know if I expected that to happen, but at the end of the day, that's what we have on paper, that's what we have on our screens, and that is, I think, very impressive that a platform is flexible and robust enough that without breaking an arm, you're able to get what you need out of it.

07:24
Binh Vu: We felt that Goodnight was very thorough in their scope of work documentation and it made it a lot easier for us to implement the functionality that they required.

07:32
Kevin Cooper: CSE was very good at communicating with us and we understood when things were moving along, we understood when things were successful, and we understood more importantly when things were challenges and how to overcome those. And those were very positive experiences and we were very happy with the Ignition platform and CSE in that we got exactly how we speced out our project.

Project Summary:

Automation Solutions Ecuador (ASE) developed a cloud-based solution for Smart Energy Applications that enables real-time monitoring, data acquisition, and reporting for Gas-to-Grid (G2G) systems located in remote oil & gas facilities in the Amazon.

Smart Energy provides Gas to Grid in a Box (G2G_B) solutions to produce energy using the gas associated with the crude oil extraction process. The G2G_B system uses gas without treatment to reduce carbon footprint. It comprises a generation unit (Waukesha), a control and synchronism unit (Woodward Easygen), and a load shedding unit (Multilin).

The project developed by ASE was crucial for Smart Energy to get real-time and historical data of electrical and mechanical parameters, KPIs, and automatic reporting of technical, financial, and environmental results. This allowed Smart Energy headquarters to assess the impact of its solutions. Additionally, the project allowed the solution to be maintained with OpEx instead of CapEx.

Problem:

Smart Energy’s generators are situated in remote facilities that are difficult to reach and have no permanent staff. As a result, Smart Energy’s systems did not have continuous monitoring and required an operator to visit each facility once or twice a day to collect data manually. At the end of each shift, the operator manually recorded the day's data in an Excel report and submitted it via email.

The staff at the headquarters would then review and analyze the technical data provided by the operator the day before. Based on this, they manually created weekly and monthly Excel reports that included process indicators and financial data. These reports were shared with management and partners who needed to justify the investment with energy savings and carbon footprint reduction to ensure the implementation of more G2G_B systems.

Obtaining KPIs and generating reports required significant time, resources, and personnel since data could only be collected directly from equipment displays.

Ignition powered this project — try it yourself for free.

Download Ignition

Solution:

ASE designed a hybrid architecture using Ignition Edge IIoT and Ignition Cloud Edition in Azure.

To install Ignition Edge, the RTU box contains an Opto 22 groov RIO. The Modbus TCP devices are connected directly with the Ignition driver, while the Modbus RTU devices are connected via a Moxa adapter to use the RTU/TCP driver. Each G2G_B system requires one Ignition Edge installation.

For historical storage, the system utilizes an Azure Database for MySQL and an Ignition Cloud Edition subscription using Microsoft Azure. Ignition Edge publishes the collected data using MQTT and subscribes using Cirrus Link's Distributor and Engine modules for Ignition, with Starlink satellite internet for data transmission.

ASE designed the application interface in Figma and developed it using the Perspective Module in Ignition Cloud Edition. The interface includes a dark theme and parameterized views to add more generators dynamically in the future. The application is mobile-responsive and has login and language selection options, along with sections for real-time monitoring, historical queries, events, KPIs, and reporting.

Results:

Smart Energy has successfully eliminated manual data collection and replaced it with an automated system. All data is now collected and processed without human intervention, from the equipment to the end users. Personnel at the headquarters can monitor the equipment in real time and alert operators when an event occurs that requires their intervention.

Smart Energy achieved this by using Ignition and Opto 22 hardware, which meet the requirements of cybersecurity and have store-and-forward capabilities. Ignition Perspective was used to develop a dynamic application that facilitates future integration of new G2G_B systems. The application is mobile-responsive, user-friendly, intuitive, and complies with dark theme features.

To further improve decision-making and analysis of future investments, Smart Energy generates online KPIs and automatic reporting for managers and partners. Smart Energy was pleasantly surprised by the value they received from the Ignition Cloud Edition service; the price is much better than the price they had in mind. This makes it easier for them to maintain the solution with OpEx instead of CapEx.

Smart Energy optimized significant time, resources, and personnel; the solution helps to monitor in real-time the reduction of CO2 emissions and economic savings.

Start Date: December 2023

Deploy Date: February 2024

Project Scope:

Tags: 300

Screens: 10

Clients: 10+

Alarms: 100

Devices used: 6 devices, Opto 22, Moxa.

Architectures used: Cloud Hybrid (Ignition Edge, Ignition Cloud Edition)

Databases used: 1 DB, Azure DB for MySQL

Historical data logged: 300

Are you curious how Ignition can solve your toughest automation challenges?
Request a free demo that the IA team will customize to your specific use case.

Request a Free Demo

Project Summary:

Dautom successfully addressed the challenge of consolidating diverse power generation assets across multiple geographical areas. By leveraging Ignition as an IIoT platform, implementing Factory Compass 4.0, and the Unified Namespace (UNS) to standardize data models, they achieved operational excellence, resulting in enhanced interoperability and scalability.

Problem:

Copower, essential in energy generation projects, operates across various geographical areas with diverse assets, including diesel, gas, and photovoltaic sources. Gathering information on these assets relied on OEM applications and software, involving multiple brands (Jichai, Jenbacher, Waukesha, Fimer, Fronius, and Huawei) and communication protocols (Modbus, CAN, and Profibus). The diversity and different data models posed a significant challenge in collecting and unifying the data with context that leverage decision-making based on information in real time for business and operation automation.

Copower wants to develop a solution focused to facilitate the operation and improve maintenance management, including prediction of failures.

Ignition powered this project — try it yourself for free.

Download Ignition

Solution:

Dautom developed the Factory Compass 4.0, with Ignition serving as the IIoT platform. This platform integrated generation assets locally through Ignition Edge, publishing information in the UNS. Ignition Cloud was then used to consolidate a national monitoring tool. The UNS enabled the standardization of data models, providing a single source of truth for Copower's assets and ensuring interoperability and rapid deployment of new solutions.

Results:

The project facilitated organic development and scalability for Copower on its infrastructure without relying on OEMs, enabling several business automation initiatives. The UNS-based architecture integrated with the 4.0 ecosystem's data cloud layer, offering functionalities like data lakes, warehouses, ML, and AI.

An inference engine for anomaly detection with Snowflake and integration with Canary Labs for large-scale historization were also deployed. These achievements opened doors to new business models and addressed similar pain points for Copower's clients and stakeholders. The project was executed by a team from Dautom and Copower, combining technical expertise with essential knowledge of the power generation process.

Start Date: September 2023

Deploy Date: Ongoing

Project Scope:

Screens:

• Embedded views: 12
• views: 16 (low count due to reuse of parameterized views)
• Clients: Unlimited
• Alarms: 150

Devices used:

• 10 PLCs DEIF AMC 600
• Pantalla HMI AGI 415 DEIF
• 1 PLCs Opto22 groov RIO
• 2 PLCs Siemens S7-1200
• 1 Industrial Edge Computer OnLogic Helix 310
• 1 Embedded Automation Computers Advantech UNO.

Architectures used:

• Industry 4.0 based in UNS with Ignition Edge IIoT nodes and Snowflake for data cloud layer.
• Tags: 41,000
• Databases used: MySQL
• Historical data logged: 10,000 tags in Tag Historian and 2,000 in Canary, and growing

Are you curious how Ignition can solve your toughest automation challenges?
Request a free demo that the IA team will customize to your specific use case.

Request a Free Demo

Project Summary:

Northern Wasco County People’s Utility District (NWCPUD) had an existing Ignition installation with several projects built by OS Engineering for reporting meter data and operating two hydroelectric power generation projects. To complete their SCADA system, OS Engineering was selected to expand this Ignition installation to include monitoring for over 80 Intelligent Electronic Devices (IEDs) across nine substations. NWCPUD wanted a single SCADA application to oversee all aspects of their transmission and distribution infrastructure, including KPIs and real-time data, along with reporting, alarming, and trending to aid in day-to-day operations.

Problem:

NWCPUD wanted the ability to monitor all IEDs at nine substations and key field reclosers across its 87-square-mile coverage area. These IEDs included protection relays for transformers, feeder breakers, voltage regulators, reclosers, and power quality monitors. There was no existing communication infrastructure between sites, and limited real-time visibility of the transmission system for operations.

Ignition powered this project — try it yourself for free.

Download Ignition

Solution:

Utilizing the new TosiBox network infrastructure, OS Engineering began development of the Substation Monitoring project, starting with the IED configuration and data mapping to SEL real-time automation controllers (RTACs) located at each substation that Ignition would communicate with using the DNP3 driver. OS Engineering defined a tag structure and UDT definitions for all devices to make full use of Ignition’s object-oriented tools. They additionally developed a set of standard templates, faceplates, and windows for each object type using ISA-101 standards. This high-performance HMI had a modern approach on the UI, making it approachable and intuitive for operations.

All substation screens have a consistent build, with dashboards for key substation parameters along with one-line diagrams, coverage area maps, and RTAC and IED dashboards for status and monitoring. Every IED has a corresponding faceplate for additional status from the over 23,000 tags monitored in the application. A custom tagging system allows operators to place informational tags on equipment, flagging them for maintenance and other purposes. These tags are visible on the corresponding device within the one-line diagram, with the full history available on the object’s faceplate.

OS Engineering completed the full system development, configuration of the SEL RTACs and IEDs for data mapping, and commissioning of the system remotely, thanks in large part to the TosiBox network infrastructure.

Results:

The Substation Monitoring project brought new visibility to NWCPUD’s electric transmission and distribution infrastructure. Outages and other system statuses can now easily be identified, and operations can be alerted through email and SMS alarms. Additionally, the influx of available data has made automated reporting possible.

Ignition’s DNP3 driver allows for event-based polling of end devices, reducing data usage at remote sites. It also allows for easy integration with SEL RTAC controllers to consolidate IED data at each site with a reliable connection that includes event buffering.

Additionally, as OS Engineering designed the project to make full use of Ignition’s UDT and template capabilities, additional devices can be added to the system with ease using a full complement of templates, faceplates, and other objects created to suit the needs of NWCPUD.

Start Date: May 2022

Deploy Date: August 2023

Project Scope:

Tags: 23,000

Screens: 55 screens with 20 device faceplate popups

Clients: 5-10

Alarms: 900 enabled. Users can dynamically enable and configure additional alarms from the client.

Devices used: 11 SEL RTACs, 80+ IEDs

Architectures used: Standard

Databases used: MySQL

Historical data logged: 3,200 tags

Are you curious how Ignition can solve your toughest automation challenges?
Request a free demo that the IA team will customize to your specific use case.

Request a Free Demo

Project Summary:

Environmental Operating Solutions Inc. (EOSi) designed a reliable, cost-effective control system capable of being deployed quickly for both pilot and long-term projects with a minimal site footprint and impact to operations. Additionally, EOSi aimed to create a user-friendly interface accessible by remote and local personnel.

Problem:

EOSi needed to design a cloud-based SCADA using IIoT edge devices and MQTT capable of making cloud-based control possible, extremely cost-effective, and reliable.

Ignition powered this project — try it yourself for free.

Download Ignition

Solution:

The infrastructure that supports the cloud-based control system starts with a Windows server installed on an Azure Virtual Machine (VM), which in turn hosts Inductive Automation's Ignition platform. The Ignition platform includes a full-blown historian utilizing an Azure SQL server, Cirrus Link’s MQTT Engine as well as the Alarm Notification Module and Twilio Notification Module.

In the field, cellular transmitters called Rangers from Signal-Fire are used to post discrete analog process values to EOSi’s MQTT broker in Ignition. IIoT gateways from Moxa with “Ignition Onboard” pull and push, where appropriate, other data points from memory space shared between the Gateway and the customer’s PLC network. The Moxa devices have full firewalls, are accessible via VPN only, and have physically separate NIC cards to ensure there is no active connection between the subnet that the customer’s PLCs are on and the network subnet used internally by the MQTT Gateway, nor the third cellular network. The MQTT protocol transmits tiny amounts of non-contextual numerical data on this third cellular connection, which is also encrypted and linked to CA certificates, so interception or hacking is not a concern.

Functionally, through the magic of MQTT, live process values appear in the Ignition tags. Formulas in expression tags provide the control algorithm. The results of the algorithms are sent back down via MQTT to the IIoT Gateway and then to the local PLC for further analysis or direct control of analog outputs. With the use of templates, EOSi developed HMIs for each site or customer at very little additional cost, since the Ignition license allows unlimited users, tags, and screens.

What was concerning, at least in the beginning, was the reliability of the cloud. To that end, each interface featured a watchdog element monitored at the server level by Ignition.

Ignition – monitored from uptime.com, a third-party service.

• Site PLC communication – a heartbeat value from the PLC ensured site communication was functional.
• IIoT Gateway to Ignition – additional heartbeat value ensured communication between the on-site IIoT Gateway and Ignition.
• Ignition to SQL database – internal checks monitor this connection.
• If any of the above watchdogs fail, notifications (email or SMS text) configured with Twilio notify plant operators and EOSi personnel.

Results:

After four years of production installations, the only communication failure has been between the site PLC and local IIoT Gateway. In each case, after contacting the customer, the issue was identified to be a power failure at the PLC, sometimes intentional due to maintenance or sometimes a local power outage. In one case, EOSi notified the site before they had noticed it themselves. It is worth noting that because these watchdogs are monitored in the cloud, they are always active, regardless of local conditions. In other words, when the application is appropriate, EOSi has found this methodology to be more reliable than locally installed PCs and PLCs.

EOSi has moved from the traditional full-blown PLC cabinet to a very small box and reduced the cost by almost two orders of magnitude. As a business model, this cost reduction has allowed them to go from the tedious process of bids, submittals, and “hurry-up-and-wait” PLC cabinet installations to one where they can provide their cloud-based control system at no additional charge as long as the customer is buying MicroC products.

For EOSi, the Ignition platform has been life-changing for day-to-day business. Their usual deliverable is a small electrical enclosure containing the communication gateway and power supply. The most minimal footprint of all was their latest installation, where EOSi simply mailed a $800 Gateway to a friendly on-site controls electrician – the customer snapped it onto an inch of DIN rail in an existing PLC cabinet, wired some power to it, and plugged in the Ethernet cable. EOSi had configured the gateway before it left, and everything was up and running in hours, not days.

Start Date: December 2019

Deploy Date: Ongoing

Project Scope:

Tags: 170 - 1,000 per project

Screens: 15+ per project

Clients: 10+ per project

Alarms: 10+ per project

Devices used: Perspective - PC, tablets, mobile

Architectures used: Azure server running standard Ignition with Cirrus Link MQTT modules

Databases used: 6 Microsoft Azure SQL databases

Historical data logged: 5,000+

Are you curious how Ignition can solve your toughest automation challenges?
Request a free demo that the IA team will customize to your specific use case.

Request a Free Demo

Project Summary:

Barbados Water Authority (BWA) implemented a comprehensive SCADA system using Ignition to monitor and manage 55 drinking water stations, nine wastewater stations, and two treatment plants. The project aimed to ensure the provision of uninterrupted and high-quality services while addressing operating system compatibility, scalability, and network issues.

Aquatec-Automation designed the SCADA system using the Vision Module for desktop and the Perspective Module for the mobile application.

Problem:

BWA faced several challenges with their existing SCADA system, including compatibility issues with updated operating systems, limitations in scalability, unreliable alarm notifications, and network connectivity issues leading to intermittent outages. These issues collectively hindered efficient monitoring and control of their water and wastewater facilities.

Ignition powered this project — try it yourself for free.

Download Ignition

Solution:

To address these challenges, BWA opted to implement Ignition. Since the platform is built using open standards, it allowed them to solve compatibility with operating systems and scalability. Also, due to Ignition’s unlimited licensing model, BWA was able to acquire a license that was more tailored to the needs of the project.

Regarding the reliability of alarm notifications, the Ignition's Alarm Notification Module provided advanced tools to ensure that operators were alerted to the most critical alarm notifications.

Ignition’s component library, along with vector graphics, allowed Aquatec to develop a wide range of functions to customize and optimize the system’s graphical interface, resulting in an intuitive and easy-to-use application.

Aquatec leveraged Ignition’s Reporting Module to tackle the challenge of designing screens that present useful information and generating automatic monthly reports with concise, summarized data. This module provided advanced tools to design customizable reports that effectively convey critical information to users. Additionally, monthly and automated reporting capabilities ensured timely delivery of summarized data for informed decision-making and efficient analysis.

Perspective addressed the need for a mobile-responsive application, ensuring that field operators had instant access to system data and could perform maintenance tasks efficiently.

Finally, Ignition's compatibility with the different industrial protocols allowed BWA to make a direct connection with the PLCs at remote stations without having to go through another additional system, thus ensuring the rapid transmission of data to and from the PLCs.

A completely isolated Linux server in the AWS cloud helped address network and outage challenges, ensuring efficiency in problem resolution and data protection.

Results:

Choosing Ignition as a comprehensive solution allows BWA to effectively address all the challenges associated with implementing a modern SCADA system, preparing the organization for future success and maximizing operational efficiency.

The implementation of Ignition SCADA yielded substantial benefits for BWA. The system's enhanced compatibility ensures seamless operation with updated operating systems, alleviating the need for costly software updates and mitigating potential disruptions. Additionally, Ignition's scalability facilitates the seamless expansion of BWA's infrastructure, accommodating growth without imposing additional licensing expenses.

Ignition's Alarm Notification Module significantly bolstered operational efficiency by providing timely alerts to personnel, enabling swift responses to potential issues, and minimizing downtime. The intuitive mobile application empowered field operators with real-time access to critical system data, enhancing responsiveness and streamlining maintenance tasks, thereby optimizing operational workflows.

The deployment of the Ignition SCADA system marked a transformative milestone for BWA, enhancing service quality, and operational reliability while positioning the organization for sustained success in the dynamic landscape of water and wastewater management.

Start Date: January 1, 2022

Deploy Date: January 1, 2024

Project Scope:

Tags: 36,806

Screens: 12 screens + 67 popups

Clients: 10

Alarms: 1,586

Devices used: 41 Rockwell PLCs

Architectures used: Standard

Databases used: One PostgreSQL database

Historical data logged: 1,342 tags, 7,674,244 rows (as of 2024)

Are you curious how Ignition can solve your toughest automation challenges?
Request a free demo that the IA team will customize to your specific use case.

Request a Free Demo

Traditionally, we've always held the Technical Keynote or Development Panel on Day Three of the conference, but this year, we've got something big to discuss, so we've moved it up to Day One of our conference content schedule. It's no secret that we've been working on the newest version of Ignition for several years now, and now we're finally able to dive deep into what's coming in Ignition 8.3 and how its powerful new features can lead users to their next big breakthrough idea!

Transcript:

00:02
Colby Clegg: Thank you. Thank you, thank you, thank you. Thank you. Welcome to the Ignition Community Conference, 2024 edition, Breakthrough. If you can't tell from the pictures, I'm Colby; that's Carl. I think we've been doing this so long, we're starting to look alike. I don't know. But we are very thrilled to welcome you here to Folsom for this week of discovery, learning, and collaboration.

00:37
Carl Gould: Yeah, this event is really the highlight of our year. It's our chance to get together with all of you and, of course, discuss what we've been up to this year. But at the same time, it's just as important for us to hear from you, hear what are your challenges, what are your successes throughout the year, and what are you most interested in right now? Because the collaborative nature of this community is really what makes ICC so special. So whether you're a returning ICC veteran or you're here for the first time, we're really glad you made it out, and we're looking forward to an incredible week.

01:11
Colby: Yes, and what a week it'll be. The pace of innovation in our industry has really been accelerating. It's an incredible place right now. Fundamental technological building blocks have been put in place over the last few years, are being used with new thought processes, new methodologies to build incredible, global, unified systems that are defining the future of automation right now.

01:25
Carl: And, of course, we see Ignition as a foundational part of this future, driving and supporting all of that innovation. And to that end, we're thrilled to be here this afternoon to introduce to you the latest major version of Ignition, version 8.3.

01:45
Colby: Indeed. Thank you. Yeah, certainly, in some regards, this release has been a long time coming. But from a different perspective, the new release is a culmination of a journey that we've been on for a few years. And Carl and I can say with confidence that we really feel that it is the right product for where the industry is at right now. So we can't wait to share it with you. Also, Ignition 8.3 is our most substantial and ambitious release we've ever done. I know we say that each time, but when you consider that the last time we did a major release, consider that our development team was about one-third of what it is now. So this is a substantial release, and we're gonna share a lot of it with you this afternoon by going over three key parts.

02:37
Carl: Yeah, and those three parts are applications, the historian, and our approach to infrastructure. And then, so we're gonna be out here giving a high-level overview of what's new in each of these three areas. And after that, Travis and Kevin will come out, and they're going to go over some examples of architectural use cases, and then after this keynote, right here on this stage, we're gonna be back for some deeper dive sessions going into what these... All these new features that we're about to go over are all about and how to use them. And then finally, we'll be back for a closing keynote on Thursday, where we'll touch briefly on what the future looks like beyond Ignition 8.3.

03:10
Colby: So with the agenda out of the way, we are ready to get started, but we wanted to take one moment just to talk about numbers, because I think that everyone here who's qualified to use our software knows that three does not come right after one. So very quickly, we wanted to talk about why we're calling it this with two key points.

03:27
Carl: Yeah, so the first is just that we really used the time frame that would have gone into developing what would have been a theoretical 8.2 just to make Ignition 8.1 all that much better. And the second one is that we use even numbers to represent releases that don't come with long-term support, and we don't think anybody wants a version of Ignition without long-term support, so we wanted to use another odd number. And those are both fine and accurate explanations, but it's also not a pattern that we wanna keep going with. So after 8.3, we're gonna be getting back to a slightly faster release cycle, roughly two to three years. Four was too long. And the next version will fix this numbering scheme we've gotten into.

04:07
Colby: Ignition XP?

04:09
Carl: Time will tell.

04:12
Carl: Well, let's call it Ignition XP.

04:12
Colby: Well, I got a few years to convince him on that one. But I'll tell you for now, a side effect of calling it 8.3 is that the three invokes perhaps the third part of a trilogy, which is really very much how we see this release. 8.0, 8.1, and 8.3 represent a philosophical progression towards delivering what was our ultimate vision starting a few years ago: to build a completely modern platform to support the next generation of industrial applications.

04:41
Carl: Evolving a platform like Ignition in this way is not easy. And historically, a lot of vendors in this space have really struggled with it over the long term. Continuing to innovate and stay modern while at the same time providing stability and continuity that this industry demands is pretty challenging. But we're proud of our strong track record in this area. We have a 20-year track record of doing exactly that. And 8.3 really continues in that tradition, promising a smooth upgrade experience as we have totally modernized the platform. In fact, when we think about our development process and how we approach what to include in the product and how to change it, we realize that there's really four key forces that we're always working to keep in balance. And those are innovation, continuity, stability, and security.

05:39
Colby: Taking the first two, innovation and security, both of these require constant evolution and change, and those fight against the desire for continuity and stability, which are paramount for plant floor operations. Really, there's one goal on the plant floor, and that is to keep running and keep running well. Well, stability is crucial here, as well as continuity, so that you don't have to continuously reinvent the wheel as new solutions come along. Typically in our industry, though, that has been achieved through the years by sacrificing innovation and security. Innovation is about bringing in new technologies to expand what you're doing, and security really often depends on your ability to evolve infrastructure, adapt to changing environments, and roll out security updates effectively. Balancing these four forces is a complex struggle, but as Carl said, we're very proud of the track record we've built.

06:26
Carl: Yeah, let's take a look at each one individually. So let's start with security. This year, we passed our audit for ISA 62443 security maturity level 3, which attests to the fact that our software development lifecycle considers security at every point along the chain. We also routinely participate in security conference competitions where we put Ignition up in front of security researchers who are highly motivated by some pretty sizable cash prizes to find new vulnerabilities in Ignition. If and when a new vulnerability is found, we're known throughout the industry for having a rapid response time and a transparent disclosure policy so that you can all be apprised of any new vulnerabilities that are found, including information so that you can evaluate whether or not your systems may be at risk, and if so, how to patch them.

07:17
Colby: In regards to stability, we've been working for the last few years to get to the place where today we're proud to say we have a one-to-one engineer ratio between software engineers and QA engineers. So that means that QA is an equal voice in the entire development lifecycle from inception to release. We also work hand-in-hand with our support division, which is in-house, of course, and the front line of our user experience. So support, test, and dev are all able to work effectively together to really be able to deliver changes in a timely manner.

07:52
Carl: Next up is continuity. Around here, backwards compatibility is always job number one, and we have the 20-year track record to prove it. There are systems in production today running the latest version of Ignition that have been continuously upgraded all the way from the old Factory PMI and Factory SQL versions 1, which was the software we had way before we even came out with Ignition. And we're able to do this because we take special care to manage our technical debt, which means that we can ensure that the platform itself is able to stay modern and doesn't get sort of bogged down by its own baggage. This is actually a huge part of the work that went into the development of Ignition 8.3 that should be mostly invisible. So it's not very flashy, but it really is an important point for creating the conditions necessary for this kind of long-term continuity.

08:44
Colby: Absolutely. And then finally, innovation. It's always been our philosophy to not create solutions in search of a problem. We always try to talk to customers and then create solutions that are practical and pragmatic. We also put special attention on creating features and solutions that have the broadest applicability possible and avoid going too much into vertical solutions. Finally, it's important to note that both the product itself and Inductive Automation as a company are the result of organic growth without a expansion through acquisition mentality. And so that helps the product to be much more cohesive and natively integrated.

09:21
Carl: Yeah, for sure. So we wanted to start our presentation this afternoon for 8.3 by highlighting these four topics because, by focusing on achieving balance with these four forces, our ultimate goal is that through Ignition, we can all help you balance these same four forces that are at play in all of your systems as well. But without further ado, let's get into what's actually new in Ignition 8.3 that should help you do just that. And let's start with the category of applications.

09:48
Colby: Yes, and let's start with perhaps the most obvious visual change as you start up a new Ignition gateway, and that is the complete redesign and recreation of our gateway web interface. So our design team reimagined our gateway configured interface from the ground up. We combined years of user feedback and experience with our own increased sophistication in UI and UX design to create an interface that is intuitive, easier to use, more scalable, and packed with clever features.

10:17
Carl: The navigation section of the gateway has been completely reimagined, resulting in a far more logical and structured layout. So items are easier to find, and configuration and diagnostic data have been combined together so that you don't have to bounce around between different sections any longer to both understand what's going on with your system and then also make configuration changes. This interface is also designed to work far more gracefully at scale, providing a consistently fast UI no matter how many items you've configured in your gateways and allowing for multi-selection, bulk edits, and an integrated search capability throughout the entire UI. So there's a lot of advanced functionality to discuss here, but we'll save some of that for the deep dive as we move on to the next UI-focused feature.

11:05
Colby: Yes, indeed. We're happy to announce that Perspective finally gets its own integrated drawing tools in Ignition 8.3.

11:17
Colby: So we've spent a lot of time, a lot of time, creating a completely bespoke drawing interface and making it really good, built entirely to work with Perspective.

11:28
Carl: Yeah, using the new built-in drawing tools, you can start with the existing symbols, you can import symbols from other systems, or you can just create symbols from scratch, all without leaving the designer at all. And the editor has all the kinds of drawing conveniences you would expect in a vector editing package, like snapping and guides and fill and stroke and path editing, layering, et cetera.

11:53
Colby: Best of all, since it was built from the ground up for Perspective, it has native binding integration, which means that you can connect the visual representations of your drawings to your real-time state throughout your system. We know this was a hotly anticipated feature, but it's not all that we have for Perspective.

12:09
Carl: No, not at all. Let's talk about forms. So, input and edit forms, a pretty commonplace part of any application. I'm sure building forms is something many of you who have application experience, application building experience, have spent a lot of time doing. It's kind of a mundane feature. Doesn't usually get a lot of attention, but we've, over the years, observed some patterns in how forms are built over and over again, and we realized that this was an area that was actually quite ripe for some improvement.

12:41
Colby: Yes. First of all, wiring together a form with labels, inputs, dropdowns, and so on is tedious and repetitive. Then, when you think about what should be done in regards to validation and intuitive user feedback, it gets even more laborious. So, of course, we realized we could save you a lot of time by creating a component that helps you with this. So now all you need to do is configure your form's sections, fields, data types, and validations in a declarative manner, and the component will take care of the hard work of making the UI for you, building the form's internal, the form's layout, internal validation, and client-side validation and feedback rules.

13:16
Carl: Yeah, all that automatic layout and having it be automatically mobile responsive, I'm really excited about this. But perhaps the most important part of the new form component is actually in how it deals with packaging up a data submission and sending it back to the gateway, which brings us to the third feature we have today for Perspective.

13:34
Colby: Yes, over the last five years, you've shown how Perspective can be used to create all sorts of applications. But there is one category of application that you haven't been able to create, and those are applications that have to be able to work without connectivity to the gateway.

13:52
Carl: In 8.3, this is no longer a limitation. So now you can design a Perspective application that is designed and built to work entirely offline. The intended use case here...

14:07
Carl: All right. We're glad you're excited also.

14:09
Colby: Somebody knows the use case.

14:11
Carl: Somebody does. The use case is intended for applications where an operator might need to drive somewhere remote, they have no connectivity whatsoever, and they need to gather some data, maybe fill out a maintenance form or read a meter. And in these kinds of scenarios, you'll be able to mark your Perspective application for offline use, arrive in your off-site location, launch it, fill out your form, and submit the data.

14:41
Colby: Yes. And once submitted, the form's data will be queued up, and when the device is later returned into a field of connectivity, that data will be synchronized behind the scenes automatically to the Ignition gateway that the project is connected to. So as always, when we add an additional feature like this, some fundamental building block that opens up a new category of application that can be built, we get very excited to see what you build with it.

15:06
Carl: Absolutely. Because we all know that Ignition is really all about data, right? Acquiring it, contextualizing it, storing it, building useful applications around it. One of Ignition's biggest strengths is all of the different ways data can be used and manipulated. And Ignition is called many things, depending on the context. A data hub, or an edge data collector, or a data ops platform if you wanna be trendy. It can be all those things because of all the different ways data can be used.

15:46
Colby: These are all data concepts that exist today in the Ignition ecosystem. They're technologies that all of you use each day to wire together data in and out and together in different ways. But as we continue to add more connectors and really look at the ways that data can be made more useful, we realized that we were missing a central unifying concept. And that's what we're introducing today with Event Streams.

16:05
Carl: An event stream is essentially a pipeline that maps event data from a source to a handler. Pretty simple idea. And like so many things in Ignition, that simplicity also relies on incredible power. Because inside of the pipeline, you're able to do all sorts of things with the data. You can coerce it and transform it and filter it, batch it up for efficiency's sake.

16:28
Colby: Yes, and both sources and handlers are extensible, which means that all parts of Ignition and modules can contribute them. So when we launch, we'll have sources and handlers for some of the most important key systems in Ignition.

16:45
Colby: That means that event streams are a bus for data in and out of Ignition, but it's also a bus for data inside of Ignition, and you can now connect together many subsystems in a very easy, powerful, and intuitive manner. That power will only continue to grow as we add new sources and handlers over time.

17:02
Carl: Yeah, the real power of this design is in the decoupled nature of these sources and handlers. So let's look at some examples of how this might be used. You might install the new Kafka Module and subscribe to a Kafka topic. Okay, so now events from Kafka are arriving in your gateway. You might also have the Sequential Function Chart Module installed so that when a new event arrives, it instantiates an instance of an SFC to handle that event using some complex logic. Now, the Kafka Module doesn't know anything about the SFC Module. The SFC Module doesn't even know Kafka exists, and yet here they are working seamlessly together through Event Streams.

17:42
Colby: There are really so many great examples we could give. For example, we came out with the MongoDB Connector a little while ago. Well, MongoDB has a cool feature called Change Streams where you can basically register a query and be notified as data changes. So imagine having a Mongo Change Stream observer coming into Event Streams where you're running a script or performing a calculation, or perhaps writing that data to tags.

18:06
Carl: You could pipe Ignition alarm events to an Amazon simple notification service.

18:12
Colby: You could have a whole chain with UDTs publishing changes to Kafka, which are then consumed by a set of front-end servers, for example.

18:21
Carl: Yeah, you can see we're having fun dreaming up all kinds of fun possibilities because the combinatorics here are really fun to play with. There's just so many possibilities.

18:31
Colby: Ignition has so much power in it now, and we're absolutely thrilled about how Event Streams gives us a new way to magnify that power in such a simple and intuitive manner. This new feature basically leverages all of the incredible features of Ignition to create a robust and capable stream processing engine. On the subject of data, you know what else people like to do with it in Ignition. They like to store it and a lot of it.

18:54
Colby: And so let's talk about our historian system. Our approach to history has always been as controversial as it has been successful. Unlock modern open technology to serve your history needs. Yes, we use SQL databases as our historian. Many people love to argue that SQL databases are not industrial time-series historians, but we found those tend to be the people selling industrial time-series historians.

19:22
Carl: What, it's true. What SQL databases do is enable you to use standard, open, well-understood, IT-supported technologies to store any kind of data. They're very flexible. Now, I'm sure there's more than a few enterprise DBAs spread amongst you that might be a little bit upset with us for the amount of data that ends up showing up in their databases that then they are responsible for maintaining, but you can't deny the fundamental benefits of this approach. Open data, industry standard tools, and technologies that your companies already have a lot of standards and expertise built around.

20:00
Colby: Yes, that said, since the first release of Ignition in 2010, we've been asked over and over again this simple question: When are you gonna build a real historian? Well, today, we're gonna answer that. We're not. Now hold on. I see some of you are trying to unbolt the chairs and throw them at me. Don't worry, I'm mostly trying to rile you up, and I actually do have something new for you shortly. But the point is, the answer is more complex than that.

20:27
Carl: Yeah, you know, in the last few years, there's been a lot of really exciting development in the open technology area when it comes to time series data. And a lot of this innovation has come from the consumer IT space, where concepts like IoT and the way the modern internet tracks every click and every impression hundreds of millions of users are making results in massive streams of time-series data. And so it's led to a proliferation of a lot of really interesting, robust, and open technologies becoming available in that space.

21:01
Colby: Yes, today there are so many incredible technologies available to store, analyze, and manage time-series data. When we look at that technology ecosystem and think the way that we have always thought, it strikes us that we don't wanna create another, some sort of new proprietary historian system. No, instead, we wanna make it possible to leverage all of that technology through Ignition.

21:26
Carl: But there's not really any kind of standard for all this different technology, like there is for relational data. So in order to help us leverage all these interesting options, we needed to first create a framework for building historian implementations inside Ignition around these technologies, which is what we've done for 8.3. In 8.3, we've totally rethought the approach to time-series history storage. And we've created a new public API that will allow us or any third-party module author to quickly implement new historian implementations and adaptations around these sorts of storage and querying technologies.

22:06
Carl: It has support for bulk storage as well as streaming data collection and the ability to store rich metadata models along with the history, which will help with the contextualization needed to support more advanced querying. It also supports key historian features like data annotations and native in-engine data aggregation and calculations, and many things like that.

22:30
Colby: Yes, so this means that Ignition isn't just a historian; it's a platform for building historians. And that may be a first in this industry. But I told you, we do have something new, and it would be the first implementation of this interface, and it's called the Ignition Power Historian.

22:47
Carl: So the Power Historian, it's an embedded in-process time-series historian that can store your data simply efficiently with minimal configuration. And we wanna be clear about positioning this correctly. So this isn't supposed to be a drop-in replacement for some grand enterprise historian solution. But it'll make a really big difference in what is becoming increasingly a very common architectural use case.

23:12
Colby: Yes, let's look at one very common architecture today. So virtually everyone is storing history into a SQL database. And the system uses store and forward to get the data there. Well, while the data is in store and forward, it's unavailable to the system. So for that reason, combined with local query performance, it's very common now for users to also add a local historian there in that gateway. And then use the Tag History Splitter to send data to both places. That tool, the Tag History Splitter, manages storing to both areas as well as querying based on timeframe.

23:47
Carl: So the new Power Historian really simplifies this architectural picture significantly. It can serve as a high-performance local historian, and it doesn't need the store and forward system in between the source of data and the Power Historian. It can then be used as a source to later synchronize to a remote historian for longer-term storage. So you can see how much efficiency and simplicity we get by adding this piece into the architecture. And real quickly, talking about performance, what do we mean? What are we expecting? So we've got some preliminary benchmarks out, and we have compared the Power Historian to both our local historian option we have as well as to a popular database system. And I just wanna pick out one key benchmark 'cause I think it's emblematic of the way this fits into the architecture, and that's really about the ingest rate capable with this time series system.

24:41
Carl: So this is a chart showing how many millions of data points per second can be ingested into the new Power Historian. And as you can see, it really blows SQLite and MySQL out of the water when it comes to ingest rates, which makes sense when you think about how we're trying to put it into the architecture and not require store and forward anymore because it's capable of keeping up with the data changes, and it's always local, so it doesn't have any network connectivity fragility in between Ignition and the Power Historian.

25:16
Colby: We'll have more benchmarks coming soon, but to summarize here these key high-level points, what we're talking about is a zero-config, self-maintaining time-series historian built into Ignition that is vastly more powerful than what's already available today for those solutions, that can act as a data source for enterprise data roll-up, thus simplifying architectures, that's part of a unified historian platform that supports richer data modeling and enhanced historian features, and by the way, is still open and non-proprietary in its data storage, and of course, is platform-independent just as Ignition is. So with all of that said, I'm sure you're wondering, Colby, that sounds great, but how much does it cost? To which I respond, nothing. We're including it in the Tech Historian Module. That means that everyone who has that module and has that upgrade protection will get this on day one with Ignition 8.3.

26:21
Carl: So again, this historian really shines when you view it from the lens of how it fits into bigger distributed architectures. So let's take a quick look at what the layers of those architectures look like.

26:35
Colby: This is a message we like to reiterate as we talk about these subjects. We really see edge, plant, and cloud, or perhaps you could describe them as edge, site, and enterprise, as a continuum where multiple levels work together in concert. Each of these layers has its own needs and requirements, but together, they form a homogeneous ecosystem. This is what we've been saying for years now and what we've been building, and we're gonna keep building towards this vision because we believe in it now as much as we ever have.

27:06
Carl: Yeah, and that philosophy can be applied to historical data as well. Each of these layers has its own requirements and its own opportunities for utilizing historical data. At the lower levels, you typically want high-resolution data stored for a shorter time frame in a system that is mostly autonomous and self-maintaining. And then, as you go up the stack, you enter into worlds where you might be aggregating and combining data for an entire region or even an entire company. And that demands a different approach. It demands more of an enterprise-grade engineered solution.

27:40
Colby: And this is a place where maximum flexibility and technological choice is vital. It's simply our philosophy that walled gardens are not the answer. Interoperable technology is. And that's what we're offering here with Ignition 8.3, a continuation of that philosophy. We've created an incredible site-level historian that provides immediate benefit. We've also created a framework for leveraging the world's best time-series technology on an enterprise scale.

28:09
Carl: Yeah, going forward, there's really a lot of incredible potential for us to continue building on this foundation and spanning from edge to cloud with this solution. But what we're offering in 8.3 is such a huge step forward for us, and we're really excited to continue to evolve it over the next few years. And now, let's move on to the final subject before we go into those architectural use cases, which is infrastructure.

28:34
Colby: When we talk about infrastructure, we're talking about how and where you run Ignition. But more importantly, we're also talking about the tools available to you to manage those instances and all of the different pieces that come along with it, the resources, the configuration, and so on. When you're building an HMI or a dashboard, you probably don't think a whole lot about infrastructure. But when you're using Ignition to do everything, everywhere, as we hope you all eventually will, infrastructure becomes fundamental.

29:06
Carl: Yeah, the subject of OT/IT convergence has been a topic that we've been talking about in this industry for a long time now, and we like to feel like we played an important role in helping to ignite that discussion because it's really a core part of our origin, why we even exist. Even before that term was in popular use, one of the first modules we came out with for Ignition was the SQL Bridge Module. What was it bridging? It was bridging OT technology in the form of OPC and IT technology in the form of SQL databases.

29:40
Colby: But at that time, it was really about unlocking value and functionality by leveraging the capabilities of IT software in the OT space. But true OT/IT convergence is far more than that. At the end of the day, it's about bringing together these two worlds that have vastly different engineering requirements and bringing them together to try to find a way to compromise those requirements and find an optimal way forward.

30:08
Carl: So what do we mean by that? On the OT side, as we've been saying, stability and continuity are paramount. Nothing should stop production, and the investment that you put into your OT projects has gotta last a lot longer than the average life cycle of an IT project does. But over on the IT side, you need to be able to manage these applications and systems as well-behaved citizens in your technology ecosystem. They can't be rogue agents or isolated islands that are not touchable. And of course, security is paramount because IT's gotta keep these systems patched.

30:46
Colby: Yes, today we're far beyond the idea that security can be achieved through isolation. And I haven't met anyone recently who doesn't believe that IT working closely together with OT is vital to create a better security stance in our industry. That means agility in responding to threats, frequent updates, and the ability to recover quickly should anything happen. Concepts that are typically far more comfortable for IT than for OT.

31:11
Carl: Yeah, our role is really a lot bigger than just letting you use some neat technology to send a ton of data up to HQ. If you want to achieve true convergence between operational and information technology as you're on a Digital Transformation journey, what you need is a platform that perfectly bridges the unique requirements of both sides. A platform for building OT applications on IT infrastructure. And that's what Ignition is. Hashtag, what the heck is Ignition? I finally figured it out, Colby.

31:45
Colby: I think that competition ended six months ago.

31:48
Carl: Too late.

31:49
Colby: Okay, but what does this mean exactly? What traits make Ignition so IT compatible? And more importantly, what does that mean today for Ignition 8.3? Well, first of all, of course, Ignition is platform-independent. This was a big deal when it was first released because at that time, not only was the industry completely dominated by Windows, far worse, it had become very, very sensitive to OS requirements. In fact, I just heard a story a few weeks ago about a plant that's still running a Windows Server 2003 machine in the corner because they can't upgrade it right.

32:22
Carl: I feel like we all have stories like this in this industry. They're far too common. But it's really not about Windows or Linux anymore. It's really just about being platform agnostic in the first place so that you can just conform to whatever technologies and platforms your IT department can happily keep patched and up to date, which again is vital for security. But Ignition's always been platform-independent. That's not new. So what's new today? Well, today, the discussion about deployment infrastructure has moved far beyond operating systems at all.

32:55
Colby: Yes, today's enterprises are managing resources on an incredible scale. And the technologies to help them manage those resources have really advanced in the last few years. Today, concepts like containerization, orchestration, infrastructure-as-code, and source control are no longer cutting edge. They're just standard tools of a modern IT infrastructure.

33:16
Carl: And there's plenty of ways to leverage these kinds of tools with all kinds of software, but it really works best when that software has native support for these techniques. And we've long been proud of how well Ignition works with these types of technologies, but that support hasn't really been complete in our minds until now.

33:35
Colby: Yes, with Ignition 8.3, we're completing the vision that we had years ago of building the world's most advanced and most IT-friendly SCADA system. So let's start at the lowest level and work our way up to see exactly what that means.

33:48
Carl: Yes, 8.3 really does complete the themes we started and set out within 8.0. So now, all of your configuration is stored in simple text-based configuration files, which means that everything in Ignition is compatible with source control systems.

34:11
Colby: Yes, in 8.3, we've eliminated the internal database, which means that all configurations, settings, project resources, even tags, are in simple and clean JSON, which means that they can be versioned, tracked, and managed with source control tools. Now, when we talk about source control tools, of course, those are very useful for engineering and the development lifecycle, but they also really help with standardization and resource reuse, because that means that all of these resources can be stored and managed and deployed using that tooling system.

34:42
Carl: Remember that shiny new web UI we looked at 20 minutes ago? Well, that web UI is completely powered by a new and modern RESTful web API. That means that everything you can do in that web API, all of that configuration management and diagnostic work, you could now do through an external agent. Furthermore, this API is totally self-documenting, and the documentation is embedded right in the product.

35:07
Colby: This means that Ignition instances can be programmatically configured and managed using standard IT technologies. We almost feel a little bad that we made the UI look so good because the most advanced companies may actually never see that configuration UI.

35:21
Carl: Sad but true. Moving on to what is often one of the trickiest, fiddliest pieces of infrastructure design, which is managing the build, test, and deployment cycle. So one of Ignition's most celebrated attributes is how quickly you can get in there and make changes. The designer's included, you can launch it, change things, hit that save button, and deploy a ton of changes right to production. But pretty quickly, as your project stabilizes and starts being critical in production, and as the teams who are collaborating in a single gateway grow and need to negotiate for resources, you wanna start developing a bit more governance around that deploy, test, develop cycle.

36:10
Colby: In an ideal picture, you would have developers making changes. Those changes would get sent over to a testing system where they'd be validated. Only after that would those validated changes be rolled out to a production gateway. The issue here is that your gateways depend on many, many external resources. And many of those resources may need to be different for each of these stages.

36:32
Carl: Yeah, so in dev, maybe you're using simulators, right? You don't wanna connect to the production assets from development, might be dangerous. Maybe in your staging environment, you have a replica database, not the actual database. There's always little differences between the environments, and that makes the deployment phase pretty challenging, reconciling those differences. And that's always been a challenge in Ignition, something that many of you have come up with a bunch of ingenious techniques to manage in different ways.

37:01
Colby: Yes, well, in Ignition 8.3, Deployment Modes are now a first-class feature. With Deployment Modes, the gateway is aware of which environment it's running in, called the deployment mode. So for example, dev, staging, or production. It's able to automatically change its configuration so that it can load the correct settings based on the defined mode for that gateway.

37:24
Carl: So the way this works is actually pretty simple. So as you configure different resources in your gateway, like database connections or devices, you can define different settings for different modes, and then the gateway will automatically load the correct settings based on which mode it's running in. So for example, if you have a database connection, and you wanna use one IP address in production and a different IP address in staging, you can do that. Those are just different settings for the same resource, active automatically in different modes. The gateway handles this all completely automatically, and to the rest of the system, it's one logical database connection that other systems depend on. So it's really a pretty simple idea, but again, once applied to the entire configuration system, it offers tremendous flexibility in your ability to build a sophisticated environmental deployment process.

38:17
Colby: I think I saw on the schedule that there was a table talk about this subject earlier. So if you weren't talking about this new 8.3 feature, well, this conversation will get easier now. So anyhow, we've just quickly covered a lot of very powerful new tools. Each one of these solves existing pain points and unlocks new potential. But to explore that concept a little more, the potential behind them, and then perhaps introduce even more, a few more new features, we'd like to welcome out here two people who know Ignition use cases probably better than anyone else in the world. No offense. That's okay. With that, please help me welcome to the stage Travis Cox and Kevin McCluskey.

39:02
Travis Cox: Hey everybody, I'm Travis Cox.

39:02
Kevin McCluskey: And hello everyone, I'm Kevin McCluskey.

39:04
Travis: You know, Kevin and I have been working together for years and I think at this point, we know each other well enough to finish each other's...

39:11
Kevin: Lunches?

39:11
Travis: Kevin, I said sentences, come on, man.

39:14
Kevin: Sorry.

39:17
Travis: Well, even though we work together a lot, we both play very different roles. In my role as Chief Technology Evangelist, I focus on spreading the word of success people are having with Ignition.

39:28
Kevin: And in my role as Chief Technology Architect, I get to work with Ignition users and our teams here at IA to ensure that our technology continues to meet the architectural needs of our customers.

39:38
Travis: So in other words, I help people dream it and to see the art of the possible.

39:43
Kevin: And I help them take the ideas that they have and do it in the best way possible for their businesses. And one of the reasons that we both wanted to talk to you about 8.3 is that we're both really excited about the possibilities that 8.3 open up for you, for your architectures today, and going into the future. We know that each of you is at a different step inside your Digital Transformation journey. And no matter where you are in the process, this release has something for you.

40:10
Travis: Absolutely, that's right. Ignition 8.3 is advanced enough for where you are right now and for where you wanna go into the future. Whether you're an Ignition newbie or you have many years of experience working with Ignition, 8.3 is gonna help bring the level and the power of your systems up to a whole new height.

40:29
Kevin: From the beginning, we've always wanted to leverage the latest and the greatest technologies. We're technologists, we absolutely love this, and you know, the whole company is, right? And we've wanted to expand Ignition's tool set so that you can up your game. 8.3 is a great example of that. Take advantage of what makes sense for you.

40:51
Travis: Yeah, Ignition always has been around answering questions like, can Ignition do this? Or can it connect to that? And these types of questions have evolved over the years. Now people are asking more questions around IT technologies than ever before. And the idea is to be able to answer the questions that are important to you. And the questions that people need answers to depends, though, on the level of sophistication they have with their systems. Now, when I say sophistication, I'm not talking about complexity. It's more about your Digital Transformation journey, and what part of that journey you're at right now. We've broken down Ignition 8.3, and this new release, into four different categories. And that is projects, data processing, system management, and IT. And today what we wanna do is talk to you about how the features of Ignition 8.3 help accomplishing your goals in each of these categories much easier.

41:41
Kevin: The first level is that of your typical SCADA application. If you've created a project that uses Perspective, Tag Historian, SQL Bridge, and you're doing very sophisticated things inside a single Ignition gateway or redundant pair, what you see here might represent you. In this example, it's advanced project design doing a lot of really cool things with this relatively simple architecture and without wider, company-wide data flows. If you're doing an IIOT system or using Ignition communication layers like MQTT or more Ignition gateways in a scale-out architecture or multi-site architecture, your complexity might look a little bit more like this. And if you're doing a full enterprise system with hundreds of locations, multiple connections, advanced deployments supported by orchestration and supported by IT departments, your sophistication level might look a little bit more something like this, where it's high across every category.

42:37
Kevin: Everyone's at a different stage inside their sophistication level and inside their journey overall. So to help understand how 8.3 can make things easier, no matter where you are on this journey, we're going to show you which of the features that Carl and Colby just talked about are going to be the most useful at each of these levels of sophistication, starting with projects.

43:01
Travis: Right, so the first area is project sophistication. And these are tools that help you build better projects, especially around SCADA. So let's say you're a brand new user to Ignition. Building a complete SCADA system is easier than ever with the new Power Historian. You can simply deploy a single Ignition server and everything's up and running. You can connect to all your devices, you can log all that data to the Power Historian, you can build up your applications and launch clients very quickly. There is no need to install any separate software.

43:35
Kevin: Yeah, so a lot of folks are used to having Ignition with a SQL Database right alongside it, even for simple applications. You can still do that, of course, and we do encourage it for more complex systems. But if you're just dipping your toes in the water of Ignition, so to speak, and you wanna spin something up really quickly, having a Historian built in along with charts and graphs and the other visualization tools all inside Ignition, that new Power Historian makes it really easy for new users to roll that type of thing out.

44:07
Travis: Yeah, and now let's say that you're an existing user and you already have a system up and running. 8.3 adds the ability to connect to more devices with the addition of the Siemens S7+ Driver. Siemens PLCs are becoming way more popular and we're seeing them used for a lot of new projects that are out there. We wanna make sure that Ignition has the relevant drivers for you to do your job.

44:30
Kevin: That's right. With a lot of folks who are using the newer Siemens processors, this is a really big deal because it allows you, if you're connecting to those processors, basically, you understood and been using symbolic addressing and you've been using some of the optimized block addressing and probably, I don't know, 20, 30% of folks inside here have struggled with that in the past, right? With the new driver, you don't have to worry about using third-party drivers or manually configuring tags from a spreadsheet or connecting to and reprogramming and changing some of those options inside the existing Siemens PLCs. This new driver just connects immediately, allows browsing, and really speeds up the time to deploying Siemens-based projects.

45:17
Kevin: And another thing that's really easy to connect to in Ignition 8.3 is Twilio Voice and WhatsApp. With native integrations to these two services, you can send out notifications to the people the way that they want them.

45:30
Kevin: Ignition's existing notification system can already send things out to SMS, email, voice over SIP or voice over hardware, get one of those boxes and go through that. We've got the Grandstream and a couple others that we recommend there. These new notification options expand out on that more to give you more services, which really gives folks a lot of great additional options here. IT loves these for a couple of reasons. They're simple, and they also reduce that need for physical hardware. It reduces or eliminates that footprint on-premise.

46:05
Travis: I'm really excited about these features, but I gotta tell you, I'm really excited that we can, for the first time, actually draw a circle in Perspective.

46:16
Kevin: Travis. Ah. What is it that they say? Sometimes the simplest things are the ones that matter the most. Seriously, though. Perspective Drawing Tools, not Perspective Circles. We know people have been asking for this for a long time. We're really happy that we're providing this first-class, state-of-the-art drawing tools that you saw earlier directly inside Perspective.

46:42
Travis: For sure, and this feature's really gonna get us to get people the confidence and the speed to build full HMIs with Perspective to really take advantage of the most amazing, the most advanced visualization system on the market today. So, like Carl said earlier, Perspective, there's a lot of new tools that are coming in there. And in addition to drawing tools, Perspective's also taking forms to that next level. There are a lot of customers out there that need to collect data in remote locations that have very limited or no connectivity at all. And this makes it really challenging to collect inventory or sample data and get that information back into Ignition. And we've all had to do this before by building custom-built solutions. That is very difficult to maintain over time. This new form component and offline capability, it gives you the ability to do that so easily. It's gonna be a game-changer for data collection possibilities inside of Ignition.

47:33
Kevin: I've built a lot of forms in Ignition over the years, as I know a lot of you have as well. And I can tell you that there's a substantial amount of time that goes into building good forms. 8.3 is going to make that so much faster and easier for folks to build forms. And when you combine that with the forms offline mode, it's going to be a really nice experience for building projects, especially things that are replacing clipboard entry or some of the traditional types of forms that people would be walking around and filling out. You can do that inside Ignition in a way that is quick, economical, easy to implement. We have a bit of an internal mantra. It's "First make it possible, then make it easy." This is a perfect example of doing just that, where form applications inside Ignition were possible before, and they were good. But with these new features, we think they're really gonna be great going forward.

48:31
Travis: And I think we could expand that mantra to a lot of the features that 8.3 is bringing. So all of these tools here, they really help you in building better SCADA systems, and they give you more tools inside of Ignition that you can take advantage of to accomplish your project goals. Now let's move on to the second area of sophistication here, and that is with data processing. So everybody's level of sophistication with data processing is changing all of the time, right? Customers wanna make the most of their data, especially with getting data to the business. Well, with more devices we wanna connect to, more systems we wanna integrate with, and of course, more places we want that data to actually go, 8.3 is gonna help people up their game in data processing. First off, in 8.3, OPC UA is getting some updates. Now you can actually securely share specific tag data to specific places or clients.

49:26
Kevin: Yeah, with tag sharing, it's really nice. You can pull in a set of tags for a specific system to share them with a third-party OPC UA client. This allows other systems to get data that they need from Ignition without sharing more tags than you want to. We're also updating the OPC UA stack to the latest Eclipse Milo version, supporting OPC UA 105, and additionally, we're going to be adding OPC UA events to Event Streams so we can easily handle events coming from OPC UA.

49:54
Travis: And of course, that brings us to Event Streams, which I personally think is gonna be a huge game-changer. It's gonna really accelerate the movement of data from OT systems into business systems than ever before. We're gonna be able to leverage the full power of all the connectivity options that are in Ignition, from OPC UA, MQTT, SQL, of course with the new Kafka connection, and a lot more. Now speaking of Kafka, that is the standard enterprise message bus for almost every large company in the world.

50:25
Travis: They use it to talk to ERP systems, scheduling systems, and a lot more. And with Event Streams, Ignition's collection with Kafka is gonna be first class. Event Streams allows you to move data in unique ways without writing a single line of code.

50:39
Kevin: I'm really excited about Event Streams. This is one of the features that I've been talking to everybody at Inductive about for quite a while here. I think it's going to be a really significant feature, and I'm seeing it in two different ways, right? That it's useful for two different types of folks inside an organization. One would be the folks who use Kafka or other IT message-oriented platforms. It's gonna make Ignition really easy, as you saw earlier, and Carl and Colby were talking about, really easy to bridge that IT/OT gap with the right tools built into Ignition. The other category is folks who are using Ignition for tag change scripts, using Ignition in other places, and they wanna manage changes or events that are happening centrally in a way that everyone who's designing inside Ignition has access to. An event happens; could be a tag change, an alarm change, something in the database triggers it, and you wanna respond to that event inside the SCADA system directly. Event Streams are gonna be a fantastic way to do that directly inside Ignition.

51:40
Travis: With all of these tools, Ignition continues to accelerate building UNS architectures. You know, you hear a lot about UNS today from groups like 4.0 Solutions and Sesame. Ignition allows you to provide a single source of truth of your operational data that is clean and contextualized.

51:58
Kevin: You can easily contribute to a UNS of your choice, Unified Namespace, right, whether that's a pub/sub system like MQTT or Kafka, storing that data at a warehouse or anywhere, really, with context. Not only that, Ignition can also easily access data from a UNS system, providing dashboarding and visualization to anyone.

52:22
Travis: So in 8.3, there's a lot of new connectivity options and tools to help users accomplish their data processing goals. Now, of course, systems are getting a lot larger, and with larger and bigger systems comes a need to have better management. And there are a lot of great tools in 8.3 that are gonna do just that, and let's start with the deployment modes that Carl mentioned earlier. A lot of people are developing on a single production server, and they've started out with that; they've built a small system, and over time, they've built that up, and it's scaled up to be a very big system.

52:55
Travis: That became a critical system for that company. And at that point, making changes to a production environment is risky, right, and it's not the best practice. So really, it's about adding a development environment, and doing that now with 8.3 is easier than ever with this new deployment mode.

53:11
Kevin: The idea is that you have separate environments, Carl and Colby; if you were paying attention earlier, this looks very familiar, of course, but just to go over it again, right, the idea is to have these separate environments that you have different changes, and you might develop new changes that have differences between production, between your development system, between your QA system. And that production environment might have real PLCs, the development environment might have simulator PLCs instead of real ones; different SQL databases; more things like that.

53:39
Kevin: This feature allows us to define the configuration for all the different environments inside that single Ignition server. It means we can deploy one backup containing everything to multiple different environments. You don't have to worry about merging your changes from one environment to another, plus you can define the deployment modes that you want.

54:04
Travis: So now you can actually have a true development environment where you can build all the configuration for everything, you can test it out in a safe way, and you can deploy, of course, when you're ready.

54:11
Kevin: To deploy, you can simply take a backup from the development server and restore that to the production system manually, or if you wanna use source control, you can push changes from a repository and pull them into production when you're ready.

54:26
Travis: Exactly, and change tracking is incredibly important. In Ignition 8.0, we dipped our toes into that, right? We started making this easier when we moved the projects into the file system, but it was just the projects, not the rest of the configuration. But people wanna track everything, right? And with 8.3, all the configurations in the file system, and this is a big deal to make change tracking very simple. So now you can do it in a first-class way using systems like Git, which is really the most popular system around and the one that folks are trying to use and getting information about with us.

55:00
Kevin: If you've ever tried to use source control systems with the SCADA system, you'll know that some things get tracked and others don't, and others end up in binary formats that might be hard to work with. Sometimes it's kind of terrible. So, but you know, honestly, with the way things are set up with 8.3, it's amazing now. So behind the scenes, the changes, for moving everything to disk, having everything stored in configuration, that's JSON files, the internal database going away, and switching that all out, you can track everything. So if you're taking a look at project versions, you can see what changed, when it changed, what system it changed on. And Travis mentioned Git. A lot of folks use Git, but you can use other systems as well, since everything is file-based. So anything that plays with a file-based storage system is going to play well with Ignition.

55:50
Kevin: Now, if we combine source control with deployment modes, like we were taking a look at just a minute ago, it's easier than ever to track your changes and have that true environmental separation at the same time.

56:05
Travis: So with things like deployment modes and change tracking, handling more sophisticated levels of system management is easier than ever with 8.3. Another thing that's gonna be easier is working with IT departments. Increasingly, we're seeing OT and IT teams working together, especially to better manage OT systems. And IT wants to be able to help, not only by helping with system management but also by integrating with IT tools to help enhance a system and follow established best practices. So at this next level, we're gonna talk about the IT tools that 8.3 can easily integrate with, and the first one is with Secrets Management.

56:43
Travis: So Secrets Management is where you can pull out all of the secrets from within Ignition. These are the passwords, the credentials, and put it into a secrets vault that can easily be managed. And it can also handle encryption keys and certificates. Now, this has several major security advantages.

56:58
Kevin: Yeah, so for example, say IT sets up a Microsoft SQL Server database and gives you a service-level account to it. You know, a few months later, maybe they come and they want to change the password. Oh, without Secrets Management, it could be a daunting task.

57:14
Kevin: I think we've all been there, right? I certainly have, and you know, a lot of folks simply push back and might actually win that battle and not do it and have that password just stay the same because they don't wanna change a production system. You know, that could also be a potential security risk if that password ever gets compromised. By putting passwords inside a secret spot, they become much easier to manage; auto-rotation becomes something that can be automatically done, and it mitigates a lot of that risk. However, the biggest advantage here, in addition to that, really, is taking secrets out of Ignition's configuration. So let's go back to that example of setting up, you know, IT setting up that database.

57:58
Kevin: If they give you credentials to that database and you put the credentials into Ignition, then one day you need to send that gateway backup to us for support or you start working with a new systems integrator. Those credentials are included in the backup. If you're using secrets management and externalization instead, that won't happen because the credentials live in the secret manager that's outside of Ignition and they're simply used by Ignition.

58:21
Travis: Another area that IT can help is with deployments. You know, recently we've seen an increase in the number of devices that Ignition's being deployed to on the plant floor, right, with the proliferation of the edge. And as a result, we've seen the use of containerization grow incredibly fast. I wanna bring up a couple of other updates here about containerization. First is that we're actually bringing Ignition Cloud Edition to the container marketplace. So, on AWS, so Amazon ECS will now be available to spin up Ignition Cloud Edition instances.

58:52
Travis: And we're working with partners like CradlePoint and Digi and others who have orchestration platforms of their own, allowing Ignition to be deployed simply with one click using their marketplaces.

59:04
Kevin: This makes it really easy to get containers deployed on-premise and in the cloud because you're not having to install software anywhere. Basically, so, as you know, we've always said that Ignition has a three-minute install. It's one of those other mantras that we have, which it still does when you're installing in the traditional way. But with containerization, Ignition is a 30-second install, and that's with a full system, with configuration, with connections, all of that. It's just built in. Containerization is pretty incredible and enables a lot of things that we'll see in the next couple of slides here as well.

59:40
Travis: So now, when it comes to being able to deploy a lot of Ignition systems and then send out fleets of configuration changes or being able to manage it from third-party tools, the new REST API is gonna be another game-changer. I think I'm saying that a lot here today. But with tools like, using tools like Ansible to be able to access status and configuration or any other third-party tool that IT has, they can use the tools that they're comfortable with, they can get information from Ignition, they can create their own alerts, and they can manage Ignition the way that they want to.

1:00:11
Kevin: As you can tell, we're going up in sophistication level here, and not everyone's going to end up using this feature, and that's okay. But for those of you who are familiar with REST and web services, this is gonna be a really nice feature. And if you're not at that level yet but you want to get there, this is gonna be here to help you and make it easier when you're ready. The REST API will also help with wide-scale deployments and orchestration, which is the next feature we'll talk about.

1:00:36
Travis: Yes, so we talked about containerization and being able to deploy a Docker container. But there's a lot of IT departments that are setting up Kubernetes clusters both on-premise and in the cloud, and they want to deploy Ignition through that. And with Ignition 8.3, we're doing something that's pretty unique here, Kevin. So what the helm are Helm charts?

1:00:57
Kevin: I see what you did there. So Helm charts, I'll reset for a second. Helm charts are these fantastic configuration files. If anyone's ever worked with AWS CloudFormation scripts or other systems that fall under that wide catch-all phrase of infrastructure-as-code with scripts that set up architecture, Helm charts are another example of that. They're not only some basic configuration scripts, but they can go pretty advanced, and they also are fully cross-platform. So they're not specific to any specific cloud provider or set of infrastructure.

1:01:33
Kevin: Helm charts are for this system called Kubernetes that probably most folks have heard of. It's the most popular orchestration system that's out there, and it can really help with these large deployments.

1:01:44
Travis: So for example, if you wanna spin up several Ignition gateways, or you wanna spin up a scaled architecture or any other deployment that you'd usually install Ignition on a number of different places, and of course connect them all up together, these Helm charts are gonna make that incredibly simple.

1:02:03
Kevin: And we're releasing many of these. We'll have a lot of Helm charts and Helm chart options that are built into the Helm charts that'll allow for a lot of different configurations and going to make it really easy for folks to use Kubernetes to quickly spin things up, spin things down, move them around, orchestrate things in a way that requires less work. We're releasing them with 8.3, so when 8.3 is released, all of these Helm charts are going to be released along with it.

1:02:31
Travis: So as you can see, no matter what the sophistication level of your system is, Ignition 8.3 has answers to questions that you are facing. And the next question you might be asking is, okay, Travis and Kevin, when can I start doing this stuff? When can I start getting access to 8.3? So let's talk about that.

1:02:50
Kevin: I'm glad you asked, Travis. So happy to announce the beta's gonna be available soon. We're looking at a December release, so we're targeting that. Look at the forums if you wanna participate. You can go there; there's information there, and there's also going to be feedback that's going back and forth through the forums. Some of you asked about a private beta, and we have a list of folks who are interested in that as well. And what we decided to do is basically take a look at the release, and when it's good enough for a private beta, we're instead going to make that a public beta for everyone. So everyone's going to be able to get access to that.

1:03:28
Kevin: That's happening in December, and so stay tuned for that. Also, during the beta period, we'd like to ask you, please keep the feedback contained to the forums. So please don't call into tech support with your 8.3-specific troubleshooting steps quite yet. The forums, the folks on the forums are the actual developers who built the 8.3 features, and so they're really best equipped to be able to help you.

1:03:53
Travis: And once it's released, we'll be back to our regular five-week coordinated minor release cadence. That's our release train that we have. Expect releases of 8.1, though, to slow down significantly, as we only plan on releasing patches for security, vulnerabilities, or critical bug fixes that we find.

1:04:18
Kevin: As far as support goes, as mentioned earlier, 8.3 is a long-term support release. That means active support for five years from the release date and two years of limited support following that. In case you're not aware, active support is support from our development team. It covers additional features, bug fixes, and security updates for the lifecycle. It also covers support from our technical support team via email and phone. Limited support is a two-year period right after that, where our development team is no longer providing updates for the software. Because of that, we always recommend upgrading before this window. But if you miss the date, that limited support, it provides limited email and phone support. You can see in the diagram that there's a great overlap window between the two, right? We're giving two years between 8.1 and 8.3, so there's plenty of time to plan an upgrade.

1:05:10
Travis: Right, which brings us to upgrades. So let's talk about upgrading to 8.3. The reality is that 8.3 brings a lot of amazing new features everybody wants to take advantage of, and they're gonna wanna upgrade as soon as it's ready. Now, of course, 8.3 is perfect for a brand new projects. So any new project out there, go ahead, start using that. Now, if you're already on Ignition 8.1 and you wanna upgrade to 8.3, the upgrade's gonna be seamless, right? Carl talked about that we want the backwards compatibility to be there all the way. That is certainly true with this release. And you can simply follow our upgrade guide when it is released. Now, I've got a lot of confidence in our release process, but of course, a trust but verify approach is always prudent for upgrading existing production systems.

1:05:53
Kevin: And if you're upgrading to 8.3 from an older version, you'll need to upgrade to 8.1 in order to upgrade to 8.3, go through a two-step cycle there. So if you have 7.9 or any other earlier system, 8.1 or even before 7.9, now's the time to upgrade them to 8.1. So 8.0, 7.9, 7.8, whatever it happens to be, you'll wanna hit 8.1 so that you're ready to do the upgrade when 8.3 comes out.

1:06:20
Travis: Now, individual system upgrades should be seamless. Full system upgrades with multiple Ignition gateways are also seamless, with the notable exception of the gateway network connectivity. 8.3 will communicate with 8.1 gateways, but not prior. So this is because of our updates to our encoding formats that we use to help improve our security posture.

1:06:46
Kevin: Good news, if you are purchasing today, anyone who purchases a license with any support plan from us, basic care, priority care, total care, it doesn't matter; you're covered for 8.3; it's guaranteed that that license is going to work for 8.3. If you have licenses today that aren't under support, you can add support right now, and you'll be ready for 8.3 when it comes out. And if you have, for example, end-of-year budgets that you're looking to spend or a project that's gonna be happening soon, now is really a great time to get lined up with that 8.3 guarantee. Just make sure you include the support plan when purchasing.

1:07:21
Kevin: So we've covered a lot this morning. Incredible new tools like the Power Historian, Event Streams, Perspective Drawing Tools, rapid form building, offline data collection, along with a slew of connectivity features and enterprise tools for customers who can use them. I am really excited about 8.3, and I can see that a number of you are as well. I know you are too, Travis.

1:07:44
Travis: I am unbelievably excited. I'm like a kid in a candy store.

1:07:49
Kevin: There's so much packed in here.

1:07:50
Travis: For sure. So we really hope that during our presentation today that you've heard something about 8.3 that inspired you for your next breakthrough idea. And we have some more to share with you later today. After this keynote, we're gonna have two breakout sessions this afternoon, which will go into deeper dives in 8.3 for the platform and the features. So if you wanna learn more, please make sure to stay here on stage one throughout the rest of today.

1:08:17
Kevin: Digital Transformation is a journey, and every journey is traveled one step at a time. I hope that you see that whatever and whenever the next step is for you, Ignition will be there along with you to make that next step easier. Wherever you wanna go, Ignition is the foundation for the future. And wherever you are now, there is something to get excited about with Ignition 8.3. And as always, we're really excited to see the projects that you build with this amazing new technology. Thank you so much for coming. Have a great time at ICC. Thank you.

Since the Ignition Exchange’s introduction in 2019, members of the Ignition community have contributed hundreds of resources ranging from pre-built templates, tools, and scripts to Ignition-powered retro arcade games — all available for free. Discover the full potential of the Ignition Exchange as we highlight some of its most valuable assets, including a handpicked sampling of the top Exchange resources developed by IA engineers. 

Transcript:

00:10
Mara Pillott: Hi, everyone. Welcome to the "Ignition Exchange Resource Showcase." We are Dereck and Mara, and we are the Application Engineering Managers at Inductive Automation. In application engineering, we implement Ignition projects for internal customers, for product demonstrations, and the Ignition Exchange. We also present webinars and presentations and consult with our customers on proof of concepts, best practices, and project planning for successful Ignition projects. Dereck, tell us a little about yourself.

00:40
Dereck Saunders: Thanks, Mara. Hello, everyone. I'm Dereck Saunders. As Mara said, I'm an Application Engineering Manager at Inductive Automation. Previously as an application engineer, I've worked on a variety of Ignition projects for oil and gas production, solar and winds, automotive manufacturing, water/wastewater, food and beverage production, inventory management systems, and more. Today, Mara and I lead a team of application engineers that help develop Ignition proof of concepts. We consult with customers on Ignition design best practices. We contribute resources to the Ignition Exchange, and we help develop a variety of Ignition projects, like Inductive Automation's public demo projects.

01:17
Mara Pillott: I've been working with Ignition since 2010 and previously served as a design services engineer. I've built a variety of projects for our customers, and I've also assisted them one-on-one with learning to build their projects. Most of my experience is in custom database solutions, and I'm giving a workshop next week for using databases in Ignition. So I hope to see some of you there. Today, we're going to talk about how to use the Exchange to elevate your projects.

01:44 
Dereck Saunders: Alright. So here's our agenda for today. We will be giving an overview of the Exchange, what it is, where you can find it, and how you can use its resources to elevate your project development. Next we'll go over a series of resources developed by IA that we would like to share with you today. After this session, we hope you'll explore some of the resources showcased, as well as the many resources developed by the Ignition community. Finally, we'll wrap the session up and answer some questions. So with that, let's get started.

02:09
Mara Pillott: So what is the Exchange? To explain, let's go back to the beginning. If you were here in 2019 watching the Build-a-Thon, you will remember when our own Kent Melville gave us the Exchange. Our dev team wanted to make Ignition even more customizable, encourage more collaboration, and help you save more time. We created a new online community with free resources. Now some of these are built right here at Inductive Automation, but you know what's really exciting? You, our community, are able to share your own resources. Today we're gonna be highlighting things that were built here at IA, but I encourage you to share your own and to check out our many community contributions. So what can you find in the Exchange? Well, really just about anything you could think of. I want you to go to the Exchange and try searching on keywords, categories, types. You're gonna find everything ranging from just like a single view, some scripting resources, entire projects, and so much more. Go check it out.

03:09
Mara Pillott: So why would you use the Exchange? You can just build anything you want with Ignition, but why build everything from scratch? Using prebuilt Exchange resources is going to jumpstart your project and save time. And you can use that for those trickier parts of your project that always seem to take up the bulk of your development time. You can find prebuilt projects in the Exchange and use those as a starting point. Once you download a project, it's yours. You can add views, make any changes you like. You can also find some prebuilt components and add those to your project. Today we're gonna show some examples where we start with a fairly complete project and we're gonna add some resources to improve it. We're also gonna show you some full project resources. We're focusing on only a few resources built here at Inductive, but there's many high-quality community resources. We encourage you to check those out and build your own. You could also keep your own set of resources just so you have a consistent look and feel for all of your projects.

04:05
Dereck Saunders: Alright, so just going over the resource submission process a little bit, resources are initially private when they are first submitted to the Exchange, and they are individually reviewed by an application engineer at Inductive Automation, and they're reviewed just to make sure everything with the resource generally works as expected and that it meets the quality standards expected for the Exchange. If we do find any issues during the review process, we provide feedback directly to the developer to help them improve the resource. And then once the resource has been approved, it's made publicly available on the Exchange. So there's a couple different ways to integrate Exchange resources into your projects. You can import them manually by going through the standard import process in the designer, or you can import them from the Ignition Exchange page on the gateway web page, which you may find to be just a little bit more convenient.

04:52
Dereck Saunders: So when we start to take a look at our specific resources in our presentation, you will see that some of them are deployed in a sample project. Our application engineering team developed a general manufacturing demo depicting the assembly of solar panels using robots for adhesive application and material handling. This demo will become the Perspective demo in the future, but we've decided to use it here as the foundation and backdrop to showcase a variety of IA-developed Exchange resources. With that, let's get into it and start talking about some of the great resources developed by IA. Our first resource is the Perspective Tag Meta Property Viewer. So in this resource, it includes a view that can be used as a pop-up to view any tag's meta properties from a Perspective session. Normally opening up the Ignition designer would be required to easily view all the tag's meta properties, but this resource provides the ability to view a tag's meta properties in real time from a Perspective session.

05:42
Dereck Saunders: This view is built to work dynamically with any standard tag type, so memory, expression, query, derived, whatever it may be. This resource is also configured to work with tag drop, so you can drag any individual tag onto a view and it will give you a small tag icon, which is dynamic based on the tag type. Hovering over the tag icon will display the full tag path, and clicking the icon will open the Tag Meta Property Viewer pop-up. Opening the pop-up will allow you to browse and view the tag's meta properties and also any custom properties that the tag may have. This will also work with any tag inside of a UDT, and all property values displayed are read-only. The main header includes the tag type, in this case a Boolean, the full tag path, its current value, quality, and timestamp. Similar to the tag browser in the designer, the header also has icons in the top right corner to indicate if the tag has scripting or alarms configured on it. Any tag scripts like a value-change script can also be viewed to further assist with any potential troubleshooting, diagnostics, or anything like that right from the session.

06:47 
Dereck Saunders: Alright. Next we have the Perspective Toast Notifications developed by Application Engineer Conner Futa. This resource provides the ability to create toast notifications in your projects. These toast notifications are commonly used in mobile-specific projects for tablets and phones, but these can also be deployed in a standard desktop Ignition application if you wanted to. These appear as small pop-ups with text, and they can be configured to be click-dismissable, autodismiss after a certain amount of time, and slide in from different directions. This resource does include a small demo to help get started to see some of the options for configuring toast in your project. You can simply enter the text you want to appear in the toast message, set a number of seconds for the message timeout, and click "send toast" to see it in action. There's also additional configuration that you can set within the demo to customize the toast. You can see different locations like top left, bottom right, center, set the animation style like center right, or enter top, and the message type as well.

07:44 
Dereck Saunders: Give these various options a try to see what works best for you, and then you can use the main views and scripting to build your own custom toast notifications in your project.

07:53
Mara Pillott: Thanks, Dereck. I'm going to gonna have some toast with my next project. Our next resource is Comments by Application Engineer Mitchell McPartland. The Comments resource can be used to power a blog-style system within your project. This can be useful for some ad hoc collaboration and communication between shifts or remote users. We see in this screenshot, people are discussing a fault. These notes are gonna be saved. We can look back at this later and see if this maybe happened before and who knows how to fix it. Now, you're probably going to have specific loggers in place to capture information, but this is something you can do really quickly and just give you a free-form method of communication. So resources are generally gonna include some README, maybe a guide or install notes. This page is going to tell us about the supported databases, the main view parameters, and if we want to know more about the resource, we've got a PDF document in the download folder. Now the first thing to note is we're gonna need a database connection, and we've got two parameters to set on a view. So we know we've got a database connection or gateway, we're going to hop in the designer.

08:57 
Mara Pillott: So this view is in the Comments folder under the Exchange folder. You will see some resources with different folder usages, but we really encourage you to put everything in a folder named "Exchange." This is gonna keep things separated from your other project resources and avoid any duplicated names. So any parameters I have here, I can set at runtime, but just to get started, I'm setting this database connection and schema parameters, and I'm gonna save the view. And those are the two properties I have highlighted in yellow. Once I've set the properties, I can click Create Database Tables, and that's gonna go ahead and create all the database tables I need, no setup in the database for me. So there's a few more parameters here. I'm just leaving date format default. Date range can be used for filtering. Instance name is gonna separate out your comments into different groups, and we're gonna see this in a minute. And you can change the default title to anything you like.

09:51
Mara Pillott: So I've got my pop-up all configured, and I need a way to open it. I want to have a set of comments for each robot. I'm gonna open the robot pop-up view in the designer. I added a button with a comment icon, and I'm gonna add a pop-up action. I just picked my comments view, and the only parameter I need to pass is the instance name, which I'm just binding to my robot name. So let's see it in action. The blog icon opens the comment's pop-up. They're organized by the instance name we set, so this is only showing comments that are related to this particular robot, and we can view all previous comments and add our own. So I'm the Robotech user. I want to let everybody know that I've got this robot calibrated. I'll just add that comment, and we can see it there. They've got some additional features. You can pin them, just like on a traditional forum. You can save your favorite comments. Users can edit or remove their own comments, but they can't remove anybody else's comments. And you can search these guys. You can filter them by date range. Maybe I wanna know when diagnostics were last run. I can just type that in the dialog box, and I can see if I've got any results related to diagnostics. There I go.

11:11
Dereck Saunders: Alright. Thanks, Mara. The next resource we're gonna take a look at is the CSS Animation Guide: A Robot Example developed by Application Engineer Mike Bordyukov. So this resource provides a detailed guide on how to perform basic animations in the Ignition Perspective Module using CSS. This guide covers how to create smooth motion, pause and resume animations, and synchronize two robots using a state machine. This project starts with basic animations and then demonstrates how to create more complex movements. The intermediate example shows how to combine multiple rotating elements to create an animated robot. You can adjust angles and duration to see how property adjustments affect the animations. You can also view the designer properties to better understand how to achieve and implement and adjust your own animations. The advanced example shows how multiple animations can be synced together, for example, a robot placing an object onto a moving conveyor, or in this case, two material-handling robots passing an object. These particular animations are controlled by a UDT with a state machine, allowing for animation pausing to accurately depict the actual robot or equipment movements and position.

12:16 
Dereck Saunders: The UDT tab of this resource includes more details on how the state machine is being controlled behind the scenes. Alright, so now let's take a look at the Simple Perspective SVG Editor developed by Application Engineer Charles Ahrens. So this resource is meant to allow users to edit SVG drawings that have been generated or modified within the Ignition designer as well as save those SVGs out as drawings out of the designer. You can add or edit circles, rectangles, paths, and text, and you can adjust the properties and color of each shape's fill and stroke or apply transforms to those shapes. You can edit drawings in either the designer or web browser and export those drawings to your computer as an SVG file. Alright, let's take a look at the SVG editor in action. Here we can see how to draw some simple shapes and maybe add some text to an SVG drawing. These shapes obviously aren't being used together to show a more complex drawing or depict equipment, but it should instead give you an idea of what the range of possibilities are with this awesome drawing tool in Perspective.

13:19 
Dereck Saunders: Next, let's take a look at a more practical example where we're editing an existing valve SVG. So here we can see how we can go in and manipulate and edit the valve to our liking, and then when we're happy with how it looks, we can download to use it elsewhere and clear the canvas for our next drawing. I'm honestly a fan of all the resources that we're showcasing here today, but I think this resource in particular really underscores the impact and importance of the Ignition Exchange and all the possibilities that it can unlock, thanks to the contributions of our Ignition community as well as our application engineers here at IA. Okay, so we just looked at how to draw and create SVGs in Perspective, but what if you want to take it a step further and animate them? So next we have the Perspective SVG Animation Resource, which was also developed by Application Engineer Charles Ahrens. This is a teaching/learning resource similar to the CSS animation guide that we looked at earlier, except this deals with SVG animations.

14:14 
Dereck Saunders: This resource has a few examples of SVGs being manipulated by elements within Ignition to create dynamic objects. Following these examples, a user could create an SVG representation of complex equipment in their facility and animate it dynamically to give users of that display a better idea of what is happening behind the actual process. Starting simply, the basic example shows how to move a circle around the screen controlled by two simple sliders for the X and Y coordinates, as well as a slider for changing the radius and color of the circle. Again, a very basic example just to start things off. The intermediate example uses some more complex expression bindings to draw a line connected between the center of the canvas and the center of the circle, which follows the circle wherever it goes. Additionally, this view has the ability to have automatic movement and the circle will rotate around the center point following a path that can be changed while running with the sliders.

15:05
Dereck Saunders: This automatic movement can be toggled with the manual and auto buttons. The advanced example uses lessons of movement and rotation and combines them into a robot arm, which has four positions that can be saved automatically and moved between them with a smooth motion. If you're looking to learn how to animate SVGs in your Ignition project, whether it's something very simple or even more complex, go check out this resource on how to get started.

15:29 
Mara Pillott: Wow, those are some amazing graphic tools we could use in almost any project. Our next few projects are simple but very powerful. First is the Copy to Clipboard by Application Engineer Conner Futa. This allows us to copy any text on the screen into our clipboard. In this case, let's say I sometimes just need to copy a serial number for robots so I can look up documentation or send emails to a vendor. If you wanted to look something up and they said, "What's your serial number?" and you had to go find it, you know how annoying that is. I added an embedded view to the robot view. I set my path to a link to the Copy to Clipboard resource in the Exchange folder. I've got one parameter named "toCopy" and I'm going to bind that to my serial number. So let's see it. I just click the copy icon next to the serial number. The icon turns green, so we know we've got the text in our clipboard, and we can paste it anywhere we like. I'm just going to go ahead and paste this into my email where I'm requesting some service.

15:38 
Mara Pillott: Next we have our JSON Viewer by Matt Raybourn. This resource exists just to make JSON human readable. Our imaginary robot manufacturer provided us some diagnostics as a JSON string. It's pretty long, it's not human readable, and it's not very useful in this format. In our JSON viewer, it's much better. It's human friendly, it's color coded, it's nicely formatted. We can find what we need here. We can pair this with Copy to Clipboard, and we can paste this in an email or a report or anywhere we want. We're going to stay on the subject of powerful user interfaces as I turn this back over to Dereck.

17:05
Dereck Saunders: Thanks, Mara. Our next resource is the Pan Zoom Frame developed by Application Engineer Mike Bordyukov. So this resource enables the manipulation of images or other views using CSS transformations. It offers two distinct views: a generic view that allows panning and zooming of any embedded view, and a specialized view for image components that provides more options for customization. As the name suggests, with this resource, you can pan over images or SVGs to provide a more interactive viewing experience. In this particular case, we can see how this resource is used to pan over an Ignition architecture diagram, but this could be any image, SVG, or even just another embedded view in Perspective. Even though this is just an architecture diagram, you can see how this could be especially useful for panning and zooming over detailed schematics and line drawings. While the pan zoom capabilities of this resource are awesome, this resource takes things a step further, allowing you to leverage dynamic displays that are driven by zoom level. By that, I mean we can design an embedded view to react to the zoom level of the pan zoom frame, which allows us to display certain components and details when zooming in, but then hide them when zooming out.

18:12
Dereck Saunders: Maybe we have a lot of tanks or other type of equipment on an overview screen, and we want the overview to stay relatively simple, but we still want to be able to drill down and get more details like tank level or tank contents without navigating away from the overview to a different screen or open a pop-up or dock view. This dynamic display driven by zoom level allows us to accomplish that all within the pan zoom frame, and this design approach certainly won't work for every project, and there will definitely be cases where it still makes sense to use a classic pop-up to drill down, but I think this resource offers a different and intriguing design approach that could be really useful in certain scenarios. Switching gears a little bit, let's talk about IEC 61850 and in particular the IEC 61850 Scripting Demo developed by Training Content Creator Rob Lapkass and Lead Quality Assurance Engineer Garth Gross. If you're unfamiliar with IEC 61850, I'm not going to go into all the details here, but we do have some great resources and articles on our website and in the Ignition docs to help break it all down. Essentially it enables device interoperability and data standardization in electrical power systems and provides a better way for IEC-compliant field devices to read and write data.

19:23 
Dereck Saunders: We recently released our IEC 61850 Driver for Ignition, and with that came some new scripting functions to help explain those new functions. And to help explain those new functions, we have an Inductive University video called "Using IEC 61850 Scripting Functions," and this resource is a copy of the view shown in that video. While most of the features will not work without a valid device connection, you can still download the resource and take a closer look at how the scripts work and potentially connect an IEC 61850 simulator device as well. Staying the topic of IEC 61850, let's take a look at Sales Engineer Tom Goetz' IEC 61850 Graphics resource. The goal of the Ignition Exchange resource here is to provide basic graphics and configurations to components related to the IEC 61850 Driver. The configuration allows for users to change color, text, visibility, rotation, and state of switches and breakers.

20:17 
Dereck Saunders: The configuration works both in the designer as well as in session, and if modifications are allowed in session, a SQL database can be configured to store and retain changes made in the session. You can arrange and use any of the custom components as you would any embedded view to build out a substation layout, or you can use the dashboard component in this resource for easy configuring and arranging of the graphics. Alright, next let's take a look at the Inventory Prediction Manager developed by Sales Engineer Reese Tyson. So this application is built off of a UDT and scripts that monitor levels, predicts a run-out date using linear regression, and notifies emails, notifies a list of emails before the inventory runs out. The linear regression is performed on the historical data of the inventory levels to create a prediction of the date that the inventory will run out. Once that date is established, a user-configurable lead time can be set which will determine when the notification is sent out.

21:14 
Dereck Saunders: This application is designed to take a proactive approach to making sure material is available when you need it. As you can see, the Inventory Prediction Manager is also mobile responsive. Alright, next we have the Mobile Responsive UI resource. This resource was a joint effort by Application Engineers Conner Futa, Chase Dorsey, Sales Engineer Tom Goetz, Sales Engineering Director Kent Melville, and Design Department Manager Ray Sensenbach. Mobile responsive means creating an app that is easy to navigate, visually appealing, and functionally consistent. However, there is no user manual to tell you what to include in your mobile app or what structure is best for your purposes. This resource has examples of good mobile-responsive design, all wrapped up in a semifunctional demo CMMS project. The best practices for design include intuitive navigation, reversible actions, informative feedback, smart defaults, accessibility, error design, protecting user work, visual clarity, progressive disclosure, visual style, and functional behavior.

22:15 
Dereck Saunders: So this resource is also meant to be more of a teaching or learning tool than an actual resource that you would deploy in your project. It showcases a lot of great design techniques that I just mentioned and could also help inspire your next design or take your current mobile project to the next level with excellent UI that feels intuitive and is easy to use. If you're looking for an example of some stunning visuals and best practices in UI/UX, definitely go check out this fantastic resource.

22:42 
Mara Pillott: Well, speaking of user interfaces, our next resource is the Perspective Alert Dialogs, again by Ray Sensenbach. If you're like me and you came from the Vision world, you may have noticed that we can't use things like system.gooey.confirm or message box in Perspective. Perspective is HTML-based, so if we want those dialogs, we have to create some pop-up views. We could create them ourselves or we can use these nice themable dialogs that Ray already built for us. Like a lot of resources, it comes with an information view that's going to help you get started. The dialogs are totally customizable. You can select a theme to match your project. You can warn against an action, let users know if an action was successful, alert them to an error, or just give them some information. The alert pop-up is a single view with several parameters. They're going to set everything, icons, button text, message text, all your actions. Best of all, they're extensible. They come with some built-in functions, and you can add anything you like. Let's hop in the designer.

23:41 
Mara Pillott: So we can see we have several parameters for text, icons, and actions. We can set the action for each button. We can set any of these icons, alignment, remove icons, and we can change the state based on the states we saw in the previous slide. Each button has a set of message handlers. We can see here we've got two handlers, one for closing the pop-up and one that will log us out of our session. You're not limited to what you see here. Like I said, you can add any of your own custom message handlers. I have an icon over here that I can click to log out of my project, but I want to let users confirm before they close that project. I added an event handler. It's got a pop-up action. I set my parameters. I want my log-out action for the primary button, and for my secondary button, I just want to close the pop-up. I set some yes and no text, and it's not visible here, but I set a title and a message. So let's see it in action. I click the log-out icon and realize I don't want to log out. I can just click no, and the close pop-up action executes.

24:48
Dereck Saunders: Alright. Thanks, Mara. Now let's check out the System Monitor resource developed by Application Engineer Tyler Earnest. So this project is a basic system monitor for CPU and memory utilization of the gateway PC beyond that being used by Ignition itself. This is accessed using the Java ManagementFactory library. Two Perspective views are provided. One is a mobile view showing real-time details, and the other is a desktop view showing historical details over the last five minutes using tag history. An included system monitor UDT can be imported that includes CPU, total memory, available memory, and calculated in-use memory. So here's a better look of the desktop view showing those historical details for the CPU and memory usage. Obviously, you can customize this, alarm on the UDT tags for high CPU and memory usage or embed this elsewhere as part of a larger in-session diagnostics bundle. While it's common for Ignition to have its own dedicated server, there are definitely instances where Ignition is installed alongside a database or other software where knowing the overall machine CPU and memory usage and potentially alarming on it might be quite useful.

25:54
Dereck Saunders: Alright. Next, we have the GeoJSON Explorer developed by Application Engineer Mitchell McPartland. This Perspective project can be used to display GeoJSON data in the Map Component. For demonstration purposes, this resource retrieves datasets from data.gov that can be modified, and it can be modified such that it retrieves datasets from other sources as well, and there are examples included in this resource. You can browse a selection of datasets that the developer included and see a lot of different ways to visualize GeoJSON data. As cool as all the examples are, you will really unlock the full potential of this resource by leveraging your own GeoJSON data. There's a good amount of options you can choose from to display the GeoJSON data differently, including the base map type, the overlay, and the theme. We just talked a few minutes ago about UI/UX best practices with the mobile-responsive UI resource, but I think this resource also really showcases some really clean and intuitive UI.

26:49 
Dereck Saunders: And as you can see, this resource is also fully mobile-responsive and can be run on a phone or tablet right out of the box. And lastly, before I turn it back over to Mara, let's check out the Perspective Electronic Signature Framework resource developed by Chief Technology Evangelist Travis Cox. This resource shows how to leverage the new authentication challenge feature in Perspective to perform electronic signatures with full auditing. This resource provides a framework and example that you can use in your project. This resource is designed to be extended to any kind of action you want to perform. The example provided shows how to perform tag writes with a two-stage verification process. And this resource was made possible through the collaboration with 4IR, an Inductive Automation Solution Partner. 4IR Solutions provides an easy way to deploy Ignition and its partner ecosystem into the cloud via a fully managed solution. They have deep expertise in 21 CFR 11. So yeah, this is a really neat resource that Travis put together with 4IR and provides some awesome new functionality with this electronic signature framework.

27:53 
Mara Pillott: Alright, we've seen some pretty cool resources today, but I have one here that's going to help you with just about any project that you have. I talked about themes a little when I introduced dialogues. Ignition comes with built-in themes, but like anything, you're not limited to just what is built in. You can build your own themes using the built-in themes as a base. Now, these themes are built using cascading style sheets, but you can modify these with your favorite text editor, and if you want a more visual tool for building themes, check out this Theme Builder by Sales Engineer Tom Goetz. Let's take a minute and just talk about themes in Perspective. This was a little new to me coming from the Vision world. So like I said, it comes with built-in themes, and this is going to provide an initial style to your components. Now, we're going to focus on color today, but the themes allow you to change all the styling. For example, you can change scrollbar width or the default borders. The themes are built on cascading style sheets or CSS, like I said. These advanced users, you're going to just you're going to learn this very quickly on your own, but this resource is going to help you build a set of colors visually.

29:01 
Mara Pillott: So how does this look in a Perspective project? We saw an example of this in the dialogs project. There's a built-in session property for theme. Changing this theme is going to change the default colors of your components. Here we can see that choosing between the themes changes our background and text colors. I don't have any colors or styles set for these components. These are just default colors, and they're based on the theme. They range between light and dark, and you've got some cool and warm selections as well. Now, you can set custom colors for your components, or you can use the themes to just give yourself a set of color variables. In this example, I want purple buttons, but I still want all my buttons to work with the theme. I chose sequential 4 for my button background color. It only applies to this button, and it's going to follow my theme selection. So using light, I'm going to get a dark purple button with white text, and if I switch over to dark, I'm going to get a lighter background and darker text.

30:01
Mara Pillott: You can also use theme colors in your style classes. So in the previous example, I was just working with the color selection for a single component, but using styles, I could apply these selections to multiple components and give my users a consistent look and feel. So that gives you a few basics on themes, so let's see how we can use this theme builder to create a new theme. So the main view shows you all the colors in your selected theme. You can start with any existing theme as a base or import a theme. Here, I'm selecting light and dark, and we can see that my color sets are changing with my selection. Configuration is on the left, and the theme colors are displayed on the right. This just gives me a chance to preview. So I'm going to start with the dark theme, and I'm going to start changing some colors. Notice that the colors are grouped. In this example, I want to change my neutral colors. I want lots more blue, and I'm just going to slide that blue selection all the way over. As I change this, you notice that the preview colors change. The original colors are in one column, and my updates are in the far right.

31:08 
Mara Pillott: So this gives me some idea of where I'm going, but I don't really know how this is going to look on a screen. Well, I got a preview mode, and I can test drive my theme. Now I've got a really blue background, and you can see my neutral colors range from blue to yellow, and this really hurts my eyes, and I've gone way too far. But I got a reset button. I can reset everything using the bottom reset button, or I can just reset to a neutral group. Now maybe I just want to make a few changes. So I would just like call to action to be a nice Ignition orange. I can expand the individual color config, enter in my hex color, and apply that to call to action. So check it out. I get a nice orange color listed in the preview pane. I can come over here to see how it would look on my screen. I've got standard light theme for everything except call to action, and just a few other selections like my checkbox and slider are now the orange color that I'd like. I can keep making changes, and I can just see what they look like right here on screen.

32:11 
Mara Pillott: I'm going to apply my ICC 2023 color to the diverging colors and to the info color. I expanded the diverging color selection, entered in the hex color, and I applied that to the starting color property. All the diverging colors changed. Next, I expanded the individual color config and set that same hex color for my info. Once I'm happy with my theme, I'm going to want to use it in all my projects. So it's time to build my variable CSS file. I'm just going to click my build button, choose a starting theme, give it a name, and I can download this as a zip. So I've downloaded it. What do I do with it? Well, like a lot of the resources we have here, we've got a README file in the download, and I just had to copy my CSS file in my theme folder into the Ignition program files. So once I've got the theme in the Ignition install directory, I can use it. I can just go to my session property for theme, check out my dropdown selections. My new ICC 2023 theme is here. I can select this and notice that my button color is changing from that default blue to my new custom orange.

33:25 
Dereck Saunders: Nice. Alright. Thanks, Mara. So those are all the resources that we had to share here today. We do want to let you guys know that there are going to be some great new features coming to the Exchange soon. We do plan to add resource ratings, which should be great, and even more search capabilities. So stay tuned for that. And we look forward to bringing even more improvements to the Exchange in the future. Also, every single year we host the Ignition Exchange Challenge now. So all resources entered to about a month up before ICC are eligible for the challenge. And the winners will be announced at the live Build-a-Thon after this session, so you'll be learning their names soon. And we look forward to this year's announcement and seeing all of your new resources in the coming year. Lastly, while we wanted to showcase resources today that were developed by our application engineering team and others here at IA, we still want to say a big thank you to the entire Ignition community that contributes to the Exchange.

34:17 
Dereck Saunders: There have been a lot of incredible resources that have been built just in the last year by the Ignition community, and we invite you to go visit the Exchange now or later and check out all of the resources that are available. You might find something really useful that you've been waiting for but you didn't think existed. You might find something that you can leverage and build on to accomplish your project goals. You might find a helpful learning resource that helps you take the next step, or you might find something that inspires you to go create that next amazing feature or project. And if you build something that you think is useful, fun, or just plain cool, please upload it to the Ignition Exchange and share your creations with the Ignition community. Inductive Automation's motto has long been: Dream It, Do It. And I think that motto is personified, and to borrow a term that you may have heard once or twice this week, elevated by the Ignition Exchange and its contributors.

35:04 
Mara Pillott: So once again, we just really want to thank all of our contributors from Inductive Automation and all of you for what you've done in the Exchange. We've seen some amazing resources today. I just cannot wait to see what you, the Ignition community, are going to develop next. You never fail to surprise me. With that, we're going to conclude our presentation and answer any questions you might have.

35:36 
Audience Member 1: So the question was, if we're going to contribute to this, and we're working for a company, what is it that they have to agree to? What are the legal kind of, what's the paperwork?

35:47
Mara Pillott: Sure. Everything that you download from the Exchange is freely available and free to use in your, in anybody's projects. And it can be changed or modified at will.

35:57 
Audience Member 2: If he contributes.

35:58 
Mara Pillott: Sure. Sure. So if you want to ask something of your users, that's really, you know, that they give you credit or anything else, that's really not part of the Exchange. It's a freely available resource.

36:12 
Audience Member 1: So basically, the, whoever we work for needs to be okay with, basically.

36:16 
Mara Pillott: Oh, absolutely. Sure.

36:17 
Audience Member 1: Yeah, yeah, yeah. So what is the, is there like a legal, is there like a form you have to sign to sign away the...

36:24 
Dereck Saunders: There's an agreement that you sign when you set up an account for the Exchange, but that's essentially it.

36:29 
Audience Member 1: Okay. Thank you.

36:33 
Audience Member 3: I was wondering if there's talk about adding more videos to how to use these tools like you had today.

36:40 
Dereck Saunders: Yes, great question. And that is something that we are planning on doing. Right now, you know, if you uploaded a resource, you could potentially include a link to YouTube or whatever it may be for that resource. But our team is planning in the future to provide videos for every resource that's uploaded by IA. So in the future, the idea is to have a video companion with every resource that we make.

37:03 
Audience Member 4: So how do you decide which applications make it into the main installer? Or what should live in the Exchange?

37:13 
Dereck Saunders: Sorry, you're asking what our approval process is? Or just somebody who's just using the Exchange?

37:17 
Audience Member 4: Oh, what made you put it on the Exchange instead of just putting in the main program? Since it's being developed by the same company?

37:25 
Dereck Saunders: Oh, like why isn't in the platform that you would download with Ignition?

37:27 
Audience Member 4: Yeah.

37:28 
Dereck Saunders: Yeah. So you know, our dev team has a lot of things that they want to add to Ignition and a lot of things they need to maintain. With the Exchange, we have the flexibility to have developers build things that they think are useful. Maybe a while ago, it might be something that we might have built for one or two customers. Now we have the ability to build something that might be more generic and share it with a lot of different people. So it just gives us that flexibility, where we can build something that maybe dev would like to do. And maybe we'll come to Perspective or Ignition or whatever it may be someday. But you can essentially build something and upload it in a few weeks and have it be available for people to use.

38:01 
Mara Pillott: And it allows people outside of Inductive Automation to also contribute to this community, collaboration is very important here at Inductive. And even though you're giving your resource away, you're really publicly showing people what your developers can do. And I think there's some... There's some contributors that are pretty famous, really in the community for what they've built here on the Exchange.

38:23
Dereck Saunders: Yep.

38:25 
Audience Member 5: Are there any constraints on the sort of things we can put up on the Exchange, such as like injecting JavaScript into views and then with that, when it comes along to 8.3, are you doing regression testing on Exchange resources?

38:42 
Dereck Saunders: So I'm not sure on the JavaScript question. I'd have to check on that. We do do a full review of the resource. So anything that gets uploaded before it goes public for anyone to download, we do do a full review of the resource. And then for 8.3 in terms of regression testing, that is something that we probably will have to look at. But I don't know that we'll be going through and doing every single Exchange resource, probably the ones that IA has developed. But that'll probably be something that will be the responsibility of the person who uploaded the individual resource.

39:09 
Mara Pillott: And our developers are committed to making sure that you don't have regression problems with 8.3.

39:17 
Audience Member 5: And aside from JavaScript, are there any other absolute no-no's in terms of if I'm going to put a resource up there that you just say you shouldn't be doing that sort of thing?

39:27 
Dereck Saunders: I don't think so. If it's something that you can build in Ignition and it's part of your project, you can essentially upload it. Again, we do review the resource for anything that could potentially be malicious or anything like that. But yeah, if it's something that you can build in Ignition, you're pretty much free to upload it.

39:42 
Mara Pillott: There are certain types of function calls that we are specifically looking for in the review process that we might not allow. So if we had questions about anything you had built, or even if you have questions before you build it, go ahead and talk to us because we might be able to have a conversation with our reviewers about that.

40:01 
Audience Member 6: Just a suggestion of either a feature request, like someone could request a resource and people could look at making that or having a challenge or something to create a certain kind of resource for future stuff.

40:17 
Dereck Saunders: Yeah, you can go to the Ideas section of the Inductive Automation website and there is an Exchange section there where you can put in requests or just ideas or just see the status of something that you may be interested in. Yep.

40:29
Mara Pillott: But I like where you're going with that.

40:31 
Dereck Saunders: Yeah, for sure.

40:31 
Dereck Saunders: Exchange specifically.

40:34
Dereck Saunders: But other than that, I think that's it. Thank you.

40:38 
Mara Pillott: Thank you. Just like us, I'm sure you're looking forward to Build-a-Thon.

Come and learn with Cirrus Link and Snowflake what your data has to say. Snowflake, Inductive Automation & Cirrus Link have partnered to provide Data Cloud Solutions. With Ignition UDTs, MQTT, and Sparkplug, discover how easy it is to leverage Snowflake’s platform to gain derived data insights immediately through native AI tooling. Learn about the impact of the recent partnership of NVIDIA and Snowflake. See how this disrupting technology, in conjunction with Ignition, will elevate and simplify your journey to data insights. 

Transcript:

00:00
Travis Cox: Let's do it. Hello, everybody. Welcome. Hope you guys had some fun here today, so far. I know the session's been pretty amazing so far, yeah? We definitely have another great session for you now. Hope you guys are excited about this one, Accelerator for Driving Edge to Cloud Business Outcomes, and we're gonna show a complete edge-to-cloud solution today using data models, and we're gonna actually bring in the Data Dash and kinda show you how all that comes into play.

00:30
TC: Got three amazing speakers, really two, besides myself. We got Arlen Nipper, who is the CTO for Cirrus Link Solutions. He's the man, the myth, the legend behind MQTT. I'm sure a lot of you know him. Excited for having him here today. We also have Pugal Janakiraman. He's the Industry Field CTO for Manufacturing for Snowflake, and he's responsible for building higher level solutions to kinda drive business outcome for manufacturing. And we're really excited about this particular session. We're gonna kick it off with Arlen. He's gonna show, we're gonna show Ignition Edge and Ignition, how we can bring that in through MQTT to the cloud, bringing that from IoT Bridge over to Snowflake. We're gonna show you that whole journey here this morning. So Arlen, without further ado.

01:16
Arlen Nipper: Thank you. Thanks, guys. Thanks, everybody. Everybody enjoying it? This has been awesome so far. So real quick, Cirrus Link Solution, we've been around... This is our 11th year now. We've been growing year on year. This has been a fantastic journey for us. And we started eight years ago. I was over in stage two. And I did the first ever MQTT engine demo. That was our first Ignition module. From there, we've developed a whole line of Ignition modules, as well as products that we support, including the Chariot standalone MQTT broker, and all of the IoT Bridge products that we've developed for getting data out of Ignition into the cloud. So where I'd like to start is largely due to the community and all of the feedback and the involvement of all of you.

02:13
AN: We started with MQTT and the first demo that we did was just Arlen and one of the engineers I worked with. And we had a little binary way that we published MQTT. It was great. As we started going to conferences and all of that, everybody goes, oh, we do MQTT, and we do MQTT, and we do MQTT. But if we would've plugged it all together, nothing would've worked, because the topic namespace would've been different, the payload would've been different. So we started on a journey for our own sanity five years ago. We said, mm, let's invent a spec. And since we have Engine and we're running on Ignition, let's call it Sparkplug. And so we started the Sparkplug specification. And again, it was internal. People started looking at it, Ignition users. I still remember Chevron going, "Well, Arlen, who owns that?" And we said, "Well, it's up on our public GitHub site. You can download it, it's open source." "No, really, who owns it?"

03:12
AN: So at that point, we kinda went on this journey of taking the Sparkplug spec to the Eclipse Software Foundation, which is a standards body and we worked for three, almost four years, in getting the spec cleaned up and getting it ratified. And at the end of last year, Sparkplug 3.0 was officially released. And from that, what you see up here, is that resulted in the release of a Technology Compatibility Kit. So that means that if you're doing MQTT Sparkplug, whoever wants to do it, you can download the conformance kit and you can run your client against it and get conformance-tested and get listed up onto the Eclipse website, so that we have interoperability. So when Todd Anslinger at Chevron orders your module or buys your product, he can be assured that it is Sparkplug B compliant going forward. And then other thing interesting from that is that because of Eclipse and their relationship with the IESO, IEC standards body, now Sparkplug is pending, but it'll be an international standard, IEC 2237. So now Sparkplug will be an international standard.

04:29
AN: And then the last thing I wanted to mention is that I know a lot of you, especially in manufacturing, you deal with a protocol called MTConnect. MTConnect's been around for about 15 years. There's probably over a million CNCs and Lays and Autoclaves that talk MTConnect. And the cool thing about MTConnect is they already do data models, but they do them with XML. So if you want to get the spindle speed from a current MTConnect, you do a get and it sends you back a 300K XML file that you can parse down and find the spindle speed. And what they've realized is they wanna be able to publish those MTConnect models using MQTT Sparkplug. So we are working with the MTConnect Foundation to natively have MTConnect agents running on CNC machines and Autoclaves and all this other equipment, be able to publish that information natively. And you can imagine, that means you could have a whole factory with all of this machinery. You turn it on, it publishes into Ignition, you automatically learn everything about those machines, which would be pretty cool. That's our end goal, if you will.

05:46
AN: So the other interesting thing, we hadn't even thought about it, so I had Chris run a report and say, well actually, how many people are using MQTT Sparkplug? And at this point in time, there are over 1,300 separate companies that are using MQTT Sparkplug. And six years, seven years ago, if I were to put this pie chart up, it would have been 95% oil and gas. And over the last four or five years, you can see, we've expanded pretty much across this technology, across all of the verticals that Inductive Automation is in. So the adoption for MQTT Sparkplug across all of the industry section has been huge going forward. So real quick, I just wanted to review this. What does Sparkplug do? Well, it does four important things. Number one is it gives you plug-and-play auto-discovery. So with a well-known, with Sparkplug, you know what the topic is, you go subscribe to it, it publishes a message, you get the message, and you go, oh, I know where you came from and I know what you wanna do.

06:58
AN: So, high level, gives you plug-and-play auto-discovery. Number two, very important, as we're finding out, as Colby and Carl talked this morning, this is digital transformation. And to do that, you can't have data in the data swamp, you have to have contextualized data that you can actually see from a business-level standpoint of what that data is. So with Sparkplug, we can publish a model, or the definition of that. Now, you instantiate that and create the asset, and I hate the word, but we'll call it that, you create your digital twin. Now, everybody's notion of a digital twin is different. I think ours is the best and we'll see that in the demo here in a little bit.

07:43
AN: The third thing that Sparkplug does is that we have been wrestling with registers from PLCs and our sensors and our flow computers for the last 47 years that I've been doing this. Modbus register 40002, and it's got a value of 17. 17 what? Degrees, gallons, we have no idea, so what do we do? We sat a human being in a chair, and we said, "Okay, Arlen, engineering high is this, engineering low is this, engineering units is that, and I hope I typed it all in correctly because you're gonna run your plant with all of that information that I just typed in."

08:21
AN: But with Sparkplug, we create a digital object that I can go back five years from now from this Snowflake demo that I'm gonna do, find that tag, and I can tell you the name, the value, the timestamp, the engineering high, the engineering low, the quality, and any other custom property you wanna decorate that measurement with and get it into Snowflake, we can do that now with Ignition. And then the last thing Sparkplug does is it gives us that state management. Because if I can't guarantee that I know the state of all your process variables, if you're doing command and control, or you're going to the cloud, then you're not gonna trust that, you're not gonna use Sparkplug. So, Sparkplug tells you that you are online, that value is last known good, and then if your network goes down, you're gonna know about it, all the tags will go scale in Ignition, but when it comes back up, we know at the edge, at the Ignition Edge, everything we would have published goes into a store and forward queue, and now we can do store and forward.

09:24
AN: So with Ignition on the left side, we've got that brownfield connectivity that we need to connect to all those different protocols, all those machines, and bring that into the Ignition platform. From the platform, we've got a really cool tool called UDT, and with that UDT, we can organize that data, we can give it context, we can give it engineering use, give it engineering high, we can give it asset properties because it's very important. Think of like PI Asset Framework, you've got all your asset information over here, which is different from your historical data over here, but we're gonna be able to put that together in one single database, and then we can take MQTT transmission and publish that to an MQTT infrastructure, where it can be consumed by what? Well, it can be consumed by Ignition, for sure, but we're introducing IoT Bridge for Snowflake. So those Sparkplug messages coming from Spark, from our MQTT transmission module into a server, well, IoT Bridge sits there, it's an MQTT client, it knows how to receive those messages coming in, and then using Snowpipe Streaming, we can do sub-millisecond inserts into rows into Snowflake data tables.

10:45
AN: So that means that we can take all of that contextual data we have in Ignition, and by a click of a button, get all of that natively into Snowflake, the data cloud platform. But wait, what is Snowflake, right? So I'll bring Pugal out, Pugal will tell us. Now, Pugal and I have a bit of a history. We've been working together since AWS IoT, and right before Christmas last year, Pugal called me, he said, "Hey, Arlen, I'm the manufacturing CTO for Snowflake," and I said, "Great, Pugal, that's fantastic. What's Snowflake?" And so here it is, it's incredible technology, and here's Pugal to tell you about it.

11:31
Pugal Janakiraman: Thanks, Arlen. Okay. So what is Snowflake? There is a reason why we sat together and picked Snowflake as a platform to build this out, because this is an Industry 4.0 journey. There is a whole bunch of requirements around Industry 4.0. One is that the attractive thing around Industry 4.0 and value proposition is you need very high level of compute, you need an extremely performant database out there, because this is a big data problem. You're bringing in huge volume of data, spanning IT and OT data sources into one location, whether you call it as unified namespace or a centralized location where you can facilitate IT and OT convergence, you need a high-performance database out there. So, the challenges I have seen, been in the middle of a few hundred of these Industry 4.0 initiatives, is today if customers want to go build an Industry 4.0 solution, if they pick a cloud vendor, you have to learn around 200, close to that amount of services, elemental services, stitch it together to build a solution, govern all of it, go through the whole journey of learning that and go from there.

12:45
PJ: That is hugely challenging for most of the customers we work with. So what do we do here? Snowflake is a globally connected cloud vendor agnostic data platform. So what does it mean? You don't have to go learn hundreds of services from multiple cloud vendors and build an Industry 4.0 solution. We got that covered. It's one single managed service from Snowflake. We take care of security, we take care of governance, we take care of scalability. Every one of it is taken care by us. And after that, much more cool, your API of choice is still SQL. You don't have to learn hundreds of new services. You continue to use SQL as a mechanism to leverage data which is present in Snowflake, whether it is around building dashboards or you want to build an AI and ML model or build inference around those models, you still use SQL as an API for doing that.

13:38
PJ: So this is extremely powerful, one-stop shop, easy button to adapt to the cloud. And that's what we bring to the table, Snowflake as a company. The other one, as I said, you need a highly performant database to do that. So Snowflake is a cloud-native database built 100% on cloud, and it is one of the most performant database today in the market today. Again, this is not a marketing statement. If I had to pick a number, I just brought up a number on what really is the kind of transactions which happens in Snowflake today. So April of this year, 2.9 billion queries was launched in the Snowflake data platform. And around just in one single customer, one single table, there are around 50 trillion rows out there. For us to go operate and pull up millions of rows and visualize that, it's no big deal. We do that on a daily basis.

14:33
PJ: And it's around the largest number of queries within one-minute interval a customer is executing, around 160,000. 177 petabytes of data just on five customers, what is being maintained within their database. So big data handling, we do it on a daily basis. That is our lineage. We started as a data warehousing company and built a data platform around it. So handling this volume of data is pretty much a daily affair for us. So other one around collaboration. There is a whole bunch of customer ecosystem built around Snowflake. Data sharing between different customers, it's a matter of you don't copy the data over, you can just refer to the data and still run analytics. Why is it important? You got a whole bunch of OEMs and you got a whole bunch of suppliers out there. If you want to share quality records or you want to share connected product performance data to your supply chain, you don't need to copy the data over.

15:33
PJ: Data can still reside on-premise or it can reside in whatever is your cloud vendor of choice. You can run analytics without the data movement out there. So we provide that kind of collaboration mechanisms. Another cool thing, with the volume of data, just visualizing billions of records or millions of records, human mind cannot comprehend that and derive inferences out of it. We provide AI and ML-based analytics. In fact, yesterday we demonstrated how you can just provide the data set to our pre-built anomaly detection algorithm. It is going to tell you that there is an anomaly going to happen and you might want to take a look instead of getting into an unplanned downtime kind of situation. So we do that as well. We provide all this reference architecture as part of Snowflake data platform. And obviously, with all these capabilities, it accelerates the analytics adoption, whether it is on IT or OT data or a mix of both.

16:31
PJ: So that's what Snowflake brings to the table from a manufacturing perspective. There's a lot of technical detail behind this. Feel free to stop by at our booth. We can go through this in detail on, any level of detail on what you would like to understand around what Snowflake brings to the table, technically speaking. Just to summarize, so what does it mean for customers and partners? So we got it covered, whether the data is sitting in silos of database and on-prem systems or it could, across different organizational boundaries, data is distributed, or it is distributed across multiple cloud vendors, across multiple regions, we can run analytics seamlessly. So I think that is one of the major value proposition we bring to the table. So any data products you build and offer to your customers, it's global in nature. It can scale. We got the security covered. There is seamless collaboration which is possible between you and your customers, and your suppliers.

17:31
PJ: It's not an issue at all, okay? Performance, as I said earlier, we got the performance factor covered as well, okay? Added to that we got thousands of customers today using Snowflake for various analytical needs today with pre-built integrations with popular systems like SAP, in addition to OT systems which Arlen talks about and which he's going to demonstrate as well. And we provide Snowflake Marketplace where you not only can take the products you've already built today on Ignition, you can monetize those data products and offer it through our marketplace to thousands of customers we got around the world. So that's what Snowflake brings to the table. Instantly scalable. You can build global data products which you can take it to your customers. So pretty much that's a Snowflake value proposition.

18:25
PJ: So again, quickly before I hand it over to Travis, this is how the journey started for us. Ignition on Edge with zero coding using Snowpipe Streaming API, send the data to Snowflake. So again, this is one of the best integration built by any cloud vendor as of today from a cost point of view and a fidelity of data point of view. To accurately represent every possible manufacturing data in cloud, you need to support around 13 data types. No other cloud vendor does that today. So maximum they support is four data types, which means all the other data types, you slam it on the existing data types you support. And there is always loss in translation issues associated with that.

19:10
PJ: In our case, we support all 13, Sparkplug B is an associate. We support all 13 of it, and this is the lowest possible cost integration with high performance, near real-time analytics, we can perform as well. That's what we built and launched as part of manufacturing cloud between Inductive Automation, Cirrus Link, Opto 22 as a joint solution offering. Okay. We have made that much better now with Snowflake, with Ignition Cloud Edition as a connected applications available in Snowflake, and along with that, in addition to OT data, you got IT data, you got third party data like weather, traffic information, supply chain information already being managed in Snowflake, you have an opportunity to build applications on top of Cloud Edition and take it to your customers. And every applications you have built and launched at Edge seamlessly will work in cloud, with this edition. I think again, this is a cloud vendor perspective. With that, I'm going to give it to Travis to talk about from Ignition point of view.

20:11
TC: Alright. Thank you.

20:19
TC: Alright. So everything that we are showing on this slide here is something that's available today. And we're gonna show a full example of how, with a demo with Arlen and myself, how we go from Edge to Cloud going into Snowflake, back into Ignition Cloud Edition so we can show some dashboards, get information out there. And what we're talking about is what Snowflake's calling Connected Apps, right? We're simply gonna be deploying Ignition Cloud Edition to our Azure AWS account, and we're gonna connect to Snowflake through JDBC, and be able to be able to get that data from there and put it onto dashboards. So we're gonna show you what that looks like. However, we're thinking future and how this can even grow and get even bigger as we go forward.

21:01
TC: And there is a potential future landscape where... Whoops. All of that can be simply running all within Snowflake's cloud environment, so that you could spin it up really, really fast and get these solutions going quickly. So, but the idea is really simple, right? The focus of this is being able to get data that is modeled, customers need to... Basically it's a culture shift, right? Where they have to think about how they're gonna standardize on data and their data models across their entire organization, and the idea of this is to get it into a storage where that data is stored with its context, so we can go a lot further. So, what's really funny about this whole thing, when we got introduced to Snowflake is, at the end of the day, it's a database and we can connect to it just like we connect to every other database within Ignition through JDBC. And you can install that JDBC driver really easily in Ignition and you can issue queries just like we do with any other database.

21:54
TC: And so, we're gonna show that here today. It's very, very easy to get connected, very easy to issue those queries. We can issue anywhere within Ignition and they also do provide REST API so you can actually go a little bit further as well with that. There was nothing we had to do in day one. We just had to install the JDBC driver and get started. And from the very beginning of our company, we've been centered around SQL databases. This is just now a database that's highly scalable, it's in the cloud that allows for a lot more opportunity that we can... Where we can... For what we can do with that data. And a lot of that is around AI and ML, as Pugal was saying, there's anomaly detection and forecasting services that are built into Snowflake, and you basically train models and you can can do the detection on those just by running simple SQL queries against Snowflake.

22:45
TC: So it's very easy to work with this. However, it doesn't have to be within that. Any other service or tool that's out there that wants to be able to do that same thing, you can connect to the database the same way and you have all that data, you have all the context, you can go and learn everything that's there and go a lot further, right? And with this, what we're talking about too is not only you get the storage, you get these kind of services, but you get those results back into Ignition so that we can provide that information back to our operators, can provide alarms, whatever it might be. So it's kinda that full circle kind of integrated solution. So that's all I wanted to say really, in terms of Ignition and Snowflake. We're gonna get into the demo a lot more, but I did wanna bring up the Community-Powered Sparkplug Data Dash, because we thought for the conference here, we wanted to show this whole thing in action.

23:31
TC: And well, we got all the community to participate, where they're basically leveraging Ignition or Ignition Edge or potentially have a smart device that speaks MQTT Sparkplug and they're gonna build a data model, publish that up to a Chariot broker that's in the cloud. Real simple. Then we can use the IoT bridge for Snowflake by Cirrus Link and all that data from Sparkplug goes directly into the Snowflake database. We're showing it on a dashboard within Ignition, but it's going to Snowflake database as well. And we can easily go and query that data. And we went one step further and we're actually showing the anomaly detection within the Data Dash. So we'll do a demonstration of this in just a moment, but wanna show you just how easy it is for this solution. And it's all something we could do right now. It's very, very simple to get started with this whole thing. So with that, Arlen, I'll bring it over to you for the demo... Start at the demo here.

24:23
AN: Alright. Cool. Thank you. All right. Real quick, the topology is, I've got some simulated devices. Some of the devices are in Stillwater, Oklahoma that I'm actually talking to publishing those up to distributor running on Ignition on an EC2 instance in the Cloud. And so what we're gonna do is we're gonna go into Ignition, we're gonna build our "digital twins," but they're much more than digital twins. We're gonna show all that context and then we're gonna say, "Okay. Well now we've got this single source of truth. How much code are we gonna have to write to get it into a highly scalable Ignition or into a highly scalable cloud database?" And then from there, Travis is gonna go, "Oh. Well I've got that data in there. Let's see what I can do with Ignition Cloud Edition."

25:13
AN: So we're going to do the live demo, which we always love doing. All right. So, I know it's a bit of an eye chart, but it's hard to zoom in on the Tag provider. But I've got a Tag provider, Smart Factory and Smart Factory, underneath that I've kind of got the whole unified namespace of, I've got Smart Factory one and under Smart Factory one, I might have some building management systems because we've got BACnet/IP with Ignition now, I might have some Opto 22 KYZ meters and I've got my equipment in the factory, right? I've got CNC, a lathe, haul-off machine. And then down here you can see I've got the notion of an extruder. And this extruder has some process variables, some temperatures and some pressures and things like that. And had we... The way that we've been doing this going forward is that executives came to operations, they go, "Hey guys, we heard there's digital transformation. We gotta get all of our data in the cloud."

26:15
AN: "Okay. Well let's put all of our data in the cloud." So they go out and they write a bunch of code and they go in here and they go, "Okay. Let's do this and then let's pretend this is the cloud over here. And boom. Okay. We're done." We've got all of our data going into the cloud. It's all going into a data lake. But wait a minute, without some context, how can I use this? So I come into my data lake and I wanna look at something, and I've got 148 degrees, 148.85 degrees, where'd that come from? What machine was it attached to? What plant did it come from? I don't know. Oh. That's over another database. So I need to write some code. And then maybe there was some other asset information, now I've gotta get some code. And what happens is we've got terabytes of data hitting data lakes in the cloud and nobody's doing anything with it because it's too hard and you can't get any context from the data. So, let's drain the swamp. And before we do that, let's go into that extruder and actually give it some context.

27:34
AN: So I wanna build a UDT of an extruder model. And every time that extruder shows up, the first thing that I want to do is I probably want to give it some asset information. Asset ID, asset serial number, location, anything else that you want to be available to you on each instance of that extruder in Snowflake that you want to be up there, you can define in your UDT and it'll be automatically published up there. And now that I've got my asset information, I can go back to that melt temperature and say, "Look, for that machine when melt temperature shows up, I don't care if it came from Allen-Bradley PLC or a Modbus or Rockwell, I want to know that it represents melt temperature, it's 0 to 225 somethings. Those are in degrees C, it's using absolute deadband.

28:22
AN: There's my deadband percentage and my scale mode and anything else again that I want available to me in Snowflake when I'm done with this demo, I can define in this UDT. So now that I've defined my machine, very, very simply using tools on platforms and I can go in and define a dryer and a bunker, and now I can come back and take those nebulous tags and look at the fact that this extruder actually was, extruder seven, was a model of an extruder. And you can see here I've got my asset ID Wile E. Coyote, asset serial number B549 courtesy of Hee Haw, location in Oklahoma and all my process variables. And since it is a UDT, I can use the Power Perspective or Vision to be able to start taking that and maybe when the extruder feeds into a bunker, and the bunker feeds parts when it comes out into a CO2 dryer, and maybe I've got an Opto 22 EMU and it's measuring the three-phase power on that extruder. But my point is, is that at 3:14 on September 27th, this is the single source of truth of my factory.

29:48
AN: This is the single source of truth. I didn't define it in the cloud and then try to bring it back down and iterate back and forth, I know this is my factory. So I just came off of a really cool demo from Snowflake and I go, "Wow. What if I could get that single source of truth into Snowflake? How hard would that be?" So what I'm gonna do is I'm gonna go to the Azure or AWS marketplace and I'm gonna download the IoT Bridge for Snowflake. I'm gonna install it. And when I install it, it's going to go in to my Snowflake console here and it's gonna create two very simple databases, a node database and a staging database. And in here, I have a very simple Sparkplug device message table that you can see right now is empty. And when we installed it, we also added some convenience and I could get a view, and since it's all going up from UDTs, I've got a view that says, "Hey, tell me about all the UDTs that are in that factory or all the factories." Oh, well, I don't have any factories yet. So I need to fix that. Let's go back into our Ignition configuration. And you can see here that I demo a lot. I've got a lot of tag providers and if you look at Smart Factory, it's pointing to the Snowflake MQTT server. So that's great. I'm gonna come over here and I'm gonna enable my MQTT transmission. Okay? And when I did that, what happened? 

31:36
AN: When I did that, MQTT transmission looked into the Smart Factory Tag provider and it says, "Hey Arlie. You've got all these models, you got dryers and extruders and conveyors." And so we're gonna publish those using Sparkplug. And the Snowflake Bridge was sitting there listening to an MQTT server. It was a very... It wasn't doing anything. All of a sudden, messages started showing up. Remember that advantage, auto discovery. "Oh. We got an extruder." Now I'm gonna put that into Snowflake using Snowpipe Streaming. So 15 seconds ago, I didn't know anything. Let's go back to our Snowflake console and let's hit Refresh. And lo and behold, we now have a Smart Factory 1 with views of every machine that we've got in that factory.

32:32
AN: Before I go look at one of those, let's ask the SQL database, what models do I have? Let's ask it again. "Oh. Arlen, you've got an extruder, a chiller, a dryer." So now I literally know everything that was in that UDT on Ignition. Now that I know all of the models, I can go back over here and say, "Well, now that I know that, let's go to that extruder and let's do an SQL query, which everybody knows SQL and single, this unified namespace, Smart Factory, Smart Factory 1, line seven, extruder seven, when did the message arrive? What was its sequence number, and all of my process variables in real-time, all hydrated, no holes in the database. I literally could start using this today. So if I know SQL, it took me five minutes to get all my machines defined, get everything up there in real-time. And now for every machine I had in that Smart Factory, I now have a single source of truth of all the real-time data is showing up in Snowflake. Pretty cool. Now, once it's in Snowflake, what can we do with it from there? And with that, I'll turn it back over to Travis.

33:55
TC: Sweet. Alright. So, again, once it's in the Snowflake database, it's just a matter of going and doing, issuing queries against that. So, I'm going to switch over and show you the Sparkplug Data Dash here. And so this is our server that we have that's running in the cloud. And you can see that we've got a Snowflake database connection here that is connected and valid. So what we did first though is we went to the driver's part here in Ignition and then JDBC drivers, we had a bunch of pre-built ones that come with it. Now we're working on getting the Snowflake one built into Ignition, in a new build. But for now, you can go download the JDBC driver and simply just go ahead and install it.

34:37
TC: And we have some instructions on that, a little Read Me on how to do that. Real simple. Get that installed. Once we have that installed, we can go and make a connection like we have here. And so just like any other databases, of course, once I have that valid connection, I can go anywhere in Ignition, and I can use it. So I'm gonna open up the designer here and what we've done for the Data Dash, and I'll go and show you the application in a minute. But we just basically, if I go to the Snowflake, we have a bunch of predefined name queries that basically go and query certain tables. So, he was showing that, that Sparkplug device messages table, and so if I go and look at this, you can see that we're just doing a standard select query against that Sparkplug device messages table.

35:21
TC: And we're looking for... And this one I'm filtering for specific group ID, Edge node ID, and a specific data model that I wanna look for, that we're using for the actual dashboard itself. So it's incredibly easy for me to go into Ignition. In fact, we can go into the database query browser against the Snowflake database and we can easily start saying, "Select star from stage DB, sparkplug device messages." And so we can just bring that data back and anywhere in Ignition within that. And in those queries, we can have... There could be millions of rows. In fact, with the Data Dash, we've got over 120 million rows at this point that we've been logging with that and it's very, very high performance to get that information back.

36:12
TC: So as you can see, that's how we have developed it with the Data Dash. Let's actually go and show the outcome of what we built. So we're gonna go to tryignitioniot.com. So if you haven't checked out Data Dash, simply go to tryignitioniot.com on your phone. You can go... There's the... On the tech lounge, there's a TV up there that has this application open. So here's what we did. We asked participants to go and do exactly what Arlen just showed. He built an extruder machine, a data model. Build any kind of data model that you want, right? Provide that context, provide those parameters that you wanna associate, provide the engineering units and the engineering ranges of the values. Basically create a UDT within Ignition or any other device that speaks Sparkplug, and have that published up to a cloud MQTT broker. With IoT Bridge, everything he showed, that all came into Snowflake and it's all ready to be discovered. So, this dashboard, you can go and you can actually go and see these data models. So if I go look at, for example, I'll use Opto 22's EPIC c-store. We're just showing a visualization of this. Let's go to a different c-store.

37:20
TC: So, we're just showing a visualization of that data model. So you can see the information up here. So there's a perspective template that corresponds to that data model, so that we can easily look at that live data. But again, that history is all going into Snowflake and it's accessible so that we can query that. So let's go over here to the Snowflake tab. And the first overview of this is basically just a discovery of all the data models that happen to exist within Snowflake. So much like he just showed how all those views got created, well now we can actually go and query those, and we can discover information about this. So for example, let's go in. Since I was using the Opto 22 c-store, I'll go into the Stillwater and look at that particular data model. So there, on the right-hand side, we can see all of the parameters that are gonna be... That are part of this is like the UDT definition. All the parameters that are there, what the data model is, here are all of the process variables that are in there.

38:17
TC: For the process variables, like, for example, if I look at this freezer compressor, I'm gonna get, of course, that it's KW and I get the range, 0 to 1500. So this is all... I can have Ignition completely independent from all of the... Not even connected to the MQTT broker, and I can see all the data models that happen to exist within Snowflake, because again, using Sparkplug, those templates were sent to a broker and into Snowflake, again, it's that same exact context. So very, very easy to see that. So this overview is kinda just showing all the data models that are in there, and we've got a whole slew of them with this, so let's see if I can clear this out or there's no exit on that, but we have a whole slew of different data models that are there. At the end of the day, then we can go and query the history very, very easily, and build dashboards and we can go a lot further.

39:06
TC: So I'm gonna show you two kind of demos, one is we're just gonna go and query the history, bring it back into trends, so we're gonna go and select... I'll need to go down to one of those instances, those data models that we have, I don't wanna look at that data, so we'll go... Again, we'll look at the Opto 22, since we're on there, we'll go to Stillwater, look at the EPIC c-store, and because we have the data model stored, you can see here's all the tags, all the process variables associated with it. We already know what those are, and I'll go and select a particular instance. So here's our c-store 405, here's my date range that I'd wanna query the history on, and we'll just select some process variables. I'm not gonna select all of them, we'll just do, let's say, the compressor, all the freezer system, we'll bring those back. I'll apply. And basically, at this point, we're gonna go and issue the... For that time period that we have up here, we're gonna issue a query to get back that history. The idea is that we can simply just go and query all that data. We can bring it back on trends... Hey, there we go, just took a few for that information to come back.

40:03
TC: So, not only is all that data stored there, we can discover that, we can understand what it is, we can query it, put it back onto a dashboard very, very easily. So that's kind of one demonstration of what we're using with Snowflake. The other, of course, is going to the ML/AI side. We're talking about anomaly detection. And so if I go back over here to the map and we look at a particular location, let me go back to that, that Stillwater one, on that freezer, where we have that Compressor KW, we do have the Anomaly Detection turned on in Snowflake. We trained the model based on good data already and just basically ran a SQL query to train the model. And once it's trained, then we continuously, since that data is piping through the bridge into Snowflake all the time, on the Snowflake side of the task that's running, very, very quickly, that is basically looking at the last bit of data we brought in and we're gonna run it through that model to see if it detects any anomalies. Now we're kind of manufacturing this by clicking a button that says Trigger Anomaly, but it is going through that whole system, kinda coming back, where we're getting that feedback back in Ignition. So if I go ahead and do that, what we're doing is gonna...

41:08
TC: We're gonna spike that Compressor KW, which of course, is gonna cause that anomaly to happen, but as you can see, that came back extremely fast, running that model very, very quickly on the Snowflake side. We got the anomaly that's an alarm within Ignition, we could do something about that, but those can be running all the time. And because we trained the model off of that UDT, any new site that has that same data model can take advantage of that same... The same thing that we've built, so we can easily do anomaly detection across the entire enterprise on those data models.

41:41
TC: So it's very, very easy to get these things going, to go further with all of this, not only are we showing how we can get the data into... Get it into Snowflake and how we can leverage those UDT models, we can easily bring it back into dashboards and show that data very effectively. So with that, I think we'll just be opening up to questions.

42:11
TC: So anybody have questions out there? Yes? We have one down here...

42:14
Speaker 4: I know it's hard to say, but what's the rough startup cost of getting the MQTT,

42:22
And then the Snowflake? 

42:26
AN: Free. It's one of the rough startup costs... Everything that you're seeing there, you can run in trial mode, right? So you'd probably have to get a test account, and you can get a test account from Snowflake. For the IoT Bridge, that's 30 days free. So you can do it for 30 days, basically for free.

42:47
TC: The whole thing would be, so you got... You've got Ignition you could do in trial period, no problem, in trial period, we can also provide longer trial licenses if required. The IoT Bridge is 30 days free, easy to work with, and with Ignition Cloud Edition, that would be the broker, that would be in the cloud, you'd wanna have some broker up there, it could be that, it could be something else, so you can run that for a couple of hours or a few hours. It's pretty low cost, maybe a dollar per hour. And then with Snowflake, I believe, when you create the account, there's a... I think credits you already get.

43:17
PJ: Yeah, they are some credit options, we can work with you on that. I would say it's pretty much everything is... When you do the compute, you do the reporting, it's pay-as-you-go... It's like electricity bill. When you use it, you get the bill; otherwise, we're not going to charge you. So, pay-as-you-go model. That's what it does. And again, I think having done those kind of Industry 4.0 initiatives,

43:38
AN: Multiple effort, I would say this is the lowest cost possible startup cost around Industry 4.0 because even four years back around what the initiatives which used to happen, a few hundred thousand dollars, we can connect three machines and we can do a business outcome. That was the pitch. It's no longer there. It'll be hardly a few thousand dollars to get it started. At pilot level, I don't see that as a challenge.

44:06
TC: And yeah, and one thing to mention is that... Oh, I lost my train of thought... Oh, well, we'll come back to that.

44:13
AN: Well, no, I think... What I was gonna mention is that, the other thing that's really different here, it was an advantage, Snowflake didn't have an IoT service when we started this project, so they had no notion of charging by the measurement. So it doesn't matter if you're publishing a 1000 tags or 50,000 tags, you're running in a compute warehouse, so you're not charged by the measurement like you are on all the other data services, you're just running in a compute warehouse; as long as you stay within that warehouse, you know your cost.

44:47
PJ: In fact, there are two advantages which came with that. When Arlen mentioned there is no IoT service, [0:44:53.8] ____ but last year when I took this role, I told Arlen that this time, when we do the integration between Snowflake and at the edge, for edge-to-cloud business outcome through Inductive Automation, they should be the best-in-class integration ever built on this planet, so far. Again, I think there, we had an advantage because we didn't have an IoT service. There are two major advantages which came with it; one, there is no additional cost factor. We are not gonna charge you for an IoT service which other cloud vendors are going to do.

45:26
PJ: The other one, pretty much every IoT service as a sub-optimal view of the manufacturing asset world, and they have done the modeling, that always comes to the challenge when you try to move that edge data to the cloud, there is always a compromise made on the data model. When you try to change the data model, you've got a bigger problem associated with it. So these are all the challenges we never had, so we made sure that we can handle every possible data types. And data ingestion, in our viewpoint, should be a commodity, because either way, we don't make a lot of money in data ingestions, it's pretty much nickel and dime to move the data from edge to the cloud, it's really around compute, that's how we charge you. So we are trying to keep it as easy as possible to move the data into the cloud.

46:09
TC: I remembered my train of thought real quick, which is for existing customers who already have Ignition, it's incredibly easy to take advantage of this. We're talking about simply just getting MQTT transmission, just plopping it in, if you have models already built, it'll be that quick to get integrated again.

46:24
AN: Exactly. If you already have Ignition, we're probably talking less than a day.

46:27
TC: We're talking, for new customers though, for people that maybe have a new site or a new facility or something, or they haven't had Ignition at all, it's going with Ignition Edge or your full Ignition, putting it in to connect to PLCs, bringing those... Building the models is super easy. In fact, we've also built a kit with Opto 22, where they have their EPIC controller with Ignition Edge on it already ready to go; especially for energy, with the energy monitoring units to basically pump those energy UDTs in the cloud, so there's a lot of easy ways to get started. Other questions? There's one in the back up there.

47:07
Speaker 5: So, for the piece that you were speaking about, in terms of ML or the pre-trained models, can you go into a little more detail about A, the training that goes into those pre-built models and B, the explainability behind those models? 

47:21
TC: Yeah, so for the Anomaly Detection Service, the way that that works is, you're basically kinda like calling a stored procedure almost. You're specifying, you're doing a train model call and you're specifying the data set that you'd wanna train it on. And so in our particular case, we're doing one of those [0:47:37.1] ____ as of use that Arlen showed, for a particular...

47:39
TC: So we did it for this, the c-store, we did it on that, on that freezer compressor, we basically brought back the data from the time period that we'd wanna train in... We trained it on, I think, a few thousand rows of data that was good. So we call that function once and it creates an object in Snowflake, that is the anomaly detection object. And much like you're creating a table or a view or a task screen like that, you're creating one that you can then run again later. So then next time, when you want to do a detect anomaly, you just run another SQL query that is saying... Basically, call this anomaly detection name, you say detect anomaly, so you give it a new query or a new set of data you'd wanna run through, and it will give you back a result, a table that's gonna show you, if all the data, if there's anomalies or not, what the variation is, all of that. And so we just basically take that, that result and if we see anomalies, we then trigger that alarm to come back to Ignition. So as simple as that, two queries: One to train and one to detect. It's as simple as that.

48:40
Speaker 6: Okay. Is there any plans to add discovery tools for engineers who like to look at trends initially to build out some ideas before they run it through the model? 

48:54
PJ: If you can swing by the Snowflake booth, we can go deeper into that. That's a longer conversation, if you don't mind.

49:02
AN: Alright.

49:02
TC: Alright. Thanks, everybody. Awesome.

49:03
AN: Thanks, everybody, appreciate it.

Project Summary:

Design and develop a new treatment plant HMI to replace WinCC and condense third-party applications into one platform.

Problem:

The City of Orlando used Siemens WinCC for many years, but had several problems with it. The City had to wait until the development team in Germany could find a solution to its issues. After many days of trial and error, the City of Orlando finally got a solution. Updating WinCC was a very daunting task. It usually had to completely rebuild its servers, from installing the operating system to upgrading each client out in the field, and it took about two weeks to complete a system upgrade.

Solution:

When the City of Orlando has a problem with Ignition, it can easily contact one of the developers or a very knowledgeable technician who will help it as best they can to find a solution to the problem or find a path for its own solution. Myron, The City of Orlando’s Inductive Automation account representative, is also very quick to help set up meetings with the developers and find a solution to specific issues. The City of Orlando can contact Ignition support in a matter of minutes and resolve an issue in a matter of a day or two. Upgrading the same version of Ignition takes minutes and is fairly easy to do. The same is true for installing Ignition and restoring a project.

Results: 

One of Ignition's main benefits is it saves development time. Ignition takes less time to maintain than the previous platform. There are some built-in modules in Ignition that eliminate the need for third-party software. Consequently, the City of Orlando no longer needed the paging software Win911, and Kepserver for some of its communications as Ignition has a built-in paging system.

Ignition also has a built-in auditing feature, and there was no need for auditing in the previous platform unless it was scripted or third-party software.

The system can also bring information from other applications into Ignition via SQL communications, scripting, and querying. There is an interface to CMMS asset management software, and its end users find that very helpful. It can feed more information into Ignition than what it could before.

Deploy Date: September 2021

Project Scope:

Tags: approximately 49,000

Screens: 289

Clients: 42

Alarms: 200 plus

Devices used: 55 PLCs

Architectures used: Standard

Databases used: MySQL

Historical data logged: 140GB

Learn more about how Ignition helps to enable Digital Transformation for the Water & Wastewater Industry

Project Scope:

• Tags: 43,019 PLC Tags (>170k tags total)
• Screens: 127
• Clients: 5 (this number is expected to grow as more devices start coming in and used by field operators)
• Alarms: 24,641
• Devices used: 22 ControlLogix PLCs
• Architectures used: Standard
• Databases used: 1 (SQL Server)
• Historical data logged: N/A

Project Summary:

In addition to the HMI baggage handling system Vision application running on the workstations for Houston Terminal C/E (and now B), the intent was to offer the same functionality on a mobile device, such as a tablet. While incorporating the same security roles as the Vision application, the operator on the tablet can view/acknowledge/shelve alarms, view graphics, view and interact with device statuses and controls, view statistics and view connection status details from the new Perspective application.

Problem:

One of the problems Brock Solutions was trying to solve by introducing a Perspective mobile application is offering field operators greater visibility and awareness of what is happening in the system. The workstations in the control room provide valuable information to those operators, where they can relay information (such as alarms) to field operators who can investigate but having the physical representation would ease the maintenance work.

Solution:

Perspective was used to solve this problem by having devices (tablets) used by field operators. Rather than having control room operators call out alarms to the field operators, the mobile application allows the field operators to view and interact with alarms and devices straight from their tablet. This eliminates the need for a control room operator calling out alarms. Due to the size of the system, it is broken up into configurable “areas,” such that the application could be filtered out to show only relevant information (devices and alarms), which allows the field operators to focus on their configured areas.

Having the physical representation of the system in the field is very important in how operators/maintenance crew interact with it and improves the efficiency of resolving alarms on site.

Project Scope:

• Tags: 70,000
• Screens: 880 screens and 450 popups
• Clients: 1 fixed dedicated client (workstation), 5 web clients, with 20-25 mobile/tablet clients
• Alarms: 4,500
• Devices used: 80+ Red Lion Protocol Converters (DA30D); 75+ Teltonika RUTX09 4G Modems; PLCs - 80+ Koyo Click Plus, 60+ MELSEC across several varieties: MELSEC FX1N/60MRES, MELSEC FX1S/30MRES, MELSEC FX3G/40MRES, MELSEC FX3G/40MRES; 10 Modicon PC-E984-285
• Architectures used: Ignition Standard architecture with redundancy
• Databases used: 2 SQL Databases (System Data and History)
• Historical data logged: 65,000 historized tags

Project Summary:

A regional municipal council has implemented the next generation of remote telemetry monitoring and data-driven decision-making. This represents a significant step for the water industry in Australia and provides access to the same data-driven decision-making process used by large water authorities for a fraction of the cost. Since implementing the new system, the council has seen the commencement of significant cost reductions, improved planning, and data-driven decision-making.

Problem:

Australia has a long history of remote telemetry operations with many water authorities covering huge geographical regions. Often these systems are based on old poorly secured technology (by current standards). This project is a great example of a small council in a growing region using a forward-thinking approach during their control system upgrade. 

Alexandrina Council is one of the fastest-growing regions of South Australia, with a population greater than 27,800. During summer, the population swells with visitors, requiring the council to account for this additional peak demand. The region is home to the Murray Mouth, Coorong, and significant environmental sites including Ramsar wetlands. 

The council had more than 300 remote sites across at least six independent SCADA technologies with very limited to no remote accessibility. This created a difficult asset environment to manage and meant maintenance teams were constantly traveling to collect data and spot-check the status of the different systems. 

The council’s wastewater team had a future vision to leverage the rich data capture and drive analytical tools to enable predictive maintenance for their sites. 

SAGE implemented a superior solution using Ignition Perspective, MQTT Sparkplug B, and LTE, that enables the council to:

• Implement a large wide-area remote telemetry system with data buffering for a fraction of the price of other comparative solutions on the market.
• Combine multiple SCADA and HMI technologies into a unified Ignition platform.
• Use a mobile-first design approach that allows data to be accessed anywhere on any device, all developed/tested and commissioned once.
• Store data from more than 300 sites and provide access to decision-making support tools.
• Reduce maintenance costs via site visibility, reducing the amount of travel needed.

Solution:

The latest features of Ignition Perspective’s visualization platform were used to provide a flexible project. Taking a mobile-first approach allowed templates to be used across different devices (mobile, tablet, and desktop) without duplicating development effort. This was completed without negatively impacting the desktop environment, which includes full P&ID views using the latest Ignition piping tools.

The project is built around Ignition’s tight integration with MQTT Sparkplug B. It uses Red Lion DA30D units at each site as a common edge device which can communicate to the wide range of PLCs that the council has installed over 15 years. The ease of integration and data backfilling combine for a powerful solution at a fraction of the price of a traditional RTU architecture.

SAGE leveraged the web service connectivity, powerful scripting, and templates within Ignition to replicate an entire IoT system quickly. The Flovac IoT system is used as a data source, and Ignition’s graphics and data are all generated dynamically. This allows Ignition to be a single source of truth from an operator’s perspective and removes the need to manually update Ignition as new sites are added or removed in the IoT system. This significantly reduces the level of system maintenance required in the future.

Results:

The council gained full remote visibility of sites, with multiple external systems integrated into a single centralized SCADA. As a result, operators can access historical data, as well as intelligence (such as event markers) to improve troubleshooting and response times, from whatever location they need. 

SAGE takes a highly collaborative approach when working with software and hardware vendors. The requested features and improvements developed in this process change the industry for the better. Specifically, SAGE worked with the Red Lion team to improve how the MQTT backfilling process works and increase stability. Within Ignition, they were one of the first teams to implement the piping tool in a live system and provided valuable feedback on it and other critical features of Perspective like trending, alarm display, and shelving. 

Introducing new operations personnel to a SCADA system is time-intensive, so 3-5-minute training videos are embedded into the system. These recordings step users through common scenarios typically covered by in-person training sessions, such as simple navigation and color standards, through to complex features like trending. This also allows experienced users to re-familiarize themselves with infrequently used features. Fundamentally, this system supports and provides critical user tools for the operators, ensuring they remain at the center of application development.

The council’s on-call support has vastly improved - previously, any alarm would require travel to the site. Using Ignition’s alarm notification system, alarms are categorized and directed to the appropriate operations group, who can log in through their mobile device or tablet, and address the alarm with the operational intelligence they need. 

Operations now more effectively plan and schedule multi-site works by remotely monitoring site status to ensure a suitable operational state when they arrive at the next site to take samples and measurements.

Prioritizing alarms, reducing travel time, and performance-based maintenance create direct cost savings for the council, allowing funds to be redirected towards expansion plans. It also provides the council with the core infrastructure for analytics and machine learning tools to increase those savings even further.

Transcription:

00:18
Scott: I'm Scott Avis, senior systems engineer, and have been with SAGE Group for 12 years, delivering SCADA and telemetry solutions across a number of industries. SAGE Group is an Australian-based company with more than 600 people across two continents. We are a Premier-Level Integrator with Ignition. We have a presence in every state and territory in Australia and are focused on delivering a smarter future, better world. Alexandrina Council has a population of more than 27,800 residents across more than 1,800 square kilometers and is one of the fastest growing regions of South Australia. The region is a popular tourist destination with more than 800,000 overnight visitors each year. The Council originally had more than 300 remote sites across at least six independent SCADA technologies, with very limited to no remote accessibility. This created an asset environment that was difficult to manage and meant that maintenance teams were constantly traveling in order to collect data and spot-check the status of the district systems.

01:20
Scott: In 2021, SAGE Group began working with the Council to introduce an overarching control system across all their wastewater assets. This project involved Alexandrina Council's implementation of the next generation of remote telemetry monitoring and decision-making in wastewater. This represents a significant step change for the water industry in Australia and provides access to the same data driven decision making processes used by large water authorities for a fraction of the cost. Since implementing the new system, the Council has seen significant cost reductions, improved planning, and better decision-making. So before we take a look at some actual graphics, I'd like to discuss the design philosophy of this project. Initial discussions with the Council revealed their preferences for a highly mobile workforce. With this in mind, SAGE designed faceplates for mobile resolution first. These face plates are common between both the mobile and desktop environments. Everywhere possible, we focus development on faceplate templates, which are dynamically placed on the view interface, regardless of resolution.

02:24
Scott: So we'll start here with the map overview page. This page shows all the sites in the Council district. The pump station overview page provides a high-level status of all pump stations in a township, including pump status and sublevel. From the individual pump station page, Operations receive a more detailed view of site status, including pump operation, sump levels, pump statistics, site control. Both the pump station overview in this detail page are created dynamically based on site information in the system tag database and SQL tables. This is allowed for quick and simple site instancing. SAGE have utilized the new Perspective piping tool to create the P&ID pages operators are familiar with. One of the Council's existing more featureful SCADA installations was deployed across a vacuum pumping system. SAGE system engineers worked with the FLOW-VAC developers to utilize a new rest API service, which enabled replication of the FLOW-VAC SCADA system within the Perspective environment. This has enabled Ignition to fulfill the Council's desire for a single source of monitoring.

03:40
Scott: This implementation will even recognize when a new device is added on the FLOW-VAC side and automatically added to Perspective without any user interaction. In terms of actual graphics, you'll see, we have a graphical map showing asset locations, which can be filtered based on which pump station the vacuum site feeds, which gateway they communicate through. We have also developed a table view showing all sites. This table can be filtered based on any column value. Table rows can be selected to display additional site information, including a trend and statistics, which automatically update based on the trend time period. SAGE has developed a trend saving feature which allows operators to build their own specific trending. These trends can be saved and retrieved at a later date by themselves or another operator based on user credentials and page settings. Operator training is a small part of a project handover, but for new operators and those unable to attend training sessions can often result in a "here's the manual, have a read" approach. To mitigate this issue, we've embedded training videos directly into the SCADA application.

04:50
Scott: This allows any operator to access short and specific training videos on demand. In addition to the new operator training, we also foresee an experienced operator accessing specific videos for SCADA elements they don't often use, such as advanced trending features like multi-plot trends. One of our team members had a stroke of inspiration and developed a dark mode feature. Now every graphic in the system functions in both a light and dark mode. You can see this as I cycle through the graphics. Everything I've mentioned previously works on mobile and tablet environments. Displays automatically scale up and down based on device resolution. This results in a SCADA system which works as well on a mobile device as it does in a multi-monitor operator control room. At its core, Council operations has been significantly improved. They have the data to drive informed decision-making and the ability to push that data into other analytical platforms. They have SCADA access from any location on any device and minimized incident response time through prioritizing of alarm events.

06:03
Scott: This has resulted in a significant reduction in transport costs and operator driving time. SAGE has delivered all this at a fraction of the cost of a traditional RTU wide area communication network, saving the Council money, allowing prioritized spending and benefiting Council residents as their funds can be redirected. Looking forward, the Alexandrina Council is discussing growing the SCADA system by incorporating additional storm water and irrigation sites.

Learn more about how Ignition helps to enable Digital Transformation for the Water & Wastewater Industry

When Castle & Key took ownership of the long-idled Old Taylor Distillery in Frankfort, Kentucky, and revitalized it as a modern facility, they opted to leave some of the 140-year-old buildings’ wear as is. The property, which features an honest-to-goodness castle, a sunken garden, and the world’s longest rickhouse, had languished in disrepair. Prior to the sale in 2014, there was even talk of deconstructing the castle itself and selling the limestone bricks. Leaving the patinaed brass and occasional cracked tile is an aesthetic choice, one that nods to the site’s history as the birthplace of bourbon hospitality in the 1890s. But step inside, under the original Old Taylor sign, and it’s clear that Castle & Key is equal parts tradition and innovation.

Castle & Key implemented Ignition — an industrial automation platform for SCADA, HMI, IIoT, and more — with the help of Gray AES to replace an outdated FactoryTalk system. Headquartered in nearby Lexington, Gray AES is a professional services company offering architecture, engineering, and automation solutions across a wide range of industries, including major greenfield or brownfield expansions. “Supporting distilled spirits producers and bourbon distillers, being headquartered in Lexington, Kentucky, is very important for us, not just as a systems integrator, but as a corporate citizen of our home state,” said Taylor Sawyer, Director of Business Development at Gray AES.

The two companies have a long history together; before the Ignition implementation, Gray AES had redone Castle & Key’s control cabinet, running new terminals and updating the PLC programming. After that success, Gray AES was the clear choice to upgrade Castle & Key’s SCADA system. As Elliott Schmitz, Distillery Manager at Castle & Key, put it, “Our goals were aligned from the get-go.”

Improving Operational Efficiency

The biggest issue with the old system was the lack of historical data. While Castle & Key could see current production numbers, there was little context. For a company with multiple products that require years to properly mature, this inability to look back made looking forward increasingly difficult. “Distilleries are in a unique position. They have to make decisions on a five-to-ten-year spectrum. They can't make a product today and sell it tomorrow,” said Sawyer.

There is a limit to throughput as well; spirits like bourbon require physical space to age. To remain competitive in the market, Castle & Key needed to use the space they already had to its full potential.

Speaking about operational efficiency, Sawyer said, “It's not so much a buzzword or a euphemism within the industry. It's just the nature of where the industry is heading. How do you do what you're doing today, albeit more efficiently?” This is especially true for a registered historic site that doubles as a production floor.

“We are a historic distillery, but the things we like to modernize aren't necessarily traditional whiskey practices. It’s more [about] improved automation techniques, better data and analytics, correlation and connectivity, and then just constantly being neurotic about scientific advancement of our craft,” said Castle and Key’s Brett Connors, whose formal job title is Whiskey Wizard, a position that encompasses the duties of head blender, product strategy, hospitality, and sales support.

High-Performance HMI

This implementation was Gray AES’ first large-scale project using Ignition’s mobile-responsive Perspective Module. “The main request was to make it a more modern look and feel. Perspective was a natural fit, taking advantage of the CSS and the style sheets,” said Jeremy Plunkett, Digital Transformation Engineer at Gray AES.

Gray AES designed a new SCADA system featuring a high-performance HMI, leveraging modern frameworks closer to website design than traditional SCADA visualization. The goal was to modernize the system to run mostly on iPads while maintaining a close visual resemblance so that operators could easily transition to Ignition with minimal training.

When developing the system, Gray AES utilized DevOps principles. “We would pull down a stack into our local environment, spin it up with Docker, have code reviews using GitHub, and we'd create pull requests for any changes. Then we deploy it to our test server, test out changes before we'd actually deploy it to the production environment,” said Plunkett.

The design process was collaborative between both companies, not just between Gray AES and Castle & Key upper management, but with plant-floor staff as well. One request from operators was to keep the application’s primary color the same. While the new HMI still adheres to the fundamentals of high-performance screens — heavy use of gray, bright colors like red reserved for alarms, minimal clutter — the background is a bright, inviting teal. When activated, all valves, pumps, and motors turn white, in line with the high-performance standard. “It felt very unfamiliar until we had the teal background. And it makes the white stand out a little bit more too,” said Schmitz.

More than anything, this gave operators a sense of ownership of the Ignition system. “At the beginning, operators were a little resistant, just because change is difficult,” said Schmitz. “However, there have been some really good features in Ignition. It’s very easy to navigate and it's been well-received among the team.”

Being able to access the Ignition system through mobile devices has greatly improved operator workflows, and the application’s “crisp” response provides immediate feedback.

UI/UX

The Ignition system defaults to an overview of Castle & Key’s still, giving operators an immediate view of the high-priority functions. The system is logically connected for the process flow, allowing operators to navigate between screens without having to return to the main overview like they did in the previous system.

The side menu provides quick access to other screens within the application. The operator can select the screen, monitor key metrics like temperature, and control distillation to hit target proofs and ensure consistency. With so much information on the screens, operators can move pop-ups out of the way, monitoring flow rate while adjusting the aperture of a valve. Additionally, Gray AES designed a variety of standard faceplates so that anytime Castle & Key needs to add another pump, agitator, or valve, they can reuse assets.

For processes like grain intake, the application shows the operator the entire path flow, including all conveyors and valves, as well as any information required to bring the grain from the truck to one of the silos. In addition to individual mobility, the Ignition system saves time by giving operators access to every part of the facility at any time. For example, when one operator is getting ready to unload a grain truck and does not have an iPad, they can radio for assistance, and another operator can help remotely.

Historian

Beyond the visuals, the Ignition system includes the Tag Historian Module. This allows Castle & Key to easily view historical data, identify trends, and make projections. Perhaps most importantly, this access to historical data allows them to identify anomalies, which can have far-reaching consequences for a process that is still as much art as science.

“On the product strategy and research side, we love the historian functionality of [Ignition] because it allows us to really integrate our product quality to historical records and data to be able to improve our overall strategy and processes,” said Connors. “We're excited about the data being able to come from the historian and to correlate that into our production methodology.”

Alarming

The system also features Ignition’s Alarm Notification Module, which provides two locations where operators can access alarms: current overview and alarm history. The former allows operators to see any active alarms in the system, while the latter gives Castle & Key long-term data, similar to the historian, to make continual improvements and better dial in preventative maintenance.

Prior to Ignition, acknowledging alarms was a highly manual endeavor, requiring an operator to physically walk to a machine (sometimes on a separate level of the production floor) and press a button to stop the process. Now, with Perspective’s mobile-responsive capabilities, operators have a convenient, and immediate, method for responding to alarms.

Momentary Push Buttons

Distillation involves a great deal of sensory response during production; operators monitor the smell, taste, and visual clarity of product as it travels through the system. Fittingly, part of the process is dependent on another sense — touch — more specifically, the need to hold down buttons. “The FactoryTalk application had a lot of momentary push buttons, and that was a bit tricky with Perspective because there's not a one-to-one component that mimics a momentary push button,” said Plunkett. “We didn't want to have to rewrite all the logic in the PLC, so we pretty much created our own custom momentary push button.”

Gray AES’ solution was to let operators tap a button in the Ignition application to “bump” open a valve or open it completely instead of holding down and releasing. Accurate grain weight is a critical component of spirit production, so the ability to slightly open, throttle, and completely close a gate with a tap or two instead of continually holding the button down has been just as, if not more, effective.

Parallel Deployment

As with most manufacturers, Castle & Key could not afford to halt production while Gray AES installed the new system. “We took a gateway backup and dropped it into their Ignition gateway on site. We had a simulation PLC as well, so we had already had all the tags mapped,” said Plunkett.

That last point was originally considered an issue because all labels were stored in the FactoryTalk HMI and could not be directly collected from the PLC. While this task seemed daunting at first, Ignition’s scripting capability allowed Gray AES to write a script that parsed through all of the tags from the HMI, then populated them in Ignition, avoiding what would have been an arduous conversion process.

Deploying the Ignition system was fast (“It took five minutes to deploy,” said Plunkett) but to ensure there was absolutely no downtime, Castle & Key ran the old and new systems in parallel. That way, if there were any unexpected changes after the fact, the plant floor could continue moving, not to mention bubbling, agitating, and distilling. “You can connect either to the control panel on the iPad on the same internal network or be connected to the PLC and Ignition at the same time,” said Schmitz.

“The ability to continuously run on our daily basis as we're developing this new programming system was really paramount because it caused us to not have to lose any production time as we were planning and eventually now transferred onto the new system,” said Connors.

Process Refinement

Shift after shift, Castle & Key is collecting data to further refine their processes. They have found that the Ignition system opens up a whole new path forward. As Schmitz put it, Ignition allows them “to get that access to identify trends and make improvements either to our programming or to mechanical aspects in order to drive consistency.”

Even as Castle & Key plans to expand the system by incorporating more processes, they intend to retain the human element that makes their operation unique. “Our industry relies a lot on organoleptic and sensory data. How do you correlate a human experience to your automated experience?” asked Connors. “To be able to actually take that data and scientific overlay and then apply that to your organoleptic program is incredibly uncommon. That's kind of the way our industry merges the balance of science and art, where we're still very human, but the more we move towards automation, we're not trying to remove that human element from the actual tasting and enjoying of whiskey, but we're trying to imbue that into our scientific ideology.”

Sawyer echoed the sentiment succinctly. “Technology is seen as it's going to replace human beings,” he said. “Here it augments, it enhances.”

Project Scope

• 27,505 Tags
• 27 Screens
• 16 Pop-ups
• 10 Clients
• 736 Alarms
• 1 Devices
• Basic Architecture
• 1 Database
• 62 Tags logging historical data

In an industry like pharmaceuticals, maintaining quality and compliance is a strict requirement, not an optional goal. Outdated or ineffective technologies and methods can not only hamper efficiency, but also stunt growth and potentially affect product quality.

That was the situation Sandalwood Systems Integration Group found itself in with one customer who was having difficulty bridging the gap between their scheduling application and their ERP system. Sandalwood leveraged Ignition — an industrial automation platform for SCADA, HMI, IIoT, and more — to deliver a solution that completely revolutionized the customer’s production processes.

Minding the Gap

The customer was struggling with a recipe control gap. While their ERP system provided meticulous high-level recipe control and monitoring, the plant floor lacked real-time data as well as access to scheduling and optimization tools, relying instead on an in-house Excel-based application to schedule multiple sterilization lines.

Sterilization scheduling can be a complex process: components must be sterilized in time to feed fill lines, which are predicated on the downstream demand of the final product. On top of that, the existing inventory of sterilized components needs to be considered when determining production quotas. Relying on Excel macros for batch preparation did not offer the flexibility or scalability required to effectively manage the sterilization lines, resulting in a system that could only schedule a few days at a time, hindering long-term planning efforts.

“We were initially given a copy of the Excel-based application and asked to duplicate it in Ignition, which acted as our initial requirements,” said Bob Sloma, Digital Transformation Lead & SME, Systems Integration Services at Sandalwood. “As you can imagine with an Excel-based application, figuring out what they were doing by analyzing the VBA code was a challenging task.”

Even consulting with the application’s developer, it was a challenge to dig through layers of code and determine which reports were actually being used, as it became evident that certain reports were more vital than others.

The Excel application determined the best overall schedule by calculating all possible routings and their overall durations. This brute-force approach could not produce a full schedule without overloading the machine running the application. Clearly, it had reached the limit of its efficacy. “I have significant experience with MRP and production scheduling with my 30-plus years of experience and knew there was a better way to do this,” said Sloma.

Batch Production Scheduler

Once Sandalwood and the customer clearly defined the objective of the project, Sandalwood was able to deliver the Batch Production Scheduler: an application that would allow the customer to create a schedule of the sterilization lines that covered the requirements for the full horizon of the fill lines’ schedule as well as enable them to add products and lines over time. The core functionality of the Batch Production Scheduler included efficient component sterilization scheduling, component quantity determination, as well as reports and metrics.

The Batch Production Scheduler transformed the customer’s production process with real-time scheduling and optimized resource utilization, leveraging Sandalwood’s algorithm to intelligently evaluate processing routes for each component, selecting the most efficient plan. The improved scheduling delivered accurate component quantities for caps, vials, and plungers based on the fill line product schedules, not only ensuring timely production, but also reducing waste and avoiding unnecessary downtime.

Beyond that, the new application delivered adaptable scheduling, allowing users to define multiple routings for component categories. This increased flexibility was especially useful as the new system introduced long-term scheduling, expanding the time window to weeks ahead. As production introduces new products and adjusts current offerings, the customer can now add new products easily, with bill of material-defined component quantities.

The new system also revealed some unexpected benefits, highlighting how difficult it was to implement changes in Excel and how little connection the data had to other applications. “Ignition was chosen as the platform to enable future interoperability starting with integration to directly query a database for inventory data,” said Sloma.

The system displays metrics for each sterilization machine’s schedule and its ability to meet fill line requirements. These detailed reports empower decision-making. “There are over a dozen middle managers and the reporting is being utilized by over three dozen people across a 24x7 operation,” said Sloma.

Sandalwood developed the solution’s UI in the Ignition Perspective Module. Perspective, which leverages mobile-responsiveness and web-based deployment, combined with the Reporting Module enables operators and managers to access reports via a web browser, eliminating the need for local files and allowing the customer to control and constrict access to specific screens and critical data.

Sandalwood’s “lab on a cart” speeds up the development process

Lab À La Carte

A solution like this doesn’t come out of nowhere. At Sandalwood’s corporate headquarters in Michigan, they have a “lab on a cart” where they develop the basis for their applications. The lab consists of a two-unit rack-mounted device running two Windows PCs — one is on the corporate network while the other is connected to a manufacturing network with a firewall between the two — in addition to other devices like industrial PCs, RFID readers and antennas. Sandalwood runs a VM to simulate multiple PLCs publishing data via OPC UA with other VMs running various development environments, one of which contains a shared Ignition Gateway, MSSQL Server, and PostgreSQL.

“Ignition’s use of Python as a scripting language was also a big advantage,” said Sloma, who developed a prototype coded in Python for the scheduling algorithm, including specialized rules for how often the sterilization machines need to go through a wash cycle between production cycles or component changes. “Most of that code was able to be used within the Ignition application by the Ignition developer without significant changes. That saved a lot of development time.”

Ignition’s designer does not limit the number of concurrent developers for a single project. While Sloma was the project lead for this application, Ignition’s shared environment allowed multiple people to perform code development, reviews, and functional testing. As a result, Sandalwood was able to complete most of the development within their lab before implementing the solution in the customer’s environment. “Ignition is a breeze to install,” said Sloma. “This was handled by the customer directly. It takes more time to get the infrastructure in place (VM, network access, etc.) than it takes to install Ignition.”

Ignition’s capacity for rapid development and implementation greatly expedited the project. “The ability to start development sooner within our lab while our customers get their environment in place is a game-changer for us and allows us to deliver solutions more quickly than if we had to wait for clients to set up the resources and grant us access,” said Sloma.

Planning Long-Term

Even with the successful implementation, Sandalwood is already looking to improve the customer’s downstream visibility and advanced scheduling while utilizing the same UI template. Even though this project is not currently connected to any devices, it includes the SQL Bridge Module. Sandalwood plans to connect to a SQL database at some time in the future, with the goal of eventually obtaining the live component inventory data directly by querying the database via Ignition. The Sandalwood team hopes to utilize Ignition to develop line side user dashboarding and annunciation (Andon board) and create a digital whiteboard for the operators. Another goal is to integrate the customer’s Microsoft Active Directory for user management in place of Ignition’s built-in capability as well as their badge-in systems.

The Batch Production Scheduler has streamlined the customer’s scheduling process, and by implementing the Ignition platform, created a foundation for innovation both short and long-term.

Kanoa MES is a modern Smart Manufacturing solution designed in and for Ignition. Learn about the Kanoa MES Modules, Kanoa MES Database, and Kanoa APP Ignition project you'll use to get started with Kanoa MES. Check out a live demo of Kanoa Ops and Kanoa Quality to see how you can configure your MES in days and get insights into your manufacturing data with ease.

Transcript:

00:01
Jason: I'd like to start by thanking you all for coming today to hear what it is we're doing at Kanoa, and thank Inductive for creating Ignition, for creating this incredible platform that has allowed us all to do the amazing things that we're doing today. In 2018, we formed Kanoa to help companies implement Ignition-based MES solutions with a bent on project management, lean Six Sigma solutions, and change management to help them drive continuous improvement. We'd seen way too many projects fail, and not because of software, but because of people's failure to transition. And it seemed that most companies were so focused on the digital transformation part and the implementation of software that they really hadn't spent any time on the people side of making sure that these projects were successful. So for us, selling MES software and solutions is a really poor business model if companies do not get value out of the solutions that we're implementing. So we really do focus, we come in for companies here. If it's your first time implementing an MES solution, we're going to work with you. Once you've got a proven track record, you've rolled this one out, you've done your pilots, you've got production lines, and people are actually deriving value from it, then knock yourselves out, you can carry on, you can use this as much or as little as you want.

01:33
Jason: MES applications are not trivial, and there's a fair amount of customization that has to take place. What we found over the years was really the difficulty in keeping up with the constant pace of a release train. I mean, every few months or every five weeks, they keep changing, they keep adding to it, and we have gone through so many refactors, we all have. We went from... Well, we started on 7.5, then 7.9 to 8.1 was a refactor vision to perspective, a huge one. Then we started changing expression tags to reference tags to take advantage of MQTT. And this is none of this is a bad thing. It's a constant evolution. But we have constantly had to keep reinventing ourselves to remain relevant. And because of that customization and the constant change, we found that some customers ended up potentially throwing away their solution, and starting again every time with the big changes. So in 2020, we decided to take a fresh look at what an MES solution or platform should be. And from what we've learned over the years, keeping the good and replacing the bad. So for a while now, we've been touting MES for masses. This is not a communist manifesto, but it's more of a guiding principle that really drives the products that we develop, in a sense, do I press or do you?

03:03
Jason: You got, amazing technology, go, it should be affordable. And we follow because of this, we follow the same licensing model as Ignition. It works for them, nobody books at the cost of Ignition. And the Ignition platform has been so flexible, in the sense that you could throw everything on a single server, every single one of your sites, your enterprises, your assets, run it up in the cloud, and you could have Edge devices pushing it up, but you could also distribute it. At the end of the day, the architecture that you're going to use is going to be driven by whatever constraints, whatever requirements of the applications you're building. In that vein, we said, let's follow what Ignition does, if you truly want to have an MES cloud server. And we think that's a great idea. Everything it has to connect to ERP systems is up in the cloud. Why not have a connectivity up there and use MQTT and Edge devices to push it up? It should be accessible. And that's a fairly easy thing to do because we are building modules exclusively for Ignition, and their licensing of unlimited users, unlimited tags, has been a game changer since 2010 when I first started using it.

04:17
Jason: If you're going to drive continuous improvement, you want everybody inside your corporation, your company, to have access to the information that's going to allow them to drive continuous change. It should be intuitive, moving to perspective. We absolutely love this because we can really make the user interface intuitive. And quite frankly, if you look at Amazon or Google, any of those companies, we use them every day. Nobody has ever read the user manual to be able to buy something on there. We kind of feel the same. Yes, there are aspects of MES that might be a little bit more specific, but if you use the same interfaces that people are using on their phones, if you give it to them in the same devices, it can be on a computer, a tablet, or a phone, then we can make it intuitive. And if it's intuitive, people will use it. And it has to have value. Value is in turning data into information. So when we built Kanoa MES, we started from the ground. We started with data. Data is the most essential part of it. So we built a third form, normalized database schema that stores the data, and it's open, and it's accessible.

05:34
Jason: So we build our APIs, our system functions that will interact with that database. They will give you the analysis, and it's lightning fast, and it's the smallest footprint that has data integrity and constraints. But you can also call those same stored procedures if you want to share it with Power BI, or Tableau, or an ERP system, or SSRS reports, it really doesn't matter. But you build from the data, you get value.

06:01
Jason: And then finally, it has to remain relevant. Keeping up with Ignition release train is like trying to board a train that's got no doors. You're never going to do it, and that may sound like a bad thing, but consider what Ignition gives us with this release train. They keep us relevant. They keep us on top with the newest technologies. They ensure that security matters are handled. They've given us MQTT, they've given us Kafka. I still don't know what Kafka is, but they've given it to us. And that's what Ignition does. So in this journey, we've got to keep abreast of the train. So whatever solution you're building here, it's got to be relevant, and it's got to be upgradable. So we, in our design, have ensured that our modules and our implementation have the lowest coupling with Ignition, because they're going to make changes anyway. We want you guys to be able to update with impunity and not fear that you're going to be held back by using our solution. Now, having said that, give us a chance to check under the hood of 8.3 before you upgrade. But with that, that's enough about words. I'm going to hand it over to Sam. He'll show you around. Thank you.

07:12
Sam: Yeah, thanks, Jason. So, really, all of those design ethos that Jason is talking about has culminated into the Kanoa MES platform that we have built. This configurable, flexible, intuitive MES software that is really meant to empower teams and drive continuous improvements. Because we are not doing MES just because it's fun, even though it is for some of us, but we are doing it to really improve processes and make plants run better. So when you get Kanoa MES, there are three components that you get every single time to make sure that you are starting from a strong foundation. You get the Kanoa MES database, that third form normalized database schema that Jason was just talking about. That is where all of that core key MES data is stored, as well as all of your configurations. You get our Kanoa MES modules that plug into Ignition and give you almost 400 new system functions to go and call the data that you need from that database. And very importantly, you get the Kanoa app Ignition project. This project is designed to give you a starting point with all of your configuration and analysis and daily operation tools that you need to get started with an MES from day one and continue to expand, customize, and tweak that application using the power of Ignition to make sure it can fit your application.

08:30
Sam: There are three modules that we sell over at Kanoa, actually, I guess two that we sell, but three that we make. Kanoa Core comes with any other module that you get because that has a lot of those core functionalities that you're just going to need for any smart manufacturing system. Theming, languages, security, all of that is in our core level and is shared across all other modules in Kanoa. But really, the two things that we're here to look at today are Kanoa Ops and Kanoa Quality. Kanoa Ops is going to be your system for OEE, work order management, asset management, scheduling, and shifts, and all the analysis that comes along with that. And then Kanoa Quality is a pretty unique offering in that this is a form design and dispatching tool that also gives you the tools that you need to analyze the data that you got from those quality forms. All again designed within the Ignition application. So, I am going to try to do the fastest demo I have ever done in 15 minutes and try to give you all enough time for questions at the end. But I do plan to do a webinar within the next two weeks after ICC to do a more thorough one-hour demo.

09:32
Sam: So if you like what you see here, definitely come and keep track of our LinkedIn page and our website to get more information on that. But without any further ado, here is our Kanoa Ops system. So as I mentioned, we do have two modules, Kanoa Ops and Kanoa Quality. You can get them together, you can get them totally separate. I'm going to start with Ops and then do Quality second. So let's kind of go through the day in the life of a production operator and the way that you could be using our Kanoa Ops platform. We'll start with looking at our work orders, scheduling some work, running that work in production on a line, and then getting some of the data afterwards. Then we'll actually peek into the configuration as well. So if I'm going to go ahead and manage my work orders, I need some interface for actually downloading all of those production orders. This can be downloaded from an ERP. They could be made right here in Kanoa MES. You are just picking the work order name the material that you need to run and how much of it you need to produce.

10:31
Sam: Once you have all that, you need to actually schedule that work on a line. So we have our operations schedule here, where you can actually see we're taking advantage of the BIJC calendar component that we do include with any Kanoa purchase. And this lets us do all sorts of things like create non-production events with certain recurring rules and things like that. Really fantastic tool to help manage all of these schedules. We have our normal production schedule here, but I can also do things like pop open our work order list, drag and drop a new work order into our timeline. The system's going to go, see what material you're running, see the appropriate rate that it runs on that line, and schedule it for the proper amount of time, which I'm then going to delete before it tries to run two work orders at once. The other thing that we have in here is our shift scheduling. So our shift scheduling is really cool. What it gives you the ability to do is to define shifts at any level in the hierarchy, and an asset will look for its closest parent with a shift. So if your whole plant runs on a four shift complex rotation pattern, except for the packaging area that runs in a different shift schedule, you can manage that very easily within Kanoa.

11:38
Sam: So we have our work orders, we've scheduled that work on a line, we have all of our shift data, we're going to track our data within the context of those shifts. Now it's time to actually open up one of these lines and get some work done. So from here, you can see our main enterprise overview page. You'll notice a couple of things here. So we're kind of following an ISA-95 style hierarchy with our enterprises at the top, a number of sites with areas, and then OEE enabled assets underneath them. We like to say we're ISA 95 inspired but not restrictive. So if you wanted to have, say, a business unit layer and organize all of your sites into business units between your enterprise and your site, go for it. We totally enable all of that. We want to have a site in an enterprise, but besides that, we're really flexible. So I can click into my production area here and get a summary of how all of my production lines in this area are currently running. We can see we got a little bit of an issue over here on Pac Line 1, and our other lines are running at various degrees.

12:35
Sam: I can go ahead and click into Bake Line 2 here and get to what we call our asset Operations screen. The idea of this screen is that every BIM operator that is responsible for this piece of equipment, everything that I need to run it is right here within this interface. I can see my current production modes and states. I can go into my run control and manually override my mode to say we need to go into a changeover.

13:00
Sam: I could manually select another work order or another product that I need to run from here. I can also go ahead and check things like the schedule right here from this interface. And then one of the very common things is, of course, to go and check on all of my downtimes. So I'm going to go and say, what were all of my downtime codes over the last seven days? And then from an interface like this, I can always double-click into one. I can recode things, I can add comments, I can add, delete, or change downtimes that we have recorded. Again, we like to collect all this data automatically and perfectly whenever we can, but there are plenty of times you need to do some manual work afterward too.

13:38
Sam: One other report that I'll show really quickly is our run review. So, this is really critical in letting you kind of see all of those production events that have gone through a certain asset. So what I'm pulling up here is we can see I've done three production runs on this line. It's breaking them up by shift and I'm getting certain metrics like their total runtime minutes, their OEE downtime minutes, all here from this screen. So another type of... We also have some more complex analyses. I'll pull up our downtime report as one example, taking advantage of some of the Apex charts here. Thanks again, Travis and the Ignition team for helping prepare all that. We can see all of our downtime by category, by state, and reason, broken out and seeing how it distributes by shift. I can do a stacked bar chart of my total downtime by reason, by day, and down here at the bottom, I can put it all into a table with a handy little export to Excel button. 'Cause I can make you the greatest dashboard in the world. And what's the first thing that you're going to ask me? How do I download it to Excel? I'll take it.

14:44
Sam: I'll take it. So again, in the fastest demo ever, I also want to quickly show you some of the configuration about this because one of the coolest things about Kanoa is again, everything I'm showing you here, you just get in that starter project that we are going to give you, including all of these configuration tools that you need to get you a significant amount of the way into your MES implementation. So you can see over here, I have my asset hierarchy. I can drill into a site and an area. I can click into a specific line and see I have this OEE enabled. You say, something's OEE enabled, we're going to go ahead. We drop a UDT into the ignition designer. And that's where you're wiring up your points. Another interesting thing to note is that everything I've shown you here runs off of three tags per piece of equipment. Give me your Infeed count, your Outfeed count, and your state. Everything else is configured over here in the Kanoa app. And granted, I know it can get more complicated than that. There's a lot of ways that you can make it more complicated than that.

15:41
Sam: But you can get all of this with just three pieces of data per piece of equipment. We have things like modes and states, where I'm designating all of the modes that are appropriate for this, and our state list where I am associating specific states with an asset, giving it a PLC code. That's how we're tracking all of your downtime. But it's really great that all of this is right here, configurable in the app with handy, intuitive tools. I can come in here, we can drag and drop this mix line into Jacksonville Juices if you want. It'll let us do all of that on the fly. So drag and drop assets, rename things. All of your data goes along with you. It happens all live. So that is a very quick preview of Kanoa Ops. Let's totally switch gears here and talk a little bit more about Kanoa Quality. So Kanoa Quality is all about paper on glass, right? You're running around with a bunch of check sheets today. You need to move that into a digital system to not only just get that paper off the shop floor, make that data more real-time, but also as we're moving these systems into digital platforms, we can establish more accountability.

16:46
Sam: We have this sense of a state of each of your check sheets. We're tracking the state of these as they go through. So check sheets can become overdue or missed, and we can flag operations and management teams when the sheets aren't getting done the way they need to get done. And that starts with our main overview schedule. Here you can see I have one approved test in my queue. I have four missed tests. Let's go and just do one of those missed tests, a little bit late. I'll double-click into this. I can even get a little bit bigger because again, we're just using Perspective for all of this. That's an important point I'll mention is that all of this is built in Perspective and none of this is using custom components. We are just using regular Perspective components that we are providing to you in that open starter project. So we're going to take advantage of Ignition's inheritance features. You're going to make new projects that inherit our projects where you can then override screens, make your own screens, all with our examples that you can build from. So I'm going to come in here, we're going to do a couple of checks to make sure that we can switch over this packaging.

17:49
Sam: Our area is clear of debris. Our machine is shut off. I'm going to take out my rye bread packaging and it's going to weigh 566 pounds. I'm going to put in our next wheat bread packaging. Notice this control limit up here as I put in something that's 625 pounds, and that gets flagged as orange in our little progress bar and in our control limits. I do a final checklist to say yes, my tooling is out of there and yes, my machine is turned back on. I do a final check to make sure that all of this data is the way that I want it and I go ahead and submit. So that was a very manual test. It doesn't always need to be that way. We can get data automatically from PLCs. We can get data and do run quality checks that don't have any manual data. And it's more like an event-based historian. The advantage of doing that is that we get all of that data into Kanoa Quality and then we can run our analysis on it. So I'm going to come into something like our fermentation temperature check, where I believe every 20 minutes this goes and collects three points out of our simulator and spits it back out here into this report.

18:52
Sam: Notice how quick that just happened. Right? Let's actually do for all of the data for this month in September, grab those three data points collected every 20 minutes, go get the data. It's done. That's the power of this database that we have in the background that's storing all this information. I can click into one of these zone temperatures, and I can chart that. This is where all of our SPC comes in. I can pick our Nelson rules. I can apply all of those. I can see my rule two violations, my threes. I can put it all in a histogram too.

19:19
Sam: Now, like ops, one of the most powerful things about this is, you don't need to go into the Ignition designer to do almost anything that I've shown you here. The only thing that you would need to do is to make certain tags available to the quality system so that you can just tie them in and get automated data. But the rest of this form design is done here in the app. If I come into our Kanoa quality configuration and look at our check sheets, I can take a look at that packaging changeover that we were doing earlier.

19:48
Sam: We can see things like if it's enabled, if this requires a sign off, if it's only appropriate for certain assets in my hierarchy, I can go into the checks themselves. And here is my machine shutoff check where you can see it's a string where I can add in specific instructions for my operators, where we can create a pick list of what shows up for them to be able to enter. The whole idea here being your quality managers and the ones that are making these forms, not necessarily the people that you want in your Ignition projects every day, they need a different interface to go in, add more instructions, tweak checks as things change. And that is why we give them this interface here. In addition to that SBC data and the configuration here, we did also talk about kind of the efficacy of the checks as well. So I can also do my check summary and by check sheet I can see how many are getting missed, how many are getting approved. I could put this on a shift heat map to see if there are certain shifts that are not doing the test they need to on time, again driving that continuous improvement and really trying to drive accountability around a lot of this data.

20:53
Sam: So I did it. That was a very quick demo. The one other thing that I will show really quick, 'cause I actually even have a little bit of extra time, is I didn't really get to talk too much about some of those Kanoa core functions that you get within every application. And there's three main things that you really get. One is over here and that we do have multi-language support. We are just using the embedded Ignition translation engines that you have in there. So we do have a couple of languages out of the box, though I've heard our Korean is terrible. We also have all of our themes in here. Jason would not let me do this presentation in grape, despite how bad I wanted to. These are also totally configurable. So you are totally welcome to go ahead and brand this for what you need for your specific company. And I will shift this back to blue before I go and show you the other main thing that you get out of the core modules, which is our security. So we're still using Ignition for all of your authentication, but we do add an extra layer of security here in Kanoa, just because the roles and permissions that you need in MES are a little bit different.

21:56
Sam: But we're doing it using things that you're all used to. We have our individual users that you put into groups. You give certain permissions to people in those groups, and you could do all of this by asset too. So I could be a manager for the packaging area, but just an operator somewhere else if I want to. So there's a lot of other exciting things that we have built or are building in the Kanoa Ops and quality platforms. We do have a mobile solution for Kanoa Quality if you wanted to run all of those checks on your phone with a slightly different interface. We do have a new dashboard editor as well as we are making new widgets to give people the capability to design their own MES dashboards. And we are also introducing lot tracking as a free upgrade in Kanoa Ops very, very soon. So we just need to upgrade some of the UX for it. The bones of it are all there and working, but it's really exciting to see that we can now have lot tracking and track traceability within our OEE solution, so that all of our counts are going to match up and all of those production orders and the tracking is all synced with a single source of truth.

23:02
Sam: So, again, that was a very fast demo. Keep an eye on our website and our LinkedIn if you wanna get more information on a webinar coming up soon. We do have a booth upstairs, but now is a great time for questions if anybody has anything they wanna ask us.

23:17
Audience Member 1: Can you talk about ERP integration?

23:20
Sam: Can we talk... The question is... Sorry, I'm gonna repeat it just 'cause I know there are some mics going around in the live stream. The question is, can we talk more about ERP integration? So, yes, we do a lot of ERP integration into these systems very frequently. Two of the most common points would be downloading all of those work orders that you have from an ERP into your MES. We can download them into the work order table and then have you schedule them manually, or we can fully schedule all of that work as well. The other one would be around material, something I didn't go through in the demo today, where we can download all of the materials that you run on your lines and then associate specific materials to specific assets with the rates that they are expected to run at, Jason you wanna talk more about that?

24:01
Jason: Yeah. Just to add, in terms of the interfaces, we can use all the tools that Ignition provides. So we can use web dev module for web services, you can use the Sepasoft one. If you wanna use the SAP business connector, it's really entirely up to you. Generally, we will do a RESTful API and then just have the ERP system pushing production orders down. If they push down a production order that's got the item, the item doesn't exist in our system, we will create it. If they then wanna put information about a start and end date for an item or an asset, we will create the association that this item can run on this asset. We'll give it default information. Every ERP integration that we've done is different. There are different business rules, so you've got to have that flexibility. But certainly, yes, web services are favored. We've done flat files. Hate doing flat files. Done middleware tables as well. Not really happy with those either. It's always funny when you have these digital transformation projects, they talk about everything they're going to do and then they're saying, yes, you can open this flat file and get the data out of it.

25:00
Sam: Great question. Any other questions? Yeah, right there.

25:06
Audience Member 2: So does the Kanoa Quality Module provide mechanisms to have a, say, PDF or image or something like that that is a helping guide in addition to the instructions and text?

25:16
Jason: Yes.

25:20
Sam: Yeah, sure.

25:20
Jason: Yeah. And again, everything that we've shown you here is we made a conscious choice. These are just Ignition perspective components. We've seen too many times where you'll get like a really complex component which doesn't allow for customization. So you can look at our views in here. If you're going to start like a production order, you're going to take a quality check, but you wanna have the operator do an additional step. I mean, you can go in, you can add, you can see how we're doing it in the background. They've got the PDF viewer, they've got the iFrame. So again, with every company you're going into is saying, sure, it'd be great to give them work instructions. Where do you store them? Is it in SharePoint? Is it on a network drive? How do you want to do it? We also add support for images. So particularly on the phone, we've now got it where people can take a quality check and it's saying, take a picture of a weld. From here we can use the phone, it will capture it. We store it as a blob in a database or we can push it out. All of that stuff is the customization.

26:13
Jason: What we're giving you here is not going to be 100% solution. It never is, but it gives you 80% of the way there. It's a fully functioning application. It's on you guys now to extend it as you see fit. And as you're doing that, if you find that there's stuff that you want, you see that you need, you can talk to us. Absolutely. If it's out of left field, we'll say, that's all on you. But if we look at it and say, that's actually really good for the product, that makes sense. Absolutely. The more we can get into the product, the better it is for us and for you. Because ultimately, what we're focusing on here is building a product that we can support for the long term. We have documentation, we have training, and we're going to make sure it's a supported product so that you guys don't have to.

26:58
Sam: Yeah, great question. I see one in the back over there. Yeah.

27:02
Audience Member 3: Is there like an API library for scheduling something like automatic work order stops and starts, or doing like, basically, you know, automated sample collection on the machine?

27:11
Jason: Yes.

27:11
Sam: Yeah, so the question was. Sorry, the question was about the API hooks that you have and kind of how you can build your own things with the API. Jason, yes.

27:18
Jason: Yes, I said we got 380 functions there, so absolutely, you can build your solutions in there. Everything that we do through here is going to be calling one of those system functions. So we can be called from a tag. You could stick it on the end of a web service call if you wanna do it from another system. However, that data is in there. But yeah, everything's through an API.

27:37
Sam: Yeah, but like for example, that downtime report that we do, there is a system.Kanoa of.events.getdowntime events for this asset with this start date, this end date. And yes, there's a lot of other variables you can kind of put into there. But yeah, we're giving you 400 system functions like that to put in and retrieve data from that database.

27:53
Jason: Let's have Dan. And we were promised a mic runner. Where's our mic runner? All right. Okay.

28:00
Audience Member 4: Hey, Jason, is this available as a trial?

28:03
Jason: Yes. Yeah, I mean it's just modules, so it works exactly the same, as Ignition, but you can do trial license. We actually think we do one better. One of the things here is that there's work and effort involved in getting the modules and getting it up and running. We'll just give you a container. So we've got a bunch of Linux cloud containers. We can run eight docker containers all running at the same time. So we'll actually get it where it's configured, it's set up for you. You can get in there and the design it, you can play with it and try it out. And if you do want to like an extended period, we can give an extended period trial license.

28:38
Sam: Yep.

28:39
Audience Member 4: Please.

28:41
Sam: But no, definitely those for the, the integrators and the people that just kind of wanna try this stuff out. Those containers are a really fast way to get onboarded. You meet with us, I kind of show you some of the basics and setups, and we kind of go through a basic configuration and then you usually have it for two weeks to show it with your teams and start to play around and see if it's going to be the right thing for you. So, if you are interested in something like that again, you can reach out to us, booth, website, however you want to. And we're happy to schedule some time to get you connected with one of those. Any other questions?

29:13
Audience Member 5: I saw that the quality module looked really good. We do a lot of that with our shop orders. So would I need both modules to essentially execute an order that collects a lot of data?

29:24
Jason: Yeah, actually, I can take this one. So when we built them separately, because there are a lot of people, they already have their own MES solution. They want a quality one. That's saying one of the things that we can do is everything through our APIs forget... Ethan, I didn't recognize you there. Nice to see you, man. So you can create a view table of assets. You could do it for work orders. You could pump it in if you didn't wanna use it at the same time here. If you're going to use quality in here, but you wanna configure assets and stuff. Yeah, we can absolutely figure that out.

29:54
Sam: Yeah, in the front.

29:55
Audience Member 6: So one of the things you guys started out with was providing a full solution. Not that this isn't. But to go from a great piece of software to return on investment. How are you guys tackling that?

30:09
Sam: Yeah, so we do think that... So I think this is our last question. I've just got flagged for. But it's actually a really great one. Because that was, as you said, that was a big part of our philosophy that we're not doing this for fun, as much fun as we find it, oddly. But we wanna drive continuous improvement. The software only gets you there so far. A lot of it is then around adoption and change management and actually intentionally doing continuous improvement. So a lot of what we think we're kind of trying to provide in this software is something again that kind of is intuitive, that with minimal training people can go in and actually be using, which we know is a huge adoption hurdle for a lot of these systems. That's why we really wanted to embrace things like language support, which I also think is a hugely important hurdle that we wanna be able to cross over. But then really a lot of it is also kind of just whether it be through Kanoa or the teams managing the projects or a trusted integrator or consultant really working with that end user to talk about their continuous improvement goals and how they're going to achieve them and having an intentional plan to do so.

31:08
Jason: Yeah. And to add to that, still the same last question. It's the nature of the beast of MES. Every implementation is going to have different challenges. So you can go into a company where they've really got their stuff together and they don't need any. They've got it figured out. But you've got the other companies where you need like it's the connections to PLCs, the manual lines is a real part of the data collection, which is going to be a challenge. We go in, we always talk about an engineering study, but it's a collection of meetings that go over the first week of in there where we're first off, we'll do education. So we're PMPs, we're lean, Six Sigma certified. We've been doing this for a really long time. We know the pitfalls and we know the risks of MES projects. We'll start off with half a day of education with all the stakeholders from everyone from operations, maintenance, quality, IT, finance, planning to basically discuss. And we've done this to various levels of degrees of success in that some companies have actually after that training, they've just stopped because they said we realized we weren't ready as an organization, we are not ready and it's a waste of time.

32:17
Jason: You have the other ones who they say, "I hear what you're saying, Jason, just write the software." It's like, seriously. So we can, we'll provide changes, whatever it's needed there. We'll do change management, we will help. We say, you need a project chart. So you certainly need a vision for what it is you're doing. You need a cross functional team. You need stakeholder agreeing and buyin. And let's figure out who's being affected by this one. Let's create a process map of what your existing systems are, because we're going to be deprecating some of those in here by the very nature of that act. That's where you start to actually uncover areas for continuous improvement just in implementing.

32:53
Sam: That's a great question to end on. Thank you all so much.

32:55
Jason: Thank you.

Learn more about our networking and automation portfolio as a complement to Ignition. We will showcase our PLCnext technology with Modular I/O, Ethernet switches, and new MQTT / MODBUS protocol converter products. We will introduce you to new upcoming technologies based on Single Pair Ethernet and APL. 

Transcript:

00:00
Arnold Offner: Hi there. My name is Arnold Offner, and this will be my very first presentation to you Ignition system integrators, end users, and partners. It's just recently that Phoenix Contact became a member of the Inductive Alliance Partner Program, and so my presentation today will not include a true demonstration of product as such, but I wanted to talk to you about some of the examples of some of the work we've already been doing with the Ignition software package. I wanted to thank you all for coming to this presentation. At least I was not holding you up from lunch, and I'm glad you took the time after lunch to be here this afternoon. At Phoenix Contact we're actually a German-headquartered company, but there are a lot of similarities between ourselves and Inductive Automation. If you look at the idea that they're family-owned, privately held, and they essentially have grown organically just like we have. Here in the US, we're about 1000 people. You probably know us for terminal blocks, those green terminal blocks that you find on a lot of electronics out there. You probably know us for power supplies and relays, but our real connection with Inductive Automation and the Ignition software package is related to the hardware that I would call networking and automation.

01:19
Arnold Offner: And so in my presentation today, I wanted to show you some of those examples, but more importantly, I wanted to give you an outlook into where our partnership is gonna go and how that might benefit applications of yours in the future because I've heard people talk about the IIoT, I've heard people talk about applications that might involve the edge, and what I wanted to share with you today is some of the work that I'm doing at Phoenix Contact that involves, I think, a technology that will be very interesting for you towards the end of my presentation. And then Marcus will run around with the microphone towards the end, and he'll get to see if there's any other questions you have at the end of my presentation. So we're good to start. You signed up for 30 minutes, so I'm gonna try and respect your time and make sure that this works for both of us. So at Phoenix Contact we talk about enabling the Digital Transformation. This actually is a campus picture of our headquarters in Germany, but we actually, shall we say, essentially, except for my accent, which you'll note didn't come from the US, came from way south of here.

02:21
Arnold Offner: We actually have a campus; this is our main campus in Blomberg, Germany. It essentially services our global operations but what it also does at the same time it allows us here in the US to actually, what we would say, think global but act local. In other words, a lot of my colleagues that you'll ever get to be meeting here in the US market or whichever market you're in, you will find that they are essentially local people who understand the local markets. I'm involved in development and manufacturing, and like I say, it's about this idea of the Digital Transformation; it's about automation; it's about networking. So now I'm gonna make sure that the clicker works. And it doesn't. Okay. I'll tell you what we'll do.

03:05
Arnold Offner: We'll do it the other way. Alright. So this, just to give you an idea, is the web interface that we've set up at Phoenix Contact, and if you come to our small booth outside in the hallway, you'll get to see two things that we're actually demonstrating. We've used the Ignition software package to show essentially our customers, yourselves, but to allow our salespeople just to tell a customer, "Hey, if you type in iiot.phoenixcontact.com, we will actually give you a sampling of some of the things we're working on right now." On this lower purple line, you'll notice that actually is our current, and this is just a screenshot, so it's not live; it actually is our solar installation that we have at our facility in Harrisburg, Pennsylvania. And then we also have about 18 electric vehicle employee charging stations.

04:00
Arnold Offner: And so we actually just run a very little interesting number each day. We basically think that about four miles is possible with one kilowatt of electric energy in an electric vehicle. And so that's where we come up with 550 miles of... miles that we've charged employees that have an electric vehicle in the employee fleet in Harrisburg. We have about 800 people in our facility in Harrisburg, so product marketing, sales coordination, design and manufacturing, and logistics. And then scattered around the country another 250 salespeople who are responsible for either customers or particular industries around the contiguous US. So one of the exciting reference projects that I did wanna mention, and you'll find more of this on YouTube if you go looking for it, involves a project we did last year, and actually last year and the year before, but it was successfully deployed during the course of early last year. It's with a hydro plant up close to Boise, Idaho, known as the Lucky Peak Hydro Power Plant. Derek Stone is one of the gentlemen who is actually very closely involved with this project together with our team, and we actually have two Gold Certified Ignition Software Engineers at our facility in Pennsylvania, which means they actually wrote a lot of the code that then helped the folks at Lucky Peak actually deploy Ignition together with our hardware in the upgrade that they were deploying in their facility near Boise, Idaho.

05:29
Arnold Offner: What I will tell you is there's two videos, and then there's also a set of articles that were written that actually discuss how the Phoenix Contact hardware together with the Inductive Automation software came to be, how this upgrade took place. So as part of my agenda for today, like I said, I really wanted to just talk to you about the things that we're displaying here to add to products you might already know from us, and I'm gonna save that one right at the end there for last. Like I said, Phoenix Contact back in 2017 launched a controller we know as PLCnext. It is a very interesting PLC because it's not your custom PLC. It's based and predicated around a Linux controller. In other words, it's based entirely on the Yocto platform. And what it allows customers to do is we develop software that allows you to use the typical IEC 61131 software programs, but it also allows you to write your own code. And so if you're best in class or you have a certain skill set, either as a programmer or as a company, it's also possible for you then to develop software code that you could then sell through a PLCnext store that we've created to go with it. I'm gonna cover a little bit of the Ethernet switch technology and then talk about protocol converters, but really my key discussion for today is to tell you about how we're very soon gonna be able to get into this space as well.

06:53
Arnold Offner: And that technology is gonna be based on what I wanted to share with you in a moment called Ethernet APL and SPE. And so that is Ethernet APL is predicated around its usage in the process industry, the heavy process industry, and SPE; if you've not heard about it so far, it actually is called... It's single-pair Ethernet. And single-pair Ethernet is gonna allow you to go 1000 meters, so 3280 feet. It's gonna allow you to essentially take 10 megabits of data all the way to devices. And some of the technology that I'll show you in a moment actually just stands to benefit from this capability. And then towards the end, I might still have a chance to then tell you some of the raffle prize winners of people who may have stopped by our booth already and some of the raffle prizes we have to give away. So the area of application where we get involved could be considered to be these five. Phoenix Contact is very well known in the factory automation space. So what we would consider production logistics, everything there, machinery, network machinery. If you then take a look further up to the side here, you'll see infrastructure. So we've done a lot of projects with customers that involve ports, harbors, pipelines.

08:07
Arnold Offner: We've been very much involved in the area of power plants, so the IEC 61850. And when I talk about networking, also realize that part of our portfolio also includes cybersecurity. So we also have capabilities to allow people to log in remotely to equipment, plant, machinery, and basically extract data without having to physically send a person there. And this is very important too if you consider that Germany as such is an export-led country, so a lot of technology that our customers buy from us in Germany that gets exported to other countries. It's a very expensive proposition to send a technician out to find out that the power cord was unplugged, and that's the reason why the machine's not working. It'd be good to know that ahead of time, and then also know what parts you need to take with you if you get called away to a site somewhere else across the globe. Phoenix Contact is probably best known for its products that were originally defined in, when electricity became a big thing in the '20s and '30s. And so our terminal blocks actually go back that far, in other words, to the time when electricity and electric trams, and this is even before the motor car became an essential, I think, part of everyone's life globally.

09:20
Arnold Offner: Then of course we're talking machines and systems, so whether it's logistics, whether it's going to be containerized packages, and the part that is not quite clearly shown here that I'd refer to in area number four is we also do a lot of work in the water, wastewater. And slowly but surely we're also starting to invest more and more effort right now into the oil and gas, the chemical industry, and that's the team that I'm involved with here in the US. So we've actually been set up in Harrisburg, Pennsylvania, as a center of competence for the process industry, and that is why a lot of the process-related products that I'm about to talk to you about today come from the work that the team, the development team, and the manufacturing team we have in Harrisburg is involved with. So with that, I wanted to first show you a product portfolio that we started in about the 2016-2017 timeframe. This is also a pointer, right? So I wanted to let you know we've developed an IO-Link Master, in other words, a device that allows us to connect independently using an Ethernet port to an IO-Link infrastructure. There is somebody already who's come to talk to us about a module we created, which was a serial gateway, but actually not a serial gateway; it's an Ethernet-based gateway which allows us to extract HART data from a HART installation.

10:41
Arnold Offner: So customers are revisiting their HART devices in the field, and those critically important ones we can actually extract that data off the side without compromising the performance of the plant. And then over to the very left is a set of four different families of products that we have, and I'm just gonna basically not belabor all the different types of protocols. Save to tell you that this is where we take a serial communication and we convert it to Ethernet, and the moment we can convert it to Ethernet, there's a lot of creativity that all of you could come up with to then deploy this into an Ignition-based package or a solution for your customers. The one important one that's exciting for us this week is we are doing a little bit of a soft launch this week about an MQTT protocol converter that we've created, which essentially is available in a form factor of one of those four. Two of those are actually raffle prizes, and essentially what we're doing is we are taking Modbus TCP or RTU and then either through a single port or through a dual port, which allows you to daisy chain things. You can then essentially take Modbus data and then convert that to MQTT along an Ethernet infrastructure. So those are the part numbers, and I know sometimes always people grab a cell phone and want to see part numbers, but that just to give you an idea of the Ethernet port count and the part numbers.

12:10
Arnold Offner: And the ones I marked in bold are actually the two protocol converters we've actually set up as raffle prizes for today. Alright, so the most important thing that I did want to talk to you about revolves around this topic of the field level today. The slide, as you'll notice bottom left, refers to something called Akima. Akima is the world's largest process control and process automation trade show anywhere in the world. It's held every three years. And back in 2021 is when we first, during the lockdown, actually conducted a virtual event where we talked about the space in the process automation space that is still not Ethernet compliant. And this is where a currently serial bus or analog connectivity currently exists. You're all aware of 4-20 milliamp loops. You're probably all aware of things like HART. You're probably also aware of things like PROFIBUS PA or Foundation Fieldbus. And this little area has never really been, until now, an area, a domain that you could actually do with Ethernet. And roll on into a time now that I'll refer to you as well, is we now have a technology known as Ethernet APL.

13:20
Arnold Offner: So it is a derivative of the IEEE single-pair Ethernet specification. And what we've actually gone and done is we have created an intrinsically safe connection, which allows us to go 200 meters from a switch in two wire down to a field device. And what we're able to do now is essentially tell you that Ethernet is now possible all the way to the very edge in a process automation application, probably the most difficult ones to engineer. And using this technique, this is the very same technique we do with single-pair Ethernet. So everybody who's ever worked with 4-20 or with HART or with any of the field bus systems know it's always two wires. It's not four pairs. So what we've actually gone and done is we've taken the IEEE 802.3cg standard, which essentially allows 10 megabits a second over a distance of 1000 meters. So make that 1000 meters. I always have to be careful how I get this right, but 3280 feet. And what that would allow you to then do is essentially have a smart device in the field that now has an IP address, which essentially can become part of an Ethernet network. So single-pair Ethernet is something that you're gonna hear more and more about. And I think at Phoenix Contact, because we've developed both things in the SPE space or the APL space, APL is nothing more than an advanced physical layer for process applications. So you can put whatever Ethernet protocol on top of that that you want.

14:49
Arnold Offner: We're essentially now going to be able to tell you that going to the edge means going all the way to the field instrument. What this also means, of course, is that this technology is still gonna live side by side with 4-20 and HART. It's still gonna live side by side with Fieldbus techniques, but it is gonna allow you now to get very advanced instrumentation or actuating devices to be part of your infrastructure at far higher speeds. And 10 megabits a second, just so you know what we're talking about, 10 megabits per second means we are 10,000 times faster than HART. And it also means that we are 300 times faster than any Fieldbus system out there. So sometimes when I do this presentation for my colleagues, I say, "This is an industry that no longer is gonna have time for coffee breaks." So the APL project is based around work that was done by four very notable standards development organizations. You'll probably recognize those four logos across the top. The FieldCom group is responsible, of course, for foundation, Fieldbus, and the HART protocol. The ODVA, as you know, is responsible for Ethernet IP. We're a member there. We're also a member of the OPC UA because what you now have to realize, if you start talking things in a digital space, OPC UA is probably gonna become the future platform on how this data transfer occurs.

16:04
Arnold Offner: And then, of course, the PROFIBUS, PROFINET organization, which also has its strength and is pretty much the rest of the world. But there are applications here too in the US that we're aware of. So those four standards organizations got together, together with 12 well-known companies in the space. And essentially what we did was we created a standard, a physical layer, which is protocol agnostic. And then what happened is at the end of August of 2022, the project, as it started in 2018, four years later, was dissolved. And then these standards development organizations went back to their particular members to then develop this technology further so that each of them can now create an Ethernet-based protocol on top of this advanced physical layer. So some of these companies you will recognize too, either because they are producing DCS systems or because they are producing sensors and actuators, commonly already used in the process space, or companies like Phoenix Contact, who we consider... Who I would consider to be in the infrastructure space. In other words, we are using a Layer 2 managed switch technology to actually create an IT-to-OT combination, which allows us to use regular Ethernet on the north side and then use the OT capabilities of APL into the field.

17:23
Arnold Offner: You will see that this is also a group of competitors that collaborate very well, just like I would say Alliance partners do within ICC each week, or each year when we meet for this week. And then the other thing I wanted to share with you is just some of the standards that we've also created and some of the documentation we've created, which allows us to essentially also basically create the foundation for now other companies to get involved in the technology too. And so I think I'm speaking to a lot of people who are gonna deploy the technology, and so the one thing I would mention is there is also an APL engineering guideline, which would probably become very interesting for you in the future. It's about 100 pages long, but it essentially takes the technology and the technique we've used from 4-20 and HART, and essentially now using APL allows us now to actually allow people to actually start defining, to start specifying an APL infrastructure moving forward. We are also currently, this is the part we're wrapping up right now, we're currently in the process of doing APL conformance testing, so interoperability, but all of these manufacturers are currently in the stages of either getting final certification or on the stages of still making sure that they have their class 1, div 2 standards, that they can conform to IECX or ATEX or any kind of national standards.

18:42
Arnold Offner: There are some countries that still insist on doing things a little differently. I'm thinking of countries like the UK. I'm thinking of countries like China, Korea, Japan. Those standards for those particular markets are still basically the steps that these manufacturers, including us, still have to work on. But the technology is now here, and what I wanted to share with you is that the technology is gonna allow us to actually develop some very, very interesting new concepts moving forward. And so in this Digital Transformation, we finally now have Ethernet all the way to field devices. I just wanted to give you a picture that shows the collaboration that occurred at the Phoenix Contact booth in June of this year in Germany. So together with the companies ABB, together with Endress and Hauser, together with KROHNE, and then a valve controller company here called Samson, we actually physically showed how this is possible. And I always like to point out that if you look at this ring, you're looking at a layer 2 managed ring, all right, with redundancy integrated. It can either be done with copper, or we've also got two SFP ports, which allow us to do it over fiber. And then we're using our PLCnext actually as an edge gateway. So in other words, it's not actually in part of the process. We're using the graphics here of any DCS manufacturer.

19:56
Arnold Offner: Our success so far has been with ABB and Honeywell. We're currently working with companies like Yokogawa and with Siemens on Next. And essentially our PLCnext is really doing what we call the NOA, the NAMUR Open Architecture. So it actually is extracting all the other data that is supposed to then, that is possible... That can be accessed while this process is running. And just to give you an idea, all of these devices are essentially then also push buttons that we have on a demo. I don't have that demo here this week. But essentially it's to give you an idea that all of these devices are essentially IP-driven devices, IP-connected devices. And so we can actually get into all the other information that this device actually has that would otherwise be hidden or not be available real time in a HART or a Fieldbus type application. So what I was gonna do is then just show you where I see this happening. And so I do have an example just to give an idea of where this goes. If you were to take a Coriolis massflow meter, you are probably looking at over 480 seconds in HART to get a downloaded piece of data back from the device. So you send out the command, and now that information comes back. It's gonna chew up a lot of time.

21:11
Arnold Offner: So close to eight minutes. With PROFIBUS, it's gonna take just about three. So about 180 seconds. And then if you're looking at Ethernet APL, this can be done in 10 seconds. And to give an example of how this really works, I wanted to show you an example of how Vega does it. So Vega, and this is a very interesting comparison. You'll notice the cursor moving around here. We're actually trying to connect to a Vega device using HART, while at the same time we're watching an envelope curve here continually being updated every two seconds using APL. So you can imagine the new kinds of business cases and the new kinds of performance categories that could be created in here. And I'm sorry that I dragged this out for two minutes, but you'll notice this bar is still filling up. And so who knows whether the HART information you're ultimately gonna get when that bar closes is actually correct. Because this Vega device on this side using APL has been able to keep tabs on it every two seconds and give you data that is very, very current and very, very accurate. And so, like I said, my comment to my colleagues when I talk about the speed is there's no more time for coffee breaks. People who use HART, I think a lot of them know that whenever you send a HART command, it's always a good time to head to the coffee machine or to go take a bathroom break because you're never sure if it's gonna be done by the time you get back.

22:29
Arnold Offner: All right. And with that, I wanna leave you with a topology that is actually what I see us doing in the future. Phoenix Contact has actually developed an SPE device as well. Some of those first SPE-compatible field devices are now out there. There is a company in Germany called Jumo that's already created three different types of devices, which they demonstrated last year at a microbrewery. So they have an environmental sensor, which in one package over two wires and 1000 meters can actually give us the air quality in here, would give us a CO2 level, and would give us the humidity and temperature. They have another device that does pressure. They have another device that does flow. And then what I wanted to show you here is just the use of Ethernet APL again with a Phoenix Contact product. And all of these devices now could run out 200 meters to APL devices in the field. And so that's why I just want to show you is that we are gonna be part of this discussion moving forward as we essentially take this kind of technology to the edge. What you can also notice, and that's the beauty of a network, is you'll notice we are running a ring structure. We are running another series of Phoenix Contact PROFINET, Modbus TCP, OPC UA, or Ethernet IP type devices.

23:45
Arnold Offner: We can then run them to redundant control systems. And essentially that network now allows us to do all kinds of things. And if you would for a moment just imagine that SCADA could also be Ignition. But I feel Ignition could be also used in other parts of the plant because asset management now becomes very interesting too. In other words, it's up to now the creativity of yourselves as to how you would use Ignition on this backplane here to basically do the things related to the instrumentation here in the field. With that I was gonna just mention, I don't know, is Mark there?

24:22
Mark: Yeah.

24:23
Arnold Offner: Are you ready with the list, Mark?

24:25
Mark: I am.

24:30
Arnold Offner: Okay. Did you bring them with you as well, or are they at the table?

24:30
Mark: I brought them with me.

0:24:33.9
Arnold Offner: Alright. Five minutes, perfect. We've got five more minutes. So Mark is our local sales guy here. Thank you, Mark. Alright. So is Chris Bomarito in the audience? Nope. We'll catch up with you later. Sabrina Rodriguez in the audience?

24:54
Sabrina Rodriguez: Here.

24:54
Arnold Offner: Okay. We have a switch for you, an unmanaged switch. Is Bram Fenter here from Element 8? Nope. Justin Davies from DCI?

25:05
Justin Davies: Right here.

25:05
Arnold Offner: Okay. We have a product for you too. We're getting you a MQTT Modbus protocol converter. Is Dallas Ward from Sierra Controls here? Nope. We'll catch up with him in a moment. And then I'm looking for Ryan Birch from California Resources Corporation. Alright. We'll catch up with him later as well. Thank you. Alright. We'll catch up with you and provide you with all your samples in a moment. And with that, I was gonna let Marcus hand the microphone out to anybody who had any questions. And that leaves us with three minutes. Go ahead. Anybody have any questions? So there, I can go back to the slide. The current companies that produce the APL devices that I showed in the table, and I think there's maybe three or four that have been added to that list, have created an IP-based control system that runs on the two wires.

25:54
Mark: Okay. So...

25:54
Arnold Offner: The switch, in turn, can still, in this current configuration, because there is a project out there right now that everybody's scrambling to get their hands on, the switch that we have also has proxy functionality. So we can substitute, if the APL device is not yet ready, we can use a PROFIBUS PA device of the same type. But if you think about 4-20, if it's a 4-20 device, it probably didn't do much more. If it was a HART device or a Fieldbus device, it probably does more. And so to your question, I would say it's not as much a 4-20 as much as it is more of the sophisticated devices that those field device manufacturers have never really been able to get into the marketplace.

26:32
Arnold Offner: Hope that answers your question. Yeah. If you look at IO-Link, I would say complementary, only because IO-Link is predicated more towards the factory automation space. And IO-Link is actually working in two other spaces still. They are starting to do what they call IO-Link Wireless, and they're also creating what they call IO-Link Safety. Think about IO-Link as truly being something that gets used in the factory automation space, whereas APL and SPE are gonna be covering essentially that entire market space, so both the EX and the non-EX market. So, complementary. Yeah. The only challenge is with three wires, it doesn't tie in very nicely to the two. And I have seen companies already start working on media converters that will convert IO-Link to SPE. But then your challenge still is you're talking about a gateway, and we're trying to eliminate gateways. Because IO-Link is a master-slave type configuration, and so it doesn't really have a great way to connect into Ethernet networks above.

27:38
Audience Member 1: For device manufacturers, do you see a big adoption happening for this on the end devices?

27:43
Arnold Offner: I would say end devices, the adoption is probably gonna come from best-in-class device manufacturers who have always had a lot more intelligence inside the device. So if you looked at that name, you're probably looking at really high-end devices that these companies produce. I think the challenge in the SPE space is think about it more of being a combination of devices just over two wires. Because what I probably forgot to mention is that over my 1000 meters at 10 megabits a second, we're also pushing out power. So we're doing the same thing we do with 4-20, but we are actually sending out power. And those power categories are then also defined. I don't want to go into too much of the weeds on that, but essentially it's a powered two-wire system.

28:23
Audience Member 1: So outside the working group, obviously they're adopting, they're part of it, but do you see other companies looking at it, asking about it, trying to get involved?

28:32
Arnold Offner: Yes, yes. And like I said, they are then working through their standards development organizations. So in the PROFINET space, currently in the Ethernet IP space, they've already created something called a constrained in-cabinet type technique, also using single-pair Ethernet. And so you're slowly but surely gonna see more of those companies step up and develop that kind of thing. Yes. Well, thank you very much for taking the time. I really appreciate it. I want to wish you a wonderful rest of the day, safe travels back home. And it's been nice meeting all of you. Thank you.

Learn how process manufacturers are leveraging the power of SafetyChain & Ignition to drive meaningful value in their production environments. We’ll cover how manufacturers benefit from seamlessly connected systems and the broader impact that has on various segments of their operations. You’ll hear about a case study where thousands of data points derived from a complex manufacturing process were leveraged to drastically improve quality and production metrics. Finally, we will showcase how easy it is for manufacturers to connect SafetyChain and Ignition with a live demo.

Transcript:

00:01
Geoff Nelson: Glad you're here. Appreciate your time here to talk to us. We are here to talk to you about SafetyChain and our Ignition Module to help capture real-time data for a digital plant management system. My name is Geoff Nelson, I am the VP of Technical Solutions for SafetyChain Software. This is Jonathan.

00:21
Jonathan: Hello, everyone. Welcome. Thank you for joining us today. I've been with SafetyChain a little over three years working as a Solution Engineer. But I primarily come from the food and beverage manufacturing industry. I spent over a decade working in a plant and SafetyChain is a plant management platform. So, I'm really excited to talk to you guys about the value that SafetyChain can bring and how we can leverage the Ignition Module.

00:49
Geoff Nelson: So, let's get into it. So, we will talk about SafetyChain, we'll give you some of our key applications where we kinda hit the plant management, plant floor, talk about digital transformation which I'm sure you're all pretty familiar with, give you a customer success story and then go into a demo. So, we'll try to get through these kinda quick so we can show you a demo and leave time for questions at the end. So, we are a digital plant management platform. We're a SaaS solution hosted in Microsoft Azure, we have native applications for Android, iOS and Windows and we help kinda pull everything together, the glue for the digital plant management platform. We are an alliance partner here with Inductive Automation and we will show you our module that we have.

01:35
Jonathan: All right. So, yeah, as Geoff's kinda said, we bring everything together. I like to think of us as kinda like a one-stop shop when it comes to plant management. And as you can see, everything here listed, these are some of the key use cases and applications that a lot of our customers use as and leverage in manufacturing. I'm not gonna go through the whole list, but we touch your whole process from shipping and receiving all the way to getting your product out the door. And primarily, we've come up in the food and beverage space, but we have had other applications outside of that. Now, as it relates to the Ignition Module, that specifically focuses on how we're capturing data for our customers.

02:13
Jonathan: So, with the Ignition Module, we can capture any data that's already mapped to their Ignition Gateway in SafetyChain. And SafetyChain is already a pre-built solution for you to extrapolate your data. You can aggregate that, graph it, trend it as you need. We could take for an example, temperature logs here listed right here. Instead of having a maintenance tech or operator go in and take hourly required check and write that down and put it away in a folder or binder, SafetyChain helps you digitize that process and take it a step further by automating it. So, with the module, we could set off a trigger where we're capturing that specific data tag on a specific routine or basis, or if there's a condition that needs to be met, we can trigger it as well. We have multiple ways of triggering that data collection point.

03:11
Geoff Nelson: So, like Jonathan said, these are the key areas of impact, what we do, it's pretty customizable. And so, you can build really your own process out within SafetyChain. And then he's highlighted here these blue ones as real-time, maybe ones that resonate more through Ignition. But then you can bring this data in and it can live next to all of these other impact areas as well.

03:36
Jonathan: So, again, I talked about my time in the plant. This slide kind of really illustrates the process around capturing data and using that data to further your continuous improvement efforts. SafetyChain is basically gonna help you do that and then the module's gonna help you also automate that. So, in SafetyChain, primarily you could collect data via a workstation or tablet. So, we're device-agnostic. You can use a Windows workstation, you can use an Android or iOS tablet. Typically, it's operators entering checks or maintenance guys entering their work orders, things of that nature. But you can also trend and track that data and find your opportunities for improvement, find your opportunities to save time and waste and then you gather insights and you act on that data. And as you're acting on that data, as I said, you're pushing your continuous improvement and you're pushing the bottom line so that ultimately you're growing as a company. That's what we try to help our customers and try to generate those success stories from helping them leverage that data.

04:41
Geoff Nelson: So, whether you're coming from paper and we're helping you create a digital process or you already have data being collected and you're just going to multi-site networked cloud solution, we help you come to ask questions that you didn't even realize you had because you're doing that CI, that continuous improvement, on your processes and on your data. So, I'm gonna tell you a little story about Egglife. So, I don't know who here is familiar with Egglife. They make the tortilla alternative out of egg so you can have tortillas that are made from egg. They took the Ignition Modules. They already were using SafetyChain, they had gone from a paper process to a digital process on their tablets. So, they're using tablets to gather information, they're gathering downtime, dwell time, temperatures, all sorts of information within SafetyChain and already performing analytics. Then, they moved to the Ignition Module because all of that data was available within Ignition but they still needed to collect the data for auditability, for compliance and for audits that come in. Now, they took about 12 manual processes. They had people going up to the machines or going up to the HMIs and collecting this data in a tablet.

05:55
Geoff Nelson: They moved it over to the Ignition Module and all this data's still being captured but in an automated way. So, they took 12 processes and automated them. So, that's people, that's time now that people aren't having to go walk up with a tablet and it's all within SafetyChain and they can still perform their analytics. It's all in the cloud and it's all stored long-term. So, an opportunity there for them to save time, save money. And then now, they can use those operators really to do something else more valuable than looking at a screen and collecting data. All right, now we're gonna jump into the demo. So, bear with me just for a second here. Okay. So, I am bringing up the module first and then we'll jump into SafetyChain. So, this is just an Ignition Gateway here which I'm sure you guys are all familiar with. We have a module that can be installed and it puts this SafetyChain piece here at the bottom. It's really easy, I mean, a few clicks to install a module and then you get your connections, your Form Collectors, your OEE Collectors and your Tag Collectors.

07:01
Geoff Nelson: This allows you to really grab any data that Ignition has access to and then put it into SafetyChain in different ways. So, I'm showing a Form Collector here and it'll make more sense when we start showing SafetyChain in a moment because we'll show you our Demo 1 tenant. I'm just gonna go into the kettle temps here and just show it to you real quick. And I am using this connection here at this site and connecting to a VM, so might be a little bit slow here. When this comes up, it gives you a user interface that allows for configuration to create an integration between Ignition and SafetyChain. So, Ignition has view into what SafetyChain data exists. So, we call these Forms. So, a person might be entering, writing on a piece of paper what their kettle temps are and then so we digitize that into a digital form within SafetyChain and then Ignition gets access to that. So, a user could come in here and access all of the forms that exist within SafetyChain, pull it into Ignition, set up a trigger, so when do I wanna send this data to SafetyChain? Do I want to do it time-based, every five minutes, every one minute? Do I wanna do it tag-based? So, if a temperature exceeds a certain value, does the dwell time exceed a certain value?

08:20
Geoff Nelson: Send this information to SafetyChain, there're different ways to do it. Do I wanna do it manually so you can actually script this execution? You can put it into a button and perspective revision into a screen, and then you map each of the fields. So, I can have my Kettle Temp 1, 2 and 3. I have which line is it coming off of. Average is a calculated value within SafetyChain, so I don't have to send it. The temps, the tags, the fields within SafetyChain have different sources. So, you can choose a tag, a static value, an expression. You can choose a data source which allows you to go to any data source that Ignition has access to. So, if you have a SqlConnection or something, you can then pump that data directly here through configuration. So, it allows you to really take, like we said, any of the data that Ignition has access to, package it and send it to SafetyChain. I'll show you one more. So, what this does is it pulls the SafetyChain context into Ignition. So, Ignition knows how to talk SafetyChain language. The other option that we have are tag and OEE Collectors which really just says, "Hey, give SafetyChain the tag," and then it will deal with it.

09:34
Geoff Nelson: So, here, it's not talking SafetyChain language, we're just sending, okay, this tag goes to SafetyChain and it is your in count or it is your out count so that SafetyChain can then track your downtime, it can track your throughput, your productivity. All we need to know is the tag, just send us the tag and we'll do the rest. So, in this context, all the business logic is in SafetyChain. In the Form Collector, the business logic is basically in Ignition but it allows you to really do the integration in whichever way is needed.

10:02
Jonathan: Yeah. And then we can visualize that. Once we have that data and we've set up all the configuration on the back end on the SafetyChain side, you can then see that visualization and reporting of your OEE and we're going to demonstrate that a little later as well.

10:15
Geoff Nelson: So, that's what we'll jump to now. So, that was the Ignition Module. So now, what does that look like in SafetyChain? So, this is what we call our reporting or our grid screen. It's just one click from the homepage to get here. And now, we can quickly start to see and visualize the data. So, all the data that comes in, whether it's from Ignition, from a user on their tablet or on their phone, on the PC app or even a web-based browser interface, they can put their data within SafetyChain and it all here lives together. So, if you wanna perform analytics, deep dive into the data, you can have your automated data right next to your manually collected data and start to make decisions. Once you come in and start to look at your data, so it looks like I am here looking really at our kettle temps. You can also start to then perform actions. So, you can create tasks to assign to users. So, for follow-up, you can trigger notifications. So, if this is out of compliance, you can also do verifications. So, you can create your own sign-offs and verifications within the system.

11:23
Geoff Nelson: So, if you're doing data verification, pre-shipment review, that all is done within SafetyChain. So, you can have your processes built out and start to see the digital plant management part of it. So, I'll just show here the verify and I don't know, Jonathan, this is your site more than mine. Is this data verifiable?

11:44
Jonathan: Yeah, for sure.

11:45
Geoff Nelson: Well, you see here, so we had Sign-off, Record Review, FS Coordinator and Pre-shipment Review. So, those are verifications that have been built into the system, it's just all configurable and this data then can be verified and it's all tracked historically, so who did what when is not alterable. So, a person would come in here, so I would be here with my user, I would go verify these. So, I'd select the ones that I wanna verify, I'd sign them and I would put my note and then all that's tracked historically and so all these... So, those records have been verified for that verification that I picked. Do you want to jump in here a little more...

12:26
Jonathan: Sure, yeah. While I'm doing that, as I said, I worked prior to SafetyChain in food and beverage space. How many people here have been a part of an audit before? Raise your hand if you've been a part of an audit. Was that fun as far as like getting prepared and...

12:49
Geoff Nelson: No.

12:49
Jonathan: No? Yes?

12:51
Geoff Nelson: Audits and fun.

12:52
Jonathan: I like to do audits on the weekends maybe. Yeah. So, one of SafetyChain's big claim to fame would be having our customers become 24/7 audit-ready. And I'm gonna show you our Programs feature as soon as I remember where the link is. Here we are. And yeah, I've been a part of a few audits myself prior to going through digital transformation. So, we're talking filing cabinets, we're talking binders, we're talking going through old emails and work orders, it can be a headache and it's usually across a few days. So, when I came to SafetyChain, I learned about our Programs feature. It really resonated with me coming from industry and I'm like, "I wish I had this back when I was on the other side of the desk." So, what SafetyChain can do, as Geoff said, is we do a lot of customization of our forms so that you can capture those and you have record and documentation of that for future purposes. You can link those back to your food safety or internal program and be able to be audit-ready at any notice. So, if you have multiple clauses, we'll look at our HACCP one right here.

14:18
Jonathan: I like to think of these as kinda like those binders but in digital form. You can see all of your forms that have been linked to that specific program so that if the auditor was to come in and say, "Hey, I need to see records from this date to this date for this specific clause," it's right there at a few clicks of your fingertips. So, you can see all the records, you can see all of your documentation, so that means any SOPs or work orders and instructions that you have already listed specific to those clauses and that program, you can put that in there and it's customizable. So, we're not just doing food safety, we're not just doing SQF or HACCP in this case, but we can do an internal program that's specific to your specific company guidelines. So, if you have an EHS program or safety program, if you have maybe a GMP audit that you do internally, you can set that all up and have that traceability in there as well.

15:14
Geoff Nelson: You could do, like he said, internal binders or maybe customer or auditor ones. So, if you build one specific to what an auditor might look for, you can do it that way. And instead of having a piece of paper or a single physical drawer or location, these digital binders or programs, you can have multiple assignments. So, that form that we looked at like the kettle temps or any of those ones that we build out can belong to multiple programs and it's just at that form level so then any of the data that comes in will go to all these. So, if you filter for... If it's in Master Sanitation and it's in Food Standard 9, the data will all exist there without further mapping. So, there's nothing you have to do after the initial configuration.

15:54
Jonathan: Right. So, as far as all of the prep work, you do most of the lift up front when you're doing your configuration, setting up your forms, storing your documents and then from there, as you're collecting your data, as you're going through your typical everyday work processes, it's automatically going to its right place as related to your program. So, these are just a couple examples in our demo environment. As you can see, you got your docs, your forms and then your records for a given time. You can go out longer. So, this is the date and time filter at the top. So, if you wanted to go back three months, you could do that and you'd have even more records there. Yeah. So, here we go with the same HACCP one that we were looking at. It's got 492 records and so if an auditor was to come here, walk in today and say, "I need to see your HACCP records," I can pull that up pretty easily. Should I go into OEE now?

17:00
Geoff Nelson: Yeah, let's do it.

17:00
Jonathan: All right. So, another one that's near and dear to my heart would be around line efficiency and OEE tracking. I spent some time as a production manager, so knowing how the lines are running on a given day, basis, knowing where your opportunity is to reduce downtime is a very big deal especially in the manufacturing space. And that's where our OEE module comes into play. So, with the Ignition Module, as Geoff said, we have the OEE collector and we can map those tags back to our OEE solution so that we can generate this right here. This is one of our main screens here, this is live monitoring. So, in real time, we're capturing those tags and the counts from the machines coming from the line and we could tell whether the line is up or down, we could tell how fast it's running and we could tell if we've made our plan for today or where we're at in regards to what we were scheduled to produce. So, very impactful.

18:02
Jonathan: We have different screens, we could look at a more abbreviated version as well where you don't see the graph and you just can see at a high level. It's green, that means it's running. If it's red, it's down. You can see what your current rate is, obviously, what your total downtime is right there and what your current OEE is for that specific run.

18:21
Geoff Nelson: And here, we're looking at a single line but this is made for a multi-line, even multi-site so you can look across locations, built for scalability to look. Yep, here we go. So, he's showing two lines now. And so in the slim view, you might look at multiple... There's different views even to make them even smaller. But you might put it up on a screen down at the plant floor, pull it up in your office, put it up on your phone at a different site to get you visibility into how you're performing. Are you currently down? Why were you down? Why are you not meeting your goals?

18:54
Jonathan: Right. Yeah, this is a lot more lines here now. So, yeah, this view kinda... I'd say like the supervisor, manager/operator view, so you can see specifically what's going on on your production floor from an OEE standpoint. And then from a reporting standpoint, we have some out-of-the-box reporting as well where you can focus in on how you're doing as a plant but also if you were looking at an enterprise view, how you're doing across all of your plants. As Geoff said, we're very scalable. So, if you had multiple plants, you could see how specific SKU was running across your different plants if they shared SKUs. This is the enterprise view right here. I need to go out in more time to skip data.

19:56
Jonathan: Here we are. So, you could see how each location is behaving, you could see how your shifts are trending, if you have one shift that's doing a little better than others, graveyard shift might be taking breaks when they're not supposed to, get your OEE by line and then also by SKU down here. And then another good one is our top five reasons like Pareto. So, figuring out where your biggest opportunities are from a downtime at the source and reason level. And then, we also have some customizable reporting as well in our report builder. So, even if you don't see exactly what you want here, odds are you can use the raw data to build that in SafetyChain as well. So, we have customers that wanna see something specific or specific tables, they're able to build that with the raw data that's being collected via the tags. All right, we are about 20 minutes in. Do you think we should take questions now or is there something else you wanted to show?

21:08
Geoff Nelson: Let's show... Can you show SPC real quick?

21:11
Jonathan: Oh, yeah... I'll let you do it.

21:13
Geoff Nelson: You know the data though, right?

21:15
Jonathan: You talking about the Ignition?

21:17
Geoff Nelson: Yeah.

21:18
Jonathan: Okay. Let me...

21:20
Geoff Nelson: So, like he's saying, this is all out-of-the-box functionality and we do have report builders so you can make customized reports and dashboards. Most of our system, almost everything also can be done through API too, so you can pull your data out into other systems. The Ignition Module allows those screens that we were just showing to be set up really within minutes with a couple of tags per line to get your in count, your out count or even just your in count will drive a lot of those screens. What he's pulling up now is an SPC dashboard just to show a little bit more analytics to the data that we pull in. Was there not one on the main screen?

22:03
Jonathan: I'm not seeing the ones that I built, but I'll probably use one of these other ones.

22:07
Geoff Nelson: This is our demo site like Jonathan said. So, we use... A lot of people use this site for a lot of different reasons and it may look a little different from time to time depending on maybe who we're demoing to. So, he's searching a little bit. I typically don't go in here, Jonathan does a little bit more than I do.

22:23
Jonathan: With my login, though.

22:25
Geoff Nelson: Oh, right, yeah. This is my login.

22:28
Jonathan: Let me change the secure profile.

22:30
Geoff Nelson: I don't know why my browser's doing that, that's weird. So, as you can tell, this is a part we didn't rehearse, guys. But you saw that chart before. We have a lot of out-of-the-box charts for your data to start populating. Is there one here? Hold on a second, this mouse works. Does this one work?

23:01
Jonathan: I haven't seen that one...

23:05
Geoff Nelson: Well, this is what I get for doing this. But you can build SPC charts that will show up on a dashboard. You can also have ones that will show up on the tablets. So, when a user's entering their data, as soon as they hit submit on the form, it'll pop up the SPC chart to show you how data has been doing across the line or the shift or the day and it could be paired with the Ignition data too. So, if you wanted them to be paired, they could be paired. And then what we're trying to show here too is kinda the plant management piece. We showed you verifications on your data, we show all the data that exists, the forms you can create. Those are all customizable. We also have ones that are kind of what you see over and over again like our OEE and production ones. Those are pretty basic. I mean, they're kind of a template or standard that we do over and over again. We showed you programs so you can collect your data and be audit-ready. We showed you the OEE and productivity screens and... Oh, here we go.

24:09
Jonathan: This is what I was looking for. Okay.

24:10
Geoff Nelson: This is what he was looking for and some SPC charts so the data can come in, you can be looking at your control limits. So, we have compliance, whether a value is in or out of compliance, so pass or fail and then we also have SPC control limits which are different. Are you in control for your process? We have alarming and alerting for different rule violations. So, you can see here the different rules you might violate. This data looks pretty good, so it's not really violating anything. A little bit crazy stuff. But a lot of out-of-the-box SPC charts, some reports and then you can build your own, customize like Jonathan said. So, with that, I think we will turn over for any questions. Yeah, back there.

24:51
Audience Member 1: First question, how does the licensing work on the module?

25:00
Geoff Nelson: Good question. Adam, do you wanna answer that? No. The module itself in the showcase is free. So, the module itself is free. And then in SafetyChain, we build into the licensing. We license by location, not by user. So, a specific location can have as many users. And then whatever you're purchasing is kinda how we do the cost. So, integrations typically has a cost to it. I think right now we're doing a deal on the IoT piece. Is that right, Adam?

25:27
Adam: Yep. Correct.

25:28
Geoff Nelson: So, if you... Till the end of the year, for now, I think it's a year free on the IoT piece. So, you would just be paying for SafetyChain on a per-location basis.

25:38
Geoff Nelson: Right now, our Ignition Module is sending data from Ignition to SafetyChain. We are frequently enhancing it, but we do not do bidirectional in the module. However, we do have APIs that can do just about anything. So, if you wanted to customize some work, you could pull any data down, record data, you could do tasks, really just anything. Not native embedding of a specific chart but this is all web-based. So, if you could embed a web page or like a browser framed, you could do that. But otherwise, the charts won't embed themselves. No. Was there a question over here? Yeah.

26:15
Geoff Nelson: So, your question was, basically can another system trigger events within SafetyChain? Is that right? The answer is yes, it can. And there are two ways really to do that. One, like I said, we have APIs that can do just about anything and you could call our either Task or Record API to create actions in SafetyChain. So, you could assign a task to a person to go do some work based on whatever other system was doing. The second one is, through Ignition, you could create a record in SafetyChain and that record could be tied to what we call a dynamic flow that says, "Hey, go do another thing." So, based on whatever you send us, we configure in SafetyChain somebody else to do whatever the work is. So, depending on whatever your use case is. So, yeah, you could definitely do that.

26:57
Geoff Nelson: Are the forms dynamic? Absolutely. Yeah, they're dynamic, customizable. So, you create your own from scratch. You can have fields that are hidden and dependent on values of previous fields. So, it's very customizable and dynamic. Yeah. Are the forms developed by a developer? No. So, it is a user interface where a power user would go in and create their form. Really the requirement there would be on change management, so deciding who has the power to go create forms. Because once you release it, that's it, everybody gets it. So, if you cause a problem or something that users didn't expect, then you'll hear about it. But yeah, it's a user interface for you to drag and drop fields and configure them. Yeah.

27:36
Geoff Nelson: Is there an enterprise piece? Yeah. So, that goes with how you wanna do your roles and permissions. So, you can choose a certain level of user that has access to edit and create forms and then nobody else has access. So, at an enterprise level, you could say, yeah, this is a group that we've created, maybe you pick a person per site or a region or however you wanna manage it and then... Yes, then they would be able to edit. And then you could even have a different set that can release them which means now that people can go use them.

28:02
Geoff Nelson: Good question. So, in the downtime, reasons are configurable. So, you would configure them in SafetyChain, so which options you have available to you and then users can come into that screen that we showed and just select the reason for it. So, you can do a category, you can do a source then you can do a reason.

28:17
Jonathan: Right. And there's a free text portion as well if you need to add more information and detail.

28:22
Audience Member 2: You said you were getting that... Does your tag fill that out?

28:26
Geoff Nelson: You can in our downtime tracking with our automated downtime tracking, you can do that. Yeah. And I think we're just about out of time here. Was there one more back there? Yeah.

28:35
Audience Member 3: Does it have access to if a user enroll info from like Azure Active Directory or Ignition?

28:44
Geoff Nelson: We do have SSO available. It's SAML 2 or OpenID Connect is what we support. So, yeah, Azure, Okta. I mean, just about any of them. Yeah. Last one here. Last one.

28:55
Audience Member 4: So, you said you have these apps, mobile app as well. So, if we are performing audits and on the shop floor, there's no internet connectivity, do we have like saving in offline...

29:04
Geoff Nelson: We do have offline mode and then when connection's restored, it will push back up. Yeah. So, on those native apps, it's offline mode. So, when you go down, it'll store it. Okay. I think that's all the time we have here. Thanks, everybody.

29:14
Jonathan: Thank you, everyone.