PI 3.2 Migration

1
PI 3.2 Migration
Sean Ireland Process Quality Systems
Leader Bucksport, ME
2
PI 3.2 Migration
Remember Im just a client.
3
PI 3.2 Migration

• PI 3.2 Migration and Goals
• Why Migrate
• Technical Issues
• Interface Issues
• Challenges
• OSI Response
• Overall evaluation
• Future requests

4
PI 3.2 Migration

• Why Migrate?
• OSI development stopped on PI 2.x
• Archive history too small
• Other reasons
• No support for sub-second time stamps
• Upgrade Maintenance costs to PI 2.x system
• Higher archive efficiency with No Limit to size
• Long Tag Names
• History on CD ROM

5
PI 3.2 Migration

• Problems Faced with existing system
• Archive history too small
• High cost to increase storage space.
• Any upgrades would only be temporary. (OSI
  stopped development on 2.x)

6
PI 3.2 Migration

• Migration Considerations
• Upgrade existing system - v - New Intel Server
• Cost of Upgrades
• Training
• Proven Platform - v- Unknown/New
• Bleeding Edge syndrome
• Interface compatibility
• Home grown software issues

7
PI 3.2 Migration

• Migration Process
• I. Buy NT Server and install PI 3.2.
• Extract Tag/Configuration from PI 2.x
• Replicate (whats possible) config. tag
  structure.
• Verify/complete setup of PI 3.2.
• II. Install PI to PI interface.
• Run in parallel for verification of archives and
  user tools.
• III. Direct all user tools to 3.x system for
  user testing/feedback.
• IV. Install PI 3.2 Interfaces and test.

8
PI 3.2 Migration

• Process Contd.
• IV. Direct PI Net Nodes to talk to PI 3.x Home
  Node.
• V. Turn off PI2PI, convert VMS PI Home node to
  PI Net node. (Maintain home grown apps.)
• VI. Migrate home grown apps to NT Server Test.
• VII. Go production

9
PI 3.2 Migration

• Challenges with Migration
• Problems with initial installation on NT server.
• Installation Migration not same as
  documentation.
• Firewall table, Proxy server, User table (8 Char
  only), PI 32bit API, Logins w/ client tools.
• Archive size. 300 Meg is our choice. gt 300 Meg
  requires long conversion hours.
• System almost bogged to standstill. (Processors
  at 99-100 - new build removed bug.
• No digital state tags at first. Very different
  puppy.
• Documentation problems.

10
PI 3.2 Migration

• Challenges Contd.
• Do Not install Default points. Otherwise you
  will just have to start over again.
• Create your archives with batch files
• Minimal prep.
• Hacker by nature - 1 - 1.5 weeks total time
  from nothing to full up PI 3.2.

11
PI 3.2 Migration

• Challenges Contd.
• PI2PI startup problems.
• Used 1 PT Source at first. Not efficient.
• Created a Pt Source for each area of mill.
  Easier to handle tags.
• Consider a PI2PI pt source for each interface in
  future.
• How to convert from PI2PI to production Tags.
• Starts at PI3 tag creation during migration.
• Save Attribute changes for PI3/PI2PI in Excel
  with tag names.
• Use Jins GUI tools to change PI 3 tags to PI2PI
  req.'s.
• When ready for production, paste Tags and changes
  into Tag Configurator and run the edits.

12
PI 3.2 Migration

• Challenges Contd.
• PI2PI Startup overflowing PI 2 Event Queue.
  Event sign-up with PI 2 BEFORE PI 3 ready to take
  data.
• Data verification. Resolution not the same on
  servers. (Fixed)
• PI 3.2 Troubleshooting
• Use your PI MESS log file! (Pimesslog.txt)
• Watch Client Tools for updates.
• Check evm_monitor constantly.
• PIGetMsg on NT server.
• Health Check GUI Tools

13
PI 3.2 Migration

• Issues
• Digital States.
• Conversion caused our D.S. tables setup in our
  tags to be unusable.
• PI2 - Start and Length in configuration
• PI3 - Sets only.
• PI 3 Digital Set Features
• Cannot delete Digital States/Sets
• Starts with 0 offset.
• Edit command procedure to add DummySet0.
• Puts in DummySetX if you try to delete one.

14
PI 3.2 Migration

• Issues Contd.
• Create your D.S. Sets with a command Procedure
  output file from PIDiff, then use PIConfig on PI
  3.X. Example

LISTPIDS.TXT
List all Digital State Sets _at_Table PIDS _at_Mode
List _at_Ostructure SET, State, _at_Select
SET _at_Endselect
Usage
C\PI\ADM\PIConfig lt ListPids.txt
15
PI 3.2 Migration

• Issues Contd.
• ProcessBook Users.
• Hex Edit to look at PI 3. (Does not do the
  linked pages in Processbook.
• GUI management tools
• TagConfigurator.xls
• Health Check

16
PI 3.2 Migration

• Daily Routine
• Check Processbook for any update problems.
• Run evm_monitor on PI 2 system to check Event
  Queues for overflow.
• Check PI Mess log file
• Check PIGetMsg (PI 3.2 Message log) for any
  errors
• Check \PIPC\DAT\PIPC.LOG file for interface
  problems

17
PI 3.2 Migration

• Hardware
• PI Server - HP Netserver LX Pro
• Dual Pentium Pro 200Mhz
• 512 Meg Ram
• (4) 9gig Ultra Wide SCSI II (app. 24gig usable)
• HP NetRAID Ultra Wide SCSI Controller
• RAID 5
• CDR (On line history storage and backup)
• 24 gig DDS-3 Tape Backup (7gig/hour backup, NOT
  tested as of yet.)

18
PI 3.2 Migration

• OSIs Response
• Excellent!
• All issues found with PI 3.2 were answered and
  fixed in an expeditious and professional manner.
• System become more stable with each new build.
• OSI kept their reputation of being in the
  trenchs with their clients throughout testing
  phase.
• PI 3.2s technical staff was on top of all bugs
  found and fixed and updates posted in an
  expeditious manner.

19
PI 3.2 Migration

• Overall Assessment of PI 3.2 - Pros
• Becoming solid quick.
• System is easy to use, and understand.
• PI 3.2 Archives are more efficient. Double to
  triple storage capability.
• Fast. Client tools took no hit on performance.
• ODBC - Simple and efficient to utilize.
• VB 5 Integration
• Newer capabilities.
• Cheaper in long run
• Expandable OTS answer to storage problems.

20
PI 3.2 Migration

• Cons
• More GUI Management tools are required to get us
  completely out of command line typing.
• Documentation.
• ActiveX ???

21
PI 3.2 Migration

• Future Requests
• GUI Management tools
• GUI PIConfig
• GUI PIArtool
• Icon Health check
• PI
• Archives
• Interfaces

22
PI 3.2 Migration
Questions?