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
- project revision and intended target
Configured intent · running model · drift · recovery
The SCL file and the live relay answer different but complementary questions.
SCL describes configured engineering intent. Complete live MMS discovery shows what the connected IED currently exposes. ARSAS keeps both visible and provides a bounded recovery path when the source file is stale, incomplete or rejected by the receiving system.
What the server exposes now
- physical device identity and reachable endpoint
- complete Logical Device, Node, object and attribute hierarchy
- current DataSet and RCB inventory
- live values, quality and timestamp evidence
- supported service and access outcomes
- available type and control-model evidence
Diagnostic path
Compare the relationships that affect the failed workflow.
A full-file textual difference can create noise. Focus on physical identity, endpoint, full domain names, object references, DataSet membership, RCB association, GOOSE identity or control model related to the observed problem.
Identify the controlled project source
Record filename, owner, revision, intended target and receiving-system expectation before comparing it with live evidence.
Discover the complete running model
Use the approved endpoint and retain physical identity, full MMS hierarchy, DataSets, RCBs, types and association context.
Compare functional references
Check the exact object, DataSet, RCB, GOOSE or communication reference required by the failed test.
Choose repair, normalization or regeneration
Repair the controlled source when it remains authoritative, normalize it into bounded single-IED output, or generate IID/ICD from complete live discovery when the source cannot be trusted.
Validate through the receiving engineering process
Import the bounded result and preserve exact acceptance or rejection evidence before updating the controlled baseline.
The device is a stronger source than the available file.
- the vendor CID or ICD is missing
- the file describes an older firmware or configuration
- physical identity and MMS domains do not align
- DataSet or RCB inventory is incomplete
- another tool rejects the file before useful comparison
The project intent includes information MMS cannot reconstruct.
- station communication design and subscribed relationships
- project-wide GOOSE or Sampled Values intent
- vendor-private engineering information
- approved project naming and ownership decisions
- configuration that has not yet been deployed to the IED
Use live evidence to prepare a controlled baseline
Generate IID or ICD from complete live discovery, normalize opened SCL or retain one verified DataSet and selected RCB context while preserving the original sources.
Continue with the actual failure mode
Choose the recovery path instead of editing XML blindly.
Use the CID rejection guide for importer errors, Smart Reporting for report mismatch, or the IP-to-SCL workspace for generation and bounded conversion.
Use the evidence to narrow the cause—not to claim conformance.
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.
Written and reviewed by Ari Sulistiono.
Reviewed 20 July 2026 for practical IEC 61850 laboratory, FAT, SAT, commissioning and troubleshooting use.
Verified stable release · ARSAS 1.6.33
Download the release-grade IEC 61850 workstation for Windows.
The current stable build includes Rev.3 IO List FAT import, an executive AS TESTED evidence report, a loaded Engineering/FAT workspace session, and direct receive-only GOOSE plus bounded SMV capture from each IED card.
Use the installer for a normal workstation, choose the portable single EXE for an approved no-install deployment, and verify the published SHA-256 before use.
What’s new, engineering boundaries and signing status →