Both deliver DataSet changes, but buffering, reconnect behavior and client ownership affect what evidence remains available after an interruption.
Designed to retain report entries according to the IED implementation and buffer policy so a client can request continuity after reconnection.
Delivers reports while the client is connected and enabled, without the same expectation of replaying events that occurred during disconnection.
Do not choose only because one RCB is easier to enable. Start from whether event continuity across interruption is required, whether the IED exposes usable buffered state, and whether another approved client already owns the intended reporting path.
Compare exact member coverage before treating two RCBs as interchangeable.
An available URCB may be safer for temporary testing than disturbing a BRCB used by the operational system.
Buffered status does not compensate for missing members or unsuitable trigger options.
Keep report type, RCB reference, sequence evidence and fallback state visible in the test record.
Validate the actual buffer behavior, reconnect sequence and entry evidence on the specific IED rather than assuming all implementations behave identically.
URCB can reduce interaction with an operational buffered path, but it still requires correct DataSet coverage, triggers and client ownership.
Continue with silent reporting or occupied RCB investigation.
ARSAS can expose live model, report, GOOSE, file, control and diagnostic evidence. Final conclusions still depend on the approved project design, vendor documentation, test procedure, network access and independent verification.
Reviewed 20 July 2026 for practical IEC 61850 laboratory, FAT, SAT, commissioning and troubleshooting use.
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 →