A substation automation system is only as reliable as the control of its changes. These tools compare the approved and current versions of registers, tag lists and network designs, log which configuration file is approved and installed in every device by its SHA-256 fingerprint, validate SCADA tag databases before loading, and keep Windows patches in line with the SCADA vendor's approvals.
Everything runs in your browser; files are never uploaded. Download the logs and reports and keep them with the project records.
Compare the approved and current versions of an IP or asset register, SCADA tag list, port or cable list (CSV/Excel), SCL NetStudio project or AJ Collector report: added, removed and changed items, with the documents to update and tests to repeat for each change.
Record which version of each SCD, CID, switch, RTU, PLC, HMI or firmware file is approved and installed in each device, identified by its SHA-256 fingerprint; read SCL header and history; check any file against the log.
Check a SCADA, gateway or RTU tag list: duplicate names and addresses, missing descriptions and units, engineering ranges, alarm limits out of order, Modbus and IEC 104 addressing, naming rules and copied rows.
Installed Windows updates from AJ Collector reports against the SCADA vendor's approval list: not approved, under test or withdrawn updates installed, approved updates missing, and redundant servers on different patch levels.
How to keep a commissioned substation automation and SCADA system in its approved state: baselines, version control of SCD, CID and switch files, comparing revisions before and after a change, tag database checks, patch control and the records to hand over.