Order recovery FMEA

// Trace order recovery failures, from duplicate fulfilment to a false completion message, from cause to effect and mitigation; compare ordinal risk priorities without interpreting them as probabilities.
// Synthetic worked example: all entities, schedules and measurements are illustrative.
// Every string below is EXAMPLE text from a fictional model: replace it.
// Replace assumptions and inputs before applying this model to actual work.

fmea assessment {
  title: "Illustrative Order recovery FMEA"
  system: "Order recovery FMEA"
  team: "Cross-functional review"
  revision: "Workshop example"
}

failure_mode failure_0 {
  component: "Payment callback"
  mode: "Duplicate fulfilment"
  cause: "Replay processed twice"
  effect: "Multiple parcels for one order"
  severity: 8
  occurrence: 3
  detection: 6
}

mitigation mitigation_0 {
  mode: failure_0
  action: "Enforce operation idempotency"
  owner: "Assign accountable reviewer"
  target_severity: 8
  target_occurrence: 2
  target_detection: 3
}

failure_mode failure_1 {
  component: "Reservation"
  mode: "Stock remains held"
  cause: "Cancellation does not release stock"
  effect: "Available inventory understated"
  severity: 7
  occurrence: 4
  detection: 4
}

mitigation mitigation_1 {
  mode: failure_1
  action: "Add compensating reservation release"
  owner: "Assign accountable reviewer"
  target_severity: 7
  target_occurrence: 2
  target_detection: 3
}

failure_mode failure_2 {
  component: "Refund"
  mode: "Refund omitted"
  cause: "Separate systems disagree"
  effect: "Customer remains charged after cancellation"
  severity: 6
  occurrence: 3
  detection: 5
}

mitigation mitigation_2 {
  mode: failure_2
  action: "Reconcile refund states to cancellations"
  owner: "Assign accountable reviewer"
  target_severity: 6
  target_occurrence: 2
  target_detection: 3
}

failure_mode failure_3 {
  component: "Notification"
  mode: "False completion message"
  cause: "Message sent before durable commit"
  effect: "Customer receives incorrect status"
  severity: 9
  occurrence: 2
  detection: 7
}

mitigation mitigation_3 {
  mode: failure_3
  action: "Publish notifications from committed events"
  owner: "Assign accountable reviewer"
  target_severity: 9
  target_occurrence: 2
  target_detection: 3
}

view priorities: fmea_table