The supply chain at Whirlpool Corp. in 2000 was broken. Indeed, a manager there at the time quipped that among the four major appliance makers in the U.S., Whirlpool ranked fifth in delivery performance.
“We had too much inventory, too little inventory, wrong inventory, right inventory/wrong place, any combination of those things,” says J.B. Hoyt, who was then supply chain project director. He says a sales vice president approached him one day and said he’d accept even worse performance from supply systems if they would just be consistent rather than wildly bouncing back and forth between good and poor production and shipping plans.
So in 2001, Benton Harbor, Mich.-based Whirlpool embarked on a multiproject global overhaul of its supply chain systems. The metaproject remains a work in progress today, with a number of systems yet to be rolled out and some major technical issues to be resolved. But managers at Whirlpool say its success to date — including huge improvements in customer service and reduced supply chain costs – is providing the psychological and financial impetus to drive the remaining systems work.
Whirlpool CIO Esat Sezer says that by 2000, the company had grown by acquisition and geographic expansion to the point that old systems, stitched together by spreadsheets and manual procedures, couldn’t cope with the exploding complexity.
“Our supply chain was becoming a competitive disadvantage for us,” he says. Availability — the percentage of time a product is in the right place at the right time — was an unacceptably low 83%, even as inventories remained too high overall.
The homegrown supply systems were primitive and not well integrated with the company’s SAP ERP system, which had been installed in 1999, or with a legacy production scheduling system, Sezer says. And they weren’t integrated with the systems of major wholesale customers or suppliers of parts and materials. “The plans we were creating weren’t linking back into reality,” he says.
In particular, Sezer says, supply chain systems weren’t fine-grained enough, nor were they very good at juggling priorities and constraints except through slow and cumbersome manual methods. Often, they would optimize locally – a single product line at one location, for example – but not for the supply chain as a whole.
Here’s what Whirlpool was using for its North American supply chain in 2000:
• A homegrown production scheduling system, the Whirlpool Manufacturing Control System (WMCS), which was developed in the mid-1980s and extensively modified over the years.
• SAP AG’s R/3 ERP system, which was installed in 1999 and used for transaction-processing applications such as accounting and order processing.
• i2 Technologies Inc.’s Demand Planner (now called Demand Manager), which was installed in 1997 and used for demand forecasting.
• A system for distribution planning that was custom-developed for Whirlpool in the 1980s that used optimization software from ILOG Inc. Then, in 2001, Whirlpool began to implement an advanced planning and scheduling (APS) system. It included a suite of supply chain integration and optimization tools from i2 — Supply Chain Planner for Master Scheduling, Deployment Planning and Inventory Planning. Those three modules, the heart of Whirlpool’s efforts to fix its supply chain, went live in three phases over 2001 and 2002.
In mid-2002, Whirlpool installed the i2 TradeMatrix Collaborative Planning, Forecasting and Replenishment (CPFR) system, a Web-based collaboration tool for sharing and combining the sales forecasts of Whirlpool and its major trade partners — Sears, Roebuck and Co., Lowe’s Cos. and Best Buy Co.
The rollout of a component for Web-based collaboration with suppliers, based on SAP’s Inventory Collaboration Hub, is just getting under way. And Whirlpool continues to use the old WMCS for production scheduling but plans to replace that with SAP’s Production Planning module.
It’s available
By all accounts, the supply chain overhaul was a smashing success for the $13 billion company. CPFR cut forecasting errors in half. APS boosted availability in North America from 83% to 93% (it’s at 97% today), reduced finished-goods inventories by more than 20% and trimmed 5% from freight and warehouse costs. Whirlpool declined to discuss the cost of the projects.
Managers at Whirlpool give much of the credit for the success of these projects to a close partnership between the IT department and the business units. Says Hoyt, “It was one of the first times the IT community didn’t say, ‘OK, here’s your tool.’ We said the tool had to do x, y and z. We did the requirements analysis together.”
Whirlpool considered standardizing completely on SAP for all ERP and supply chain systems in North America, but i2 ultimately got the nod for the APS system, the critical part needed to fix the company’s availability and inventory problems. “There was a lot of back and forth, but after a long harangue and discussion of our business requirements, we settled on the i2 tool set in North America,” Hoyt says.
But while i2 was seen as being more capable than SAP for handling the fine-grained optimization, constraint-based planning and prioritization that the business units wanted, it was far from ideal from an IT perspective.
The APS system would cost IT, whose budget is about $190 million, more than an all-SAP supply chain because there would be less integration, more systems interfaces and more skills to maintain in-house. Plus, IT was worried about i2’s deteriorating financial condition.
Whirlpool had already standardized on IBM AIX application servers and zSeries mainframe database servers for supply chain systems and had put systems for all its global operations in a single data center in Benton Harbor. Now it was time to standardize on software.
So in 2001, a mandate came from the CIO, via Whirlpool’s Executive Committee, that supply chain modernizations henceforth would be based entirely on SAP. In particular, new systems planned for Europe for 2003 and Latin America would use SAP’s Advanced Planner and Optimizer rather than the more capable but costly i2-based APS system used in North America.
And they were to use SAP’s NetWeaver for Web collaboration with suppliers and trade partners rather than North America’s TradeMatrix CPFR. Vivek Mehta, a lead supply chain analyst at Whirlpool, says SAP may catch up with i2 in its optimization capabilities, but in the meantime, i2’s financial condition is worrisome. “There were 10 guys at i2 that we interacted with, and some of them are gone now,” he says.
“There’s lack of continuity.” “We have this challenge, where the IT organization is pushing for everything to be SAP, but the business, on the other hand, is going for whatever brings them value,” Mehta says. “They are now used to the optimal plan, the high service levels, the lower inventories. So if we bring in something and say their availability will go down by a couple of points, no way will they buy that.”
Sezer says Whirlpool will probably replace i2 with SAP “eventually” but is in no hurry. “We’d like to get the return out of that investment before making any platform decisions,” he says.
Sezer says that in the four years since Whirlpool standardized on IBM and SAP as “strategic partners,” revenue has increased on average $1 billion per year and IT expenses have fallen 6% per year. He says there are several joint development projects under way involving all three companies.
But for the time being, the combination of SAP and i2 works well for Whirlpool, far better than the legacy tools of a few years ago. Sezer says the company’s supply chain is now a competitive advantage. “On a global scale, to be able to manage all your operating platforms, I’m not aware that any of our competitors have that today,” he says.
