Per-item results
A batch never fails silently: each reading is accepted, flagged as duplicate, or rejected with a reason such as unknown sensor or timestamp in the future.
Technology
/01Telemetry ingestion pipeline
Sensors on pumps, blowers, tanks and analyzers
Per-site key, HTTPS POST MQTT / OPC UA planned
Gateway auth, rate limits Unknown tags rejected per item
Units, timestamps, quality flags Duplicate message IDs ignored
Tenant-scoped time series Deadband + on-delay alarms
Per-connection authorisation Last-Event-ID replay
Live overview, alarms, history & CSV export
Asset context in view Freshness on every value
A batch never fails silently: each reading is accepted, flagged as duplicate, or rejected with a reason such as unknown sensor or timestamp in the future.
Message IDs make retries safe; out-of-order readings are stored by observation time, not arrival time.
High, high-high, low and low-low rules with deadband hysteresis and on-delay, evaluated as readings land.
/02Context awareness
/03Device pairing & identity
Glasses have no keyboard, so they never handle a password. The QR code carries no reusable credential; challenges are single-use, expire after five minutes and are rate-limited against guessing.
The device asks for a pairing challenge and receives a short user code plus a separate device secret that is never displayed.
The viewport shows XXXX-XXXX and a QR link. The alphabet avoids look-alike characters (no 0/O, 1/I/L).
Signed in to the console on another device, they confirm the code and assign the glasses to an operator and sites.
The glasses poll (no faster than every 3 s) and, once approved, exchange their secret for a short-lived device credential.
Lifecycle: unregistered → pending pairing → paired → assigned → connected / disconnected. Any device can be suspended or revoked from the console.
/04Offline-capable sync & realtime
When the network drops, the viewport says so and every value shows its age.
Inspection responses queue on the device and sync in order on reconnect.
One long-lived HTTPS stream per client, with the token in a header — never in the URL.
Last-Event-ID replay closes gaps; sessions are re-validated every 30 s so revoked devices are disconnected.
Safety & reliability
No write path to SCADA, PLCs or field devices. Hydris shows context and records observations; operators act through your existing controls and permits.
Every query runs in the caller’s organisation context, enforced in the database. Realtime events are authorised per connection.
Pairing approvals, device assignments, alarm actions, inspection reviews and permission changes are recorded with who and when.
Role- and site-scoped permissions. Devices get their own short-lived credentials and only see approved documents.
Short-lived access tokens held in memory; refresh tokens are httpOnly, SameSite=Strict cookies and rotate on use.
Per-site gateway keys are stored as hashes and can be revoked instantly from the console.
Simulator data is only accepted in demo tenants and is labelled synthetic wherever it is shown.
Accounts are invited by an administrator; there is no self-registration into a customer tenant.
/05Integrations
| Integration | How it works | Status |
|---|---|---|
| Edge gateway → HTTPS ingestion | JSON batches (≤ 500 readings) with a per-site API key; per-item accept / reject results; idempotent by message ID. | Available now |
| Manual & laboratory entry | Field and lab results entered in the console with source and timestamp provenance. | Available now |
| Realtime stream (SSE) | Server-Sent Events to console and glasses, authorised per connection, Last-Event-ID replay. | Available now |
| History export | Per-sensor history and CSV export for reporting and regulator submissions. | Available now |
| MQTT adapter | Edge adapter subscribing to existing broker topics and forwarding to ingestion. | Planned |
| OPC UA adapter | Edge adapter reading tags from OPC UA servers. | Planned |
| Native glasses adapter | Device packaging for Meta Ray-Ban Display class glasses; today the viewport runs in a browser. | Planned |
/06Future: computer vision & more
We are exploring gauge reading and visual anomaly prompts from the glasses camera. Any such feature will suggest, never decide: the operator confirms what is recorded. None of it is available today.
Planned items describe direction, not committed delivery dates. We will tell you plainly what exists when you evaluate Hydris.
A 30-minute walkthrough: the glasses viewport, the operator console and how your gateway telemetry would reach both. We will be clear about what is available today and what is planned.