Use Cases | VIGIL by ARRC Global

Sector 01 · Data Centre

"The decision was made before the constraint was found."

Data centre development moves fast.
Constraints do not wait.

The Failure Pattern

A site is selected. Capital is committed. The architect is engaged. The planning application is filed. Then — eighteen months into the project — someone discovers the constraint that was always there.

01
Power constraint found after lease execution. Grid connection feasibility is assessed using publicly available tariff data. Actual MW availability from the named grid operator — the number that determines whether the project is viable — is confirmed during detailed design. At the point where reversing the decision costs as much as proceeding with the constraint.
02
Hazardous adjacency identified after the architect is appointed. A petroleum storage facility 180 metres east is identified during planning — not site selection. The blast separation requirement enters the design at the point where it causes maximum disruption to the layout and maximum cost to the capex budget.
03
Connectivity assumption rather than confirmation. The site is selected on the basis that a major carrier has infrastructure nearby. Nearby means a trunk route 2.1km away with no planned extension. Carrier-neutral connectivity is absent and cannot be established within the project timeline.
04
Climate headroom not designed in. A site where peak ambient already exceeds 48°C is designed to a standard cooling specification. Within seven years, the design temperature is regularly exceeded. The constraint was in the IPCC projections for that region at the time of assessment. Nobody checked.
05
Regulatory timeline underestimated. A new market is entered on the basis that the regulatory framework is "developing favourably." Licensing, data localisation, and mandatory redundancy requirements are not assessed against the project timeline. Operations are delayed by fourteen months after construction completes.

Where it broke down

The constraint existed before the decision was made. In every case, the information was available in public databases, grid operator records, planning authority documents, and published climate projections. It was not collected, structured, and scored in a way that made it visible at the right moment.

The methodology was subjective. A consultant applied professional judgement. A different consultant, on the same site, with the same information, would have produced a different score. Neither score could be defended when challenged.

The confidence level was unknown. A finding with MCI 34 was presented with the same confidence as one with MCI 91. There was no mechanism for that question to be asked — let alone answered.

The future was not assessed. The site was suitable at the time of assessment. Whether it would remain suitable over a 20-year lifecycle — given climate trajectory, urban expansion, and regulatory evolution — was never asked.

What VIGIL changes

Before lease

Power feasibility confirmed from named grid operator

Grid Connection Feasibility scored against five anchor statements. A score of 0.75 requires the named operator confirmed and the connection pathway confirmed. A score of 1.00 requires written confirmation with MW commitment. The difference between 0.50 and 0.75 is the difference between an assumption and a finding.

Before architect

Hazardous adjacency mapped and scored

All hazardous facilities within defined radii pulled at the moment of assessment. A petroleum depot at 180 metres is not discovered during planning — it is scored at site evaluation. Constraint Significance = Severity × Cost × Permanence. It enters the design brief as a blast separation requirement.

Before design

Carrier diversity confirmed or flagged

Telecom Route Diversity scored using the number of independent carriers with active infrastructure within 2km — confirmed from named provider data, not proximity to trunk routes. Carrier-neutral connectivity is a condition of the site selection verdict.

At assessment

Climate headroom built into design basis

MRI scores temperature trajectory against IPCC projections for the specific region. A site where peak ambient is projected to exceed 52°C by 2040 receives a deteriorating lifecycle score. The cooling specification is designed to the 20-year ambient — not the commissioning-day ambient.

Before commitment

Regulatory pathway mapped to project timeline

Licensing, data localisation, and mandatory standards assessed against the specific project timeline — not characterised as "developing favourably." Regulatory risk scored as a domain indicator with its own confidence rating.

Always

Evidence trail complete at every score

Named source, recorded date, anchor statement selected. Never reconstructed after the fact. The finding can be opened, audited, and defended in any room — by anyone — at any point in the asset lifecycle.

"The constraint was always there. The trajectory was always visible. The question was never structured correctly before the decision was made — and the methodology never ran long enough to find the answer."

Sector 02 · Supply Chain Node

"The site was perfect. Until the supply chain moved."

Location was assessed.
Environment was not.

The Failure Pattern

Port-adjacent logistics assets and regional distribution hubs are selected for their location advantages: port proximity, highway access, workforce catchment. The assessment stops at location. It does not assess what is happening to the environment around it — or what the site will look like in year ten of a twenty-year lease.

01
Cargo theft risk underestimated at site selection. The site scores well on standard country crime indices. What the index does not capture is organised cargo theft on the specific approach routes — visible in freight operator incident data and local enforcement records, but not in the aggregate index used in the assessment.
02
Single-provider power dependency not identified. A bonded warehouse requires continuous cold chain power. The site has a grid connection. Whether there is a redundant feed, whether the substation has a history of outages, or whether the grid operator's expansion plan will relieve capacity pressure before the lease expires — none of this was assessed.
03
Labour unrest on access routes not captured. Industrial action at a neighbouring facility, a fuel depot, or the port authority creates an access disruption that is not a security incident — it is a supply chain incident. It was predictable from historical labour relations data. It was not assessed.
04
Flood risk reclassified after commitment. The site is assessed as outside the 1-in-100 year flood zone. Within four years, updated climate modelling reclassifies the adjacent tidal drainage channel. The site is now in the 1-in-75 year zone. Insurance cost increases 40%. The trajectory data was available at assessment. The MRI component was never run.
05
Port expansion changes the risk environment. The terminal expands. HGV volume on access routes increases 60%. Congestion exposure — a scored VIGIL indicator — transforms the site's operational viability within five years of commissioning. The expansion plan was in the port authority's published development programme at the time of site selection.

Where it broke down

Location was assessed. Environment was not. Site assessments focused on what the site has — port proximity, road access, racking capacity. Not what is happening around it — adjacent hazards, labour relations trajectory, flood reclassification trend.

Cargo crime was treated as a country risk, not a route risk. Country-level indices do not capture route-specific patterns. The difference between a 12-minute access route across an industrial corridor and a 4-minute controlled highway route is significant — and invisible in aggregate data.

The lifecycle was not considered. A twenty-year lease is a twenty-year commitment to the risk environment. Port expansion plans, road investment programmes, flood trajectories, and grid capacity additions were all in published data. None were assessed.

What VIGIL changes

Site evaluation

Cargo crime scored on routes, not country index

Theft and Cargo Crime Risk scored using freight operator incident data and route-specific patterns. The difference between MSI 82 and MSI 74 on this indicator is the difference between a controlled-access site and one with three high-risk HGV ambush points on the approach route.

Infrastructure

Power redundancy assessed, not assumed

Single-Point Dependency Exposure is a scored indicator. The number of mission-critical dependencies with a single provider and no backup is counted — not inferred. A cold chain facility with one grid operator, one water provider, and one access route has a fundamentally different risk profile from one with confirmed redundancy.

Lifecycle

Flood trajectory assessed against 20-year lease

MRI scores water stress trajectory and extreme weather frequency against published climate data. A site in a tidal zone with a deteriorating 20-year trajectory receives an Adverse MRI flag before commitment — not after reclassification. The insurance brief and drainage specification are informed by the trajectory.

Labour environment

Industrial relations assessed as a scored indicator

Labour Relations and Access Disruption Risk scored using historical industrial action data in the district, union coverage at adjacent facilities, and access route redundancy. Predictable disruption is captured before the lease is signed.

Portfolio

Congestion exposure tracked through operations

When port expansion is announced, when road infrastructure funding is confirmed or withdrawn, when HGV volume trends shift — the VIGIL record is updated and the site's operational viability reassessed against the original baseline. The board sees the change before operations feel it.

Always

Environment, not just location

Every VIGIL assessment evaluates both the site characteristics and the operating environment around the site — adjacent risks, access route quality, labour environment, trajectory of each. Location is necessary. It is not sufficient.

Sector 03 · Critical Infrastructure

"The assessment was conducted. The finding could not be defended."

The finding belongs to
the person who produced it.
Until it is challenged.

The Failure Pattern

Critical infrastructure sites — power generation facilities, water treatment plants, telecoms nodes — carry the highest consequence of failure of any built asset class. They are also among the most complex to assess: long regulatory pathways, sensitive adjacencies, multi-decade operational lifecycles, and intense scrutiny from regulators, insurers, and government. When these assessments fail, the failure is not technical. It is structural.

01
The finding cannot be reproduced. Two qualified assessors evaluate the same substation site with the same information and produce scores that differ by nineteen points. Neither score is wrong — both reflect genuine professional judgement. Neither can be defended against the other. The regulator asks which one to use. There is no answer.
02
The evidence trail is incomplete after the fact. A security assessment is conducted. Two years later, an incident occurs. The investigation asks for the evidence behind the original risk rating. The evidence exists in the assessor's notes, email threads, and memory. It cannot be reconstructed into an auditable record. The finding cannot be defended.
03
The confidence level is invisible to the buyer. A national power authority commissions a security assessment for a new generation facility. The assessment is delivered. The confidence level behind the finding — how much of it is verified primary data and how much is professional inference — is never stated. Nobody asks. Nobody knows. The finding is acted upon at face value.
04
The 30-year asset is assessed on today's threat environment. A water treatment facility sited in 2024 will operate until 2054. The threat environment will not stand still. Climate stress on water supply catchments, geopolitical shifts, and urbanisation of the surrounding area are all in trajectory data available at assessment. The assessment reflects 2024. Operations will face 2044.
05
Regulatory compliance is assumed, not assessed. A new energy facility is designed to meet current regulations. The regulatory trajectory — pending updates, consultation responses, and government policy direction — is not assessed as an indicator. Within three years, new requirements demand a retrofit that was foreseeable from published regulatory consultation documents at the time of design.

Where it broke down

The finding was personal, not institutional. Every critical infrastructure assessment produced by a consultant is a personal finding. It belongs to the person who produced it. When that person is unavailable, the finding cannot be audited or reproduced. It cannot be updated by someone else without starting again.

The evidence was never structured. Notes, emails, site observations — none of it was structured into a named, dated, sourced record that could survive regulatory scrutiny. Producing the audit trail after the fact is reconstruction, not documentation.

The long-horizon question was never asked. A thirty-year asset in a changing threat environment requires a thirty-year assessment. The question of where the environment is heading — and whether it will remain compatible with the mission over the asset's full lifecycle — requires a trajectory methodology that standard assessments do not have.

What VIGIL changes

Reproducibility

Same site, same evidence, same result

VIGIL's anchor statement methodology generates scores from evidence, not judgement. Two assessors, same site, same data, same framework: same result. The finding is institutional. It holds regardless of who ran it or when.

Evidence trail

Built in, not reconstructed

Every indicator scored carries a named source, a recorded date, and the anchor statement selected. The evidence trail is created at the moment of assessment — not reconstructed when scrutiny arrives. It is always complete.

Confidence

MCI stated on every finding

A critical infrastructure assessment with MCI 88 and one with MCI 61 are explicitly, visibly different. The regulator, the insurer, and the board can see the difference. Acting on a low-confidence finding is a choice — not an unavoidable condition.

Trajectory

30-year asset assessed on 30-year horizon

The MRI projects the risk environment trajectory over the asset's operational lifecycle — incorporating climate stress, geopolitical direction, urbanisation trends, and regulatory evolution. The 2054 operating environment is estimated at 2024 assessment. The design brief responds to both.

Regulatory

Trajectory assessed, not status assumed

Regulatory Environment is a scored domain indicator. Pending consultations, policy direction, and international regulatory alignment are assessed as trajectory items — not binary compliance checkboxes. A regulation that is two years away is visible in the assessment, not a surprise in the design programme.

Governance

Defensible in any room, at any point

The VIGIL record travels with the asset. Five years after the original assessment, when the regulator, the insurer, or an acquirer's legal team asks for the evidence behind the original rating — it is complete, structured, and immediately producible. Not reconstructed. Not approximated. Complete.

The constraint was
always there.

Data centre development moves fast.
Constraints do not wait.

Location was assessed.
Environment was not.

The finding belongs to
the person who produced it.
Until it is challenged.

Four failures that repeat
regardless of sector.

Which of these patterns
are you about to repeat?

The constraint wasalways there.

Data centre development moves fast.Constraints do not wait.

Location was assessed.Environment was not.

The finding belongs tothe person who produced it.Until it is challenged.

Four failures that repeatregardless of sector.

Which of these patternsare you about to repeat?

The constraint was
always there.

Data centre development moves fast.
Constraints do not wait.

Location was assessed.
Environment was not.

The finding belongs to
the person who produced it.
Until it is challenged.

Four failures that repeat
regardless of sector.

Which of these patterns
are you about to repeat?