Question

Case Study 1: American Water Keeps Data Flowing

American Water, founded in 1886, is the largest public water utility in the United States. Headquartered in Voorhees, N.J., the company employs more than 7,000 dedicated professionals who provide drinking water, wastewater and other related services to approximately 16 million people in 35 states, as well as Ontario and Manitoba, Canada. Most of American Water's services support locally managed utility subsidiaries that are regulated by the U.S. state in which each operates as well as the federal government. American Water also owns subsidiaries that manage municipal drinking water and wastewater systems under contract and others that supply businesses and residential communities with water management products and services.

Until recently, American water's systems and business, processes were much localized, and many of these processes were manual. Over time, this information environment became increasingly difficult to manage. Many systems were not integrated, so that running any type of report that had to provide information about more than one region was a heavily manual process. Data had to be extracted from the systems supporting each region and then combined manually to create the desired output. When the company was preparing to hold an initial public offering of its stock in 2006, its software systems could not handle the required regulatory controls, so roughly 80 percent of this work had to be performed manually. It was close to a nightmare.

Management wanted to change the company from a decentralized group of independent regional businesses into a more centralized organization with standard company-wide business processes and enterprise-wide reporting. The first step toward achieving this goal was to implement an enterprise resource planning (ERP) system designed to replace disparate systems with a single integrated software platform. The company selected SAP as its ERP system vendor.

An important step of this project was to migrate the data from American Water's old systems to the new platform. The company's data resided in many different systems in various formats. Each regional business maintained some of its own data in its own systems, and a portion of these data was redundant and inconsistent. For example, there were duplicate pieces of materials master data because a material might be called one thing in the company's Missouri operation and another in its New Jersey business. These names had to be standardized so that every business unit used the same name for a piece of data. American Water's business users had to buy into this new company-wide view of data.

Data migration entails much more than just transferring data between old and new systems. Business users need to know that data are not just a responsibility of the information systems department: the business "owns" the data. Business needs determine the rules and standards for managing the data. Therefore, it is up to business users to inventory and review all the pieces of data in their systems to determine precisely which pieces of data from the old system will be used in the new system and which data do not need to be brought over. The data also need to be reviewed to make sure they are accurate and consistent and that redundant data are eliminated.

Most likely some type of data cleansing will be required. For example, American Water had data on more than 70,000 vendors in its vendor master data file. Andrew Clarkson, American Water's Business Intelligence Lead, asked business users to define an active vendor and to use that definition to identify which data to migrate. He also worked with various functional groups to standardize how to present address data.

One of the objectives of American Water's data management work was to support an enterprise wide business intelligence program based on a single view of the business. An analytical system and data warehouse would be able to combine data from the SAP ERP System with data from other sources, including new customer information and enterprise asset management systems. That meant that American Water's business users had to do a lot of thinking about the kinds of reports they wanted. The company had originally planned to have the system provide 200 reports, but later reduced that number by half. Business users were trained to generate these reports and customize them. Most financial users initially tried to create their reports using Microsoft Excel spreadsheet software. Over time, however, they learned to do the same thing using SAP Business Objects Web Intelligence tools that came with the system. SAP Business Objects Web Intelligence is a set of tools that enables business users to view, sort, and analyze

business intelligence data. It includes tools for generating queries, reports and interactive dashboards.

Case Study 2: American Water Keeps Data Flowing

Give some examples of problems that would have occurred at American Water if its data were not "clean"?

Answer 1

American hater 1ssues t i the data Weue not clean Points to consider - The business coveus a Jarge genglaphy tendung to 16 mill people in 35 states Ontaruo Mantoba in Canada - Local rebidential aueas seuices - Recent Scen auio aue albo puovided Systems Businesses wene locaized and MANUAL No systems integuated nformation in she form Extrapelating a uepert tor mone than one uegion a heauily manual puocesss was inadequake s kms do perfetmung legulatory contots for public fferin stock n 2006 Management arpixahon Centrralizahion the eganizaien funehionalily Souution ERP: Enterpise Resoure Pl Plannung csingle To ueplace disparate sys with a ntigrated sw platfelm SAP DATA Caning ceaning Requrement tor data

Fer an ingrated sw platfeim it that the data O the bame toumat to enbure Consitenuy Collaberated om dlerent that it eglens bo Headilyavailable in a Ange ur ce . Rermoual Hedundant and inconsistent data tandardizaton eaon ece infermbtion i generially Master Matenuau the data o thal undestood the data needs to be dome duung Reiew miglation preciesty underbtoed ouich Viequiiet t needb o be and which u gre.ce df JunEcescauy Psiobable puoblems iData were not deaned data is ) Redundant, unusable data wRould hawe Koatedl in the database 2) Analysib would have been skewed afterxeet afected due to unnecessary date (3) Standaydizahon wab not done possible that dupuicate data tom uegional mater data tiles okould have ce ed the itwas et the entire database accusra y

4 wthout Data dleaning the whoe guocess f eotablshment would have become data migtahon and ERP complicate, tedious and ineficient (5) using toob lile SAP Business Objects Web Intelligence to vieo, sort and data helps the managenmen anatyze he achi eve its goal to eficienty tablis the Buiners Intelligence progtam clean data, optimizah'on tem epetts from tD halt ie 1OD wold Jossi ble (7A clean data fastens the data 6 Oithout a the nD a value to 200 not hawe been analyois processintuen enabling taoter eticient and mae data analyss utputs u wrth a accurate