Advanced Micro Devices Inc. (AMD, Sunnyvale, CA) is one of the world’s largest semiconductor manufacturers, with more than $5.6 billion in revenue in 2006. In 1984 AMD installed a mainframe-based enterprise work in progress (WIP) management system and had used it ever since. That is, until Clay Cipione, AMD’s chief information officer, decided enough was enough and that the 23-year-old system had to go.
That was no mean feat, given how deeply engrained in an organization a system with that kind of tenure tends to become. But by working with experts from Mountain View, CA-based Serus Corp., the AMD IT team succeeded in retiring the legacy system altogether, replacing it with Serus’ enterprise solution code-named INCA (short for Inventory Control and Accountability), an integrated manufacturing, inventory tracking and financial consolidation system. The project resulted in an immediate return for AMD, along with a host of additional benefits. Chief among them is more accurate, reliable inventory status reporting, which has a ripple effect, improving a myriad of other manufacturing and financial operations. The new tool also enhanced AMD’s ability to quickly make updates to suit its various and changing requirements.
“We had a 23-year-old piece of software that was incredibly antiquated, incredibly hard to maintain and almost impossible to extend,” Cipione says. He credits Rick Carlson, AMD’s director of IT, as well as Serus, for taking a complex project and implementing it with no major snags. “This went like clockwork. Between Rick and Serus, they made it look easy.”
Out with the OldMainframe-based WIP systems present numerous problems. For one, mainframes are expensive to maintain, both in terms of ongoing software costs and in finding and retaining people with the skills required to operate them-a vanishing breed. The systems also are difficult to update because of fixed data fields.
As a result, a lot of extra effort is needed to maintain accurate inventory records, and consolidating all the appropriate information into any given report can be a challenge. The legacy system provided less-than-desirable visibility to costing systems, which made closing the books each month a time-consuming chore.
Serus Gets a TryIn September 2005, AMD signed on Serus to replace the legacy system. The work was to be done in two major phases: first an architectural overview and needs assessment, followed by a proposal for a future architecture.
The first phase took three months, during which a Serus team interviewed some 200 AMD employees to find out exactly how they used the existing WIP system-and any ancillary shadow tools that had cropped up along the way. “That’s where Serus produced what I think is one of the better pieces of work I’ve seen in 48 years in the business,” Cipione says. The work documentation produced by the Serus team, led by Geoff Annesley, vice president and general manager of enterprise solutions, reflected the requirements as well as the functional and physical design of the proposed application. “That’s what really sold us,” Carlson says. Together, Serus and AMD got into detailed discussions with factory personnel to find out exactly how they did their jobs, how processes worked, what was working with the current system and what they would like to see in a new solution.
“We had interactive workshops throughout the process,” Carlson says. “About every six weeks we’d go and spend a week at a site and play back what we heard the previous time, demonstrate the software functionality and then refine it.”
By the end of the process, Annesley and his team had impressed AMD with their understanding of their problem. “The fact that they could literally dissect our problem and articulate a solution gave us confidence that they really had a great comprehension of our needs,” Cipione says.
He was also impressed by the enthusiasm of the Serus team. “They had a Coast Guard-like attitude: Got to go out, don’t have to come back,” he says. “They really wanted to do the work for us and demonstrated great capability to do it in the design phase.”
Corralling Reluctant WarriorsIts quality design work earned Serus the right to proceed to the next step of the project: implementation of its proposed solution.
In January 2006, AMD put a stake in the ground: it would implement the new Serus INCA system by January 1, 2007. “That was an imperative to march to,” as Carlson puts it. “We missed that date by about 37 days, but we came close, so I’d say it worked.” Implementation meant changing the way AMD had done business for the last 23 years. Knowing that a change of such magnitude would be difficult, the company formed a steering committee with high-level representatives from multiple crucial departments, including IT, supply chain, global logistics and finance executives from each of the three countries involved. Cipione was the IT representative while Carlson served as technical secretary and coordinator for the committee.
When implementation began, the steering committee would meet monthly; by the time the project was complete, they met daily. “Nothing happens in a large global company without that kind of focus,” Cipione says. “There were a lot of reluctant warriors along the way, but we managed to overcome that by dragging them in for fireside chats and encouraging them to play ball.”
Implementing INCA meant tying the system in with various existing AMD applications, including SAP, cost accounting, factory MES systems and various databases. “You have to get down to the transaction level and understand what happens on the other side of the fence,” Carlson says. He describes the process as a series of punch list activities to complete. “They happened without any significant problems,” he says.
Along the way, the remaining undocumented systems came to light and had to be accounted for in the new setup.
Reaping the BenefitsToday, AMD has complete visibility into all aspects of its enterprise manufacturing processes, including production, engineering and development data. Day to day, the system brings the most benefit to employees on the factory floor and those involved in inventory control. Product lifecycle management involves managing the flow of a product from development to production to obsolescence. INCA enables AMD to keep on top of each process along the lifecycle in ways that its legacy system simply could not.
AMD also can detail in the INCA part chain management system what type of data should be gathered at each step in the process and what information is required for a lot to move from one stage to another. The system keeps track of all required validations, making it simple to move a lot to the next stage when it is ready. Previously, some of that validation data might be housed in the legacy mainframe system, but much of it existed in other systems. Now, AMD has a complete part chain, from start to finish.
INCA also provides for a reconciliation process, to identify and correct any errors in inventory levels. Every four hours, AMD MESs take a snapshot of inventory levels while INCA does the same. Then the two are compared and if any discrepancies exist, INCA provides a process for digging into various transactions to root out the cause.
The multiple audits built into INCA also help AMD comply with its internal control requirements. Security is provided based on the group employees belong to and their location. Each operator has to be authenticated through INCA’s built-in LDAP directory and the system tracks all changes made as well as who made them, providing a clear audit trail.
Such a system brings increased efficiency to AMD, with improved accuracy in inventory status, which helps with planning and financial reporting for sites around the globe.
Cipione notes that INCA, with its improved accuracy and ability to act as a sole source of data for sites around the globe, also helps AMD to close its books much quicker each month. “It’s hard to quantify that in terms of dollars and cents, but suffice to say there are certainly benefits to it,” he says.
Cost SavingsThe benefits that AMD has been able to quantify are considerable, starting with the substantial savings from retiring the mainframe. And it was indeed retired, not repurposed. “It’s dead as a doornail,” Cipione says. “We kept the faceplate; that’s all that’s left.”
In contrast to its legacy system, INCA is written in Java, runs on AMD-based computers and uses SQL databases. That kind of adherence to industry standards makes INCA far easier and less expensive to support than the proprietary mainframe system it replaced. INCA has also reduced inventory variances at AMD, which improves its supply visibility, control, risk management and valuation accuracy.
- Serus Corp.
Report Abusive Comment