SHIFTLEDGER / STAGE CONSOLE / FICTIONAL DATA
Record the stage.
Watch the pressure.
Chase the cause.
A working simulation of data-van duties: parameters recorded and sent before a stage starts, alerts that tell the supervisor why, deliveries checked against the schedule, and an evidence checklist for maintenance and engineering.
Nothing here connects to equipment or a real Performance Center. Data is simulated and the logic is the tested code from the repository. The point is the workflow and its rules.
01 / Record and transmit
No parameters,
no stage start.
Performance Center log
| Stage | Seq | Checksum | State |
|---|
02 / Monitor and alert
Replay a stage.
Choose what goes wrong.
Use your own data (CSV from any tool)
Paste or choose a CSV export with a time column plus treating pressure and rate. Units in headers (psi, kPa, MPa, bar; bpm, m3/min, L/min) are converted. Nothing leaves your browser.
Start a replay. The stage must be started first.
Treatment summary and pressure trend
Run a replay to see totals, horsepower, proppant against plan and the pressure trend.
How these are calculated
Hydraulic horsepower is wellhead pressure times rate divided by 40.8. Slurry and proppant totals add up rate over each ten-second interval, with proppant approximated from the clean-fluid concentration. The pressure trend is the slope of net pressure against time on a log-log scale, in the style of Nolte and Smith: net pressure is surface pressure minus the reference you enter. Surface pressure includes friction, so treat the reading as a hint for engineers. This is not a fracture simulator and does not replace tools like FracPro.
03 / Supply
Know before the
stage needs it.
| Order | Item | Needed for | Status | Next action |
|---|
04 / Root cause
Evidence first.
Owners named.
Run a replay with an alert, then choose it. The package lists evidence from the data and candidate causes to verify. It never states a cause.
No alert selected.
Work order draft
A request preview for whatever maintenance system you use. Nothing is sent. Pick a profile, then rename any field the target system calls something else.
Choose an alert above.
05 / How this compares
Where it fits.
Where it does not.
| Tool type | Strong at | This console’s angle |
|---|---|---|
| Frac analytics (for example Corva, NexTier IntelliStim) | Live treatment data, trends, sensing, field and office collaboration | Does not replace them. It adds the rules around the data: the start gate, the record trail, supply and cause follow-up. |
| Maintenance systems (whatever your company runs) | Asset records, work orders, parts and permits | Drafts the work order from stage evidence, with owner and checklist filled in, in a shape you can map to your system. |
| Mobile field apps | Offline work, checklists, voice and photo capture | Offline-safe by design too, and the sequence checks stop duplicate or tampered records from counting twice. |
Comparison drawn from public vendor pages and not from using those products. Matthew has not benchmarked this against them.
What this is not
It is not connected to pumps, sensors, a data van or a Performance Center, and thresholds are examples. Real use needs the company’s limits, signed-off alarm rules, and safety review. Alerts here support people; they do not control equipment.