What happened
The value, the limit, the time and the equipment when the pressure limit was exceeded.
[ Energy, oil and gas ]
From the sensor to the investigation.
A plant produces millions of readings and a few events that someone must answer for. Tabellix keeps those events, the procedures in force when they happened and the investigations they open. Raw telemetry stays in the historian.
01 What gets asked
What regulators and investigators ask.
After an incident, the questions are about the minutes before it and the paperwork behind them.
01
02
The procedure in force
The operating procedure version that applied at that moment, on that unit.
03
The response
Who acknowledged the alarm, when, and what happened next.
04
Management of change
For a modification to equipment or a procedure: the impact assessment, the approvals and the procedure versions it changed.
05
Contractor briefing
Which contractor received which version of the procedure, and what they opened.
06
The investigation file
The investigation file, complete and unchanged, without access to your network.
02 How Tabellix answers
Events, not telemetry.
01
Exceedances captured once
Your historian or control system sends exceedances through the API, up to 100 records per call. A source reference already captured is recognized instead of stored twice, and each record locks at capture.
02
Pinned to the procedure in force
An exceedance links to the operating procedure version in force when it occurred, and that link never moves, even after the procedure is revised.
03
Acknowledgements on the record
An alarm acknowledgement is its own event record with the person and the time, and late entries are flagged at capture.
04
Management of change as a case
A change request links the affected documents, pinned to their versions, and moves through approvals signed with their meaning. Workflow tasks carry owners, delegation and overdue marking.
05
Contractors without seats
Procedures reach contractor companies through expiring, watermarked shares, with an agreement before content and a report of what each recipient fetched.
06
Investigations for the regulator
Release the investigation as a sealed bundle the regulator verifies offline, or open an inspector session: read-only, fixed in scope, for at most 72 hours.
03 Typical records
What becomes a record.
The historian keeps every reading. Tabellix keeps what someone must answer for.
| Record | Kind | What it holds |
|---|---|---|
| Operating procedure OP-0310, compressor startup | document | Draft, review and approval with signatures; effective on a scheduled date; periodic review on schedule. |
| Pressure exceedance, separator V-101 | event record | Value, limit, time and equipment from the historian, captured once and linked to the procedure version in force. |
| Alarm acknowledged | event record | Who acknowledged it and when, flagged if entered late. |
| Incident investigation INV-0057 | case record | Opened from the exceedance; the exceedance, the acknowledgement, witness statements and the window export as members. |
| Window export around the event | document | The readings around the exceedance, kept as their exact CSV bytes and signed over their content digest. |
| Management of change MOC-0212 | case record | Affected equipment documents pinned to their versions; impact assessment and approvals as lifecycle steps. |
05 FAQ
Common questions.
01Does Tabellix store our process data?
No. Raw telemetry stays in the historian or time-series store built for it. Tabellix keeps exceedances, acknowledgements, calibrations, overrides and the investigations they open. Raw data becomes a document only when it is itself evidence, such as an export of the window around an event.
02Can it run on our own network?
Yes. It runs on Kubernetes in any cloud or on premises, and is designed for air-gapped networks, with no dependency on a cloud provider. The license is verified offline, and the software never calls home.
03Can agents help with an investigation?
An agent can gather the exceedances, acknowledgements and procedures behind an incident and draft the investigation summary. You decide which writes wait for a person to confirm out of band, and every tool call is on the audit trail.
04How does an operations or HSE software vendor embed Tabellix?
Your product keeps its dashboards, permits and maintenance screens. It captures events through the API, receives committed events through signed webhooks or an optional NATS JetStream bridge, and ships Tabellix under your brand.
[ Contact ]
Build your product on proof.
Tell us what you build and who audits it. We'll show you how Tabellix fits into your product and how it answers your auditors' most common questions.