# 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 UV-CO2-01, IT-ERP-01 and AN-SCHLACHT-01, by the ids your dependency register holds for them.

“So the worst case reaches four at the eight-hour horizon. That's your MTPD anchor: eight hours for stunning, not twenty-four.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“| A1 | CO₂ group stunning | UV-CO2-01 | 8 h | < 8 h (owner: 4 h) | 8 h | **No — equal** |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“**Dohm:** RPO — any data you'd lose?

**Ahlgrim:** 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 and KA-01, by the ids your dependency register holds for them.

“So the MTPD anchor for this activity is the zero-to-four band.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“| A2 | Carcass chilling on the line | KA-01 | 0–4 h | < 4 h (owner: 2 h) | 4 h | **No — equal** |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“**Struck:** 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 from the line

| 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 from the line depends on LF-ABP-01, LF-ABP-01 and LF-ABP-01, by the ids your dependency register holds for them.

“**Dohm:** MTPD anchor twenty-four hours.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“| A3 | Category 3 removal | LF-ABP-01 | 24 h | < 24 h (owner: 12 h) | 24 h (SLA replacement collection also 24 h) | **No — equal** |” (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 from the line 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 from the line 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 from the line can be down before that becomes unacceptable stands at 24 h.

No data set is named for Ongoing removal of Category 3 material from 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 Ongoing removal of Category 3 material from the line: 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 from the line is not established.

The minimum resources over time for Ongoing removal of Category 3 material from the line 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, UV-DAMPF-01 and UV-DAMPF-01, by the ids your dependency register holds for them.

“So a second activity anchors at eight hours for the same reason.” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“| A4 | Scalding 58–62 °C | UV-DAMPF-01 | 8 h | < 8 h (owner: 4 h) | 8 h | **No — equal** |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“**Struck:** And the scalding temperature record is a CCP record. If we lose that we can't evidence the clean either.” (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.

“Proposed by nemo, confirmed by the manager in chat: Statutory no-start; animal welfare line reaches 4 at 8 h. (the model called this stated; the check could not find it in the quote)” ()

“| 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)

“Proposed by nemo, confirmed by the manager in chat: Physical activity; water-quality records retained at 24 h. (the model called this stated; the check could not find it in the quote)” ()

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 and UV-ABWASSER-01, by the ids your dependency register holds for them.

“Proposed by nemo, confirmed by the manager in chat: Behaves as a production cap, not a switch; exceedance with notification at 24 h. (the model called this stated; the check could not find it in the quote)” ()

“| A6 | Wastewater slaughter/scalding | UV-ABWASSER-01 | 24 h | < 24 h (owner: 12 h) | 24 h | **No — equal** |” (07_Interviews/26_08_20_slaughter-ahlgrim-followup-interview.md)

“**Ahlgrim:** 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: CO2 tank reserve at slaughter draw (F-1) — settled by the manager: Register redundancy field says about three slaughter days; register consumer line says roughly eight hours; asset owner to settle

Human decisions: Category 3 container buffer, normal vs peak (F-2) — settled by the manager: Under twelve hours at peak line speed, with two unrecorded special collections

Human decisions: Department MTPD: 24 h (Feb prose) vs 0–4 h (scored grid) (F-5) — settled by the manager: Grid gives 0–4 h driven by carcass chilling, with owner objection recorded

Human decisions: Dependency recovery targets equal to MTPD horizons (F-4) — settled by the manager: Method rule requires RTO strictly less than MTPD