ignition architectures

• Basic
• w/ redundancy

• Basic

  

  

• w/ redundancy

  

  

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

With the scale-out architecture, the workload is split between I/O gateways that handle device data and front-end gateways that process data for 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 & Spoke architecture consists of one Ignition Gateway (Hub) that is connected to several local or remote networks (Spoke).

The Hub 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.

Each local as well as remote network is fully independent, operating with its own history, alarms and clients, with the client gateway being used for coordination and long-term history storage.

Connect multiple sites – local as well as remote (e.g. plants anywhere in the world) – to a central corporate server to create a secure interconnected system.

• Basic
• w/ redundancy

• Basic

  

  

• w/ redundancy

  

  

This architecture enables you to collect data from any device and send it to the main MQTT Broker. It is this MQTT Broker that the Ignition server is connected to. MQTT Broker data can be read out and processed by a whole range of software applications. Apart from reading out data, these applications can send (i.e. publish) data to the MQTT Broker.

For reading data from MQTT devices, you can use the MQTT Transmission Module or Ignition Edge.