Identify the available source
Start from the approved IED IP address, the available CID/ICD/IID/SCD, or both. Preserve the original file and record the intended receiving system.
Interoperability testing evidence · live model · SCL · reporting · GOOSE
Build evidence for multi-vendor IEC 61850 interoperability testing.
Compare what the project says should exist with what the IED actually exposes. ARSAS keeps live-model, SCL, DataSet, RCB, reporting and GOOSE observations visible so integration mismatches can be isolated before either system is changed.
Recover from IPComplete live discovery to Edition 2 IID or Edition 1 ICD
Normalize SCLBounded generic single-IED conversion with structured findings
Verify runtimeReporting, GOOSE, identity, DataSets and RCBs in live context
Export intentionallyOne verified RCB as an Edition 1 or Edition 2 CID baseline
Suggested workflow
Find the mismatch before changing either system.
Interoperability failures usually sit between three sources: the IED that is online, the engineering file that describes intended configuration, and the proprietary expectations of the receiving SAS or gateway.
Discover the live IED completely
Inspect physical identity, full MMS domains, hierarchy, DataSets, RCBs, type information and service behavior actually exposed by the device.
Generate or normalize bounded SCL
Create IID or ICD from complete live discovery, or convert the opened source into a generic single-IED output while retaining findings and provenance.
Compare reporting and GOOSE evidence
Check RCB names, availability, DataSet membership, trigger options, APPID, VLAN, addresses, references, sequence behavior and ordered payload.
Validate the receiving system deliberately
Import the bounded output, retain exact errors, and separate schema, identity, reference, reporting and proprietary importer problems before making changes.
“CID rejected” is not a root cause.
- Physical IED identity does not match the receiving project
- Logical Device domains were shortened or reinterpreted
- Edition 1 and Edition 2 expectations differ
- DataSet members or FCDA references are missing
- An indexed RCB name was modified incorrectly
- The receiving tool applies an undocumented proprietary rule
Keep each layer visible.
- Live device identity and complete model
- Original configured SCL intent
- Generated or normalized bounded output
- Read-only live RCB availability and options
- Observed GOOSE communication and payload
- Exact receiving-system import result
Bounded selected-RCB CID export
Audit live availability, choose the intended reporting path and preserve exact RCB identity plus verified DataSet evidence before exporting the integration baseline.
SAS, gateway and IED integration.
- Recovering when a vendor CID or ICD cannot be used
- Edition 1 and Edition 2 project alignment
- Reporting DataSet and RCB troubleshooting
- GOOSE address, reference and payload verification
- Configured-to-live model comparison
- Multi-IED diagnostic attribution
Evidence is not universal conformance.
A successful connection, generation or import does not prove full IEC 61850 conformance, interoperability with every vendor, project correctness or acceptance by another proprietary tool. Final FAT/SAT engineering validation remains required.
Related product areas
Inspect the evidence behind the integration.
Verified stable · ARSAS 1.6.41
Ready for an approved Windows workstation?
Installer and portable packages share the same application scope. Verify the published SHA-256 and review the release boundary before field use.
Release notes, limitations and signing status →