Sunday, June 19, 2016

Project Delivery Process D668

D668 - Setup, Transport & Verify Live Configuration

SIIPS Delivery Processes (D).png

DEFINITION

SIIPS D668.pngTransport the tested final Application Software configuration into the live environment and check that it has been correctly set up.

SUMMARY

Use Application Software transport and correction facilities to move the final tested configuration into the live environment.  Verify that the configuration has been fully and correctly transferred.  Proper change control procedures should be followed for each update.

PATH PLANNING GUIDANCE

This process is normal practice for Application Software implementations.

DEPENDENCIES

Prerequisites (Finish-Finish):
  • Implement live server systems - hardware / software / database (D666)
  • Plan, prepare and conduct user / system/ acceptance and integration testing (D800)
  • Plan, prepare and conduct technical tuning and volume testing (D810)
  • Evaluate testing and report results (D812)
Dependent procedures (Finish-Start):
  • Decision to go live (D900)

RECEIVABLES

  • Tested and accepted system
  • Application Software online Implementation Guide
  • Application Software Documentation
  • Business process documentation and specifications
  • Existing Forms and Reports
  • Application Software Technical Documentation
  • Testing Results

DELIVERABLES

  • Fully configured live configuration ready for live running

TOOLS

  • Application Software correction system and version management

DETAILED DESCRIPTION OF TASKS

The full configuration should have been set up, tested and accepted in the testing region.  Use the Application Software transport system to move the configuration into the live region and check to ensure that the transport was fully successful.
The Application Software may have a correction system built into the development environment  for the purpose of correcting objects, working with the transport system, organising corrections and transporting them.  Together the correction and transport systems record and document all changes and by whom they were made.  They analyse options, provide distribution logistics for automatically supported distribution of software development, and the control the creation and management of versions during changes to software elements (ie restoring and comparing versions).
Correction updates should be monitored with regularity and the facility should never be turned off.  Failure to use the corrections system correctly could result in serious damage further on.
In addition to the initial transport of the live configuration, the same process may be used for transferring subsequent updates and changes, subject to proper change control.  Bear in mind that any changes will need to be authorised, fully tested and accepted before entering the live environment.  With a live system, always consider the retrospective effect of any change - is the new way of doing things compatible with old and current transactions and master data?
Once the live configuration has been transferred, a set of basic tests should be run, based on test cases, to ensure that the transport has been complete and correct.  However, it is important to ensure that this test data is removed and cannot affect the live data to be introduced to the system.

Once the live configuration is ready, start up data may be entered or transferred from the data conversion processes (see Process D875, D880, D890).

No comments:

Post a Comment