Quality board · Q1 review
Pareto, FPY trend, open 8Ds and the scorecard the QA team meets around.
Boards are the self-serve middle ground between a fixed dashboard and a daily teamboard — a manager picks a column count, drags in the widgets they care about, configures each one, and saves. It's live the second you save it. No deploy, no ticket, no engineering.
Bulk Boards are the self-serve middle ground between a fixed dashboard and a daily teamboard. A manager picks a column count from one to six, drags in the widgets they care about from a catalog of 21 across five modules, configures each one, and saves. It's live the second you save it — no deploy, no ticket, no engineering.
A board is a column-based canvas. Flip on edit mode, drag widgets between columns, drop one in from the catalog, configure it — changes save the moment you drop. Try it: turn on Edit and move the tiles around.
The picker is a searchable wall of the boards your site has made. Each tile renders the board's real widget layout as a preview, and a stable colour and BRD- code derived from the board itself — so a board always looks like itself. Search matches the name, the code or the description.
Pareto, FPY trend, open 8Ds and the scorecard the QA team meets around.
OEE scorecard, live downtime feed and the asset leaderboard for the shift lead.
Risk matrix, open incidents and the review calendar for the EHS lead.
OEE trend, reasons pareto and the KPI charts the ops manager reviews on Mondays.
Task table, downtime feed and a pinned PDF of the standard work for the line.
Quality scorecard, OEE scorecard and a note board for the 7am walk-through.
Boards draw from a shared widget registry — the same shelf Teamboards and the Hub pull from. Each widget is owned by the module that knows the data, so a board only stores where a widget sits and how it's configured; the numbers stay live at the source.
There's no resize grid to fight and no board-settings page to get lost in. Drop a widget into a column, drag it where it belongs, configure it on the widget itself. That's the whole model.
Pick 1 to 6 columns; drop a widget into any of them and drag to reorder. No grid maths, no resize handles to wrestle.
1–6 columnsTime window, asset, target, filter — every dial lives on the widget itself, not on a global settings screen nobody can find.
per-widget settingsNo deploy, no nightly export, no PDF. Drop a widget and it's reading live data — the data is the data.
save = liveAccess is decided per board, on top of the module permission. The rule is deliberately simple: a board with no named viewers is visible to everyone on the site; the moment you name one, it's that list plus the creator — and the creator can never lock themselves out.
Leave the viewer list empty and the board is public to every user on the entity who can see boards. The picker even labels it Public.
is_public in the list Add a viewer and the board narrows to that set plus its creator. Manage the list whenever; clear it and the board goes site-wide again.
A board owns almost no data of its own. Every widget is owned by the module that records the numbers, so a board is only ever as current as the floor underneath it — which is to say, live.
Defect pareto, FPY trend, NCR aging, quality items and the scorecard surface defect data.
Scorecard, trend, reasons and loss pareto, the asset leaderboard and the live downtime feed.
Risk matrix, risk assessments, the incident table and the review calendar pull from Safety.
The task table reads any project and status filter — and stays writeable from the board.
The KPI chart reads any metric definition, target and actual you've configured in KPIs.
The document-display widget pins a PDF or image from the file system, validated on save.
metrics · charts · tables · utility, from five modules, one shared shelf.Boards are the self-serve middle ground between a fixed dashboard and a daily teamboard: you pick a column count, drag in the widgets you care about, configure each one, and save. It goes live the moment you save it.
No. A manager builds it by picking a column count and dragging in widgets — no deploy, no ticket, no engineering. It is self-serve, end to end.
There are 21 live widgets on one shared shelf, spanning metrics, charts, tables, and utility, drawn from five modules — so a single board can mix data from across the system.
Boards save on drop: drag results persist the moment you let go. It is optimistic, with rollback if the save fails.
Access is set per board. Leave the viewer list empty and the board is public site-wide; name one person and it becomes that list plus the creator.
Shrink the count and any orphaned widgets re-home into the last column automatically, so nothing is lost when you change the layout.
We'll pick a column count, drop in the widgets your role lives by, set who can see it — and you'll have a live board, not a mock-up.