SCL · live model · reporting · GOOSE · gateway integration

Multi-vendor IEC 61850 integration with configured and live evidence together.

Use ARSAS to compare project SCL intent with the services and model exposed by each IED, inspect reporting and GOOSE behavior, and prepare a controlled selected-RCB baseline for SAS or gateway integration.

SCL contextSCD, CID, ICD, IID and SSD engineering input
Live modelObserved hierarchy, services, DataSets and RCBs
GOOSEAPPID, VLAN, references, sequence and payload
ExportSelected-RCB Edition 1 or Edition 2 baseline
Suggested workflow

Find the mismatch before editing the project.

Interoperability problems often involve differences between configured intent, live server behavior and the expectations of the receiving SAS or gateway.

01

Open project context

Load the available SCL and identify the intended IED, access point, DataSets, RCBs, GOOSE control blocks and addresses.

02

Discover the live IED

Connect to the approved endpoint and inspect the model, services, DataSets, report controls and command descriptors actually exposed.

03

Compare reporting evidence

Check RCB availability, ownership, DataSet membership, report behavior and any rejected or unsupported operations.

04

Inspect GOOSE identity

Verify APPID, VLAN, destination MAC, goCBRef, DataSet reference, sequence counters and ordered payload leaves.

05

Prepare a controlled baseline

Select the intended RCB, retain verified DataSet members and export an Edition 1 or Edition 2 SCL baseline for further engineering review.

ARSAS selected RCB SCL export for multi-vendor IEC 61850 integration

Selected-RCB SCL export

Review RCB availability, choose the intended reporting path and retain the verified DataSet members before exporting the integration baseline.

Useful for

SAS, gateway and IED integration.

  • Edition 1 and Edition 2 project alignment
  • Reporting DataSet and RCB troubleshooting
  • GOOSE address and payload verification
  • Configured-to-live model comparison
  • Multi-IED diagnostic attribution
Boundary

Evidence is not universal conformance.

A successful connection or export does not prove full IEC 61850 conformance, interoperability with every vendor, project correctness or acceptance by the receiving system. Final engineering review remains required.

Related product areas

Inspect the evidence behind the integration.

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 →