# Requirements handover — Slaughter

This is a requirements handover for solution-design discussion. It is not approved: nobody has signed off a decision by writing it, and nothing in it commits anybody to anything.

It is written for whoever designs the continuity solutions next. What it hands over is the figures and the decisions behind them — how long each activity can be down, what has to be back and by when, the minimum acceptable service, the resources, what each activity depends on, and every reservation attached to an answer that was not endorsed.

It hands over those inputs and stops at them. The guidance this BIA was run under holds no step-by-step method for designing a continuity solution, so nothing below tells you how to design one.

## The continuity requirements, activity by activity

### Slaughter (stunning → dressing)

The record has Torsten Ahlgrim stating Slaughter (stunning → dressing)'s own figures, so this activity is theirs.

Your interview puts the longest Slaughter (stunning → dressing) can be down at 0–4 h, and the grid was read beside it rather than instead of it.

Your grid for Slaughter (stunning → dressing) first reaches the level your method calls intolerable under animal-welfare-food-safety, and it reaches it at 0–4 h, so the longest Slaughter (stunning → dressing) can be down before that becomes unacceptable stands at 0–4 h.

No data set is named for Slaughter (stunning → dressing) in this BIA, so what stands below stands for the activity as a whole rather than for one set of its data.

For Slaughter (stunning → dressing): the recovery target is < 4 h, and the recovery point is n/a (physical).

The minimum acceptable service for Slaughter (stunning → dressing) is not established.

The minimum resources over time for Slaughter (stunning → dressing) were not established, so this document names none rather than one nobody wrote down.

Slaughter (stunning → dressing) depends on UV-CO2-01, KA-01, AN-SCHLACHT-01, KA-01, KA-01, KA-01, LF-ABP-01, LF-ABP-01, LF-ABP-01, LF-ABP-01, UV-DAMPF-01, UV-DAMPF-01, UV-DAMPF-01, UV-WASSER-01, UV-DAMPF-01, UV-ABWASSER-01 and UV-ABWASSER-01, by the ids your dependency register holds for them.

## Referred to the risk assessment

This BIA refers nothing to the risk assessment. That is what the record holds rather than a section left out.

## What is still open, and accepted by id at the signature

OPEN-1 — Human decisions: Category 3 container buffer: one slaughter day vs under twelve hours in peak season — settled by the manager: Under twelve hours in peak season (two unrecorded special collections in summer 2026)

OPEN-2 — Human decisions: KA-01 consumer clock against slaughter/cutting: register says ≈2–4 h, measured value is 90 minutes — settled by the manager: Measured: 90 minutes of hall inertia before cutting must stop

OPEN-3 — Human decisions: CO₂ bulk tank reserve at slaughter draw: ≈1 week (owner) vs ≈3 slaughter days vs ≈8 hours (register entries) — settled by the manager: ≈ 1 week at normal draw

OPEN-4 — Human decisions: Department MTPD for Slaughter: 24 h (February, unscored) vs 0–4 h (Stage 1 scored MIN principle) — settled by the manager: Canonical MTPD 0–4 h under MIN principle, driven by A2 carcass chilling

OPEN-5 — Human decisions: SLA-2024-ABP assumes a chilled Category 3 store at ≤ +7 °C that does not exist at volume — settled by the manager: SLA assumes chilled interim storage which the site cannot provide

## What was reserved on the way here

Every card in this BIA was endorsed as it stood, so nothing was reserved.

## What the check of this BIA found

The check of this BIA found nothing to raise.

## Where this BIA stops, and what you decide after it

The BIA stops here. It says what has to be back and by when, and it chooses nothing about how: no site, no supplier, no system, no continuity plan. Which continuity solution meets these requirements, and which of the open items above anybody carries, is yours to decide after reading this and is not decided in here.