Find what the IED really exposes
Connect to a reachable IED, build the live model and keep identity, logical hierarchy, DataSets, report controls and services together.
Capability map · plain-language entry · deep detail on demand
Choose the engineering job first. Open protocol detail when you need it.
ARSAS keeps discovery, monitoring, traffic inspection, SCL, fault records, control and project evidence inside the same IED context. Start from the result you need; each dedicated page then exposes the exact IEC 61850 objects, states and limitations behind it.
Six capability domains
Follow the engineering job, not a wall of protocol acronyms.
Plain-language outcomes stay at the top. The protocol-level detail remains available one layer deeper for commissioning, protection and integration work.
Watch values, alarms and sequence of events
Keep values beside quality, timestamps, IED identity and acquisition source so operational evidence stays attributable.
See IEC 61850 traffic in device context
Inspect GOOSE and bounded SMV capture together with the engineering references that give the network messages meaning.
Exercise approved workflows without losing context
Use guarded controls, DataSet/reporting paths and FAT/SAT workflows while keeping the tested device and result visible.
Retrieve relay records and investigate the event
Browse relay files, download COMTRADE groups and move directly into waveform and protection-timeline analysis.
Keep configured intent and observed behavior reviewable
Preserve SCL source, live observations, provenance, diagnostics and bounded output so another engineer can review what was actually seen.
Investigation workflow
When something happens, follow the evidence from network behavior to the disturbance record.
ARSAS keeps these views connected by IED and engineering context. Start with the clue you have; move deeper only when the next source can answer a new question.
Inspect GOOSE identity, sequence, timing and payload context; use bounded SMV capture where the workflow applies.
GOOSE analysis →Keep signal reference, state, quality, IED time, receive context and acquisition source together.
Event evidence →Stay inside the originating IED session, scan remote files and preserve completeness and transfer state.
Retrieve records →Open the record in ARSAS and inspect synchronized analog/digital evidence, trigger position and protection channels.
See native analysis →Compare the available times and states across sources while keeping clock, source and acquisition differences visible.
Review evidence boundaries →Correlation is not automatic causation proof.GOOSE capture time, IED event time, Reporting receive time and COMTRADE time can come from different clocks and acquisition paths. ARSAS helps keep them reviewable; protection acceptance still requires the approved test method and independent engineering checks.
Dedicated product pages
Choose the engineering result you need.
Each page explains the workflow, evidence available in ARSAS, current limitations and the relationship between configured intent and live device behavior.
Ordered Digital-Indication Evidence
Import approved SDI points, bind them to one IED, require OFF → ON → OFF evidence, and export Excel, native PDF or a verified .arsas continuation project.
Live Discovery to IID or ICD
Discover the complete typed model from an IED on an authorized engineering, FAT, SAT or commissioning network and generate a schema-aware Edition 2 IID or Edition 1 ICD with companion evidence.
Generic Single-IED Output
Open SCD, CID, ICD, IID or SSD context, preserve the source and create bounded single-IED output with structured interoperability findings.
IEC 61850 MMS Client
Connect to a relay on an authorized test, FAT, SAT or commissioning network, discover the live hierarchy and inspect searchable values, quality, timestamps, DataSets, RCBs and controls.
Alarm Annunciator and SOE
Monitor active, unacknowledged and returned alarms by IED, then review sequence-of-events evidence with device time, quality, state and acquisition source.
Smart Reporting
Prefer verified BRCB or URCB coverage, evaluate exact DataSet membership, recover permitted gaps and keep visible fallback. Live RCB selection shows concrete runtime instances actually exposed by the IED.
GOOSE Analyzer
Inspect APPID, VLAN, destination MAC, goCBRef, stNum, sqNum, TAL, retransmission, flags and ordered payload evidence.
Fault Records and Native Analysis
Browse and download disturbance records through MMS, then open them in-process for synchronized time signals, RMS, exact cursors, Phasor, Harmonics, six-loop distance Locus and a digital protection timeline. Display easing never changes authoritative engineering values.
Runtime Instances, Canonical Source Export
Inspect concrete live instances such as Buffer01/02 or Unbuffer01/02 when exposed by the IED. For source-backed export, preserve the canonical logical ReportControl and RptEnabled indexing metadata instead of duplicating runtime slots into the saved engineering model.
Command Dock
Keep validated command objects close to live values and events; read ctlModel and execute supported Direct or Select-Before-Operate sequences with visible checks and outcomes.
Multi-IED Monitoring
Keep associations, values, events, files, controls and diagnostics isolated per device while reviewing project-wide evidence.
FAT, SAT, commissioning and integration
Apply the available capabilities to the project stage you are preparing for, with focused workflows and explicit evidence boundaries.
Sampled Values
Per-IED SMV entry points and a viewer workflow are available for controlled evaluation. Production maturity still requires deeper decoding, binding, scaling and sustained-performance validation.
Verified stable · ARSAS 1.6.41
Ready for an approved Windows workstation?
Installer and portable packages share the same application scope. Verify the published SHA-256 and review the release boundary before field use.
Release notes, limitations and signing status →