Metro Bus Operational Performance (MR4)
Operational Performance dataset including all outcomes related to overall Public Punctuality and Reliability (% Services Monitored) metrics
Data Dictionary
| Field Name | Name | Type | Description | Fixed Values |
|---|---|---|---|---|
| % allocated | Proportion of services allocated | DOUBLE | Proportion of services loaded in the bus tracking system that have been allocated. # journeys allocated (Bus) / # journeys loaded (Bus) |
|
| % journeys monitored (Bus) | Proportion of services monitored | DOUBLE | Proportion of services scheduled that were monitored by the bus tracking system (BTS) # journeys monitored (Bus) / # journeys scheduled (Bus) The reasons why a service may not be monitored include BTS equipment or systems failures, reference data and timetable issues, failure of a bus to be allocated to a timetabled services and a service cancellation. Some of these factor are not in the direct control of bus operators. |
|
| % ontime (ArrDep|tp) | Punctuality - Ontime arrival and departure at timing points | DOUBLE | Proportion of services arriving no more than 4 minutes and 59 seconds late and departing no more than 59 seconds early at timing points. # of services arriving no more than 4 minutes and 59 seconds late and departing no more than 59 seconds early at timing points / # of services observed arriving and departing at timing points. |
|
| # service unique | Number of unique services in timetable | DOUBLE | Number of unique services scheduled to operate in the bus tracking system. | |
| # journeys monitored (Bus) | Number of scheduled services monitored | DOUBLE | Number of scheduled services monitored by the bus tracking system (BTS) at one or more location. The reasons why a service may not be monitored include BTS equipment or systems failures, reference data and timetable issues, failure of a bus to be allocated to a timetabled services and a service cancellation. Some of these factor are not in the direct control of bus operators. |
|
| # ontime (ArrDep|tp) | Number of services ontime | DOUBLE | Number of services arriving no more than 4 minutes and 59 seconds late and departing no more than 59 seconds early at timing points. | |
| # not ontime (ArrDep|tp) | Number of services not ontime | DOUBLE | Number of services arriving more than 4 minutes and 59 seconds late or departing more than 59 seconds early at timing points. | |
| # punctuality events (ArrDep|tp) | Number of punctuality events delivered | DOUBLE | Number of punctuality events monitored | |
| # loaded | Number of services loaded in bus tracking system | DOUBLE | Number of journeys loaded in Smartrak bus tracking system. Note: Prior to mid 2019 some services were monitored by a different bus tracking system. This systems did not handle loading and allocation of services in the same manner as the Smartrak system. Loading and allocation data is only provided for the Smartrak system services in this report. |
|
| # allocated | Number of services allocated in bus tracking system | DOUBLE | Number of journeys allocated in the Smartrak bus tracking system. Note: Prior to mid 2019 some services were monitored by a different bus tracking system. This systems did not handle loading and allocation of services in the same manner as the Smartrak system. Loading and allocation data is only provided for the Smartrak system services in this report. |
|
| Date | Date (Metropolitan Bus) | DATE | Date on which services are run | |
| Line/Route | Line/Route (Metropolitan Bus) | TEXT | Line/Route on which services are run |
Additional Information
| Field | Value |
|---|---|
| Data last updated | 12 November 2026 |
| Metadata last updated | 13 November 2026 |
| Created | 12 November 2026 |
| Format | CSV |
| License | Creative Commons Attribution 4.0 International |
| Attributes | [{"attribute_display_order_id": 1, "db_format": "DOUBLE", "db_name": "% allocated", "definition": "<p>Proportion of services loaded in the bus tracking system that have been allocated.</p>\n<p></p>\n<p># journeys allocated (Bus) / # journeys loaded (Bus)</p>", "id": "11742", "name": "Proportion of services allocated", "ref_number": "AT-11742"}, {"attribute_display_order_id": 2, "db_format": "DOUBLE", "db_name": "% journeys monitored (Bus)", "definition": "<p>Proportion of services scheduled that were monitored by the bus tracking system (BTS)</p>\n<p></p>\n<p># journeys monitored (Bus) / # journeys scheduled (Bus)</p>\n<p></p>\n<p>The reasons why a service may not be monitored include BTS equipment or systems failures, reference data and timetable issues, failure of a bus to be allocated to a timetabled services and a service cancellation. Some of these factor are not in the direct control of bus operators.</p>", "id": "11743", "name": "Proportion of services monitored", "ref_number": "AT-11743"}, {"attribute_display_order_id": 3, "db_format": "DOUBLE", "db_name": "% ontime (ArrDep|tp)", "definition": "<p>Proportion of services arriving no more than 4 minutes and 59 seconds late and departing no more than 59 seconds early at timing points.</p>\n<p></p>\n<p># of services arriving no more than 4 minutes and 59 seconds late and departing no more than 59 seconds early at timing points / # of services observed arriving and departing at timing points.</p>", "id": "11744", "name": "Punctuality - Ontime arrival and departure at timing points", "ref_number": "AT-11744"}, {"attribute_display_order_id": 4, "db_format": "DOUBLE", "db_name": "# service unique", "definition": "Number of unique services scheduled to operate in the bus tracking system.", "id": "11740", "name": "Number of unique services in timetable", "ref_number": "AT-11740"}, {"attribute_display_order_id": 5, "db_format": "DOUBLE", "db_name": "# journeys monitored (Bus)", "definition": "<p>Number of scheduled services monitored by the bus tracking system (BTS) at one or more location.</p>\n<p></p>\n<p>The reasons why a service may not be monitored include BTS equipment or systems failures, reference data and timetable issues, failure of a bus to be allocated to a timetabled services and a service cancellation. Some of these factor are not in the direct control of bus operators.</p>", "id": "11735", "name": "Number of scheduled services monitored", "ref_number": "AT-11735"}, {"attribute_display_order_id": 6, "db_format": "DOUBLE", "db_name": "# ontime (ArrDep|tp)", "definition": "Number of services arriving no more than 4 minutes and 59 seconds late and departing no more than 59 seconds early at timing points.", "id": "11739", "name": "Number of services ontime", "ref_number": "AT-11739"}, {"attribute_display_order_id": 7, "db_format": "DOUBLE", "db_name": "# not ontime (ArrDep|tp)", "definition": "Number of services arriving more than 4 minutes and 59 seconds late or departing more than 59 seconds early at timing points.", "id": "11738", "name": "Number of services not ontime", "ref_number": "AT-11738"}, {"attribute_display_order_id": 8, "db_format": "DOUBLE", "db_name": "# punctuality events (ArrDep|tp)", "definition": "Number of punctuality events monitored", "id": "11741", "name": "Number of punctuality events delivered", "ref_number": "AT-11741"}, {"attribute_display_order_id": 9, "db_format": "DOUBLE", "db_name": "# loaded", "definition": "<p>Number of journeys loaded in Smartrak bus tracking system.</p>\n<p></p>\n<p>Note: Prior to mid 2019 some services were monitored by a different bus tracking system. This systems did not handle loading and allocation of services in the same manner as the Smartrak system. Loading and allocation data is only provided for the Smartrak system services in this report.</p>", "id": "11737", "name": "Number of services loaded in bus tracking system", "ref_number": "AT-11737"}, {"attribute_display_order_id": 10, "db_format": "DOUBLE", "db_name": "# allocated", "definition": "<p>Number of journeys allocated in the Smartrak bus tracking system.</p>\n<p></p>\n<p>Note: Prior to mid 2019 some services were monitored by a different bus tracking system. This systems did not handle loading and allocation of services in the same manner as the Smartrak system. Loading and allocation data is only provided for the Smartrak system services in this report.</p>", "id": "11736", "name": "Number of services allocated in bus tracking system", "ref_number": "AT-11736"}, {"attribute_display_order_id": 11, "db_format": "DATE", "db_name": "Date", "definition": "Date on which services are run", "id": "12018", "name": "Date (Metropolitan Bus)", "ref_number": "AT-12018"}, {"attribute_display_order_id": 12, "db_format": "TEXT", "db_name": "Line/Route", "definition": "Line/Route on which services are run", "id": "12019", "name": "Line/Route (Metropolitan Bus)", "ref_number": "AT-12019"}] |
| Ckan url | https://discover.data.vic.gov.au |
| Datastore active | True |
| Datastore contains all records of source file | True |
| Edc sync | True |
| Has views | True |
| Hash | 20d99b7c4b23724e5481557c4588039f |
| Historical | False |
| Id | 41756c13-191b-47c5-ae3c-4406f4e32469 |
| Ignore hash | False |
| Mimetype | text/csv |
| Open dataset title | Metro Bus Operational Performance (MR4) |
| Original url | https://opendata.transport.vic.gov.au/dataset/ad5c3923-db19-4f53-b78d-5a2df040ca07/resource/41756c13-191b-47c5-ae3c-4406f4e32469/download/metro_bus_operational_performance_by_month.csv |
| Package id | eb77556d-c8c1-4e57-adcd-eb2e33a7e8aa |
| Period end | 2026-10-31 |
| Period start | 2017-07-01 |
| Position | 6 |
| Queue name | default |
| Resource id | 41756c13-191b-47c5-ae3c-4406f4e32469 |
| Set url type | False |
| State | active |
| Task created | 2026-11-12 15:36:24.679705 |
| File size (bytes) | 8.7 KB |
| Temporal Coverage Start | 1 July 2017 |
| Temporal Coverage End | 31 October 2026 |