Configured intent · running model · drift

The SCL file and the live relay answer different questions.

SCL describes configured engineering intent. Live MMS discovery shows what the connected IED currently exposes. Troubleshooting becomes stronger when both are compared without treating either one as complete proof by itself.

SCL context

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
Live model

What the server exposes now

  • reachable endpoint and association behavior
  • Logical Devices, Nodes, objects and attributes
  • current DataSet and RCB inventory
  • live value, quality and timestamp evidence
  • supported service and access outcomes
Diagnostic path

Compare the items that affect the failed workflow.

A full-file textual difference can create noise. Focus on endpoint, model reference, DataSet membership, RCB association, GOOSE identity or control model related to the observed problem.

01

Identify the authoritative project file

Record filename, source, revision and intended target before comparing it with live evidence.

02

Discover the running server model

Use the approved endpoint and retain the association and model timestamp context.

03

Compare functional references

Check the exact object, DataSet, RCB or GOOSE reference required by the test.

04

Resolve drift through engineering process

Update the controlled project baseline or device configuration only through the approved owner and procedure.

ARSAS live model and SCL selected RCB export comparison workflow

Use live evidence to prepare a controlled baseline

ARSAS can retain verified DataSet members and selected RCB context while keeping the source SCL and live model visible.

Related guides

Continue with the actual failure mode.

Use the CID rejection guide for parser problems or silent reporting for report mismatch.

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

Download ARSAS 1.6.18 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 →