Run Book
Run Book is BINGS' most mature module — a live, multi-user run sheet system that's been field-tested with real crews on site, and the design reference the rest of the suite is built against.
Why Crews And Offices Use Run Book
The Drill Run Ledger
Every run is logged as a row: rod number, rod string length, run type, From/To depth, Stick Up, Drilled, Recovered, and Rec%. Enter Stick Up or Drilled on a row and the other derives automatically, along with the running rod string length and next row's starting depth.
- New Rod, Same Rod, Barrel, Same Barrel, and Custom Length run types, each tracked with their own rod numbering
- "Continue" marks a run where the tube stayed downhole — measurements defer to the next row instead of being forced in early
- Exports to a clean, printable PDF — if an error turns up during core processing at the core farm, there's a legible run log to check it against, instead of hunting for a paper sheet that's gone missing or become too dirty to read
Fewer Manual Calculations, Fewer Errors
The numbers that used to mean a separate calculator, a notepad, or working it out in your head happen automatically as you log a run:
- Rod string length tallies itself as rods and barrels are added — no running total to keep track of by hand, no more mis-calculations from a non-standard rod (like a 2m rod) getting missed in the tally
- Stick Up, Drilled, and hole depth To all derive from whichever field you actually entered, instead of needing every value worked out separately
- Recovery % calculates itself the moment Drilled and Recovered are both in — a number that, on paper, often wasn't captured at all
- An over-drilled flag catches a run that's come out physically impossible — depth exceeding the rod string — right when it's entered, not days later when someone reviews the sheet
- Survey shots are checked against tolerance automatically, so a dip or azimuth that's drifted out of range gets flagged at the moment it's logged
Shift Start And Finish
A run sheet follows a hole across as many shifts as it takes, so each crew presses Start Shift when they take over the rig and End Shift at handover. The date, day or night, and the hole depth at both ends are filled in from the last run, so the metres for every shift are recorded without anyone adding them up.
- Each shift can be marked as normal drilling, specialised drilling or a full-shift mine delay
- Forget to end a shift? The next crew starting theirs, or submitting the hole, closes it off at the right depth
- Those shift metres can fill in production targets (and, with BINGS People, the metre bonus) in BINGS Launcher, and can still be changed by hand there
- With RigLog, each shift's metres and surveys go onto that shift's rig log
Downhole Survey Registry
A separate survey log tracks dip and azimuth shots by depth, and automatically calculates variance against the planned trajectory for the first shot and against the previous shot for every one after — flagging anything outside tolerance. Changes are worked out from the figures shown on screen, and azimuth goes the short way round north. Survey reminders prompt the crew at the depths a shot is due.
Built For A Rig With No Signal
Every entry saves to the device first. When the connection comes back, queued changes sync automatically — and each sheet shows its own save status (synced, saving, or saved locally offline), so whoever's using it always knows where things stand.
- Nothing to remember to press. Every driller knows a survey pad or drill plod that never made it back because someone forgot to sync it at the end of a long shift — Run Book syncs itself the moment there's a connection, whether that's minutes later or after driving back into range
- Settings → About shows when the device last synced, with a Sync Data Now button for anyone who wants to check before they leave
Role-Based Access
Rig operators log runs and update hole status from the rig. Supervisors see every hole and run sheet across their sites and manage holes and settings. Company admins manage sites, rigs, logins and billing across every site the company runs.
- A rig login only ever works on its own rig's run sheets — it can't start or change another rig's
- Once a run sheet is submitted it's locked, so late saves from another tablet can't change it. Only a company admin can correct it
- If the sheet you have open is changed on another device, Run Book tells you, and a hole that has run sheets can't be deleted by mistake
- One device per login: if the same login signs in on another device, the first one stops with a clear message — and anything it hadn't uploaded yet is kept and still goes up