Choose the dedicated IO List path when an approved SDI test sheet already defines the indications. Choose general IEC 61850 testing for complete model discovery, reporting, GOOSE, command outcomes, file access and broader integration investigation.
.arsasAdapt the sequence to the approved FAT procedure and project responsibilities.
Add the approved endpoint, establish MMS association and inspect the live hierarchy, DataSets, RCBs and control model.
Choose status, measurement, quality and timestamp points required by the test sheet instead of mapping the entire IED blindly.
Prefer configured reporting, verify exact DataSet membership and keep unsupported or unavailable coverage visible.
Check stream identity and sequence evidence, then execute only approved Direct or SBO operations with visible completion results.
Probe available fault records and retain communication, report, frame and service outcomes with the originating IED.
Whether the session starts from an IO List or manual signal selection, review identity, object reference, value, quality, timestamp and acquisition source together.
ARSAS does not replace calibrated injection equipment, protection-function testing, approved drawings, settings review, cybersecurity controls, witness sign-off, digital signatures or vendor responsibility. IO List FAT is available on current mainline; verify the stable release scope before 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 →