1. Sangyoung Mo, et al. 1 PI Introduction on ERP Project in KHNP Sangyoung Mo 1 and Taegheon Kwag 2, KOREA HYDRO & NUCLEAR POWER CO., LTD. PI Introduction on ERP Project in KHNP May 13, 2003 Sangyoung Mo 1 and Taegheon Kwag 2 1 ERP Project Office, ERP Project Division, 2 Maint. & Eng. Office, Power Generation Team, Headquarters, KOREA HYDRO & NUCLEAR POWER CO., LTD.

2. Sangyoung Mo, et al. 2 Outline oIntroduction l Introduction of KHNP l ERP Project in KHNP oPI Installation l Scope l System Layout l Data Flow l Interface with SAP oTrouble-shootings oConclusion

3. Sangyoung Mo, et al. 3 Background and Information of KHNP (1/2) oKorea Electric Power Corp. (KEPCO) officially split up its power generation sector into 6 separate companies on April 2, 2001 by the Korean government’s electric power industry restructuring program. oThe goal of the restructuring is to provide users with stable supplies of high-quality and low-cost electricity by maximizing the competitiveness and efficiency of the power generation companies. l Korea’s electric power exchange market have been operating since April 2002. Although it is currently a Cost-based pool, it will be changed into TWBP (Two Way Bidding Pool) market by April 2004 oAs one of the subsidiaries, KHNP has been formed combining hydro and nuclear generating facilities of KEPCO. l operate 18 nuclear reactors in 4 sites, and 16 hydro plants l 2 new reactors are under construction l plan to build an additional 10 reactors by 2015

4. Sangyoung Mo, et al. 4 Background and Information of KHNP (2/2) oInstalled nuclear capacity : 15,716 MW (as of the end of 2002) l 29.2 % of the nation’s total installed capacity oNuclear power output : 119 billion kWh (in 2002) l 38.9 % of the country’s electricity consumption oAverage capacity factor of NPPs : 92.7 % (in 2002) PWR PWR PHWR Ulchin # 1, 2, 3 & 4 # 5 & 6 Wolsong # 1, 2, 3 & 4 Kori # 1, 2, 3 & 4 PWR Yonggwang # 1, 2, 3, 4, 5 & 6 In Operation : 18 (15,716MW) Under Construction : 2 (2,000MW)

5. Sangyoung Mo, et al. 5 Background and Objective of ERP Implementation Strengthen Competitiveness through Implementation of Advanced Business Management Technique Establish Profit Oriented Management & Transparent Accounting Method Need for Implementation of Business Process Innovation for Utility Industry Implementation of BPR & ERP Management Transparency/Implement ation of profit oriented business system Gain Comparative Advantage in Power Generation Project Background Innovation Program Project Objective Changes in Utility Industry Business Environment  Graduate Dispersion of Demand & Open Competition Introduce Advanced Business Mgt. Technique Integrate/Implement developed information system

6. Sangyoung Mo, et al. 6 Brief Process of ERP Project o2001.4.2 : Split up of KEPCO into KHNP o2001.6.1 : Launch ERP project team o2001.12.31 : Sign contract (Anderson consortium) o2002.1.14~2.28 : SAP module training o2002.4.1 : Commence 7 key BPR processes o2002.4.10 : Complete As-is analysis o2002.7.31 : Complete To-be design o2002.10.24 : Contractor change to BP (BearingPoint) consortium o2003.1.20~1.25 : Complete final integration test o2003.1.29 : Decide on ERP system title as DREAMS (Digital Realtime Enterprise Asset Management System) o2003.2.8 : ERP system open (on Ulchin Plant 2) o2003.4.12 : Roll-out on All plants excluding Ulchin Plant 2

7. Sangyoung Mo, et al. 7 PI Introduction Scope Server Side  PI UDS : Data Storage (6 PI Servers) Interface Side  PI RDBMSPI I/F : Site Interface I/F  PItoPI I/F : I/F between head office and each site  PI API : App. I/F (Manual input, SAP CO module I/F)  PI Activeview : Web I/F  PI RLINK : SAP PM module I/F Client Analysis Tool  PI DataLink : MS Excel I/F  PI PrecessBook : Mimic Implementation ✤ We intended to introduce PI ICE for web interface but PI Activeview was finally installed instead of PI ICE to improve speed on the web.

8. Sangyoung Mo, et al. 8 PI System Layout Ulchin Nuclear Division Han River Site Disch. Temp. Disch. Rad. ERMS Weather Info. TMS Chem.Plant-2 Com.Plant-1 Com. Buffer Node UJPI (RTDB) Kori Nuclear Division (Same as Ulchine) TADA Sys. Buffer Node HYDROPI (RTDB) Wolsong Nuclear Division (Same as Ulchin) Yonggwang Nuclear Division (Same as Ulchin) Head office Customized KHNP LAN HQPI Web Server (RTDB) PI-RLINK Gen. Monitoring Sys. Power Trading Sys. DREAMS Out of KHNP YKPI (RTDB) WSPI (RTDB) KRPI (RTDB) KPX Gen. Monitoring Sys. in other companies Legacy PI SAP Korea Power Exchange Co.

9. Sangyoung Mo, et al. 9 Integrated Data Flow  Eq. reliability  Gen. cost/profit  Key operation indicator  Perform. index Power Trading Sys. Each Legacy System NPP Monitoring Sys. TADA System HPP Monitoring Dam Information Plant Parameters Power Generated Env./Radiation Power Sales Operating History PI Interface Buffer Nodes Nuclear Div. - Kori - Wolsong - Yonggwang - Ulchin PI-API PM Head Office DREAMS (SAP) PI R-Link Han River Buffer Nodes PI Server PI-A/V Gen. Monitoring Sys. PWR Output Web Interface PI User Interface & Analysis ToolsERP Package RTDB RDB Legacy System Buffer Node Client Tools - PI DataLink - PI ProcessBook

10. Sangyoung Mo, et al. 10 Interface with SAP PM through RLINK oPI RLINK provides an interface between PI and SAP PM oTrigger based SAP Transaction l Transaction is triggered by the alarm tag l Automated PM notifications l Measurement document creation in SAP PM l Additional tags are needed for alarms, PM notification number, and measurement document number. oNo way to transfer PI analog type data to SAP frequently, through RLINK l In case of manual input, the additional step resetting the alarm is necessary l Can not deliver any real time analog data from PI to SAP

11. Sangyoung Mo, et al. 11 SAP Transaction Steps in detail oIn case of Run/Stop signal of Rotating Equipment Source TagSet Alarm Tag Create PM Notification and Measurement Doc. In SAP Return Notification & Doc. No. SAP → PI Manually Input Dummy Value(-1) Manually Input Actual Value Set Alarm Tag Create Measurement Doc. In SAP Return Doc. No. SAP → PI Reset Alarm Tag oIn case of Manual Input Data Delete Dummy Value

12. Sangyoung Mo, et al. 12 Interface with SAP and Legacy systems oWe have developed an application using PI-API, PI RDB I/F and BAPI Generation Monitoring System SAP R/3 PI System (API App.) Power Trading System ① ② ② ② ①  Power Sales  Prices  Power Generated  Power Purchased  In-Site Consumption  Operating Time Sharing data with other companies CO, PP, FI, SEM Auto./Manual Input

13. Sangyoung Mo, et al. 13 Web Screen Shot – Main page

14. Sangyoung Mo, et al. 14 Web Screen Shot – Unit summary page

15. Sangyoung Mo, et al. 15 Web Screen Shot – Primary system

16. Sangyoung Mo, et al. 16 Web Screen Shot – Secondary system

17. Sangyoung Mo, et al. 17 Web Screen Shot – TBN-GEN

18. Sangyoung Mo, et al. 18 Trouble Shooting on ProcessBook (1/2) oProblem : DataSet expressions are truncated after the pdi file, which include datasets, is copied to another PC. (PB version 2.31) oSolution : After upgrading the UDS server from version 3.3.361.93 to version 3.3.362.47, the problem was disappeared.

19. Sangyoung Mo, et al. 19 Trouble Shooting on ProcessBook (2/2) Original Expression Truncated Expression after being copied

20. Sangyoung Mo, et al. 20 Trouble Shooting on DataLink oProblem : PI time strings (‘Y’,’T’, ‘*’, etc.) are not work in Excel properly (DL version 2.1) oSolution l Use Excel functions such as ‘today()’, ‘Now()’, etc., instead of PI time string OR l Use the Application.CalculateFull method in VBA script OR press ‘Ctrl+Alt+F9’ key combination in the Excel sheet.

21. Sangyoung Mo, et al. 21 Trouble Shooting on Manual-Logger(1/3) oProblem : Font Broken in Manual-Logger screen (version 1.3) oSolution :not yet oBecause of this problem, we had to develop API applications instead of Manual-Logger to provide manual input function.

22. Sangyoung Mo, et al. 22 Trouble Shooting on Manual-Logger(2/3)

23. Sangyoung Mo, et al. 23 Trouble Shooting on Manual-Logger(3/3)

24. Sangyoung Mo, et al. 24 Conclusions oPI is an important data path among KHNP ERP system, plant computer, and other legacy systems. oConcept of information system was changed after introducing PI system l Scope : Individual plant → Whole company l Objectives : Business function based → Business process based l Implementation : S/W development → Package configuration oPI began to change many people who ware opposite to PI, with impressive capabilities. oAlthough there is some problem and additional necessary functions, we don’t doubt PI system is very flexible, easy to use, and powerful. oPI agencies and customers must have correct understanding of all features of each PI package as well as OSIsoft, prior to PI introduction. The end.