Session:2.6 Conversions

1

• Session 2.6 Conversions
• Panelist Ida Fu, City of Fremont CA.
• Art Henriques, City of Santa Clara , CA
• Date Thursday October 4, 2001

2
Implementing a Tidemark Upgrade

• Lessons Learned from
• Fremont and Santa Clara

3
Session Agenda

• Santa Clara and Fremont Recap
• Important Components for a Successful
  Implementation
• Issues that Arise During an Upgrade
• Brief Recap by Art Henriques from Santa Clara
• Brief Recap by Ida Fu from Fremont
• General Discussion

4
Recap of Fremont and Santa Claras2.61 Upgrade

• Fremont went live with 2.61.aj on July 16
• Conversion took approximately 57 hours
• Santa Clara went live with 2.61.01 on August 27
• Conversion took approximately 2 hours

5
Important Components for a Successful
Implementation

• Planning
• Clearly defining and limiting the scope of work
• Allocating the necessary resources
• Project manager
• Computer support
• Power users
• Clearly define the expectations on Tidemark

6
Important Components Cont.

• Project Management
• Build a Responsibility Matrix
• Set-up weekly conference call with Tidemark
  Project Manager and Implementation Expert
• TEST EVERYTHING THOROUGHLY
• Develop a method for tracking issues
• Get an early handle on Crystal Reports

7
Important Components Cont.

• Project Management Cont.
• If your municipality has anything out of the
  ordinary with your network or computer, then run
  an on-site test conversion
• Build a conversion events timeline
• Build a workstation upgrade checklist
• Allocate time to training your staff

8
Issues that Arise During an Upgrade

• Tidemark sends a bad conversion
• You discover new bugs
• Your business rules may have to change to
  accommodate the upgrade
• You do not know how to go about testing
• You do not have the resources

9
Upgrade Issues Cont.

• Your Tidemark support group is not responsive
• Your computer group wants to incorporate a
  network change at the same time as the upgrade
• You cannot keep track of all the new reports

10
Upgrade Issues Cont.

• Tidemark seems to run slower after the upgrade
• Tidemark will not print reports
• A particular workstation may not work with
  Tidemark or gives an error