Schema · identity · references · edition · live recovery

A rejected CID file does not automatically mean the relay is not interoperable.

First determine whether the failure is XML syntax, SCL structure, physical identity, edition handling, vendor-private content, broken references or a mismatch between the file and the running IED. When the source cannot be repaired safely, complete live discovery can provide a new bounded baseline.

Immediate answer

Preserve the original file and capture the exact import error.

Do not begin by deleting arbitrary XML sections. Record the parser location or rejected reference, the receiving tool and edition expectation, then compare the file with live IED evidence.

Typical symptoms
  • schema or namespace error during import
  • unknown or unsupported edition element
  • physical IED identity or MMS domain mismatch
  • unresolved DataSet, FCDA, RCB or communication reference
  • vendor-private section rejected by another tool
  • file imports but reporting remains silent
Diagnostic path

Separate file validity from integration usefulness.

A file can be valid XML but unsuitable for a target configurator. It can also import successfully while representing an outdated device model, incorrect identity or incomplete reporting assignment.

01

Record the receiving-system evidence

Keep the original filename, edition, namespace, exact error message, reported location and receiving software version.

02

Validate identity and critical references

Trace physical IED name, AccessPoint, server, full Logical Device domains, DataSets, FCDA members, RCBs and communication references without blind deletion.

03

Compare with the live IED

Confirm endpoint, complete typed model, DataSet directory, concrete RCB names and options currently exposed by the relay.

04

Choose the recovery path

Repair or normalize the opened source when its relationships remain trustworthy. Otherwise generate Edition 2 IID or Edition 1 ICD from complete live discovery.

05

Reduce only when the receiving workflow requires it

For a bounded gateway or legacy SAS path, audit availability and export exactly one verified RCB as an Edition 1 or Edition 2 CID baseline.

Live recovery can preserve

Relationships commonly damaged by manual cleanup.

  • physical identity separate from MMS Logical Device domains
  • complete typed hierarchy and available type information
  • DataSet membership and member order
  • exact indexed runtime RCB names
  • available trigger, optional-field and timing evidence
  • source, endpoint and export provenance
Still requires validation

The receiving importer remains authoritative for acceptance.

Generated SCL is vendor-neutral and schema-aware, but proprietary tools can apply rules beyond the standard. Retest the exact importer and preserve its result as project evidence.

ARSAS selected RCB SCL Edition 1 and Edition 2 export workflow

Build a bounded integration baseline

Select the intended RCB, retain verified DataSet members and choose the required SCL edition instead of removing unrelated XML through trial and error.

Related guides

Check whether the file still matches the running relay.

Continue with live-model comparison, the IP-to-SCL workspace or the complete multi-vendor integration workflow.

Engineering boundary

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.

Technical review

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 →