REINSURANCE · FUNCTION · 01 / PRIORITYRDM-03
SURFACE 10 / REINSURANCE / FUNCTION
ACCUMULATION / EXPOSURE MANAGEMENT
RDM-03 does not create one generic accumulation problem. It can disturb several separate decisions inside exposure management: where the boundary sits, what is treated as independent, how correlation is represented, how scenarios are constructed, and where capacity can safely move.- Function
- Accumulation / Exposure Management
- Surface question
- Accumulation boundary. Does the accumulation boundary stop at the data centre? The bounded decision boundary is owned by each institution; see its profile.
- Role classes
- Head of Exposure Management / Global Head of CAT and Exposure Management / Head of Accumulation Control · decision-owning role classes, confirmed per institution from public role evidence; not title-first routing.
- Governing question
- WHERE COULD RDM-03 CONNECT REINSURANCE EXPOSURES CURRENTLY TREATED AS INDEPENDENT?
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 | ACCUMULATION BOUNDARY | The accumulation boundary may stop at the data centre, insured asset or peril while the dependency extends into the grid. | A wider dependency boundary could reveal concentrations invisible in conventional location-based views. | Where could RDM-03 extend the accumulation boundary beyond the data centre itself? |
| 02 | INDEPENDENCE ASSUMPTION | Exposures treated as independent may share the same large-load contingency. | A better independence test could improve aggregation, diversification and portfolio steering. | Where could RDM-03 connect exposures currently treated as independent? |
| 03 | CORRELATION | Correlation may arise through a mechanism that does not sit inside an existing catastrophe or operational taxonomy. | A dependency-led correlation view could expose where aggregate risk is understated or overstated. | Where could RDM-03 create correlation that the current accumulation view does not represent? |
| 04 | EXPOSURE DATA | Current exposure attributes may not contain the variables needed to identify the dependency. | New attributes or proxies could make hidden dependency concentrations measurable enough to manage. | What exposure information would be required to see RDM-03 if it is absent from current data? |
| 05 | SCENARIO DESIGN | Existing scenarios may assume weather, cyber, asset failure or grid outage rather than correlated load withdrawal as the initiating mechanism. | A new scenario class could test a failure pathway conventional scenario libraries omit. | Which current scenarios would RDM-03 challenge if correlated load withdrawal is treated as the initiating mechanism? |
| 06 | AGGREGATE VIEW | Aggregate limits may be calibrated to geographic or peril concentrations while missing dependency concentration. | Dependency-aware aggregation could change where concentration is tolerable and where it is not. | Where could RDM-03 change the organisation's aggregate view? |
| 07 | PORTFOLIO STEERING | Growth can appear diversified while adding exposure to the same hidden dependency. | Better dependency visibility could reveal where the portfolio can grow without increasing the same accumulation. | Where could RDM-03 change the organisation's view of where it can safely grow? |
| 08 | CAPACITY DEPLOYMENT | Capacity may be deployed without visibility of a cross-account common contingency. | A bounded dependency view could support more discriminating capacity decisions rather than blanket caution. | Where could RDM-03 change a capacity decision? |
| 09 | UNDERWRITING HANDOFF | Exposure management may detect a concentration but lack a clear route into underwriting action. | A sharper dependency object could create a direct bridge into underwriting questions, terms, structure or pricing. | Which underwriting decision would need to change if the RDM-03 accumulation survives? |
| 10 | OWNERSHIP / ESCALATION | The dependency may cross exposure, modelling, underwriting and enterprise-risk boundaries without one obvious owner. | A named dependency can create a clearer escalation path and decision owner. | Who owns the decision if RDM-03 crosses existing functional boundaries? |
That is the surface-level governing question. The matrix above decomposes it into the smaller desk decisions an accumulation or exposure-management team may actually need to test.
GUARD · CONSEQUENCE REPORT
Potential aggregation pathways, independence assumptions, concentration questions, scenario boundaries and portfolio steering tests.
CREATE · OPPORTUNITY REPORT
New aggregation views, steering logic and capacity-deployment options.