From strategy to network design
How the company competes, based on its capabilities
Supports and enables the organizational strategy
Partners, facilities, products, transport modes, information systems
Targets for each manager along the chain
Example logic from the module: if a company competes on low cost for commodity items, the supply chain is designed to be as low-cost and automated as possible rather than the fastest or most responsive. In the SCOR DS framework, this stage still sits in plan, which sets direction for orchestrate, source, transform, order, fulfill, and return.
Four areas of strategic decisions
Customers & markets
No single supply chain strategy fits all. Inditex (Zara) runs two distinct chains: one for functional products and one for fashion products.
Technology
Weigh benefits against costs. Theory of constraints (TOC): speeding flows into a bottleneck adds no value.
Processes & flows
Pick one or a few processes central to strategy, then measure and benchmark them. The flows show who must be involved.
Sourcing
Buy (arm's length) or outsource. Non-core activities tend to be contracted to partners in the best-suited location: near raw materials, near customers, or for tax and cost reasons.
The four flows that determine who is involved
Information flow
Orders, sales activity, and forecasts.
Product flow
The value-adding movement of goods from the moment materials are procured.
Cash flow
Payments and working capital.
Reverse flow
Products coming back: returns, repair, remanufacturing.
Network configuration: what gets optimized
Network configuration is a strategic decision about how suppliers, plants, distribution centers, and manufacturing resources are organized. Every decision is judged by its impact on the entire chain, not just the single issue at hand.
- Plant locations and production capacity for each product
- Number, location, capacity, and capabilities of warehouses
- Transportation between all facilities
The ideal: materials never rest in a warehouse and keep moving until they arrive just in time. In reality, demand fluctuation, accidents, and weather mean some inventory at various points is still needed.
Trade-off in the number of warehouses
| Adding warehouses | Impact |
|---|---|
| Benefit | Goods closer to customers, shorter delivery time, lower transportation cost up to a point |
| Cost | Total inventory rises and more warehouse space is needed |
Transportation cost depends on distance, bulk discounts, and the type of transport.
Due diligence for global expansion
- Ports and airports: size and quality of facilities
- Highways: condition and extent of the network
- Rail: routes that minimize delay; gauge differences and capacity limits can add lead time
- Borders: heavy paperwork
Efficient, responsive, and resilient
Responsiveness means reacting to changing customer requirements, through investment in customer service and/or agility. In SCOR DS, agility is measured by the ability to ramp production volume up or down without a major impact on cost or operations.
Because customer focus, agility, and resilience all carry a cost (for example, spare capacity), efficiency and responsiveness cannot both be maximized at once, yet neither can be ignored entirely.
Attribute comparison
| Efficiency-focused Cost | Responsive Speed & flexibility | |
|---|---|---|
| Demand | Stable, low uncertainty | Unstable, high uncertainty |
| Forecast error | Manageable | Can be significant |
| Market structure | Locations of demand and vendors change little | Adapts; locations of demand and vendors may change |
| Product life cycle | Long | Short |
| Product introductions | Infrequent or planned well in advance | More frequent |
| Product variety | Limited | Broader |
| Operating traits | Orders filled from inventory; time-series forecasting; fits make-to-stock | Real-time customer data; multiple warehouses near customers; spare capacity; fast 3PLs; agile suppliers; fits make-to-order or assemble-to-order |
| Forecasting pattern | Demand-based | Based on system flexibility and capacity cushion (safety/protective capacity). With high volume and high variability, forecast parts and components, then postpone final assembly |
Note: the matrix fitting supply chain type to product (Exhibit 2-2) is an image in the source. The table above is built from the module's text.
Case study: Gap Inc.
Cost-conscious
Manufacturing and sourcing in China, where labor and material costs are lower.
Trendy, mid-priced
Supply chain in Central America, where speed and flexibility matter most.
Quality
Supply chain in Italy, rich in fine fabrics and well-made fashion.
Resilience
Redundancy
- Safety stock
- Multiple suppliers, even when more expensive
- Deliberately low capacity utilization
Flexibility
- Indicators that sense threats
- Mechanisms to react quickly and appropriately
According to Hau Lee, efficiency is necessary but not sufficient. Chains must be agile, adaptable, and aligned. An efficiency-focused chain may skip the most expensive resilience initiatives, but not all of them.
The role of IT: from data to action
By the ASCM definition, an information system is interrelated hardware and software together with people and processes for collecting, processing, and disseminating information for planning, decision making, and control.
Technology should automate, control, and standardize processes so people can focus on the "why" behind transactions, the social side, and exceptions.
Eight ways IT helps the supply chain
Velocity, agility, scalability
Secure information exchange among partners enables virtual chains.
Low-cost global visibility
Large volumes of data flow cheaply over the internet.
Avoiding the bullwhip effect
Integrated logistics data prevents forecasting from incomplete information.
Information flows replace inventory flows
Moving from push to pull using real-time point-of-sale data.
Knowledge sharing
Stronger strategic and tactical capabilities for every partner.
Planning coordination
Partners pursue total-chain profitability, not just their own.
Data accuracy
Straight-through processing: enter once, store in one place, use many times.
New relationships and trust
Less "friction" makes new partners easier to add, and real-time sharing deepens trust.
Justifying technology investments
Benefits
Tangible Lower maintenance costs, higher sales volume, fewer changeovers, greater financial returns, lower overhead, shorter cash-to-cash cycle.
Intangible Faster implementation, customer retention, customer service, order-status visibility, employee satisfaction and efficiency, workforce redeployment.
Estimates for intangible benefits are best built by consensus, not one person's opinion. Position labor effects as redeployment, not headcount cuts; savings from layoffs often prove wrong and hurt morale.
Costs: three categories
- Capital expenditure: amortized over the technology's expected life. If the amortization period exceeds the real life, costs are understated.
- One-time project expenses: including hidden costs such as investigating alternatives, training travel, data conversion, and productivity lost during the learning curve.
- Ongoing support: licenses or subscriptions, vendor maintenance, bug fixes, upgrades, taxes on fixed assets, IT support staff.
Why IT projects often run over budget
Major costs overlooked
Especially operational support costs.
"Everything goes to plan" estimates
With no room for deviation.
Deliberately understated
To secure project approval.
No change management
Or training, which puts quality and acceptance of deliverables at risk.
Formulas and the module's example
New ERP example from the module. Bars are drawn to scale.
Benefit-cost ratio = total benefits ÷ total costs
345,000 ÷ 259,000 ≈ 1.33
ROI = (benefits − costs) ÷ costs
(345,000 − 259,000) ÷ 259,000 ≈ 33%
Keep the analysis time frame short because of the risk of technology obsolescence.
Maturity Stages 1 to 5
Characteristics, obstacles, and how to reach the next level
| Stage | Main characteristics | Focus to move up |
|---|---|---|
| 1 Multiple dysfunction | Several disconnected legacy MRP systems following departmental barriers; communication via paperwork and re-keying; no supply chain leader; minimal web capability; systems cannot produce timely order status or lead time; performance is unmeasured or poorly measured | Standardize internal processes; become internet- and mobile-capable; phase in, starting where savings are greatest, namely procurement and logistics (typically 5–8% each); change management is a must |
| 2 Semifunctional | MRP II complete; cross-functional integration of planning; documented processes; KPIs aligned to goals; main external ties are outsource providers; web use still functional (intranet, commodities) | Appoint a supply chain leader with external-integration experience and executive backing; start where change does not hurt market performance (for example, aggregating purchasing for volume discounts); lean strategies for transportation, warehousing, inventory, and equipment |
| 3 Integrated | Point-to-point planning integration with the extended enterprise; (near) real-time information sharing; collaborative forecasts with tier-1 customers and suppliers; ERP, possibly CRM/SRM; S&OP | Overcome cultural resistance ("external ideas are inferior") and technical resistance (fear of data loss, difficulty linking legacy systems); needs a visionary business-unit leader alongside the supply chain leader and IT head |
| 4 Extended | A supply network; e-commerce; automated information flows; CPFR and VMI; risk- and reward-sharing contracts; public or private exchanges; functions like a virtual company | Sustained executive leadership; human and technological expertise; an integrated performance measurement system; adaptable and scalable software |
| 5 Orchestrated | Cross-organizational, cross-functional teams; mature change management; end-to-end visibility; automation of repetitive work so people focus on exceptions and relationships; predictive analytics; drill-down to tier 2 and 3; cybersecurity standards followed by all partners; technology delivers competitive advantage | Sustain the advantage through optimization and innovation that never end |
The capability tables per stage (Exhibits 2-5 and 2-6) cover internet, integration, supply chain planning, production scheduling, supplier integration, and customer delivery, ranging from basic MRP/email/phone at Stage 1 to CTP/VMI/data-driven analytics at Stages 4–5.
Golden rules of maturity
- Stages cannot be skipped. Cross-company team collaboration matures only through experience.
- A majority of capabilities is required. Having ERP and WMS alone does not lift a stage.
- The weakest unit becomes the bottleneck. Different divisions or supply chains can sit at different stages; one organization can be more mature in some capabilities than in others.
- Staff tend to be over-optimistic about their own organization's stage, which can stall improvement efforts.
- Many companies get stuck along the way. The value of internal integration is easy to see; the leap of trust needed for external integration is much harder.
Six steps to build a move-up strategy
Goals & end state
Determine the goals and the desired end state of the supply chain.
Cross-functional/business teams
Create teams within and across companies.
Processes & IT mission
Organize the supply chain's operational processes and IT's mission.
Change & training
Design in, with stringent timetables for all parties; measure results and give feedback.
Conceptual model
Explain the process and all of its elements.
Technical infrastructure
Establish the supporting technical infrastructure.
Planning is collaborative and centralized, but execution is decentralized. The starting point for reaching Stage 4 is often a single partnership that shows the way.
Who leads the move between stages
Role of the nucleus firm
- Champions the initiative
- Contacts potential partners
- Performs a technology audit
- Forms teams with qualified partners across functional and enterprise boundaries
- Measures, monitors, and manages the supply chain across companies to make it appear seamless
Teams commonly formed
The technology team is formed first because the methods of connecting systems must be agreed and the connections made before other teams can progress past the conceptual stage. Its members should include general IT staff (not just supply chain technology specialists) for cybersecurity and networking expertise.
Executive team
Led by the nucleus firm; sets the pace and strategic goals for collaboration and examines mutual strategies for market penetration.
Technology team
Examines requirements for databases, networking, software, and configuration, especially communications and security; looks for types of information that create mutual advantage.
Buying · Making · Selling
Combined purchasing power; collaborative manufacturing improvements (taken in steps because members feel their process is already optimal); marketing, sales, and customer service synergies.
Inventory team
Determines optimal total inventory and inventory turnover to show the benefits of collaboration.
Delivery team
Examines total space against actual inventory; builds consensus on logistics best practices, total asset use, JIT, and network safety stocks.
How external relationships progress
Collaboration meetings → pilot → standing or project-based teams. Once the initial connectivity project is complete, the network is at the beginning of Stage 3.
Five reflection questions for your organization
DISCUSSION QUESTIONS
These questions are drawn from Section A as material for team discussion. The answers depend on each organization's situation and should be backed by facts, not perception.
- Strategy vs design. Is your organization's strategy closer to efficiency or responsiveness, and are your current network design and sourcing choices consistent with it?
- End-to-end evaluation. Which configuration decisions (facility locations, capacity, transportation) are currently judged function by function rather than by their impact on the whole chain?
- Location of the bottleneck. Where is the real bottleneck? Does the planned technology address it, or does it only speed up flows toward the same bottleneck?
- The IT business case. Which costs are usually missed in justifications: operational support, change management and training, and the cost of not doing the project? How are intangible benefits estimated, by consensus or by one person's opinion?
- Maturity position. Based on the capabilities that actually exist (a majority of a stage's characteristics), which stage is your organization or unit at? Who makes that assessment, and how large is the risk of over-optimism?