Ignition SCADA and MES Integrator in Australia

Ignition covers SCADA screens, alarming, historian, reporting and integration from one gateway, with data stored in standard SQL databases. That makes it a practical base for plants that want the control room and the production data on the same platform, and for MES functions that grow out of SCADA rather than sitting beside it.

• SCADA and HMI in Perspective or Vision, designed to ISA-101 principles with clear process context and alarm handling.
• Historian and SQL data models for process, production and quality records.
• OEE, downtime and production reporting read from PLC states.
• MES functions such as order tracking, lot records and ERP posting, built on SQL or MES modules where they fit.
• Integration with CMMS, ERP and third-party OEE platforms.
• MQTT and edge data collection for condition monitoring and remote assets.

Most Ignition work in established plants replaces an older SCADA or a set of standalone HMIs. We audit the existing tags, alarms, screens and scripts first, decide what to carry over and what to retire, and build the Ignition tag model with user-defined types so each machine type is engineered once. Cutover is staged by area or line, often with the old and new systems running side by side until operators have signed off. On the McCormick CIP migration, the move to Ignition was planned and executed to keep production running throughout. Where the controllers are also due for replacement, the SCADA migration is planned alongside the automation upgrades so each shutdown is used once.

Ignition is licensed by the server rather than by tag or client, and since 2023 it has been sold and supported locally by Inductive Automation Australia. We help sites choose the gateway licences and modules they need for the scope, and we support Ignition systems after handover under automation support agreements, including systems another integrator originally built after an initial audit of the gateway, projects and backups.