Migrating to AF and AF driven Power applications

Transcription

1 Migrating to AF and AF driven Power applications Presented by Henryk Schneider SP-AusNet Steve O Donnell Realtime Results

2 Agenda About Us Migration to PI System 2010 Projects Wiredown/SWER Events/BrownOuts Load Profile Analysis Windows Services 2

3 About SP AusNet Diversified energy business $7 billion electricity & gas network 1.2 million customers 3

4 What we do Managing three key Victorian energy networks Electricity Transmission Network 13,000 high voltage towers ~6,580 km of transmission lines Electricity Distribution Network 650,000 customers Network spans 49,500 kms across an area of 80,000 sq. kms. Gas Distribution Network 620,000 customers Network spans 10,000 kms across an area of 60,000 sq. kms. 4

5 Realtime Results RtR Started with the Asset Condition Management project in 2006 Dynamic Lines, Transformers and Asset Health Continued with additional projects for Weather Warning System Gas Advisor and Leak detection system Background 34 years in Process Control and Process Management Systems 26 years with the PI System TM 22 years active software development Focus is advanced value-added PI applications for clients 5

6 Upgrade to PI 2010 v > v Drivers end of life hardware performance archive storage software upgrade 6

7 System info 13 servers (Windows 2003) Point count 370,000 Module count 7,300 Archive storage 800GB 1000 archive files online 7

8 Products used PI Server PI ACE rtwebparts rtalerts PI - ESCA HabConnect, PI to PI, HTML, PerfMon, SNMP, Ping, TCPResp, RDBMS, PIOLEDB PI Datalink PI Processbook Windows Services 3.0 MS SQL 2005 MS SQL 2005 Reports PI SDK applications 8

9 System Architecture Corporate WSS 3.0 RtWebParts RtAlerts PI HTML PI UFL PI RDBMS Site A Site B Misc. Misc. WSS 3.0 RtWebParts DMZ PI ACE Custom Services PI ACE Server A PI Server PI PerfMon PI SNMP PI Ping PI TCP Resp Collective Server B PI ACE SCADA HabConnect - Transmission HabConnect Distribution & Gas SCADA SCADA SCADA 9

10 Key Changes 32 bit -> 64 bit environment (Windows Server 2008 R2) Module DB -> Asset Framework 2010 rtwebparts -> PI WebParts 2010 rtalerts -> PI Notifications 2010 PI Datalink 3.1 -> 2010 * PI Processbook 3.1 -> 3.2 * WSS 3.0 -> 2010 Foundation MS SQL & Report Server > 2008 MS Visual Studio >

11 Approach Staged implementation around each system component Install Migrate software/database Run in parallel Test & Verify Cutover Advantages Low risk Minimised impact on users Rollback simple by switching users/apps back to old system 11

12 Communication PI Bulletin newsletter Pre and Post cutover information & instruction e- mails users 12

13 Migration Misc.. Misc. Collective PI ACE Server A Server B PI ACE SCADA SCADA SCADA 13

14 Stage 1 New SCADA interfaces Misc.. Misc. Collective PI ACE Server A Server B PI ACE New SCADA New SCADA New SCADA New SCADA 14

15 Stage 2 New Collective & AF AF Collective Misc.. AF Server A AF Server B Misc. Collective PI 2010 PI ACE Server A1 Server B1 PI ACE PI to PI Collective New SCADA New SCADA Server A Server B New SCADA New SCADA 15

16 Stage 3 Misc. & temp. interfaces New Misc Intf AF 2010 Collective New Misc Intf AF Server A AF Server B Temp SCADA Server A1 PI 2010 Collective Server B1 Temp SCADA Misc.. PI to PI Misc. PI ACE New SCADA New SCADA Server A Collective Server B New SCADA New SCADA PI ACE 16

17 Stage 4 New ACE Servers New Misc Intf AF Server A AF 2010 Collective AF Server B New Misc Intf New ACE A1 New ACE A2 New ACE B1 New ACE B2 PI 2010 Collective Temp SCADA Server A1 Server B1 Temp SCADA Misc.. Misc. PI ACE New SCADA New SCADA Server A Collective Server B New SCADA New SCADA PI ACE 17

18 Stage 5 New portal New AF 2010 Collective New New Misc Intf AF Server A AF Server B New Misc Intf New ACE A1 New ACE A2 New ACE B1 New ACE B2 PI 2010 Collective Temp SCADA Server A1 Server B1 Temp SCADA Misc.. Misc. PI ACE New SCADA New SCADA Server A Collective Server B New SCADA New SCADA PI ACE 18

19 Stage 6 Switch SCADA interfaces New Misc Intf New AF 2010 Collective New New Misc Intf AF Server A AF Server B New ACE A1 New ACE A2 New ACE B1 New ACE B2 PI 2010 Collective New SCADA New SCADA Server A1 Server B1 New SCADA New SCADA Misc.. Misc. PI ACE Collective PI ACE Temp SCADA Server A Server B Temp SCADA 19

20 Stage 7 Cutover Users New Misc Intf New AF 2010 Collective New New Misc Intf AF Server A AF Server B New ACE A1 New ACE A2 New ACE A1 New ACE A2 PI 2010 Collective New SCADA New SCADA Server A1 Server B1 New SCADA New SCADA 20

21 Lessons Learned Memory usage & File System Cache (FSC) under 64bit environment OSIsoft KB Article # KB00784 AF Collective (Replication) can t write to AF database when Primary is not available. 21

22 Possible AF Deployment Scenarios PI AF 2010 Users s Guide. 22

23 Resources PI Server 2010 Installation and Upgrade Guide PI Server Installation and Upgrade Guide v PI User Guides Tech Support Realtime Results vcampus 23

24 Recent AF based Applications WireDown Events SWER Step Events Device Operations Load Analysis Consumption Summaries Data Transfers Gas Logging Meter Management BrownOut Analysis 24

25 Wiredown/SWER Events Project Problem Power lines in distribution network fail periodically Need to detect and alarm these events urgently Proposal Use data from the field devices to detect failure in realtime Projects are in Trial/Evaluation mode 25

26 Wiredown/SWER Applications Separate Windows Service applications.net 4 based using VB.NET AF Template driven 104 Substations, 365 Feeders,2237 devices Not ACE based Primary/Standby 26

27 Asset Definition 27

28 Template Driven 28

29 Field Devices Circuit Breaker/Feeder Relays (F650, SR760) AutoReclosers ACR s (Form 5, Form 6, & RC10) Single Wire Earth Return AutoReclosers SWER s (RC10S and Nulec) Sectionalisers SEC (GSS100 & CAPM5) Data received via SCADA 29

30 Device Definition 30

31 Application Device Uses High Voltage Load analysis Substation Load Analysis Consumption Summary WireDown Analysis SWER Step Event Analysis Fire Risk Analysis 31

32 Devices in AF Check made for new tags Device elements automatically created New device added when new tag found Based on template Trigger values calculated when sufficient history is available (~ 1 week) Device elements used by many applications 32

33 WireDown Trigger Condition Send Alarm Calculated Trigger Value (Amps) (based on Time weighted average data) Specified Period (mins) 33

34 WireDown Conditions Important to eliminate false positives Otherwise ignored by Control Room Filter out several conditions Abnormal Load switching Parallel events Relay testing Alerts issued for various cases Embedded trends for fast assessment 34

35 WireDown Earth Fault Alarm Alert 35

36 Abnormal Load Switch - Resolved 36

37 Real WireDown Example 37

38 SWER Step Change Analysis Calculated Step Change exceeded (Amps) Analysed all steps over last 60 days to calculate Step trigger value for Device Alarm sent after specified duration 38

39 SWER Earth Fault Alert

40 Load Profile Project Problem Planners need to know what power is going through their Pole transformers (aka Substations) Need to aggregate usage via Smart meter data Simple tool required for analysis Proposal Combine Oracle and PI data to analyse data Perform calculations for 60,000 meters Summaries for Weekly, Yearly data Calculation run over 3 4 days Provide Web based tool for planners 40

41 Web site for Load Profile Analysis 41

42 42

43 Search by Name or NMI 43

44 Select Time to see trend 44

45 Plot Load and Frequency 45

46 Load Plot 46

47 Frequency and Duration Plots 47

48 Applications Settings via Web page 48

49 Application Management Project Problem Growing number of Windows Services installed Installed in Primary/Standby configuration Need to monitor performance and track activity Proposal Define Application template for common approach Provide Element Relative display for PI System Manager 49

50 Application Management Currently running 9 Windows Services Performing a variety of tasks Consumption Summaries Automated Data Transfers via FTP/ Substation Load Profile calculations Tracking Gas Corrosion Loggers Tracking Wiredown and Earth faults Running in Primary/Standby mode AF used to monitor Services 50

51 Applications in AF 51

52 Application Template 52

53 Application Monitoring via ER displays 53

54 Application Monitoring via ER displays 54

55 Conclusions Trials have proven effective Real and impending faults identified early No cost benefits done as yet AF is very versatile for developing applications AF Templates reduce significant re-work 55

56 Questions? 56

57 Henryk Schneider Systems Analyst SP-AusNet Steve O Donnell [email protected] Managing Director Realtime Results Ltd 57

58 Brought to you by