Supply Chain Planning, 2nd Edition

1. 1Define the three planning levels for each supply chain function (manufacturing, logistics, customer service, inventory, transportation, procurement) using the passages' categories. Strategic covers plant and warehouse location, size, capacity and technology, outsourcing mix, transportation network design, order fulfillment approach (make-to-order vs. make-to-stock), and sourcing scope. Tactical covers resource allocation and utilization, with annual planning as a subset. Operational covers planning, scheduling, and execution. Note that tactical planning includes planning and scheduling, while operational planning includes planning, scheduling, and execution.
2. 2Draw the function-by-level grid (the Figure 1.2 structure). Each function gets its own strategic, tactical, and operational boxes. Your definition of what counts as a major function is firm-specific: some firms fold transportation or customer service into logistics. Settle this before you assign owners.
3. 3Anchor the top row to the firm's business goals and objectives. Strategic plans formed at the business-unit level must support the overall business strategy. Each function's strategic plan then needs an explicit link from the supply chain mission to objectives, objectives to strategies, and strategies to projects.
4. 4Enforce the downward hierarchy. Strategic results guide and direct the tactical plan, and the tactical plan guides and directs the operational plan. Before any tactical or operational plan is approved, state in writing which higher-level decision it implements and which it must not contradict.
5. 5Build the upward feedback loops. Each level of each function needs a defined path back to the level above, so operational results and constraints can revise tactical and strategic assumptions. Treat the vertical lines in Figure 1.2 as bidirectional.
6. 6Build the horizontal links between functions. Schedule formal interactions such as joint planning sessions, and expect informal day-to-day communication to carry the rest. The dashed lines in Figure 1.2 show these interactions should occur between every pair of functions.
7. 7Put decision support at every level. Match the tool to the level and the problem's complexity, from spreadsheets and database analyses to optimization, simulation, statistics, or AI-based applications. Do not use one oversimplified tool for all three levels.
8. 8Select projects through the strategy chain. Use the Analytic Hierarchy Process (AHP) to weight objectives and strategies against the mission and to score how well each project supports the strategies. Then run a benefit-cost analysis to pick the portfolio best aligned with the plan. Add performance measures at each level so misalignment shows up early.

The source describes a ceramic tile manufacturer (American Olean Tile Company) that implemented a hierarchical manufacturing and logistics planning framework. It reduced annual operating costs by approximately 10 percent and improved customer service fill rates. The sequence mirrors the steps above. Strategic network and capacity decisions set the structure. Tactical planning allocated resources within that structure. Operational planning scheduled and executed within the tactical plan. Manufacturing and logistics were planned as linked functions rather than separate silos. A second case is a large pharmaceutical and consumer health care firm. It had invested for years in hierarchical planning frameworks and decision support systems. When business conditions changed rapidly and strained logistics capacity, it used those existing frameworks to respond. It kept fill rates very high and avoided potential revenue losses of $20 million. The lesson is that alignment is built before the stress arrives, so the response runs through structures that already exist.

• If an operational or tactical decision cannot be traced to a specific higher-level decision (strategic to tactical to operational), then hold it until you can name that parent decision or the parent plan is revised.
• If operational results show a persistent constraint the tactical plan did not assume, then send it up the feedback loop and revise the tactical or strategic assumption. Do not keep rescheduling around it.
• If two functions' plans touch the same resource or customer outcome (e.g., manufacturing and logistics), then require a joint planning session before either plan is finalized. Informal contact alone is not enough.
• If budget limits force a choice among projects, then rank them with AHP against objectives and strategies, then run benefit-cost analysis on the portfolio. Do not rank by function or by who argues loudest.
• If a decision's scale differs sharply from the tool in use (a plant location decision vs. a one-week line schedule), then change the tool. Match decision support complexity to the problem's complexity.

• Silo planning: each function has its own framework and no horizontal links. The tell is functions optimizing separately and surprised by each other's plans, with no joint planning sessions on the calendar.
• One-way hierarchy: plans flow down but nothing flows back up. The tell is strategic assumptions that stay unchanged while operations repeatedly work around the same constraint.
• Missing level: strategy and daily scheduling exist but tactical resource allocation is thin. The tell is operational schedules that cannot be traced to any annual or resource plan.
• Planning effort without results: managers spend heavy time on planning activities with little tangible outcome. The tell is plans that no one can connect to a business objective or a decision actually taken.
• Mismatched or oversimplified decision support: one expedient tool is applied to a complex problem. The tell is a spreadsheet standing in for a network design question, or models built at one level that no other level uses.

• ▸Function and owner: name the function (e.g., manufacturing) and the accountable person, noting how your firm defines its scope.
• ▸Business objective supported: state the firm-level goal or objective this function's strategic plan serves.
• ▸Strategic decision(s): list the current strategic decisions (e.g., plant sizing, outsourcing mix, make-to-order vs. make-to-stock).
• ▸Tactical plan linked to it: name the resource allocation and utilization plan (including the annual plan) that implements the strategic decision.
• ▸Operational plan/schedule linked to it: name the planning, scheduling, and execution activity that implements the tactical plan.
• ▸Feedback loop: record what operational or tactical information goes up, to whom, and how often.
• ▸Cross-function interactions: list the other functions affected, plus the formal session (date/cadence) and the informal channels.
• ▸Decision support tool by level: record the tool used at the strategic, tactical, and operational levels and why it fits the complexity.
• ▸Alignment check and metric: write whether each level's plan is consistent with the one above (yes/no, with the exception) and the performance measure used to detect drift.

1. 1Define agility with the SCOR agility attribute, which is external and customer focused. Track three Level 1 KPIs: upside supply chain adaptability (maximum sustainable percentage increase in quantity delivered within 30 days), downside supply chain adaptability (sustainable reduction in quantities ordered 30 days before delivery, with no inventory or cost penalties), and overall value at risk (sum of probability times monetary impact of risk events).
2. 2Tie agility to strategy before measuring it. Link the objective (the book's list includes flexibility) to the business strategic plan, so the agility target follows from market share, product mix, and service goals and is not an isolated number.
3. 3Maintain the planning framework as a living structure. Keep the hierarchy of business strategy, supply chain strategy, and individual function strategy (manufacturing, logistics, transportation, procurement) current, so a shock at one level has a defined path for re-planning at the others.
4. 4Use the SCOR hierarchy to diagnose agility gaps. When a Level 1 KPI misses, review the Level 2 metrics that influence it, then the Level 3 processes and metrics behind them. Extend the model to at least Level 4 with your own industry, organization, and location-specific processes and systems.
5. 5Build a mixed DSS portfolio. Use commercial tools for standard scheduling and planning, and also develop flexible internal DSS capabilities for sudden, unforeseen operational problems that turnkey tools do not fit.
6. 6Keep strategic and tactical optimization models for manufacturing-distribution networks maintained, so you can re-run scenarios when conditions change. In the book's example, such a model identified over $5 million in potential annual operational savings.
7. 7Pair the agility KPIs with the other SCOR attributes. Because costs and assets are internal and agility is external, review them together, so that faster response does not quietly add inventory or cost penalties.
8. 8Test the response path against a rapid-change scenario: capacity shortfall, demand surge, or demand drop. Measure how long it takes to get from signal to a deployed decision, and record which tool or framework was used.

Pfizer, early 2000s, after the Warner-Lambert merger. Finished goods inventory in pallets for the merged consumer division suddenly exceeded the in-house storage capacity of the consumer distribution network. The cause was the merger plus several unanticipated internal issues, and it arrived with minimal advance warning. Both legacy companies had used third-party overflow storage only occasionally and seasonally, but by 2001 third-party storage had to become a standard part of daily operating capacity. Neither a major investment in internal storage nor opening a new third-party full-service customer-facing DC was acceptable. Pfizer logistics therefore built a customized inventory deployment DSS to support daily logistics operations. The lesson the authors draw is that turnkey tools alone could not provide the agility to react quickly. A firm also needs flexible internal DSS capabilities it can build when the unexpected occurs.

• If a sudden operational problem falls outside what your commercial DSS handles, then build or adapt an internal DSS rather than wait for a vendor fit.
• If a Level 1 agility KPI (upside or downside adaptability, value at risk) misses target, then drill to the Level 2 metrics, then the Level 3 processes, before choosing a fix.
• If a temporary condition (such as overflow storage) becomes permanent, then redesign it as a standard operating capability instead of continuing to run it as an exception.
• If the response options are a large capital investment or a new facility, then first test whether a cheaper operating change (third-party capacity plus better deployment decisions) meets the need, as in the Pfizer case.
• If you raise agility targets, then review the cost and asset KPIs in the same cycle, because the downside adaptability definition requires no inventory or cost penalties.

• Relying exclusively on turnkey DSS tools. The tell: a sudden problem arrives and no one can produce a decision-ready analysis without waiting on a vendor or building from scratch.
• Treating agility as a slogan with no metric. The tell: no one can state your sustainable 30-day upside or downside adaptability in numbers.
• Letting the framework go stale. The tell: function plans (manufacturing, logistics, procurement) no longer match the supply chain strategy, so a shock forces improvised re-planning.
• Measuring only internal efficiency (costs, assets). The tell: dashboards show cost and asset KPIs but no external, customer-focused agility or risk exposure measures.
• Running a recurring workaround as a one-off. The tell: the same emergency fix, such as overflow storage, repeats year after year with no process or system built around it.

• ▸Business objective supported: state the corporate goal (market share, product mix, service) this agility target serves.
• ▸Upside adaptability (30 days): record the maximum sustainable percentage increase in quantity delivered.
• ▸Downside adaptability (30 days): record the sustainable reduction in quantities ordered 30 days before delivery with no inventory or cost penalties.
• ▸Overall value at risk: list risk events with probability times monetary impact, then sum.
• ▸Level 2 / Level 3 diagnostic trail: name the Level 2 metrics and Level 3 processes to examine for each missed KPI.
• ▸Commercial DSS coverage: list the decisions your turnkey tools handle and the ones they do not.
• ▸Internal DSS capability: name the flexible in-house tools or skills ready for unforeseen problems, and the owner of each.
• ▸Maintained models and frameworks: note the last review date of the planning hierarchy and optimization models.
• ▸Cost and asset check: record the effect of the response on total supply chain cost and cash-to-cash cycle time.

1. 1Start from the business strategy, not from the metric list. Write down the corporate objectives that touch service: market share, profitability goals, and business and product mix targets. The source says market share and product mix objectives strongly influence a firm's capacity and service strategies, so each service target must cite the objective it serves.
2. 2Set the strategic customer service targets together with a maximum inventory investment level. The source lists both as high-level supply chain strategies set at the same stage. A service target with no inventory ceiling is half a decision.
3. 3Define the four outcome metrics in writing before anyone reports them: order fill rate, line-item fill rate, on-time delivery, and order cycle time. For each, state the numerator, the denominator, the clock start and stop, and the point in the chain where it is measured. The passages name the metrics but give no formulas, so your firm must fix its own and then keep them constant.
4. 4Cascade the targets down the planning hierarchy. Strategic plans guide tactical plans, and tactical plans guide operational plans. Give manufacturing, logistics, and transportation each a function-level service goal that supports the supply chain target. For example, manufacturing sets planned capacity levels and the number and location of facilities, while logistics sets inventory deployment.
5. 5Measure across the supply chain, not inside one function. The construct covers service delivered to customers across the network, so define who owns each metric and where the data comes from. Report at the same cadence the planning levels use.
6. 6Review service results against cost and capacity in the same meeting. The source's cases show service gains and cost reductions coming from the same planning framework, so a fill-rate result with no cost or capacity context cannot support a decision.
7. 7Stress-test the plan before conditions change. Use the decision support systems that sit under the planning framework to ask what happens to fill rates if volume or capacity shifts. The pharmaceutical case shows the payoff of having this ready.
8. 8Institutionalize the process, tools, and expertise. The foreword stresses this is not a one-time event. Keep the definitions, targets, and review routine as a standing process that survives personnel changes.

The source describes a large pharmaceutical and consumer health care firm that invested heavily in hierarchical supply chain planning frameworks over many years. Business conditions changed dramatically and put significant stress on its logistics capacity. Because strategic, tactical, and operational plans were already linked, and decision support systems already existed, the firm responded rapidly. It maintained very high fill rates and avoided potential revenue losses of $20 million. The practical point is that the fill-rate result came from planning infrastructure built before the stress, not from heroic expediting. The passages do not give the actual fill-rate values or the specific actions taken, so treat those as unknown. A second case in the source is a ceramic tile manufacturer. It implemented a hierarchical manufacturing and logistics planning framework, reduced annual operating costs by approximately 10 percent, and improved its customer service fill rates. Together the two cases show service and cost improving under the same framework.

• If a service metric cannot be traced to a stated business objective such as market share, profitability, or product mix, then drop it or rewrite it until it can.
• If you raise a customer service target, then re-set the maximum inventory investment and the capacity plan in the same revision, because the source treats them as joint strategic decisions.
• If market share or product mix objectives change, then reopen the service and capacity strategy before changing operational tactics.
• If fill rates come under pressure from a capacity stress, then run the scenario through the existing planning and decision support framework first, and fall back to ad hoc expediting only if no framework exists.
• If your logistics orientation is cost-focused (process strategy), then pair every efficiency metric with a customer-facing one. If it is market-focused (reducing complexity for customers), then weight on-time delivery and cycle time more heavily.

• Planning effort with no outcome. The source warns that managerial resources often go to planning with little tangible result. The tell: plans are produced on schedule but fill rates and on-time delivery do not move.
• Service targets floating free of strategy. The tell: nobody can name the corporate objective a given fill-rate target supports.
• Service judged without cost and inventory. The tell: a fill-rate target is raised while no one revisits the inventory ceiling or capacity plan.
• Metric definitions that drift. The tell: fill rate or cycle time changes meaning between functions or periods, so trends cannot be compared.
• Treating the framework as a one-time project. The source says the process, tools, and expertise must be institutionalized. The tell: the targets and models are not updated after the project team disbands.

• ▸Linked business objective: name the market share, profitability, or product mix goal this service target supports.
• ▸Metric and formula: order fill rate, line-item fill rate, on-time delivery, or order cycle time, with numerator, denominator, and clock start and stop.
• ▸Measurement point and data source: state where in the supply chain and from which system it is captured.
• ▸Strategic target: the service level set at the business and supply chain strategy stage.
• ▸Paired inventory ceiling: the maximum inventory investment set with this target.
• ▸Function-level goals: the manufacturing, logistics, and transportation targets that support it.
• ▸Metric owner and review cadence: one named owner and the meeting where the result is reviewed against cost and capacity.
• ▸Stress scenario: the capacity or volume change to be tested in the planning and decision support framework.
• ▸Last revision date and trigger: the date this card was last revised and the strategy change that would force a revision.

1. 1Decide first whether cost efficiency is the right primary objective. The passages tie it to functional products: stable demand, low margins. They tie it to products with predictable demand and stable supply sources. If demand is unpredictable, a responsive or agile strategy applies, and cost is a secondary measure.
2. 2Define the cost outcome in three forms the construct names: total operating cost reduction (annual, as a percent), distribution cost per unit, and identified operational savings (annual dollars, labelled 'potential' until realized). Record a baseline for each before any planning change.
3. 3Build the cost number from a hierarchical plan, not from isolated function budgets. Strategic plans guide tactical plans, and tactical plans guide operational plans. A cost saving that exists only at one level is not aligned with the firm's high-level strategy.
4. 4Use the annual plant/DC/family (PDCF) optimization model to produce the cost-bearing decisions: the sourcing plan (regions to DCs and plants), plant-to-DC and inter-DC shipping plans, plant production plans by time period with operating rates and product mixes, and the inventory plan. Cost the model's plan against the baseline.
5. 5Test the annual plan in the weekly production scheduling model before you count the savings. Production plans that look feasible at the annual level often show infeasibilities in weekly buckets or with weekly changeovers. Savings from an infeasible plan are not real.
6. 6Feed the weekly and operational results back to the tactical and strategic levels (feedback loops). Restate the savings after infeasibilities are resolved, so the reported figure reflects what operations can execute.
7. 7Track cost efficiency in a performance measurement system alongside service. The ceramic tile case reported a cost reduction and improved fill rates together. Report cost per unit next to fill rate so a cost cut that damages service shows up.
8. 8Label each figure by status: 'identified potential' (model output) versus 'realized' (measured after implementation). The confectionery case's savings were 'identified' potential annual savings, a different claim from realized savings.

A ceramic tile manufacturer implemented a hierarchical manufacturing and logistics planning framework to manage and schedule manufacturing and distribution over a multiechelon network. The result was a reduction of annual operating costs by approximately 10 percent, together with improved customer service fill rates. The source supports two readings of the metric: operating cost reduction as a percent of annual cost, and service held or improved at the same time. A second case, a multibillion dollar confectionery division, used a global manufacturing planning decision support system. Its strategic and tactical components identified over $5 million in potential annual operational savings. Treat the two figures as different kinds of claim: the tile figure is a reported reduction, while the confectionery figure is identified potential. A pharmaceutical firm adds a third, adjacent measure: it avoided potential revenue losses of $20 million while keeping fill rates very high. That is avoided loss, not an operating cost saving, so keep it in a separate line of the scorecard.

• If the product is functional (stable demand, low margins) and supply is stable, then make cost efficiency the lead metric. If demand is unpredictable, then pair cost with a responsiveness measure and do not optimize cost alone.
• If a savings figure comes from an annual optimization model, then call it 'identified potential' until the weekly scheduling model confirms feasibility.
• If cost falls but fill rate falls too, then do not report an efficiency gain. The reference case improved both.
• If a savings claim sits at only one planning level, then trace it through the strategic, tactical, and operational levels before reporting it.
• If a firm has a planning framework but no performance measurement system (or the reverse), then expect the cost result not to hold. The passages say the combination of frameworks, decision support systems, and measurement systems is required.

• Reporting model output as realized savings. The tell: the number is labelled 'savings' but no weekly feasibility test or post-implementation measurement exists.
• Counting an annual-level plan that breaks at the weekly level. The tell: planned operating rates or product mixes that ignore weekly changeovers and time buckets.
• Measuring cost without service. The tell: the scorecard has cost per unit but no fill rate, so a cost cut that hurts customers goes unseen.
• Optimizing one function in isolation. The tell: a function's cost drops while the plan no longer aligns with the tactical and strategic levels, with no feedback loop from operations upward.
• Applying a cost efficiency target to the wrong product or market. The tell: a new-market or innovative product with uncertain demand is held to a pure cost target when a responsive strategy is called for.

• ▸Product/market type: functional or innovative; demand predictable or not; supply stable or evolving. Confirms cost efficiency is the right lead objective.
• ▸Baseline annual operating cost: the figure before any planning change.
• ▸Baseline distribution cost per unit: the starting value and the unit basis used.
• ▸Fill rate baseline and current: the paired service measure reported next to cost.
• ▸Plan source: the annual PDCF optimization model run, with sourcing, shipping, production, and inventory outputs.
• ▸Weekly feasibility result: pass/fail from the weekly production scheduling model, and any infeasibilities found.
• ▸Feedback loop notes: changes sent from operational to tactical to strategic levels.
• ▸Savings status: 'identified potential' or 'realized', with annual dollars or percent reduction.
• ▸Separate avoided-loss line: revenue losses avoided, kept apart from cost savings.

1. 1Define the metric before anything else: Firm Profitability = operating margin (EBIT) adjusted for industry. Write down the exact EBIT and revenue lines you use, and pick one industry benchmark (for example, the margin of your industry peer set). Hold that benchmark fixed so changes in the adjusted figure reflect the firm, not a shifting yardstick.
2. 2Start from the business plan, not the supply chain plan. Per the book's three-step framework, profitability goals, market share goals, and product mix targets set in business strategic planning drive supply chain strategy. Record the firm's profitability goal first, then trace which supply chain strategies are supposed to serve it (capacity and service strategies, customer service level targets, maximum inventory investment).
3. 3Name your outbound logistics posture. The book's profitability analysis contrasts cost minimization with high customer service levels. State which one your supply chain mission commits to, so you know which direction of metric movement should show up in margin.
4. 4Select the performance measures that follow from that strategy. Chapter 6 links the choice of key measures directly to supply chain strategy. Choose outbound logistics measures that reflect your posture, for example cost efficiency and delivery effectiveness, the objectives Zenith used. Drop measures that do not trace back to a strategy.
5. 5Pair each logistics metric with the same firm's profitability data over multiple years. The book's study used actual outbound logistics metrics and profitability data for 247 major firms across 11 industries, over multiple years. A single year's snapshot cannot support a strategy-to-margin claim.
6. 6Compare within industry. Because the profitability measure is industry-adjusted, rank or benchmark each firm against its own industry. Do not pool raw margins across industries.
7. 7Roll the selected measures into a customized management index (Chapter 6) and review it against adjusted margin on a fixed cadence. If the index moves and adjusted margin does not, revisit which measures you selected, not just the targets.
8. 8Document the link as quantitative evidence. The authors note that most prior studies of logistics strategy and profitability are qualitative or anecdotal. Keep your own file of metric and margin pairs so decisions rest on data, not stories.

Take Zenith, the book's strategic planning case. Its supply chain team chose the mission 'Position Zenith's supply chain to support the overall firm objectives as efficiently and effectively as possible.' It then set explicit objectives in five areas: regulatory compliance, cost efficiency, delivery effectiveness, flexibility, and security. Three of these (cost efficiency, delivery effectiveness, flexibility) reflect the efficiency and responsiveness trade-off. To tie this to Firm Profitability, you first record Zenith's EBIT margin and its industry benchmark, and take the difference as the industry-adjusted margin. Next you identify Zenith's posture. A mission built on efficiency and effectiveness together does not settle whether it leans toward cost minimization or high service, so you must resolve that explicitly. You then choose cost-efficiency and delivery-effectiveness metrics from its objectives and track them alongside adjusted margin over several years. This mirrors the book's study of 247 firms in 11 industries. The passages do not report that study's findings, so this example shows only the method, not a result.

• If a profitability goal exists in the business plan but no supply chain strategy references it, then stop selecting metrics and re-link the strategy to the goal first.
• If your outbound posture is cost minimization, then expect the evidence to show up as cost metrics improving against adjusted margin. If it is high service, then test delivery and service metrics against adjusted margin, and do not judge either posture on the other's metrics.
• If you are comparing margins across firms in different industries, then use industry-adjusted margin only. Raw EBIT margin comparisons are not valid.
• If you have fewer than several periods of paired metric and margin data, then treat the link as a hypothesis and keep monitoring, not as a finding.
• If the management index and adjusted margin diverge over multiple periods, then audit measure selection against strategy before changing targets.

• Using raw EBIT margin without industry adjustment. The tell: a firm looks strong or weak simply because of its sector, and the 'insight' reverses when you compare it to peers.
• Selecting logistics metrics by habit instead of from strategy. The tell: you cannot say which strategy a given measure supports.
• Declaring a logistics strategy successful from anecdotes or one year of results. The tell: no paired multiyear metric and margin series exists, only a narrative.
• Leaving the posture undefined (cost minimization vs. high service) so every metric movement can be explained as good. The tell: both cost cuts and service gains are celebrated, and nobody can say which was supposed to drive margin.
• Treating supply chain planning activity as the outcome. The book warns that considerable managerial resources go into planning with little tangible result. The tell: planning milestones are reported but adjusted margin is never reviewed.

• ▸Firm and fiscal periods covered: list each year included (multiple years required).
• ▸EBIT and revenue by period: record the exact figures used to compute operating margin.
• ▸Industry benchmark: state the peer set and benchmark margin, and keep it fixed.
• ▸Industry-adjusted margin: firm operating margin minus the benchmark, by period.
• ▸Business profitability goal: copy the margin or market share goal from the business strategic plan.
• ▸Outbound logistics posture: cost minimization or high customer service level, in one sentence.
• ▸Selected outbound metrics: each metric, plus the strategy it supports.
• ▸Metric values by period: record each metric alongside the adjusted margin for the same period.
• ▸Observed relationship and next action: note whether the metrics and margin moved together, and whether to keep, replace, or retarget the measure.

1. 1Define the three horizons by decision type, not by calendar alone. Strategic decisions use highly aggregated data and take years to show impact (the new-plant decision). Operational decisions use detailed data and take effect in hours or days (what a line produces next week). Tactical decisions sit between them. Write down which decisions belong to each level for each supply chain function, such as production planning, distribution, and logistics.
2. 2Postpone each decision to the latest point its lead time allows, and commit early only where lead time forces it. Test every decision with the passage's widget rule: if the lead time is hours or days and the demand is uncertain, defer it. The red-or-blue widget in a week 3 years out is the example. If the lead time is years, decide now. The new plant, needed within 3 years, is the example.
3. 3Anchor the top of the hierarchy with a linked strategic structure: mission (level 1), objectives (level 2), strategies (level 3), then projects. Score the links numerically. Allocate 100 points across the objectives, split each objective's points across the strategies that support it, and total each strategy's points. Zenith's example gives 25 points to cost efficiency, split 15 financial and 10 internal.
4. 4Convert strategy scores into project priority so top-down constraints reach action. Score each project as a percentage of the strategy score it supports, and add the points for projects that support several strategies. Zenith's example is CUST at 20: CRM services at 90% gives 18, and integrate POS data at 75% gives 15. Fund projects in rank order within the resource limit.
5. 5Make each plan constrain the level below it. The strategic plan guides the tactical plan, and the tactical plan guides the operational plan. Check that every tactical plan stays inside the strategic constraints, such as capacity and network decisions. Check that every operational schedule stays inside the tactical plan.
6. 6Give each level its own decision tool and database. The foreword's point is complementary but distinct tools per level, with commonality and granularity differences in the supporting data. Keep shared definitions (products, locations) common across levels, and let the detail differ: aggregated for strategic, detailed for operational. Match tool power to problem complexity, using optimization and stochastic simulation for complex resource allocation.
7. 7Build the bottom-up loop. Operational results and constraints (fill rates, capacity stress) go back up to the tactical and strategic levels. Pair each level with its own performance metrics. Use them to revise the higher-level plan when lower levels cannot execute it.
8. 8Assign layered management ownership and institutionalize the process. Senior management leads strategic decisions, and less senior managers and supervisors lead tactical and operational decisions. Keep the process, tools, and expertise in place permanently. One-time projects do not produce a continuing stream of results.

Zenith's strategic planning team starts at the top of the hierarchy. They allocate 100 points across five objectives, then split each objective's points across the strategies that support it. The cost efficiency objective gets 25 points, split 15 to the financial strategy and 10 to the internal strategy. Summing each strategy's points shows how much it contributes to the mission. With the customer strategy (CUST) scored at 20, project 3 (CRM services) is judged to support it very strongly and gets 0.90 × 20 = 18. Project 2 (integrate POS data) gets 0.75 × 20 = 15. Ranking the 12 candidate projects this way directs limited resources to the actions that best serve the most important strategies. A weighted AHP version of the same hierarchy gives delivery effectiveness 0.354 and cost efficiency 0.250 as objective weights. It also gives the G&S strategy 0.380 and the INTERNAL strategy 0.206. Further down, the book's ceramic tile manufacturer applied a hierarchical manufacturing and logistics planning framework and cut annual operating costs by about 10 percent while improving fill rates. The pharmaceutical firm used years of invested frameworks and decision support systems to keep very high fill rates and avoid $20 million of potential revenue loss under logistics capacity stress.

• If a decision's lead time is hours or days and its inputs are uncertain, then defer it to the operational level and decide it at the last responsible moment.
• If a decision takes years to show impact and capacity is needed within about 3 years, then decide it now at the strategic level, using aggregated data.
• If a project cannot be traced through a strategy and an objective to the mission, then do not fund it. Score each project's support for strategies and fund in rank order within the resource limit.
• If a lower-level plan cannot be executed inside the constraints from above, then send the conflict back up as feedback and revise the higher-level plan. Do not let operations quietly override it.
• If the problem is a complex resource allocation, then use optimization or stochastic simulation rather than a spreadsheet, and use a different tool at each level.

• Siloed planning, where each function plans alone and the levels are not linked. The tell: tactical plans that never reference strategic objectives, and functions with conflicting targets.
• Deciding at the wrong level or the wrong time, such as committing detailed schedules years ahead. The tell: frequent re-planning of long-horizon detail and schedules that are obsolete before use.
• One generic tool and database for all levels, usually a spreadsheet. The tell: strategic models that need operational-level detail, or operational plans built from aggregates.
• Top-down only, with no feedback. The tell: unexecutable plans, recurring service misses, and strategy that never changes despite operational stress.
• Treating the framework as a one-off project. The tell: gains fade after the initial effort and no one owns the process, tools, or expertise.

• ▸Function: name the supply chain function covered, such as production planning or distribution.
• ▸Strategic decisions: list decisions with multi-year impact, their aggregated data, and the senior owner.
• ▸Tactical decisions: list medium-term decisions, the constraints they receive from strategy, and the manager owner.
• ▸Operational decisions: list decisions that take effect in hours or days, their detailed data, and the supervisor owner.
• ▸Decision lead time and defer point: for each decision, give its lead time and the latest date it can be made.
• ▸Top-down constraints: state what each level hands to the level below, such as capacity, network, or targets.
• ▸Bottom-up feedback: state which metrics return upward (for example fill rate), how often, and to whom.
• ▸Tool and database per level: name the tool and the data granularity used at each level, and the common data shared across levels.
• ▸Strategy-to-project score: record the points per strategy and each project's percentage support, with the resulting score.

1. 1Write the firm's high-level business goals and objectives as a short, fixed list. Every later plan is checked against this list, so a plan with no goal to point to has no basis. The source says all supply chain planning frameworks 'must support and align with the firm's overall business goals and objectives.'
2. 2Name the planning framework for each level and function: overall supply chain strategic planning, plus separate frameworks for transportation, manufacturing, and logistics. The source expects both the overall framework and a well-established one per function.
3. 3Link the horizons hierarchically. Strategic plans guide and direct tactical plans, and tactical plans guide and direct operational plans. For each tactical or operational plan, record the strategic plan or goal it inherits from. A plan with no parent is misaligned.
4. 4Put the goal link into project selection. Score each candidate supply chain project against the business goals with explicit, written weights, using a structured approach such as MOS or AHP. The supplied passages name these approaches but do not describe their mechanics, so use your own documented method and keep the weights visible.
5. 5Drive the objectives from the top. Restate the goal linkage at the start of every planning cycle and review, as the authors do at the start of every chapter. Each function's objectives should be derived from the business goal, not set independently.
6. 6Run the review cross-functionally. Transportation, manufacturing, logistics, and strategy sit in the same review so that functional plans are tested against the shared goals rather than each function's local optimum. The foreword contrasts this with the 'outmoded silo management mentality.'
7. 7Check the outcome in business terms. Test whether alignment produced results in operating cost, customer service fill rates, and revenue protection. If planning effort is high but results are 'little in the way of tangible results,' the linkage is nominal and needs rework.
8. 8Re-test when conditions change. A well-linked hierarchy lets you respond rapidly to changing business conditions. Confirm that the goal-to-plan chain still holds after a shock and re-point plans if it does not.

The source describes two firms that built hierarchical planning frameworks in which strategic plans drive tactical and operational ones. A ceramic tile manufacturer (American Olean Tile Company) implemented a hierarchical manufacturing and logistics planning framework. It reduced annual operating costs by approximately 10 percent and improved customer service fill rates, so the cost goal and the service goal both moved because plans at each level traced back to high-level strategy. A large pharmaceutical and consumer health care firm (Pfizer/Warner Lambert) invested heavily over many years in hierarchical frameworks and related decision support systems. When business conditions changed dramatically and stressed its logistics capacity, it used those existing frameworks to respond rapidly. It kept fill rates very high and avoided potential revenue losses of $20 million. The lesson for your own work is to build the goal-to-plan chain before the disruption, because it is what lets you re-plan quickly and in line with the business goals. The passages do not give the internal scoring steps for either firm.

• If a tactical or operational plan cannot name its parent strategic plan or business goal, then pause or re-scope it until the link is written down.
• If two candidate projects both claim to support the goals, then rank them with explicit written weights (MOS, AHP, or your documented equivalent), not advocacy by the sponsoring function.
• If a functional framework (transportation, manufacturing, logistics) optimizes its own metric at the expense of a stated business goal, then change the functional objective, not the business goal.
• If planning effort is high but cost, fill rate, or revenue outcomes are not moving, then audit the hierarchy for broken links before adding more planning activity.
• If business conditions shift sharply, then re-run the goal-to-plan check top down, strategic first, before changing operational plans.

• Functional plans built in silos: each function has a polished plan but no shared goal list. The tell is that transportation, manufacturing, and logistics objectives conflict in the same review.
• Alignment claimed but not traceable: strategy documents mention the goals, but no plan records a parent goal. The tell is that nobody can answer 'which goal does this project serve?'
• Project selection by sponsor influence: weights and criteria are implicit or change per project. The tell is that the ranking cannot be reproduced from written scores.
• Planning without results: large effort goes into planning activities with 'little in the way of tangible results.' The tell is activity metrics rising while cost and fill-rate outcomes stay flat.
• Linkage built only after a disruption: the chain is improvised under stress. The tell is slow, ad hoc re-planning when conditions change, instead of the rapid response seen in firms with established frameworks.

• ▸Business goal / objective: the exact high-level goal from the firm's list that this row serves.
• ▸Strategic plan: the supply chain strategic plan or initiative that derives from that goal.
• ▸Tactical plan (parent: strategic plan): the medium-term plan that this strategic plan guides.
• ▸Operational plan (parent: tactical plan): the short-run plan or action that this tactical plan directs.
• ▸Owning function: transportation, manufacturing, logistics, or other, with a named owner.
• ▸Project candidate and selection score: the project name, the method used (MOS, AHP, or other), the written weights, and the score.
• ▸Outcome measure: the cost, fill-rate, or revenue measure expected to move, with baseline and target.
• ▸Cross-functional reviewer(s): the functions that signed off, to prevent silo-level optimization.
• ▸Last re-validation date and trigger: when the chain was last checked, and the business change that forced a re-check, if any.

1. 1Map the planning hierarchy first: list the strategic, tactical, and operational decisions for each supply chain function (transportation, manufacturing, logistics). Each decision needs a named owner and a horizon. The passages treat these three levels as the organizing spine, so DSS tools attach to decisions, not to departments.
2. 2Assign at least one DSS tool to each level. Do not reuse one tool across all three. The foreword calls for 'complementary yet distinct tools for each level.' Write down, per level, the question the tool answers and the output the next level down consumes.
3. 3Match tool complexity to problem complexity. Complex resource allocation problems call for mathematical optimization and stochastic simulation. The foreword warns that an expedient, oversimplified approach 'necessarily fails in the end.' Reserve spreadsheets and database analyses for problems that are genuinely simple, and record why each tool was chosen.
4. 4Design the databases with deliberate commonality and granularity differences. Keep shared definitions (items, locations, resources) common across levels. Aggregate for strategic use and detail for operational use. Document the mapping rules between the aggregate and detailed views so a strategic plan can be translated into tactical and operational inputs.
5. 5Wire the hierarchy: strategic outputs set the constraints and targets for tactical models, and tactical outputs set the targets for operational scheduling. Add explicit feedback loops from lower levels back up, and schedule the lateral interactions between functions (joint planning sessions plus day-to-day contact).
6. 6Pair the DSS with a performance measurement system. Metrics report how efficiently and effectively the chain is operating and give advance warning of future problems. Choose metrics that tie back to the corporate goals the plans serve.
7. 7Validate with a quantified business case before scaling. Record the baseline and the result (cost, fill rate, revenue at risk) as the cited cases do.
8. 8Institutionalize the capability: the process, the tools, and the expertise must persist, not be a one-time project. Assign ongoing owners, schedule model and data refreshes, and treat the DSS as a standing process.

The passages describe three firms that built hierarchical planning frameworks with supporting DSS. A ceramic tile manufacturer (American Olean Tile is named in the foreword) implemented a hierarchical manufacturing and logistics planning framework. It reduced annual operating costs by approximately 10 percent and improved customer service fill rates. A large pharmaceutical and consumer health care firm (Pfizer/Warner Lambert) invested in hierarchical frameworks over many years. When business conditions changed dramatically and stressed its logistics capacity, it used its existing frameworks and DSS to respond. It kept very high fill rates and avoided potential revenue losses of $20 million. A multibillion dollar confectionery division built a global manufacturing planning DSS whose strategic and tactical components identified over $5 million in potential annual operating savings. The pattern across all three is the same: purpose-built tools at each horizon, linked through a hierarchy, and kept in place long enough to be used when conditions shifted. The $20 million avoided loss came from capability that already existed, not from tools built during the crisis.

• If a decision is a complex resource allocation (many products, sites, constraints), then use mathematical optimization or stochastic simulation. If it is a simple lookup or aggregation, a database analysis or basic spreadsheet is acceptable.
• If a tool serves one planning horizon, then do not stretch it to another. Give each level its own tool and database granularity, and connect them through defined inputs and outputs.
• If a lower-level plan cannot meet the target handed down from above, then send the gap up through a feedback loop. Do not quietly rework the number at the operational level.
• If a DSS result is not tied to a corporate goal or a measured outcome (cost, fill rate, revenue protected), then it is not ready to scale. Quantify it first.
• If a model's value depends on one analyst or one project team, then institutionalize it before relying on it: assign ownership, refresh cycles, and training.

• Spreadsheet as the universal tool: complex allocation problems run in high-speed arithmetic. The tell is that results degrade as scale or constraints grow, and the model needs constant manual patching.
• One database for every level: strategic models drown in transaction detail, or operational schedules run on aggregates. The tell is that planners rebuild data by hand to move between horizons.
• Disconnected horizons: tactical and operational plans do not trace to strategy. The tell is considerable managerial effort in planning with little tangible result, which the authors identify as the common problem.
• One-time tool build: the model is delivered, then decays. The tell is that nobody can explain or rerun it six months later, and savings claims stop being updated.
• Silo planning: each function optimizes alone with no lateral interaction. The tell is that functions' plans conflict at handoff points and no joint planning session exists.

• ▸Function and horizon: name the supply chain function (e.g., manufacturing) and the level (strategic, tactical, or operational) being audited.
• ▸Decision supported: state the specific decision this level makes and who owns it.
• ▸Current tool and method: list the tool in use (database analysis, spreadsheet, optimization, simulation, forecasting, dashboard).
• ▸Problem complexity vs. tool fit: rate the problem as simple or complex and state whether the tool matches it, with one sentence of justification.
• ▸Data source and granularity: name the database, its level of aggregation, and which definitions are shared with other levels.
• ▸Upstream input: identify the plan or target received from the level above and how it enters the tool.
• ▸Downstream output and feedback loop: identify what this level passes down and what it reports back up when targets cannot be met.
• ▸Lateral interaction: record the formal or informal interaction with other functions (e.g., joint planning sessions).
• ▸Measured outcome and owner: record the baseline and current metric (cost, fill rate, revenue at risk), and the named person who keeps the tool and data current.

1. 1Start from the written business goals, not from a metric list. The source says every supply chain planning framework must support and align with the firm's overall business goals, and that supply chain strategy must be explicitly linked to corporate strategy. Write the 3-5 strategic objectives the supply chain serves (for example cost minimization versus high customer service levels, the strategic contrast the authors test in Chapter 7). These objectives decide which measures qualify.
2. 2Select key performance measures by tracing each one to the supply chain strategy. Chapter 6 presents a methodology that links the choice of key measures directly to strategy. Use it as a filter: if you cannot name the strategic objective a measure supports, drop it.
3. 3Build the hierarchy to mirror the planning hierarchy. The source requires planning support at the strategic, tactical, and operational levels, and for each individual function (transportation, manufacturing, logistics). Give each function a small set of KPIs at each level, with operational measures rolling up into tactical and then strategic ones. Each level's measures should explain movement in the level above.
4. 4Balance the set deliberately. Check that it contains both efficiency measures (cost, resource use) and effectiveness measures (customer service, such as fill rate), and both internal and external views. The book is keyworded to the balanced scorecard and reviews the SCOR model from the Association for Supply Chain Management as a reference list of standard supply chain measures. Use SCOR to check coverage, not to adopt every metric.
5. 5Add advance-warning measures on purpose. A PMS must indicate potential future problems, not only report past results. For each critical outcome KPI (for example fill rate), name at least one earlier-moving indicator the planning process can act on (for example logistics capacity stress). The source's pharmaceutical case shows capacity stress as the pressure that threatened fill rates.
6. 6Roll the vital few into a customized management index. Chapter 6 describes a way for executives to build a single index to monitor overall supply chain performance. Keep the underlying KPIs visible so a movement in the index can be traced to its cause.
7. 7Connect the PMS to the DSS and the ERP system. The source treats PMS and DSS as paired tools in the planning framework, and stresses integrating the supply chain DSS with the ERP system. Source measures from that shared data so plan-versus-actual comparisons use one set of numbers.
8. 8Institutionalize the PMS. The authors say tools and expertise must be institutionalized to produce a continuing stream of results. Assign an owner for each KPI, set a review cadence at each planning level, and re-test the set whenever strategy changes.

The source does not list the KPIs of its case firms, so this example shows how a PMS would be wired to the pharmaceutical and consumer health care case, which is real; the KPI placement is illustrative. That firm invested in hierarchical planning frameworks and DSS over many years. When business conditions changed and put significant stress on its logistics capacity, it kept very high fill rates and avoided potential revenue losses of $20 million. A PMS built for that situation puts fill rate at the top as the external effectiveness measure, tied to the customer service objective. Beneath it sits an advance-warning measure of logistics capacity stress at the tactical level, which signals trouble before fill rates fall. An efficiency measure (cost) sits alongside so that protecting service is not paid for blindly. The ceramic tile manufacturer case shows why the pairing matters: it cut annual operating costs by about 10 percent and improved fill rates together, a result only visible if both efficiency and effectiveness are measured. The capacity-stress reading is what turns the PMS into the early warning the source describes.

• If a proposed KPI cannot be traced to a stated business or supply chain strategic objective, then drop it, because the source requires alignment with business goals.
• If a function's KPI set contains only efficiency (cost) measures or only effectiveness (service) measures, then add the missing side before approving the scorecard.
• If a critical outcome KPI (such as fill rate) has no earlier-moving indicator, then add an advance-warning measure for it, because a PMS must flag potential future problems, not just report results.
• If the strategy shifts, for example from cost minimization toward high customer service levels, then re-run the strategy-to-measure selection rather than keeping the old set.
• If the management index moves but no one can name the underlying KPI that drove it, then the index is too opaque; show its component measures beside it.

• The scorecard is a long list of standard metrics (for example copied from SCOR) with no link to strategy. The tell: nobody can state which strategic objective a given KPI serves.
• Cost and service are measured in separate places and reviewed by different people. The tell: cost wins are reported with no fill-rate impact, or service targets are met with no cost visibility.
• Everything measured is lagging. The tell: problems are discovered in the outcome KPI after the damage, and no one saw capacity or similar stress building.
• The PMS is built apart from the planning process and data. The tell: KPI numbers conflict with DSS or ERP data, and planners at the operational level ignore the scorecard.
• The PMS is a one-time build and is never institutionalized. The tell: KPIs have no owners, reviews lapse, and measures stay unchanged after the strategy changes.

• ▸Function and planning level: name the function (transportation, manufacturing, logistics) and the level (strategic, tactical, operational).
• ▸Strategic objective served: state the business or supply chain objective this KPI supports.
• ▸KPI name and definition: write the exact formula and data source (ideally the ERP or DSS).
• ▸Type: mark as efficiency or effectiveness, and as internal or external.
• ▸Role: mark as outcome measure or advance-warning indicator.
• ▸Linked advance-warning indicator: name the earlier-moving measure paired with this outcome KPI.
• ▸Roll-up path: name the higher-level KPI or management index this feeds.
• ▸Owner and review cadence: name one accountable person and how often it is reviewed.
• ▸Trigger and response: state the threshold that prompts action and the planning response.

1. 1Scope the extended network first. Map the chain from supplier relationship management at one end to customer relationship management at the other, with operations in between. Add worldwide sourcing and markets, international finance (duties, taxes, exchange rates), and external shocks such as a global pandemic. Risks outside this map go unseen.
2. 2Identify risks using the strategy criteria the firm already scores, not a blank brainstorm. For suppliers, use the S&P criteria: reliability (RELIABL), material quality (QUALITY), flexibility and lead time to respond to changes in supply requirements (FLEXIBLE), partnership maintenance (PARTNERS), and cost competitiveness (COSTCOMP). For the government and society side, use ENVIRON and SEC_REG compliance (Homeland Security, OSHA, FDA). For the internal side, use SCCAPABL, NONITTEC, ITTEC, SKILLSET, and PRODIVITY. Write one or more risk statements per criterion.
3. 3Classify each risk by origin (internal or external) and by planning level (strategic, tactical, operational). The level decides who owns it and how often it is reviewed. A DC capacity shortfall is a strategic network risk, while a line scheduling disruption is operational.
4. 4Prioritize with the AHP logic. Pairwise-compare criteria only against other criteria that support the same strategy, so the weights within each strategy sum to 1. When the item count makes pairwise comparison unwieldy (the Zenith example has 12 projects), rate each item on a scale instead. Multiply importance by rating to rank the risks.
5. 5Check current data before you assess. Tactical inputs (costs, rates, capacities, product mix capabilities, forecast demand) should be refreshed at least every 6 months, as AO's standard process requires. A risk assessment built on stale network data ranks the wrong risks.
6. 6Test every proposed mitigation against the existing framework. Ask what new interfaces and communications it requires. Ask whether it duplicates a capability that already exists or truly improves a function. This avoids "one-off," ineffective decisions.
7. 7Quantify mitigation options with the tactical models. Modify the existing model to include the new option (for example, a potential new DC location with estimated costs and capacities), then evaluate its effect on the entire network before committing.
8. 8Monitor through feedback loops. Route operational-level results to the tactical level, and tactical results to the strategic level. The authors call these loops a "key and defining attribute" of hierarchical planning. Also run the scheduled annual strategic planning process, and launch an off-cycle strategic exercise when an event requires it.

The passages do not label this a risk case, but AO's planning setup shows the monitoring-and-response mechanics. AO's tactical production–DC–customer flow (PDCF) optimization model held production costs, rates, capacities, and product mix capabilities by line and plant, DC costs, rates, and capacities, freight costs between plants, DCs, and customer regions, and forecast demand by product family. The planning team updated every input at least once every 6 months. Over time it became clear that DC storage and throughput capacity would have to expand to meet rising demand, which is a capacity-shortfall exposure. Because the model was current, AO modified it to add potential new DC locations, estimated each location's costs and capacities, and used the optimization to see how each candidate changed the whole network. It could pick a location with minimal notice and run this outside the regular annual strategic cycle. The lesson is that mitigation speed depends on the currency of the planning data and models, not on the response plan written after the event.

• If a risk touches several strategies, then score it under each strategy's criteria separately. Weights are comparable only within a strategy, because criteria are pairwise-compared only against others supporting the same strategy.
• If you must prioritize more than a handful of risks or projects, then use a rating scale instead of full pairwise comparison, as the Zenith example does with 12 projects.
• If the tactical data behind a risk assessment is older than the 6-month refresh cycle, then update it before ranking or choosing mitigations.
• If a proposed mitigation tool or process duplicates an existing capability, then reject it. If it requires new interfaces, then cost those interfaces into the decision.
• If operational-level results keep deviating from tactical assumptions, then trigger the feedback loop upward and revisit the tactical model, and the strategic plan if the deviation persists.

• Counting only supplier risk: the register contains no entries for internal criteria (ITTEC, SKILLSET) or governmental and societal criteria (ENVIRON, SEC_REG). The tell is that every risk owner sits in procurement.
• Stale inputs: costs, capacities, and demand in the planning models are older than 6 months when a disruption hits. The tell is that scenario results contradict current plant or DC reality.
• One-off mitigations bought without checking fit: a new tool is added with no view of its interfaces. The tell is a capability that duplicates an existing one, or a handoff nobody owns.
• Treating all criteria as equal: the register has no weights and no ratings, so the loudest risk wins. The tell is that the ranking changes with whoever speaks last.
• Open-loop monitoring: operational and tactical findings never reach strategic planning. The tell is that the annual strategy review surprises people with problems the floor already knew about.

• ▸Risk statement: describe the event and the network node it affects (supplier, plant, DC, customer region, regulator).
• ▸Origin and level: mark internal or external, and strategic, tactical, or operational.
• ▸Strategy and criterion affected: name the strategy and the criterion code (e.g., S&P / FLEXIBLE, G&S / SEC_REG).
• ▸Criterion weight: enter the within-strategy weight; weights under one strategy must sum to 1.
• ▸Rating: score the risk on your chosen scale; use ratings rather than pairwise comparison when the list is long.
• ▸Priority score: multiply weight by rating and rank the register.
• ▸Mitigation option and data currency: state the action and the date the supporting model inputs were last updated (limit: 6 months).
• ▸Framework-fit check: list the new interfaces required and whether it duplicates an existing capability (yes/no).
• ▸Owner, feedback trigger, and next review: name the owner, the signal that escalates the risk to the next planning level, and the review date.