ARSAS

From an IED IP address or approved IO List to attributable IEC 61850 evidence

Discover · Monitor · Test IO Lists · Diagnose · Generate SCL · Export Evidence

ARSAS is an open-source Windows IEC 61850 engineering workstation for FAT, SAT, commissioning, troubleshooting, and multi-vendor integration. Start from an approved IED IP address, an existing SCL file, or an ARSAS IO List workbook; discover what the device actually exposes; and preserve the result as attributable engineering evidence.

Download installer · Portable ZIP · Quick Start · IO List FAT Evidence · Product website · Compatibility evidence · Roadmap

_{Start from an IED IP address, an SCL file, a saved project, an approved IO List workbook, or the built-in communication workspace.}

Development and stable-release boundary: the current main line is version 1.6.19 and includes the IO List FAT evidence workflow described below. The latest published stable Windows release remains 1.6.18 until a separately validated and tagged release is produced. Check the release notes before assuming the downloaded stable package contains a mainline feature.

Why ARSAS stands out

Engineering problem	ARSAS response
The vendor CID or ICD is missing, outdated, or rejected by another engineering tool.	Perform complete live MMS discovery from the IED IP address and generate a schema-aware Edition 2 IID or Edition 1 ICD with companion evidence.
Reporting setup consumes the test window before useful values appear.	Read selected values immediately, prefer verified BRCB/URCB coverage, recover specific gaps where permitted, and retain visible bounded polling when reporting cannot be trusted.
A multi-IED test loses device ownership and diagnostic context.	Keep an independent association, model, monitoring state, events, controls, files, and diagnostics for every IED while providing a unified project view.
A FAT team must prove every IO List indication and then rebuild the evidence manually in Excel and PDF.	Import the approved ARSAS workbook, test one IED at a time, require ordered OFF → ON → OFF evidence, and export an Excel result copy, native PDF report, and resumable .arsas project.
Integration failures are reduced to vague messages such as “CID rejected” or “download failed.”	Preserve identity, references, DataSet membership, RCB options, protocol stages, negative responses, timing, and copyable diagnostic evidence.

ARSAS is designed to shorten the path from “the IED is reachable” to “the engineer has usable, attributable evidence.” It does not hide unsupported behavior or turn an uncertain result into a false success.

Two first-run paths

General IEC 61850 testing

Add an approved IED by IP address for complete live discovery, signal selection, Smart Reporting, multi-IED monitoring, GOOSE, file transfer, SCL workflows, diagnostics, SOE, and guarded control.

FAT / IO List testing

Import an approved ARSAS Excel workbook or open a portable .arsas project. The dedicated workspace shows only the imported IEDs and SDI signals, binds them to live-discovered IEC 61850 references, and records ordered transition evidence.

The IO List path is read-only toward the IED. It does not create DataSets, modify RCB configuration, or issue controls.

IO List FAT evidence workflow

Approved ARSAS IO List workbook
              ↓
Strict schema and identity validation
              ↓
Imported IED and SDI test points
              ↓
Live IEC 61850 object-reference binding
              ↓
Trustworthy OFF baseline
              ↓
OFF → ON evidence
              ↓
ON → OFF evidence
              ↓
PASS / REVIEW / FAIL / PENDING
              ↓
Excel result · Native PDF · Portable .arsas project

A point passes only when a new ON transition and the corresponding OFF transition are captured in order. An initial ON image is never accepted as ON evidence. The first image after reconnect is a baseline only. Quality, acquisition source, IED timestamp, independent ARSAS timestamp, monotonic observation sequence, and connection generation remain attached to the evidence.

IO FAT outputs

• Export Excel — copies the approved workbook and updates matching TestPointId rows; the source file is never modified in place.
• Export PDF — writes an A4 landscape PDF directly with the built-in dependency-free native PDF 1.4 engine ported from ARIEC60870 primitives.
• Export .arsas — packages the source workbook, project snapshot, sealed hash-chain journals, Excel result, PDF report, manifest hashes, and handover notes for another workstation.
• Legacy compatibility — existing .arsas-iofat filenames remain readable, while new projects use .arsas.

See IO List FAT Evidence Testing for the workbook contract, state machine, persistence model, package layout, integrity checks, and engineering boundaries.

Built for real project work

• FAT: import an approved SDI IO List, capture ordered state evidence, inspect models, selected signals, reports, GOOSE, controls, file services, and integration output before shipment.
• SAT: reconfirm installed endpoints, report behavior, station-bus traffic, and configured-versus-live differences.
• Commissioning: correlate live values, sequence of events, communication quality, fault records, and command completion.
• Multi-vendor integration: reconstruct or normalize bounded SCL output when vendor files, schema editions, identities, DataSets, or RCB names do not align cleanly.
• Troubleshooting: keep exact failures attached to the originating IED instead of rebuilding context across disconnected tools.

IP address to interoperable SCL

A successful full discovery can become a reusable engineering baseline:

Approved IED IP address
          ↓
IEC 61850 MMS association
          ↓
Complete typed live discovery
LD · LN · DO · DA · DataSet · RCB · types · identity
          ↓
Schema-aware normalization and validation
          ↓
Edition 2 IID or Edition 1 ICD
          ↓
Optional selected-RCB Edition 1/2 CID
          ↓
Target SAS or gateway import and FAT/SAT validation

What ARSAS preserves

• the physical IED identity separately from complete MMS Logical Device domains;
• typed model hierarchy and available type information;
• DataSet membership and member order;
• exact concrete runtime RCB names;
• available TrgOps, OptFlds, BufTm, IntgPd, RptID, and ConfRev evidence;
• endpoint and source context;
• structured JSON evidence, Markdown summary, and export findings.

What this helps prevent

• a Logical Device name being mistaken for the physical IED identity;
• valid MMS domains being shortened or rewritten;
• an exact indexed RCB name receiving a duplicate 01 suffix;
• incomplete FCDA membership being exported as if it were complete;
• Edition 1 and Edition 2 expectations being mixed silently;
• large vendor or project SCL files being passed downstream when only one bounded IED or one reporting path is required.

For an opened SCL source, ARSAS can also create a bounded generic single-IED Edition 2 output through the engine-owned interoperability converter while preserving the original file and surfacing structured findings.

The output is vendor-neutral, typed, and schema-aware, and is intended to reduce common multi-vendor import failures. It is not a universal acceptance guarantee. Every IID, ICD, or CID must still be reviewed and validated in the receiving SAS, gateway, or engineering tool.

Smart Reporting: useful values without a report dead end

Selected signals
      ↓
Immediate MMS image
      ↓
Validate configured BRCB / URCB coverage
      ↓
Recover exact uncovered gaps where supported and permitted
      ↓
Keep rejected, occupied, empty, or unverified points visible in bounded polling

ARSAS records how every displayed value was acquired. The engineer can distinguish report delivery from polling, inspect DataSet coverage, preserve report reasons and timestamps, and see when a dynamic write or existing RCB cannot be used.

Product tour

Every image below is captured from the working Windows application rather than a marketing mockup.

Independent multi-IED sessions Each device keeps its own association, discovered model, monitoring state, selected signals, files, controls, events, and diagnostics.	Unified live-value workspace Search selected values while retaining device ownership, quality, timestamp, acquisition source, report reason, and recent-change evidence.
Sequence of events Correlate state transitions, report activity, command feedback, and process timestamps without losing the originating IED.	GOOSE supervision Inspect APPID, VLAN, MAC, goCBRef, DataSet, stNum, sqNum, TAL, retransmissions, ordered payload leaves, and model binding.

Attributable communication diagnostics
_{Separate routing, TCP/102, association, discovery, reporting, file-service, GOOSE, timing, sequence, control, and device-behavior problems.}

Capability status

ARSAS uses explicit maturity labels so available behavior is not confused with roadmap direction.

IEC 61850 area	Status	Current scope
MMS client and model discovery	Available	Association, physical identity, complete LD/LN/DO/DA hierarchy, values, quality, timestamps, DataSets, RCBs, type information, and communication diagnostics.
IO List FAT evidence	Available on current mainline	Strict SDI Excel import, one-IED sessions, OFF → ON → OFF evidence, quality/reconnect handling, autosave, hash-chain journal, Excel result, native PDF report, and portable .arsas continuation.
Live discovery to SCL generation	Available	Generate a single-IED Edition 2 IID or Edition 1 ICD from the last successful complete typed discovery of an IP-connected IED.
SCL workspace and generic conversion	Available	SCD/CID/ICD/IID/SSD import, endpoint extraction, configured/live context, generic single-IED Edition 2 conversion, schema-aware Edition 1 export, findings, and source preservation.
Selected-RCB CID export	Available	Read-only availability audit, exact live RCB name, verified DataSet members and live options, and one-RCB Edition 1/2 CID output.
Reporting and live monitoring	Available	BRCB/URCB inspection, immediate reads, exact coverage evaluation, bounded recovery where permitted, visible polling fallback, multi-IED monitoring, and SOE.
GOOSE subscriber	Available	Read-only Npcap capture, APPID/VLAN/MAC metadata, sequence and TAL supervision, ordered allData, timeline evidence, and SCL/live-model binding.
IEC 61850 file transfer	Available	Bounded MMS browsing and download, partial or grouped record handling, COMTRADE-related retrieval, reconnect boundaries, duplicate detection, and detailed transfer evidence.
Smart Control	Available	Live ctlModel discovery, typed Direct and SBO sequences, Test/interlock/synchrocheck context, CommandTermination, application errors, timing, and mapped feedback.
Project persistence	Available	Save selected signals and project context; retain complete discovery snapshots and resumable IO FAT .arsas projects while refusing to treat a signal-only cache as a complete export model.
Sampled Values / SMV	Engineering preview	Per-IED entry points and bounded evidence workflow; deeper decoding, binding, scaling, synchronization, and sustained-performance validation remain active work.
Full visual SCL authoring	Planned	Create and edit complete project structures, communication, DataSets, control blocks, validation, diff, and reusable project output.
Unified multi-service test campaigns	Planned	Reusable analog, GOOSE, SMV, file, control, time-sync, exception, witness, approval, and campaign-level evidence workflows beyond the current SDI IO FAT phase.

See ROADMAP.md for milestones, definitions of done, and explicit non-goals.

Current stable Windows release

The latest verified public release is ARSAS v1.6.18, published on 21 July 2026.

Package	Intended use
Windows installer	Recommended for normal use, Start Menu integration, uninstall support, and the verified update workflow.
Portable ZIP	Extract and run without installation on a controlled engineering workstation.
SHA-256 checksums	Verify the exact package before use.
Release details	Version scope, assets, publication evidence, and release notes.

The installer checks the stable public manifest, validates the expected asset identity, size, and SHA-256, and only then opens the downloaded installer. Current public binaries are not Authenticode-signed, so Windows SmartScreen may show an unrecognized-publisher warning.

Start using ARSAS

System requirements

• Windows 10 or Windows 11, x64.
• An isolated laboratory network or an approved FAT, SAT, or commissioning boundary.
• Ethernet access to the intended IED for MMS services, normally TCP port 102.
• Npcap only for raw-Ethernet GOOSE or Sampled Values capture.
• Suitable authorization, switching authority, procedures, and independent verification before any active control or configuration workflow.

Visual Studio and an ARIEC61850 source checkout are not required for normal use of the packaged release.

First read-only session

1. Download the installer or portable ZIP and verify its SHA-256.
2. Confirm the approved network path and TCP port 102.
3. Choose Add IED by IP address.
4. Complete live MMS discovery.
5. Select a small known set of read-only signals.
6. Verify device ownership, value, quality, timestamp, and acquisition source.
7. Expand to reporting, GOOSE, file transfer, SCL generation, or control only after the read path is understood.

Start an IO List FAT project

1. Choose FAT / IO List Testing on the first-launch workspace.
2. Open an approved ARSAS IO List .xlsx workbook, or open an existing .arsas project.
3. Review import findings and live binding status.
4. Select one imported IED and confirm it is connected and discovered.
5. Start the IED session and obtain a trustworthy OFF baseline.
6. Operate the external test source so the indication changes OFF → ON → OFF.
7. Stop the session before exporting.
8. Export Excel, native PDF, or the complete .arsas continuation project.

Generate SCL from the IED

1. Complete a successful full discovery or Re-scan.
2. Confirm the physical IED identity and review blocking discovery diagnostics.
3. Choose Save SCL on the IED card.
4. Select Edition 2 for .iid or Edition 1 for .icd.
5. Review the SCL, JSON evidence, Markdown summary, and warnings.
6. Import and validate the result in the target SAS or gateway.

For a bounded legacy integration, open RCB, run the read-only availability audit, select exactly one usable RCB, and generate an Edition 1 or Edition 2 CID baseline.

Explore without a live IED

Press Ctrl+Shift+D while no real IED session or GOOSE capture is active. The built-in communication workspace helps users explore the UI and workflow. It is generated presentation data—not a relay simulator, compatibility result, performance benchmark, or conformance proof.

See the bilingual Quick Start, IO List FAT Evidence guide, Guided Demo, FAQ, and Troubleshooting Guides.

Core engineering workflows

IO List FAT evidence

• Import only approved SDI test points with explicit project, IED, object-reference, and expected-state identity.
• Bind imported points to the intended live IED without writing configuration.
• Reject initial ON as test evidence and require a new OFF baseline.
• Preserve ordered ON and OFF transition evidence with quality, source, IED time, ARSAS time, event sequence, and reconnect generation.
• Autosave progress and verify append-only evidence journals.
• Export an immutable-source Excel result copy, native PDF report, or portable .arsas project.

Live MMS engineering

• Maintain independent device sessions and lifecycle state.
• Discover the complete typed hierarchy and available services.
• Search large models without flattening away device ownership.
• Keep the complete model attached even when the operator view hides non-operational attributes.
• Compare configured SCL intent with current live evidence.

Selected-RCB integration export

• Audit availability without enabling, disabling, or reserving an RCB.
• Retain verified live DataSet members and configuration evidence.
• Preserve exact runtime RCB names and prevent duplicate indexing.
• Export a bounded Edition 1/2 CID while keeping original sources unchanged.

GOOSE supervision

• Capture receive-only Ethernet frames through the ARIEC61850 Npcap transport.
• Inspect identity, addressing, sequence, retransmission, TAL, flags, and ordered payload.
• Bind streams to SCL or live discovery where evidence permits.
• Surface mismatches rather than silently truncating data.

Fault-record retrieval

• Browse the selected IED MMS file service with bounded operations.
• Download complete, partial, extensionless, or single-file records actually exposed by the device.
• Support signed FRSM handles, segmented responses, reconnect checks, progress, cancellation, and safe temporary files.
• Detect local record state and provide copyable transfer diagnostics.

Guarded control

• Discover the live ctlModel and exact control descriptors.
• Execute supported Direct or Select-Before-Operate sequences.
• Preserve origin, ctlNum, timestamp, Test, interlock, and synchrocheck context.
• Surface CommandTermination, application errors, timing, and mapped process feedback.

Architecture

┌────────────────────────────────────────────────────────────────────────────┐
│                                   ARSAS                                    │
│ Explorer · IO FAT · Monitor · SOE · GOOSE · SMV · Files · SCL · Control │
│ Project state · Excel/PDF evidence · .arsas packaging · diagnostics      │
└────────────────────────────────────┬───────────────────────────────────────┘
                                     │ typed application services
┌────────────────────────────────────▼───────────────────────────────────────┐
│                                ARIEC61850                                  │
│ MMS · Reporting · GOOSE · SMV · File Services · SCL · Control            │
│ Transport · Type System · Schema Profiles · Diagnostics · Validation      │
└───────────────────────────┬──────────────────────┬─────────────────────────┘
                            │ TCP/102              │ Ethernet process bus
                       Approved IEDs          Approved capture network

Protocol parsing, transport behavior, typed contracts, schema profiles, SCL conversion/export, and reusable validation belong in ARIEC61850. ARSAS owns the Windows workflow, project state, visualization, diagnostics, IO List test coordination, Excel/PDF evidence output, and engineer-facing packaging.

The native IO FAT PDF primitive design is ported from the project-owned ARIEC60870 engine. The IEC 61850 report layout and IO FAT state model are implemented in ARSAS.

Detailed notes: Architecture · IO List FAT Evidence · Engine compatibility

Build from source

Developer requirements

• Windows 10 or Windows 11.
• .NET 8 SDK.
• Visual Studio 2022 with .NET desktop development, or the .NET CLI.
• A compatible ARIEC61850 source checkout.
• Npcap when building or testing raw-Ethernet workflows.

Recommended layout:

D:\Git\
├─ ARIEC61850\
│  └─ src\
│     ├─ AR.Iec61850\AR.Iec61850.csproj
│     └─ AR.Iec61850.Transports.Npcap\AR.Iec61850.Transports.Npcap.csproj
└─ arsas\
   └─ ArIED61850Tester.csproj

git clone https://github.com/masarray/ARIEC61850.git
git clone https://github.com/masarray/arsas.git
cd arsas
dotnet restore .\ArIED61850Tester.csproj
dotnet build .\ArIED61850Tester.csproj -c Release

For a non-sibling engine checkout, pass ArIec61850Project and ArIec61850NpcapProject explicitly.

Documentation and support

Resource	Purpose
Product website	Product overview, workflows, evidence, Indonesian navigation, and downloads.
Quick Start	Verified package to first live value and IP-to-SCL continuation.
IO List FAT Evidence	Workbook import, OFF → ON → OFF evidence, Excel/PDF output, .arsas continuation, and integrity boundaries.
Compatibility evidence	Service-level evidence with version, date, conditions, and bounded conclusions.
Guides	Symptom-led troubleshooting for port 102, reporting, RCBs, files, GOOSE, SCL, control, and IO FAT evidence.
Download Center	Installer/portable comparison, hashes, requirements, and stable release scope.
Documentation hub	Engineering, validation, legal, contribution, and operational documents.
Support guide	Required troubleshooting evidence and sanitization.
Security policy	Responsible private vulnerability reporting.

A successful service observation or IO transition is not a universal vendor conclusion, a protection-function proof, or an IEC 61850 conformance certificate.

Safety, privacy, and evidence boundaries

IEC 61850 control, report configuration, temporary DataSet creation, file access, and other active operations can affect IED resources or equipment state. Use them only inside an approved boundary with suitable isolation, authority, procedures, and independent verification.

The IO List FAT workspace is read-only toward the IED, but the external process simulation or injection used to change the indication still requires an approved procedure, safe plant state, and qualified personnel.

GOOSE and Sampled Values capture is receive-only in ARSAS, but station traffic still requires an approved adapter, network boundary, and data-handling policy.

Do not publish credentials, private endpoints, customer identity, confidential IO Lists, SCL, relay settings, packet captures, disturbance records, or .arsas evidence projects. Sanitize evidence before opening a public issue.

ARSAS is not:

• an IEC 61850 conformance certificate;
• functional-safety certification;
• cybersecurity approval for an operational network;
• automatic switching authority or proof of safe isolation;
• a guarantee of acceptance by every proprietary SCL importer;
• a calibrated protection or process injection system;
• an automatic witness approval, legal signature, or acceptance record;
• a substitute for an approved FAT, SAT, commissioning, or operating procedure.

Contributing

Focused, reproducible, independently authored contributions are welcome. Strong contributions include exact sanitized diagnostics, bounded reproduction steps, fixtures with clear provenance, expected behavior, validation evidence, and a clear application-versus-engine boundary.

Read CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, SUPPORT.md, and NOTICE.md.

License

The community edition is licensed under GNU GPL v3.0 or later. See LICENSE.

A separately negotiated commercial license is available for proprietary integration, OEM or white-label distribution, closed-source redistribution, warranty, maintenance, priority support, training, and project-specific development. See COMMERCIAL-LICENSE.md.

Names, logos, icons, and official-release branding are not granted by the software license. See TRADEMARK.md and NOTICE.md.

---

ARSAS
From an approved IED endpoint or IO List to trustworthy IEC 61850 evidence and reusable project output.