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.
FAT · SAT · commissioning · interoperability evidence
Use one IEC 61850 tester across factory, site and integration work.
Start from an approved IO List, IED endpoint or SCL source. ARSAS keeps the tested device, observed live behavior and reviewable evidence connected as the project moves from FAT to SAT, commissioning and multi-vendor investigation.
Start from the IO ListStrict SDI plan, one-IED execution and ordered transition evidence
Start from the endpointComplete live model discovery without requiring usable vendor SCL
Export evidenceExcel result, native PDF and verified portable .arsas project
Carry context forwardFAT, SAT, commissioning and integration remain attributable per IED
Project workflows
Choose the starting condition and stage you are preparing for.
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.
General IEC 61850 FAT testing
Validate the complete live model, selected signals, reports, GOOSE, control outcomes, disturbance-record access and integration output before shipment.
IEC 61850 SAT testing
Reconfirm endpoint access, reporting, station-bus behavior, generated or supplied SCL and downstream system integration after installation.
IEC 61850 commissioning
Investigate live behavior, sequence evidence, communication quality, file services and command completion during controlled commissioning.
Multi-vendor interoperability
Recover from unusable vendor files, generate or normalize bounded SCL and isolate identity, DataSet, RCB, reporting and GOOSE mismatches.
One product, two controlled starting paths
Use General IEC 61850 Testing for endpoint-led engineering. Use FAT / IO List Testing for imported SDI plans and durable transition evidence. Both retain the originating IED and explicit evidence boundaries.
Start from the approved evidence source.
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.
ARSAS supports the test process.
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.
Verified stable · ARSAS 1.6.41
Ready for an approved Windows workstation?
Installer and portable packages share the same application scope. Verify the published SHA-256 and review the release boundary before field use.
Release notes, limitations and signing status →