Network workstream
Reporting requirements, against what runs
Every reporting requirement on the Network list, in the phase it is asked for, with an honest answer against it: running now, buildable from data the platform already holds, or waiting on a feed that does not exist yet.
Reading the platform…
The list
Requirements that repeat across phases are listed once, with the phases they appear in marked. What changes between phases is usually the format demanded — a spreadsheet before Day 1, the platform after it — not the measure, which is why the same measure needs a baseline built before Day 1 to be compared against afterwards.
Scheduled against operated
Reliability, missed trips and lost mileage are one measurement: the registered timetable for the day, journey by journey, against the journeys a bus was seen working. The registered timetable is resolved the same way the vehicle matcher resolves it — calendar plus exceptions — so the two halves cannot drift apart.
| Day | Scheduled | Operated | Not seen | Operated |
|---|
What this figure is not. A journey nobody reported on looks exactly like a journey that did not run. Today the gap holds both, so this is the ceiling on lost service rather than a count of cancellations. Under franchising the contract can require the vehicle to report, and the same query then produces the real number — no rebuild, no new feed.
Journey speed
Measured from the journeys themselves rather than from the timetable: the distance between the stops a bus was actually seen at, over the time it took between them, dwell time included.
Where the network loses time
Delay added between one stop and the next, summed across every journey in the window. Measuring delay added rather than delay observed is what separates the place that causes the problem from the twenty stops downstream that inherit it.
| Approach to | From | Journeys | Average added | Total lost |
|---|
The baseline problem
What a baseline can contain
Punctuality, early running, reliability, journey speed and stop-level running times can all be baselined from the day recording started, for every operator in the area, franchised or not. That baseline grows a day every day and needs no supplier.
What it cannot
Nothing before recording started can be recovered. Bus location feeds are not archived nationally; what was not captured on the day is gone. Any pre-Day 1 comparison that reaches further back has to come from operator returns, with the accuracy that implies.
Patronage, revenue and satisfaction have no baseline here at all — the feeds do not exist, so the clock on those starts when they are procured. That is the argument for procuring them before Day 1 rather than for it.