Data Schemas

Machine-readable JSON contracts for plant issues, lab results, notifications, observations, and handovers.

4 pages

• Agent Triage Handoff Schema

  Defines the structured, advisory output an AI agent produces after running Plant Issue Intake & Triage — capturing safety/authority flags, domain routing, retrieval targets, missing data, and a non-authorizing summary.

  An output/handoff contract, not an action plan. After triage normalizes a messy report, this schema standardizes what the agent hands off: a neutral issue summary, intake completeness, a safety routing status (never a clearance), domain routing flags, the recommended next route, retrieval targets, missing-data questions, a non-authorizing advisory summary, explicit authority limits, an escalation flag, the human owner of the decision, and a required not-authorization statement. It makes agent outputs consistent without authorizing any action.

  Category: operations · Users: ai-agent, process-engineer, control-room-operator, production-supervisor, qc-lab, reliability-engineer · Updated: 2026-06-27

• Plant Issue Intake Schema

  Canonical structure for capturing a reported plant problem an agent can route and reason about.

  Normalizes a reported plant issue into typed fields (area, equipment, symptom, severity, time, available data, reporter) so an AI agent can triage and request the right follow-up. Capture only — the schema authorizes no action, and a safetyRelevant flag forces routing to human authority.

  Category: operations · Users: ai-agent, process-engineer, operator, reliability · Updated: 2026-06-25

• Safety Observation Schema

  Define a structured record for observed safety-relevant conditions, near-miss notes, housekeeping/access/guarding/dust/traffic/energy-isolation concerns, and routing status — observational and advisory only, authorizing no safety decision or action.

  A recordkeeping-and-routing contract, not an action plan. It standardizes how an observed safety-relevant condition is captured (who saw it and when, area and location, observation type, a neutral summary, supporting evidence) and where it is routed (a routing status that is never a clearance, an immediate routing destination, follow-up owner). It records and routes; it never authorizes corrective action, field work, operation, shutdown, restart, LOTO decisions, safety clearance, environmental/compliance conclusions, or legal determinations, and it carries no numeric criteria (qualitative observations only — never exposure limits, thresholds, or alarm values).

  Category: operations · Users: ai-agent, control-room-operator, production-supervisor, safety-coordinator, reliability-engineer, maintenance · Updated: 2026-06-27

• Shift Handover Schema

  Defines the structured record one shift hands forward to the next — qualitative equipment status, open issues, work in progress, watch items, and what is pending for authorized personnel — without authorizing any action.

  A capture-and-carry-forward contract, not an action plan. It standardizes what an outgoing shift records for the incoming shift: who prepared it and when, the areas in scope, qualitative equipment status, open issues with a carry-forward status, work in progress, watch items, safety/environmental notes routed to authority, and the decisions left pending for authorized personnel. It records status and routes what is pending; it never instructs anyone to operate, adjust, release, or do field work, and it carries no numeric criteria (status words only — e.g. 'running', 'down for maintenance', 'watch', never temperatures, rates, or setpoints).

  Category: operations · Users: ai-agent, control-room-operator, production-supervisor, process-engineer, reliability-engineer, qc-lab · Updated: 2026-06-27