+
# ARSAS
-### IEC 61850 IED Explorer, Multi-Device Monitor, GOOSE Subscriber & Smart Control Workstation
+### One application for practical IEC 61850 engineering
-**A modern Windows engineering application for SCL-assisted workflows, live MMS model discovery, report-first monitoring, read-only GOOSE subscription, sequence-of-events analysis, diagnostics, and guarded IEC 61850 control.**
+**MMS · Reporting · GOOSE · File Transfer · Sampled Values · SCL · Control · Diagnostics**
-[](https://github.com/masarray/ArIED61850Tester/actions/workflows/build.yml)
-[](https://masarray.github.io/ArIED61850Tester/)
+ARSAS is an open-source Windows engineering workstation for IEC 61850 testing, commissioning, troubleshooting, model inspection, live monitoring, fault-record retrieval, and evidence-driven control workflows.
+
+[](https://github.com/masarray/arsas/actions/workflows/build.yml)
+[](https://masarray.github.io/arsas/)
[](LICENSE)
[](https://dotnet.microsoft.com/)
[](#requirements)
-[**Product website**](https://masarray.github.io/ArIED61850Tester/) · [**Quick start**](#quick-start) · [**Architecture**](docs/ARCHITECTURE.md) · [**GOOSE Subscriber**](docs/GOOSE_SUBSCRIBER.md) · [**Validation**](docs/VALIDATION_CHECKLIST.md) · [**Report an issue**](https://github.com/masarray/ArIED61850Tester/issues)
+[**Product website**](https://masarray.github.io/arsas/) · [**Capabilities**](#capability-status) · [**Roadmap**](ROADMAP.md) · [**Architecture**](docs/ARCHITECTURE.md) · [**Report an issue**](https://github.com/masarray/arsas/issues)
The address may have changed, or the content may have moved into the repository documentation.
+The address may have changed, or the engineering content may have moved into the repository documentation.
ARSAS keeps the Windows operator experience and project workflow separate from protocol implementation. Each configured IED owns a dedicated runtime session while shared UI pipelines coalesce updates for responsive monitoring at scale.
ARSAS keeps the Windows engineering workflow separate from protocol implementation. Every configured IED owns an independent runtime session, while ARIEC61850 provides typed services for MMS, reporting, GOOSE, Sampled Values, files, SCL, control, and diagnostics.
┌────────────────────────────────────────────────────────────────────┐ -│ ARSAS │ -│ │ -│ IED Explorer · Signal Workspace · Live Monitor · Event Log │ -│ Diagnostics · Project Cache · Command Panel │ -└───────────────────────────────┬────────────────────────────────────┘ - │ typed application services -┌───────────────────────────────▼────────────────────────────────────┐ -│ ARIEC61850 │ -│ MMS Session · Discovery · Reporting · SCL Workspace · Control │ -│ Type Binding · CommandTermination · Protocol Diagnostics │ -└───────────────────────────────┬────────────────────────────────────┘ - │ IEC 61850 over TCP / report traffic - Laboratory IEDs
┌────────────────────────────────────────────────────────────────────────┐ +│ ARSAS │ +│ Project · IED Explorer · Monitor · SOE · GOOSE · SMV · Files · SCL │ +│ Diagnostics · Control Staging · Evidence · Engineer-facing UX │ +└──────────────────────────────────┬─────────────────────────────────────┘ + │ typed application services +┌──────────────────────────────────▼─────────────────────────────────────┐ +│ ARIEC61850 │ +│ Transport · Association · MMS · Reporting · GOOSE · Sampled Values │ +│ File Services · SCL · Control · Type System · Protocol Diagnostics │ +└──────────────────────────┬──────────────────────┬───────────────────────┘ + │ TCP/102 │ Ethernet process bus + Laboratory IEDs Approved capture network
Connection and monitoring state are not global. Stopping one device does not stop another, and a failure on one endpoint can be diagnosed without destroying the rest of the project workspace.
Endpoint, identity, configured context, cached model, selected points, status, and lifecycle state are owned by the device.
Each connected IED has its own association, discovery progress, request routing, report sessions, and reconnect context.
Report candidates, dynamic reporting, uncovered polling points, aliases, and coverage evidence remain scoped to that session.
Unread indicators and semantic process events retain their originating IED and reference context.
Control descriptors and cached control-object sessions are associated with the live IED association that produced them.
Connection, discovery, report, fallback, command, and cleanup evidence is recorded with the affected device.
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 tools.
Device cards, SCL project context, signal selection, persistence, navigation, and engineer-facing task orchestration.
Live grids, events, GOOSE and SMV views, file-transfer UX, control staging, diagnostics, and export-ready evidence.
Transport, association, MMS services, reporting, GOOSE, Sampled Values, file services, SCL, and control sequencing.
Live descriptors, object references, DataSets, control blocks, command structures, value decoding, and validation.
Application services expose explicit capabilities and errors rather than leaking UI assumptions into protocol implementation.
Build-time checks fail explicitly when required ARIEC61850 contracts are missing instead of hiding degraded runtime behavior.
Static configuration is useful evidence, but it is not treated as proof that every selected point will arrive in a usable report. The runtime validates coverage and maintains bounded fallback for anything still uncovered.
Use discovered RCB and DataSet hints to prepare the most relevant configured report groups.
Connecting, monitoring, transferring files, viewing process-bus traffic, or staging control for one device must not silently alter another device.
IP address, port, configured SCL context, discovered identity, capability state, and reconnect information belong to the device.
Association, discovery progress, requests, report sessions, file services, and cleanup remain scoped to the originating IED.
Static reports, dynamic coverage, uncovered polling points, aliases, and source evidence are maintained per session.
GOOSE and Sampled Values actions open with the selected IED and configured model context rather than as ambiguous global tools.
Control descriptors and command sessions remain associated with the live MMS association that produced them.
Connection, report, sequence, file-transfer, command, and cleanup evidence retains the affected device reference.
Configured report membership is valuable evidence, but it is not treated as proof that every selected point will arrive in a usable stream. The runtime validates actual coverage and retains bounded fallback.
Use discovered RCB and DataSet metadata to prepare the most relevant configured groups.
Reserve or enable appropriate report control blocks and validate the actual member references.
Create temporary dynamic plans for exact points not covered by usable static groups where the IED permits it.
Place only still-uncovered or unverified points in a priority queue serviced by the device monitor loop.
Associate each value update with its acquisition source and keep alias or reference proof available for diagnostics.
Create bounded dynamic plans for selected points not covered by usable static groups where the IED permits it.
Place only still-uncovered or unverified points in a priority queue serviced by the device monitor loop.
Associate each update with timestamp, quality, reason, source, alias, and originating-device context.
Process views use the timestamp supplied by the IED, report, or companion timestamp attribute. Local runtime time may be used internally for diagnostic ordering but is not presented as the process event timestamp.
GOOSE and Sampled Values data rates should not force the UI to allocate or render every network sample. The architecture separates capture, decoding, supervision, aggregation, and presentation.
Workflow navigation, device cards, signal selection, project persistence, live grids, event presentation, diagnostics UX, and command staging.
Transport, association, MMS services, model discovery, report sessions, SCL workspace services, control sequencing, type binding, and protocol decoding.
The build checks for required engine contracts before restore and compilation so missing APIs fail explicitly rather than producing hidden runtime degradation.
Process views use the timestamp supplied by the IED, report, or companion timestamp attribute. Local runtime time may support diagnostic ordering but is not silently presented as process event time.
Association failures, unsupported services, model mismatches, report gaps, GOOSE sequence anomalies, file-service errors, and negative command termination should be explicit and attributable.
The repository contains the multi-IED ownership model, engine compatibility requirements, validation checklist, reporting behavior, control integration, and clean-room boundaries.
The repository documents multi-IED ownership, engine compatibility, reporting behavior, validation boundaries, Smart Control integration, and clean-room development policy.
ARSAS does not infer a command from a button label alone. It reads the live control model, resolves the command type, constructs the required Direct or Select-Before-Operate sequence, and records completion and feedback evidence for the test condition.
ARSAS does not translate a button label into a blind write. It reads the live control model, resolves the command structure, preserves the required control context, executes the supported Direct or Select-Before-Operate sequence, and presents completion evidence.
A semantic action becomes available only after ARSAS and ARIEC61850 have enough live evidence to represent the command without positional field guessing or a generic write fallback.
Normalize the selected reference and verify the expected control-object boundary.
Determine whether the object requires Direct or Select-Before-Operate, with normal or enhanced completion handling.
Retrieve `Oper`, `SBOw`, and optional `Cancel` type descriptions and locate the named `ctlVal` field.
Represent Open, Close, Raise, Lower, Boolean, counter, or setpoint intent using the actual live MMS type.
Preserve origin, `ctlNum`, timestamp `T`, Test, interlock, and synchrocheck values across selection and operation.
Present confirmed service results, CommandTermination, errors, AddCause, elapsed time, and mapped process feedback.
A semantic action becomes available only when ARSAS and ARIEC61850 have enough live evidence to represent the command without positional guessing or a generic write fallback.
Normalize the selected reference and verify the control-object boundary.
Determine whether the object requires Direct or Select-Before-Operate, including normal or enhanced completion handling.
Retrieve `Oper`, `SBOw`, and optional `Cancel` type descriptions and locate the named `ctlVal` field.
Represent Open, Close, Boolean, Raise, Lower, counter, or setpoint intent through the actual live type.
Preserve origin, `ctlNum`, timestamp, Test, interlock, and synchrocheck values through selection and operation.
Present confirmed service results, `CommandTermination`, errors, `AddCause`, elapsed time, and mapped feedback.
The UI presents the action an engineer intends. The engine independently handles the control model and command value representation discovered from the IED.
Open and Close actions with position feedback decoded separately from the command wire representation.
True and False actions represented through the discovered single-point control type.
Raise and Lower actions for supported binary step command structures.
Typed integer command values when the live descriptor is operationally usable.
Explicit setpoint entry and type-aware value binding for supported analog control objects.
Test, interlock, and synchrocheck request flags remain attached to the exact command row being staged.
The UI presents the operator intent. The engine independently handles the control model and value representation discovered from the IED.
Open and Close actions with command encoding and feedback decoding treated as separate evidence.
True and False actions represented through the discovered single-point command type.
Raise and Lower semantics for supported binary step command structures.
Typed integer command values when the live descriptor is usable.
Explicit value entry and type-aware binding for supported analog control objects.
Test, interlock, and synchrocheck requests remain attached to the exact command being staged.
Direct · normal Oper → confirmed result SBO · normal SBO → Oper → confirmed result Direct · enhanced Oper → CommandTermination SBO · enhanced SBOw → Oper → CommandTermination -Completion evidence: service result · ControlError · AddCause · LastApplError · feedback
Validate positive and negative termination, interlock and synchrocheck rejection, Test mode, timeout, Cancel, association loss, competing-client ownership, and process feedback mapping in the approved test environment.
Validate positive and negative termination, interlock and synchrocheck rejection, Test mode, timeout, Cancel, association loss, competing-client ownership, and process feedback in the approved test environment.