Automatic meters (SCADA)

Equipment meters (running hours, starts, cycles) can be fed automatically from the control system, without manual entry, and raise alerts when a threshold is exceeded.

Two modes depending on the network

• Files (no direct access to the control network): the historian periodically exports a CSV or Excel file (Tag;Timestamp;Value) into a watched folder of the server; the gmao-scada-files job imports it every five minutes, archives it with a timestamp and logs the result. The screen also allows a manual Import file.
• OPC UA (with a DMZ or a gateway): the CMMS polls the OPC UA server at the chosen interval (gmao-scada-opcua), reading the current value of the configured nodes; Test connection checks access. The client certificate is generated in App_Data\pki and must be trusted on the OPC UA server if it does not accept unknown certificates.

Configuring a source

Administration > SCADA sources > New source: name, type, site, polling interval; for a file source, the watched folder, the pattern (*.csv), the delimiter, the column names, the date format and the time zone (site local time or UTC); for OPC UA, the endpoint (opc.tcp://...), the user name, the password (encrypted) and the security mode.

Tag → meter mappings

For each historian tag or OPC UA node (ns=2;s=...), indicate the CMMS meter fed, a factor and an offset (unit conversion), and optionally high and low thresholds. A reading outside the thresholds creates an urgent work request in the name of "SCADA" on the equipment, notifies the configured role (Scada.AlertRole) and respects a cooldown so as not to repeat the alert at every reading.

Log

The Import log tab lists each run: file, rows read, readings imported, rejected (unknown tag, timestamp already known, unreadable value) and alerts. Imported readings appear in the meter history with the SCADA source and trigger meter-based preventive plans like a manual reading.