Start selected MMS reads
Show initial values, quality and timestamps while report objects are inspected.
BRCB · URCB · DataSet coverage · visible fallback
Select the signals. ARSAS builds a defensible acquisition path.
Smart Reporting is not a promise that every selected value will arrive through a report. It is a failure-aware workflow that starts useful MMS reads, evaluates configured reports, proves exact coverage, recovers specific gaps when permitted and retains polling for anything still uncovered or unverified.
ImmediateSelected MMS values begin while reporting is evaluated
Configured firstExisting DataSets, BRCBs and URCBs are preferred
Exact coverageMembers and order are validated instead of assumed
Fallback retainedUncovered or degraded points remain in bounded polling
Per-IED acquisition plan
Static reports first. Specific recovery for gaps. Polling when required.
Every step remains attached to the IED association that produced the evidence, so reporting decisions from one device cannot silently change another.
Discover configured reporting
Read available DataSets, BRCBs, URCBs, references, reservation state and relevant options.
Validate exact coverage
Compare selected signals with actual DataSet membership and order rather than relying on names alone.
Recover specific gaps
Use temporary DataSet coverage with a suitable available RCB only when the IED and approved procedure permit writes.
Retain visible fallback
Keep rejected, uncovered, unverified or degraded points in a bounded polling schedule.
No report dead end.An empty DataSet, occupied RCB, rejected write or silent stream does not have to block the live-value workspace.View the complete capability scope →
Problems the workflow makes visible
Communication success does not prove reporting success.
ARSAS keeps negative evidence visible so the engineer can distinguish association, configuration, ownership, trigger and delivery problems.
Empty or incomplete DataSet
An RCB can exist while its referenced DataSet is empty, incomplete or different from the signals required for the test.
RCB already reserved
An unbuffered or buffered report may be owned by another client, reserved by configuration or unavailable for the current association.
Configured coverage mismatch
A promising DataSet name is not proof that every selected signal is present in the required order.
GI without spontaneous updates
A successful general interrogation can return an initial image while change-triggered reports remain absent or incomplete.
Rejected dynamic recovery
The IED may reject DataSet or RCB writes because of capability, access control, configuration or active ownership.
Degraded report stream
Missed changes, association loss or invalid delivery evidence can return affected points to bounded polling.
Every update keeps its origin.
- IED and association context
- Value and quality
- IED or process timestamp
- Report reason where available
- Report, polling or other acquisition source
- Coverage and degradation diagnostics
Automation does not remove approval requirements.
- Configured reports are preferred before writes are considered
- Dynamic recovery is conditional and explicit
- Polling remains a valid fallback, not a hidden failure
- IED access, project procedure and test authority remain external requirements
- No universal reporting interoperability claim is made
Real application evidence
Live values remain attributable across multiple IEDs.
The same workspace shows selected values, quality, timestamps, source and recent-change evidence while each IED retains an independent acquisition lifecycle.
EvidenceUnified live-value workspace
Selected signals from independent IED sessions retain device, value, quality, time and acquisition context.
Verified stable release
Download ARSAS 1.6.17 for Windows.
Use the installer for a normal workstation, choose the portable ZIP for a controlled folder deployment, and verify the published SHA-256 before use.
What’s new, limitations and signing status →