IO List FAT evidence
Import approved digital indications, bind to the intended IED, require OFF → ON → OFF, and export Excel, native PDF or a resumable .arsas project.
Start from an approved ARSAS IO List when a digital-indication test plan already exists, or start from an endpoint/SCL for general engineering. ARSAS keeps device identity, live behavior, evidence and bounded project output connected.
The IO List workspace is a read-only test-plan layer for imported SDI points. General FAT and engineering workflows continue to cover discovery, reporting, GOOSE, files, SCL and guarded control.
Import approved digital indications, bind to the intended IED, require OFF → ON → OFF, and export Excel, native PDF or a resumable .arsas project.
Validate the complete live model, selected signals, reports, GOOSE, control outcomes, disturbance-record access and integration output before shipment.
Reconfirm endpoint access, reporting, station-bus behavior, generated or supplied SCL and downstream system integration after installation.
Investigate live behavior, sequence evidence, communication quality, file services and command completion during controlled commissioning.
Recover from unusable vendor files, generate or normalize bounded SCL and isolate identity, DataSet, RCB, reporting and GOOSE mismatches.
Use an IO List for repeatable indication proof, or use the endpoint and SCL context to investigate broader IEC 61850 services. Preserve what happened and what still requires review.
It does not replace approved procedures, calibrated test equipment, protection-setting verification, switching authority, witness acceptance, formal signatures, target-system import validation or vendor responsibility.
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 →