Establish device context
Confirm the approved endpoint, active interface, device identity and live MMS model before interpreting results.
Use ARSAS to inspect current values, quality, timestamps, reporting state, GOOSE behavior, command completion, fault-record access and per-IED diagnostics while commissioning activities are performed under an approved procedure.
Commissioning pressure can encourage premature changes. Start by preserving the evidence already available from the IED and network.
Confirm the approved endpoint, active interface, device identity and live MMS model before interpreting results.
Review selected values, quality, process timestamps, reason-for-inclusion and semantic event history.
Check RCB state, DataSet coverage, stream identity, sequence counters, retransmission and payload evidence.
Use typed Direct or SBO workflows only when the procedure, role and plant condition permit active control.
Unsupported services, rejected writes, report gaps, timeouts and command failures remain visible for root-cause analysis.
ARSAS does not grant switching permission, determine plant safety, replace protection testing, approve settings or override site procedures, cybersecurity controls and independent verification.
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 →