Create each device session
Add approved endpoints or SCL-derived device context and retain a clear identity for every relay, bay controller or gateway.
ARSAS gives each IED its own association, discovered model, selected signals, reporting state, events, file workflow, control context and diagnostics while still providing project-wide live-value and evidence views.
Multi-device work becomes unreliable when one global connection, one polling loop or one generic event list owns every relay. ARSAS keeps the runtime boundary per IED and combines only the evidence intended for project-wide views.
Add approved endpoints or SCL-derived device context and retain a clear identity for every relay, bay controller or gateway.
Each IED owns its live model, chosen signals, DataSets, RCBs, control objects and file-service state.
Values and events keep the originating device, quality, timestamp, reason and acquisition path visible.
Search and compare selected points across devices without collapsing their diagnostics or lifecycle into one ambiguous session.
The screenshots show the working application handling multiple IEDs, shared live-value review and device-attributable diagnostics.

Each device retains its own connection, model, monitoring and diagnostic state.

Search across devices while retaining source, quality, timestamp and acquisition evidence.

Separate semantic events from continuous live values and keep the originating IED visible.

Distinguish network, association, report, service and device-specific failures.
ARSAS uses per-IED runtime ownership, bounded collections, coalesced UI updates and virtualized engineering grids. The objective is responsive engineering work—not uncontrolled background polling or repainting every value continuously.
Browse the model, select signals and retain current type and reporting context per IED.
Keep directory browsing, downloads and transfer diagnostics attached to the originating relay.
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 →