Guide / the toolkit
Operations management tools, models and analytical approaches
The textbook toolkit — forecasting, EOQ, ABC, capacity and scheduling models, quality methods — mapped honestly to what software implements and what stays a human decision.
The key facts
- The classic toolkit has five shelves: forecasting, inventory models, capacity and scheduling, quality management, and supply-chain coordination.
- Software implements some shelves better than others: inventory models and KPI measurement embed well; forecasting and quality remain decision support, not autopilot.
- Every analytical model is only as good as the record beneath it — garbage quantities in, confident garbage out.
- BSimple's position: the record and measurement layers (KPIs, reorder points, movement histories) are product; the strategy layers stay with management.
- 01The key facts
- 02The five shelves of the toolkit
- 03The honest mapping to software
- 04Where BSimple sits in the toolkit
The five shelves of the toolkit
Forecasting. Moving averages, exponential smoothing, seasonality decomposition — models that turn history into demand expectations. Software computes them cheaply; the judgement (which model, which horizon, when a trend breaks) stays human. Beware any product selling forecasting as certainty.
Inventory models. The classics — EOQ (economic order quantity: order size balancing ordering cost against holding cost), reorder point (demand during lead time plus safety stock), ABC analysis (effort concentrated on the few SKUs that matter), safety stock statistically derived from variability. These embed well: a system holding live quantities and lead times computes reorder points continuously, which is exactly what purchasing from demand means in BSimple.
Capacity and scheduling. Little's law, bottleneck analysis, sequencing rules (FIFO, SPT) — the models behind "what can we actually take on". Software surfaces the data; the scheduling decision in make-to-order businesses stays a planner's call — the MRP boundary is where this shelf meets its software ceiling.
Quality. Control charts, Pareto analysis, root-cause discipline. The record contributes the data (variances, returns, adjustments); the method is management's.
Supply-chain coordination. Lead-time measurement, supplier scorecards, the bullwhip effect and its dampening. Systems make the data available; coordination is a practice.
The honest mapping to software
Two shelves embed well: inventory models (reorder points, par levels, ABC reporting are computed continuously from the record) and measurement (fill rate, accuracy, cycle time — the KPI set — fall out of a movement history automatically). Two shelves become decision support: forecasting produces numbers that a human still orders against; quality analytics surface patterns a team must act on. One shelf mostly exceeds SMB software weight: capacity optimisation at MRP scale is enterprise territory — the boundary is real, and honest vendors state it.
The dependency beneath every shelf: the record. EOQ computed on untrustworthy quantities optimises fiction. This is why operations texts start with data collection and why the movement-based design is the foundation of every analytical approach above.
Where BSimple sits in the toolkit
We build BSimple, so weigh that. It implements the record and the embedded-model shelves: live multi-location quantities (the data foundation), reorder levels and purchase orders from demand (the inventory models), KPI-computable histories (the dashboard), batch traceability for the quality shelf's root-cause work. It deliberately does not implement forecast-driven MRP scheduling — the planning shelf stays with heavier systems or with spreadsheets run by people who understand their demand. Plans: $180/$250/$399 per month AUD, the trial full-featured. The toolkit's textbooks are right about one thing above all: the analytical approaches only pay when the record beneath them is true.
Frequently Asked Questions
What are the main tools of operations management?
Forecasting models, inventory models (EOQ, reorder points, ABC analysis), capacity and scheduling techniques, quality methods (control charts, Pareto), and supply-chain coordination practices. The first question for all of them is whether the underlying record is true.
What is EOQ and should we compute it?
Economic order quantity — the order size minimising combined ordering and holding costs, from annual demand, order cost and holding cost. Useful as a sanity check on order sizes; compute it from real cost data or skip it rather than feed it guesses.
Which operations models does software automate?
Inventory models and KPI measurement embed naturally — computed continuously from movement records. Forecasting and quality analytics are decision support; capacity optimisation at scale is enterprise software. No model automates the judgement.
Does BSimple include forecasting?
No demand forecasting is claimed — the record provides clean history (which forecasting requires), and the reorder logic works from par levels and live quantities. We state the boundary rather than sell certainty we do not have.
Where should a small business start with this toolkit?
With the record and the inventory models: a truthful stock history, reorder points on the SKUs that matter (ABC first), and the KPI trend. The trial establishes the record on your products — the foundation every other tool presumes.
BSimple