ARVREL
Workflows / FAT/SAT preparation

Rehearsal before formal acceptance

Use deterministic virtual evidence to prepare the test plan—not to replace approved commissioning evidence.

Beta.6 can rehearse feeder secondary injection, process-bus conditions, Transformer Differential, AVR/OLTC behavior, MMS interactions, and evidence review before hardware FAT/SAT.

Feeder rehearsal

Practice the complete cause-and-effect chain.

  1. Freeze settings, CT/VT context, source profile, and expected operate/restrain result.
  2. Run internal closed-loop injection and record relay ANY PICKUP, TESTSET BI2, operated-element pickup/P→T, relay trip request, and TESTSET BI1.
  3. Verify trip auto-stop comes from accepted BI1 only.
  4. Review OUTPUT OFF · FROZEN CAPTURE and schema 9 evidence.
  5. Use the open BO1→BI1 case to prove that relay internal operation is not silently counted as a TESTSET result.
  6. Press RESET once and confirm READY TO RE-ARM before the next run.

Transformer rehearsal

Prove the software baseline before external SV.

Packaged-core self-test

Run the deterministic 10-scenario suite; expected baseline is PASS · 10/10 · transformer-public-beta-v1.

Two-sided internal injection

Exercise stable through load, internal fault, REF HV/NGR, and REF LV/NGR using synchronized HV/LV/independent neutral currents.

Move to paired-SV replay/live only when publisher identity, synchronization, network behavior, or interoperability is part of the test objective.

AVR / OLTC rehearsal

Exercise virtual authority and MMS without physical process authority.

  • Use the simulated transformer and 17-position OLTC.
  • Verify LOCAL/REMOTE and AUTO/MANUAL interlocks.
  • Test MMS browse/read and DataSets first.
  • Then exercise reports, GI/integrity, modeled SBO/SBOw controls, and virtual settings.
  • Record accepted/rejected command cause and resulting virtual plant state.

Process-bus rehearsal

Use replay for repeatable negative cases.

Identity

APPID, MAC/VLAN, svID, dataset, confRev, and SCL binding.

Continuity

Gaps, duplicates, out-of-order frames, restarts, stale windows, and recovery.

Trust

Verify when measurement remains visible but pickup/trip authority is blocked.

Evidence package

Carry forward the assumptions and expected results.

  • Exact ARVREL version and release identity
  • Settings fingerprint and engineering context
  • Source/run identity and virtual wiring where relevant
  • Expected operate and restrain outcomes
  • Timing semantics and clock resolution for feeder closed-loop tests
  • Transformer/AVR configuration and virtual-control authority
  • Trust state and source provenance for replay/live tests
  • Known beta limitations requiring formal hardware confirmation

Acceptance boundary

Formal FAT/SAT still needs the approved procedure and equipment.

ARVREL is preparation, troubleshooting, training, and research software. It does not replace calibrated secondary-injection equipment, approved test sheets, protection-setting governance, site interlocks, commissioning acceptance, or switching authorization.

RelatedProtection engineeringNextEducation and research