Project and workflow
Device cards, SCL context, signal selection, persistence, navigation and task orchestration.
Application boundary · protocol engine · independent IED ownership
Independent device sessions above a reusable IEC 61850 engine.
ARSAS keeps the engineer-facing Windows workflow separate from protocol implementation. Every IED owns an independent runtime session while ARIEC61850 provides typed services for transport, MMS, reporting, GOOSE, Sampled Values, files, SCL, control and protocol diagnostics.
System boundary
┌──────────────────────────────────────────────────────────────┐
│ ARSAS │
│ Explorer · Monitor · SOE · GOOSE · Files · SCL · Control │
│ Diagnostics · Project state · Engineer-facing evidence │
└──────────────────────────────┬───────────────────────────────┘
│ typed application services
┌──────────────────────────────▼───────────────────────────────┐
│ ARIEC61850 │
│ Transport · MMS · Reporting · GOOSE · SMV · Files · SCL │
│ Control · Type system · Protocol diagnostics │
└──────────────────────┬────────────────────┬──────────────────┘
│ TCP/102 │ process bus
Approved IEDs Approved capture networkSeparation of concerns
Protocol behavior remains testable outside the UI.
The application can evolve its workflow and visualization without duplicating protocol rules, while the engine can be validated with deterministic fixtures and reused by other engineering tools.
Visualization and evidence
Live grids, events, GOOSE and SMV views, file UX, control staging and communication diagnostics.
Protocol services
Transport, association, MMS, reporting, GOOSE, Sampled Values, files, SCL and control.
Type and model handling
Live descriptors, object references, DataSets, control blocks, value decoding and validation.
Typed contracts
Explicit capabilities and errors rather than UI assumptions leaking into protocol behavior.
Compatibility gates
Build-time checks fail explicitly when required application or engine contracts are missing.
Per-device ownership
One IED, one session, one attributable lifecycle.
Connecting, monitoring, transferring files or staging control for one device must not silently alter another device.
Endpoint and identity
IP, port, SCL context, discovered identity, capability state and reconnect information belong to the device.
MMS association
Association, discovery, requests, reports, file services and cleanup remain scoped to the IED.
Acquisition plan
Static reports, dynamic recovery, polling points, aliases and source evidence are maintained per session.
Process-bus context
GOOSE and SMV actions open with the selected IED and available model context.
Control context
Control descriptors and command sessions stay with the live association that produced them.
Diagnostics and events
Connection, report, file, sequence and command evidence retains the affected IED identity.
Bounded runtime work
Scale without one background task per signal.
ARSAS uses per-IED loops, bounded queues, coalesced values and virtualized grids to keep large engineering workspaces responsive.
One monitoring loop per IED
Selected values share a controlled acquisition lifecycle instead of spawning unbounded tasks.
Priority polling for uncovered points
Only points that still require polling are scheduled in a bounded queue.
Latest-value coalescing
Rapid updates can be combined before the UI receives a bounded batch.
Bounded history
Events and diagnostics retain useful evidence without growing indefinitely.
Virtualized grids
Large live models remain navigable without rendering every row at once.
Users do not need the source tree to use ARSAS.
The landing website provides downloads, capabilities, engineering boundaries and workflow guidance. Repository detail remains available for developers and technical reviewers.
Source remains available for deeper review.
Developers can inspect the ARSAS application and reusable ARIEC61850 engine when architecture, contribution or implementation detail is required.
Verified stable release
Download ARSAS 1.6.17 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 →