Carbone

The day :
Opening :
Sessions :
:
ARA. Reyes · operations manager
EN

The day

What is done, what remains, what gave out. Everything starts here and everything comes back here.

Read the article ›
Demonstration. No server behind this page: the state is kept in this browser, photos are resized to 1600 px then stored, and sending to maintenance opens a preview of the email.

Today's sessions :

Audit trail timestamped, unalterable

Pre-opening checklist

The walk before the first visitor. One critical check with an issue raised, and opening stays shut: it is the checklist that holds the door, not goodwill.

0%
:

Report an incident

Thirty seconds while operating, not an insurance form. What matters: where, what, what effect on the session, and a photo.

Incident record INC-…

Images are resized to 1600 px in the browser before being kept: enough to read a silkscreen marking or a solder joint. On a tablet, the camera is offered directly.

Incidents :

Closing checklist

The walk afterwards. This is where the counters and consumables are read, and without that, the maintenance forecast is worth nothing.

0%
:

End-of-day readings feeds the forecast

The plan, annotated

A remark placed at the exact spot where it means something. The maintenance technician who arrives knows where to go before setting the toolbox down.

Incident To check Observation Planned work (square) Dotted line: visiting direction A marker moves with a finger

Maintenance, costs and consumables

The counters read at closing make the due dates; the due dates make the budget. Nothing is entered twice.

Equipment maintenance schedule by forecast date

What the store will have to supply the next five service tasks

Open tasks :

The store

What is left on the shelf, what upcoming service tasks will draw from it, and the date by which to order so the count comes out right.

Consumables run down at the pace of sessions and service tasks

Spare parts wait on the shelf for a dated due date

Reorder plan routine usage + parts for upcoming service tasks

Days of cover supplier lead time deducted

View the data

Dash board

Twelve weeks of operations. Not for decoration: to know which equipment really costs, and which merely makes noise.

Incidents per week stacked by severity

View the data

Operational availability share of sessions played without downtime

View the data

Incidents per space 12 weeks

View the data

Most serviced equipment total downtime, in minutes

View the data

Duration of the opening check target 45 min

View the data

What this dashboard does not measure read this before using it to judge

These curves only count what has been reported. Out of frame, by construction: the incidents nobody bothered to report, what was repaired without being logged, the team's real workload, and the quality of the experience as the visitor lived it.

These are indicators of operations, not of people. A number used to judge someone stops being a number you can believe: it becomes a number that gets produced. The log only has value if writing the truth remains without consequence for the person writing it.

Report to maintenance

The day assembled into one document: issues raised, incidents, readings, open tasks, attachments. One gesture, one recipient.

Report preview :

 : 

Recipient

:

Attachments :

Sending history

CARBONEOperations log

Smartphones are not supported : neither iPhone nor Android. This log is kept on a tablet (iPad or equivalent) or on a computer screen. The checklists, the maintenance schedule and the store are tables: six centimetres wide, they cannot be read, only guessed at.

Reopen this link on a tablet or a computer. It is the same one.

‹ Read the article instead

CARBONEOperations log

The demonstration is opened on request. It runs on an invented venue, with twelve simulated weeks of operations: there is no real data behind it, and nothing leaves it.

The session stays open for two hours, then the code is asked for again.

Request access to the demonstration › ‹ Read the article