What was engineered or exported
- IED and AccessPoint definitions
- communication addressing
- Logical Device and DataType templates
- DataSets, RCBs and GOOSE intent
- vendor-private engineering context
SCL describes configured engineering intent. Live MMS discovery shows what the connected IED currently exposes. Troubleshooting becomes stronger when both are compared without treating either one as complete proof by itself.
A full-file textual difference can create noise. Focus on endpoint, model reference, DataSet membership, RCB association, GOOSE identity or control model related to the observed problem.
Record filename, source, revision and intended target before comparing it with live evidence.
Use the approved endpoint and retain the association and model timestamp context.
Check the exact object, DataSet, RCB or GOOSE reference required by the test.
Update the controlled project baseline or device configuration only through the approved owner and procedure.
Use the CID rejection guide for parser problems or silent reporting for report mismatch.
ARSAS can expose live model, report, GOOSE, file, control and diagnostic evidence. Final conclusions still depend on the approved project design, vendor documentation, test procedure, network access and independent verification.
Reviewed 20 July 2026 for practical IEC 61850 laboratory, FAT, SAT, commissioning and troubleshooting use.
Use the installer for a normal workstation, choose the portable ZIP for a controlled folder deployment, and verify the published SHA-256 before use.
What’s new, limitations and signing status →