Group configuration
Five settings make every company’s report consolidate: the criteria set, the materiality tiers, the reporting periods, the MTPD bands and the hazard set. The group root owns them, and they apply to every entity beneath it. Each company’s data stays its own.
Who may do it: the Group RM, acting at the group root only. Every other role reads the configuration that applies to its entity. A company outside a group is its own root. See Roles and permissions.
What the group configures
Section titled “What the group configures”| Setting | What it decides | Used in |
|---|---|---|
| Criteria set | Likelihood scale, impact dimensions and their levels, and the rating bands and their colours | Scoring a risk · Heat map |
| Materiality tiers | The thresholds that set each loss event’s tier, and who each tier is routed to | Materiality tiers |
| Reporting periods | The year and its cycles; only the group root opens a year | Reporting periods and roll-forward |
| MTPD bands | The bands that give each critical activity its criticality tier | Critical activities |
| Hazard set | The hazards BCP Core watches and warns on, and the scenarios it carries | Hazard page and early warning |
KRI thresholds are not group configuration: each Entity Risk Manager sets and calibrates them for their own entity — see Thresholds.
Change a setting
Section titled “Change a setting”- Sign in with the Group RM role and switch to the group root company.
- Open Group configuration and choose the setting.
- Make the change and write the reason.
- Choose Save. The change is saved as a new version, with who and when, and applies to every entity beneath the root.
What a change does
Section titled “What a change does”- Values are recomputed, never retyped. Tiers, bands and criticality tiers are computed by the system from the setting in force, so nobody re-enters a rating (Computed, never typed).
- History keeps its version. A filing already approved, or a period already frozen, keeps the version it was made under.
- A materiality change can flag a threshold review on loss events whose tier it would move.
- Hazard sets switch without a rebuild. Adding a hazard adds its scenario to BCP Core.
What the system does or refuses
Section titled “What the system does or refuses”- Only the group root changes the configuration. A subsidiary reads it and cannot change it.
- The configuration never reaches into a subsidiary’s records. The subsidiary scores, tiers and files under it, by its own acts (Subsidiary-Independence).
- Every version is kept and recorded in the audit log.