ignition architectures

• Basic
• w/ redundancy

• Basic

  

  

• w/ redundancy

  

  

The standard architecture is best suited for applications that require a scalable, centrally managed SCADA system using only one on-premise Ignition server and select modules. This implementation is the most cost-effective setup since you only pay for one license to have unlimited connections, tags, databases and web-deployable clients.

With the scale-out architecture, the workload is split between tags and I/O Gateways that handle device data and front-end Gateways that handle client applications. This architecture scales out easily without overloading any single Gateway.

• Basic
• w/ redundancy

• Basic

  

  

• w/ redundancy

  

  

• Basic
• w/ redundancy

• Basic

  

  

• w/ redundancy

  

  

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

The Ignition Enterprise Architecture enables you to create a connected system while also securing data at multiple levels. Connect multiple sites to a central corporate server, and use Ignition Edge to ensure data from critical assets is never compromised.

• Basic
• w/ redundancy

• Basic

  

  

• w/ redundancy

  

  

Ignition IIoT can collect data from any devices 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. This broker can be located on-premise, in the cloud, or a hybrid of the two. The MQTT Engine module located on an Ignition Gateway can subscribe to any data published from the broker. This data can be used in any Ignition application.