Open the available SCL source
Load the approved project or device file and extract endpoints, model references, communication settings, DataSets and reporting context that can support the task.
SCD · CID · ICD · IID · SSD · configured-to-live evidence
Use SCL as engineering intent—then compare it with the relay evidence available now.
ARSAS opens common IEC 61850 SCL inputs, extracts useful endpoint and model context, keeps configured information beside the live IED session and supports controlled selected-RCB export for Edition 1 or Edition 2 integration baselines.
Common inputsSCD, CID, ICD, IID, SSD and compatible XML context
Live comparisonKeep configured intent and discovered server behavior visible together
RCB reviewInspect available and occupied reporting paths before export
Edition-aware outputSelected-RCB baseline export for controlled Edition 1 or 2 integration
Configured-to-live workflow
Avoid treating an available SCL file as unquestioned truth.
Engineering files can be incomplete, outdated or created for a different integration stage. ARSAS uses them as valuable configured context while preserving what the connected relay currently exposes.
Connect to the intended IED
Discover the current live server model and keep differences visible instead of silently replacing one source with the other.
Review reporting availability
Inspect existing RCBs, ownership and verified DataSet members before selecting a path for downstream SAS or gateway integration.
Export a controlled baseline
Choose the intended RCB and Edition target, retain verified members and create a cleaner baseline without blind XML deletion.
New integration evidence
Selected-RCB SCL export for legacy SAS and gateway workflows.
Choose the reporting path intentionally and keep the available relay evidence visible during export.
SCLChoose the RCB and target edition
Inspect available and occupied RCBs, select the intended reporting path, retain verified DataSet members and export a normalized baseline.
Reduce avoidable integration cleanup.
- Focus the baseline on the selected reporting path
- Retain verified DataSet members
- Make Edition target explicit
- Avoid deleting XML sections without understanding relationships
- Keep source and live evidence traceable
Export is not end-to-end interoperability certification.
The receiving SAS or gateway must still be validated against its supported schema, edition behavior, naming expectations, DataSet handling and report configuration. ARSAS does not claim that one exported file will work unchanged with every vendor.
Multi-vendor integration and troubleshooting
- Compare a CID or ICD file with the live relay model
- Investigate missing or mismatched report members
- Review RCB availability before gateway mapping
- Create an Edition 1 baseline for legacy integration
- Preserve configured and observed context during FAT or SAT
Files and devices are complementary evidence sources.
Use the SCL file to understand intended configuration and the live IED to understand current behavior. A difference is not automatically a relay fault or a file fault; it is evidence that requires engineering review.
Discover the live model through MMS.
Use current server evidence to assess whether configured objects and reporting paths are still available.
Compare configured GOOSE with observed streams.
Use publisher identity, sequence, TAL and payload evidence when SCL alone cannot explain runtime behavior.
Verified stable release
Download ARSAS 1.6.17 for Windows.
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 →