Dot.Central
Sign in Create an account

The control room for a mining shift.

Dot.Central reads the fleet from Dot.Mines and turns it into the work of a shift: who is on which machine, which machines can run, what stopped and why, what the next shift must know. Operators act on it. Nothing here edits a Dot.Mines fact.

One shift, in order

The system follows the order a control room already works in. Each step only needs what the previous one produced.

Start the shift

Pick the shift type and the supervisor. Open issues from the previous shift are listed before anything else: machines down, units on standby, exceptions still unexplained.

Build the line-up

Faces come from the geofences or mine areas already configured. Loading units are placed, haul trucks are counted against the configured ratio, and the rest go to standby with a reason.

Assign operators

Every placed machine gets an operator. Assignments are pushed to Dot.Mines, which checks licences, medicals and inductions and refuses what it cannot accept. A refusal is shown, never hidden.

Run and hand over

The overview, availability board, stoppages, exceptions and alerts follow from the line-up. At the end, the handover carries the line-up, the open issues and the supervisor's notes to the next shift.

Read from the fleet, not typed in

Operators record decisions. Facts come from Dot.Mines on a schedule and through signed webhooks, and the room shows how fresh each one is.

Availability

A machine is down when Dot.Mines reports it offline or in maintenance, or when a stoppage has been classified as counting against availability. Missing telemetry is shown as unknown, not as stopped.

Production and hours

Loads, tonnes, cycle times and engine hours are read as the provider reports them, with the provider's timestamp. Thresholds for exceptions are set per control room.

Alerts

Alerts arrive from Dot.Mines. Acknowledging or resolving one here is recorded locally and pushed back, and the outcome of that push is part of the record.

Who does what

Four roles, each scoped to a control room. Every action lands in an append-only audit log with the actor, the shift and the reason.

RoleCan
OperatorStart and close shifts, build the line-up, classify stoppages, explain exceptions, acknowledge and resolve alerts, write handover notes.
SupervisorEverything an operator can, plus approving exceptions and confirming handovers.
ManagerReports and exports, shift types, downtime reasons and thresholds for the room.
AdministratorRooms, members, the Dot.Mines connection and its health. Administrators configure; they do not operate.