From demand to purchase order
Material requirements planning answers one question: given what we expect to sell, what do we make, what do we need, and what must we buy? Knotworking follows that chain with each step reading the one before it.
- Demand. Enter demand per product, week and customer by hand, import it from CSV, or have your sales system post it.
- Batch schedule. Turn demand into a production schedule built from approved recipes.
- Material requirements. Each scheduled batch is checked against stock, so shortfalls show before the day you need the material.
- Purchase orders. Raise purchase orders from the shortfall, then receive goods against the order.
A plan that turns into records
A batch isn't only a line on a schedule. Its batch record consumes real lots from stock and produces new ones, so what the plan assumed and what the floor did end up in the same ledger. The next plan starts from what is actually in stock.
Stock is kept as locations and dated lots with an append-only movement ledger, so every number can be traced back to the goods-in and batches that made it.
Who it suits
It is designed around food: recipes with yields and allergens, dated lots, and the records an inspector asks for. If that describes your site, the planning and the compliance records share one database instead of living in a spreadsheet and a separate system.
If you build discrete assemblies, or need a general-purpose manufacturing suite, it is probably not the right tool.
The modules involved
Each is a separate module, switched on in the installation and then granted person by person. How modules work.
- Demand planning
- Demand per product, week and customer, entered by hand, imported from CSV or posted by your sales system.
- Recipes
- Versioned bills of materials with yields, scaling, allergen and cost roll-up, approved before use.
- Stock
- Locations, dated lots, goods-in and an append-only movement ledger with traceability.
- Production
- A batch schedule from approved recipes, material requirements against stock, and batch records that consume and produce lots.
- Purchasing
- Purchase orders from the shortfall, goods-in against an order, three-way invoice matching and supplier performance.
- Items and suppliers
- Ingredients, packaging and products with units and allergens, and approved suppliers.
- Costing
- Actual cost per batch from the lots it used, work in progress, yield variance and standard against actual.
Questions
- Is this a full MRP system?
- It covers the planning loop above for food production: demand, an approved-recipe batch schedule, requirements against stock and purchase orders. It is built for food manufacturing rather than for every kind of factory.
- Do I pay per user?
- No. Knotworking is free and open source, and you run it on your own server. There is no hosted plan or per-seat price.
- Can I switch on just the planning modules?
- Yes. Modules are chosen in the installation's settings, and each one names the modules it depends on. Turning one off hides it and deletes nothing.
- How does demand get in?
- By hand, from a CSV file, or posted by your sales system. Demand is held per product, per week and per customer.