Deployment Runbook

Daily health checks, restart procedures, maintenance schedule, troubleshooting quick reference, and escalation contacts for IT administrators.

This runbook is for IT administrators and shift supervisors responsible for the Capped AI appliance day-to-day. Keep it accessible on-site. For operator-facing guidance, see the Operator Training Guide.

Daily health check

Run these checks at the start of each day shift before operators begin handovers.

CheckHow to verifyExpected result
Appliance reachablePing appliance IP from plant networkResponse <1ms
Capped AI web UI loadsOpen https://<appliance-ip> in browserLogin screen renders
OPC-UA historian feedAdmin dashboard → Integrations → StatusGreen — last data <60s ago
GPU inference serviceAdmin dashboard → System → InferencevLLM running, GPU utilization shown
Disk spaceAdmin dashboard → System → Storage>20% free on data volume
WORM log integrityAdmin dashboard → Audit → Log integrityLast check: Passed

Starting a handover session (operator-initiated)

This is handled by operators on their tablets. See the Operator Training Guide. IT staff do not need to intervene unless the system is unavailable.

Appliance restart procedure

Only restart the appliance if directed by Capped AI support or during a scheduled maintenance window. In-progress handovers will be lost if not signed before restart.

1
Notify shift supervisor
Inform the shift supervisor that Capped AI will be unavailable for approximately 5 minutes. Operators should complete and sign any in-progress handovers before restart.
2
Initiate restart via admin dashboard
Log in to the Capped AI admin dashboard → System → Maintenance → Restart Appliance. Confirm the restart. Do not power-cycle the hardware directly unless the software restart fails.
3
Wait for services to come up
The appliance takes approximately 3–5 minutes to restart all services (PostgreSQL, vLLM, OPC-UA bridge, web UI). Monitor the System → Services page until all services show green.
4
Verify OPC-UA reconnect
After restart, confirm the OPC-UA historian feed reconnects automatically (Admin dashboard → Integrations). If it does not reconnect within 2 minutes, check the troubleshooting section below.

Scheduled maintenance windows

FrequencyTaskDurationResponsible
Weekly (Sat 02:00–04:00)Software update check (auto-applied if approved)Up to 30 minCapped AI Ops Cloud (auto)
MonthlyDisk usage audit — archive old handovers if >80% full1 hourIT admin
MonthlyWORM log export to encrypted USB backup30 minIT admin
QuarterlyHardware visual inspection (cables, LEDs, fan noise)30 minIT admin
AnnuallyFull appliance health report sent to Capped AI support1 hourIT admin + Capped AI

Software update procedure

Capped AI Ops Cloud notifies your IT admin contact via email when an update is available. Updates include release notes and a SHA-256 hash for verification.

  • Log in to Admin dashboard → System → Updates
  • Review the release notes and confirm the update window with the shift supervisor
  • Click Approve and schedule — the appliance will apply the update during the next configured maintenance window (default: 02:00 local time)
  • After the update, verify all services are green and run the daily health check
  • To roll back: Admin dashboard → System → Updates → Rollback (available for 48 hours after each update)

Troubleshooting quick reference

Handover generation fails or times out

  • Check GPU inference: Admin dashboard → System → Inference. If vLLM is stopped, click Restart Inference Service.
  • Check OPC-UA historian feed. If disconnected, see OPC-UA reconnect procedure below.
  • If GPU temperature exceeds 85°C, check physical ventilation around the 1U appliance. Ensure 1U of clearance above and below in the rack.
  • If neither resolves the issue, contact Capped AI support with the request ID shown in the error message.

OPC-UA historian feed disconnected

  • Admin dashboard → Integrations → Historian → Reconnect. This retries the OPC-UA session without a full restart.
  • If reconnect fails, verify firewall rule: TCP 4840 from Capped AI appliance IP to DCS historian IP must be open.
  • Verify DCS historian service is running (contact your DCS engineer).
  • If historian credentials have changed (certificate rotation), update them in Admin dashboard → Integrations → Edit credentials.

Operator cannot log in to Capped AI

  • Verify the operator tablet can reach the appliance IP (ping test).
  • Check the HTTPS certificate: browsers will show a certificate warning if the self-signed cert has expired. Renew via Admin dashboard → System → TLS Certificate → Renew.
  • Reset the operator PIN via Admin dashboard → Users → select operator → Reset PIN.

Disk space below 20%

  • Admin dashboard → System → Storage → Archive handovers. Select handovers older than 90 days to export to encrypted USB and remove from primary storage.
  • The WORM log is append-only and cannot be trimmed. Archiving moves handovers to a signed export file; the WORM log entry remains immutable.
  • Contact Capped AI support if you need a storage expansion kit (additional NVMe drive).

Appliance does not respond (full outage)

  • Check physical power LEDs on the front panel. Both PSUs should show green.
  • Access the IPMI management interface from the IT management network to view hardware status without logging in to the OS.
  • If hardware fault is confirmed (GPU, disk, or PSU failure), call Capped AI hardware support immediately. Do not attempt to swap components without Capped AI guidance.
  • During appliance downtime, operators revert to manual paper-based handovers. Handover data is safe on the RAID-1 mirror.

Escalation contacts

SeverityCriteriaContact
P1 — Production downAppliance fully unavailable during active shiftCapped AI on-call: +1 (305) 000-0000 (24/7)
P2 — DegradedHandovers generating but slow (>60s), or OPC-UA data stalehello@capped.ai — response <2h
P3 — MinorUI glitch, single operator login issue, non-urgent questionshello@capped.ai — response next business day
Hardware faultGPU/disk/PSU failure indicated by IPMI or front-panel LEDCapped AI hardware support: hardware@capped.ai

Backup and recovery

The appliance maintains a RAID-1 mirror of the data volume. In the event of a single disk failure, the system continues operating on the surviving disk. Capped AI ships a replacement NVMe drive within 5 business days (Standard) or 48 hours (Enterprise).

For off-site backups, export the encrypted handover archive monthly via Admin dashboard → System → Export. The export is AES-256 encrypted and signed with the plant manager's key. Store on an encrypted USB in your plant safe.