Manual / Ways in
If you plan diversions
- For
- a controller who draws, approves and files route diversions
- Status
- current
- Covers
- the Diversions tab, and the overlays and map pages a plan is checked against
- Last checked against the app
ebc6de9(2026-08-20)
A route through this manual for the person whose output a driver is handed at the wheel. It is a reading order, not a summary: each page below is written once in the section it belongs to, and this page says only why it is on your path and where in the job it belongs.
What your day looks like
A street closes, or is about to. You find out which routes run through it, draw where the bus leaves its normal route and where it rejoins, send it a way that a bus can actually go, write what the driver is told, get it signed off, issue the paperwork, record the window it was in force for, and retire it when the street reopens.
What you own: the one part of Kinetic Melbourne OCC — the tool built for Kinetic Melbourne's Operational Control Centre — whose output leaves the building. A driver acts on your bulletin at the wheel, and a record you approve is what somebody reads in a year when they ask why the street was diverted.
What you can leave alone: rostering and punctuality, which are the operations sections and answer a different question; and accounts and data versions, which belong to the administrator's route. The live picture you work from is the controller's route, and if you do both jobs, read that one first.
Before you draw anything
Three pages, and they are in this order because the third one is the reason the first two matter.
| Read | Why it is here |
|---|---|
| Diversions | The framing the whole tab is built on, including the sentence the tab prints about its own figures. Two minutes, and everything after it reads differently |
| The register | What one record actually is, how it is referenced and found, and the four states it moves through. The reference is what you read out over the radio |
| Finding a route | A record is one route in one direction, and a route number is often several patterns. This is the page where those two facts come from |
Drawing one
The workspace, and the three overlays that tell you whether the way round is a way a bus can go.
| Read | Why it is here |
|---|---|
| Planning a diversion | The workspace itself: the anchors, the drawn path, via points, marks on the plan, and the three things it will refuse outright |
| Starting one from a road incident | The faster way in when the closure has already happened, and how to check later whether it has ended |
| Low clearances | The check that is cheap now and expensive later. Switch it on over your drawn path before you approve it |
| Live congestion | Whether the street you are sending the bus down is already blocked. A drawn path knows the roads, not the traffic |
| What the timetable does not know about the road | Read this the first time the planner refuses you a figure rather than printing one. It is the app being careful, and the page says exactly what it is careful about |
| Driver instructions and the bulletin | The half of the record a driver actually reads. Written last, and worth as much attention as the line on the map |
Getting it out
| Read | Why it is here |
|---|---|
| Approval, and what it freezes | The step most often mistaken for a fault. Read it before your first approval, not after somebody tells you they cannot edit a record |
| The documents you can produce | Which of the three is for the driver, which is for the file, and what the watermark on an unapproved one means |
After it is out
| Read | Why it is here |
|---|---|
| Activations, and the figures they carry | Recording the window a diversion was actually in force for, which is what every service-km figure afterwards is summed from |
| Every diversion figure is an estimate | Read it before anybody quotes one of your figures at a meeting. It is one page, and it is the difference between an estimate and a number somebody treats as measured |
When it is relevant
| Read | When |
|---|---|
| Road incidents | When you want the closure list itself, and which of our routes each one sits on |
| The Allocation view | When the question has turned from "route it round" into "the running time no longer fits" |
| Allocation | When you need to know what else a diverted trip will disturb — the same bus's later work, and the driver shifts hanging off it |
The +1 clock |
Before you set an activation window that crosses midnight |
| Glossary | Anchor, variant, no-go area and service day are all in it, in the sense this app uses them |
Where this route ends
The pages this route skipped are open to you in the full tutorial, and the quick start has the whole diversion lifecycle as seven numbered steps for the days when you want the sequence and not the reasoning.