The command sequence must follow the object and IED behavior actually exposed. A generic write is not a safe substitute for a typed IEC 61850 control workflow.
The client sends the supported operate sequence directly, subject to the live control model, origin, check conditions, timing and device logic.
The client first establishes a selection context, then operates within the permitted sequence and timing window.
Inspect ctlModel, command type, service reference, select behavior, required checks and command completion path before presenting an active control action.
Do not infer Direct or SBO only from the object class or vendor family.
Use the live descriptor for DPC, SPC, INC, BSC, APC or other supported control form.
For SBO, retain select response, timing and operate response as distinct evidence.
A positive service response, CommandTermination and process feedback are not interchangeable.
Retain service result, command completion, AddCause, timing and the resulting status or position feedback.
Do not hide rejected checks, expired selection, access denial or device interlocking behind a generic failure message.
Continue with CommandTermination and AddCause or review the Smart Control capability.
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.
Reviewed 20 July 2026 for practical IEC 61850 laboratory, FAT, SAT, commissioning and troubleshooting use.
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 →