{
  "status": "shipping",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-16",
  "slug": "failure-operation-ticket",
  "term": "Failure operation ticket",
  "aliases": [
    "FOT"
  ],
  "definition": "A failure operation ticket is a management-system record of a detected hardware problem and its handling status, rather than necessarily a unique failed component.",
  "note": "Wang et al. analyze repair and unrepaired ticket categories, excluding false alarms. A repeated symptom after closure can produce another record; closing a ticket with an action does not establish completed physical repair. [wang-dsn17] Keep ticket, component, incident and exposure counts distinct.",
  "related": [
    "failure-label",
    "rate-of-occurrence-of-failures",
    "failure-burst"
  ],
  "citations": [
    {
      "id": "wang-dsn17",
      "title": "Wang, Zhang and Xu. What Can We Learn from Four Years of Data Center Hardware Failures? DSN 2017, sections II and III-D.",
      "url": "https://netman.aiops.org/~peidan/ANM2019/9.EventPrediction/ReadingList/2017DSN_What%20Can%20We%20Learn%20from%20Four%20Years%20of%20Data%20Center%20Hardware%20Failures.pdf",
      "accessed": "2026-10-16"
    }
  ]
}