The historian companies would build for themselves.
- Status
- In development
- Pilots
- Seeking additional pilot operators for 2027
- Priced
- By the well or the facility, not by the tag
- Posture
- Read-only. It never writes to control
Why now
Fewer people are covering more wells. More of the decisions are getting made away from the pad. Work that took an engineer a week is starting to be done by a model in an afternoon.
Every one of those runs on history. That is the part that has not kept up, and the tools built for the way the business used to run are not going to close the gap.
Built with operators
Energy is critical infrastructure. The companies that run it should have a say in the software that holds their history. We are early, which is the most useful moment to be told we have something wrong. If you run an operation, or you used to, write to me directly.
What we build
Tacitus is the operations historian we are building.
- A time-series store built for OT Real field scan rates and real retention.
- An asset model treated as the product General enough that any company can model itself in it. The assistant proposes it from what is already arriving.
- Real-time calculations and analytics Rates, efficiencies and rollups computed as data arrives and kept as history.
- Episodes When something happens, like a compressor going down, it is kept with its start, its end and the readings around it.
- Alarm intelligence A cascade of alarms collapsed to the condition that caused them.
- AI in every part of it Building the model, writing the calculations, watching the alarms, answering the questions.
How it works
From the field, at the resolution you choose
Every tag lands on its asset in your asset model
Calculations, alarms and episodes as it lands
History you can trust, bad readings set aside
Back where you need it
The asset model
A pressure reading is just a number until you know which well it came from. The model is built to hold any operation, however yours is actually shaped.
Built from what you already have
Your SCADA's device types and your own lists, like a well master, kept in step on a schedule.
Set it once on a type
Write a calculation or alarm once for every compressor. A new compressor picks it up the day it arrives.
One asset, counted several ways
A meter can sit on a route and inside a gathering system at the same time.
Reorganize without rewriting history
Move a well to a different route in March and February’s totals stay as they were.
AI and agents
Agents propose your asset model, draft calculations and alarm rules, and answer questions about your history in plain language. They can do that because the asset model tells them what every number is attached to.
None of it takes effect until a person accepts it.
How it is priced
An E&P company counts wells. A midstream company counts facilities. We bill against whatever you already count.
Add sensors, raise scan rates, keep the history longer. None of that changes what you pay.
Where we are
We start in upstream and midstream oil and gas, taking data in over MQTT Sparkplug B. The same architecture carries into the rest of energy, and into any industry that runs on real-time operational data.
Tacitus is in development. We are looking for additional pilot operators for 2027.