Performance Measurement, Analytics and Continuous Improvement

Introduction

Inventory and warehouse management becomes strategically valuable when performance is measured consistently, interpreted intelligently, and improved systematically. A warehouse may report high productivity while creating downstream stock-outs, inaccurate inventory records, unsafe conditions, or excessive expediting. Conversely, a facility may appear costly because it carries safety stock that protects customer service during unreliable replenishment. Performance measurement therefore cannot be reduced to a single productivity ratio. It requires a balanced system linking operational activity to service, cost, asset utilization, quality, resilience, and improvement.

This chapter develops an integrated approach to measuring and improving inventory and warehouse performance. It explains key performance indicators (KPIs), dashboard design, data-quality requirements, root-cause analysis, Lean and 5S, Six Sigma, and simulation. The emphasis is not merely on calculating indicators, but on understanding what they mean, what they conceal, and how managers can convert evidence into responsible decisions.

Learning Objectives

By the end of this chapter, the learner should be able to:

1. Define and calculate major inventory, warehouse, service, and cost KPIs.
2. Interpret relationships and trade-offs among inventory turns, days of supply, accuracy, utilization, throughput, cycle time, and fulfillment accuracy.
3. Design a dashboard that distinguishes strategic, tactical, and operational measures.
4. Apply Pareto analysis, the five-whys method, fishbone analysis, process mapping, and statistical reasoning to operational problems.
5. Use Lean, 5S, Six Sigma, and simulation principles in warehouse improvement.
6. Evaluate data, governance, ethical, and implementation risks in performance-management systems.

1. Performance Measurement as a Management System

A KPI is a defined measure used to evaluate performance against a purpose, target, standard, or benchmark. A metric becomes a KPI when it is connected to a decision and an accountable owner. For example, “picks completed” is a metric; “lines picked per labor hour compared with the engineered standard, with corrective action when the gap exceeds 10%” is a management KPI.

A robust measurement system has five characteristics:

• Strategic alignment: measures support organizational objectives such as availability, cash reduction, customer service, safety, or resilience.
• Balance: financial, customer, process, people, and asset measures are considered together.
• Causality: leading indicators, such as replenishment compliance, are linked to lagging outcomes, such as stock-outs.
• Comparability: definitions, time windows, exclusions, and units are stable.
• Actionability: a responsible person can investigate and influence the result.

Measurement systems often fail through local optimization. A receiving team that maximizes pallets processed may push congestion into put-away. A picking team that maximizes lines per hour may increase errors. A purchasing team that achieves a low unit price may create excess inventory and obsolescence. The correct question is therefore not “Which department has the best number?” but “Does the complete flow deliver the required customer outcome with minimum total waste and acceptable risk?”

Levels of measurement

A dashboard should not display every available measure. Excessive indicators dilute attention and encourage superficial reporting. A practical dashboard normally contains a small set of outcome KPIs, diagnostic measures, and clearly defined targets.

2. Inventory Performance Indicators

2.1 Inventory turns

Inventory turns indicate how many times average inventory is consumed and replenished during a period. The cost-based form is:

Average inventory may be calculated as the mean of beginning and ending inventory, or as the average of periodic observations when inventory fluctuates substantially:

Here, I_i is inventory value at observation i, measured at a consistent cost basis, and n is the number of observations. The formula assumes that cost of goods sold and inventory are measured over the same period and use comparable valuation rules. Using sales revenue in the numerator and cost-valued inventory in the denominator produces a distorted ratio unless the purpose and valuation basis are explicitly justified.

High turns can indicate efficient flow, but may also indicate understocking, frequent emergency replenishment, or vulnerability to disruption. Low turns can reflect excess stock, slow-moving items, strategic buffers, or long lead times. Interpretation must therefore be segmented by product family, service requirement, and supply risk.

2.2 Days of supply

Days of supply (DOS), also called days of inventory on hand, expresses current stock in relation to expected daily demand:

If demand is based on a period of T days:

Inventory available must be defined. It may mean on-hand stock, or on-hand plus usable scheduled receipts minus committed demand. The chosen definition should be documented because including unavailable, quarantined, or already allocated inventory can produce a misleading result. DOS is a time-based measure and should not be compared across products with different demand variability without considering safety stock and lead time.

Under a simplified constant-demand relationship, turns and DOS are approximately related by:

This relationship is valid only when the same valuation and demand basis is used and average inventory is representative. It is not a substitute for detailed inventory planning.

Worked example: turns and days of supply

A distributor reports annual cost of goods sold of $12,000,000. Monthly inventory at cost averages $2,000,000. Annual demand in units is 365,000, and current usable stock is 18,000 units.

Inventory turns are:

12,000,000 ÷ 2,000,000 = 6 turns per year

Average daily demand is:

365,000 ÷ 365 = 1,000 units per day

Current DOS is:

18,000 ÷ 1,000 = 18 days

The six-turn result uses average inventory and annual cost. The 18-day result uses current units and forecast demand. They answer different questions and should not be treated as identical indicators.

2.3 Inventory accuracy

Inventory accuracy compares system records with physically verified stock. A common item-location accuracy measure is:

A quantity-based measure may be used when quantity variance is more important:

The quantity formula assumes a non-zero, consistently valued denominator and expresses aggregate absolute error relative to recorded stock. It can conceal serious errors in small but critical items; therefore, item-level exception rates and ABC-based reporting should supplement it. Accuracy is affected by receiving discipline, unit-of-measure conversions, location control, picking confirmations, returns, damage recording, and cycle-count design.

2.4 Obsolescence, availability, and inventory quality

Inventory value alone is insufficient. Managers should examine:

• aged and obsolete inventory;
• excess inventory above policy levels;
• stock-outs and backorders;
• inventory at risk from expiry or deterioration;
• cycle-count adjustments;
• supplier and customer returns;
• inventory subject to quarantine or quality hold.

A useful governance principle is that inventory should be classified by both value and criticality. An inexpensive safety component may deserve stricter control than a high-value but easily replaceable item.

3. Warehouse and Fulfillment KPIs

3.1 Capacity and utilization

Storage utilization can be calculated by volume, pallet positions, floor area, or an engineered capacity measure:

“Usable capacity” excludes aisles, safety clearances, fire-protection zones, structural restrictions, and inaccessible locations. Utilization above a nominal threshold is not automatically efficient. Very high utilization may increase travel, double handling, congestion, and replenishment difficulty. A facility should distinguish space utilization from flow utilization: a warehouse can be full but operationally ineffective.

Labor utilization is also context-dependent:

The definition of productive hours must include or exclude meetings, training, travel, waiting, and equipment downtime consistently. Low utilization may reflect poor planning; high utilization may indicate inadequate flexibility or unsafe workload.

3.2 Throughput and productivity

Throughput is the quantity completed by a process during a defined interval:

Examples include pallets received per hour, cases put away per shift, or order lines shipped per day. Productivity relates output to a resource:

Throughput should be interpreted with quality and service. A higher rate accompanied by more mis-picks is not genuine improvement. Bottleneck analysis is essential because improving a non-bottleneck activity may not increase total system output.

3.3 Dock-to-stock time

Dock-to-stock time measures the elapsed time from receipt at the dock to stock being available in the correct system location. A formal definition should specify start and end events. For receipt i:

The average is:

Median and percentile values are often more informative than the average because a few delayed receipts can produce a long-tailed distribution. Causes of delay include documentation errors, inspection, congestion, system downtime, put-away travel, missing locations, and quality holds. A facility should report both total time and process segments rather than treating all delay as warehouse labor inefficiency.

3.4 Order-cycle time

Order-cycle time is the time from customer order release or receipt to shipment, delivery, or another agreed completion point. The start and end points must be explicit. For example:

If customer promise is measured through delivery, transportation time must be included. Comparing a warehouse-only measure with an end-to-end customer promise creates an invalid conclusion.

3.5 Fulfillment accuracy

Fulfillment accuracy measures whether the customer receives the correct product, quantity, condition, and destination within the required time. A simple order-level measure is:

The organization must define whether late orders, substitutions, damaged items, and documentation errors count as failures. Line-level accuracy can be calculated similarly, but order-level accuracy is often more meaningful for customer experience. Both should be reported when a single order contains many lines.

3.6 Cost KPIs

Warehouse cost analysis may include labor, space, equipment, utilities, information systems, packaging, maintenance, damage, and outsourced services. Useful ratios include:

The carrying-cost rate may include financing, insurance, storage, handling, shrinkage, and obsolescence. It is not a universal constant; assumptions must be stated. Cost per order can fall as volume rises while total cost increases, so managers should examine both unit cost and total cost.

4. Dashboard Design and Interpretation

A dashboard is an information interface for decisions, not a decorative collection of charts. It should provide a concise view of current condition, trend, target, variance, owner, and required action.

A practical dashboard architecture contains:

1. Outcome layer: service level, fulfillment accuracy, inventory turns, total cost.
2. Process layer: dock-to-stock time, pick productivity, replenishment compliance, backlog.
3. Driver layer: receiving errors, travel distance, slotting compliance, system downtime, absenteeism.
4. Exception layer: critical shortages, aged orders, blocked locations, safety incidents, data anomalies.

A KPI card should state the measure definition, numerator, denominator, data source, frequency, owner, target, tolerance, and exclusion rules. Traffic-light colors are useful only when thresholds are meaningful. A green value can be misleading if the target is too easy or if data completeness is poor.

Figure: A balanced dashboard connects outcome measures with process drivers and an improvement loop.

Data quality and statistical interpretation

A KPI is only as credible as its data. Important controls include timestamp synchronization, master-data governance, unit-of-measure validation, duplicate-event detection, audit trails, and reconciliation between warehouse-management and enterprise-resource-planning systems. Missing data should not automatically be interpreted as zero performance.

Managers should distinguish variation from a genuine shift. A control chart plots observations over time against a central line and statistically derived control limits. Control limits describe expected process variation; they are not the same as customer targets. A process can be stable but incapable of meeting the target, or unstable while its average appears acceptable. For a measured variable with mean μ and standard deviation σ, conventional three-sigma limits are:

These limits are appropriate only under suitable assumptions about the data, sampling, independence, and stable process behavior. Control charts should not be used mechanically, and limits should not be recalculated after every undesirable observation to hide special causes.

Correlation between KPIs does not prove causation. For example, higher utilization may coincide with longer cycle time because both rise during peak season, while the underlying cause is demand surges. Segmentation, process knowledge, controlled trials, and time-order analysis improve interpretation.

5. Root-Cause Analysis

Root-cause analysis seeks the systemic conditions that allow a problem to recur. It is different from assigning blame. A disciplined investigation defines the problem, establishes evidence, identifies contributing causes, tests hypotheses, implements controls, and verifies that the result persists.

Problem definition

A useful problem statement specifies what happened, where, when, magnitude, and comparison with the expected condition. “Picking is poor” is weak. “In Zone B, wrong-item errors increased from 0.4% to 1.5% during evening shifts over four weeks, primarily on replenished locations” is actionable.

Pareto analysis

A Pareto chart ranks categories by frequency, cost, or impact and displays cumulative contribution. The “80/20 rule” is a heuristic, not a law. A small number of causes may dominate, or many causes may contribute similarly. The correct measure of importance depends on the decision: frequency, financial loss, customer harm, or safety risk.

Five whys and fishbone analysis

The five-whys technique repeatedly asks why a condition occurred until a controllable systemic cause is reached. Five is not a mandatory number; stopping at five can be premature. A fishbone diagram organizes possible causes under categories such as people, methods, machines, materials, measurement, and environment. These tools generate hypotheses, but evidence is required to confirm them.

Fault trees and failure modes

For high-risk processes, a fault tree starts with an undesired event and works backward through logical combinations of causes. Failure Mode and Effects Analysis (FMEA) evaluates failure modes by severity, occurrence, and detectability. A traditional risk priority number may be calculated as:

The ratings are ordinal judgments, not physical measurements. Multiplying them does not guarantee a valid ranking; a high-severity rare failure may deserve priority even if its RPN is moderate. Modern practice therefore uses RPN as one input alongside severity thresholds, legal requirements, and expert review.

6. Lean Warehousing and 5S

Lean thinking seeks to deliver customer value with less waste while respecting people. Common warehouse wastes include excess transport, motion, waiting, over-processing, inventory, defects, overproduction, and underused human capability. Lean does not mean simply reducing labor or inventory. Removing buffers without stabilizing demand and replenishment can make the system fragile.

Value-stream mapping represents material and information flow from request to fulfillment. It helps identify queues, handoffs, rework, and non-value-adding time. Kaizen involves structured, incremental improvement by the people who perform the work. Standard work documents the best currently known method, sequence, timing, quality points, and response to abnormalities. It is a baseline for improvement rather than an unchangeable rule.

5S

5S is a workplace organization method:

1. Sort: remove unnecessary items.
2. Set in order: locate items for safe, intuitive retrieval.
3. Shine: clean while inspecting equipment and conditions.
4. Standardize: establish visual and procedural standards.
5. Sustain: audit, coach, and improve the system.

5S is not merely cosmetic cleaning. In a warehouse it can reveal damaged racks, leaking batteries, obstructed fire equipment, mislabeled locations, obsolete tools, and unsafe pedestrian routes. Audits should assess whether the condition supports flow and safety, not whether a checklist was completed.

7. Six Sigma and Process Capability

Six Sigma uses structured problem solving and statistical evidence to reduce defects and variation. DMAIC consists of Define, Measure, Analyze, Improve, and Control.

• Define: clarify the customer requirement, scope, problem, and business case.
• Measure: establish operational definitions and reliable baseline data.
• Analyze: identify and verify significant causes.
• Improve: test and implement solutions.
• Control: standardize, monitor, and respond to regression.

For a normally distributed process with specification limits, a capability index can be expressed as:

where USL and LSL are upper and lower specification limits and σ is within-process standard deviation. C_p measures potential capability if the process is centered. A centering-sensitive index is:

where μ is the process mean. These indices assume meaningful specification limits, an appropriate measurement system, and a sufficiently stable process. Warehouse count errors and cycle times may be skewed or discrete; normality should not be assumed automatically. Alternatives include transformation, percentile analysis, or defect-rate modeling.

Measurement-system analysis is important. If scanners, clocks, location masters, or counting methods are inconsistent, apparent process variation may be measurement variation. A highly sophisticated analysis of unreliable data is still unreliable.

8. Simulation and Digital Experimentation

Simulation represents the behavior of a real system so that alternatives can be evaluated without disrupting operations. Discrete-event simulation is suitable for warehouses because arrivals, picks, replenishment, equipment failures, and departures occur as events over time. It can examine congestion, staffing, wave release, conveyor capacity, dock appointments, and storage policies.

A credible simulation process includes:

1. define the decision and performance measures;
2. map the real process and collect arrival, service, routing, and failure data;
3. build a conceptual model with explicit assumptions;
4. verify that the model was implemented as intended;
5. validate outputs against observed system behavior;
6. run warm-up and replication periods where appropriate;
7. test scenarios and quantify uncertainty;
8. communicate limitations and implementation implications.

Simulation outputs are estimates, not facts. Random-number seeds, input distributions, model boundaries, resource rules, and exceptional events influence results. A scenario that improves average throughput may worsen the 95th-percentile order time or create unsafe congestion. Decision-makers should examine distributions and service constraints, not only averages.

A simple queueing relationship is useful for diagnostic reasoning. Little’s Law states:

where L is the average number of units in the system, λ is the long-run average throughput rate, and W is the average time a unit spends in the system. The relationship applies under stable conditions and consistent system boundaries. For example, if an average of 240 orders are in a fulfillment process and throughput is 60 orders per hour, average order-cycle time is:

W = L ÷ λ = 240 ÷ 60 = 4 hours

Little’s Law does not explain why the time is four hours, nor does it imply that increasing work-in-process is beneficial. It provides a consistency check and highlights the trade-off between backlog and cycle time.

9. Integrated Illustrative Case: Northstar Distribution Centre

The following case is fictional and intended for instructional application.

Background

Northstar Distribution Centre supplies retail stores and e-commerce customers. Management observed that inventory turns improved from 5.2 to 6.4, yet customer complaints and premium freight increased. The dashboard showed 96% storage utilization, 94.8% order fulfillment accuracy, and an average dock-to-stock time of 19 hours against a 10-hour target.

Problem and analysis

A cross-functional team segmented the data by channel, shift, product family, and location type. It found that:

• the turns increase was partly caused by reducing cycle stock before a seasonal peak;
• 38% of order errors came from 6% of locations with similar packaging and adjacent product codes;
• the average dock-to-stock time concealed a median of 7 hours and a 90th percentile of 31 hours;
• receiving delays were associated with incomplete advance shipment notices and quality holds;
• utilization above 95% caused temporary floor storage and blocked replenishment routes;
• the dashboard counted shipped orders but did not consistently exclude customer-requested changes.

The team used a Pareto analysis for errors, a fishbone analysis for receiving delays, and a time study of replenishment. A five-whys investigation showed that location labels were not the primary cause: the deeper issue was a master-data process that allowed new packaging configurations without a formal slotting and scan-validation review.

Approach and solution

Northstar introduced the following actions:

1. created a KPI dictionary with owners, definitions, exclusions, and data sources;
2. separated inventory turns by stable, seasonal, and promotional product classes;
3. redesigned the dashboard to show median and 90th-percentile dock-to-stock time;
4. implemented scan confirmation at receiving, put-away, and picking;
5. re-slotted high-frequency and look-alike items, with visual differentiation;
6. established a daily cross-functional exception meeting limited to actionable issues;
7. used 5S to remove obsolete packaging and mark pedestrian and staging zones;
8. simulated alternative receiving appointment patterns before changing dock schedules;
9. introduced a control plan monitoring errors by shift and location family.

Outcome

After twelve weeks, the illustrative results were: fulfillment accuracy increased from 94.8% to 98.7%; median dock-to-stock time declined from 7 to 5 hours; the 90th percentile declined from 31 to 14 hours; and storage utilization fell to 89%, while usable capacity increased through improved slotting. Inventory turns declined slightly to 6.1 because a deliberate buffer was restored for critical seasonal items. Premium freight fell despite the lower turns.

The results demonstrate that a lower inventory ratio is not automatically superior. Northstar improved total performance by using inventory selectively, improving data integrity, and reducing process variation. The outcome also illustrates why average values alone can conceal operational risk.

Learning points

• KPIs must be interpreted as a system, not as isolated scores.
• Percentiles can reveal service risk hidden by averages.
• Root causes often involve master data, process design, and governance rather than individual effort.
• Improvement should be verified through sustained results and unintended-consequence checks.
• A deliberate inventory buffer can be economically rational when it protects service and reduces expediting.

10. Implementation, Governance and Ethics

Performance systems influence behavior. If employees are rewarded solely for speed, they may bypass scans, conceal errors, or avoid difficult work. If managers publish individual rankings without considering task mix, equipment constraints, disability accommodation, or training status, the system may be unfair and operationally damaging.

Good governance requires:

• transparent KPI definitions and change control;
• role-based access to employee and customer data;
• data minimization and retention policies;
• auditability of adjustments and overrides;
• security for operational technology and warehouse systems;
• human review of algorithmic recommendations;
• protection against discriminatory productivity standards;
• consultation with workers when monitoring technologies are introduced.

Artificial intelligence can assist with demand anomaly detection, slotting recommendations, computer vision, predictive maintenance, and natural-language explanation of dashboard changes. However, AI outputs depend on data quality and may reproduce historical bias. Recommendations should be explainable enough for operational review, tested against safety and service constraints, and subject to human accountability. AI should support—not replace—process knowledge and responsible managerial judgment.

Contemporary warehouses increasingly combine warehouse-management systems, labor-management systems, IoT sensors, robotics, digital twins, and cloud analytics. Integration creates opportunities for near-real-time control but also increases cyber risk, vendor dependence, and data-governance complexity. Technology adoption should begin with a defined decision problem and measurable benefit, not with a desire to acquire advanced tools.

Best-Practice Checklist

A mature performance-improvement system should:

• define each KPI mathematically and operationally;
• use consistent time periods, units, and valuation bases;
• combine outcome, process, driver, and exception indicators;
• segment results by product, channel, shift, and location where relevant;
• report distributions and percentiles when delays are variable;
• validate data and measurement systems before analysis;
• use root-cause evidence rather than blame or assumptions;
• protect safety, quality, and employee dignity;
• pilot changes and assess unintended consequences;
• standardize successful improvements and continue monitoring;
• document assumptions in dashboards, models, and simulations.

Chapter Summary

Performance measurement in inventory and warehouse management is a decision system linking strategy, process execution, customer service, cost, assets, and risk. Inventory turns and days of supply describe different aspects of stock; accuracy measures expose record reliability; utilization and throughput describe resource and flow performance; dock-to-stock and order-cycle time reveal responsiveness; fulfillment accuracy and cost indicators connect warehouse activity to customer and financial outcomes.

Effective dashboards use controlled definitions, reliable data, balanced measures, targets, owners, trends, and exception logic. Averages must be supplemented by medians, percentiles, segmentation, and control-chart reasoning where variation matters. Root-cause analysis uses problem statements, Pareto analysis, five whys, fishbone diagrams, FMEA, and evidence-based verification. Lean and 5S reduce waste and stabilize work, while Six Sigma provides a structured DMAIC method for reducing defects and variation. Simulation supports safe experimentation with capacity, congestion, staffing, and policy alternatives, but its assumptions and uncertainty must be made explicit.

Continuous improvement succeeds when measurement is connected to action, learning, standardization, and ethical governance. The best-performing warehouse is not necessarily the one with the highest turns, utilization, or labor rate; it is the one that reliably delivers required service at sustainable total cost and risk.

Key Terms

KPI: A defined performance measure connected to a target, decision, and accountable owner.

Inventory turns: Cost of goods sold divided by average inventory at cost.

Days of supply: Available inventory expressed as expected days of demand.

Inventory accuracy: Agreement between recorded and physically verified inventory.

Utilization: The proportion of usable capacity or available labor resource occupied or productively used.

Throughput: Quantity completed by a process during a specified time interval.

Dock-to-stock time: Elapsed time from receipt confirmation to inventory availability in the correct location.

Order-cycle time: Elapsed time between defined order initiation and completion events.

Fulfillment accuracy: Proportion of orders or lines completed without specified errors.

Dashboard: A visual information interface designed to support monitoring and decisions.

Leading indicator: A measure that signals conditions likely to influence future outcomes.

Lagging indicator: A measure of an outcome after performance has occurred.

Root-cause analysis: A structured investigation into systemic causes of recurring problems.

Pareto analysis: Ranking causes by contribution to frequency, cost, or impact.

Lean: A management philosophy focused on customer value, flow, waste reduction, and respect for people.

5S: Sort, Set in order, Shine, Standardize, and Sustain.

Six Sigma: A data-based approach for reducing process defects and variation.

Process capability: The ability of a stable process to meet specified requirements.

Simulation: A representation of a real system used to evaluate behavior and alternatives.

Little’s Law: The stable-system relationship L = λW, connecting average work-in-process, throughput, and time.

Review Questions

Short Answer Questions

1. Why should inventory turns not be interpreted without considering service level and product characteristics?
2. Distinguish storage utilization from throughput utilization.
3. What information should be included in a KPI definition?
4. Explain the difference between a control limit and a customer performance target.
5. Why is measurement-system reliability important before applying Six Sigma analysis?

Long Answer Questions

1. Explain how a balanced warehouse dashboard can prevent local optimization. Use at least four KPIs in your answer.
2. Describe the DMAIC method and show how it could be applied to recurring picking errors.
3. Compare Lean, 5S, and Six Sigma in terms of purpose, methods, and expected outputs.
4. Discuss the assumptions and limitations of simulation in warehouse design and operational decision-making.
5. Evaluate the ethical and governance risks of using employee productivity analytics and AI recommendations in a warehouse.

Analytical / Application Questions

1. A warehouse has annual cost of goods sold of $18 million and average inventory at cost of $3 million. Usable inventory is 24,000 units and forecast annual demand is 438,000 units. Calculate inventory turns and current days of supply, and explain why the measures are not directly interchangeable.
2. A fulfillment process has 360 orders in progress and completes 90 orders per hour. Use Little’s Law to estimate average order-cycle time. Identify two operational causes that could increase the result even if the completion rate remains unchanged.
3. A facility reports 97% average order accuracy but experiences a 25% rise in customer complaints. Design an investigation using segmentation, Pareto analysis, data validation, and at least one process-improvement method. State which additional KPIs you would place on the dashboard.

Multiple Choice Questions with Answers

Question 1

A distributor has cost of goods sold of $8,000,000 and average inventory at cost of $2,000,000. What are its inventory turns?

A. 2 turns

B. 4 turns

C. 6 turns

D. 10 turns

Correct Answer: B. 4 turns

Question 2

Which definition best represents days of supply?

A. Annual sales divided by average inventory value

B. Inventory available divided by average daily demand

C. Total warehouse cost divided by orders processed

D. Completed units divided by labor hours

Correct Answer: B. Inventory available divided by average daily demand

Question 3

Which measure is most likely to reveal severe delays hidden by a small number of extreme observations?

A. Mode only

B. Average only

C. Median and a high percentile

D. Total annual demand only

Correct Answer: C. Median and a high percentile

Question 4

A warehouse has 300 orders in process and completes 75 orders per hour. Under stable conditions, what is the average time in the process?

A. 2 hours

B. 4 hours

C. 225 hours

D. 375 hours

Correct Answer: B. 4 hours

Question 5

Which activity is the primary purpose of the ‘Standardize’ step in 5S?

A. Remove all inventory from the facility

B. Establish consistent methods and visual conditions

C. Increase equipment speed regardless of quality

D. Replace cycle counting with annual counting

Correct Answer: B. Establish consistent methods and visual conditions

Question 6

What is the correct sequence of DMAIC?

A. Define, Measure, Analyze, Improve, Control

B. Design, Monitor, Allocate, Inspect, Calculate

C. Determine, Model, Audit, Integrate, Certify

D. Define, Manage, Automate, Inspect, Close

Correct Answer: A. Define, Measure, Analyze, Improve, Control

Question 7

Which statement about inventory accuracy is most appropriate?

A. A system record is accurate whenever its value is high

B. Accuracy requires comparing system records with verified physical stock

C. Accuracy can be measured only through annual financial statements

D. Accuracy is identical to inventory turns

Correct Answer: B. Accuracy requires comparing system records with verified physical stock

Question 8

Which condition is required for the usual interpretation of a control chart?

A. The process must be intentionally changed every day

B. The data and process boundaries must be reasonably stable and defined

C. All observations must equal the target exactly

D. Control limits must be the same as specification limits

Correct Answer: B. The data and process boundaries must be reasonably stable and defined

Question 9

What is a major risk of measuring warehouse performance only through lines picked per labor hour?

A. It necessarily lowers throughput

B. It can encourage speed at the expense of accuracy and safety

C. It eliminates all local optimization

D. It measures customer satisfaction directly

Correct Answer: B. It can encourage speed at the expense of accuracy and safety

Question 10

Which statement about simulation is correct?

A. Simulation results are facts independent of assumptions

B. Simulation removes the need for process validation

C. Simulation can compare alternatives, but outputs depend on model assumptions and data

D. Simulation is useful only for financial accounting

Correct Answer: C. Simulation can compare alternatives, but outputs depend on model assumptions and data