BBGI-OPS · LIVE MULTI-SITE OPERATIONS
Every site. Every shift. One live operational picture.
PXNT — AVGVSTVS · the live operations engineBBGI connects real sites — buildings, floors, rooms, doors and assets — to the people, procedures and work that keep them running. See who is present, who is available, what is underway or overdue, and where risk is rising or falling. Local teams execute the work as it happens; central operations see every site, exception and outcome.
- Site teams
- Reception
- Supervisors
- Control room
- Regional operations
- Contractors
The real-world model
The real structure. Connected to every operation.
BBGI does not treat a door, an issue or a completed inspection as an isolated record. It models regions, sites, buildings, floors, zones, rooms and physical assets, then connects that context to people, procedures, work, evidence and recurring weaknesses. Select an asset to see the relationship.
01 / THE PHYSICAL STRUCTURE
Select an assetPhysical places form a hierarchy. People, responsibilities and work link to the places and assets they concern.
02 / THE REAL LOCATION
Floor 02 · East Wing03 / CONNECTED OPERATIONAL CONTEXT
Illustrative dataAccess Door 04
London HQ / Building A / Floor 02 / Room 204 · Door
Linked operation
Door inspection · in progress
Evidence & outcome
Issue recorded · follow-up required
Not a logbook. The live operational day.
The work happens here, not in disconnected records written after a shift. Each action stays connected to a real place, an authorized person, the required procedure and its outcome.
How it works
- 01
Model the sites
Organization, regions, sites with their own timezone; buildings, floors, zones and rooms; doors, desks, assets and checkpoints — NFC, QR, GPS or manual.
- 02
Write the procedures
Templates for rounds, inspections, maintenance, fire and door-held responses, reports, handovers, contractor visits. Steps that are mandatory or conditional, that decide, flag or spawn. Posts and shift templates with seats.
- 03
Publish and run
Publishing materialises the shifts, seats and recurring duties. The cockpit runs the day, the command center watches every site, approvals catch the exceptions.
Five connected capabilities. One operational picture.
Every part of the system shares the operational context: what exists on site, who can act, what is happening now, what changes, and what remains traceable.
The physical context
Buildings, floors, zones, rooms, doors and assets — connected to the work and weaknesses associated with them.
Live operational execution
Presence, coverage, time-based duties, guided procedures, collaboration and handover.
Dynamic response and risk
Answers and events can increase or reduce risk, flag issues and create the next required work.
Multi-site command
Every office in one live view, with coverage gaps, trends, exceptions and drill-downs.
Governance and continuity
Eligibility, scoped authority, evidence, audit and work carried responsibly across shifts.
A duty
Ticked, flagged, signed, co-signed
A person on duty checks a sequence of real doors. A failed check exposes a slow hold-open magnet, raises an issue and changes the risk. This particular procedure requires two signatures; other work may not.
Lets an answer spawn the next work
Damage found, and the next duties already exist
A door-held alert raises its response procedure on the timeline. The last step's answer decides what follows: "damage found" spawns the report and the follow-up round by themselves, without a phone call.
Equipment & resources
The equipment the work depends on
PXNT — AVGVSTVS · the live operations engineKeys, radios, fire extinguishers, AEDs, ladders and tools, spare parts and consumables, vehicles. BBGI knows which exist, where they are, how many are free, who is using them, and whether there are enough for the work ahead — under Site → Equipment & Resources: the inventory, who holds what, the checks and the maintenance.
Site · Equipment & Resources
Illustrative dataLondon HQ / Floor 3 / Plant room
4 resources · 2 need action
Linked actions
- Restock spare filtersOpened by the configured minimum
- Inspect AEDPeriodic check due
The loop
Illustrative scenario- 01A round or task needs a qualified person and certain equipment.
- 02BBGI checks what is available, and where the nearest free one is.
- 03The person does the work and scans what they used. The stock updates.
- 04Below the minimum, the engine opens a restocking task, assigned by the configured rules.
- 05A failed inspection takes the item out of service and opens a repair.
- 06When an outside contractor or supplier is needed, the service network coordinates it.
Three kinds of resource
Individual equipment
Its own identity and code, its exact location, its condition, who holds it, and the inspections that are due.
AED · extinguisher · master key · ladder
Supplies by quantity
Product, quantity, batch and expiry, where it is stored, what was consumed, and when to restock.
Filters · batteries · first-aid refills
Shared and bookable
Availability over time, bookings, handovers from one person to the next, and conflicts before they happen.
Vehicles · lifts and cherry pickers · tool kits
Wherever it really is
Not only in fixed rooms: a resource sits at a site, in a room, in a cabinet or key safe, in a vehicle, or in a person's kit.
- Site
- Room
- Cabinet
- Key safe
- Vehicle
- A person's kit
Taken and given back
One holder at a time. A resource is taken and returned by scanning its code or picking it from a list, and every movement is traced: what, how much, from where, to where, who and when.
Availability comes only from recorded movements, scans, checks and connected devices. If nobody records that something moved, the system cannot know it moved.
Questions BBGI answers
- 01How many radios are there across all sites, and how many are free now?
- 02Where is the nearest working AED?
- 03Which fire extinguishers are due for inspection this month, and where are they?
- 04Which keys are out, and with whom?
- 05Which tasks cannot start because equipment is missing?
- 06What was taken, used, returned or moved?
“The availability of a radio is a fact about the resource. Deciding to open a repair is an operational decision.”
Every site at once
An alert moves the number, and the ranking
The command center folds understaffing, alerts, overdue duties and open issues into one risk index per site. An alert pushes one site to the top; the control room drills into the response behind the number and watches it fall back.
You stay in charge
Every action has an authority, a physical context and a trace. Work remains attributable even when responsibility passes between people, shifts or sites.
Identity and access
Device-aware sign-in, passkeys, multi-factor protection and controlled sessions, with accountability for who entered.
Authority and traceability
Scoped permissions govern who may act. Successful and refused actions are recorded so decisions can be reconstructed.
Eligibility is authoritative
Certification and post gates on every seat; an unqualified pick is refused; an override needs a reason and an approval.
Held, never lost
What a shift does not finish carries over to the next one. Overtime is asked about and escalated, not assumed.
Complements what you run
Badge and visitor systems, access control, CCTV and ticketing stay. BBGI-OPS is the execution and governance layer across them.
Recorded from the running app
See what a shift looks like in BBGI-OPS
Seven recordings from the working application, using illustrative people and sites. Scroll, or choose a tab.
The story
A fire-door audit, start to signed
The weekly audit is overdue. The person on duty checks each door, flags a slow hold-open magnet and opens a linked issue. A colleague joins from her phone and co-signs this procedure. Its outcome changes the operational picture.
On screen
- The person on site
- A colleague co-signing
Result: five attributable steps, two required signatures, and an issue preserved for follow-up.
The story
Live risk across every site
The command center: the composite index, the counters, the offices ranked by risk with their deltas, the duties at risk. The control room drills from a red number into the site, the duty and the step that put it there.
On screen
- The control room
- Every site
Result: one screen that says where to look first.
The story
Scheduling and coverage
The roster suggests people for each seat and refuses an unqualified pick; open seats sit in the coverage lane with a one-tap Claim. An override needs a reason and goes to Approvals. Publishing materialises the shifts, the seats and the recurring duties.
On screen
- A site supervisor
- The roster
Result: a week published, nobody on a post they are not certified for.
The story
An alert, handled as a team
An alert arrives on the timeline and raises its response. One person acknowledges and goes en route, another takes a duty from the pool, a third co-signs; the activity feed writes the handover as it happens.
On screen
- Three colleagues
- The activity feed
Result: acknowledged, en route, on site, resolved — with a name on each.
The story
One answer spawns the next duties
A step asks a question. The answer decides what follows: a "no" on a door check spawns the maintenance call and a re-check on the next round, each landing on the timeline with its own steps and owner.
On screen
- The person on site
- The timeline
Result: the follow-up exists the moment the answer is given, not when somebody remembers.
The story
The alert's last answer decides what follows
A door-held alert, its response procedure on the timeline, and the last step's answer: damage found. The report and the follow-up round spawn by themselves, and the command center's risk moves.
On screen
- The person on site
- The control room
Result: the right procedures, in the right order, without a phone call.
The story
Sites, issues, roles and proof
Around the record through real navigation: the site tree down to doors and checkpoints, an issue with its typed actions and its source step, the roles and permission matrix, and a completed duty opened to its evidence.
On screen
- The office
- The evidence room
Result: every piece of work tied to a real place, a procedure, a person and a trail.
Built for the field
Site teams work wherever the operation takes them. The same operational context is available on a phone, tablet or desktop.
- A PWAAny phone, tablet or desk; one URL, installable
- CheckpointsNFC, QR, GPS or manual, at the door itself
- Site timeEach site in its own timezone
- Manuals from WordPaste a DOCX, get a page tree, search it with ⌘K
- Alert levelsFour alert levels and a seven-level escalation policy
- 12 roles, 3 tiersGlobal, regional, site — stacked, with a visible matrix
Install the app
The Cockpit, on your home screen.
Install BBGI from the browser and it opens like any other app: one tap from the home screen, full screen, straight into the shift. No app store.
- One tap inFrom the home screen to the shift
- Full screenNo address bar, no tabs
- Same accountYour data, your duties, as they are
Questions, answered
Yes. One region, one site, one post template; the cockpit, the duties and the evidence are the same. The command center simply ranks a single office.
Yes. Vendors have their own roles and work queue, vendor escorts are a procedure like any other, and a vendor's duty carries the same steps, evidence and signatures as your own staff's.
No. Those systems keep doing what they do. BBGI-OPS ties the work around them — the door-held response, the camera check, the visitor escort — to a procedure, a person and a trail.
That is where it was designed to run. The recordings above were made on phones and desks alike; checkpoints are tapped, steps ticked and duties signed on the phone.
A composite from 0 to 100 per site: understaffing weighs 0.40, alerts 0.25, overdue duties 0.20, open issues 0.15. It is a pointer, not a verdict — every number drills into the duty behind it.
Access is by invitation today. Write to us with your sites and posts, and we set up a region with your procedures and invite your supervisors.
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
Connect every site to one live operational picture
Model the sites, connect your procedures and publish the first operating day. Use BBGI in the browser or install it as an app.