Import the ARSAS Excel template, test one IED at a time, require a trustworthy OFF baseline, capture a new OFF → ON → OFF sequence, and export reviewable Excel, native PDF and portable .arsas project output.
The first release is deliberately scoped to imported SDI / digital indications. Adapt the external simulation and witness steps to the approved FAT procedure.
ARSAS validates the ARSAS_SIGNAL_IMPORT sheet, required headers, project identity, unique TestPointId, IED identity, object reference and expected ON/OFF states. Blocking findings reject the import instead of being guessed.
Select the intended imported IED and review whether every enabled point is safely bound to the discovered IEC 61850 signal. Only the selected IED and its imported signals enter the FAT session.
A good-quality OFF image arms the point for ON. If the point is already ON, ARSAS waits for a new OFF baseline. The first image after reconnect is also baseline only.
ARSAS records the new OFF → ON transition and then waits for the matching ON → OFF transition. Duplicate, steady-state and out-of-order observations do not create false evidence.
Each transition can retain the raw value, normalized state, IED timestamp, independent ARSAS timestamp, quality, acquisition source, monotonic sequence, connection generation, verdict and reason.
Stop the IED session before export so the append-only evidence journal can be sealed and verified. Then create Excel, PDF or the complete portable project.
The approved source workbook remains preserved. Result and handover artifacts are generated separately and protected by explicit identity and integrity checks.
ARSAS copies the approved workbook, matches rows by TestPointId, and writes observed values, IED and ARSAS timestamps, quality, source, ON/OFF verdicts, overall result and state-machine notes. A point mismatch refuses partial output.
A4 landscape evidence is generated directly by the built-in PDF 1.4 engine with project summary, per-IED sections, wrapped signal rows, timestamps, quality, source, result and reason. No browser, printer driver or third-party PDF layout package is required.
.arsas continuationThe project bundles the source workbook, snapshot, sealed evidence journals, Excel result, native PDF, manifest hashes and handover notes. New exports use .arsas; legacy .arsas-iofat filenames remain readable.
ARSAS validates package kind, versions, safe archive paths, size limits, workbook identity, report hashes and the evidence-journal hash chain before continuing the project on another workstation.
Completed evidence remains preserved, but a new workstation still requires a new trustworthy runtime baseline before unfinished points continue.
Import workbook, bind the IED, run the available tests, stop the session and export one .arsas file.
Keep the project file under the same confidentiality and evidence-handling controls as the source IO List and IED addresses.
Choose FAT / IO List Testing → Open ARSAS Project, reconnect and discover the intended IED, then obtain a new baseline.
Completed points are excluded by default. Interrupted ON-only continuity is review evidence and is never silently resumed into PASS.
The current development line includes strict import, one-IED sessions, transition evidence, autosave, journals, Excel, PDF and .arsas. Check the stable release notes before expecting this workflow in the latest published installer.
Analog tolerance, output commands, reusable GOOSE/SMV/file/control campaigns, formal witness approval, digital signatures and multi-user review are not claimed by this first IO FAT phase.
The workspace does not replace calibrated injection equipment, protection-function testing, drawings and settings review, switching authority, independent witness sign-off, vendor responsibility or IEC 61850 conformance certification.
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 →