I think it is usefull to add a native MQTT client to Plant SCADA.
Guest
|
Idea business value
MQTT is used more and more to send data to higher level platforms and also back. This will make communications to and from other plants or sites much easier. |
|
| Idea priority | 4 – Important to my company |
@Nathan another thread https://products.feedback.aveva.com/ideas/SCADA-I-12
said there was a solution using an Operations Control Supervisory subscription or an add on licensed driver for us perpetual license folks.
If a customer requires MQTT, this year, for data into SCADA and data out of SCADA what is the "recommended" solution until the OI Server is developed?
Is there a "target" release date for the OI Server solution you mentioned for Plant SCADA?
Yes please native MQTT driver! And it has to implement Sparkplug. See the implementation in the latest version of Geo SCADA.
But I also want to add: It is not only about getting data into Plant SCADA from a remote devices. It is also about publishing data from Plant SCADA back into the broker, for consumption by other software - MES, ERP, etc.
See 4.0 Solutions' videos on Youtube, regarding Unified Namespace, and how they use Ignition.
Plant SCADA Is looking to incorporate the AVEVA Communications Drivers (OI Servers) as a Data Acquisition Engine directly into the Plant SCADA IO Server for processing. The OI Servers already support MQTT & MQTT Sparkplug B. Can use this utility today, and push the data into Plant SCADA via OPC until this is built.
duplicate of https://aveva.aha.io/ideas/SCADA-I-12