External KRIs from BCP Core
Every hazard an entity watches in BCP Core has an external KRI in ERM Core. Each time the entity’s BCP level for that hazard changes, the change is recorded as an observation, so the risk desk sees continuity events in the same place as every other indicator.
Who uses it: the Entity Risk Manager. Nobody types these observations. See Roles and permissions.
How a BCP level becomes an observation
Section titled “How a BCP level becomes an observation”| BCP level in BCP Core | Band of the observation |
|---|---|
| Normal | Green |
| Standby | Amber |
| Activated | Red |
- The BCP head orders a level for a hazard, and the level is saved in BCP Core with its note.
- The system records an observation on that hazard’s external KRI, at the time of the change.
- The level note is the observation’s explanation — so a Red observation from Activated always has one.
- A Red observation is a breach like any other and creates an action item — see Observations and breaches.
What the system does or refuses
Section titled “What the system does or refuses”- External observations are recorded only by BCP Core. They cannot be typed, edited or deleted by hand.
- Only the entity’s own BCP level is recorded. A Group advisory from the parent never creates an observation for a subsidiary.
- The indicator stays the entity’s own. Its definition and calibration remain the Entity Risk Manager’s act — see Thresholds.