Presentation by Angelo Marguglio
Research Area Manager and Head of the “Smart Industry and Agrifood” Unit, Engineering Ingegneria Informatica SpA
FIWARE Global Summit
21-22 May 2019 - Genoa, Italy
8. Why OPC UA?
Any product being advertised as “Industrie 4.0-enabled”
must be OPC UA-capable.
OPC UA is the de facto standard
for the automation market and Industrie 4.0.
OPC UA
Open Platform Communication
Unified Architecture
12. Current adoptions
Published into IoT
Agents catalogue
(IDAS)
Version 1.3.0
released date
May 2019
Integrated with
FogFlow by
HOPU
Integrated with
MASAI by ATOS
Validated at
POLIMI in a real
scenario (Digital
Twin for Energy)
Tested in
ENGINEERING
premises
Incubated since
FIWARE 7.4
release
14. Smart Factory Scenario – Didactic Factory
7 Stations
ActivePowerL1
Flow
Pressure
Busy
RFIDTagPresent
Done
ReadyAtStationxBG1
StationEntryxBG5
StationExitxBG6
OrderNo
…
ENERGY OPC UA DATA
MES OPC UA DATA
14 OPC UA Servers
16. Experiments results
Goal: Enable multi-domain data integration,
harmonization and multi-device interoperability
Target customers: Smart Industries, Facility
Management Companies
Main features:
• Register any machines and servers (e.g. OPC UA)
• Harmonize data in NGSI FIWARE Data models
• Command machines and monitor their status
through user friendly dashboards
17. Conclusions
Normally accessing OPC UA data is quite complex...
• Define subscriptions for each consumer
• Define monitored items
• Read data as an array of “Variants,” address via indices
• Use untyped API’s...
With FIWARE it is simple!
• Deploy and start the IoT Agent for OPC UA
• Define the data-types mapping
• List and map the OPC UA monitored items in the conf file
• Use IDAS/OCB API to subscribe to the OPC UA address space (saving OPC UA sessions)
• Send commands to OPC UA devices/servers