Integrated Warehouse Design and Future Developments

Introduction

Warehouse design is not the isolated arrangement of racks, aisles, docks, and offices. It is an integrated socio-technical decision linking customer demand, inventory policy, material flow, information systems, labor, capital, safety, resilience, and environmental performance. A warehouse may have excellent storage density yet fail because replenishment is slow; it may deploy advanced robots yet produce poor economics because order profiles are unsuitable; or it may achieve high throughput while creating unacceptable safety and workforce risks.

This chapter presents a case-based method for developing a complete warehouse design proposal. The method begins with profiling demand and inventory, translates the profile into capacity and flow requirements, develops a layout and operating model, selects systems and technology, estimates staffing and economics, and concludes with risk and implementation planning. The chapter then critically assesses micro-fulfillment, autonomous warehouses, flexible automation, smart facilities, and future workforce requirements.

The central principle is fit before sophistication: technology should solve a defined operational problem and should be evaluated against service, cost, resilience, safety, sustainability, and organizational capability.

Learning Objectives

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

1. Construct an integrated warehouse design proposal from demand and product-profile data.
2. Estimate capacity, space, throughput, labor, and financial requirements using appropriate assumptions.
3. Connect layout, material-handling systems, warehouse-management systems, staffing, and governance.
4. Evaluate micro-fulfillment, autonomous, flexible, and smart-warehouse concepts critically.
5. Develop a phased implementation plan with measurable benefits and controlled risk.
6. Assess ethical, regulatory, workforce, cybersecurity, and sustainability implications.

1. The Integrated Design Logic

A warehouse design is best treated as a closed decision system. Customer requirements determine order profiles and service promises. Order profiles determine activity patterns, which determine storage, picking, packing, dispatch, and replenishment requirements. Those requirements constrain layout and equipment. The selected operating model determines information-system functionality and labor competencies. Finally, economics and risk determine whether the proposal is viable.

A useful design sequence is:

Profile → forecast → size → flow → configure → automate selectively → validate economically → implement → learn.

The sequence is iterative rather than strictly linear. For example, a proposed automated storage and retrieval system (AS/RS) may increase storage density but impose container dimensions, barcode quality, maintenance requirements, and peak-throughput constraints. These effects may require changes to packaging, inventory policy, or the building itself.

1.1 Design boundaries and decision levels

Warehouse decisions occur at three levels:

• Strategic: location, building scale, network role, degree of automation, ownership, and target service proposition.
• Tactical: slotting rules, replenishment policy, shift patterns, storage modes, labor standards, and technology architecture.
• Operational: release rules, task assignment, exception handling, cycle counting, maintenance, and daily control.

A design is incomplete if it addresses only the physical facility. The warehouse is a node in a network, and upstream packaging, supplier reliability, transport schedules, returns, and customer order behavior all affect its performance.

1.2 Stakeholder requirements

Design requirements should be elicited from customers, operations, transport, procurement, information technology, finance, human resources, maintenance, safety, legal, and sustainability specialists. Requirements should be classified as:

• mandatory constraints, such as fire separation or food-safety rules;
• service requirements, such as order cut-off and dispatch time;
• performance targets, such as lines picked per labor hour;
• preferences, such as future expandability; and
• assumptions requiring validation.

This classification prevents an attractive but untested preference from being treated as a technical necessity.

2. Profiling Demand, Inventory, and Activity

The design begins with a time-phased profile rather than an annual average. At minimum, analysts should examine SKU dimensions and weight, inventory levels, receipts, order lines, units per line, order frequency, seasonality, returns, value, hazard class, temperature requirements, and handling restrictions.

2.1 ABC and demand variability

ABC analysis ranks items by annual usage value, commonly calculated as:

where D_i is annual demand for item i in units per year and c_i is unit cost in currency per unit. ABC classes are managerial categories, not universal laws. A high-value item may be low velocity, while a low-value item may drive most picking work. Therefore, ABC should be combined with velocity, cube, order affinity, criticality, and variability.

Demand variability can be summarized with the coefficient of variation:

where σ_D is the standard deviation of demand over the selected periods and μ_D is mean demand. The measure is dimensionless and is meaningful when the mean is positive. It should not be interpreted as a forecast-error measure unless the data specifically represent forecast errors.

A practical profiling matrix may classify SKUs as:

2.2 Order and flow profiling

The designer should distinguish pallets, cases, inner packs, eaches, and returns. A warehouse receiving 300 pallets daily but shipping 15,000 each-pick order lines has a different design from one shipping 300 full pallets. Important measures include receipts per day, put-away tasks, replenishment tasks, order lines, units, cartons, pallets, dispatch waves, and peak-hour rates.

The peak should not automatically equal the maximum historical observation. A defensible design peak may be based on a forecast percentile, a contractual volume, or a scenario combining demand growth and promotional activity. The assumption must be explicit because excessive peak sizing creates idle capital, while under-sizing creates chronic overtime and service failure.

3. Capacity and Space Design

Capacity is multidimensional. A facility can have sufficient pallet positions but insufficient dock doors, pick faces, staging space, labor, or dispatch capacity. Capacity analysis must therefore test storage, flow, and time simultaneously.

3.1 Storage capacity

For a stock-keeping unit with average inventory I_avg and a required safety factor s, a simple planning requirement is:

Here, s is dimensionless. This is a planning approximation, not a substitute for a service-level inventory model. If cycle stock, safety stock, pipeline stock, and promotional stock are known separately, they should be modeled separately rather than hidden in a single factor.

For pallet storage:

where P_design is design pallet inventory, u is usable pallets per selected storage module or location, and the ceiling function rounds upward. The result must then be adjusted for segregation, damaged stock, blocked locations, fire clearances, and reserve capacity.

Space is not equal to storage-location area. A total-area estimate should include storage, forward picking, receiving, shipping, staging, value-added services, returns, battery charging, offices, maintenance, welfare, circulation, and safety clearances. A commonly useful measure is cube utilization:

The ratio is dimensionless. High cube utilization is not always desirable: excessive fullness can obstruct access, increase travel, and reduce resilience.

3.2 Throughput and bottlenecks

For an activity with required volume V over a planning period of length T, the average rate is:

Designers must also estimate peak rate q_peak, which may be hourly or shorter. A process with adequate daily capacity can still fail at the cut-off hour. Capacity should be tested for receiving, put-away, replenishment, picking, packing, sortation, and dispatch separately.

If effective resource capacity is C_eff tasks per hour and required peak workload is q_peak, a basic resource requirement is:

The estimate assumes tasks are sufficiently interchangeable and that C_eff already reflects breaks, travel, congestion, equipment availability, and expected utilization. If it does not, the calculation is optimistic.

3.3 Worked capacity example

An illustrative e-commerce operation expects 8,400 order lines during a 10-hour operating day. Its design peak is 1,200 lines per hour. A picker can complete 75 lines per productive hour, but planned availability is 85 percent because of breaks, travel, meetings, and minor interruptions. Effective capacity is therefore:

C_eff = 75 × 0.85 = 63.75 lines per labor-hour.

The peak picker requirement is:

R = ⌈1,200 ÷ 63.75⌉ = ⌈18.82⌉ = 19 pickers.

The daily workload alone would suggest 8,400 ÷ 63.75 = 131.76 labor-hours, but peak timing requires 19 concurrent pickers. The difference demonstrates why daily averages cannot size a time-critical operation. Supervisors, replenishment labor, equipment downtime, and congestion must be added separately or modeled through simulation.

4. Layout and Operating-Flow Design

A good layout minimizes unnecessary touches while preserving safety, visibility, adaptability, and control. The preferred flow depends on product and process. A U-shaped flow can place receiving and shipping on the same building face and share resources; a through-flow layout can separate inbound and outbound traffic and suit high-volume operations; a modular layout can support future expansion.

4.1 Functional zones

A comprehensive design normally considers:

1. inbound vehicle reception and check-in;
2. unloading and receiving inspection;
3. quarantine or quality-hold space;
4. reserve storage;
5. forward pick storage;
6. replenishment and consolidation;
7. picking zones;
8. packing and value-added services;
9. sortation and dispatch staging;
10. returns assessment and disposition;
11. maintenance, charging, offices, welfare, and secure areas.

Adjacency should reflect flow intensity and risk. High-frequency paths should be short, but hazardous materials, pedestrians, powered industrial trucks, food, pharmaceuticals, and customer returns may require separation. The shortest path is not automatically the safest or most controllable path.

4.2 Slotting and travel

Slotting assigns items to locations. A robust policy may combine pick frequency, cube, weight, affinity, replenishment frequency, ergonomic limits, and service criticality. Heavy items should generally be stored at safer heights; frequently co-ordered items may be placed near one another, provided congestion does not result.

Travel distance is only one component of picking time. A more realistic task-time model is:

Each term represents time per task, normally in seconds or minutes. The model is useful for labor standards and comparative design, but its parameters must be measured or validated; it should not be treated as a universal law.

5. Systems Architecture and Data Governance

The warehouse-management system (WMS) should control location, inventory status, task creation, allocation, replenishment, cycle counting, exceptions, and performance reporting. An enterprise-resource-planning system may own financial and order information, while a warehouse-control system (WCS) or warehouse-execution system (WES) may coordinate automation. Transport systems, labor-management tools, robotics fleets, scanners, sensors, and customer platforms must exchange reliable data.

A sound architecture defines:

• system ownership for each master-data object;
• interfaces and message timing;
• item, location, container, order, and employee identifiers;
• error handling and reconciliation;
• role-based access;
• audit trails and retention;
• cybersecurity monitoring and recovery procedures.

Automation magnifies bad data. Incorrect dimensions can cause cartonization failure; inaccurate inventory can stop a robot from finding stock; poor location master data can create unsafe task instructions. Data governance is therefore an operational control, not merely an information-technology issue.

6. Staffing, Work Design, and Performance

Staffing should be derived from workload by process and time period, not from a single warehouse-wide ratio. The plan should include direct labor, supervisors, planners, inventory controllers, maintenance technicians, systems support, safety personnel, and temporary or cross-trained capacity.

Work design must address ergonomics, fatigue, training, job rotation, accessibility, and meaningful opportunities for worker feedback. Performance measures should balance speed with quality and safety. Useful measures include:

• order accuracy and inventory accuracy;
• dock-to-stock time;
• lines or units per labor hour;
• on-time dispatch;
• replenishment response time;
• damage, injury, and near-miss rates;
• equipment availability;
• energy per order or per handled unit;
• return disposition time.

A narrow productivity target can create unsafe behavior, hidden quality defects, or employee turnover. Incentive systems should therefore use a balanced scorecard and include minimum safety and quality gates.

7. Technology Choices: From Mechanization to Autonomy

Technology selection should follow a problem statement, baseline measurement, and total-cost analysis. Technologies may be grouped as follows:

7.1 Micro-fulfillment

Micro-fulfillment centers are compact, often urban facilities designed to shorten last-mile distance and accelerate online order fulfillment. They can use vertical storage, shuttle systems, AMRs, or human-led picking. Their value is greatest where delivery speed, urban proximity, and high online demand offset expensive real estate and smaller assortment capacity.

They are not automatically superior to a regional warehouse. Constraints include limited storage range, replenishment complexity, local labor cost, fire and building restrictions, difficult reverse logistics, and dependence on accurate demand forecasts. A network study should compare transport savings, facility costs, inventory duplication, service benefits, and failure resilience.

7.2 Autonomous warehouses

An autonomous warehouse combines automated movement, sensing, software orchestration, and limited routine human intervention. Full autonomy is rare in heterogeneous, exception-rich environments. Most practical systems are selectively autonomous: machines handle predictable transport or storage while people manage exceptions, replenishment, maintenance, quality, and decisions.

Autonomy introduces new failure modes: fleet deadlock, sensor occlusion, software defects, communications loss, cyberattack, and opaque algorithmic decisions. The design must include manual bypasses, safe shutdown, recovery procedures, redundant critical data, and clear accountability.

7.3 Flexible automation

Flexible automation emphasizes modular equipment, movable robots, standard interfaces, and software-configurable processes. It is particularly valuable where product mix and demand change rapidly. Flexibility, however, may trade off against peak efficiency, and modular equipment still requires integration, charging, maintenance, training, and governance. The correct comparison is not “manual versus robot” but alternative operating systems over their expected life.

7.4 Smart facilities and AI

A smart facility uses sensors, event data, analytics, and control systems to improve visibility and decision-making. Examples include predictive maintenance from vibration and motor data, dynamic slotting, congestion detection, energy management, and exception prioritization.

AI should support accountable decisions rather than replace judgment indiscriminately. Models require representative data, monitoring for drift, documented performance thresholds, human override, and privacy controls. Worker monitoring requires purpose limitation, transparency, proportionality, and compliance with applicable employment and data-protection law.

8. Economics and Investment Appraisal

Economic appraisal should include capital expenditure, implementation cost, operating cost, maintenance, software subscriptions, training, energy, downtime, residual value, and benefits. Benefits may include labor avoidance, increased capacity, reduced damage, lower transport cost, improved service, and inventory reduction. Some benefits are difficult to monetize and should be presented explicitly rather than overstated.

For a project with initial investment I₀, annual net cash flows CF_t, discount rate r, and terminal value TV_n, net present value is:

The formula assumes cash flows occur at the end of each period, the discount rate is appropriate to the risk and currency, and cash flows are stated consistently as nominal or real values. A positive NPV indicates value creation relative to the chosen discount rate, not certainty of success.

Payback is useful for liquidity discussion but ignores benefits after recovery and the time value of money. Sensitivity analysis should vary volume, labor cost, service benefit, equipment availability, implementation delay, and useful life. Scenario analysis is especially important for seasonal and technology-intensive facilities.

9. Illustrative Integrated Case: Northstar Home Delivery

Background

The following is a fictional illustrative case. Northstar Home Delivery distributes household goods and personal-care products to retail stores and direct-to-consumer customers. Its existing 18,000-square-meter facility has 12,000 active SKUs, 1,600 pallet positions, and a largely manual pick-pack process. Online orders have grown rapidly, but the building has not been redesigned.

Problem

Northstar experiences 96 percent inventory accuracy, 91 percent on-time dispatch, frequent replenishment interruptions, and congestion near packing. Peak-season overtime is high. Management initially proposes a fully autonomous goods-to-person system, but the proposal lacks a profile, business case, workforce plan, or resilience design.

Analysis

The design team collects 12 months of order-line data, dimensions, weights, inventory records, returns, and hourly dispatch history. The analysis identifies:

• 18 percent of SKUs generate 72 percent of order lines;
• 9 percent are bulky or ergonomically difficult;
• 14 percent are seasonal;
• direct-to-consumer orders are small and multi-line;
• store replenishment is predominantly case and pallet based;
• returns peak after promotional events;
• the highest dispatch hour is 2.4 times the daily hourly average.

The team separates store and e-commerce flows rather than forcing both through one pick path. Fast e-commerce items receive a goods-to-person forward area; long-tail items remain in selective shelving and reserve storage. Case-pick lanes serve retail replenishment. A dedicated returns cell prevents reverse logistics from disrupting outbound packing.

Proposed operating design

The proposed layout uses a controlled U-flow. Inbound docks, inspection, and reserve storage occupy one side; forward picking and packing sit centrally; outbound staging and dispatch occupy the opposite side. Pedestrian routes are separated from powered equipment at crossings. A modular AMR system transports totes between goods-to-person stations and packing, while pallet movement remains forklift-based because the pallet profile is stable and existing equipment is cost-effective.

The WMS remains the inventory and order authority. A WES coordinates AMR work and packing release. Standardized tote dimensions, barcode rules, and location identifiers are introduced before automation commissioning. The design includes manual picking fallback for a minimum operating level during system outages.

Capacity and staffing proposal

Northstar sizes e-commerce picking at a design peak of 1,500 lines per hour. Measured manual productivity is 70 lines per productive hour, with 88 percent planned availability, giving:

C_eff = 70 × 0.88 = 61.6 lines per labor-hour.

A fully manual peak would require:

⌈1,500 ÷ 61.6⌉ = ⌈24.35⌉ = 25 pickers.

The proposed goods-to-person stations are designed to process 1,000 lines per hour collectively, while a retained manual zone handles the balance and exceptions. If manual capacity remains 61.6 lines per labor-hour, approximately:

⌈(1,500 − 1,000) ÷ 61.6⌉ = ⌈8.12⌉ = 9 manual pickers are required at peak, excluding station operators, replenishment, packing, supervision, and maintenance. This is a design estimate, not a guaranteed labor saving: the automated system creates new work in tote replenishment, exception handling, software support, and maintenance.

Economics and governance

The business case includes equipment, integration, building modifications, training, software, maintenance, energy, and temporary dual-running costs. Benefits include avoided peak labor, improved dispatch reliability, reduced travel, and fewer picking errors. The appraisal is tested under base, high-growth, and delayed-implementation scenarios. Approval is conditional on successful pilot performance, not solely on the projected NPV.

A governance board comprising operations, IT, finance, safety, HR, and worker representatives approves design changes. It monitors service, safety, quality, worker experience, system availability, and financial performance. Algorithmic task assignment is audited for unfair workload concentration, and workers receive training for new technical roles.

Implementation

The project uses five gates:

1. Discovery: validate profile, data, constraints, and baseline measures.
2. Concept design: compare manual, mechanized, and automated alternatives.
3. Pilot: test representative SKUs, peaks, exceptions, and recovery procedures.
4. Build and commission: install in controlled stages with integration testing.
5. Ramp and stabilize: run parallel processes, monitor benefits, and optimize.

A cutover plan protects peak season by prohibiting major migration during the most consequential demand period. The facility retains emergency procedures, spare critical components, manual documents, and tested data-recovery arrangements.

Outcome and learning points

In the illustrative outcome, the hybrid design improves peak dispatch reliability without committing every process to automation. The principal lesson is not that AMRs are universally best. It is that the design matches technology to flow: automation supports variable tote movement, while stable pallet work remains comparatively simple. The case also shows that implementation readiness, data quality, workforce transition, and fallback capability are part of design—not post-project details.

10. Risk, Resilience, and Sustainability

Warehouse risk should be assessed across physical, process, digital, human, and network dimensions. A risk register should identify the hazard, cause, consequence, likelihood, severity, existing controls, owner, trigger, and response. High-consequence risks require more than probability ranking; a rare fire, cyberattack, or unsafe autonomous interaction may justify substantial preventive investment.

Resilience measures include diversified suppliers, spare parts, alternate carriers, backup power where justified, offline operating procedures, redundant communications, emergency staffing, inventory visibility, and recovery exercises. Recovery-time and recovery-point objectives should be defined for critical systems.

Sustainability includes building energy, lighting, heating and cooling, equipment charging, packaging, travel, waste, water, and asset life. Measures should be normalized—for example, energy per order—while recognizing that measurement boundaries affect conclusions. Automation that reduces travel may increase embodied carbon and electronic waste. A credible assessment considers the whole life cycle rather than one favorable operating metric.

Safety governance must comply with applicable occupational safety, fire, accessibility, machinery, electrical, environmental, dangerous-goods, food, pharmaceutical, and data-protection requirements. Regulatory compliance is a minimum condition; risk assessment must also address foreseeable misuse and interactions between humans and machines.

11. Implementation and Continuous Improvement

Implementation is a change program as much as an engineering program. Readiness should be tested in process, people, technology, data, facility, supplier, and governance dimensions. Commissioning should include normal flow, peak flow, partial equipment failure, bad labels, short picks, inventory discrepancies, network interruption, emergency stop, and manual recovery.

After go-live, a control-room rhythm should review service, constraints, exceptions, safety, and benefits. Process mining and digital-twin analysis can reveal actual flow, but analytical outputs must be interpreted by people familiar with operational context. Continuous improvement should use structured experimentation: establish a baseline, change one controllable factor where possible, measure results, and verify that local improvement does not damage the wider system.

12. Future Workforce Requirements

Future warehouses will need fewer purely repetitive roles in some processes, but they will not become people-free. Demand will grow for mechatronics technicians, automation supervisors, data analysts, WMS/WES specialists, cybersecurity practitioners, reliability engineers, process-improvement leaders, safety professionals, and ethically competent managers.

Workforce planning should distinguish substitution from augmentation. A robot may reduce walking while increasing monitoring and exception work. Reskilling pathways, paid training, transparent progression, and participation in system design improve adoption and operational knowledge. Ethical design rejects the assumption that every worker must simply adapt to opaque surveillance or unrealistic algorithmic targets.

Challenges and Limitations

Integrated design models remain dependent on data quality and assumptions. Forecasts can be wrong, peak behavior can change after a system is installed, and measured productivity may not transfer between layouts. Simulation models may omit human adaptation, maintenance realities, or rare failures. Financial models can overstate benefits by ignoring transition costs, software dependence, and organizational capability. Technology vendors may define performance under ideal conditions.

Accordingly, advanced design proposals should report uncertainty, use sensitivity and scenario analysis, validate through pilots, and specify stop-or-redesign criteria. The best proposal is not the one with the most automation; it is the one that remains safe, serviceable, economically defensible, and adaptable when conditions differ from plan.

Chapter Summary

Integrated warehouse design connects demand and inventory profiling with capacity, flow, layout, systems, labor, economics, technology, risk, and implementation. ABC analysis should be complemented by velocity, cube, variability, affinity, and handling requirements. Capacity must be tested across storage, throughput, time, labor, staging, and bottlenecks rather than reduced to pallet positions.

Layout decisions should minimize unnecessary movement while protecting safety, flexibility, segregation, and control. WMS, WES, automation, data standards, cybersecurity, and recovery procedures form one operating architecture. Micro-fulfillment is valuable when proximity and speed justify network duplication; autonomous and flexible systems are powerful but introduce integration, maintenance, cyber, and workforce challenges. Smart facilities and AI require governance, human oversight, privacy protection, and model monitoring.

A credible proposal includes life-cycle economics, sensitivity analysis, resilience, sustainability, ethical workforce planning, and phased implementation. The Northstar case demonstrates the value of selective hybrid automation and the importance of fitting technology to actual flow and organizational capability.

Key Terms

ABC analysis: Classification of items by annual usage value or another chosen importance measure.

AMR: Autonomous mobile robot that navigates and transports materials, usually under fleet software control.

Capacity profile: Time-based description of storage, labor, equipment, and process capability.

Coefficient of variation: Standard deviation divided by mean, used to describe relative variability.

Cube utilization: Occupied storage volume divided by available storage volume.

Digital twin: A data-connected model used to represent, analyze, or simulate a physical operation.

Forward pick area: Accessible storage positioned for frequent order picking.

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

Micro-fulfillment: Compact fulfillment facility located close to demand, often in an urban area.

NPV: Present value of project cash flows less initial investment.

Peak rate: Maximum or design activity rate over a specified time interval.

Resilience: Ability to prepare for, withstand, recover from, and adapt to disruption.

Slotting: Assignment of products to storage and picking locations.

WCS: Warehouse-control system coordinating automated equipment.

WES: Warehouse-execution system coordinating order release and dynamic work execution.

WMS: Warehouse-management system controlling inventory, locations, tasks, and transactions.

Flexible automation: Automation designed for reconfiguration as products, volumes, or processes change.

Smart facility: Facility using connected sensing, data, analytics, and control to improve operations.

Review Questions

Short Answer Questions

1. Why is average daily volume insufficient for sizing a warehouse process?
2. Distinguish reserve storage from forward pick storage.
3. What is the purpose of a WES in relation to a WMS and automated equipment?
4. State two limitations of micro-fulfillment centers.
5. Why should worker safety and quality be included in productivity governance?

Long Answer Questions

1. Explain how demand profiling should influence storage mode, slotting, layout, and labor planning.
2. Critically evaluate the claim that autonomous warehouses eliminate the need for warehouse labor.
3. Describe an integrated economic appraisal for a proposed warehouse automation project.
4. Explain how data governance and cybersecurity affect warehouse operating performance.
5. Develop a phased implementation framework for a redesigned warehouse, including commissioning and fallback controls.

Analytical / Application Questions

1. A facility must process 1,800 peak lines per hour. Each picker completes 80 lines per productive hour, and planned availability is 75 percent. Calculate the minimum concurrent picker requirement and state two additional labor categories that must be considered.
2. Compare a regional automated fulfillment center with three urban micro-fulfillment centers for a same-day delivery network. Identify the cost, service, inventory, resilience, and sustainability variables that should be modeled.
3. Design a hybrid operating concept for a warehouse with stable pallet demand, highly variable each-pick demand, frequent returns, and a shortage of skilled technicians. Justify the technology, layout, workforce, risk, and implementation choices.

Multiple Choice Questions with Answers

Question 1

Which sequence best represents the integrated warehouse design logic presented in the chapter?

A. Automate → hire → forecast → measure → locate

B. Profile → forecast → size → flow → configure → validate → implement

C. Locate → purchase equipment → forecast → profile → train

D. Measure profit → automate all processes → redesign the building

Correct Answer: B. Profile → forecast → size → flow → configure → validate → implement

Question 2

Annual usage value for an SKU is calculated as:

A. Annual demand ÷ unit cost

B. Average inventory × order frequency

C. Annual demand × unit cost

D. Unit cost ÷ annual demand

Correct Answer: C. Annual demand × unit cost

Question 3

A process requires 1,200 lines per hour. Each picker completes 75 lines per productive hour and planned availability is 85%. What is the minimum peak picker requirement?

A. 16

B. 18

C. 19

D. 21

Correct Answer: C. 19

Question 4

Which statement most accurately describes cube utilization?

A. Occupied storage volume divided by available storage volume

B. Annual units shipped divided by building area

C. Labor hours divided by storage locations

D. Available volume divided by occupied volume

Correct Answer: A. Occupied storage volume divided by available storage volume

Question 5

What is a principal advantage of micro-fulfillment?

A. It always provides the lowest inventory cost

B. It eliminates reverse logistics

C. It places fulfillment capacity close to urban demand

D. It removes the need for demand forecasting

Correct Answer: C. It places fulfillment capacity close to urban demand

Question 6

Why is selective autonomy often more practical than full autonomy?

A. People are unnecessary only in stable processes

B. Exceptions, maintenance, and judgment remain important in heterogeneous operations

C. Autonomous systems cannot move any inventory

D. Selective autonomy requires no software integration

Correct Answer: B. Exceptions, maintenance, and judgment remain important in heterogeneous operations

Question 7

Which system normally controls inventory status, locations, and warehouse transactions?

A. WMS

B. HVAC controller

C. Payroll system

D. Building lease system

Correct Answer: A. WMS

Question 8

In the chapter’s task-time model, which item is not one of the listed components?

A. Travel time

B. Search time

C. Handling time

D. Corporate tax rate

Correct Answer: D. Corporate tax rate

Question 9

What does a positive NPV generally indicate, assuming a consistent and appropriate discount rate?

A. The project is risk-free

B. The project creates value relative to the discount rate

C. The project has no implementation cost

D. The payback period is exactly one year

Correct Answer: B. The project creates value relative to the discount rate

Question 10

Which is an appropriate governance control for AI-based warehouse task assignment?

A. Remove all human overrides

B. Avoid monitoring model performance after deployment

C. Use documented thresholds, monitoring, and accountable human oversight

D. Permit unrestricted collection of worker data

Correct Answer: C. Use documented thresholds, monitoring, and accountable human oversight