Manual
Using Kinetic Melbourne OCC
- For
- anyone using the app
- Status
- current
- Covers
- the whole app — the top bar and all four tabs
- Last checked against the app
ebc6de9(2026-08-20)
This is the manual for Kinetic Melbourne OCC — the tool built for Kinetic Melbourne's Operational Control Centre. It says what each screen does, what the numbers on it mean, what they do not mean, and what to do when something looks wrong.
You do not need to sign in to read it, and you do not need to know anything about how the app is built.
Three ways in
Pick one. You are not missing anything by not reading the others — they all lead into the same pages.
Quick start
Every screen, in ten minutes. Tables and short lines — press this, that happens — with no reasoning in it at all. For the day you have to work a screen now and read about it later.
Your role
A short path through the pages your job actually uses, and only those. Each one is a reading order with a line saying why every stop is on it.
- If you are a controller — you watch the network while it runs, and answer questions about now.
- If you plan diversions — you draw them, get them approved, issue the paperwork and file them.
- If you administer this deployment — you look after accounts, roles and the data this server is running.
The full tutorial
All of it, front to back. Eleven sections, written to be read in order the first time and searched afterwards. This is where every fact in this manual actually lives; the two routes above are ways of walking it.
What the full tutorial covers
| Section | What it answers |
|---|---|
| Getting started | What this tool is, signing in, what your role lets you do, and how the screen is laid out |
| The map | Finding a route, reading a stop, what the live bus colours mean, following one bus, and switching the background map |
| Overlays | Live congestion, road incidents, bus frequency, low clearances — what each measures and when it is missing |
| The timetable | Reading a timetable, the +1 marker on times after midnight, and the allocation view |
| Operations analysis | What this tab needs before it works, rosters and depots, allocation, and punctuality |
| Diversions | What a diversion record is, planning one, matching it to a road closure, what approval freezes, and the documents you can produce |
| Traffic radio | What it plays, how to control it, and what the read state means |
| Personalising the app | Settings, the difference between "this session" and "my default", colour and accessibility, and your operator scope |
| Reading the numbers honestly | Where a figure is an estimate, where a blank is not a zero, and what the timetable feed does not know |
| When something looks wrong | The banners one by one, a tab that is greyed out, an empty map, and who to tell |
| Glossary | Headway, layover, service day, variant, deadrun, block, shift, span, anchor, no-go |
Not every page has a picture. Some screens cannot be photographed for this manual at all — the ones built from a live feed this manual's demonstration data does not have, and the ones that need a signed-in account. Those pages carry prose alone rather than a picture of something else, which is the honest outcome and not a gap waiting to be filled.
Two rules every page here follows
They are worth knowing as a reader, because they tell you what to expect.
Controls are named the way the app names them. If a page says the ⚙ Settings button, that is the label on screen. Where this manual and the app disagree, the manual is wrong — even where the manual is more precise. Tell whoever maintains it, so the page can be corrected.
Every page says what a number does not mean. That is the thing a tooltip never has room for, and it is where a wrong decision actually comes from. A figure that is an estimate is marked as one; a blank that means "nothing was published" is never presented as a zero. The quick start is the deliberate exception, and it says so on its own first line.
What this is not
It is not a description of how the app is built, and it does not tell you how to install, deploy or configure anything. Those belong to the people who change the software, and they have a separate handbook of their own.