
Thirteen sections of integrated analysis. Built from the Business Case, the Project Definition Plan, the signed Participation Agreements, the Use Case Scope Definition V1.4, and the current technology contracts.
Landgate's RFQ asks for a strategic review of one specific component of the Spatial WA Program: the use case that carries the largest concentration of the Program's expected benefits. The integrated documentation now lets us name it precisely. The use case is Use Case 3, formally titled Infrastructure Projects and Assets (IP&A), led by the Public Transport Authority on behalf of the post-MoG Department of Transport and Major Infrastructure.
The RFQ's phrasing ('Infrastructure Planning and Assets') is slightly different from the Program's formal naming ('Infrastructure Projects and Assets'), but they refer to the same use case. The Use Case Scope Definition V1.4 (October 2025) is the live operational specification.
What Nicole has committed to in Stage 1 (proposal, p4):
Deliverable: a 15 to 20 page Strategic Review Report to the Program Director and Program Board, due 30 June 2026. This working document is the substrate the Strategic Review Report will be built upon, once the stakeholder interview findings come in.
This is version 2 of the working analysis. Version 1 was written from the Business Case and Cost Benefit Analysis alone. Version 2 integrates the Project Definition Plan, its critical appendices (Strategic Alignment, Use Case Scope Development, Implementation Plan, Agency Participation Agreements, Benefits Management Plan), the live Use Case Scope Definition V1.4 dated October 2025, the Implementation Kickoff Working Group materials from February 2026, and the current Advisory Onboard deck. Several of v1's open hypotheses are now answered; others remain and have sharpened.
The Business Case described ten quantified use cases and three qualitative ones. The Project Definition Plan, signed and approved in January 2024, consolidated the ten quantified use cases into four priority use cases for Horizon One, plus added one net-new theme (emergency management exposure modelling).
The current operational scope, as of the Use Case Scope Definition V1.4 (October 2025), is:
| # | Use case | Lead agency | Origin in the BC |
|---|---|---|---|
| UC1 (Obj 1) | Administrative Boundaries for 4D Land Management (AB4D) | Landgate | Absorbed BC use cases 3.1 (DBCA), 14.1, 14.2, 14.3, 14.4 (Landgate) |
| UC1 (Obj 2) | Unlocking Land Potential for Investment (ULPI) | Landgate | Absorbed BC use case 9.1 (DPIRD) |
| UC2 | Digital Approval Workflows (DAW) | DPLH | Absorbed BC use case 2.1 (City of Swan/LGs). Was flagged in the BC as 'not yet aligned' to Planning Reform; the alignment has now happened |
| UC3 | Infrastructure Projects & Assets (IP&A) | PTA (for DTMI) | Absorbed BC use cases 16.1 (OMTID, $204.6m), 17.1, 17.2 (PTA, $49.9m), and likely 5.1, 5.2 (DoT). Approximately $254m of the BC's $394m quantified benefits sit inside this use case. |
| UC4 | Exposure Modelling for Emergency Management (EMEM) | DFES | Net new. Not in the BC's ten quantified use cases |
This consolidation is the single most important shift between the Business Case and the current Program. The BC's benefits structure was built bottom-up from agency-specific use cases. The PDP rolled them into themes that can be delivered cross-agency, with named lead agencies accountable for each theme.
Technology contracts were awarded in October 2025:
Both contracts commenced 27 October 2025, with a seven-year initial term and Landgate options to extend by 5 + 3 years. Implementation runs to mid-2028 across staged releases. As of February 2026, the Program is at the Working Group kickoff stage for implementation, having just onboarded the technology partners.
The Benefits Management Plan (PDP Appendix M) is explicit about what happened to the BC's quantified benefits:
In other words: the PDP took the BC's $394m use case PV and $1.1bn WEB PV at face value, reorganised them under four themes, and committed to recalibrate later via the Benefits Management Plan. Specifically, methodology step 4 in the BMP is to 'Validate the estimated benefits from the CBA (and recalibrate if necessary)'. Recalibration is in scope. It has not yet happened.
This matters for two reasons:
| BC use case | PV ($M) | Now sits within |
|---|---|---|
| 16.1 Minimise utilities impact on transport projects (OMTID) | 204.6 | IP&A (UC3). Water Corp now framed as a stakeholder, not co-lead |
| 9.1 Locating future land/water development (DPIRD) | 54.6 | UC1 Obj 2 · ULPI (Landgate-led) |
| 20.1 Buried services (Water Corporation) | 48.5 | IP&A (UC3) as utility data theme. No Water Corp Participation Agreement |
| 17.1 Built infrastructure and assets lifecycle assurance (PTA) | 40.4 | IP&A (UC3) · PTA-led |
| 2.1 Development & Building application processes (City of Swan) | 25.5 | DAW (UC2) · DPLH-led |
| 17.2 Geospatial engineered BIMs (PTA) | 9.5 | IP&A (UC3) |
| 14.2 Urban Forest visualisation (Landgate + LGs) | 3.8 | AB4D (UC1 Obj 1) data theme |
| 14.3 Spatial GPR (Landgate + RIA) | 3.5 | AB4D (UC1 Obj 1) data theme |
| 3.1 4D Land ownership boundaries (DBCA) | 3.0 | AB4D (UC1 Obj 1) · DBCA signed as support agency |
| 14.1 Reduce effort to adjust spatial cadastre (Landgate) | 0.6 | AB4D (UC1 Obj 1) · Landgate internal |
| 394.0 |
The structural picture: of the BC's $394m use case PV, approximately $254m (64.6%) is now bundled inside IP&A (UC3, PTA-led). Approximately $80m sits inside the Landgate-led use cases. $48.5m (Water Corp's old Buried Services line) is in IP&A's stakeholder pool but has no formal Participation Agreement underneath it. $25.5m (Local Government processing benefits) is inside DAW (UC2, DPLH-led).
With the PDP consolidation now visible, the v1 stress-test holds up but the locations of strength and weakness are clearer.
The BMP says the recalibration of the CBA benefits has not been done yet. When it is, three lines are exposed:
The Strategic Review Report can quietly anchor recommendations in the use-case BCR of 3.8 (which is robust) rather than the headline 14.4 (which is not), and recommend that the BMP recalibration be brought forward.
PDP Appendix A (Strategic Alignment) reaffirms the BC's strategic anchors with two small but consequential updates:
The other anchors continue: Digital Strategy 2021-25 (sunsetting this year), Streamline WA, Interoperability Policy, Open Data Policy, plus the Cloud Policy (newly added in the PDP) and compliance policies (Digital Services, ICT Disaster Recovery, Cyber Security, Information Classification).
Per the Advisory Onboard deck, the Program is positioned against four of the six current Government strategic priorities to 2029: Diversifying the economy, Housing, Safe & Inclusive communities, Infrastructure Services. (Not Healthcare or The Environment.)
The Use Case Scope Definition V1.4 (October 2025) is the live spec for Infrastructure Projects & Assets. The intent and structure are now well-defined, with a chosen demonstration site, an initial utility focus, and a documented release plan.
| Stakeholder group | Members |
|---|---|
| State Government · major transport infrastructure | Public Transport Authority (lead), Department of Transport & Major Infrastructure, Main Roads WA, Office of Major Transport Infrastructure Delivery, Westport, Infrastructure WA, Office of Major Infrastructure Delivery |
| State & Local Government · surrounding precincts | City of Swan, Development WA |
| Utility Service Providers | Water Corporation, Western Power |
| Infrastructure Delivery Consortiums | Midland Junction Alliance |
Two things to note here. First, Westport appears as a stakeholder. Nicole is Chair of Westport. This is a material disclosure beyond the IWA chair tenure already declared in the proposal's conflict of interest statement. The COI declaration should be extended to cover Westport, with the same management controls applied. Second, OMTID and OMID both appear as separate stakeholders, suggesting both entities exist post-MoG with related but distinct mandates. OMID is likely the broader new infrastructure delivery office; OMTID continues as the transport-specific one.
The IP&A Use Case Lead operational role is a PSCA Level 8 position, funded by Landgate but embedded within PTA, paired with a Level 6 Data Analyst. The role was created under the August 2023 Participation Agreement and is the operational interface between PTA, the Program Team, and the wider stakeholder ecosystem. Its responsibilities, per the signed agreement:
That role being vacant for five months, in the same period as the Transport Portfolio MoG settled, explains the 'limited traction' the RFQ describes. Reinstating it is necessary but not sufficient. The new incumbent needs both technical capability and credible standing with the wider DTMI stakeholder ecosystem, which is precisely the gap Nicole's Stage 2 advisory role is designed to fill while the operational role is being re-staffed.
The PDP's Appendix J contains five signed Participation Agreements. These are the formal organisational commitments to the four PDP use cases:
| Use case | Lead/support agency | Signatory | Role | Date signed |
|---|---|---|---|---|
| IP&A (UC3) | PTA (lead) | Russell Taylor | Chief Information Officer | 7 Aug 2023 |
| DAW (UC2) | DPLH (lead) | Anthony Kannis | Director General | 25 Aug 2023 |
| AB4D (UC1 Obj 1) | DMIRS / DMPE (support) | Richard Sellers | Director General | 17 Aug 2023 |
| AB4D (UC1 Obj 1) | DBCA (support) | Stuart Smith | Director General | Sep 2023 |
| EMEM (UC4) | DFES (lead) | Darren Klemm | Commissioner | 30 Aug 2023 |
Three things stand out from these signed commitments:
Per the Advisory Onboard deck, the Program Board's named agency sponsors are: Landgate, PTA, DPLH, DFES, Infrastructure WA, Treasury, and the Office of Digital Government. Seven agencies. The Board operates under the Landgate Board (which reports to the Minister for Lands). It interacts with two external committees: MPERSC (Major Projects Expenditure Review Sub-Committee) and the Office of Digital Government's contract management governance. It also reports to WALIS Council and DALAC.
This is a more developed governance structure than the BC described, with explicit MPERSC oversight that wasn't named in the BC.
Named roles in the current Program team (per the Advisory Onboard deck):
The Program is not under-resourced at the centre. The gap is at the agency embedded layer, specifically in PTA for IP&A.
The MoG decision document itself is not in our document set. The new structure is inferable from current Working Group composition and the Advisory Onboard deck, but several mappings are unconfirmed.
The new input set fills most of the gaps v1 identified. What remains useful but absent:
The PDP commits to delivery of Horizon One implementation by June 2028. The signed Participation Agreements all reference this date. The technology contracts (Accenture for NGSC, Jacobs for SDT) commenced 27 October 2025 with implementation runs sized to complete by mid-2028.
NGSC delivery (Accenture), starting 27 October 2025:
SDT delivery (Jacobs), starting 27 October 2025:
The deadline is for Horizon One implementation completion. Benefits realisation under the BMP runs to 2033. So '2028 benefits' realistically means 'benefits realisation underway by 2028, with the longer tail to 2033'. The question for each of the BC's quantified benefits is: when does the underlying use case capability come live, and how much realisation time does it have between live-date and the political horizon date?
The Focus Area (Midland Station Precinct) is the first IP&A capability live, in late 2026. That gives IP&A approximately 18 months of implementation, 24 months of demonstrable realisation by Horizon One end (June 2028), and an additional 5 years to 2033 for the full realisation tail. By comparison, AB4D capability comes live in mid-2026 in NGSC Release 1, giving it more runway.
If the political horizon is moved earlier (e.g., the State Government wants benefits visible by election cycle rather than 2028), the use cases most exposed are IP&A (newest, broadest, most complex) and EMEM (newest theme overall). AB4D and DAW are more likely to show early measurable realisation.
These are the questions sharpened by the integrated documentation. The list is shorter than v1's because several of v1's questions are now answered.
With the integrated documentation visible, Nicole's positioning is sharper than v1 indicated:
Refined from v1, with the integrated evidence:
That paragraph is testable against the interviews and revisable as the picture sharpens. It is the seed of the Executive Summary.
Threads worth tracking but not for this phase:
End of working analysis version 2. The Strategic Review Report due 30 June 2026 will be built from this analysis plus the stakeholder consultations now underway plus any further inputs that arrive (Risk Register, current Cost Model, Transport Portfolio MoG decision documentation).