migrating to af and af driven power applications...b stage 5 – new sharepoint portal 18 new scada...

Presented by

© Copyr igh t 2013 OSIso f t , LLC.

Migrating to AF and AF driven Power applications

Henryk Schneider – SP-AusNetSteve O’Donnell – Realtime Results


Agenda• About Us• Migration to PI System 2010• Projects

– Wiredown/SWER Events/BrownOuts– Load Profile Analysis– Windows Services

2


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

3


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


Realtime Results• 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 SystemTM

• 22 years active software development• Focus is advanced value-added PI applications for clients

5

RtR


Upgrade to PI 2010• v3.4.380.36 --> v3.4.385.77• Drivers

– end of life hardware– performance– archive storage– software upgrade

6


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

7


Products used• PI Server• PI ACE • rtWebParts• rtAlerts• PI Interfaces - ESCA HabConnect, PI to PI, HTML, PerfMon, SNMP, Ping,

TCPResp, RDBMS, PIOLEDB• PI Datalink• PI Processbook• Windows SharePoint Services 3.0• MS SQL 2005• MS SQL 2005 Reports• PI SDK applications

8


System Architecture

9

SCADA Interfaces

SCADA Interfaces

SCADA Interfaces

PI ACE PI ACESharePoint SharePoint

SharePoint SharePointMisc.Interfaces

Misc. Interfaces

Site A Site B

Corporate

DMZ

SCADA

Collective

Server A Server B

PI HTMLPI UFLPI RDBMS

WSS 3.0RtWebPartsRtAlerts

PI ACECustom Services PI Server

PI PerfMonPI SNMPPI PingPI TCP Resp

HabConnect –Distribution & Gas

HabConnect -Transmission

WSS 3.0RtWebParts


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 -> SharePoint 2010 Foundation• MS SQL & Report Server 2005 -> 2008 • MS Visual Studio 2005 -> 2010

10


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


Communication• PI Bulletin newsletter• Pre and Post cutover

information & instruction e-mails.

• 200+ users

12


Migration

13

SCADA Interfaces

SCADA Interfaces

SCADA Interfaces

Collective

Server A Server BPI ACE PI ACESharePoint SharePoint

SharePoint SharePointMisc. Interfaces.

Misc. Interfaces


Stage 1 – New SCADA interfaces

14

New SCADA Interfaces

Collective



Misc. Interfaces





Stage 2 – New Collective & AF

15


Collective

Server A Server B



Misc. Interfaces




CollectivePI 2010

Server A1 Server B1

PI to PI

AF Collective

AF Server A

AF Server B


AF 2010 Collective

AF Server A

AF Server B

Stage 3 – Misc. & temp. interfaces

16


Collective


SharePoint SharePointMisc.

Interfaces.Misc.

Interfaces

PI 2010Collective

Server A1 Server B1

PI to PI

New Misc Intf New Misc Intf

Temp SCADA Interfaces






AF 2010 Collective

AF Server A

AF Server B

Stage 4 – New ACE Servers

17


Collective



Interfaces.Misc.

Interfaces

PI 2010Collective

Server A1 Server B1







New ACE A1 New ACE A2 New ACE B1 New ACE B2


AF 2010 Collective

AF Server A

AF Server B

Stage 5 – New SharePoint portal

18


Collective



Interfaces.Misc.

Interfaces

PI 2010Collective

Server A1 Server B1








New SharePoint New SharePoint


AF 2010 Collective

AF Server A

AF Server B

Stage 6 – Switch SCADA interfaces

19


Collective

Server A Server B



Interfaces.Misc.

Interfaces

PI 2010Collective

Server A1 Server B1

New Misc IntfNew Misc Intf




New SCADA InterfacesNew SCADA

Interfaces




AF 2010 Collective

AF Server A

AF Server B

Stage 7 – Cutover Users

20


PI 2010Collective

Server A1 Server B1

New Misc IntfNew Misc Intf


New SCADA InterfacesNew SCADA

Interfaces

New ACE A1 New ACE A2 New ACE A1 New ACE A2



Lessons Learned

21

• 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.


Possible AF Deployment ScenariosPI AF 2010 Users’s Guide.

22


Resources

23

• PI Server 2010 Installation and Upgrade Guide• PI Server Installation and Upgrade Guide

v3.4.380• PI Interfaces User Guides• Tech Support• Realtime Results• vCampus


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

24


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


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


Asset Definition

27


Template Driven

28


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


Device Definition

30


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

31


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 applications32


WireDown Trigger Condition

33

Specified Period (mins)

Calculated Trigger Value (Amps)

Send Email Alarm

(based on Time weighted average data)


WireDown Conditions• Important to eliminate false positives

– Otherwise ignored by Control Room• Filter out several conditions

– Abnormal Load switching– Parallel events– Relay testing

• Email Alerts issued for various cases– Embedded trends for fast assessment

34


WireDown Earth Fault Alarm Email Alert

35


Abnormal Load Switch - Resolved

36


Real WireDown Example

37


SWER Step Change Analysis

38

Alarm sent after specified

duration

Calculated Step Change exceeded (Amps)

Analysed all steps over last 60 days to calculate Step trigger value for Device


SWER Earth Fault Email Alert


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


Web site for Load Profile Analysis

41


Search by Name or NMI

43


Select Time to see trend

44


Plot Load and Frequency

45


Load Plot

46


Frequency and Duration Plots

47


Applications Settings via Web page

48


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


Application Management• Currently running 9 Windows Services

– Performing a variety of tasks• Consumption Summaries• Automated Data Transfers via FTP/Email• Substation Load Profile calculations• Tracking Gas Corrosion Loggers• Tracking Wiredown and Earth faults

– Running in Primary/Standby mode• AF used to monitor Services

50


Applications in AF

51


Application Template

52


Application Monitoring via ER displays

53


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


Questions ?

56


Henryk [email protected] AnalystSP-AusNet

57

Steve O’[email protected] DirectorRealtime Results Ltd

Brought to you by


migrating to af and af driven power applications...b stage 5 – new sharepoint portal 18 new scada...

Documents