Download PPT Template

Slide 1
Preparing for an Upgrade to
Release 4.2
John Pagan
Manager – Professional Services
October 15, 2012
© 2012 Invensys. All Rights Reserved. The names, logos, and taglines identifying the products and services of Invensys are proprietary marks of
Invensys or its subsidiaries. All third party trademarks and service marks are the proprietary marks of their respective owners.
Introduction
Upgrading IntelaTrac to release 4.2 SP1 requires a considerable
amount of effort. The customer should plan ahead to make sure the
upgrade is executed with no problems. The most important things
to remember are the following:
1) Review system requirements and ensure your servers are in
compliance
2) Send your IntelaTrac Database to Invensys for integrity checks
3) Schedule your resources to assist the consultant during the upgrade
4) Schedule training for your super users and operators
Slide 3
Upgrade Timeline
Slide 4
Upgrade Timeline
Critical
Step
Slide 5
8 Hour
Outage
4 – 8 Weeks
Before Upgrade
Verify System
Requirements
Slide 6
Verify System Requirements
4 – 8 weeks before upgrade
Slide 7
Verify System Requirements
4 – 8 weeks before upgrade
Do you need new Handhelds?
Slide 8
Some handhelds
are no longer
supported
Some handhelds
are near end of
life
Some handhelds
have more
capability
• Symbol 8943
• Symbol 9060
• Intermec 751
• Symbol 9090
• Intermec CK61
• Faster Processor
• More Memory
• Camera
• GPS
• Phone
Verify System Requirements
4 – 8 weeks before upgrade
Slide 9
Are you using
the latest
service pack for
OS and SQL?
Are you
migrating to
new server?
Are you
planning to use
virtualization?
Do you have a
Test
Environment?
1 – 2 Weeks Before
Upgrade
Create CAB Files
Database Analysis
Slide 10
What are CAB files?
• CAB files contain the image of the handheld and are located in the
storage card
• If the handheld gets corrupted it can be restored from the CAB files
• CAB files also contain the customer site configuration
Slide 11
S
Create CAB Files
1 – 2 weeks before upgrade
Slide 12
Database Analysis
1 - 2 weeks before upgrade
Slide 13
Database Analysis
1 - 2 weeks before upgrade
Some issues
require manual
fix
Slide 14
Some issues
must be fixed
before the
upgrade
Some data will
have to be
deleted
Upgrading
from 3.1
Must be done
in Procedure
Builder
Normally
fixed by
repair script
Normally
orphan
records
Monthly
schedules
must be
manually
recreated
Requires
Super User
assistance
May require
assistance
from DBA or
Super User
A report will
be provided
listing all
affected data
Remove
multiple roles
from
procedures
1 Week Before
Upgrade
Training
Slide 15
Training
1 week before upgrade
Slide 16
Super User Class
End User Training
Supervisor
Training
• Significant
changes in client
• 5 days of training
• Administration
• Procedure Builder
• Auditor Plus
• WebReports
• Mobile IntelaTrac
• Minor changes in
Mobile IntelaTrac
• 2 – 4 hours of
training
• How to collect
data
• Transfer
• Significant
changes in
Auditor Plus
• Auditor Plus
• Web Reports
• How to review
and approve data
Day 1
Upgrade Database
Install Server Software
Deploy Handhelds
Slide 17
Upgrade Database
Day 1
Plan for 8 hour
outage
• System will be down
from 8am to 5pm
• Transfer all
completed
procedures by 6am
• Collect all handhelds
by 8am
Slide 18
Backup Database
• Should be done just
prior to upgrade
• Can never be too
safe
Upgrade Database
Day 1
Repair Database
Integrity Issues
• Run repair script
• Run integrity reports
• Correct any manual
errors
Slide 19
Upgrade Database
• Run
DatabaseScript.exe
• May take several hour
to run depending on
database size
• Requires SA account
to run
Install Server Software
Day 1
Install Sync
Server
• Verify all services
start correctly
• Setup service
accounts
Slide 20
Install Test Client
• Verify
connectivity to
database
• Verify procedures
and schedules
• Run invalid
procedure wizard
• Some procedures
may need
tweaking
Install Test
Handheld
• Verify transfer
are working
• Verify procedures
are available for
execution
Deploy Handhelds
Day 1
Install Mobile IntelaTrac in Handhelds
• Copy CAB Files to storage card
• Cold boot the handheld to reimage
• CAB Files may require minor tweaks
• Be prepared to help with this process
• Deploy handhelds to the field
Slide 21
Day 2, 3, 4, 5
Install Client Software
Install WebReports
System Test
Slide 22
Install Client Software
Slide 23
S
May involve
multiple
computers
IMC, Procedure
Builder, Auditor,
Administration
IT person should
learn how to install
the software
The consultant will
install as many
clients as it is
practical
Requires
administrator
account
Some folders need
special
permissions in
Windows
Vista/Windows 7
Be prepared to
help with this
process
Some procedures
may require
manual corrections
and re-release
User permissions
may require
review and
adjustment
Run the Invalid
Procedure Wizard
Install WebReports
Slide 24
Need access to the
Web Server
Can be installed in
Sync Server
Requires
administrator
account
Requires
Exchange/SMTP
Server
Some folders need
special permission
in Windows Server
2008
Be prepared to
help with this
process
System Test
Procedures
•Converted
properly
•Correct any
errors
Slide 25
Transfers
•Handhelds
transfer
correctly
•No transfer
errors
•Data moves
to database
WebReports
•Access to the
data
•Scheduled
reports email
automatically
Peripherals
•RFID
•VIBTOOL
•Temperature
Gun
CAB Files
•Install
Correctly
•All settings
included
•All
configuration
is complete
Unexpected Delays
Hardware does not
meet requirements
Hardware is not
ready for
installation
Database
administrator is
busy
Database
administrator
wants to review
the scripts before
running them
Database too
+4 scripts
big/repair
Hrs time to
take a long
run
Database upgrade
scripts +1
failed for
an unknown
Day
reason
Customer has the
wrong version of
+2 PHD
PI SDK,
Hrs Client,
Client, IP21
etc.
Customer has the
wrong patch for
SQL server, SDK,
.Net Framework,
etc.
Remote desktop
access is not
available
Passwords are not
available/wrong
password was
provided
The server is not
in the
network/domain
Network+1security
policies
prevent
Week
the installation
Database is
corrupted
+2 and has
to be Days
sent to the
support group
Database issues may take a week or more to resolve
Slide 26
Summary
Verify System
Requirements
Database
Maintenance
OS / SQL
Version
Backup
Apply latest
service pack
Virtualization
Slide 27
Send DB Backup
to Invensys
Shrink
New handhelds
New servers
Database
Repair
Reorganize
indexes /
Rebuild indexes
Perform these
actions before
repair
Be prepared to
do manual
corrections
Some problems
will prevent
upgrade if not
corrected
Resources
Plan 8 Hour
Outage
Weekly calls
with Services,
PM, and sales
8 hours is an
estimate
Schedule a
Super User
Be prepared in
case the outage
extends
Schedule IT and
DBA
Send email to
operators
Make sure your
resources are
available to help
Transfer
procedures by
6am
Workshop: Upgrading to IntelaTrac 4.2
IntelaTrac version 4.2 is a significant release for our customers. This
workshop will provide detailed information to consider when
planning and executing an upgrade project. The day will be spent
working through scenarios and touching on the critical areas to
think about for a successful upgrade plan.
Session 1: October 17, 9:00 am – 4:00 pm
Session 2: October 18, 9:00 am – 4:00 pm
Holiday Inn Houston Westchase
10609 Westpark Dr., Houston, TX. 77042
Slide 28
Slide 29