Other Features
The things that sit behind every module: one central database the whole suite shares, BINGS Launcher where everyone signs in, and the office tools built into it — production targets and the crew metre bonus.
Why it matters
One central database for every module
Every BINGS module reads and writes the same company record, so information entered in one place is already there in the others.
- Sites and rigs are set up once in BINGS Launcher and appear in Run Book, Stock, People and Assets
- Metres logged in Run Book feed production targets and the metre bonus
- The People roster tells the metre bonus who actually worked each shift
- Drill rigs join the Assets register automatically, and stock is issued against the same rigs
- Each company's data is kept separate from every other company's
One sign-in: BINGS Launcher
Everyone signs in at one address and opens their modules from there, with a Back To Launcher button in every module.
- One device per login: if the same login signs in somewhere else, the first device stops with a clear message, and anything it hadn't uploaded yet still goes up
- Every module's Settings → About shows when the device last synced, with a Sync Data Now button
Company setup and access
The Company page holds your Sites, Rig Fleet and Users in one place.
- Add sites and rigs once, and move rigs between sites as they relocate
- Invite users and give each a role for what they can see and do
- Limit a supervisor to their own sites, so they only see those sites' holes, stock and crews
- Plans are priced per rig, with extra logins added when you need them
Production targets
Set a yearly metre target for each site. It splits evenly across the months, and any month can be changed — a shutdown, say — with the rest re-sharing what's left.
- Headline figures for the year target, target to date, actual to date and how far ahead or behind you are, with the metres a month needed to still finish on target
- Average metres per shift year to date — from the shifts recorded in Run Book, or from calendar days at two 12-hour shifts a day
- A running-total chart of target against actual, and a month-by-month table — for one site or every site added together
- Actual metres come straight from Run Book; an admin can type over any month when needed
Metre bonus
Enter metres per rig and shift — or fill them straight from Run Book's shift records — and BINGS works out every driller's and offsider's bonus for the pay period, using who actually worked each shift from the People roster.
- Pooled across the site, pooled per rig, or paid shift by shift on each rig's own metres
- Paid as a rate per metre, a threshold then rate, or set bands — with different rates for each level, and banded rates if you want them
- Specialised drilling and full-shift mine delays count as set metres
- Single-operator shifts paid as normal, double, with a percentage loading or a set amount
- Bonus deductions — the whole bonus, a percentage, or a number of shifts — with a reason and whether disciplinary action was submitted
- Export the payroll file, the bonus sheet PDF and the metres sheet for the period
Locked schemes
Once a bonus scheme is set up it's locked, so rates and rules can't be changed by mistake. Changing it means pressing Edit Scheme on purpose, and Cancel puts everything back.
Needs signal
BINGS Launcher is office work (company setup, billing, production targets and the metre bonus), so it needs a connection. Everything on the rig is logged offline in the modules and syncs when it can.
Where it is right now
The central database and BINGS Launcher run every module today. Production targets and the metre bonus are built and in testing before they're called field-tested.