Deployment

Implementation Plan (including Rollback plan)

Implementation plan has been followed to deploy to Test and updated in case of issues found

Rollback plan has been documented.

Production Branch in Bamboo can be deployed to overwrite project changes in the event of issues occurring.

DSOR (Release 1-n)

John Chan

13/04/18

Implementation Risk Assessment

A risk assessment has been undertaken for the Implementation Plan and selected deployment dates.

Approved by GoCab

ASOR (Release 1-n)

John Chan

13/04/18

TAD/Operational Document

Documentation complete

Action: The Document must be copied to the Wiki

No changes to TAD

ASOR (Release 1-n)

John Chan

13/04/18

Review EOL spreasheet to ensure new versions and servers are updated or added to this list.

Sharedpoint with USG, CSG and ISG EOL spreadsheet

https://uoe.sharepoint.com/sites/TechnologyEndOfLife2018

Current EOL technology register

https://www.wiki.ed.ac.uk/display/insite/2018%3A+Technology+End+of+Life+Register+for+Software+and+Infrastructure

No change

John Chan

13/04/18

System Design Specification (SDS)

Document complete and accurate.

Action: The Document must be copied to the Wiki

ASOR (Final Release  / Handover)

John Chan

13/04/18

System Description Document

Document complete, accurate and it has been reviewed by Application Management

Action: The Document must be copied to the Wiki

version 1.9 uploaded

ASOR (Final Release  / Handover)

John Chan

13/04/18

Scalability/Load Testing

Adequate load testing has taken place. The results have been recorded and analysed to ensure that the application will cope with the anticipated load.

No change to number of users.

ASOR (Final Release  / Handover)

John Chan

13/04/18

Performance

The application has been tested against stated performance criteria. Performance has been assured by user and support staff testing.

No issues raised with the performance of running the reports/application during UAT.

ASOR (Final Release  / Handover)

John Chan

13/04/18

Source Code available in GIT

Source code has been secured in GIT and Production branch is up-to-date

Action: ensure Production Branch created

Where code is provided by a third party (e.g. supplier) it has been established who is responsible to maintain source code

Source code not in GIT but still in SVN.

DSOR (Final Release  / Handover)

John Chan

13/04/18

Configuration Management Database

The relevant details regarding new or changed infrastructure components have been added to the CMDB in unidesk

To be reviewed as there are still issues. Ji ra raised.

ASOR (Release 1-n)

John Chan

13/04/18

Change Control(s)

A Change & Release record has been created in Unidesk for the LIVE implementation request and notified to GoCAB if necessary

 Action: Record Unidesk number

C1803-052

ASOR / (Release 1-n)

John Chan

13/04/18

Test Log Review

A review of the test log (JIRA) has taken place to ensure all required actions have been completed.   If this is not the case, then confirmation on criticality of outstanding issues and action plan for resolution is required.

Must have Jiras have been completed. There are still other outstanding Jiras. To be reviewed by projects team.

ASOR (Final Release  / Handover)

John Chan

13/04/18

Application Management Handover

Handover to Application Management  and Development team is completed or arranged.

Action: record handover dates

JC and GP had handover on 12/04/18 at 10am-11am

ASOR (Final Release  / Handover)

John Chan

13/04/18

Support Accounts

Read access accounts or update current read access accounts have been set up for support staff(requires business owner approval)

No change

ASOR (Final Release  / Handover)

John Chan

13/04/18

Password Manager (PMP)

InfoKeep has been updated with all relevant account details including external supplier  accounts

No change.

ASOR (Release 1-n)

John Chan

13/04/18

Environment comparison

Database comparison between TEST and LIVE (might be required before and after go-live)

Not required as database object changes being done via Bamboo.

ASOR (Final Release  / Handover)

John Chan

13/04/2018

Client requirements

Does the application have specific client requirements, such as JVM/JRE versions, JInitiator etc

If so have these requirements been raised with Desktop services

Wiki pages to be updated:

[1] https://www.wiki.ed.ac.uk/display/insite/Corporate+applications+with+client+based+requirements

[2] https://www.wiki.ed.ac.uk/display/insite/Client+side+requirements+for+co...

ASOR (Release 1-n)

John Chan

13/04/2018

Technologies

Is there any new software or technologies involved? (Y/N)

If yes state any additional actions taken to ensure adequate handover to the production support team

ASOR (Release 1-n)

John Chan

13/04/2018

Access outside University

By default all web based applications are accessible outside University without use of VPN etc Wiki list

If not accessible from outside University this needs to be approved by Production Management.

ASOR (Release 1-n)

John Chan

13/04/2018

Vendor Access Required

Does vendor require db/app access (Y/N)

If yes, ensure access details are in TAD

ASOR (Final Release  / Handover)

John Chan

13/04/2018

Certificates

All changes to certificates or new certificates for this service have to be added to the certificate master list. The certificate master list is being managed by Applications Management This includes TEST and LIVE certificates and records type of certificate and expiry dates.

no change

ASOR (Final Release  / Handover)

John Chan

13/04/2018

Deployment Date(s)

Agreed date has been confirmed that allows adequate time for completion of Acceptance Sign Off Review.

See deployment strategy

ASOR (Final Release  / Handover)

John Chan

13/04/2018

Deployment Resources

IS and business area resources required for deployment, including those needed for post implementation checking and sign off have been secured.

ASOR (Final Release  / Handover)

John Chan

13/04/2018

Deployment Ownership

Responsibilities for managing the go-live, including: comms with service owner and end users, ensuring go live timescales are met, managing issues arising and managing comms between all teams involved in go live.

ASOR (Final Release  / Handover)

John Chan

13/04/2018

Service Announcement(s)

A Service announcement has been raised with the agreed deployment date on the alert system:

http://reports.is.ed.ac.uk/alerts/

Service announcements should be raised by Project Manager 10 days before go live, but no later than 4 days.

http://reports.is.ed.ac.uk/alerts/index.cfm?fuseaction=view_alert&alert_id=7431

ASOR (Release 1-n)

John Chan

13/04/2018

Reporting and Analytics

New BI Universes or substantial changes to Universes/report offerings need to be documented in the Information Portal managed by GaSP.

https://www.wiki.ed.ac.uk/display/IP/Information+Portal+Home

No change to the RETAIN universe

ASOR (Release 1-n)

John Chan

13/04/2018

Consider if a new application needs to be added to 24x7 monitoring tool

Not added to 24x7 this time.

John Chan

13/04/2018

Technical Architecture/Operational Document(TAD)

Documentation complete and accurately reflects the environment subjected to UAT.

no change

ASOR (Release 1-n)

John Chan

13/04/2018

Security

All security requirements, e.g. SSL encryption, IP based restrictions firewall requirements have been specified, tested and implemented in LIVE

no change

ASOR (Release 1-n)

John Chan

13/04/2018

User Accounts

John Chan

13/04/2018

Patching

Ensure that all applications have an agreed patching schedule and this schedule is agreed with service owners. Different technologies have different patching strategies:

Action update wiki: Windows, Linux

no change

ASOR (Final Release  / Handover)

John Chan

13/04/2018

Start/Stop scripts

Are Server Start-up/Shutdown scripts in place?

Including start-up procedure documented, enabled and tested

no change

ASOR (Release 1-n)

John Chan

13/04/2018

Ports

Port allocation file been updated:

https://www.wiki.ed.ac.uk/display/insite/Port+Allocation+on+Unix+Servers

no change

ASOR (Release 1-n)

John Chan

13/04/2018

Backup and Recovery

All backups as noted in the TAD need to be confirmed operational.

A test recovery of user data needs to be done to validate the integrity of the recovery mechanism and process.

no change

ASOR (Release 1-n)

John Chan

13/04/2018

DR Copy

DR copy to SECONDARY DB configured and tested (unless existing database which is already setup).

no change

ASOR/Release1

John Chan

13/04/2018

Logs

For all logs the following is in place:

• Logs are rotated and old logs are archived or deleted to ensure server space is not reached

• In production only minimal levels of logging is switched on (debug may be adequate on DEV, but not on Production

no change

ASOR (Release 1-n)

John Chan

13/04/2018

If project deploying new server make sure old servers are being decommission including removing passwords from PMP and patching restart Wiki

no change

John Chan

13/04/2018

Check that new and existing servers are being scan by Nessus

no change

John Chan

13/04/2018

Technology Management Handover

Handover to Technology Management  and Development Technology is completed or arranged.

Action: record handover dates

No handover required as only code changes.

ASOR (Final Release  / Handover)

John Chan

13/04/2018

Support Agreement (including any charging arrangements)

A support agreement OLA is in place for any new applications – including any hosting or support charges. Where external suppliers are involved an SLA should be in place as well.

Action: SLA  moved to wiki:

https://www.wiki.ed.ac.uk/display/insite/SLA+repository+-+Applications+Management

ASOR (Final Release  / Handover)

Jchan

13/04/2018

For new and existing application update the Appcatalogue

https://appcat.is.ed.ac.uk/

Jchan

13/04/2018

Time Recording Code

A Time Recording code for the application, if required, has been confirmed and set up (in ASTA)

Action: Does application require a separate entry for business area in ASTA

ASOR (Final Release  / Handover)

Jchan

13/04/2018

Disaster Recovery and Business Continuity

Appropriate DR/BC provision is in place and has been fully tested. Application DR/BC details have been transferred to the DR Portfolio and DR level (1, 2 or 3) has been agreed

ASOR (Release 1-n)

Jchan

13/04/2018

Test Environment

An adequate TEST environment has been established for the application which may be used by support to test future changes prior to releasing these in the LIVE environment.

ASOR (Release 1-n)

Jchan

13/04/2018

Hardware and Software Licensing

All required licensing is in place including maintenance/support arrangements with external suppliers.

no change

ASOR (Final Release  / Handover)

Jchan

13/04/2018

Browser Compatibility

Browser compatibility has been tested and compatibility information updated

See

http://www.ed.ac.uk/schools-departments/information-services/services/computing/application-development/application-support/supported-web-browsers/browser-application

 for details

no change

ASOR (Final Release  / Handover)

Jchan

13/04/2018

Portal Compatibility

Portal compatibility, where required, has been confirmed the Portals Service Owner.

no portal

ASOR (Final Release  / Handover)

Jchan

13/04/2018

Help Desk

The new application is recognised with the UniDesk (A business contact queue is defined where initial calls are raised with)

no change

ASOR (Final Release  / Handover)

Jchan

13/04/2018

User Guide Documentation

Appropriate documentation has been produced for users of the new application.

to be done by H&S

ASOR (Final Release  / Handover)

Jchan

13/04/2018

Training Material

Training material, if required, has been produced and is of an appropriate standard.

to be done by H&S

ASOR (Final Release  / Handover)

Jchan

13/04/2018

Demonstration or Walkthrough

Demonstration or walkthrough of the new application has taken place for other stakeholder.

not required

ASOR (Final Release  / Handover)

Jchan

13/04/2018

Web Sites and Other Document Sources

External and internal web sites have been reviewed to ensure that all application references are present, correct and up to date.

RETAIN wiki updated accordingly

ASOR (Final Release  / Handover)

Jchan

13/04/2018