Skip to content

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.

KRI: from observation to band and breachAn observation is typed in by the KRI owner, imported, or recorded from a BCP level in BCP Core. The system places it in the Green, Amber or Red band by the thresholds in force on its date. A Red observation needs an explanation and opens a breach, which creates an action item.Typed inby the KRI ownerImportedfrom the standard workbookBCP levelNormal → GreenStandby → AmberActivated → RedObservationvalue + dateband computedGreenwithin appetiteAmberearly warningRedexplanation requiredBreachaction item createdowner · due dateLEGENDSourceObservationSystem placesRed to breach
A BCP level change in BCP Core is recorded as an observation: Normal → Green, Standby → Amber, Activated → Red.
BCP level in BCP CoreBand of the observation
NormalGreen
StandbyAmber
ActivatedRed
  1. The BCP head orders a level for a hazard, and the level is saved in BCP Core with its note.
  2. The system records an observation on that hazard’s external KRI, at the time of the change.
  3. The level note is the observation’s explanation — so a Red observation from Activated always has one.
  4. A Red observation is a breach like any other and creates an action item — see Observations and breaches.
  • 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.