Ignition architecture considerations

Ignition
1

We're planning to deploy Ignition and Edge to some remote sites, probably with a hub-and-spoke type architecture. I'm trying to work through some of the potential issues.

Is there an advantage to adding an MQTT broker to the mix? I had been planning to create a gateway connection for each to the main Ignition gateway and use the Edge Sync Settings to sync the Edge historian to the main server.

Should I be creating a tag historian for each site? Or maybe all the remote sites should use one, or maybe everyone just uses the already existing one for the central server. Each site will get it's own data table since they'll have different gateway and tag provider names.

Any advice on anything else I should be thinking about?

2

What types of connections are the remote sites? If bandwidth isn't an issue I'd just do the Edge Sync on gateway network connections. If you have the remote sites on cellular networks then MQTT would be beneficial to save on bandwidth. You might check out EAM also if you're going to have standard components used on all sites and to coordinate backups and upgrades.