Maintenance — Project Gaia

Corrective work order

MWO-26-035

Breakdown Not saved

Asset

Issue

Priority

Asset status

Take out of service — status Down Keep running — monitor

Down flips the Machines register status, shows a red note on the machine row, and blocks new operation bookings.

No operations scheduled on MX-02 in the next 7 days — no MOs blocked. FM (Sarah) and ENG (Faizal) are still notified.

When the asset has scheduled ops, this panel lists them and flags each Blocked on the Make schedule — see FL-02 / MWO-26-034: 2 MOs blocked.

Photo

Drop photo here or browse

MX02-oil-leak.jpg· 1.2 MB

Reported by

Reported at

Maintenance register

New program

Asset / area

+ Create new asset opens an inline form (name, category, room) — Filament createOptionForm.

Log entry

GMP register

Date

Room / asset

Type

Agent used

Start time

End time

Cleaned by

Checked by (QA/QC)

Feeds the supervisor Verify queue — QA counter-signs the clean.

Checklist

Every item defaults to PASS (CTW P21 form) — only exceptions expand a remark + corrective action.

Status

Saving flips this room's AM clean cell to a green ✓ and clears the "AM clean pending" remark on the Today board; the record lands in the supervisor Verify queue for QA counter-sign.

Room

Reading

Temperature (limit 20–25°C)

°C

↗ Raise work order

Relative humidity (limit 40–60%)

%

↗ Raise work order

Limits come from the per-factory compliance profile. Out-of-range readings auto-flag the "Temp/RH out of range" stat tile and can raise a corrective MWO. Same field set as the supervisor PM temp/RH check.

Program

Stations checked

Activity found

No activity keeps the "0 pest activity" tile green.

Any activity escalates to FM + owner.

Contractor report

Rentokil-Jul-2026.pdf· 640 KB

Trend remark

Internal monitoring defaults to NO ACTIVITY (ticking = pest found). Entries write the same registers the Print GMP registers pack (premises 10.2) reads.

Maintenance — field manifest

Field	Filament component	Type	Source	FK target
Asset / area	AssetResource (machines are assets with category=Machine)	record	stored: assets (factory_id, category, name, room, contractor_id nullable, gmp_critical bool)	factories / contractors
Program	RelationManager on Asset	record	stored: maintenance_programs (asset_id, task, frequency, owner_type internal/contractor, evidence_type)	assets.id
Next due	TextColumn::date() red overdue + dashboard widget	derived	last completed log + frequency; overdue GMP rows notify FM + QA	maintenance_logs
Evidence	FileUpload / form link on the completion action	media/form	stored: maintenance_logs (done_at, by, photos, cert_ref, result)	—
Cleaning log	Dedicated form matching the CTW P21 form	record	fields: date, equipment→asset, type Routine/Changeover/Deep, agent used, start/end, cleaned by→employee, checked by QA/QC, status Clean/Not clean, remarks	assets / users
Self-inspection	Program + child checklist (10 areas)	record	areas: raw mat storage, production, packaging, FG warehouse, QC lab, documentation & records, sanitation & hygiene, water system, pest control, calibration & maintenance; findings → CAPA	capas
Work order	MaintWorkOrderResource	record	stored: maint_work_orders (asset_id, issue, priority, status, blocks_production bool → flags affected MOs)	assets / mos
Report breakdown (slide-over)	CreateAction on MaintWorkOrderResource — Select (asset, optgrouped Machines/Facility/Vehicle), Textarea (issue), ToggleButtons (priority Critical/High/Medium/Low), Radio (take out of service / keep running), FileUpload (photo, optional), Select (reported_by), DateTimePicker (reported_at, default now)	form	writes maint_work_orders (asset_id, issue, priority, status Open, blocks_production derived from schedule, reported_by, media); sets asset status Down when out-of-service chosen	assets / users
Compliance profile	Per-factory settings page	config	stored: compliance_profiles (factory_id) → rooms (name, temp_min/max, rh_min/max), checklist templates per room type	factories.id
Daily cleaning record	Form: per-room checklist, all items default PASS	record	stored: daily_cleaning_records (room_id, shift AM/PM, items json default-pass, remarks on exceptions only, checked_by, qa_verified_by)	rooms / users
Temp/RH record	Form: AM + PM readings per room	record	stored: temp_humidity_records (room_id, time_am/pm, temp_am/pm, rh_am/pm, within_limits AUTO from profile limits)	rooms
Pest monitoring (internal)	Form: stations pre-populated, default No Activity	record	stored: pest_monitoring_logs (station_id, activity bool default false, pest_type, qty_est, photo, corrective) — any activity escalates to FM + owner	pest_stations
Pest control service (external)	Form per provider visit	record	stored: pest_service_records (provider, technician, areas treated, methods, chemicals + SDS ref, report file)	contractors
Pest control plan	Annual document + provider docs checklist	record	stored: pest_control_plans (effective/review dates, activities, provider docs: contract, licences, SDS, training, monthly reports)	contractors
Vehicle inspection	Form: weekly 10 checks / monthly +8, default OK	record	stored: vehicle_inspections (vehicle asset_id, type weekly/monthly, odometer, items default OK, remarks on exceptions); road tax / insurance / service-due dates live on the asset and roll into next-due	assets
Sanitation log	Form per sanitization event	record	stored: sanitation_logs (area/equipment, type Routine/Deep/Disinfection, agent, dilution, method Wipe/Spray/Fog, performed_by, verified_by)	rooms / assets

Engine notes

Two default philosophies, deliberately opposite: cleaning/cleanliness checklists default every item to PASS (only exceptions need remarks — house rule), pest monitoring defaults to NO ACTIVITY (ticking = pest found). Any pest activity or out-of-range reading auto-escalates to FM + owner.
Machines screen stays the production view; this register is the superset — same assets table, category filter. Completing a program writes a maintenance_log and rolls next-due forward automatically.
New program (+ Program slide-over) writes maintenance_programs (asset_id, task, frequency, owner_type internal/contractor, owner_id, evidence_type, gmp_critical bool, first_due); the row appears on the register under its category (e.g. Facility) with Last done — and Next due = first_due (2026-08-01).
Breakdown flow mirrors the reference: report → asset Out of Service → linked MOs flagged blocked → part check/PO → repair → back online.
Report breakdown writes maint_work_orders and (if Down) flips the asset status; the new MWO lands at the top of the Work orders tab and in the Records register as type Breakdown; repair completion + parts consumed land on Equipment history (cf. MWO-26-028 heater bar on FL-01).
Log entry (per-room Log button on the Today board) is one modal with a 3-segment toggle — Cleaning writes daily_cleaning_records (CTW P21: checklist default-PASS, exceptions only) and drops the row into the supervisor Verify queue for QA counter-sign; Temp/RH writes temp_humidity_records with within_limits auto-computed from the compliance profile (out-of-range reveals Raise work order → same corrective-MWO form as Report breakdown); Pest/sanitation writes pest_monitoring_logs (default NO ACTIVITY). Same temp/RH field set as the supervisor PM check.
Printed registers (programs + logs + certs per asset) = the premises & equipment file NPRA asks to see; cleaning logs keep the wet-ink QA verify per current paper-parallel direction.