Design Methodology, Capacity, and Flow Planning

Introduction

Warehouse design is a systems-design problem rather than a space-allocation exercise. A warehouse must receive, identify, store, replenish, pick, consolidate, pack, stage, and dispatch material while meeting service, safety, cost, and resilience requirements. Decisions about building size or rack configuration are therefore consequences of a broader design process. If requirements are incomplete or flow relationships are misunderstood, a technically impressive layout may still produce congestion, excessive travel, poor inventory accuracy, and inadequate capacity.

This chapter presents a systematic methodology for warehouse planning. It connects business requirements to process maps, demand and throughput forecasts, storage and handling capacity, space allowances, alternative flows, growth scenarios, and design validation. The emphasis is on graduate-level reasoning: the designer must quantify demand, make assumptions explicit, test alternatives, and recognize uncertainty rather than treat a single forecast as fact.

A warehouse design should be judged on at least six dimensions:

1. Service: Can customer and production requirements be met reliably?
2. Capacity: Is sufficient storage, staging, handling, and processing capacity available?
3. Flow: Can materials move with minimal conflict, delay, and unnecessary travel?
4. Resource productivity: Are labor, equipment, and information systems used effectively?
5. Safety and compliance: Are people, products, equipment, and data protected?
6. Adaptability: Can the facility accommodate seasonality, product change, and growth?

Learning Objectives

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

• define warehouse design requirements and distinguish demand from design assumptions;
• map material, information, and decision flows;
• forecast storage demand and operational throughput using appropriate time bases;
• calculate inventory, pallet-position, floor-space, staging, and handling requirements;
• develop and compare alternative warehouse flow concepts;
• incorporate utilization, variability, constraints, and growth into capacity decisions;
• validate a proposed design using quantitative, operational, safety, and financial tests; and
• communicate design recommendations and their risks to managerial stakeholders.

1. The Design Logic: From Requirements to a Validated Concept

A robust design normally follows an iterative sequence:

Business strategy → Requirements → Process map → Demand model
        ↑                                      ↓
Validation ← Alternatives ← Capacity and space model ← Flow logic

Figure: Iterative relationship among requirements, process analysis, capacity modeling, alternatives, and validation.

The sequence is not strictly linear. A process map may reveal missing requirements; a capacity calculation may show that the service target is unrealistic; and a simulation may expose congestion that requires a revised layout. The design team should therefore maintain a traceable link from each major layout decision to the requirement or evidence supporting it.

1.1 Requirements definition

Requirements should be classified before dimensions are calculated. A useful requirements register includes:

A requirement should be measurable whenever possible. “Fast picking” is not a design requirement; “95% of released orders dispatched within two hours” is more useful. Requirements should also be ranked as mandatory, desirable, or negotiable. This prevents a low-priority preference from displacing a safety or regulatory obligation.

1.2 Scope and unit of analysis

Designers must define the system boundary. A warehouse may be modeled from supplier arrival to customer departure, or may include returns, value-added services, cross-docking, and yard operations. The basic unit also matters: pallets, cases, totes, order lines, orders, kilograms, cubic metres, or handling events. Confusing these units is a common source of error. For example, a warehouse may receive 200 pallets per day but pick 4,000 order lines per day; each figure drives a different resource and space requirement.

2. Process Mapping and Activity Analysis

Process mapping converts a general requirement into a sequence of activities, decisions, resources, and information transactions. A high-quality map shows both physical and information flows:

1. appointment and yard check-in;
2. unloading and receipt verification;
3. inspection, counting, and system receipt;
4. identification, labeling, and quality hold if required;
5. put-away and location confirmation;
6. replenishment from reserve to forward or pick locations;
7. order release and wave, batch, zone, or continuous picking;
8. consolidation, packing, documentation, and value-added work;
9. dispatch staging, loading, and shipment confirmation; and
10. returns, damages, exceptions, and inventory adjustments.

For each activity, document the trigger, input, output, processing time, queue, resource, location, decision rule, and failure mode. A process map should reveal crossings and recirculation. For example, returns that enter through the outbound staging area may interfere with dispatch, even if the total annual return volume appears small.

2.1 Flow classification

A useful classification is:

• Unit flow: movement of a single case, tote, item, or order.
• Batch flow: movement of a group consolidated for efficiency.
• Pallet flow: movement of full load units.
• Information flow: orders, receipts, location records, replenishment signals, and shipment confirmations.
• Exception flow: damaged, short, overage, quarantined, or unidentifiable material.

Material flow and information flow must agree. A location cannot be considered available merely because it is physically empty; the warehouse management system must also recognize the location status. This principle is central to inventory accuracy and automation safety.

2.2 Activity relationship analysis

Flow intensity can be represented using a from–to chart. If activity i sends a quantity f_ij to activity j, the total movement burden can be estimated as:

where B is movement burden in unit-distance movements, f_ij is the number of loads or trips from activity i to j during the selected period, and d_ij is the travel distance. The measure is useful for comparing alternatives, but it is not a complete cost model: congestion, vertical travel, acceleration, waiting, safety separation, and different equipment types may make equal distances operationally unequal.

3. Forecasting Throughput and Inventory Requirements

Warehouse design requires at least two different forecasts:

• Throughput forecast: how much material or how many transactions pass through the facility during a period.
• Stock forecast: how much inventory is present and therefore requires storage capacity.

Throughput and stock are related but not interchangeable. A fast-moving cross-dock may have high throughput and low storage; a slow-moving spare-parts facility may have low throughput and high storage.

3.1 Time bases and peak factors

Let V_a be annual volume and D_o the number of operating days per year. Average daily volume is:

If the design peak is represented by peak factor p, then:

Here V_d and V_p have the same units, such as pallets/day or order lines/day. The peak factor must be based on a specified percentile or business event. A factor of 1.5 may represent a 95th-percentile day, a promotion, or a year-end surge; these are not equivalent assumptions.

For an activity lasting T hours within a working day, the average hourly rate is:

A design should distinguish average rate, peak sustained rate, and short-duration burst rate. Dock doors and sortation systems may be governed by short bursts, whereas labor staffing may be governed by a longer planning interval.

3.2 Inventory from demand and coverage

If daily demand is D, the required inventory for C days of coverage is:

This simple relationship assumes demand is expressed in units per day and that “coverage” is the intended inventory policy. When safety stock and pipeline stock are modeled separately, a more informative relationship is:

The components should not be added if one already includes another. For example, a days-of-supply measure may already include safety stock. The designer should state whether inventory is measured at average, expected maximum, or design-peak level.

3.3 Forecast uncertainty

A single-point forecast can produce false precision. Scenario planning is often more appropriate:

Where historical observations are available, variability can be summarized using the standard deviation. For observations x₁, x₂, …, x_n, the sample standard deviation is:

where x̄ is the sample mean and n is the number of observations. This statistic describes historical dispersion; it does not automatically determine safety stock. Service-level calculations additionally require assumptions about lead-time variability, demand distribution, replenishment policy, and acceptable stockout risk.

4. Capacity Modeling

Capacity is multidimensional. A warehouse can have adequate pallet positions but insufficient dock capacity, pick labor, staging space, battery-charging capacity, or information-system capacity. The design must identify the binding constraint rather than report one total capacity number.

4.1 Storage positions

If required inventory is I load units and the usable capacity target is u, where u is less than 1, the gross number of storage positions required is:

Because positions are discrete, the implemented requirement is normally rounded upward. The utilization allowance protects against inaccessible locations, uneven distribution, blocked positions, inventory imbalance, and operational variability. It is not simply empty space that can be freely consumed.

Illustrative calculation. A facility must hold 8,400 pallet loads at its design maximum. If planned storage utilization is 85%:

N = 8,400 / 0.85 = 9,882.35

Therefore, at least 9,883 pallet positions are required before considering special locations, damaged stock, quarantine, or segregation. If 3% additional positions are reserved for quarantine and exception stock, the requirement becomes approximately 10,180 positions, rounded upward.

4.2 Cubic and floor-space calculations

For products stored in cartons or bins, the basic cube requirement is:

where q_k is the quantity of SKU or load type k, v_k is its occupied volume, and C is occupied product volume. The result is not the building area. Rack geometry, clearances, beams, aisles, columns, sprinklers, fire separation, staging, offices, battery rooms, and access paths must also be considered.

If a storage module has footprint area A_m and contains L levels, the nominal storage area for N modules is:

This is valid only when modules are uniform and the footprint excludes or separately accounts for aisles and structural obstructions. A more practical area model is:

The terms must be calculated from a layout or a clearly defined area-factor method. Applying a generic percentage without understanding the operation can conceal major errors.

4.3 Staging capacity

Staging is often sized using the number of loads expected to accumulate during a defined window. If the peak arrival rate is r loads/hour and the staging window is t hours:

where S is the accumulation in loads, before adding safety or segregation allowances. If arrivals and departures are variable, the calculation should be tested against time-phased data or a queueing/simulation model. A staging area sized from daily totals can be seriously undersized when trucks arrive in concentrated waves.

4.4 Processing and labor capacity

If workload is W standard labor-hours per period and available productive labor per worker is H, the theoretical workforce is:

If η represents productive utilization, where η is between 0 and 1, then:

The productivity factor should account for breaks, travel, replenishment, equipment checks, meetings, indirect work, and normal delay. It should not be used to hide avoidable process waste. Standard times must be credible and periodically validated.

5. Space Allowances and Design Constraints

Space is consumed by more than inventory. A complete area schedule commonly includes:

• reserve and forward storage;
• receiving inspection and discrepancy handling;
• outbound staging by route, carrier, temperature, or service promise;
• packing and value-added services;
• returns, quarantine, damaged goods, and hazardous materials;
• aisles, intersections, pedestrian paths, and equipment turning envelopes;
• docks, dock offices, marshalling, and yard interfaces;
• battery charging, maintenance, waste, and utilities;
• offices, welfare, security, IT, and training;
• fire protection, emergency access, and legally required clearances; and
• expansion or reconfiguration zones.

5.1 Utilization is a design variable

High nominal utilization can reduce construction cost but increase travel, search, congestion, replenishment interruptions, and stock accessibility problems. Low utilization improves resilience but may raise fixed cost. The appropriate target depends on storage mode, SKU profile, replenishment frequency, and service promise. Selective pallet racking, block stacking, automated storage, and shelving have different practical utilization characteristics; one universal percentage is inappropriate.

5.2 Physical and regulatory constraints

The concept must respect building columns, slab load limits, ceiling height, sprinkler design, fire egress, accessibility, hazardous-material rules, food or pharmaceutical controls, and local planning requirements. Equipment clearances and pedestrian segregation should be determined from applicable standards, risk assessments, and manufacturer specifications—not improvised from a drawing. A design that fits geometrically but violates fire access or safe operating envelopes is not a valid design.

6. Flow Alternatives and Layout Logic

The central flow decision is not simply “straight” versus “U-shaped.” The designer should compare alternatives against product characteristics, volume, variability, labor, technology, and site constraints.

6.1 Common flow concepts

Straight-through flow places receiving and dispatch on opposite sides. It can reduce interference when inbound and outbound operations are distinct and the site supports two-sided access. It may, however, require more building frontage and can create long travel for shared resources.

U-flow places receiving and dispatch on the same side, with storage and processing inside the U. It can share docks, labor, and yard infrastructure and is often adaptable to constrained sites. It requires careful separation of inbound and outbound staging to prevent conflict.

Zone or department flow assigns areas to product families, temperature regimes, order profiles, or process steps. It can support specialization but may increase travel and make volume imbalance more difficult to manage.

Cross-dock flow transfers suitable goods from receiving to dispatch with little or no storage. It reduces storage requirements but requires synchronized appointments, reliable information, and sufficient order visibility.

Goods-to-person flow brings inventory to a workstation using conveyors, shuttles, or autonomous systems. It may reduce walking and improve ergonomics, but it introduces capital, maintenance, software, and exception-management requirements.

6.2 Evaluation criteria

Alternatives should be compared using a weighted decision model only after mandatory constraints have been screened. A conceptual score is:

where S_j is the score for alternative j, w_i is the weight of criterion i, and r_ij is the rating of alternative j on criterion i. Weights should sum to 1 if ratings are normalized. This method supports structured judgment; it does not replace feasibility analysis, cost estimation, risk assessment, or simulation.

Typical criteria include service performance, movement burden, peak resilience, safety, flexibility, implementation risk, capital cost, operating cost, scalability, energy use, and data requirements. Sensitivity analysis should test whether a small change in weights reverses the recommendation.

7. Growth, Uncertainty, and Real Flexibility

A warehouse should not be designed only for today’s average. Nor should every possible future be built into the initial facility. The practical objective is option value: preserving affordable choices that can be activated when demand becomes clearer.

7.1 Growth scenarios

If current volume is V₀ and annual growth is g, the deterministic volume after t years is:

This assumes a constant compound growth rate and should not be interpreted as a probability forecast. For example, with 100,000 annual cases, 6% annual growth, and a five-year horizon:

V₅ = 100,000(1.06)⁵ ≈ 133,823

The designer might provide full capacity for the base case, reserve a site for an extension, use modular racking, install scalable controls, or contract overflow capacity. Each option has different cost and risk.

7.2 Flexibility mechanisms

Useful mechanisms include adjustable rack beams, standardized storage modules, expansion-ready utilities, removable partitions, multi-purpose staging, software-configurable waves, cross-trained labor, and contractual overflow arrangements. Flexibility has value only if the change can be executed safely and economically. An empty area that cannot support fire protection, floor loading, or future access is not genuine expansion capacity.

8. Design Validation

Validation should occur at several levels.

8.1 Requirement validation

Confirm that every mandatory requirement has an owner, metric, source, and acceptance threshold. Resolve contradictions such as simultaneous requirements for maximum utilization and unrestricted accessibility.

8.2 Capacity validation

Test storage, docks, staging, labor, equipment, charging, packing, and systems under average, peak, and stress scenarios. Identify the bottleneck. Capacity should be evaluated as a time-dependent relationship, not just a static total.

8.3 Flow and congestion validation

A scaled block layout can identify obvious crossings, but dynamic analysis may be required for queueing, travel, and equipment interactions. Discrete-event simulation is appropriate when arrivals, processing times, routing, and queues vary materially over time. Simulation results are only as credible as their data, logic, and validation against observed operations.

8.4 Economic validation

Compare capital expenditure, labor, equipment, maintenance, energy, software, training, disruption, and residual value. A simple annualized comparison may be useful, but discounted cash-flow analysis is preferable for major investments. Benefits should be separated into capacity, labor productivity, service improvement, risk reduction, and avoided expansion.

8.5 Operational and human validation

Conduct walkthroughs with operators, supervisors, maintenance personnel, safety specialists, IT teams, and carriers. Review ergonomics, visibility, emergency access, pedestrian behavior, replenishment interruptions, exception handling, and cleaning. Worker participation is both a practical design resource and an ethical responsibility because operators experience risks that may not appear in aggregate calculations.

8.6 Data and technology governance

Warehouse management systems, location control, sensors, computer vision, robotics, and AI can improve forecasting, slotting, and task assignment. However, technology does not eliminate requirements analysis. AI-generated forecasts may reproduce biased or incomplete historical patterns; automated decisions require audit trails, access controls, cybersecurity, fallback procedures, and human accountability. Personal data from cameras or wearable devices should be collected proportionately, protected, and governed according to applicable privacy requirements.

Applied Case: Illustrative Omni-Channel Consumer Goods Warehouse

Background

The following is a fictional illustrative case. Meridian Home Products distributes packaged household goods through retail replenishment and direct-to-consumer orders. Its existing facility has 7,000 pallet positions, 1,200 square metres of staging and packing space, and a peak outbound requirement of 3,600 order lines per day. Growth in online demand has increased small-order picking, while retail customers continue to require pallet shipments.

Problem

The facility is experiencing congestion at the shared receiving and dispatch doors. Reserve storage is frequently above 90% occupied, replenishment interrupts picking, and outbound staging is filled before the final carrier wave. Management is considering either extending the current building or leasing a second facility.

Analysis

The design team establishes the following design-year requirements:

• design-maximum inventory: 8,400 pallets;
• planned pallet-position utilization: 85%;
• quarantine and exception allowance: 3% of the resulting positions;
• peak inbound: 28 pallets/hour for a two-hour appointment wave;
• peak outbound staging window: 35 pallets/hour for 1.5 hours;
• online picking: 4,500 order lines/day, with 8 productive picking hours;
• retail picking: 1,200 cases/day, with 8 productive hours.

Storage positions before exception allowance are:

8,400 / 0.85 = 9,882.35,

so 9,883 positions are required after upward rounding. Adding 3% gives:

9,883 × 1.03 = 10,179.49,

or 10,180 positions. The design therefore requires approximately 3,180 additional positions beyond the current 7,000.

Inbound staging for the two-hour wave is:

28 × 2 = 56 pallets.

Outbound staging for the specified window is:

35 × 1.5 = 52.5,

so at least 53 pallet-equivalents are required before segregation, safety, and carrier-specific allowances. Because the two flows are currently sharing space, the design team rejects a single undifferentiated staging pool.

Online picking averages:

4,500 / 8 = 562.5 order lines/hour,

while retail picking averages 150 cases/hour. These are not directly additive because they use different units and may require different methods and equipment. The team models them as separate workstreams, with shared labor only where training and congestion analysis support it.

Approach and solution

Three alternatives are screened:

1. Current-site extension with U-flow: adds rack capacity along the rear and creates physically separated inbound and outbound staging near shared dock infrastructure.
2. Second facility: separates retail pallet operations from online fulfillment but adds transport, inventory duplication, and management complexity.
3. High-density automation: provides additional storage in the current building but requires substantial capital and creates dependence on controls, maintenance, and system uptime.

The preferred concept is a phased current-site extension with U-flow and a dedicated forward-pick module. Reserve storage is expanded first; online picking receives a separate, ergonomically designed area; inbound quarantine is physically segregated; and outbound staging is divided by carrier wave. The site plan preserves a utility and access corridor for future automation rather than installing automation immediately.

Outcome

The concept meets the design-year storage requirement, separates the principal congestion sources, and retains a lower-cost expansion option. Before final approval, management requires a time-phased simulation using actual appointment and order-release data, a fire and egress review, an ergonomic assessment, and a pilot of the proposed online picking method.

Learning points

The case demonstrates that storage positions, order-line capacity, and staging space are separate design problems. It also shows why a flow alternative must be judged against implementation risk and future flexibility, not only nominal space efficiency. Finally, the calculations are screening estimates; final dimensions require a detailed layout, operational standards, and validated peak data.

Challenges and Limitations

Warehouse design calculations are sensitive to data quality. SKU dimensions may be outdated, inventory records may omit damaged stock, and “peak” may be defined inconsistently across departments. Forecasts may also fail when promotions, network redesign, supplier disruption, or channel substitution changes the demand pattern.

Static formulas do not capture queues and interaction effects. A dock may have adequate daily capacity but still fail when arrivals are synchronized. Similarly, a rack layout may have enough positions but produce excessive travel because popular SKUs are poorly located. These limitations justify time-phased analysis, sensitivity testing, simulation, and operational trials.

Optimization models also require caution. An objective that minimizes travel can increase risk if it places pedestrians and vehicles in conflict. An objective that maximizes utilization can reduce accessibility and resilience. Good design therefore uses multiple objectives and explicit constraints, with safety and regulatory requirements treated as non-negotiable.

Best-Practice Checklist

• Define measurable service, product, process, and growth requirements.
• Separate throughput units from inventory units.
• Use design peaks and time-phased profiles, not averages alone.
• State utilization, coverage, and exception assumptions explicitly.
• Calculate storage, staging, labor, equipment, and system capacity separately.
• Map information and exception flows as carefully as physical flows.
• Screen mandatory constraints before scoring alternatives.
• Preserve practical expansion and reconfiguration options.
• Validate concepts with operators, safety specialists, and maintenance personnel.
• Test the preferred design under base, high, and stress scenarios.
• Document data sources, assumptions, ownership, and change-control procedures.
• Treat technology and AI as governed enablers, not substitutes for sound process design.

Chapter Summary

Warehouse design is an iterative systems methodology that begins with measurable requirements and proceeds through process mapping, demand and inventory analysis, capacity modeling, flow alternatives, and validation. Throughput and storage are different dimensions: a facility may process many units while holding little stock, or hold extensive stock while processing few transactions. Correct design therefore requires consistent units, explicit time bases, peak factors, utilization allowances, and clearly defined inventory components.

Capacity must be assessed across storage positions, staging, docks, labor, equipment, information systems, and support areas. Space allowances include aisles, safety clearances, exceptions, utilities, and future flexibility, not merely product cube. Straight-through, U-flow, zoned, cross-dock, and goods-to-person concepts each offer advantages and trade-offs. Growth should be addressed through scenarios and real options rather than unsupported precision.

A valid design satisfies mandatory safety and regulatory constraints, performs under expected and stressed conditions, remains economically defensible, and is understood by the people who operate it. Simulation, pilots, sensitivity analysis, and governance controls strengthen confidence, but they do not remove the need for accurate data and managerial judgment.

Key Terms

Requirement specification: A measurable statement of what the warehouse must achieve.

Throughput: Quantity or transactions processed through a warehouse during a period.

Inventory capacity: Quantity of stock that can be held under defined operating conditions.

Peak factor: Ratio used to convert an average rate into a specified design-peak rate.

Design maximum: Inventory or workload level selected for capacity planning.

Utilization allowance: Capacity margin that prevents operation at complete physical saturation.

Storage position: Defined location for a pallet, carton, tote, bin, or other load unit.

Staging: Temporary accumulation of goods before or after a process.

Process map: Representation of activities, decisions, resources, information, and flows.

From–to chart: Matrix showing movement quantities between activities or locations.

Movement burden: Quantity of movement multiplied by the distance traveled.

Forward picking: Accessible picking stock positioned near the order-fulfillment process.

Reserve storage: Bulk inventory held for replenishment of forward locations.

Cross-docking: Transfer from receiving to dispatch with little or no storage.

U-flow: Layout concept in which receiving and dispatch are located on the same side.

Goods-to-person: Method in which equipment brings inventory to a stationary operator.

Scenario analysis: Evaluation of a design under alternative demand or operating assumptions.

Bottleneck: Resource or process constraint limiting system performance.

Discrete-event simulation: Modeling method representing time-ordered events and queues.

Design validation: Evidence-based confirmation that a concept meets its requirements.

Review Questions

5 Short Answer Questions

1. Why must throughput capacity be distinguished from storage capacity?
2. What information should be recorded for each activity in a warehouse process map?
3. Explain the purpose of a utilization allowance in storage-position calculations.
4. Identify two reasons why staging space cannot be sized reliably from daily totals alone.
5. What is meant by real flexibility in warehouse design?

5 Long Answer Questions

1. Explain a complete warehouse design methodology from requirements definition through final validation.
2. Compare straight-through and U-flow layouts, including their operational advantages and limitations.
3. Discuss how demand uncertainty, seasonality, and growth should influence capacity decisions.
4. Explain why warehouse space planning must include support, exception, safety, and future areas in addition to storage.
5. Evaluate the appropriate uses and limitations of weighted decision models and discrete-event simulation in layout selection.

3 Analytical / Application Questions

1. A warehouse must hold 12,000 pallet loads at a planned utilization of 80%. Calculate the minimum number of pallet positions before any quarantine allowance. Then explain what additional information is required before finalizing the rack design.
2. A facility receives 24 pallets per hour during a 2.5-hour inbound wave and dispatches 30 pallets per hour during a 2-hour outbound wave. Calculate the basic accumulation requirement for each flow and propose two design controls that would prevent inbound and outbound congestion.
3. A company forecasts 8% annual growth for four years from a current volume of 75,000 cases per year. Calculate the deterministic fourth-year volume and critically assess why management should also test a high-growth and disruption scenario.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes warehouse throughput from storage capacity?

A. Throughput measures stock held, while storage capacity measures orders processed.

B. Throughput measures activity over time, while storage capacity measures inventory that can be held.

C. Throughput and storage capacity are interchangeable when measured in pallets.

D. Throughput applies only to receiving, while storage capacity applies only to picking.

Correct Answer: B. Throughput measures activity over time, while storage capacity measures inventory that can be held.

Question 2

A warehouse has design-maximum inventory of 8,400 pallets and plans to operate at 85% utilization. Approximately how many pallet positions are required before other allowances?

A. 7,140

B. 8,400

C. 9,883

D. 10,500

Correct Answer: C. 9,883

Question 3

What is the primary purpose of a peak factor?

A. To convert a design rate into an annual average

B. To convert an average rate into a specified design-peak rate

C. To remove all demand variability from a forecast

D. To calculate building height from inventory volume

Correct Answer: B. To convert an average rate into a specified design-peak rate

Question 4

Which item is most appropriately treated as a separate warehouse capacity dimension rather than as storage capacity?

A. Pallet positions

B. Reserve inventory

C. Dock processing rate

D. Load-unit quantity

Correct Answer: C. Dock processing rate

Question 5

A staging area receives 28 pallets per hour during a two-hour wave. Ignoring additional allowances, what accumulation should be planned?

A. 14 pallets

B. 30 pallets

C. 56 pallets

D. 84 pallets

Correct Answer: C. 56 pallets

Question 6

What does a from–to chart primarily represent?

A. The legal ownership of inventory

B. Movement quantities between activities or locations

C. The depreciation schedule for equipment

D. The probability distribution of annual demand

Correct Answer: B. Movement quantities between activities or locations

Question 7

Which statement about a weighted decision model is correct?

A. It replaces all feasibility and safety analysis.

B. It is valid only when all alternatives have identical costs.

C. It structures judgments across criteria but should be supported by feasibility and risk analysis.

D. It guarantees the alternative with the lowest travel distance is optimal.

Correct Answer: C. It structures judgments across criteria but should be supported by feasibility and risk analysis.

Question 8

Online picking demand is 4,500 order lines over 8 productive hours. What is the average required rate?

A. 360 order lines/hour

B. 562.5 order lines/hour

C. 1,125 order lines/hour

D. 4,508 order lines/hour

Correct Answer: B. 562.5 order lines/hour

Question 9

Which is an example of genuine expansion flexibility?

A. An empty area with no floor-load or fire-protection provision

B. A blocked aisle reserved informally for future use

C. Expansion-ready utilities and access for a future modular extension

D. Operating all storage locations at 100% utilization

Correct Answer: C. Expansion-ready utilities and access for a future modular extension

Question 10

Why should AI-supported warehouse planning be governed with audit trails and human accountability?

A. AI eliminates the need for operational data.

B. AI outputs may reflect incomplete data and can affect safety, privacy, or resource decisions.

C. AI can guarantee that forecasts are unbiased.

D. Governance is needed only when no warehouse management system exists.

Correct Answer: B. AI outputs may reflect incomplete data and can affect safety, privacy, or resource decisions.