Start from an approved endpoint.
Add an IED address or open SCL. The first objective is read-only identity and model evidence, not configuration change.
Real screenshots · no marketing mockup · evidence-first
See the ARSAS workflow before downloading.
This is a guided product storyboard, not a simulated relay session or time-to-value claim. Every image comes from the current application evidence set.
Keep each IED attributable.
Associations, live models, monitoring state and diagnostics remain separated by device instead of being merged into an ambiguous session.
Inspect value, quality, timestamp and source together.
A selected value becomes useful evidence only when its object identity and acquisition context remain visible.
Preserve negative and fallback evidence.
Association, service, reporting and device-behavior diagnostics remain visible when an RCB is occupied, a write is rejected or polling is used.
Supervise GOOSE as a stream.
APPID, VLAN, stNum, sqNum, TAL, retransmission and ordered payload need to be interpreted together.
Retain event and transfer context.
Sequence evidence and fault-record workflow diagnostics can be carried into a test record without claiming that the retrieved record is complete or correctly scaled.
Export a bounded SCL baseline.
Choose one live RCB evidence path and preserve its exact identity. The output remains an engineering baseline requiring schema, project and vendor review.
The product exposes evidence-oriented workflows.
The screenshots prove that these interfaces exist in the current product evidence set. They do not prove interoperability with an untested device or guarantee a result on an operational network.
Use Quick Start before field testing.
Verify the package, confirm network authorization, obtain one read-only value and review diagnostics before attempting reporting recovery, file transfer, GOOSE capture or control.
Verified stable release
Download ARSAS 1.6.18 for Windows.
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 →