1. A Software Installation DuetBy
JoAnn Logue-0’Malley
Roseann Ferrara

2. Client Scope New Clients in the Implementation Phase
Existing Clients in the Upgrade Phase

3. Presentation Premise
Software Installations are DUETS with collaboration between CLIENTS & SCC through the process.

4. Presentation Objectives
Describe CLIENT steps involved in a Software Installation and/or synchronization
Describe SCC steps involved in a Software Installation and/or synchronization
Scope includes installation of Software/Hot Fixes and Operating Systems

5. Terminology SIF = Software Installation Form
SYNCH = Software Synchronization
SWI = Software Installation
SSS = Software Support Service
DM = Development Manager
SE = System Engineer
AE = Account Executive/Account Manager
CSR = Client Support Representative
VP OPS = Vice President of Operations
CAB = Change Advisory Board
CCB = Change Control Board
IC = Software Installation Coordinator

6. Client Requests Software Installation
Contact your account manager to determine what hot fixes are available or to discuss patch or upgrade options
Conference Call

7. TO SIF OR SYNCH? THAT IS THE QUESTION
SIF = Software Installation
SYNCH = Software Synchronization from a SOURCE environment to a TARGET environment
SIF is ALWAYS done 1st to a SOURCE ENVIRONMENT (the only exception is when there are space limitations)
SIF does NOT INCLUDE SETUPS it is for SOFTWARE ONLY
SYNCH CAN include SETUPS or can also be Software only

8. TO SIF OR SYNCH? THAT IS THE QUESTION NEW Environments
For NEW ENVIRONMENTS in preparation for example for an upgrade or patch project the following occurs
SYNCH OF CURRENT LIVE SOFTWARE AND SETUPS IS DONE 1ST TO THE NEW ENVIRONMENT
SIF FOR NEW VERSIONS OF SOFTWARE IS DONE TO THE NEW ENVIRONMENT AFTER SYNCH IS COMPLETED
AFTER NEW ENVIRONMENT IS COMPELTED SETUPS NEED TO BE MAINTAINED MANUALLY BETWEEN THE TWO ENVIRONMENTS
This effort is required because the applications and the databases are now different and data entry can also be different! The application and the databases both now have a delta and data entry must occur within version

9. TO SIF OR SYNCH? THAT IS THE QUESTION SETUP COMPARISON
SCC Internal Change Control Board (ICCB) Project approved
Target 3Q or 4Q 2014
Requirements
On Demand Report that can be requested by Client – AE – Module Specialist
Compare Significant Setups between a SOURCE environment (i.e. TEST and LIVE etc.)
Produce a report of the DELTA between the two with data elements of primary keys listed.
Report will be required to be run PRIOR to A SIF – SYNCH
Report will be required to achieve GO LIVE READINESS – any delta identified will be signed off on by clients as valid or will need to be corrected manually prior to go live

10. SCC Processes SWI Request From Client
AE Creates SWI class TMS task
with description of Software Load
LIVE DEMO

11. SCC Processes SWI Request From Client
AE creates SIF
(uses TMS Task # from SWI task)
LIVE DEMO

12. SCC Processes SWI Request From Client
Release Management Reviews SIF Form
SIF Approval Process
DM – SE – VP Approvals
LIVE DEMO

13. SCC Processes SWI Request From Client
AE Checks with Software Installation Coordinators (IC) for available installation dates to present to client for scheduling
LIVE DEMO
SWI Calendar

14. SCC Processes SWI Request From Client
AE receives notice SIF form has been approved
AE Reviews Downtime Estimate from SIF Form
AE Copies HF Summary from SIF Form into Word Doc & attaches the doc to the SWI task for client to review
AE Places the SWI task in xW status with action to the client about downtime estimate, attached HF summary and available installation dates
LIVE DEMO

15. Client - Change Management Submission and Approval Process
Client selects installation date from dates AE provides in SWI task
Client prepares required paperwork for submission to their respective change advisory boards (CAB) for approval and scheduling of the installation to TESTx or UPGx etc. environments
Client processes through weekly Change Advisory Board
Client notifies SCC of selected and approved date/time for the installation

16. Client – SIF Installation Request
Client selects installation date/time from dates AE provided in the SWI task
Client actions SWI task with permission to proceed on the selected date/time

17. SCC Processes SWI Installation Request from Client
AE Books SWI Install with Software Installation Coordinator (IC)
SE performs Installation and actions task to AE when done
AE places task in xW status for testing by client
LIVE DEMO
SWI Calendar / Installation

18. Client - Change Management (example)

19. Client - Retrieve HF Summary List (from TMS SWI Task)

20. Client - List of Patch Items
Client retrieves list of patch items from SCC web site
Release notes
Version on to Version moving to

21. Client - Example List

22. Client - Export to Excel

23. Client - Processing Hot Fix or Patch Items
Recommended Steps
Client Processes List
Hot fix number
Module
Description
Assigned to
Status
Associated TMS if applicable
Attach test plan
Notes
List items need to be managed for testing, validation and Ready for Live Status
Add hot fixes to list such as excel or SharePoint (recommended)

24. Client - List Content

25. Client - Laboratory Management Site

26. Client - SharePoint List

27. Client - Management Views

28. Client - LIS Project Site

29. Client - SharePoint List

30. Client - Management Views

31. Client Preparation for Validation
Client Additional Processes for Patch and Upgrade
For each Module Full Functional Scenarios
Cross Module Full Functional Scenarios
Interface and Interface Engine Customization Scenarios
Vallapalooza

32. Client Validates Hot Fixes
Client - Validation
Client Validates Hot Fixes
Test the hot fix if possible
Use SCC test plan if possible
Cover in General Functionality Testing
Defined set of test plans covering module functionality and interfaces

33. SCC - Vallapalooza Support
Develop communication plan outlining Key Contacts at SCC
Develop scheduling plan for Key contacts to be made available to respond to any immediate issues with client testing
Deliver additional fix and/or system and interface configurations in a timely manner
Assist with meeting clients Vallapalooza timelines on repeat testing

34. Vallapalooza Unit Testing

35. Vallapalooza Scenario Testing

36. Client Issue Tracker List
Validation Phases
Issue Status
Error Code

37. Release Note Progress

38. Client Workbook Progress

39. Vallapalooza Total Completion 95.4%

41. Validation Completion Status By Module for each OE System

42. Scenario Execution Status By Functionality/Module

43. Education

44. Client to Call “Go for Load”
Review SharePoint List for Completion
All outstanding issues have been mediated from Vallapalooza

45. SCC – Process SWI Scheduling Request for SYNCH
AE Creates SWI class TMS task for SYNCH to x environment
AE contacts Software Installation Coordinator to add SWI to the SWI calendar
IC schedules SWI on SEPOL Calendar
AE submits RFQ for dedicated support coverage for client to PO
Once PO is received DM lines up dedicated resources for Installation Manager to contact for issues that might occur during/after synch DM sends to AE – Installation Manager

46. SCC – Process SWI Scheduling Request for SYNCH TO PRODUCTION ENVIRONMENTS
Installation Manager requests breakout of downtime by module for presentation to client from SE –DBA teams
Installation manager attaches breakout in action to client for review with copy to AE
AE works with client to finalize date
Client actions task with permission for installation with date/time
AE and Installation Manager send notification to SE –DBA-Programming teams and 1800SOFTLAB Support

47. SCC – Process Client Request for SYNCH to Production SWI Scheduling
LIVE DEMO
SCC Calendar Scheduling Process

48. SCC Processes SWI Request From Client
AE Creates SWI class TMS task
with description of Software Load
LIVE DEMO

49. SCC Processes SWI Request From Client
AE creates SYNCH FORM
(uses TMS Task # from SWI task)
LIVE DEMO

50. SCC Processes SWI Request From Client
Release Management Reviews SIF Form
SIF Approval Process
DM – SE – AE - VP Approvals
LIVE DEMO

51. SCC Processes SWI Request From Client
AE Checks with Software Installation Coordinators (IC) for available installation dates to present to client for scheduling
LIVE DEMO
SWI Calendar

52. SCC Processes SWI Request From Client for SYNCH to Production Environment
AE receives notice SYNCH form has been approved
Software Installation Manager Reviews Downtime Estimate from SYNCH FORM and requests Module Breakout of downtime by SE for client and AE
AE Copies HF Summary from SYNCH Form into Word Doc & attaches the doc to the SWI task for client to review
AE Places the SWI task in xW status with action to the client about downtime estimate, attached HF summary and available installation dates
LIVE DEMO

53. Client - Request Time Line for Installation Steps by SCC to LIVE
Discuss with SCC the Date and Time for Loading to Production Environment
Enter Change Management for installation
A Timeline and Module impact is critical to determining messaging and communication
Minimize downtime Internal to Lab
Orders
Results
Downtime Number assignment
Minimize downtime External to Lab
Delay of results
SOFT ID and collection throughout hospital facilities

54. Client - Determine Load to Live
Communicate installation plans to Laboratory Leadership
Service Request for early release of EPIC lab orders for sweeps
Communication to Nursing and Physicians via IT Bulletin

55. IT Bulletin

56. Load to Production
Open Line of Communication between Client and SCC at 20 mins prior to installation
Communicate a periodic milestones during the implementation noting progress or problems
Client assumes on-call pager responsibility
Client prepares group page of testers ready to send at release

57. Client - Release to Users Steps
Page testers to begin General Functionality testing
Call key lab areas such as Stat Labs to verify no immediate concerns
Open Lync for Testers – start recording
Testers note progress
Testers note issues and TMS numbers
with SCC still open
Provide updates to SCC implementer on progress
Report issues and TMS numbers
Work to resolve all open issues

58. Load is Completed- Client Steps
Close Lync Session with Testers
Store recorded file on Change Management Entry
Send out all clear page to lab leadership
Return pager assignment to on-call person
Close Change Management
Close with SCC
Compose and send a Summary of the Load and send to IT and Lab Leadership
Bedtime

59. QUESTIONS Our Software Installations presentations DUET is now over
Hope you found this presentation Duet informative and enjoyable 
JoAnn and Roseann
X4223

60. Presentation Premise
Software Installations are DUETS with collaboration between CLIENTS & SCC through the process.