1. Upgrading to SoftLab Version 4.0.6.X
Presenting Voyagers:
James Pomicter
Jane Blackmar

2. Overview Getting Started Planning Working with your assigned SCC Team
Project Execution
Go-Live
Wrap Up

3. Getting Started Working with your Post-Live AE
Decisions to be made based on system requirements and future workload
Determine hardware and software needs
DB_Vista vs. Oracle
Add-on modules
Additional setup
Generating a quote (based on all of the above)
Determine a reasonable start date and timeline for project
2-4 weeks lead time for start of project
Upgrade projects will generally be about 9 months in duration

4. Planning Designate your team and allocate resources
Personnel availability
Subject Matter Experts (SMEs)
Back up personnel (if able)
Allocated project hours
30 hours per product/per week is recommended (including HIS, Instruments and Reference Laboratory)
See Client Project Manager Workbook, CWB01S5000 for additional information
Best practices and your organization’s workflow should be the guiding force for your project (build new setup, validation, parallel run/mock go-live)

5. Working with Your Assigned SCC Team
One SCC Implementer per module will be assigned to your project
Technical assistance and advise
Weekly technical calls with their modules counterpart on the client side
There will also be a dedicate SCC Project Manager assigned to your project
Schedule and moderate weekly conference calls between SCC and Client Upgrade Teams (includes all modules)
Manage the timeline to ensure the project remains on track, meets all goals and escalates go-live critical tasks

6. Project Execution Review SoftLab 4.0.6.X new features
RBS rules have the “Events” button that will need to be set for:
Reflex
Test Call
Send Message Warning
Print Instant Report
Post Results
Pathologist Review
Test Maintenance replaces individual and group tests
All prompt tests utilizing Flag 25 currently built will need to be reviewed
Option for new Security Management System (SMS)
SoftLab New Features and SMS are being presented at various times during this week’s voyage
Check the schedule for appropriate coordinates

7. Project Execution These are not your father’s release notes
Release notes have been sorted for ease of operation
Links provided to test cases when applicable for ease of testing and validation
Release Notes Tool
Schedule and coordinate any applicable trips through your assigned SCC Project Manager

8. Project Execution Validation
SCC will provide general validation checklist for each applicable product
Client can use these documents as a starting point to build their validation plans based on their specific business workflow
Signed validation checklists must be submitted to SCC before going live
Your validation plans are built according to release notes and your business workflow

9. Project Execution
Go-Live Preparation to include stress testing and Mock Go-Live
Client and SCC prepare a Go-Live Switch Plan
Includes timelines and approximate down time

10. Go-Live
Patient Database is converted and configured to meet new software requirements
All setup, changes and additions will be moved and copied to Live environment
Live environment name now becomes “LIVE2”
SCC Implementers will test the new LIVE2 environment prior to releasing it to the client for their own testing
SCC personnel will be available for assistance with any go-live issues during normal working hours (unless otherwise specified)

11. Go-Live Post-Live Support:
A new TEST environment is created based on the new LIVE2 Environment
Approximately thirty days after live you will be transitioned back to the Post-Live Support Team (Post-Live AE and TSS support)

12. Wrap Up
A final call between the client and SCC Upgrade Teams and the Post-Live AE will be scheduled
During this meeting, the following issues will be discussed:
Any outstanding issues that will remain with the implementers until resolution
Designated date for formal handoff
Client concerns

13. Summary Getting Started Planning Working with your assigned SCC Team
Project Execution
Go-Live
Wrap Up

14. Questions?
When questions you have, asking is good, Padawan