Observations and breaches
An observation is one value of an indicator for one date. The system places it in the Green, Amber or Red band; a Red observation needs an explanation and opens a breach that lands in the action register.
Who may do it: the indicator’s owner enters observations; the Entity Risk Manager follows the breaches. See Roles and permissions.
Entering an observation
Section titled “Entering an observation”- Open the indicator, or your list of observations due.
- Enter the value and the date it relates to.
- The system shows the band the value falls in.
- If the band is Red, write the explanation: what caused it and what is being done.
- Save. Your name and the time are stamped on the observation.
Observations can also be loaded in bulk from the standard workbook, and the observations of external KRIs are recorded by BCP Core without anyone typing them.
When an observation is Red
Section titled “When an observation is Red”- The observation is a breach.
- The system creates an action item in the action register, with an owner and a due date.
- The breach stays open, with its age shown, until its action is closed.
Trend and breach views
Section titled “Trend and breach views”- Current status of every indicator, by band.
- Trend — the observations over time, drawn against the bands that applied at each date.
- Open breaches with their age, by entity and by risk.
What the system does or refuses
Section titled “What the system does or refuses”- The band is computed and cannot be chosen — see Computed, never typed.
- A Red observation cannot be saved without an explanation.
- Every breach creates an action item.
- Who entered each observation is stamped, and an observation is never silently overwritten — see Who-filed is stamped.
Related
Section titled “Related”- Thresholds
- External KRIs from BCP Core
- Management review — Red KRIs are one of its inputs