Call Us 1-800-266-7798  |  Schedule a Demo

International Distributors

Resources / videos

Ease of Project Design

Ignition Customer Testimonial

3 min video  /  1 minute read
 

Automation and System Engineers from different industries share how easy it is to design in Ignition and create a solution to meet any industrial process. "You can really get any kind of customization you want out of Ignition." — John Furby, Automation Engineer - Chobani

Learn more about Developing in Ignition

Posted on February 15, 2019

You Might Also Like

customer project Food and Beverage

Data from Numerous Processes Aids Large Salmon Producer

This project has been developed by employees at the automation department of Nordlaks Produkter AS for the Nordlaks group. The project consists of several departments where operators can control entire processes and managers can extract information and data all the way down to the component level.

8 min video

Watch the customer project
article Guide

Checklist: Avoid Common Project Mistakes in Data Collection, HMI Design & Scripting

It’s easy to make mistakes. We’ve all done it! Sometimes we complete a task in an inefficient or overly complex way. Other times we only discover a mistake after the fateful copy/paste that breaks an entire screen. Luckily, with Ignition it’s just as easy to fix mistakes and in the process create reusable assets that save development time. Below, we’ve compiled a checklist to help you avoid common mistakes and make your project as efficient as possible.

Read the guide
customer project Construction Materials

Creating Tag Tools in Ignition for Porting From Other SCADA Platforms

The client is Continental Cement, a continuous-process cement plant located in Hannibal, Missouri. The project involved porting a Citect SCADA platform project based on TOP Server as the OPC server. The Citect system is a legacy system with various iterations enhanced over time by various parties. Each party had their own methodology, naming conventions, and standards for graphic objects. The goal of the port was to move the entire legacy system to Ignition, and, as part of the process, normalize the tag tree and naming conventions with uniform HMI navigation behavior. As there was no overall documentation for the legacy system, the port consisted of reverse-engineering the entire Citect system. Due to this, for functional validation to be effective, the ‘new’ Ignition windows had to contain graphics objects with a look, window placement, and behavior equivalent to the Citect system.

5 min video

Watch the customer project
✕