Plant to Enterprise in a multi-site environment

2. Plant to Enterprisein a multi-site environment Peter Luttje Bert Wissink

3. Agenda • Introduction • What is our PI mission? • What have we encountered? • How did we solve it? • What did we learn? • What are the benefits?

4. 1. Introduction • Companies involved • Akzo Nobel Base Chemicals BV • Sub Business Units: Chlorine, MCA, Energy, Salt and Ecosystems • Atos Origin Nederland BV • Enterprise Solutions unit MES

5. 1. Introduction: AkzoNobel • Serving customers throughout the world with coatings and chemicals • € 14.4 bln sales • 60,000 employees in more than 80 countries • Committed to delivering Tomorrow’s Answers Today • Headquartered in Amsterdam • Global Fortune 500 company • Listed on the Euronext Amsterdam stock exchange • Top position on the Dow Jones Sustainability Indexes and FTSE4Good

6. Total revenues € 900 mln, excl. JV’s 1,650 Employees Business areas: Salt, Energy, Chlor-Alkali, Ecosystems, MCA Leading position in Europe for chemical transformation salt, chlorine and caustic lye for industrial applications Worldwide number one position in monochloroacetic acid (MCA) Products play a key role in the production of glass, textile, detergents, building, automotive, pharmaceuticals, plastics and disinfectants 1. Introduction: Akzo Nobel Base Chemicals BV

7. 1. Introduction: Akzo Nobel Base Chemicals BV LeMoyne Ohmi Taixing Skoghall Mariager Delfzijl Ibbenbüren Deventer Rotterdam Hengelo Arnhem Bitterfeld Active in 7 countries Manufacturing (16 plants/ 9 locations) 3 Joint ventures 2 R&D locations

8. 1. Operational excellence in an integrated business model Chlor Alkali Salt and Energy Ecosystems and MCA FeCIx H2 HCI Electricity Co-Generation Fuel Electrolysis Cl2 Steam MCA Internal Customers NaOH HypoCI Dissolving underground salt Brinepurification Salt Salt External Customers

9. Agenda Introduction What is our PI mission? What have we encountered? How did we solve it? What did we learn? What are the benefits?

10. 2. Our PI Mission • Run a project program to have PI working in all plants by the end of 2010 • Plant to Enterprise Challenge • 4 sub Business Units • 2 Continents • 5 Countries • 8 Sites • 19 Plants • Multiple languages and cultures • 1 Production chain • 1 SAP system • 1 HQ in Amersfoort (NL)

11. 2. Our PI Mission Linking Organizations to IT standards

12. 2. Mission: Where we come from ERP Navision SAP FC SAP BC SAP Salt SAP Energy Scattered Progres Progres MES PHD PHD SQL Excel Excel PHD Excel Excel Excel PI Fox-com Fox-com PI2 PHD Fox-com Honey- well Fisher RS/3 DCS Honeywell Emerson Emerson DeltaV ABB Foxboro ABB Foxboro Honey-well Honey-well Valmet Foxboro Foxboro Emerson Plant ChlorineIRN Chlorine RDM EnergyDZL EnergyHGL EnergyRDM ChlorineBIT ChlorineDZL ChlorineHGL ChlorineSHL MCASHL SaltDZL SaltHGL SaltMGR MCAHGL MCATXN Germany Netherlands Sweden Netherlands Denmark Netherlands China

13. 2. Mission: Initial Objective • Harmonize on • One MES platform • KPI definitions • Production Accounting • Interfacing with SAP • One Way-of-Working • By deploying • Standard software where possible • And striving for • Low Total Cost of Ownership

14. 2. Mission: Projected Result in 2010 SAP ERP Solution “X” Production Accounting OSIsoft PI MES DCS ABB Emerson Honeywell Metso Honeywell ABB Emerson Emerson Emerson Honey-well Honey- well Honey-well Plant ChlorineIRN Chlorine RDM EnergyDZL EnergyHGL EnergyRDM ChlorineBIT ChlorineDZL MCA DZL ChlorineSHL MCASHL SaltDZL SaltHGL SaltMGR MCATXN Germany Netherlands Sweden Netherlands Denmark Netherlands China

15. Agenda Introduction What is our PI mission? What have we encountered? How did we solve it? What did we learn? What are the benefits?

16. 3. What have we encountered? • Project Organization • Corporate program • Local projects • Harmonization • Multiple plants on 1 PI system • Multiple languages and cultures • Visualization • Integration • Network load (LAN, WAN) • Process Control Layer (security) • SAP Interfacing • Production Accounting • Transaction based vs. real-time • Find a suitable solution

17. Agenda Introduction What is our PI mission? What have we encountered? How did we solve it? What did we learn? What are the benefits?

18. 4. How did we solve it? Project Organization Fixed core project team One Akzo Nobel focal point One Atos Origin project manager Local focal point per project Harmonization by balancing Standardization Tag naming convention PI security on tags and data Corporate PI Web enabled portals Differentiation Reference manuals in local languages Local PI Portals

19. 4. How did we solve it? • Integration • Network load: Prioritize PI network traffic • Security on Process Control Layer: Firewalls • SAP: OSIsoft RLINK • Production Accounting • Standard OSIsoft modules did not fit our purpose • Tailor Made solution • One Way-of-Working

20. End of Part 1

21. 1. Introduction – Part 2 • Companies involved • Akzo Nobel Base Chemicals BV • Sub Business Units: Chlorine, MCA, Energy, Salt and Ecosystems • Atos Origin Nederland BV • Enterprise Solutions unit MES

22. 1. Introduction: Atos Origin • Leading IT services company • Providing consulting, systems integration and outsourcing solutions • Delivering business outcomes globally • Annual revenues of € 5.8 billion • Over 50,000 employees • In 40 countries worldwide

23. North America South America Asia Pacific Central Europe Africa 4.000 4.000 200 700 1.900 Spain 6.000 1. Introduction: Atos Origin - Global Presence UK 6.200 Benelux 10.200 France 15.800 In total more than 50.000 employees worldwide

24. Agenda Introduction What is our PI mission? What have we encountered? How did we solve it? What did we learn? What are the benefits?

25. 4. How did we solve it? Production Accounting PI Portals SAP integration

26. 4. Solutions: Production Accounting • Definition: “ To account for intake, produced products, available stocks and delivered goods ” • Characteristics: • Interactive transactional way-of-working • Based on real-time PI data (pipeline customers) • Needs verified data (€’s involved) • Results are input for invoicing through SAP • Typical users are plant controllers

27. Production Accounting Other software Production Accounting Data Production Accounting Calculation Engine Production Accounting Production Accounting Reporting Results Calculate Manage Formulas Manual Corrections Excel + Production PI DataLink PI Production Formula Manual Input Accounting Accounting data Parser Formulas Reports Collect Fileloader Start Reports External Systems External data Performance Totalizers Equations 4. Solutions: PACE Architecture Process Control Layer PI Server PI Interface Node PI interface PI Plant data Process Control System Local Buffer Standard OSIsoft PI

28. 4. Solutions: PACE initial setup

29. 4. Solutions: PACE future setup

30. 4. Solutions: PACE screens

31. 4. Solutions: PACE screens

32. 4. Solutions: PACE Benefits • Ease of Use • Management of calculations by end-users • Validations and corrections • Testing of formulas • Starting-points achieved • Automatic calculation sequence • Interactive recalculation • Support monthly calculations • Calendar based • Other Benefits • Support for periodic closures • Support for freeze of data • One Way-of-Working

33. 4. How did we solve it? Production Accounting PI Portals SAP integration

34. 4. Solutions: PI Portals

35. 4. Solutions: RtWebParts Maturity Examples

36. 4. Solutions: RtWebParts Maturity Examples

37. 4. How did we solve it? Production Accounting PI Portals SAP integration

38. RLINK in practice • Prerequisites • Make clear functional specs • SAP configuration needs to be ready • Lessons-learned • Implementation “a tough nut to crack” • Tricks and work-arounds needed • Use it as it is intended, don’t cross borders • Configuration GUI is too “buggy” • User Manual is too technical (not “accessible”) …once running it’s very stable

39. End of part 2

40. Agenda Introduction What is our PI mission? What have we encountered? How did we solve it? What did we learn? What are the benefits?

41. 5. What did we learn? • Maturity of RtWebParts • Prepare well for RLINK • Reconsider Production Accounting setup • Importance of availability • Importance of validated data

42. Agenda Introduction What is our PI mission? What have we encountered? How did we solve it? What did we learn? What are the benefits?

43. 5. Benefits • Improved Harmonization • One Way-of-Working • Uniformity on Production Accounting • Plant data available for every seat at every site • Improved Insights • Corporate Management dashboards • View on overall performance • View on consumptions, stocks and deliveries • Improved Business Processes • Plant benchmarking possibilities • Improved support for logistics department • Improved Production Planning • New Opportunities

44. 5. Benefits: Future Plans • Technical Improvements • Upgrade RtWebParts • Improve PI availability with High Availability PI • Realize PI Dev/QA environment • Improve data integrity • Support Excellence programs • Study PI - SAP Plant Maintenance opportunities • Study Condition Based Maintenance feasibility

45. Conclusions • Project success • Management commitment • Fixed core project team • Local involvement • Availability of plant employees • Flexibility and anticipation • Standardization and differentiation well balanced • PI and PACE success • Improved our business • Good fit • Opens doors to new opportunities

46. Final Remark Plant to Enterprise = Empowering Business in Real Time

47. Peter.Luttje@AkzoNobel.com +31 (0)6 5322 0468 Bert.Wissink@AtosOrigin.com +31 (0)6 5158 2000