G Gaia

Switch factory

CYTO-11 — Balakong Jaya CTSB CYTO-29 CTSB CYTOWELL-54 — Taming Jaya PIC/S CTWSB CYTOCNGZ-602 — Guangzhou CTCNGZ

Only factories you are granted appear here (Filament tenant menu).

Leo Lim

leo@navi.my · Owner / Admin

Profile settings Change password

Theme

Sign out
RetailSellR&DMakeBuyStockPlanItemsGMPAdminInsights

Batch Manufacturing Records

Generate BMR from MO
Paper stays official (current NPRA direction): Gaia auto-generates the BMR from the MO — formula, weighing sheet, process steps, equipment, checks — pre-filled and printed. The floor executes on paper with wet-ink signatures; QA releases in wet ink. Gaia tracks the lifecycle, stores step photos, and archives the scanned BMR against the batch. Software convenience, zero software-validation burden.
BMRs · 2 in execution · 1 awaiting QA release
BMR # MO Product · batch Qty Generated Photos Status Scan
What Gaia pre-fills into the printed BMR — generated from the MO at release
  1. Header — product, batch no., MO, formula version, batch size, mfg & expiry dates.
  2. Weighing record — one line per recipe ingredient: material, allocated lot number, required qty; blanks for actual weighed, weighed-by, verified-by.
  3. Process steps — from the routing (mixing, filling, packing…), each with parameters and blanks for done-by / time / remarks.
  4. Equipment list — machines from the routing with cleaning-status tag to verify before start.
  5. In-process checks — weight variation, seal integrity, expiry print check (PASS default; exceptions get remarks — house rule).
  6. Yield reconciliation — theoretical vs actual with % blanks.
  7. Label specimen page — affix printed label sample.
  8. Deviation section — blank unless needed.
  9. QA release block — wet-ink signature. The scan of this page closes the record in Gaia.
Execution photos — BMR-26-031 — snapped on the floor, tagged to steps

Photos are timestamped + batch-tagged. Tick "share to client" on any photo and it appears on the client portal timeline.

Project Gaia — static mockup in Filament v3 idiom. No backend. MO/product/batch references follow the real numbering; BMR content structure per PIC/S expectations, wet-ink release per current paper-parallel direction.

BMR — field manifest

FieldFilament componentTypeSourceFK target
BMR #TextColumn (series BMR-{yy}-{seq})stringstored: bmrs.code
MO / product / batchTextColumn::url()FKstored: bmrs.mo_id; product/batch derived from MO outputmos.id
GenerationHeader action "Generate BMR from MO"PDFrenders recipe snapshot + batch allocations + routing into the 9-section template; template versioned per productrecipe snapshot
StatusBadge + workflow actionsenumGenerated → Printed → In execution → Awaiting QA release → Released & archived
PhotosRelationManager (production_updates filtered by mo)mediasame production_updates table as the client portal; step-tagged, timestampedproduction_updates
ScanFileUpload on the archive actionPDFstored: bmrs.scan_path — the wet-ink released document; archiving requires it

Engine notes

  • One BMR per MO output batch; regeneration after a recipe edit creates a new BMR version (old one voided, kept).
  • The weighing sheet pre-prints the allocated lot numbers from the MO batch picks — the floor confirms, not transcribes. Fewer transcription errors, faster QA review.
  • Released & archived requires the scanned wet-ink PDF; Gaia then links batch → BMR scan → photos → shipments, so a mock-recall pulls the full story in one query.
  • Generate is blocked for MOs with a live BMR; regeneration after a recipe edit voids the old version and issues a new BMR number.