BBGI-OPS · for investors
Every duty, risk and signature on one live board.
Organizations that run many sites — campuses, offices, data centers, plants, venues — still run their rounds on radio, paper logbooks, group chats and spreadsheets, so a month later nobody can prove which door was checked, by whom, and what happened after the alert. BBGI-OPS is where the round happens, so the record writes itself: every step, the signature, the evidence, and a command center that sees every site at once.
Everyone on the site, and the one who sees them all
The people on site, reception, supervisors, the control room, regional managers and contractors — one board, one trail, their own view of it.
The people on site
The cockpit is one live timeline of the day: every duty with its steps, the risk falling as they are ticked, join or take over, a co-signature where four eyes are required. The handover lists the signatures you owe.
The control room and regional managers
The command center folds understaffing, alerts, overdue duties and open issues into one 0–100 risk index per site, ranks the offices by it, and drills from a red number into the duty behind it.
Contractors and their clients
Outsourced staff have their own roles and work queue; a vendor's duty carries the same steps, evidence and signatures as the company's own staff. Twelve roles in three tiers, with a visible permission matrix.
Why now
Every site still runs on scattered tools
Campuses, offices, data centers, plants and venues run their rounds, responses and handovers on radio, group chats, paper logbooks and spreadsheets — and the client, the insurer and the auditor increasingly ask to see the work proven.
The people are the bottleneck
Site teams are hard to hire and hard to keep. Every hour a supervisor spends finding out which door was checked, by whom, is an hour nobody can hire back.
Proof is what the client pays for
A round walked on radio and paper cannot be proven a month later. Evidence per step, a named person on each, and a trail written every time are what a site contract is really paid for.
One answer spawns the next work
Not a logbook filled after the round: the round itself. A step's answer — “damage found” — raises the report and the follow-up round by itself, and the command center's risk moves.
How it earns
Software an organization pays for per site it runs on the board.
Per site, monthly
An organization runs BBGI-OPS for its regions and sites for a monthly fee per site: the cockpit, the procedures, the roster, the command center and the evidence room.
Contractors on the client's board
An outsourced contractor works inside its client's sites with its own roles and work queue — the client pays for the site, the contractor is on it.
What is built today
BBGI-OPS is built and deployed, and entering its first sites. Everything below exists and can be shown in the running application — the seven recordings on the overview were made in it.
The cockpit of the shift
One live timeline: every duty with its steps, the risk falling as they are ticked, pause, postpone or refuse with a reason; an urgent response holds routine work until it is handled.
Procedures with steps
Templates for rounds, inspections, maintenance, fire and door-held responses, reports, handovers and contractor visits; steps that are mandatory or conditional, that decide, flag or spawn.
The command center
One 0–100 risk index per site — understaffing 0.40, alerts 0.25, overdue duties 0.20, open issues 0.15 — ranked, with the change over an hour, a day or a week.
Checkpoints at the door itself
NFC, QR, GPS or manual; sites in their own timezone; buildings, floors, zones, rooms, doors and assets as a tree.
Roster and coverage
People suggested per seat, an unqualified pick refused, an override with a reason and an approval; open seats claimed in one tap; publishing materialises the shifts and the recurring duties.
Serious sign-in, rules that fail closed
Passkeys, TOTP and e-mail codes, policy-as-code on every mutation, four audit streams, four alert levels and a seven-level escalation policy.
The engine
PXNT — AVGVSTVS
The live operations engine
BBGI-OPS runs on PXNT — AVGVSTVS: configurable procedures and requirements, risk that moves with every answer, and follow-up work started by the answers themselves.
- 01Operational state, presence and availability in real time
- 02Configurable procedures and execution requirements
- 03Dynamic risk per step and answer
- 04Conditional sequences and generated tasks
- 05Operational continuity, accountability and traceability
Traction, revenue and the round: on request.
Current sites, people on post, duties signed, revenue and what we are raising change every month, so they are not printed here. Write to us and we send the current deck, with the figures as of that week.
BBGI-OPS is built on the same base as two sister products, each with its own page: Ecopick for service companies and buildings and MDXT for care teams.