2011 T&D Users Group Meeting Presentation on PGE's DIY PI 2010 Migration

2011 T&D Users Group Meeting, Philadelphia, Sept 21-23

DIY – PI 2010 Migration Upgrade

Andi Greisel, Portland General Electric

PI T&D Users Group @2011 OSIsoft, LLC - – Rights Reserved
@2010 OSIsoft, LLC - AllAllRightsReserved
© 2009 OSIsoft, Inc. All Rights Reserved
1

A Quick Look at PGE
 Established 1889
– First long distance transmission electric company
 800,000+ retail customers
 4,000 sq. mile service territory
 1,500+ miles transmission line
 26,000+ miles of distribution line

2

PGE’s PI Usage
 Separate PI Environments
– Generation
– Marketing
– Transmission & Distribution
• 130 users
– Engineering
– Operations
– Planners
• ProcessBook
– Substation onelines
– Some redundancy with EMS
• DataLink Image source: http://bobsmisanthropicadventures.blogspot.com/2011/05/wednesdays-pics.html

– Analysis
• 40,000+ PI tags
3

Why We Did It Ourselves?
 For the challenge
 To better learn the software
 Lots of custom applications
 Can always get help

5

Why We Upgraded?
 Retiring old servers
– Part of IT’s regular vintage schedule
 Move to virtual servers
– IT strongly encouraging a virtual environment
• Shared resources
• Easier rebuild on failure
• Snapshots!
 In need of a PI upgrade (3.4.375)
– AF sounds interesting
– Interest in PI Notifications
 Want to use Active Directory to control access
– PI Users are not secure

6

System Comparison
 Existing system
– Windows Server 2003
– 32-bit
– 3.4.375
– Four servers

 Replacement system
– Windows Server 2008 R1 & R2
– Virtual
– 64-bit
– 3.4.385 (PI 2010 R2)
– Five servers
• SQL database

7

Server Layout – Primary Site

 Batch  PI Server  SQL Express
 DNP  AF Server  Custom Apps
 ICCP
 OPC

8

Server Layout – Backup Site

 DNP  PI Server  IIS 6.0
 ICCP  PI SDK
 OPC

9

Our Approach
 Setup parallel systems
– Different server names and IP addresses
– Redundant interfaces
• Most data via ICCP
• Some RTU data direct via DNP
– Potentially create server name alias on corporate DNS
 Rewrite custom applications
– Alarm notification program
• Email and SMS
– MV90 batch processing
 Administer our servers separate from IT
– Drove decisions for SQL DB location

10

Biggest Design Decisions
 PI and AF on one server, SQL on another
– No AF redundancy
• Not sure how much will use AF
– Splitting up single install procedure
• Page 16 – PI AF 2010 R2
– Opening firewall between AF and SQL servers
• Page 44 – PI AF 2010 R2
 Structuring Active Directory groups
– Previously setup to control access to share drive
 SQL flavor (Express, Standard or Enterprise)
– Understanding licensing scheme
• Potentially use corporate cluster

11

Decision: Running Parallel Systems
 Pros
– No rush to upgrade
– Less downtime
– Data comparison
• Reassurance
 Cons
– Maintaining two systems
• Tag structure slightly different
– Windows Security
•
Like production once archives moved
– Setting up redundant interfaces
• Required DNP upgrade
– Multiple connections to RTU

12

Decision: SQL Server Express 2008 R2
 Pros
– Free
– Easy to upgrade to Standard or Enterprise
 Cons
– No database redundancy
– Maximum database size of 10 GB per database
• 4 GB for SQL Server Express 2008 (non R2)
– Single physical CPU, but multiple cores allowed
– 1 GB of RAM
• Runs with any RAM amount, but max use is 1 GB
 Useful comparison resource
– http://www.microsoft.com/sqlserver/en/us/product-info/compare.aspx

13

Snag: Migrate, then Upgrade
 Tried to freshly install PI 2010
 Issues
– Backup and Restore not compatible
• 32-bit to 64-bit architecture difference
– Archives not compatible
– Few weeks lost
 Resolution
– Uninstall PI 2010 and install 3.4.375 64-bit
 Salvageable
– AF installation
– Interface configuration
– SQL server setup

15

Snag: SISCO AX-S4 ICCP & RDP
 SISCO AX-S4 doesn’t work over RDP
– Virtual servers require remote desktop
– Licensing limitation
 Issue
– Licensing doesn’t work over RDP
 Resolution
– Special licensing request
– Update should be available now

16

Snag: PI Users and piadmin Account
 No user with administrator privileges after install
 Issue
– Copied across users and groups
– Disabled piadmin as part of install
– Using Active Directory instead of PI Users
– No user had administrator privileges
 Resolution
– Elevated PI User over Windows Security in PI SMT3
– Mapped piadmin to relevant user accounts

17

Where Are We Now?
 Cutting over October 17th
– Had expected to have cutover last month
• Don’t schedule for summer!
 System is running and being tested
 Custom applications need to be completed
 Complete client tests
 Verify batch data is up-to-date
 Verify archives are good

18

Time Consumers
 Internal IT policies and processes
– Largest time consumers
• Building virtual servers
• Firewall changes
• Creating service accounts and AD groups
• Setting up and testing ICCP connections
 Moving archives
– Unregister, move, reregister: script it!
 Converting PI displays
– Find and replace server names
 Updating PI tags
– A few PI ownership attributes removed

19

Summary
 Good learning experience
 Larger project than expected, a few hiccups
 OSIsoft Technical Support rocks!
– Logged around 10 calls, relatively complex
– Incredibly helpful and responsive

20

2011 T&D Users Group Meeting Presentation on PGE's DIY PI 2010 Migration

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (17)

En vedette

En vedette (19)

Similaire à 2011 T&D Users Group Meeting Presentation on PGE's DIY PI 2010 Migration

Similaire à 2011 T&D Users Group Meeting Presentation on PGE's DIY PI 2010 Migration (20)

Dernier

Dernier (20)

2011 T&D Users Group Meeting Presentation on PGE's DIY PI 2010 Migration