A Year in Operations: Nordvik Region and Hansa Mutual

All courses / AI Operations / Module 7 / Chapter 29

Learning objectives

After the lesson the participant can:

Trace four events of the illustrative year to the control that caught each of them
Explain why the book counts an unchanged level of delegation after twelve months as a result
Compare how the two organisations spent the year and what each could say at its end
Conduct a monthly review of the operations loop from its registers and records

Key concepts

Honest numbers lower than the first dashboards: The first lesson of the year: when independent probes, seeded faults and derived statuses replace self-reported measures, the figures fall. In every case the independent observer reported something worse than the actor, and each organisation was better off for it.
Closure takes longer than any plan: The second lesson: the portal failover failed in October 2027, failed again at its first re-test on 2029-04-10 and passed on 2029-06-05, so the Region could claim a verified failover only after about 20 months.
Autonomy that did not move: The third lesson: no level of delegation rose in the year. The evidence that would justify a raise, a verified claim, a seeded-fault result and a drill inside its target, was assembled for the first time and was not satisfied together.
Year ledger: An extract of the register each organisation keeps: the claims, tests, incidents, drills and decisions of the twelve months with their dates and states, from which the monthly review and the board report are read.
Monthly review of the loop: A one-hour review chaired by the head of operations that reads the register first, lists each claim by expiry and state, schedules what expires, and turns the loop's records into decisions with owners, with quarterly additions of a dark day, a seeded fault and a stop drill.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Interactive exercise 1 · Put in order

The year in order

Put these events of the illustrative year at the two organisations in the order in which they happened.

Interactive exercise 2 · Scenario

No level was raised

Apply the chapter's third lesson of the year.

Teaching plan

15 min	The teacher explains how to read the year, from the two questions of September 2028, and that every person and record is fictional and illustrative while the instruments and studies are real.
25 min	Timeline work: groups place the year's main events on a wall timeline for each organisation and attach to each the rule or artefact from earlier modules that produced or caught it.
10 min	Discussion of the four lessons of the year and the table of delegation in month 1 and month 12.
30 min	Exercise: participants run a monthly review of an operations loop.
10 min	Debrief: what each organisation could say at the end of the year that it could not say in September.

Discussion

Hansa Mutual ended the year with one verified restore claim, one expired failover and no level raised. How would you present that to a board that expected progress?
The same few named people handled the year's events in each organisation. What does that concentration cost, and what in the year addressed it?
Nordvik Region's first seeded-fault measurement missed its target by 41 seconds. What should follow from a narrow miss: a new target, a change to the observer or a re-test?

Written exercise

Exercise · 30 minutes

A monthly review of the loop

Using the ledger of your own organisation, or the extract of the year for one of the two examples, run the monthly review as the practical guide sets it out. Read the resilience register first and list each claim by expiry date and state, scheduling every claim that expires in the next period. Then read the autonomy budget per class, the observer's seeded-fault results, the stop drill's age and time, open actions by state and age, and any provider notices received. For each item that needs a decision, write the decision, the owner and the date. Note which quarterly exercise is due: a dark day, a seeded fault or a stop drill.

Deliverable: Minutes of a one-hour review: the register by state and expiry, five to eight decisions with owners and dates, and the next quarterly exercise scheduled.

Your work

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

What happened to the degrees of delegation of Hansa Mutual's IT-operations agent between month 1 and month 12?
Show the answer
B. No level rose; restart stayed at Level 3, rollback at Level 2 and failover at Level 1
The table of delegation shows every class unchanged. The chapter counts this as a result: the three kinds of evidence a raise needs were assembled for the first time and were not satisfied together.
How did the re-tests of Nordvik Region's portal failover go in 2029?
Show the answer
D. The first failed on 2029-04-10 and the second passed on 2029-06-05
RST-NR-2029-002 failed again in April and RST-NR-2029-003 passed in June, both with the provider's participation. The Region ended the year with a verified portal failover it had been unable to claim for 20 months.
What did the review of Hansa Mutual's game day of 2028-10-24 find?
Show the answer
A. The agent verified its own restart by reading the health endpoint under the identity that performed it
The seeded silent failure kept the health endpoint reporting ready, and the agent verified its restart by reading that endpoint under its own identity. OBS-HM-0001 then made the independent probe the condition for keeping restart at Level 3.