sailing Foudra MRP
Reference manual chevron_rightdashboard/index

Dashboard

The landing page. From the top: a row of counts, what needs a human (most urgent first), and graphs of how the last 13 weeks went.

Getting started

A new company starts with a checklist above the counts: the company's details, part categories, locations, parts, opening stock, suppliers and what they sell, bills of materials, and your team, in the order the data depends on. Each step ticks itself off when the data is there, so there is nothing to mark; the next step is highlighted, with a link to do it and one to how. The checklist shows to planners, admins and owners, and goes once everything is done. An owner or admin can Hide it sooner, for instance when the company makes nothing and has no use for bills of materials, and bring it back from Company settings.

Counts

Each tile is a number and a link to its list.

Tile Counts
Parts Parts that aren't archived
Stock Parts on hand at any location, and what they are worth at their standard cost. Parts with no standard cost add nothing to the value; the tile says how many there are
Movements Stock ledger entries in the last 30 days
Transfers needed Stock that work orders need, sitting at the wrong site
Purchasing Open orders (approved, sent or part-received), plus drafts
Work orders Released or running, plus drafts

Needs attention

The task list, eight at a time, most urgent first — and within a priority, tasks that carry buttons (a decision being asked for now, such as a printer waiting for its bed to be cleared) ahead of ones that only report a condition; the count in the corner is the full total and Prev/Next at the foot of the card page through the rest. Each row is one thing to do, with a priority badge, the message, and the source that raised it. Click the message to go to the page that does the action.

Tasks come from three built-in generators plus anything an integration pushes:

Source Raised when
stock.low A stocked part is at or below its reorder point once what is already on order is subtracted
purchasing.overdue A sent purchase order is past its expected date with lines still outstanding
bom.blocked A finished good is below its reorder point and none can be built from stock; the message names the missing component
workorder.blocked An open work order's next step is waiting on a component that is short at the order's component location
anything else Pushed by an integration through the API (a print-farm manager, say)

The generators run every night, and Refresh tasks (planner) runs them now. Regeneration never duplicates a task and never un-snoozes one.

Some tasks carry buttons — Bed clear, Print failed — offered by the system that raised them. Pressing one records your choice on the task and resolves it; that system reads the choice back and acts on it (the print manager completes or scraps the run). Foudra only records the decision.

Snooze (the clock) hides a task for a week. Use it for "I know" — if the condition persists the task comes back; if it clears, the next run resolves it. Done (the tick) resolves it by hand; for a generated task that is only honest if you know the generator will agree.

The alert bar

The most urgent open task also appears at the top of every page, with "and N more". Its × is the same one-week snooze.

The last 13 weeks

Four graphs, one bar per week (weeks start on Monday, in your company's timezone). Hover over a bar for its figures.

A week with nothing to judge has no bar, rather than a misleading zero.