AVGVSTVS, the engine

AVGVSTVS runs the daily work inside an organization. It knows who works where and when, what each task asks step by step, how risky each site is right now, what went wrong, and what the next shift needs to know. MDXT and BBGI run on it.

The engine has no data of its own. It decides what a change means and whether it is allowed; the product keeps the records. That is how two very different products can run the same engine.

1. Where work comes from. Planned on the schedule, started by itself when an earlier task asks for it, or asked for by someone.
2. Taken. A person takes the task, or is given it. Only someone who may do it, and who holds what the task requires, can.
3. Under way. Step by step: a check, a yes or no, a reading with its unit, a photo, a note. Each answer can change the site's risk, open more steps or start the next task by itself.
4. Completed with proof. When every step is done, with a signature where one is required, and two where four eyes are needed.
5. Recorded. Every change says who made it and when, written in the same moment as the change, so neither can exist without the other.

Shifts and their seats, templates that repeat, drafting by hand, open seats anyone suitable can claim, one's own shifts. Arriving, leaving a seat, being held past the end of a shift with the overtime asked and answered, and a check-out undone.

Each site has a risk that moves with the work: late tasks, open problems, missing people. A problem is raised from the step where it was found, with how serious it is; a serious one rings an alarm that someone must answer. Command shows every site at once.

At the end of a shift the engine gathers what the next one needs: what is still open, what was found, notes from the people leaving. The note is signed out by one shift and taken over by the next, and unfinished work is carried to the shift that follows. At the end of the day the day is sealed.

The engine's own page tells the same story with drawings: AVGVSTVS.