Do not stop at the operate response.
Wait for the supported completion path, capture CommandTermination and AddCause where available, then compare the resulting status or position feedback within the approved test window.
service response · completion · AddCause · feedback
A control request can be accepted before the device reports a negative final outcome.
Keep the initial service result, CommandTermination, AddCause, timing and process feedback as separate evidence. Collapsing them into one “success” or “failed” label hides the actual control path.
- select response when SBO is used
- operate service response
- CommandTermination result
- AddCause or detailed device reason
- process status, position or indication feedback
Diagnostic path
Identify where the command stopped.
The client, communication service, control model, device interlocking and physical process can each produce a different outcome. Preserve the timeline.
Record the request contract
Keep object reference, ctlModel, command type, value, origin, checks and selected association.
Record immediate service result
A positive acknowledgement means the request reached a certain service stage, not necessarily that operation completed.
Capture final completion evidence
Retain CommandTermination, AddCause and timing instead of replacing them with a generic message.
Correlate process feedback
Check the resulting status, quality, timestamp and event evidence from the same IED context.
Keep negative completion evidence visible
ARSAS retains service and diagnostic context so rejected or incomplete control paths can be investigated instead of hidden.
Accepted is not operated.
The service layer may accept the request while device logic later blocks or fails the operation.
Operated is not verified.
Independent status, event and process evidence remains necessary before declaring the test objective complete.
Related pages
Review the complete control sequence.
Compare Direct and SBO behavior or open the Smart Control capability page.
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
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 →