Technical Embedding
From February 2019, we operated inside ACCIONA's technical infrastructure:

• Direct AWS infrastructure access

• Shared development environment with Acciona's IT team

• 6 iPads procured and configured with company-managed Apple IDs (on our accounts initially for speed, then transferred)

• Web platform hosted on Acciona's AWS subscription (65-month lifecycle)

We didn't build something and throw it over a wall. We built it inside their infrastructure so when the inevitable handoff came, it wasn't a migration - it was a permissions change.

Decision Embedding
Tunnel conditions don't wait for procurement cycles. When field crews encountered unexpected geological zones at Western Harbour, requirements changed that week—not that quarter.

Example from the PTT (Permit to Tunnel) module: Acciona needed two different forms for two different excavation methods (road header vs. TBM). TBM forms needed only 50% of the data fields that road header forms required. In a traditional agency model, this would be "out of scope, new quote, 6-week lead time." We adapted the forms in a two-week sprint because we were embedded in their workflow, not operating at arm's length.

Capability Transfer Embedding
The 7-year engagement wasn't 7 years of dependency. It was 7 years of progressive capability transfer:

• 2019-2021: We built, they operated the app in the field.

• 2022-2023: We added features, they started making configuration changes themselves.

• 2024: Infrastructure migration from WorldTeam AWS to Acciona's IT-managed AWS. They took full ownership.

• 2025-2026: Advisory capacity only—they run everything, we're on call for edge cases.

By September 2024, when the infrastructure migration completed, Acciona's IT team could deploy updates, manage access, troubleshoot issues, and extend functionality without us. That was the goal from day one.

Build Structure: Adaptive Platform, Not Fixed Deliverable

Phase 1: Foundation (February–March 2019)

JIRA Evidence: 50 issues closed in 2 months (21 Epics, 20 Tasks)

The initial build focused on transplanting the WestConnex 3a solution to Western Harbour Tunnel:

• Wireframes V1 and V2

• Requirements documentation workshops with field crews

• UI design adapted for Western Harbour's specific geological zones

• Cost estimation and milestone planning

Critical decision: We didn't rebuild from scratch. 80% of the WestConnex solution was reusable. We focused the first 8 weeks on the 20% that was project-specific:

• Updated branding and project specifications

• New geological zone classifications for Western Harbour

• Modified dropdown menus and data fields for different rock types

• Improved filtering system for the web platform

Law 6 (Adaptive Replanning): The waterfall model says "requirements first, then build." Tunnel geology says "requirements emerge as you dig." We built a configurable platform rather than a fixed application—dropdown menus could be updated without redeploying the entire app, data fields could be added as new geological zones were discovered.

Phase 2: Field Deployment (April–December 2019)

6 iPads deployed to field crews. Geological mapping started.

First contact with reality: Field crews were mapping every 3-5 meters. At 7 kilometers, that's ~15,000 mapping events over the project lifecycle. The original design assumed crews would fill out detailed forms for every mapping point. Reality: crews needed two different form types—one for routine mapping (50% of fields), one for detailed mapping when anomalies were detected.

We adapted in a 3-week sprint: created "quick mapping" and "detailed mapping" templates. Routine mapping took 2 minutes instead of 8. Crew adoption went from "this is annoying bureaucracy" to "actually useful for risk assessment."

Phase 3: Geo-Referencing Integration (2020)

New requirement emerged: Acciona's client wanted geo-referenced visual maps showing tunnel alignment with each mapping record anchored to specific chainage (distance along the tunnel).

This wasn't in the original scope. It came up because the client's engineers wanted to click on a map and see all historical geological data for that specific tunnel section—not search through spreadsheet exports.

Law 5 (Shared Downside): In a fixed-price contract, this would be "change order, new quote." In our outcome-based model (12.5% of fees tied to system usability and compliance reporting), if the client couldn't access data effectively, we didn't get paid in full. We built the geo-referencing integration in 6 weeks because it directly affected the KMR.

Phase 4: Monthly Reporting Automation (2021-2022)

Acciona had to report to their client every month: consolidated PDF showing all mapping records for that period plus statistical analysis (percentage of rock types, groundwater distribution, anomaly count).

Initially, this was semi-manual: export spreadsheet, run pivot tables, copy-paste into a template, generate PDF. Took a project admin 2-3 hours per month.

We built an automated reporting function:

• Select time period (e.g., "June 2023")

• Select tunnel drive

• Click "Generate Monthly Report"

• System produces: cover page, consolidated PDF of all mapping records with photos, statistical histograms and pie charts, anomaly highlights

Report generation time: <10 minutes. More importantly, consistency: every report followed the same structure, no manual copy-paste errors, no missing records.

Phase 5: Infrastructure Migration (2024)

By 2024, the system had been running for 5 years. Acciona's IT team had learned the architecture through osmosis—not formal training, but through working alongside us on feature additions, troubleshooting, and configuration changes.

September 2024: Full infrastructure handoff. AWS account migrated from WorldTeam management to Acciona IT management. Permissions transferred. Documentation updated. Runbooks created for common scenarios.

Critical handoff principle (Law 8): We didn't "train them and leave." We progressively reduced our role over 5 years until the handoff was administrative, not technical. They already knew how to run it—we just formalized ownership.