"One of the key values from River Logic is the ability to bring our functional teams data that they can make actionable.We want them to understand the opportunity cost of producing and selling one more or one less of that product, and River Logic enables that for us."
— Vice President of Planning
Executive Summary
The company is a Fortune 1000 manufacturer of consumer products. It owns several well-known consumer brands, serves most segments of the North American market, and is relatively integrated: it develops, manufactures, and distributes most of the products it sells.
The company has grown significantly over the last 10 years under the current management team. That fast growth also made it harder for executives to make the best decisions. After examining the leading enterprise resource planning (ERP), supply chain management, and analytics products, management concluded they would not deliver the competitive advantage it wanted.
Typical unanswered questions included:
- How can we achieve the most profitable product portfolio?
- Where should we add or subtract capacity (plants, production lines, distribution centers, etc.) to maximize ROIC and profits?
- Which manufacturing plants should make which products?
- What inventory strategy yields the highest cash flow while maintaining acceptable inventory turns?
The company built five models in the Enterprise Optimizer® (EO) Decision Engine:
- A long-range planning model to evaluate strategic issues (e.g., capacity, capital expenditures, and product portfolio)
- A medium-range planning model to determine inventory strategy and tactical issues, including which plants should make which products
- An operational planning model to define production sequencing and shift scheduling
- A distribution model to determine the optimal distribution strategy
- A truck loading and handling model to maximize efficiency and minimize costs
To date, the medium-range and loading models have delivered significant quantitative and qualitative benefits, resulting in an ROI of 1,000% to 2,000%.
Qualitatively, the models produced better, faster decisions and insights that changed the way the company makes decisions. Management now understands that only a system-wide view of financials and operations, one that includes business constraints, yields the best decisions.
To make the investment a success, the company committed the following resources:
- A senior-level chief planning officer with cross-functional responsibilities to manage the initiative
- A capable, cross-functional team committed to the solution
- Stakeholders from all relevant areas, brought into the process early
- A data system with complete, high-quality structured data, built to feed the Decision Engine
The EO Decision Engine has been a major success for the company. The following sections describe the company's issues and results.
Business Challenges
The company's operations are relatively integrated. Most products are designed by its R&D department and manufactured in house across several North American facilities. The company also owns and operates several distribution facilities and a fleet of trucks to deliver products to its customers.
The product line consists of 300+ SKUs manufactured in house, plus 20+ SKUs private-labeled by other manufacturers. Consumption depends heavily on seasons, holidays (e.g., the school season), and other factors such as consumer preferences and weather. These demand swings require careful planning and inventory management.
Each manufacturing facility can make most SKUs, but not all do, because processing and material costs differ widely. Several distribution centers hold inventory and ship to over 4,000 locations. Customer orders arrive weekly, and the company delivers within 4 days of receiving an order.
300+
Manufactured SKUs
20+
Private-label SKUs
Over 4,000
Stores carry its brand
The company has a strong IT department. Before deploying the Decision Engine, it had already implemented an ERP system, an MES, a logistics and supply chain management tool, a financial planning application, and several other analytical/LP applications.
Even with all of these systems, management still could not answer pressing questions:
- How can we maximize profitability of the product portfolio?
- Which customers should we serve, and how?
- Where should we add or subtract capacity to maximize ROIC and profits?
- Which manufacturing plants should make which products?
- How can we maximize logistics efficiency while still maximizing profits?
- Which production and shift-staffing schedule would maximize profitability?
The company considered further SCM and ERP investments. Upper management and IT quickly chose River Logic instead: it was the only tool that provided a system-wide view of operations and financials at the same time. Management felt standard ERP and SCM systems would not provide the competitive advantage it sought, and it saw the Decision Engine as the right complement to its Six Sigma initiatives.
Decision Engine Deployments
The company built five models in the EO Decision Engine. Three help the business plan holistically for strategic, tactical, and operational requirements across the system. Two more address distribution and logistics within the boundaries set by the strategic models. Each model answers its own questions while respecting the decisions made above it.
Long-Range Planning Model
This model takes a long-term view to optimize capital investment and capacity decisions. It answers questions about specific scenarios, but more importantly it finds the combination of investments that optimizes ROI and profitability. Typical questions include:
- When and where could we add manufacturing plants to maximize ROI?
- How can we invest in additional production lines to increase profit and maximize ROI? Which capabilities maximize return?
- When and where should we add a distribution center to maximize profits and ROI while maintaining quality requirements?
Medium-Range Planning Model
This model is constrained by the capabilities set in the long-range model and by future demand forecasts. It takes a system-wide view of operational requirements and profit impact over one year to find the best tactical decisions in each period of a 13-period horizon:
- What should our inventory strategy be, given inventory requirements?
- What should be produced, and at which plant?
- Which distribution centers should carry which products?
- Which products should be made versus bought?
Short-Term Planning Model
This model finds the most profitable production plan across 60+ production lines, given production costs, constraints, and sequencing requirements. Sequencing matters a great deal to the company: line changeovers range from 30 minutes to 20+ hours, depending on product sequence.
Distribution Model
The company distributes products from several distribution centers to over 4,000 customer locations. This model evaluates distribution rules, delivery dates, and transportation routes to find the most profitable distribution plan, given customer constraints. The medium- and long-range plans constrain this model by defining capacity, product mix, and production plans.
Truck-Loading Model
This model optimizes pallet sizes, loading and unloading costs, and available truck space.
[Image: diagram of how the five models connect. The long-range model (long-term capacity, capital investment, new product opportunities) passes maximum capacity, product line, and plant constraints to the medium-range model (production optimization, inventory strategy and rules, transportation guidelines, make vs. buy). The medium-range model passes product availability, production by plant, and inventory guidelines to the operational model (production planning and sequencing, shift scheduling and staffing), and capacity and product line strategy to the distribution model (distribution optimization, customer service strategy). Shipping schedules and requirements feed the truck-loading model (materials handling, truck loading decisions).]
The company uses a product data system to gather, structure, and clean the data fed to the models. It imports data from the ERP, MES, and logistics systems, plus demand forecasts built in spreadsheets. Scenarios are run and stored in databases for easy comparison.
[Image: data flow diagram. Transactional data from ERP, SCM, and databases flows into product data systems (operational capabilities, raw material costing, new product opportunities, SKU-level production requirements, fixed and variable costs, pricing by customer and location, fixed and variable transportation costs). Combined with business knowledge (rules and constraints, demand forecasts, KPIs, new scenarios), the Decision Engine models turn this into a holistic model of operations and finances, calculate financial impact, optimize profit across thousands of options, and support ongoing decisions and scenario analysis. Outputs are reports for specific analyses, ongoing recommendations, and KPI monitoring.]
Benefits of Adopting the EO Decision Engine
This Fortune 1000 company has realized major benefits, including better decision-making and strong financial returns. Insights from building and using the models have led to new and better ways of managing the business:
- Higher profits: The medium-range and truck-loading models have generated as much as $5m in profit improvements, directly attributed to decisions enabled by the Decision Engine.
- Better decisions: Decisions are made faster and with more certainty, which means lower risk, better quality, and greater return. Decision-making is also more transparent, which leads to broader acceptance and more robust execution across the company.
- Transformational insights: One plant manager recommended transferring an entire product line to another plant based on profit impact. Before the Decision Engine, the company assumed that a plant capable of making a product should make it to serve nearby customers. That was not the case. The analysis showed that the efficiency gained by making the product at another plant more than offset the added transportation cost. The plant manager recommended the change even though it hurt her own metrics, which were based on plant revenue over plant costs at the time. Insights like this have led management to think differently about the business.
Lessons management drew:
- All decisions should consider profit impact on the entire system. That requires considering operations and financials together, and software that can model the business holistically is essential.
- Strategic, tactical, and operational decisions should be part of one overall plan, linked by a solid understanding of opportunities and constraints. Inventory requirements, for example, must be considered for optimal decisions, and tactical and operational decisions should be constrained by strategic ones.
- Objectives and incentives should align with the decisions that most affect financial performance, including profits, quality, and delivery requirements. A plant manager should not be measured on plant throughput or revenue, but on his or her contribution to overall profit.
Key Success Factors in the Deployment
The company identified several best practices. The most important were picking the right executive champion, deploying a capable team, involving all stakeholders early, and investing in the data required.
Assigning the Right Executive Champion
The Chief Planning Officer is responsible for aligning the most important cross-functional processes and for driving profit and performance improvement across the company. The CPO has a strong background in manufacturing, maintenance, and supply chain management. The Decision Engine has made it much simpler for the CPO to deliver on commitments by providing a system-wide view of realistic profit improvement opportunities. In the early stages of deployment, it is critical that a senior executive steer the organization toward buy-in.
[Image: org chart. The SVP Planning (CPO) sits alongside the SVP Manufacturing, SVP Sales & Marketing, SVP Transportation, and CFO, reporting to the President, and owns operational planning, order fulfillment, demand forecasting, and managerial accounting.]
Deploying a Capable Team
The company assigned a strong cross-functional team, supported by a consulting expert in manufacturing and managerial accounting. The team leader has a solid supply chain management background and is supported by two dedicated analysts: an MBA graduate who structures and develops the models using his business knowledge, and an IT professional who makes sure data requirements are met.
Involving All Stakeholders Early and Investing in Data
Everyone with a stake in the model should be involved early. The company selected a representative from each plant to take part in model structuring, development, and scenario analysis. This ensured the right input from the manufacturing organizations and built organizational buy-in. Involving key accounting staff early was also important to build credibility in the projected numbers that validate the model's output.
Conclusion
The company is committed to continuous improvement, and the modeling and scenario analysis in the EO Decision Engine meet that need. Because one model of the business answers questions across every planning horizon, the organization keeps finding new ways to do better.
The company is now on the way to much more profitable performance. Management believes it will significantly outperform its peers on all relevant operational and financial metrics for years to come.
About River Logic
River Logic builds the Enterprise Optimizer® (EO) Decision Engine, which turns business goals into defensible, execution-ready decisions, each with the receipt: the binding constraints behind it and a trace back to the source data. Built on 25+ years of optimization R&D, one model of the business answers questions across planning domains, from network design and capacity to product mix and capital allocation.






















