PXNT

The engine · Generation I

PXNT — AVGVSTVS

The engine that runs the daily work.

Generation I · Augustus 1.0

Augustus knows who works where, what has to be done and who is allowed to do it. It runs every task step by step, keeps the proof, raises the problems and starts the follow-up by itself. Each part below, at work.

AVGVSTVSthe engine
the next product

Inside Augustus

  1. 01Who works where
  2. 02Every task, step by step
  3. 03Live risk
  4. 04Who may do what
  5. 05Proof of every step
  6. 06The next task, started by itself
PlannedTaken or joinedStepsThe answerSignedBilledthe next task, started by itselfan issue, raised
01

Part 01 · People, places and work

Who is where, and what they can do, right now.

PXNT knows who is present, what they are qualified and authorized to do, what work is required, who is responsible for it, what is happening now, what has already happened and what remains unresolved. Every action changes that state.

  • What exists: people, places, organizations, assets
  • Who can act: roles, qualifications, certifications, availability
  • What should happen: requirements, schedules, deadlines
  • What is happening now: presence, assignment, progress, risk
  • What happens next: rules, escalation, follow-up work, handover
  • What happened: answers, evidence, signatures, audit
LobbyRoom 101Room 102Plant roomBay 3SRAKMidday round · 3 of 5seat openDoor check · overdueRight now3people present2certified for fire-watch2duties under way1seat unclaimed1check overdue34risk, falling
02

Part 02 · Every task, step by step

Work is not a checklist.

A requirement can be claimed, joined, executed, abandoned, carried forward or completed. Its steps can require specific roles or certifications, collect evidence and signatures, change risk, reveal more steps or create entirely new work.

  • Claimed, joined, carried forward or completed
  • Steps gated by role or certification
  • Evidence and signatures, a second where it is required
  • An answer starts new work with its own owner
See the engineTry it in the demo
MDXTRecorded in MDXT · An answer that starts the next duty
03

Part 03 · Live risk

Risk is a number that moves.

Risk moves step by step: one answer lowers it, another raises it, and it climbs when a duty runs late, an alert lands or a seat stays empty. Each site rolls its work into one index the control room ranks and drills into.

  • Moved by single steps, not only finished duties
  • Rises with alerts, overdue duties, open issues, empty seats
  • One index per site, ranked, watched by the hour
  • Drills to the duty and the step behind the number
05010006:0010:0014:0018:0022:00One site · risk 0–100

BBGIIn BBGI: one index per site

  • 40Understaffing
  • 25Alerts
  • 20Overdue duties
  • 15Open issues

BBGI's published weighting of the site index.

04

Part 04 · Issues and alarms

Raised from a step. Tracked to closed.

An answer that finds something wrong raises an issue on the spot, tied to the step, the duty and the place. It is tracked like a ticket, and a high one rings an alarm the control room acknowledges. Closing it resolves the alarm and the risk falls.

  • Raised from a step, or by hand
  • Severity, owner and status, like a ticket
  • A high one rings an alarm to acknowledge
  • Closing it resolves the alarm and lowers the risk
highDoor 3 holds openFire-door audit · B2 · step 3LNopenacknowledgedin progressclosedAlarm · North Plantacknowledgedclosedrisk 71risk 30
05

Part 05 · Handover

Nothing is lost between shifts.

What a shift does not finish carries over to the next one. The handover lists the open duties, the issues still open, the seats not covered and the signatures still owed, so the next shift starts where the last one stopped.

  • Unfinished work carries over to the next shift
  • Open items, issues and coverage in one handover
  • The signatures still owed, by name
  • Signed off by both shifts
Day shift · 06–14Late shift · 14–22Opening roundDeliveries intakeFire-door audit · 3 of 4Door 3 issue · openSignature owed · intakeFire-door audit · 3 of 4carried overDoor 3 issue · opencarried overSignature owed · intakecarried overOHLNhandover signed
06

Manuals inside the duty.

Every duty is a list of steps frozen when it starts, ticked in order on site with photos, values and notes. The place's own manual sits inside the step: how this is done here, in this building, at this site.

  • Steps frozen when the duty starts
  • Photos, values and notes on every step
  • The site's own procedure, inside the step
  • Manuals imported once, used by every duty
Duty · fire-door roundCheck in at the doorCheck the closerLog the readingHow to check the closersite procedure · this building1. Open the door fully2. Let it close on its own3. Under 5 s and latched: OK
07

Chat on every duty.

Every duty and every shift has its own thread. The people on it talk where the work is, with photos, and the conversation stays in the record of the work.

  • A thread per duty and per shift
  • Photos in the conversation
  • Mentions that notify the right people
  • Kept with the record of the work
Duty · night round · ward BBed 4 asks for waterOn my way, 2 minDone — photo attachedsomeone is typing
08

Follow the people as they work.

Who is on duty, where they are and what they are doing, live. The command center sees every site at once; a round on the road is measured leg by leg.

  • Who is on duty, free or busy, live
  • Where each round is, leg by leg
  • What every person is doing right now
  • A command center across every site
MDXTRecorded in MDXT · On the road, every leg measured

Every duty, live, from plan to bill.

The platform servicesFor investors
ProductsInvestors