FRAC PANE
What it's designed to do: One frac job, one shared record, every party: sand, trucking and pumping, with each party signing its own facts and money private to the parties it belongs to.
[ THE PROBLEM IN THE FIELD ] internal · product spec
On a frac job the operator, the pumping crew, the sand supplier and the trucking carriers each keep their own log. The company man stitches the job together by radio, by phone and by walking the pad. When a stage waits on sand or a truck sits in line, the logs disagree, and the argument comes back later, over an invoice.
What it's designed to do.
internal · product spec and gate record
- Designed so every party writes its own facts into one record for the job, and signs them.
- FRAC PANE is designed so each role gets its own screen: company man, frac crew, supply desk and driver, and the office.
- Designed so a question put to the job is answered from the record, or refused with exactly what is missing.
- Designed so that where two sources disagree, both stay on the record.
- Designed so a contract's money stays private to the parties on that contract.
[ WHO IT'S DESIGNED FOR ] by role · internal · product spec
Company man
The operator's supervisor on location; will run the job and open the stops.
Frac crew
Will run the stages and the pump fleet, and record standby.
Supply desk
Will work the sand queue and what the next stage needs.
Truck driver
Will carry a load and report arrival, staging and offloading.
Operator's office
Completions, operations and finance, who will read the same record.
[ WHAT'S PROVEN ] internal · gate record
In a test, after completed appends, the sequencer was killed and restarted; it reloaded and verified the same record.
The release build reproduces byte for byte.
[ HONEST STATUS ]
Engine built and independently gated. V1 app in build.
[ SCREENS ]
No screens are published for FRAC PANE on this site.