2023–2024
The commissioning register that became the program’s reference
A single traceable record of every asset, its required tests, its results and its evidence — across more than twenty-five station facilities.
- Excel
- SharePoint
- Power BI
- DAX
- Power Apps
The problem
Commissioning a transit program generates an enormous volume of evidence: check-out reports, acceptance tests, integration tests, compliance records. Most of it was technically correct and practically unusable, because it lived in a hundred places. On any given morning nobody could say with confidence what was actually finished.
What I did
I built an asset-and-test register that traced every facility asset through its required sequence — post-installation check-out, site acceptance testing, system integration testing and integrated system testing — with attributes, responsible party, status, results and retained evidence attached. The governance mattered as much as the structure: the register had to survive scope growth, changes of custodian and the addition of scopes it was never designed for.
What changed
It became the program reference for commissioning status. The model was subsequently adopted by the Systems Commissioning team and extended across their asset base — which is the only real test of whether a data structure works: other people choose to use it.
What I took from it
The instinct I would keep is to design for the handover from day one. The register was useful during delivery, but its real value showed up at the transition into maintenance, when the asset record had to stand on its own without anyone available to explain it.