Transit Ops is the live control room for South East Queensland bus operators. It watches every bus on TransLink's real-time feed, puts what needs action in front of your controllers, keeps drivers in the loop on the driver device, and shows what to fix afterwards.
Controllers see late, early and not-departed trips while there's still time to act, with a suggested fix for each.
Disruptions outside your control are claimed with evidence, and every action and message is on record.
Fitness and vehicle checks at sign-on, defects with photos, guided incident reports, a screen that locks while moving, and hands-free voice.
Passenger loads by stop, running times by section, bunching, road speeds and driver feedback.
Nothing to wire into the bus and nothing to install. Any tablet or phone with a web browser can be the driver device, and the pilot proves it on your routes first.
Each driver answers a fitness and vehicle check on the driver device before they can take a trip: drugs and alcohol, fatigue, pre-departure check, fuel or charge, bus and speedo. Anything that needs a supervisor alerts the control room straight away.
On-time running, cancellations, the worst routes and what the control room did about it, before the first bus leaves the depot.
Trips that haven't departed, buses running late or early, layovers that will make the next trip late, and bunching. Worst first, each with the bus's next trip, a predicted arrival and a suggested fix. One tap records what was done.
Control-room changes go to the driver's screen to be acknowledged. At each stop drivers count passengers on and off with one tap, say why they're late, or ask for help, by tap or by voice, and are told to hold when early, never to speed up. The screen locks while the bus is moving; voice still works.
Interventions shows whether each action helped: did the bus recover time, did the next trip leave on time. Insights ranks the trips that run late again and again and says why.
End of shift: defects reported with photos, the closing speedo, a short summary of how the shift ran, and the driver's feedback, all in front of the control room.
The driver involved is guided through the report step by step, and control is alerted the moment they say whether anyone is hurt. A controller draws a diversion on the map in under a minute; every driver on the route hears it and acknowledges it. Later, claim the trips it made late with a reason and photos.
Performance by route, hour and day; suggested running times for your schedulers; bunching and speed maps for conversations with TransLink and council; and how each trip was run, by bus and by driver.
Every shift starts and ends with a one-minute check, and the trip in between is guided, on a tablet or phone in a cradle at the driver's seat. Nothing to wire into the bus.
Drugs and alcohol, including prescription medication, and fatigue. A yes to drugs or alcohol means cease work and report to a supervisor.
Pre-departure check, defects with photos, fuel or charge, bus number and speedo.
The control room is alerted with a sound and clears the driver or stands them down. The driver device moves on by itself.
Directions, stop announcements, hold countdowns, one-tap passenger counts and late reasons, acknowledged messages and a help button. Locked to touch while moving; voice commands still work.
Defects, closing speedo, the driver's on-time summary and their feedback.
A light on the driver device and beside each driver in the control room shows whether the link to control is working, so a dropped connection never goes unnoticed.
The driver signs in, passes the sign-on check and starts the trip. The device reports its position every 10 seconds.
Green Live, amber Weak, red No link. When the link drops, a banner and a spoken warning tell the driver to use the radio.
Live, Weak signal or No update for a number of minutes, and the Drivers button counts devices not reporting.
Every sign-in, sign-on check, trip connected and shift ended is in the Activity log, with the time.
Passengers counted at every stop, hands off the screen between stops, and the driver's voice for the rest.
A crash or breakdown is handled the same way every time: the driver is guided through what the law and your incident plan require, and every other driver on the route is told where to go.
Every trip is measured leaving its first stop and arriving at its last. Choose the stops part-way along each route to see where the time is lost.
On time leaving the first stop, for every trip.
On time at the last stop, for every trip. A bus can leave on time and still arrive late.
In Settings, pick a route, see every stop in both directions and turn on the ones to measure. Administrators only, and every change is in the audit trail.
Performance shows departure, mid-point and arrival results together, so you can see which section of the route needs more time.
Patterns that point to the driver rather than the traffic, as evidence for a fair conversation.
Arrived early at the terminus, then left late on the next trip from the same place.
Ahead of time at stops along the way. Arriving early at the last stop isn't counted.
A trip that stopped short of its last stop, checked against GPS.
No passengers counted on a trip, or a control-room message not acknowledged within 5 minutes.
Transit Ops has no equipment wired into your buses, so it shows where the data falls short, how far to trust each arrival prediction, and where the timetable data doesn't match the road.
From the first full day of collection, 23–24 October 2026, across every contracted SEQ bus operator.
Live exceptions, worst first, with a shift log your controllers already understand.
The bus's next trip, the usual bus, the next service and a spare bus finishing nearby. One tap records the action.
Learned from your own running times and today's traffic, checked every day against TransLink's.
What each action achieved: time recovered, knock-on avoided, gaps closed.
Trips your control room saved, beyond the ones that would have run anyway, compared with the alerts nobody acted on.
Draw a temporary detour with a start and end time. Drivers on the route hear it, acknowledge it, and their directions follow it.
When a diversion closes stops, a printable notice for each one in your brand: when, why, where to catch the bus instead, a map and a QR code to live departures.
Take trips delayed by crashes, closures or police activity out of your results, with photos and notices as evidence.
On the driver device, a tablet or phone in a cradle: turn-by-turn directions, spoken stop announcements, hold countdowns, one-tap late reasons and a help button.
Fitness for duty, pre-departure check, fuel or charge and speedo; then the driver's on-time summary and feedback. Supervisor alerts and stand-downs recorded.
Reported at sign-on or end of shift with photos, listed in the control room until marked fixed.
Breakdowns and crashes reported step by step on the driver screen, with photos, the other driver's details and police duties; a printable written report for audit.
One tap per passenger on and off at each stop, the load departing every stop, how full each bus is now, and a CSV by stop.
A light on the driver device and beside each driver in the control room: live, weak or lost. When the link drops, the driver is told to use the radio.
The driver screen can't be tapped or typed on above 8 km/h, and the server refuses input from a moving bus.
“Transit, acknowledge”, “Transit, need help”, “Transit, three on, one off”. Hands-free on the driver device.
Every bus, coloured by punctuality, with departures and alerts.
Recurring late trips and early running, ranked by how often they happen.
Timetabled against actual, by section and time of day, with a CSV for schedulers.
Buses arriving together, and the long waits behind them, by stop and hour.
Average speed on every 200 m of road, before and after a change.
Replay any bus on any day. Answer “where was the 7:42?” in seconds.
Which trips each bus ran, late starts traced to the trip before.
Early in and late out at the terminus, running early, trips cut short, missing passenger counts and unacknowledged messages, by bus and by driver.
Late after 5 minutes, or 5 minutes 59 seconds: set your own definitions and alert thresholds.
On time leaving the first stop, at the mid-point stops you choose, and arriving at the last.
Trips missing from the feed, trips with no times, patchy GPS and feed outages, with a CSV of problem trips for TransLink.
How close arrival predictions came, by route and direction, against TransLink's.
Stops on the wrong side of the road or away from where buses stop, and route lines buses don't follow, with suggested fixes for TransLink.
A guide to every screen, and a Help button on each page that opens the right topic.
A sign-in for each person, with administrator, user, manager and driver roles, and a record of who did what.
A summary every morning, and an email when a critical exception sits unacknowledged.
Every action is matched with what happened next, and every alert is kept whether anyone acted or not, so the control room is credited only with trips that wouldn't have run anyway.
A not-departed trip that ran after the controller acted. Half a trip if it left more than 15 minutes late.
A late bus whose next trip was expected to leave late, and left on time.
A lost or cancelled bus whose trip a replacement ran.
The same test on alerts nobody acted on shows how often trips run anyway. Shown on Interventions and the manager's dashboard.
Four kinds of sign-in, each showing what that job needs. Everyone has their own access code, so the activity log shows who did what.
Add and remove people, issue access codes, change settings and see the activity log.
Duty controllers, schedulers and planners use every tool, from the control room to the reports.
One page: the performance dashboard, with on-time results, the trend, routes needing attention, network rank and safety.
The driver screen on the driver device, and nothing else.
Better on-time results, an independent benchmark against other operators, and a summary every morning.
A control room that ranks problems, suggests fixes and shows which actions worked.
Exceptions, drivers, messages, help requests and diversions on one screen, with less radio traffic and no retyping into logs.
Fitness-for-duty and vehicle checks every shift, defect evidence, incident reports ready for audit, the movement lock and a full audit trail.
Running times, bus workings, bunching and passenger loads by stop, ready to download.
Directions, stop announcements, hold advice, hands-free contact with control, and a say on how the shift went.
Defects with photos and categories the moment they're reported, listed until marked fixed.
Speed maps and passenger loads as evidence for bus priority and service changes.
3 months on your own routes with every tool, setup and controller training included. If it isn't earning its place in the control room, walk away. Prices are per bus per month, ex GST, counted on the buses you run at your busiest.
A$35 per bus per month
Everything a controller needs on the day.
A$60 per bus per month
Control, plus the analysis that fixes the timetable.
Flat annual fee quoted for your network
For TMR or TransLink: one cross-operator view of every SEQ operator, at a flat annual fee rather than per bus, so no bus is charged twice.
Ask for a quote| Pilot | Free for 3 months, every tool |
|---|---|
| Minimum | A$500 per month |
| Pay yearly | Save 10% |
| Hardware | Any tablet or phone with a browser |
| Time to go live | A day |
No. Transit Ops uses TransLink's open real-time feed, so there is nothing to wire into the bus and nothing to install. Your controllers sign in from a browser, and drivers use a tablet or phone in a cradle as the driver device.
Each operator has its own private sign-in and sees only its own control room and analysis. The public performance pages show network results that anyone can already work out from TransLink's open data.
No. They are measured independently from TransLink's real-time data, using the same on-time window (no more than 1 minute early or 5 minutes late), so they are indicative rather than the contract figures.
Yes. Each operator sets its own definitions in Settings, down to the second, along with when the control room raises an alert. The public network ranking keeps TransLink's standard so operators are compared fairly.
Not by touch. Above 8 km/h the screen locks: nothing can be tapped or typed, and it unlocks after 3 seconds stopped. Directions, timing and stop announcements carry on by voice, and drivers can acknowledge a message, hear the last instruction again or ask for help hands-free. Counts and late reasons wait until the bus has stopped.
Only when the driver turns the mic on, and it acts only on phrases that start with “Transit”, so conversation on the bus or the radio is ignored. Speech recognition is provided by the device's browser (Google on Android, Apple on iPad and iPhone); Transit Ops receives only the recognised command, never a recording.
Yes, a driver device: a tablet or phone, usually supplied by the operator and fixed in a cradle at the driver's seat. The driver screen runs in its web browser, so there is nothing to install. It locks to touch while the bus is moving and works hands-free by voice, so it fits with policies that prohibit drivers using a mobile phone while driving. Drivers get their own sign-in and can only reach the driver screen.
They are told to cease work, not to drive under any circumstances and to report to a supervisor. The control room is alerted at once and can stand them down, but can't clear them to drive that day. Every answer is recorded in the audit trail.
Everyone you choose, as administrators, users, managers or drivers, each seeing what their job needs. Your administrators add people, give each their own sign-in, and see an activity log of sign-ins, actions and changes.
The driver taps Help, then Report a breakdown, crash or incident. The screen asks about safety first and offers 000, then walks through making the scene safe, passengers, the other driver's details, whether police must be told within 24 hours, photos and whether the bus can continue. The control room is alerted at once, and the operator completes the written incident report TMR expects within 24 hours, then prints it for audit.
In under a minute. Choose the route, click where buses leave it, where they go via and where they rejoin; the path follows the roads. Set the start and end, and every driver on the route is told and must acknowledge. You see who has, and can extend or end the diversion at any time. If stops are closed, a notice for each is made in your brand, ready to print and put up at the stop.
It lists evidence to check, not a verdict. Trips excluded for disruptions are left out, control-room actions such as a short-turn are shown beside each finding, and early arrival at the last stop isn't counted as running early.
Control covers the day: the live map, control room, suggested fixes, diversions, the driver screen with sign-on and end-of-shift checks and incident reports, alerts and the morning email. Control + Insights adds the analysis that fixes the timetable: repeat late trips, running times, bunching, speed maps, playback, bus workings and driver behaviour. The pilot includes both, so you can decide with your own results.
From the most buses you run in service at once on a typical weekday: the median of the daily peaks over four weeks, measured from the feed, with a chart of buses in service by time of day for weekdays, Saturdays and Sundays. Spare buses sitting in the depot aren't charged. Your administrator sees the count in Settings and agrees it, or proposes a different number with a reason, before anything is billed.
Yes, on a network licence: one flat annual fee for the cross-operator view, so buses already licensed by their operator aren't charged twice.
Yes, from the driver's one-tap counts at each stop: boardings, alightings and the load departing every stop, live in the control room and as a CSV by stop. TransLink's real-time feed doesn't include loads; with go card data we could also rank late trips by the number of people affected.