RenniLink AlcoMaster Companion is the officer field app: pull results from a supported breath-test kit, store them offline in a local SQLite database, then send to a named destination folder (e.g. Box path) when online. Productised for supported field kits; multi-vendor adapters in field scope. An optional tray Agent keeps the send queue moving when the UI is closed.
Built for the cable moment: retrieve from device, queue destinations offline, seal exports with integrity sidecars, and let the Agent finish transfers after the shift.
Retrieve Data From Device connects on the selected COM port, pulls results, and saves to local SQLite. After a pull, Send (pick a named destination) is required before the next Retrieve — offline is fine: Send assigns the queue. Auto / Agent only retries results that already have a chosen destination.
Up to six nameable upload folders in Settings. Send binds unassigned results to the chosen path only — no silent multi-dump.
Background process: status, Send now, open Companion, run at Windows sign-in, exit. Poll every 60s + on network online. Shares flush lock with UI (no double-send). Intune / installer can write machine-wide Run key.
A durability-first offline vault for the shared UI/Agent queue — power-loss-minded writes, verified snapshots, and recovery that refuses silent loss. See Field store engine.
Successful Send shows path + SHA-256 + CRC-32; destination file is record of truth.
Sidecars *.xlsx.sha256 / *.xlsx.crc32.
Append-only audit for retrieve / send / seal / calibration / restore.
Default Warn if device overdue (site can set Block). Results kept 30 days after creation; deleted only if successfully sent — never-sent results kept until sent.
Companion’s offline store is a purpose-built field vault, not a thin wrapper around a default SQLite file. One database serves both the officer window and the tray Agent. Until a result is sealed to its destination, that vault is the shift’s working memory — so the engine is shaped around survival, recovery, and honest evidence, not a catalogue of toggles. It never shares state with AlcoMaster Control.
Commits run through a power-loss-minded journal (WAL with strict synchronous behaviour), checkpointed often enough that an abrupt shutdown does not strand a day’s work in an oversized log. Clean exit folds the journal and refreshes a snapshot when the queue has moved. When the volume is critically short of free space, the engine refuses further writes: better a clear pause than a half-written store.
Integrity is part of the open path, not a later diagnostic. Structure is checked when the vault wakes and again while it works; residual shared-memory files from a crashed process are cleared before a healthy file is mistaken for a broken one. Corruption is quarantined with a reason — not papered over — and recovery promotes the newest backup that still proves sound.
FieldCritical treats backup as continuous discipline, not a nightly afterthought. Verified cold copies roll in the product vault, with a secondary mirror on the machine so one damaged tree does not strand the queue. Retrieve and Send — the moments that matter — trigger an explicit verified snapshot, so the last known-good state tracks real field work rather than a fixed clock alone.
UI and Agent open the same vault by design: one can pull while the other finishes a send. Cross-process locks keep restore, backup, and flush from racing each other; contended access waits and retries instead of discarding the queue. Single-instance guards and crash logs sit beside the store so the field PC stays one coherent system, not two apps fighting over a file.
Resilience without authenticity is incomplete. Machine-local signing on cold backups means restore will not quietly accept a planted substitute when a key is present; CRC sidecars catch truncated or bit-rotted copies before they are promoted. The vault is hardened with best-effort NTFS access control on the host. Unsent results are never auto-purged — retention only releases what has already been successfully sent.
When a package leaves the device, the destination file is the record of truth: sealed with digests the officer can see, not merely a green tick in the UI. An append-only audit trails retrieve, send, seal, calibration, and restore — who, which machine, which result — without rewriting history. The vault itself is standalone: its own install, own data root, own keys and locks — independent of the Control console on any other desk.
Device panel, full session with history and upload paths, settings.
Not available as a public download yet. Register interest for evaluation and Intune packaging discussions. Admin analytics: AlcoMaster Control.