Assigned to me
Everything on the board waiting on you: investigations you own, reports for you to review, reports that came back to you, and actions you own. Click a row to open it.
Triage inbox · records needing triage
New records from the ERP webhook and records held for lab / formulation response after a triage return-to-source. Click a record to open triage.
Open investigations · by SLA
Records routed to an investigation path after triage and still being worked. Once a report is prepared it moves to the sign-off queue above. Target close-out is 14 days from open. Investigations older than 14 days need escalation.
Actions Register
Countermeasures across all misblend investigations. Corrective (fix root cause) and preventive (prevent recurrence). Click a row to open the source investigation.
| WO / Ref | Type | Action | Owner | Priority | Due | Status |
|---|
Misblend Log · Full history
Finished investigations — closed and verified. Set the status filter to All statuses to search every record on the system. Click a row to open the investigation.
| Date | WO / Ref | Blend | Family | Cause | Status | CoQ | Actions |
|---|
KPI Report · Monthly RFT by category
Rolling 12-month view. RFT (Monthly) reflects that month's total and misblends. RFT (YTD) is year-to-date cumulative. RFT (R12) is a 12-month rolling window ending in the row's month. Both denominators are maintained in Admin → Monthly Blends.
Against original blends
Blends only — the historic basis, and the one the dashboard, the charts and the wall board use.
Against all blending operations
Blends plus additisations, adjustments, reblends and intermediate blends. The same misblends set against every operation that could have gone wrong, so it reads higher than the table above — not because fewer things went wrong, but because more work is counted.
Cost of Quality · by month
Cost of Quality is what a misblend actually cost — material that was wasted, external analysis, and the labour to put it right. Material that could be reused, and material added to bring a blend back into specification, are not in it. Potential is what the same misblends would have cost had nothing been reusable — the same analysis and labour, with every excess or dropped-out volume counted as lost. When that volume goes back into stock it is luck, not process; the mistake was the same size either way. Recovered is the difference. Unconfirmed is the part of the cost that rests on imported records where the register never said whether the excess was wasted or reused; it is counted at the register's own figure until somebody confirms it. Hours is the rework time by role, unpriced. Potential is not on the dashboard; it is here for the people who need the size of the mistake rather than what it happened to cost.
Cost of Quality · the records behind a month
Pick a month and every record in it is listed with what its two figures are made of. Material at risk is the dropped-out, overblended or scrapped volume at cost; Material lost is the part of it that was wasted. Cost = lost + analysis + labour; Potential = at risk + analysis + labour. Click a row to open the record.
Recurring causes (frequency)
Actionable tertiary causes — excludes Non-Accountable · click a bar to see its records
Direction of travel vs prior period
Positive = worsening (more events). Negative = improving. Signals which controls are landing and where new attention is needed. Click a bar to see its records.
Ongoing investigations
Closed in the last 7 days
Live investigations
What the shift teams should be aware of — open work orders currently under investigation.
Recent outcomes (last 7 days)
Closed investigations — root cause and what to watch out for on future blends.
Admin
Reference data. Changes are saved immediately and applied to all subsequent investigations. Changes do not affect historical records.
Numeric cause codes with their Area / Sub-area / Specific cause and the evidence guide shown in the investigation modal. Historic records keep their existing code even if renamed here.
| Code | Area | Sub-area | Specific cause | Evidence guide | Actions |
|---|
Triage workflow phases and evidence items. T1 (QA verification) is a checklist an investigator ticks off before a record can proceed. T2 (Investigation path) is direct path selection — edit those in the Investigation Paths tab. Changes here affect every future triage; historic records keep the wording that was in place at the time of their triage.
Investigation path definitions. Each path drives the walk-through steps an investigator sees when a record is routed to it. Admin only — changes here affect every future investigation, so edit carefully. Steps store a snapshot of their definition on each walk entry, so historic reports render the wording that was in place at the time of the walk (not the current wording).
Options shown in the Containment dropdown on the investigation modal.
Product family classifications used for filtering and cluster analysis.
Everybody with an account on the board, and their role.
Standard hourly cost rates used to compute the labour components of Cost of Quality. Editable to reflect current fully-loaded rates.
How fast the Wall Display Mode board moves. Longer is calmer and easier to read from a distance; shorter shows more in a given time. Changes apply the next time the board is opened, or immediately if it is already running on this screen.
For a plant display that cannot sign in: open /wall on this site instead.
It is this wall board, with no login, drawn from a snapshot published hourly between 08:00 and 18:00 — the tiles, the charts and the
ticker of open and recently closed investigations. What the ticker shows is therefore visible to anyone with the address. Set it up by following The public wall board in docs/DEPLOYMENT.md.
Monthly totals used to calculate RFT %. Populate historical months from the ERP monthly report; update each new month at month-end. Only months with a value appear in the matching KPI table — the two tables below feed the two RFT tables on the KPI tab, and a month left blank in one still counts in the other.
Original blends
Blends only. This is the historic basis, and the one every dashboard tile, chart and wall-board figure uses.
All blending operations
Blends plus additisations, adjustments, reblends and intermediate blends — every operation that could go wrong. Should never be lower than the blend count for the same month; one that is gets flagged. Leave a month blank rather than guessing: a blank month has no operations rate, whereas a guess becomes a published figure.
Improvement suggestions raised from the board. Accepting one does not put it in the repository — copy the block it produces into GitHub, and the badge only turns green once the reference actually appears in the deployed roadmap index.