1 / 20

Hello PI 3!

Hello PI 3!. Migrating From PI Version 2. PI 2 Factoid. What is the best case estimate for PI 2 MTBF (mean time between failures)? A) One Year B) Archive Shift Interval C) VMS or PI Upgrade Interval D) Limited only by Hardware. Answer: A. [Fall DST Change]. Goals – Why Migrate?.

georgette
Download Presentation

Hello PI 3!

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Hello PI 3! Migrating From PI Version 2

  2. PI 2 Factoid • What is the best case estimate for PI 2 MTBF (mean time between failures)? A) One Year B) Archive Shift Interval C) VMS or PI Upgrade Interval D) Limited only by Hardware Answer: A. [Fall DST Change]

  3. Goals – Why Migrate? • PI 2 “Maxed-Out” • Choice of Operating System • Price/Performance • Support Costs • PI 3 Feature Set

  4. PI Design Changes Affecting Migration Procedure • PI Time – GMT and Subsecond • Point Class and Attribute Sets • New Point Types • Expanded Digital Set Support • Unambiguous Tag Names • TCP/IP Support Only • Point Security

  5. Alarm & Batch Changes“More Good News…” • ALARMS • Point Class “ALARM” • Conditional Tests and Priorities • Structured Digital Result Set • Alarm Group Tags…Pointsource G • SQC Alarm support • BATCH • Archive Integration “BLOB” tag

  6. Server Module Changes“The Bad News…” • PI2 String Fields May Fail to Migrate • Embedded Tags Migrate “As Is” • Some Performance Equation Features are Moved to Totalizer • Summary Function Basis (per Day) • SQC Tag Migration is Manual • PI Batch Migration is Manual

  7. Performance Equation Changes • Expression Syntax Changes • UNIINT Based Scheduler • New Functions • Calculation Order on Scheduled Basis • Unimplemented “Call Function” • No Option to Clamp Output • Formula Library NOT Supported

  8. Totalizer Changes • Point Class “TOTALIZER” • New Functions • Event, Natural and Periodic Schedules • Event and Filter Expressions • Configurable Close and Report Modes • “Special” Options

  9. “Good-Fast-Cheap” Dilemmafor Migration • Good & Fast • Perfection at a Price! • Fast & Cheap • Reduced Scope! • Cheap & Good • Might Take a While!

  10. Scope Considerations • Legacy Applications • Tag and Archive Count • System Topology Change • Transition Strategy • Interface Upgrades • Validation Criteria

  11. Preparation Tasks • PI 2 System Survey • Include Interface Nodes • PI 3 Platform Readiness • Site Design Questionnaire • Application Review • Itemize “Mission Critical” Applications • Cross Reference (PI 2 vs PI 3 Tagnames) • Identify Problem Tags

  12. Resource Scheduling • IT Support • Network Administrator • DCS Configuration • OSI Technical Support • 3rd Party Application Support • User Community Awareness • System Reboot Coordination

  13. Migration Staging Tasks • PI 3 / PI-SDK / PI-SMT Installation • No default points, manual start • Migrate PI Databases • Convert Archives • Migrate Snapshots • Commission Server Modules • Quality Assurance Check

  14. Milestones • (START) PI 2 “Lock Down” • Point Database Migration Complete • Archive Conversion Complete • Server Modules Ready • Validation & Critical Application Test • Transition Complete • (END) Acceptance & Decommission

  15. BEST CASE ZERO Data Loss Parallel Transition Strategy Spare PINET /API System(s) Update PI Clients on Routine PM. TYPICAL 1Hr Data Loss Swap Transition Stragegy PINET Install PI2 Primary Archive Conversion PI Clients Down until Updated. Critical Paths

  16. 1 PI 3 / NT and Unix 4 2 3 6 PI 2 PINET PI 3 PINET API FTP PI to PI 5 PI 2 / VMS Transition Strategy Example

  17. Point Migration Details • Changing Point Type • Changing Point Class • Digital State Tables • Embedded Short Tag Names • Parsing PI Expressions • Testing PEs

  18. Archive Conversion Details • Point ID File • Archive Conversion • Batch History • PI2 Primary Archive Conversion • DST Handling • Common Warning Messages

  19. Acceptance Testing • Excel>PI Functions • Processbook Trends • Critical Applications • Interface and Server Log Files • Performance Metrics

  20. Life After Migration • Hybrid System Issues • Tag Configuration • Archive Management • PI Health Check • PI 3 Skill Development

More Related