Choose based on what you already have: a reachable relay for live discovery, or an IEC 61850 engineering file for offline inspection.
Use the relay IP address on your authorized test, FAT, SAT or commissioning network. ARSAS connects over IEC 61850 MMS, discovers the live model and lets you choose what to monitor.
SCL means Substation Configuration Language. These XML files describe IEC 61850 devices and project configuration, so you can inspect the model before making a live connection.
Use Discover IED by IP for a reachable relay. Use Open SCL / CID / ICD to inspect a vendor or project model offline; IID and SCD are supported by the SCL workflow too.
ARSAS connects over IEC 61850 MMS on port 102, reads the real IED identity and builds its live model. If you chose an SCL file, ARSAS opens that configured model without making a live connection.
Start quickly from a discovered static DataSet or select signals manually. Live Monitor shows value, quality and timestamp; validated control objects appear in the guarded Command Dock for authorized test procedures.
ARSAS keeps the first step understandable for learners and field engineers, then exposes deeper IEC 61850 detail as the task requires it.
Understand IEDs, MMS, Reporting, GOOSE and SCL in plain language, then see each concept on a real workflow.
Connect to a relay on an authorized test network, discover the live model and read values with quality and timestamps.
Use ARSAS for repeatable FAT evidence, site re-verification and controlled commissioning support.
Compare configured intent with observed live behavior and build bounded evidence for multi-vendor IEC 61850 integration.
Start with the result you need. ARSAS keeps the first explanation simple, then opens the exact IEC 61850 detail when you need it.
Connect by IP and let ARSAS build the live IED model—identity, logical devices and nodes, DataSets, report controls and available services.
Explore live discovery →Open ICD, CID, IID or SCD, or create bounded IID/ICD output from live discovery while keeping configured intent and observed behavior distinct.
Explore SCL workflows →See measurements and status together with quality, timestamp, alarm state, sequence-of-events context and the IED that produced them.
Explore monitoring →Inspect GOOSE traffic and evaluate Sampled Values in the current engineering preview. Raw-Ethernet capture requires approved Npcap and network visibility.
Explore GOOSE analysis →Download disturbance records, then open COMTRADE inside ARSAS for waveforms, RMS, phasors, harmonics, distance locus and event timelines—without launching a separate viewer.
Explore fault records →Capture Value 1/2, quality and timestamps; review file-service and time-sync evidence; preview the report, add your company logo and save a printable PDF. Controls remain subject to approved procedures.
Explore test workflows →ARSAS is designed to keep engineering observations attributable and reviewable rather than presenting disconnected values, packets or files.
This is one of ARSAS’s core workflows: live discovery builds an observed device model first; only then do you choose what should be monitored, compared or exported.
Discovery shows the running server: identity, object hierarchy, current DataSets, concrete report-control instances and service evidence.
ICD, CID, IID or SCD can carry configured intent and project relationships that a single live IED cannot reconstruct on its own.
Once the first connection makes sense, these real ARSAS surfaces show how the same IED context expands into alarms, FAT, Reporting, SCL, fault records and disturbance analysis.
See alarms from multiple IEDs in one place. Active, unacknowledged and returned states stay separate and tied to the device that produced them.
Run repeatable indication checks and keep before/after values, quality, timestamps and result together as reviewable FAT evidence.
An RCB controls how an IED sends report data. Inspect the live RCB, the DataSet it carries and whether that reporting path is available.
Inspect the IEC 61850 engineering model and prepare bounded IID or ICD output while keeping the source and generated evidence explicit.
Find disturbance records on the relay and download complete COMTRADE file groups without losing which IED they came from.
Review disturbance waveforms and protection events on one timeline, then drill into RMS, phasor and event detail when the investigation needs it.
Published 13 October 2026. Package identity is backed by SHA-256 and exact tagged-release evidence; Windows publisher-signing status remains disclosed in the Download Center.
ARSAS does not ask you to trust a logo or a black box. Source, package identity, automated regression evidence and field boundaries remain independently reviewable.
The ARSAS application, ARIEC61850 engine, commit history and public issue trail are visible. Open source means the implementation can be reviewed—not that correctness is assumed.
Open ARSAS source →Stable v1.6.41 is tied to source commit e581a26dea5545034378adbeed5b78fc80aab773. The tagged release publishes SHA-256 checksums, an SPDX SBOM and provenance evidence for the release assets.
Application regression tests, Smart Discovery production-route guards, website/evidence validators and release checks run in CI. They catch regressions inside their declared scope; they do not simulate every physical relay.
Inspect CI history →Compatibility evidence is published per service and condition. Known limitations, negative outcomes and cases requiring physical-relay validation stay visible instead of being converted into broad compatibility claims.
Review field evidence →