Inductive Automation

  • Turn any device into a Human Machine Interface.
  • Provide automated reports linked with the power of Advanced Analytics.
  • Bring operator awareness for currently orphaned edge devices.
  • We can turn any device into a Human Machine Interface.
  • Provide automated reports linked with the power of Advanced Analytics.
  • Bring operator awareness for currently orphaned edge devices.

Consulting Services for Ignition

Ignition allows you to seamlessly collect all your data, design any kind of industrial application with ease and instantly web-deploy clients to anyone, anywhere.

We offer initial and on-demand services to empower the user with the knowledge required to effectively utilize this powerful industrial platform.

Why Work With NZ Controls

Team of over 30 engineers

Ignition by Inductive Automation

Certified alliance partners

We see our customers as partners

Ignition Architecture

With Ignition, you can instantly launch an unlimited number of zero-install, full runtime clients on virtually any device. We have the knowledge and experience to distribute your Central Ignition Gateway across one or several servers which can be physical or in the cloud, or both. View the common Ignition Architectures we support below, all options except IIoT offer redundancy:

Ignition Standard Architecture

The standard architecture allows your SCADA sytem to be centrally managed using only one Ignition server and the required modules for your needs. You only pay for one license that has unlimited connections, tags, databases and web-deployable clients.

Ignition Scale-Out Architecture

The scale-out architecture ensures the workload is balanced between I/O Gateways that handle device data and front-end Gateways that handle client applications. This architecture enables the scaling out while ensuring no overloading of any single Gateway.

Ignition Hub & Spoke Architecture

The hub and spoke architecture consists of two pieces. The hub is a central Ignition Gateway that includes Vision, Reporting, Mobile Modules, and a database server. The spoke is a stripped-down Ignition Gateway with OPC UA and SQL Bridge Modules, dedicated for data logging. Each site operates with its own history, alarms, and clients; the client Gateway is used for coordination and long-term historization.

Ignition Enterprise Architecture

The Ignition enterprise architecture secures data at multiple levels while enabling the creation of a connected system. Ignition Edge is used to ensure data from critical assets is never compromised and a central corporate server to multiple sites. For an additional layer of security, connecting through a DMZ ensures secure access and transferring of data. The Ignition Gateway connects easily to cloud services like Amazon Web Services, Microsoft Azure, IBM Cloud, and Google Cloud for storage and analytics.

Ignition IIoT Architecture

Ignition IIoT can collect data from any device at the edge of the network, publish that data to a central broker, and push that data to subscribed industrial and line-of-business applications. Ignition IIoT can connect to PLCs in the field through the use of the MQTT Transmission module, field devices with Ignition Edge MQTT installed, and/or MQTT-enabled edge gateways and field devices that use the Cirrus Link Sparkplug MQTT specification. This data is published to an MQTT broker, which can be located physically on-premise, in the cloud, or a combination of the two. The MQTT Engine module located on an Ignition Gateway can subscribe to any data published from the broker, which can then be used in any Ignition application.

Ignition Standard Architecture

The standard architecture allows your SCADA sytem to be centrally managed using only one Ignition server and the required modules for your needs. You only pay for one license that has unlimited connections, tags, databases and web-deployable clients.

Ignition Scale-Out Architecture

The scale-out architecture ensures the workload is balanced between I/O Gateways that handle device data and front-end Gateways that handle client applications. This architecture enables the scaling out while ensuring no overloading of any single Gateway.

Ignition Hub & Spoke Architecture

The hub and spoke architecture consists of two pieces. The hub is a central Ignition Gateway that includes Vision, Reporting, Mobile Modules, and a database server. The spoke is a stripped-down Ignition Gateway with OPC UA and SQL Bridge Modules, dedicated for data logging. Each site operates with its own history, alarms, and clients; the client Gateway is used for coordination and long-term historization.

Ignition Enterprise Architecture

The Ignition enterprise architecture secures data at multiple levels while enabling the creation of a connected system. Ignition Edge is used to ensure data from critical assets is never compromised and a central corporate server to multiple sites. For an additional layer of security, connecting through a DMZ ensures secure access and transferring of data. The Ignition Gateway connects easily to cloud services like Amazon Web Services, Microsoft Azure, IBM Cloud, and Google Cloud for storage and analytics.

Ignition IIoT Architecture

Ignition IIoT can collect data from any device at the edge of the network, publish that data to a central broker, and push that data to subscribed industrial and line-of-business applications. Ignition IIoT can connect to PLCs in the field through the use of the MQTT Transmission module, field devices with Ignition Edge MQTT installed, and/or MQTT-enabled edge gateways and field devices that use the Cirrus Link Sparkplug MQTT specification. This data is published to an MQTT broker, which can be located physically on-premise, in the cloud, or a combination of the two. The MQTT Engine module located on an Ignition Gateway can subscribe to any data published from the broker, which can then be used in any Ignition application.

Contact

AUCKLAND

89 Carbine Rd
Mt Wellington
Auckland
New Zealand

TAURANGA

1065 Cameron Rd
Tauranga
New Zealand