8 Supply Chain Network Design and Integration

Network structure and design decisions

A supply chain network connects suppliers to customers through facilities and the flows between them. Its design establishes both the physical structure of the network and the operating logic that determines how products, materials, inventory, and information move.

Interdependent network choices

Network design brings together several interdependent choices:

• Facility location and number: Which plants, distribution centers, or other facilities to use, and where to place them.

• Facility role: What each site makes, stores, postpones, or ships, and which products or markets it serves.

• Capacity: How much each site can produce, handle, or store, including whether to expand, contract, or reserve flexible capacity.

• Sourcing: Which suppliers provide which materials, and whether supply is concentrated or diversified.

• Flow and assignment: Which suppliers feed which plants, which plants serve which distribution centers, and which facilities serve each market.

• Inventory and transportation: Where inventory is held, how much is buffered at each point, and which modes, routes, and shipment frequencies connect the network.

These choices should be assessed together rather than optimized as isolated departmental decisions. For example, adding a warehouse may shorten delivery distances while increasing facility expenses and dividing inventory among more locations.

Capacity and resilience

Capacity is the maximum output or throughput that a resource can support over a defined period. Planners compare expected demand with available capacity at suppliers, production lines, storage areas, labor, and transportation links. A network can have ample total capacity and still fail to meet demand if that capacity is in the wrong place, serves the wrong products, or cannot be reached quickly enough.

Capacity planning considers whether to build permanent capacity, use overtime or temporary labor, outsource production, or retain flexible capacity for demand peaks. More capacity can improve responsiveness and protect against disruption, but usually raises investment or operating costs. Running every asset near its maximum may lower unit cost in steady conditions, but leaves little room to recover from demand surges, downtime, or delayed supplies.

Flow planning and feasibility

Flow decisions assign quantities and paths through the network. A basic planning model might minimize total relevant cost, including facility and production costs, purchasing costs, inventory costs, transportation costs, and shortage or service penalties.

The plan must also satisfy constraints such as:

• Supply and production limits.

• Facility storage and handling capacity.

• Customer demand requirements.

• Product-compatibility or sourcing rules.

• Delivery-time or service requirements.

For example, two plants can supply two regional warehouses, and a planner must choose how much each plant sends to each warehouse. Sending everything from the lowest-cost plant may reduce production expense, but could overload its capacity or create long delivery times. A feasible plan accounts for both the cost of each flow and the limits of the resources it uses.

Cross-functional integration

Supply chain network design is a cross-functional decision because changes to the physical network alter many operating plans at once. Demand planning estimates what customers may require and when; procurement secures materials and supplier capacity; operations schedules production; inventory management sets buffers and replenishment rules; logistics selects modes and routes; and warehousing plans storage and labor. Finance evaluates investment, working capital, and total cost, while sales and customer service clarify delivery promises and priorities.

Integration means using shared assumptions and coordinating decisions across these functions, not simply combining their reports. A demand forecast should inform the capacity plan, purchasing commitments, production schedule, and inventory targets. If sales promotes a product without informing operations, or procurement selects a low-price supplier without accounting for longer lead times, the network can incur shortages, excess stock, expediting costs, or missed delivery promises.

Planning cycle and SCOR

A practical planning cycle connects strategy to ongoing monitoring:

1. Set the strategy and service promise. Define target markets, product needs, delivery expectations, and risk tolerance.

2. Build a common demand and supply view. Align forecasts, supplier availability, capacity, and inventory data.

3. Create and compare network alternatives. Vary facility locations, capacities, sourcing, flow assignments, and inventory placement.

4. Test operational feasibility. Confirm that production, storage, transportation, labor, and systems can execute the proposed plan.

5. Choose and monitor the design. Track cost, delivery performance, capacity use, inventory, and resilience; revise assumptions as conditions change.

The SCOR framework reflects this connected view. Its strategy-level Orchestrate process sits above Plan, Order, Source, Transform, Fulfill, and Return. Shared process definitions help organizations discuss where plans, decisions, and handoffs must connect.

Balancing cost, speed, and service

A network rarely minimizes every performance measure at once. Leaders should evaluate the total supply chain rather than treating one function’s cost reduction as a system-wide improvement.

• Cost: Fewer, larger facilities can reduce facility and inventory expenses and capture scale economies. They may increase average delivery distance, transportation time, and exposure to a localized disruption.

• Speed: Facilities closer to customers, extra capacity, faster transport, and strategically placed inventory can shorten response time. These choices typically increase fixed costs, operating costs, or working capital.

• Service: Service can mean product availability, order fill rate, delivery reliability, or a promised delivery window. Better service may require additional capacity or inventory; the design should identify which customer segments or products justify that investment.

A retailer choosing between one central distribution center and several regional centers illustrates these trade-offs. A central center may consolidate stock and reduce facility overhead. Regional centers may enable faster delivery and improve local availability, but require more sites and can duplicate inventory. The right choice depends on demand density, delivery promises, product characteristics, replenishment lead times, and the costs of inventory and transportation—not on facility count alone.

Trade-offs can be made explicit by comparing scenarios or by optimizing one measure subject to minimum requirements for others. For example, a company might minimize total cost while requiring that a specified share of orders arrive within a defined delivery window. This makes the design choice transparent without implying that cost, speed, and service can all be maximized simultaneously.

• Nodes