Machines

Print machine logbook

Usage without extra data entry: every MO operation runs on a machine (the routing's resource). Booking time on a task writes a usage log row for that machine — utilisation, hours run and the GMP machine logbook all derive from work that's already recorded. PM & calibration dates are the only thing maintained by hand.

10 machines · avg utilisation 7d 46% · 1 calibration overdue

Code	Machine	Type	Room	Status	Running now	Util. 7d	Hours 7d	Last PM	Calibration due
									overdue

Project Gaia — static mockup in Filament v3 idiom. No backend. Machines and utilisation are illustrative; MO links are the real orders from the Katana snapshot. Location: CTSB — 11, Balakong Jaya.

Machines

New machine

Code

Short code used on routings and the schedule — unique per factory.

Name

Type

Room

Commissioned

Initial status

Running is derived from open operation bookings — never set by hand.

PM frequency

Calibration frequency

Seeds two starter programs on the Maintenance register, first due one cycle after commissioning (PM 2026-08-01, calibration 2027-01-01).

Notes

Machines — field manifest

Field	Filament component	Type	Source	FK target
Code / Machine / Type / Room	TextColumn + SelectFilter(type)	string / enum	stored: machines (factory_id, code, name, type, room)	factories.id
Status	TextColumn badge + Action "Set status"	enum Running/Idle/Maintenance/Down	derived Running from an open op booking; Idle default; Maintenance/Down set manually with note	—
Running now	TextColumn::url() → MO	relation	derived: open machine_usage_logs row (mo_operation_id)	mo_operations
Util. 7d / Hours 7d	ViewColumn (bar) / TextColumn	derived %	derived: Σ usage-log hours ÷ available hours (factory calendar) over trailing 7d	machine_usage_logs
Last PM / Calibration due	TextColumn::date(), red when overdue	dates	stored: maintenance_logs (type PM/calibration/repair, done_at, due_next, by, note)	maintenance_logs
Commissioned	DatePicker (CreateAction)	date	stored: machines.commissioned_at; seeds first PM/calibration due dates	—
Initial status	Select (CreateAction)	enum Idle/Maintenance/Down	stored on create; Running is never set by hand (derived)	—
PM / Calibration frequency	Select ×2 (CreateAction)	enum —/Monthly/Quarterly/6-monthly/Yearly	writes maintenance_programs rows (interval, next_due = commissioned + one cycle)	machines.id
Notes	Textarea (CreateAction)	text	stored: machines.notes	—

Engine notes

machine_usage_logs rows are written when a task/operation books time (start/stop or entered hours) — usage tracking costs the floor nothing extra.
Routing operations reference a machine type or a specific machine; the MO task inherits it, so schedule clashes are visible (two MOs on FL-01 at once).
GMP: this list + maintenance_logs printed = the machine register & logbook NPRA asks for; calibration overdue blocks "Running" via a policy warning (soft block v1).
Machines are per-factory (tenant-scoped) like all operational records.
CreateAction (+ Machine) stores machines (factory_id, code, name, type, room, commissioned_at, notes); the record lands in this list as Idle, util 0%, Last PM —.
Setting PM/calibration frequencies on create writes matching maintenance_programs rows, first due one cycle after commissioning (PM 2026-08-01, calibration 2027-01-01) — they surface on the Maintenance register.