Import the legacy ARSAS sheet or the Rev.3 workbook, keep the exact event-log telegram separate from the report display reference, test one IED at a time, and export reviewable Excel, executive PDF and portable .arsas output.
Automatic transition testing is deliberately focused on approved SDI digital indications. Unsupported, command, duplicate and incomplete-reference rows remain visible instead of being silently converted into another test type.
ARSAS accepts the legacy ARSAS_SIGNAL_IMPORT contract and the Rev.3 FAT_Points_Import plus Document_Control contract. Project identity, IED endpoint, TestPointId, data type, source state text, exact IEC reference, data attribute, functional constraint and review reason remain explicit.
Missing IED, IP, FC, data attribute or IEC reference stays blocked. Duplicate keys and active-command points stay in review scope. The exact Event Log Search Reference is preserved for log correlation, while the Report Display Reference is used only for readable customer traceability.
ARSAS discovers the live MMS model, normalizes known display wrappers without fuzzy name guessing, and accepts only one unique signal match. Real connection, discovery, binding and acquisition readiness drive the determinate card progress.
A good-quality OFF image arms the point. ARSAS then accepts a new OFF → ON transition followed by its ON → OFF return. Every accepted item retains quality, timestamp and acquisition source; startup, reconnect, duplicate, steady-state or out-of-order images never become false edge evidence.
Completed evidence rows are protected before preflight, live preparation and session start. Switching to Engineering hides the loaded FAT workspace; returning shows the same project, selected IED, evidence and progress without another file dialog.
Stop the active session, verify the append-only journal, and export the Excel result, executive PDF or complete portable project. Loading another workbook or project remains an explicit replacement action.
The approved source remains preserved. Result artifacts are generated separately with explicit document, signal and evidence identity.
ARSAS copies the source workbook and updates matching test rows without modifying the original. Observations, result, event time, log match, evidence reference and reviewer comment remain available for handover.
AS TESTED PDFThe native A4 landscape report includes project and supplier context, document number, revision, exact IEC 61850/event-log reference, expected state, ON/OFF relay timestamps, result summary, test basis and sign-off areas.
.arsas continuationThe project carries the source workbook, snapshot, journals, reports, hashes and handover context. A restored project keeps completed evidence but requires a new live baseline for unfinished points.
Package kind, safe archive paths, size limits, workbook identity, report hashes and evidence-journal continuity are checked before another workstation continues the project.
The stable release and current mainline share this IO FAT scope today. Future mainline additions are not implied to exist in a stable installer until a new verified release is published.
The executive PDF is written natively by ARSAS; it does not depend on a browser or a third-party PDF layout package.
Automatic analog tolerance, authorized output-command campaigns, calibrated measurement claims, formal digital signatures and multi-user approval are not implied by the current SDI IO FAT workflow.
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.
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 →