Work

Buildings, floors, rooms and equipment are registered once; the deceased, the family, the staff on duty, contractors and facilities are then tied to a hall. Current state and room history read from one screen.

The guidance displays are driven from the same system. Video, audio, ribbon text and decoration are chosen on screen and pushed to the equipment on site — work that used to be done on paper, by hand.

Usage and billing accumulate as you go, so settlement is not counted twice.

The first screen of the working day. Today's weather and warnings, safety scores, the canteen menu and birthdays on one page — and below them, the doors into every system people actually use. No one has to remember addresses.

The weather is where most of the work went. Forecasts (nowcast, short and medium range) and official warnings are collected continuously per site, each location mapped to the forecast grid so every site reads the numbers for its own ground.

The record starts when a threshold is crossed. The moment a site's own limit is exceeded becomes an event, and what was done about it is attached to it. When a warning was raised and when it was lifted is kept alongside. Not a screen for looking at the weather — a screen for recording what the weather made you do.

Safety scores sit in the same place. A number seen daily moves differently from one seen in a quarterly report.

Steam, electricity and treated water, produced and supplied to the companies across an industrial estate. Fuel enters, passes boilers and turbines, and divides into steam headers at different pressures while raw water is refined alongside. All of it moves live on a single process diagram.

Not only the diagram. What each company draws is metered, and that meter reading carries straight through to supply volume and billing. Fifteen-minute electricity use and peak checks sit in the same place.

Both sides read the same number. Supplier and consumer have their own screens over one set of readings, so settlement is not an argument about figures.

We built it and we use it. Improvement requests are logged per client, then carried through assignment, scheduling and status in one thread. You can see how far a request has got without asking.

Intake, review and delivery all leave a record — one that outlives whoever was on duty, attachments and conversation included.

If a server stops answering, a notification goes out. We know before anyone has to notice.

Projects and work breakdown, with schedule and ownership. So far, like any such tool.

What differs is that the drawings live inside the project. An editor for architecture, flow and ER diagrams is built into the system, so designs do not drift off into loose files — they sit in the same row of tabs as the schedule, the source and the database notes.

Which screen uses which table, and what a column actually means, is kept there too. All of it exists to stop a handover passing on the code and losing the reasoning.