Components & job cards

SUPERINTENDENT The core of daily PMS work.

The component card

Each component shows:

• Name — UCS name in ALL CAPS (truncated to one line, hover for full name — v2.29.4)
• Code — UCS code from the active Master
• Maker / Model / Serial number / Location / Install date
• Drawings — drawing_refs JSON array of registry codes (e.g. H-1, H-19)
• Source documents — every doc that contributed evidence
• Job cards — scheduled / completed jobs

DM badge (v2.26)

A blue DM badge appears on populated components without a backing source document. The "proof-bearing" fields (maker, model, serial_number, location, install_date) blink in orange when missing. You can:

• Attach a source document from the kebab menu — the doc contents prevail and the component flips to draft for re-approval
• Edit the field manually — this writes to field_overrides_log with provenance_quality='manual_override'

Adding a component

1. Components → kebab menu → New component
2. Pick the UCS code from the active Master (you cannot type a code; you must pick)
3. Fill name (ALL CAPS), maker, model
4. The system creates it as a draft
5. Submit for approval

Job cards

Job cards are the per-component scheduled tasks. They reference a component by component_id and have:

• Title — task name
• Frequency — running hours, calendar interval, or both
• Priority — critical / non-critical
• Last done / Next due — auto-computed from frequency

Job-card creation goes through the same draft → approve flow.

Auto-image (v2.29.4)

Each component card lazy-generates an AI image based on (name + maker + model + description) and persists it to components.image_url. So distinct components no longer share a generic illustration. The endpoint is /api/components/:id/auto-image; budget-guarded (429 on overlap or daily cap).