PRODUCTION PLANNING
Miridia is the supply chain automation platform for manufacturers. Bills of material carry their cost at any date, work orders post production straight into stock, and the forecast drives MRP and raw material purchasing.
WHAT GOES WRONG
Component prices move with every supplier quote. Scrap changes with the batch, and overhead follows an allocation rule that was set long ago. A unit cost that is recalculated in a spreadsheet at month end is wrong for most of the month.
When a recipe changes while a run is open, nobody can say which version the run used. The cost and the audit record both point at the wrong version.
The production plan and the raw material orders live in different files. A line stops for a missing component that the forecast showed weeks before.
Components are issued and finished goods are counted in a separate step, often on the next day. Until then, the stock figure is wrong at both ends.
THE RECIPE
A BOM in Miridia defines what goes into a product, what it cost on a given date, and which version was in force.
HOW IT RUNS
Miridia Planner, an add-on, forecasts each SKU from your sales history and from retailer sell-out. Retailer purchase orders that arrive over EDI become sales orders with no retyping.
The forecast drives the MRP report, the recalculation of reorder points and the purchase planning of BOM components. A raw material shortfall becomes a purchase order to the preferred supplier.
A work order takes a snapshot of the BOM when it is created, so a later recipe change never alters a run that is in progress. The same recipe can run through different production processes.
Completing the work order posts the components out and the finished goods in, valued at weighted average cost. It can create the output lot, with a lot number, an expiry date and the serial numbers of the units made.
FROM FORECAST TO FINISHED GOODSTHE PLATFORM
Miridia resolves the purchase price of each component from its price history on the date that you choose, normalised for pack sizes and units of measure. Watch how the cost of a product changed as its inputs moved.
A work order holds the BOM version that it started with. The trail from each finished good back to the components that it consumed stays intact through every recipe change.
Each raw material can have several suppliers, with their own SKU, lead time and minimum order quantity. Each BOM line names its preferred supplier, so MRP knows where to order.
A completed work order can create the lot of its output, with an expiry date and the serial number of each unit. Each serial links to its lot, its work order and its shipment.
A retailer purchase order over EDI becomes a sales order with the store delivery location and your SKUs already mapped. When the pallets leave, Miridia sends the dispatch advice and then the invoice.
Requisition-to-order workflows route a raw material request through an authorisation matrix and budget controls before it becomes a purchase order.
HONEST FIT
QUESTIONS
Miridia takes the components and quantities of the BOM, the purchase price of each component from its price history on the date that you choose, the scrap factor of each line, and the labour and overhead lines. Completed work orders value the output at weighted average cost.
Nothing. A work order takes a snapshot of the BOM when it is created, so the run finishes on the recipe that it started with. The new version applies to the next work order.
Yes. Miridia generates MRP reports. With Miridia Planner, which is priced separately, the forecast drives the MRP report, the recalculation of reorder points and the purchase planning of BOM components.
Yes. Completing a work order can create the lot of its output, with a lot number, an expiry date and the serial numbers of the units made. Each serial links to its lot, its work order and its shipment.
Yes. Miridia trades EDI documents through a certified EDI provider. A retailer purchase order becomes a sales order, and a sell-out report lets Planner forecast what consumers buy in store instead of what the retailer orders.
No. Miridia is not a general ledger. Cost lines on a BOM carry GL account codes, and Miridia syncs with the accounting package that you already use.
MAKE. MOVE. MEASURE.
Bring the recipe of one product and your last supplier prices. We build the BOM in a demo account and show you the unit cost today and a month ago.