REINSURANCE · FUNCTION · 04RDM-03
SURFACE 10 / REINSURANCE / FUNCTION
TECHNICAL RISK / ENGINEERING
For technical risk and engineering, RDM-03 lives or dies on mechanism: how large-load behaviour interacts with the grid, what protections operate, what propagates, what interrupts the chain, and what evidence would disprove it.- Function
- Technical Risk / Engineering
- Surface question
- Mechanism boundary. What physical mechanism, operational dependency and mitigation would have to exist for the risk to be real? The bounded decision boundary is owned by each institution; see its profile.
- Role classes
- Head of Risk Engineering / Head of Technical Risk / Chief Engineer, Energy and Infrastructure · decision-owning role classes, confirmed per institution from public role evidence; not title-first routing.
- Governing question
- WHAT PHYSICAL MECHANISM, OPERATIONAL DEPENDENCY AND MITIGATION WOULD HAVE TO EXIST FOR THE RISK TO BE REAL?
GUARD & CREATE
Each row shows a separate decision pathway through the dependency: what this function may need to guard from it, what the dependency could help it create, and which decision may change.
| # | Decision area | Guard from this dependency | Create with this dependency | Decision question |
|---|---|---|---|---|
| 01 | INITIATING MECHANISM | A generic 'data-centre risk' label can hide whether correlated load withdrawal is actually plausible. | Mechanism-level analysis can separate RDM-03 from ordinary outage or equipment-failure narratives. | What exactly must initiate for RDM-03 to occur? |
| 02 | LOAD BEHAVIOUR | Large computational loads may not behave independently during grid disturbance. | Understanding protection and disconnection behaviour could reveal where synchronisation is plausible or bounded. | Under what conditions could large loads disconnect in a materially correlated way? |
| 03 | GRID RESPONSE | A rapid loss of load can create frequency or voltage effects outside the immediate site. | A system-response map could identify where propagation is physically credible and where it stops. | What grid response would have to follow the initiating event for RDM-03 to matter? |
| 04 | PROTECTION SYSTEMS | Protection logic may either amplify correlated withdrawal or prevent it. | Testing protection assumptions could identify mitigation already present in the system. | Which protection settings or architectures would strengthen or weaken RDM-03? |
| 05 | REDUNDANCY / BACKUP | Site redundancy may protect the data centre without removing the system-level dependency. | A distinction between site resilience and grid compatibility could improve engineering assurance. | Where could conventional resilience measures fail to address the RDM-03 mechanism? |
| 06 | PROPAGATION PATH | The wider consequence is modelled rather than observed end-to-end. | A bounded propagation analysis could identify the minimum chain that must survive before insurance relevance is considered. | Which links in the RDM-03 pathway are necessary, and which are speculative? |
| 07 | MITIGATION | Controls may already exist that materially reduce the probability or severity of the dependency. | The same analysis can identify high-leverage interventions instead of merely describing exposure. | Which interventions could most directly break the RDM-03 chain? |
| 08 | DISPROOF | Technical analysis can drift into confirmation unless explicit falsifiers are defined. | A disproof-led test can eliminate weak dependency claims early. | What observation would make the technical team reject RDM-03? |
This is the governing question for this decision territory. The matrix above decomposes it into the smaller consequences, opportunities and questions that can be tested independently.
GUARD · CONSEQUENCE REPORT
Mechanism integrity, resilience assumptions, mitigation options, operational dependencies and engineering tests.
CREATE · OPPORTUNITY REPORT
Assurance, mitigation, resilience services and engineering controls around the dependency.