R&D requests

+ New R&D request

Active requests

Overdue deadline · deadline passed, not confirmed

Stuck (3+ trials) · not converging

Confirmed this month · incl. already promoted to BOM

R&D KPI · last 90 days

Avg days in development 18 Avg days awaiting feedback 9 customer clock Avg trials to confirm 3.2 Confirm rate 71%

Owner	Confirmed	Avg dev days	Trials→confirm	Downstream SO
Siti Aminah	5	16	2.8	RM 186,400
Lee Wei Ming	3	21	3.7	RM 94,200 · 1 n/a

12 requests · latest 10 shown

Request #	Customer	Product	Raw mats	Trial #	Design (parallel)	Deadline (the only priority)	Status	Last update	PIC

Project Gaia — static mockup in Filament v3 idiom. No backend. Snapshot 2026-04-12. Continuity: RND-2026-00013 / 00007 / 00009 tie to quotes.html (Q-2026-034 / 033 / 031) and formulations F-0013 / F-0010 / F-0007; RND-2026-00011 opens the worked-example detail screen.

R&D requests — field manifest

Field	Filament component	Type	Source	FK target
Request #	TextColumn (series RND-{yyyy}-{seq,5})	string	stored: rnd_requests.code	—
Customer	TextColumn::url() → customer card	FK	stored: rnd_requests.customer_id — Sales creates the request from the customer conversation	customers.id
Product	TextColumn	string + enum	stored: product_name, product_type (Sachet / Capsule / Gummy / Drink / Tea)	—
Raw mats	TextColumn badge	enum	stored: raw_material_status — Existing (all in item master) / Requesting (waiting supplier samples)	—
Trial #	TextColumn (derived)	int	derived: max(progress_log.trial_no) — auto-increments on each log entry of type Trial. Green ✓ when Confirmed, amber at 3–4, red at 5+	rnd_progress_log
Design	TextColumn dot + label (mini-badge)	enum	stored: design_track — design_status ((none) / Brief sent / Draft vN / Approved) + designer_user_id. Parallel side-track advanced by the designer concurrently — NOT a request status, never blocks the R&D flow	users.id
Deadline	TextColumn date + days chip	date	stored: rnd_requests.deadline — the ONLY priority signal (founder decision: no priority field). Green ≥ 14d, amber 1–13d, red OVERDUE	—
Status	TextColumn badge + Advance-stage Action	enum	enum simplified (founder decision): Requested → In development → Sample sent → Confirmed. Sample feedback FAIL loops back to In development (trial # increments). Cancelled = rejected / withdrawn — terminal, any point. Design is a parallel side-track (not a status); costing is a section within development (not a stage)	—
Last update	TextColumn (derived)	relation	derived: latest rnd_progress_log entry (text + date) — status changes are auto-logged, so this never goes stale	rnd_progress_log
PIC	SelectColumn → users	FK	stored: pic_user_id — R&D lead assigns; designer is a separate field on the detail	users.id

Tabs & KPI queries

Tabs = Filament table tabs on status with live count badges (All / Requested / In development / Sample sent / Confirmed / Cancelled).
Active requests = status ∉ {BOM created, Cancelled}.
Overdue deadline = deadline < today AND status ∉ {Confirmed, BOM created, Cancelled}.
Stuck = trial_count ≥ 3 AND not Confirmed — flags formulations bouncing without convergence so the R&D lead intervenes.
Confirmed this month = status_history transitions into Confirmed in the current month — includes requests already promoted to BOM, hence 5 > the Confirmed tab's 2.

R&D KPI strip (last 90 days) — formulas

Two clocks, both from status_history (derived from auto-logged Status entries): internal clock = Σ of In-development durations per request (loops after a feedback FAIL included); feedback clock = Σ of Sample-sent durations — the customer clock, tracked separately so waiting on the customer is never counted against R&D.
Avg days in development = mean(internal clock) over requests active/closed in the window.
Avg days awaiting feedback = mean(feedback clock) — customer clock, reported separately (not R&D's fault).
Avg trials to confirm = mean(max trial_no) over requests confirmed in the window.
Confirm rate = Confirmed ÷ (Confirmed + Cancelled) among requests closed in the window.
Downstream SO value = request → BOM (bom.rnd_request_id) → first SO on that product for the customer; shown where known, "n/a" while no SO exists yet. Per-owner rows group by pic_user_id.

Engine notes

Customer-request-driven OEM pipeline: Sales/CRM creates the request (Requested, customer-tagged); everything R&D does — sourcing, trials, costing — happens inside In development as progress-log entries (logged, not stock-tracked); Sample sent awaits the customer; Confirmed unlocks Create BOM.
Design runs as a parallel side-track (Brief sent → Draft vN → Approved) advanced by the designer — it never blocks the R&D status.
Deadline is the whole prioritisation model — the list default-sorts by deadline ascending.