# The worksheet — Slaughter

The worksheet: for each activity, what an outage of it costs over time, how long it can be down, what has to be back and by when, and the words each of those rests on.

## CO₂ group stunning of pigs

| Horizon | financial | customer-delivery | legal-regulatory | reputation | animal-welfare-food-safety | people-safety | environment |

| --- | --- | --- | --- | --- | --- | --- | --- |

| 0–4 h | 2 | 1 | 1 | 1 | 2 | 1 | 1 |

| 8 h | 3 | 3 | 2 | 2 | 4 | 1 | 2 |

| 24 h | 4 | 4 | 3 | 3 | 5 | 2 | 3 |

| 48 h | 4 | 4 | 3 | 3 | 5 | 2 | 3 |

| 72 h | 5 | 5 | 4 | 4 | 5 | 2 | 4 |

| 1 week | 5 | 5 | 4 | 4 | 5 | 3 | 4 |

CO₂ group stunning of pigs depends on AN-SCHLACHT-01, UV-CO2-01, UV-CO2-01, UV-STROM-01, KA-01 and LF-ABP-01, by the ids your dependency register holds for them.

“MTPD anchor **8 h** (AW — lairage feeding threshold reached by earliest arrivals).” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“- **A1 stunning** — CO₂ recovery 8 h against an 8 h MTPD; no compliant fallback at line speed.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“Not for stunning itself. Physical.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

financial — “| Fin | 2 | 3 | 4 | 4 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

customer-delivery — “| Cust | 1 | 3 | 4 | 4 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

legal-regulatory — “| Legal | 1 | 2 | 3 | 3 | 4 | 4 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

reputation — “| Rep | 1 | 2 | 3 | 3 | 4 | 4 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

animal-welfare-food-safety — “| AW | 2 | **4** | 5 | 5 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

people-safety — “| Ppl | 1 | 1 | 2 | 2 | 2 | 3 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

environment — “| Env | 1 | 2 | 3 | 3 | 4 | 4 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

Your interview puts the longest CO₂ group stunning of pigs can be down at 8 h, and the grid was read beside it rather than instead of it.

Your grid for CO₂ group stunning of pigs first reaches the level your method calls intolerable under animal-welfare-food-safety, and it reaches it at 8 h, so the longest CO₂ group stunning of pigs can be down before that becomes unacceptable stands at 8 h.

No data set is named for CO₂ group stunning of pigs in this BIA, so what stands below stands for the activity as a whole rather than for one set of its data.

For CO₂ group stunning of pigs: the recovery target is < 8 h, and the recovery point is n/a (physical).

The minimum acceptable service for CO₂ group stunning of pigs is not established.

The minimum resources over time for CO₂ group stunning of pigs were not established, so this document names none rather than one nobody wrote down.

## Carcass chilling directly on the line

| Horizon | financial | customer-delivery | legal-regulatory | reputation | animal-welfare-food-safety | people-safety | environment |

| --- | --- | --- | --- | --- | --- | --- | --- |

| 0–4 h | 3 | 2 | 3 | 2 | 4 | 1 | 1 |

| 8 h | 4 | 3 | 4 | 3 | 5 | 1 | 2 |

| 24 h | 4 | 4 | 4 | 3 | 5 | 2 | 3 |

| 48 h | 5 | 4 | 4 | 4 | 5 | 2 | 3 |

| 72 h | 5 | 5 | 5 | 4 | 5 | 2 | 4 |

| 1 week | 5 | 5 | 5 | 4 | 5 | 3 | 4 |

Carcass chilling directly on the line depends on KA-01, KA-01, UV-STROM-01 and LF-SPED-01, by the ids your dependency register holds for them.

“MTPD anchor **0–4 h** (AW — chilling curve is continuous; no retro-chilling).” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“It goes in as a recovery gap, acknowledged, handed to solution design.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“Twenty-four hours at most — the batch and traceability level. But the exact figure is
QA's and IT's, not ours.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

financial — “| Fin | 3 | 4 | 4 | 5 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

customer-delivery — “| Cust | 2 | 3 | 4 | 4 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

legal-regulatory — “| Legal | 3 | 4 | 4 | 4 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

reputation — “| Rep | 2 | 3 | 3 | 4 | 4 | 4 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

animal-welfare-food-safety — “| AW | **4** | 5 | 5 | 5 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

people-safety — “| Ppl | 1 | 1 | 2 | 2 | 2 | 3 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

environment — “| Env | 1 | 2 | 3 | 3 | 4 | 4 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

Your interview puts the longest Carcass chilling directly on the line can be down at 0–4 h, and the grid was read beside it rather than instead of it.

Your grid for Carcass chilling directly on the line first reaches the level your method calls intolerable under animal-welfare-food-safety, and it reaches it at 0–4 h, so the longest Carcass chilling directly on the line can be down before that becomes unacceptable stands at 0–4 h.

No data set is named for Carcass chilling directly on the line in this BIA, so what stands below stands for the activity as a whole rather than for one set of its data.

For Carcass chilling directly on the line: the recovery target is < 4 h, and the recovery point is 24 h (batch/traceability).

The minimum acceptable service for Carcass chilling directly on the line is not established.

The minimum resources over time for Carcass chilling directly on the line were not established, so this document names none rather than one nobody wrote down.

## Ongoing removal of Category 3 material

| Horizon | financial | customer-delivery | legal-regulatory | reputation | animal-welfare-food-safety | people-safety | environment |

| --- | --- | --- | --- | --- | --- | --- | --- |

| 0–4 h | 1 | 1 | 1 | 1 | 1 | 1 | 1 |

| 8 h | 2 | 2 | 2 | 1 | 2 | 1 | 3 |

| 24 h | 4 | 3 | 3 | 2 | 3 | 2 | 4 |

| 48 h | 4 | 4 | 4 | 3 | 4 | 2 | 5 |

| 72 h | 5 | 4 | 4 | 4 | 4 | 3 | 5 |

| 1 week | 5 | 5 | 5 | 4 | 5 | 3 | 5 |

Ongoing removal of Category 3 material depends on LF-ABP-01, LF-ABP-01 and LF-ABP-01, by the ids your dependency register holds for them.

“MTPD anchor **24 h** (Env — Category 3 backlog caps production). Rating holds for normal weeks;
see conflict F-2 on peak season.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“Category 3: MTPD
twenty-four, ABP recovery twenty-four, and the SLA's replacement collection also twenty-four.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“RPO
twenty-four hours, batch and traceability, because the commercial document per collection is the
traceability record.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

financial — “| Fin | 1 | 2 | 4 | 4 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

customer-delivery — “| Cust | 1 | 2 | 3 | 4 | 4 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

legal-regulatory — “| Legal | 1 | 2 | 3 | 4 | 4 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

reputation — “| Rep | 1 | 1 | 2 | 3 | 4 | 4 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

animal-welfare-food-safety — “| AW | 1 | 2 | 3 | 4 | 4 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

people-safety — “| Ppl | 1 | 1 | 2 | 2 | 3 | 3 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

environment — “| Env | 1 | 3 | **4** | 5 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

Your interview puts the longest Ongoing removal of Category 3 material can be down at 24 h, and the grid was read beside it rather than instead of it.

Your grid for Ongoing removal of Category 3 material first reaches the level your method calls intolerable under financial and environment, and it reaches it at 24 h, so the longest Ongoing removal of Category 3 material can be down before that becomes unacceptable stands at 24 h.

No data set is named for Ongoing removal of Category 3 material in this BIA, so what stands below stands for the activity as a whole rather than for one set of its data.

For Ongoing removal of Category 3 material: the recovery target is < 24 h, and the recovery point is 24 h (batch/traceability).

The minimum acceptable service for Ongoing removal of Category 3 material is not established.

The minimum resources over time for Ongoing removal of Category 3 material were not established, so this document names none rather than one nobody wrote down.

## Scalding 58–62 °C before dehairing

| Horizon | financial | customer-delivery | legal-regulatory | reputation | animal-welfare-food-safety | people-safety | environment |

| --- | --- | --- | --- | --- | --- | --- | --- |

| 0–4 h | 2 | 1 | 1 | 1 | 2 | 1 | 1 |

| 8 h | 3 | 3 | 2 | 2 | 4 | 2 | 1 |

| 24 h | 4 | 4 | 4 | 3 | 5 | 2 | 2 |

| 48 h | 4 | 4 | 4 | 3 | 5 | 3 | 3 |

| 72 h | 5 | 5 | 4 | 4 | 5 | 3 | 3 |

| 1 week | 5 | 5 | 5 | 4 | 5 | 3 | 4 |

Scalding 58–62 °C before dehairing depends on UV-DAMPF-01, AN-SCHLACHT-01, UV-WASSER-01, UV-DAMPF-01 and UV-STROM-01, by the ids your dependency register holds for them.

“MTPD anchor **8 h** (AW — line stop reaches the same lairage clock).” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“- **A4 scalding** — 8 h recovery against an 8 h MTPD; CIP capability on a single boiler unproven.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“RPO twenty-four hours then, batch and traceability, same caveat — QA confirms.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

financial — “| Fin | 2 | 3 | 4 | 4 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

customer-delivery — “| Cust | 1 | 3 | 4 | 4 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

legal-regulatory — “| Legal | 1 | 2 | 4 | 4 | 4 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

reputation — “| Rep | 1 | 2 | 3 | 3 | 4 | 4 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

animal-welfare-food-safety — “| AW | 2 | **4** | 5 | 5 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

people-safety — “| Ppl | 1 | 2 | 2 | 3 | 3 | 3 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

environment — “| Env | 1 | 1 | 2 | 3 | 3 | 4 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

Your interview puts the longest Scalding 58–62 °C before dehairing can be down at 8 h, and the grid was read beside it rather than instead of it.

Your grid for Scalding 58–62 °C before dehairing first reaches the level your method calls intolerable under animal-welfare-food-safety, and it reaches it at 8 h, so the longest Scalding 58–62 °C before dehairing can be down before that becomes unacceptable stands at 8 h.

No data set is named for Scalding 58–62 °C before dehairing in this BIA, so what stands below stands for the activity as a whole rather than for one set of its data.

For Scalding 58–62 °C before dehairing: the recovery target is < 8 h, and the recovery point is 24 h (batch/traceability).

The minimum acceptable service for Scalding 58–62 °C before dehairing is not established.

The minimum resources over time for Scalding 58–62 °C before dehairing were not established, so this document names none rather than one nobody wrote down.

## Statutory carcass washing and knife sterilisation

| Horizon | financial | customer-delivery | legal-regulatory | reputation | animal-welfare-food-safety | people-safety | environment |

| --- | --- | --- | --- | --- | --- | --- | --- |

| 0–4 h | 2 | 1 | 3 | 1 | 2 | 2 | 1 |

| 8 h | 3 | 3 | 3 | 2 | 4 | 2 | 1 |

| 24 h | 4 | 4 | 4 | 3 | 5 | 3 | 2 |

| 48 h | 4 | 4 | 4 | 3 | 5 | 3 | 2 |

| 72 h | 5 | 5 | 5 | 4 | 5 | 3 | 3 |

| 1 week | 5 | 5 | 5 | 4 | 5 | 4 | 3 |

Statutory carcass washing and knife sterilisation depends on UV-WASSER-01 and UV-DAMPF-01, by the ids your dependency register holds for them.

“MTPD anchor **8 h** (AW — line stop reaches the lairage clock).” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“| A5 | Washing + knife sterilisation | UV-WASSER-01 (+ UV-DAMPF-01, unlisted) | 8 h | < 8 h (owner: 2 h) | 0 h | **Yes** |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“n/a (physical); water-quality records 24 h” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

financial — “| Fin | 2 | 3 | 4 | 4 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

customer-delivery — “| Cust | 1 | 3 | 4 | 4 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

legal-regulatory — “| Legal | 3 | 3 | 4 | 4 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

reputation — “| Rep | 1 | 2 | 3 | 3 | 4 | 4 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

animal-welfare-food-safety — “| AW | 2 | **4** | 5 | 5 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

people-safety — “| Ppl | 2 | 2 | 3 | 3 | 3 | 4 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

environment — “| Env | 1 | 1 | 2 | 2 | 3 | 3 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

Your interview puts the longest Statutory carcass washing and knife sterilisation can be down at 8 h, and the grid was read beside it rather than instead of it.

Your grid for Statutory carcass washing and knife sterilisation first reaches the level your method calls intolerable under animal-welfare-food-safety, and it reaches it at 8 h, so the longest Statutory carcass washing and knife sterilisation can be down before that becomes unacceptable stands at 8 h.

No data set is named for Statutory carcass washing and knife sterilisation in this BIA, so what stands below stands for the activity as a whole rather than for one set of its data.

For Statutory carcass washing and knife sterilisation: the recovery target is < 8 h, and the recovery point is n/a (physical).

The minimum acceptable service for Statutory carcass washing and knife sterilisation is not established.

The minimum resources over time for Statutory carcass washing and knife sterilisation were not established, so this document names none rather than one nobody wrote down.

## Wastewater arising from slaughter/scalding

| Horizon | financial | customer-delivery | legal-regulatory | reputation | animal-welfare-food-safety | people-safety | environment |

| --- | --- | --- | --- | --- | --- | --- | --- |

| 0–4 h | 1 | 1 | 2 | 1 | 1 | 1 | 2 |

| 8 h | 2 | 1 | 3 | 2 | 2 | 1 | 3 |

| 24 h | 3 | 2 | 4 | 3 | 2 | 2 | 4 |

| 48 h | 4 | 3 | 4 | 3 | 3 | 2 | 5 |

| 72 h | 4 | 4 | 5 | 4 | 3 | 2 | 5 |

| 1 week | 5 | 4 | 5 | 4 | 4 | 3 | 5 |

Wastewater arising from slaughter/scalding depends on UV-ABWASSER-01, UV-ABWASSER-01 and AN-SCHLACHT-01, by the ids your dependency register holds for them.

“MTPD anchor **24 h** (Env/Legal — discharge limit exceedance under UW-2022-14 with authority
notification).” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“- **A6 wastewater** — 24 h recovery against a 24 h MTPD; no parallel treatment line.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“Discharge monitoring data. Templin's, not mine — I'd say twenty-four hours but he
owns the answer.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

financial — “| Fin | 1 | 2 | 3 | 4 | 4 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

customer-delivery — “| Cust | 1 | 1 | 2 | 3 | 4 | 4 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

legal-regulatory — “| Legal | 2 | 3 | **4** | 4 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

reputation — “| Rep | 1 | 2 | 3 | 3 | 4 | 4 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

animal-welfare-food-safety — “| AW | 1 | 2 | 2 | 3 | 3 | 4 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

people-safety — “| Ppl | 1 | 1 | 2 | 2 | 2 | 3 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

environment — “| Env | 2 | 3 | **4** | 5 | 5 | 5 |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

Your interview puts the longest Wastewater arising from slaughter/scalding can be down at 24 h, and the grid was read beside it rather than instead of it.

Your grid for Wastewater arising from slaughter/scalding first reaches the level your method calls intolerable under legal-regulatory and environment, and it reaches it at 24 h, so the longest Wastewater arising from slaughter/scalding can be down before that becomes unacceptable stands at 24 h.

No data set is named for Wastewater arising from slaughter/scalding in this BIA, so what stands below stands for the activity as a whole rather than for one set of its data.

For Wastewater arising from slaughter/scalding: the recovery target is < 24 h, and the recovery point is 24 h (batch/traceability).

The minimum acceptable service for Wastewater arising from slaughter/scalding is not established.

The minimum resources over time for Wastewater arising from slaughter/scalding were not established, so this document names none rather than one nobody wrote down.

## What is still open

Human decisions: CO₂ reserve: three incompatible figures with different or unknown demand assumptions — settled by the manager: Approximately eight hours before stunning stops, reported from the register consumer entry.

Human decisions: Normal versus peak Category 3 container buffer — settled by the manager: Less than twelve hours at peak throughput, requiring special collections.

Human decisions: Department Slaughter MTPD changes from 24 h to 0–4 h because chilling is scored separately — settled by the manager: The activity-based department MIN is 0–4 h, driven by A2.

Human decisions: Original eight-hour line recovery versus the revised four-hour stunning target — settled by the manager: Stunning should recover inside four hours.

Human decisions: One steam boiler without backup versus two boilers configured 1+1 — settled by the manager: The steam dependency has one gas boiler and no second boiler.

Human decisions: Single-compressor switchover described as minutes versus measured recovery and product-temperature excursion — settled by the manager: The May event took four hours twenty-six to stabilise and affected stock temperature.

Human decisions: Temperature-evidence RPO of 24 h versus effectively no tolerable loss — settled by the manager: Effectively no loss is tolerable for continuous temperature evidence; nightly backup is insufficient.

Human decisions: Backup-renderer action described as unowned versus later named ownership correction — settled by the manager: The live register names Dr Katrin Sauer as asset owner and second-source owner.

Human decisions: Spoken Legal lag versus the explicit Legal scoring row — settled by the manager: Legal scores are 2, 3, 4, 4, 5, 5, matching Environment through 24 h.

Human decisions: Recovery inside eight hours assessed from water alone versus the newly identified eight-hour steam dependency — settled by the manager: Steam recovery is eight hours, and the sterilisers also depend on that asset.

Human decisions: Named scalding range begins at 58 °C, but the stated hygienic lower limit is 60 °C — settled by the manager: Below 60 °C dehairing is not hygienic.