- Current product scope · explicit maturity · real evidence
-
IEC 61850 capabilities organized around real testing work.
-
ARSAS connects the live server model, configured SCL context, report behavior, process-bus traffic, fault records, control outcomes and diagnostics to the same IED session. Available, preview and roadmap work remain clearly separated.
Current product scope · explicit maturity · real evidence
IEC 61850 capabilities organized around real testing work.
ARSAS connects the live server model, configured SCL context, report behavior, process-bus traffic, fault records, control outcomes and diagnostics to the same IED session. Use the dedicated pages below to explore each engineering workflow in depth.
AvailableMMS, reporting, GOOSE, files, SCL-assisted workflows, SOE and control
Multi-IEDIndependent association, monitoring, diagnostics and project state per device
PreviewSampled Values engineering and viewer workflow
BoundaryNo universal interoperability, conformance or switching-authority claim
-
-
-
-
Available now
From endpoint to attributable evidence.
The current application covers the highest-friction parts of practical IEC 61850 investigation, integration and validation.
-
- MMS
Live model discovery
Discover Logical Devices, Logical Nodes, Data Objects, Data Attributes, values, quality, timestamps, DataSets, RCBs, control objects and live MMS type descriptors.
Connect directly by approved IP address
Independent association per IED
Searchable large-model workspace
Configured and live context together
- Smart Reporting
Report-first acquisition with fallback
Prefer existing BRCB or URCB coverage, validate exact DataSet membership, recover specific gaps where permitted and keep unresolved points in bounded polling.
Buffered and unbuffered reports
Reservation and ownership visibility
Dynamic DataSet recovery when allowed
Visible degraded-state fallback
- GOOSE
Read-only stream inspection
Capture station or process-bus GOOSE through Npcap and retain stream identity, sequence, retransmission, TAL and ordered payload evidence.
APPID, VLAN, destination MAC and goCBRef
stNum, sqNum, Test and ndsCom
Ordered allData leaves
SCL or live-model binding
- Files
Fault-record retrieval
Probe the MMS file service, browse available directories and download disturbance or COMTRADE-related records in the selected IED context.
Bounded navigation and transfer
Per-IED endpoint ownership
Progress and negative-result visibility
Record-set grouping foundation
- SCL
Configured-to-live integration
Open common SCL files, extract endpoints, compare configured intent with observed server behavior and export controlled integration baselines.
SCD, CID, ICD, IID, SSD and XML input
Edition-aware export services
Selected-RCB Edition 1 or 2 export
Verified DataSet member retention
- Control
Typed Direct and SBO validation
Read ctlModel, resolve live command descriptors, execute supported sequences and show service, termination, timing, error and feedback evidence.
DPC, SPC, INC/ISC, BSC and APC
Direct and Select-Before-Operate
CommandTermination and AddCause
No generic blind-write fallback
- Operations
Live values, SOE and diagnostics
Separate continuous values from semantic events while preserving IED timestamps, quality, report reasons, acquisition source and originating-device context.
Recent-change highlighting
Process timestamp semantics
Bounded event collections
Association, report and frame diagnostics
- Scale
Independent multi-IED sessions
Every IED owns its connection, discovery, selected signals, report state, events, control context, file workflow and diagnostics.
Isolated lifecycle per device
One monitor loop per IED
Coalesced UI updates
Virtualized engineering grids
- Productivity
Reusable project state
Save endpoints, cached model context, selected signals and workspace state so recurring projects do not restart from zero.
Fast reconnect workflow
Retained device definitions
Persisted selections
Reusable diagnostic context
-
-
-
-
-
-
- Integration evidence
Selected-RCB SCL export
Inspect read-only RCB availability, choose the reporting path intended for a legacy SAS or gateway, retain verified DataSet members and export a normalized Edition 1 or Edition 2 baseline.
Per-IED SMV entry points and a viewer workflow are available for controlled evaluation. Production maturity still requires deeper decoding, SCL binding, scaling, quality supervision and sustained-performance validation.
Inspect read-only RCB availability, choose the reporting path intended for a legacy SAS or gateway, retain verified DataSet members and export an Edition 1 or Edition 2 baseline.
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.
MMS file services · relay fault records · COMTRADE retrieval
Retrieve protection-relay fault records inside the correct IED context.
ARSAS uses IEC 61850 MMS file services to probe available directories, browse bounded paths and download disturbance-record files while preserving endpoint ownership, transfer progress and negative service evidence.
Service discoveryProbe whether the connected IED exposes usable MMS file services
Bounded browsingNavigate approved paths without uncontrolled recursive traversal
Transfer evidenceProgress, cancellation, timeout and negative responses remain visible
Record contextGroup COMTRADE-related files around the originating IED and event
+
Fault-record workflow
Move from a relay event to a complete downloadable record set.
Different relays can expose different directory layouts and naming conventions. ARSAS keeps discovery transparent instead of assuming that every device stores files in the same location.
01
Connect to the intended relay
Use the existing per-IED MMS association so file operations remain attached to the correct endpoint and project context.
02
Probe and browse available paths
Inspect the directories exposed by the IED with explicit boundaries, cancellation and visible service failures.
03
Identify the relevant disturbance record
Review filenames, timestamps and companion extensions such as CFG, DAT, HDR and INF without hiding incomplete sets.
04
Download and retain transfer evidence
Preserve source path, destination, progress, retry boundary and negative result details for later engineering review.
+
COMTRADE-aware workflow
Treat a fault record as a set—not just one downloaded file.
A useful disturbance record may include configuration, sampled data, header and information companions. ARSAS provides the foundation to recognize those relationships while keeping missing or unexpected files visible.
CFG configuration file
DAT sampled data file
HDR descriptive header when available
INF or approved companion information
Failure-aware engineering
Negative evidence is part of the result.
An empty directory, access rejection, timeout, unsupported service or partial record set should not be presented as success. ARSAS keeps those outcomes attributable to the originating relay.
Unsupported service remains explicit
Timeout and cancellation remain distinguishable
Partial downloads are not silently accepted
Vendor-specific layouts are not treated as universal
+
Connected diagnostics
Keep file-service failures beside the communication evidence.
File transfer is not isolated from association state, service responses and per-IED diagnostics.
EvidenceAttributable service diagnostics
Separate association, service, relay-behavior and transfer problems instead of reducing every failure to a generic download error.
+
Useful for
Protection and commissioning workflows
Retrieve fault records after relay operation
Collect disturbance evidence during FAT or SAT
Compare record availability across multiple IEDs
Preserve files for COMTRADE analysis tools
Investigate missing or incomplete record sets
Engineering boundary
Downloaded files still require validation.
ARSAS does not prove that a record is complete, correctly scaled or suitable for protection analysis merely because transfer succeeded. Review the record set, time basis, channel definitions and relay configuration using approved engineering procedures.
+
Related capability
Find the relay and its live model first.
Use the MMS client workspace to confirm endpoint identity and retain the correct IED context before browsing files.
Read-only GOOSE inspection · stream supervision · model binding
Turn IEC 61850 GOOSE traffic into attributable engineering evidence.
ARSAS captures GOOSE through an approved network interface and presents stream identity, sequence behavior, retransmission, Time Allowed to Live, flags, payload order and available model context without transmitting GOOSE frames.
Stream identityAPPID, VLAN, destination MAC, goCBRef and DataSet reference
SequencestNum, sqNum, retransmission rhythm and state-change evidence
SupervisionTAL, Test, ndsCom and visible stream health
PayloadOrdered allData values with SCL or live-model binding context
+
Diagnostic workflow
Find whether the problem is traffic, sequence, configuration or interpretation.
A packet list alone is not enough. ARSAS keeps stream-level evidence together so engineers can distinguish absent traffic from stale sequence, incorrect network identity, payload mismatch or incomplete engineering context.
01
Select the approved adapter
Choose the interface connected to the intended station or process-bus segment. Raw Ethernet capture requires Npcap.
02
Identify each publisher stream
Group frames using APPID, destination MAC, VLAN, goCBRef and DataSet evidence instead of treating all GOOSE traffic as one list.
03
Inspect state and sequence
Observe stNum changes, sqNum progression, retransmission behavior and TAL before deciding whether the publisher is healthy.
04
Bind payload to engineering meaning
Compare ordered allData leaves with available SCL or live-model context and keep uncertainty visible when mapping is incomplete.
+
Real application screenshot
Inspect stream details without losing the wider IED context.
The GOOSE workspace is part of the same project environment used for MMS, SCL, reporting and diagnostics.
GOOSEStream supervision and payload inspection
Review publisher identity, APPID, VLAN, sequence, retransmission, TAL, flags, ordered payload and available model binding evidence.
+
Useful questions
What ARSAS helps an engineer verify
Is the expected publisher visible on the selected interface?
Does stNum change when the source state changes?
Does sqNum progress with plausible retransmission behavior?
Is TAL being refreshed before expiry?
Do APPID, VLAN, MAC, goCBRef and DataSet match the intended design?
Can ordered payload leaves be mapped to available engineering context?
Engineering boundary
Capture evidence is not a protection-system acceptance result.
ARSAS does not transmit GOOSE, prove end-to-end trip performance or certify network design. Protection logic, timing, redundancy, subscriber behavior and final scheme acceptance still require approved procedures and independent test evidence.
+
Related context
Use SCL to explain the intended stream.
Compare observed publisher identity and payload order with the available configured model.
Browse the live IEC 61850 server model directly from the IED.
ARSAS connects to an approved IEC 61850 endpoint over MMS, discovers the live model and keeps values, quality, timestamps, DataSets, Report Control Blocks, controls and diagnostics inside the same per-IED engineering session.
Live discoveryLogical Devices, Logical Nodes, Data Objects and Data Attributes
Typed valuesValue, quality, timestamp and live MMS type context
Engineering objectsDataSets, BRCBs, URCBs and control models
Per-IED stateAssociation, selections and diagnostics remain isolated
+
Practical workflow
From an approved IP address to searchable live evidence.
Expose useful protocol evidence without reconstructing the same context across several disconnected applications.
01
Add the IED endpoint
Establish an independent MMS association and keep service failures attributable to the originating device.
02
Discover the server model
Enumerate the logical hierarchy and live type information required for values, reports and supported controls.
03
Search and select signals
Filter large models and select the exact points required for FAT, SAT, commissioning or troubleshooting.
04
Observe attributable values
Retain quality, timestamps, recent-change evidence and the verified acquisition source.
+
Real application evidence
One model browser, one live-value workspace, one IED context.
Inspect current device behavior rather than relying only on a static engineering-file tree.
01Start from the device
Add the intended endpoint or open available SCL context.
02Searchable live values
Review device, quality, timestamp, source and change context together.
+
Useful for
FAT, SAT, commissioning and protocol troubleshooting
Confirm that the IED accepts an MMS association
Compare live object availability with available SCL files
Find DataSets and Report Control Blocks before reporting tests
Inspect ctlModel before control tests
Separate model, service and communication problems
Engineering boundary
An MMS connection is not proof of complete interoperability.
A successful association does not prove that reporting, controls, file services, GOOSE binding or every modeled object is correct. ARSAS keeps those validations explicit and does not claim conformance certification.
+
Next workflow
Move from discovery to report-based monitoring.
Inspect DataSet coverage, BRCB and URCB ownership, trigger options and fallback behavior.
Monitor several IEC 61850 IEDs without mixing their engineering state.
ARSAS gives each IED its own association, discovered model, selected signals, reporting state, events, file workflow, control context and diagnostics while still providing project-wide live-value and evidence views.
Independent lifecycleConnect, discover, monitor and disconnect each IED separately
Unified valuesSearch selected signals across devices without losing ownership
Bounded eventsKeep SOE, report reasons and recent changes attributable
Isolated diagnosticsSeparate association, service, report, frame and device behavior
+
Project workflow
Scale from one relay to a complete test lineup.
Multi-device work becomes unreliable when one global connection, one polling loop or one generic event list owns every relay. ARSAS keeps the runtime boundary per IED and combines only the evidence intended for project-wide views.
01
Create each device session
Add approved endpoints or SCL-derived device context and retain a clear identity for every relay, bay controller or gateway.
02
Discover and select independently
Each IED owns its live model, chosen signals, DataSets, RCBs, control objects and file-service state.
03
Monitor with an attributable source
Values and events keep the originating device, quality, timestamp, reason and acquisition path visible.
04
Review project-wide evidence
Search and compare selected points across devices without collapsing their diagnostics or lifecycle into one ambiguous session.
+
Real application evidence
Independent device sessions with unified engineering views.
The screenshots show the working application handling multiple IEDs, shared live-value review and device-attributable diagnostics.
01Independent IED sessions
Each device retains its own connection, model, monitoring and diagnostic state.
02Unified selected values
Search across devices while retaining source, quality, timestamp and acquisition evidence.
03Bounded event evidence
Separate semantic events from continuous live values and keep the originating IED visible.
04Attributable diagnostics
Distinguish network, association, report, service and device-specific failures.
+
Useful for
FAT lineups, SAT and commissioning projects
Monitor several relays or bay devices from one workspace
Compare similar signals across multiple IEDs
Track SOE and report behavior without losing device ownership
Retrieve files from the correct relay session
Keep control and diagnostic context separated
Performance principle
Scale without turning the UI into the protocol engine.
ARSAS uses per-IED runtime ownership, bounded collections, coalesced UI updates and virtualized engineering grids. The objective is responsive engineering work—not uncontrolled background polling or repainting every value continuously.
+
Related capability
Build each session from live MMS discovery.
Browse the model, select signals and retain current type and reporting context per IED.
Use SCL as engineering intent—then compare it with the relay evidence available now.
ARSAS opens common IEC 61850 SCL inputs, extracts useful endpoint and model context, keeps configured information beside the live IED session and supports controlled selected-RCB export for Edition 1 or Edition 2 integration baselines.
Common inputsSCD, CID, ICD, IID, SSD and compatible XML context
Live comparisonKeep configured intent and discovered server behavior visible together
RCB reviewInspect available and occupied reporting paths before export
Edition-aware outputSelected-RCB baseline export for controlled Edition 1 or 2 integration
+
Configured-to-live workflow
Avoid treating an available SCL file as unquestioned truth.
Engineering files can be incomplete, outdated or created for a different integration stage. ARSAS uses them as valuable configured context while preserving what the connected relay currently exposes.
01
Open the available SCL source
Load the approved project or device file and extract endpoints, model references, communication settings, DataSets and reporting context that can support the task.
02
Connect to the intended IED
Discover the current live server model and keep differences visible instead of silently replacing one source with the other.
03
Review reporting availability
Inspect existing RCBs, ownership and verified DataSet members before selecting a path for downstream SAS or gateway integration.
04
Export a controlled baseline
Choose the intended RCB and Edition target, retain verified members and create a cleaner baseline without blind XML deletion.
+
New integration evidence
Selected-RCB SCL export for legacy SAS and gateway workflows.
Choose the reporting path intentionally and keep the available relay evidence visible during export.
SCLChoose the RCB and target edition
Inspect available and occupied RCBs, select the intended reporting path, retain verified DataSet members and export a normalized baseline.
+
What the export is designed to improve
Reduce avoidable integration cleanup.
Focus the baseline on the selected reporting path
Retain verified DataSet members
Make Edition target explicit
Avoid deleting XML sections without understanding relationships
Keep source and live evidence traceable
What it does not prove
Export is not end-to-end interoperability certification.
The receiving SAS or gateway must still be validated against its supported schema, edition behavior, naming expectations, DataSet handling and report configuration. ARSAS does not claim that one exported file will work unchanged with every vendor.
+
Useful for
Multi-vendor integration and troubleshooting
Compare a CID or ICD file with the live relay model
Investigate missing or mismatched report members
Review RCB availability before gateway mapping
Create an Edition 1 baseline for legacy integration
Preserve configured and observed context during FAT or SAT
Engineering principle
Files and devices are complementary evidence sources.
Use the SCL file to understand intended configuration and the live IED to understand current behavior. A difference is not automatically a relay fault or a file fault; it is evidence that requires engineering review.
+
Related capability
Discover the live model through MMS.
Use current server evidence to assess whether configured objects and reporting paths are still available.
