Skip to content

good practice and innovation
about us infoKits Tools & Techniques Publications Events
You are here: Home » infoKits » System Implementation infoKit » Conducting a System Implementation » Go-Live and Beyond » Setting Up the New System

Setting up the New System

As described in the installation section of this infoKit, the system set-up activities should have been rehearsed many times during the build up to 'Go live'. Those people charged with the responsibility of setting-up the new system should by now be familiar with the process and have a detailed understanding of each task and the timings involved so that little should come as a surprise at this point. Accurate calculations such as the downtime required to convert from the old system to the new are possible only with such detailed preparation. Many of the 'building blocks' for the new production system may have already been put in place while testing and training on other instances - e.g. lists of values already populated - and so largely the cutover task at this point is the migration of 'live' data from the legacy system(s) to the new. As described in the Data Migration section of this infoKit, the final conversion of data from the old system(s) to populate the new is critical and any problems when populating data will likely impact the schedule, the level of service provided and damage what would otherwise be a otherwise faultless implementation.

Detailed task checklists should have been prepared and tested on the basis of the other instance set-ups and responsibility for each task should be allocated. The tasks are likely to include the following:

Task Status
All hardware (e.g. production server) has been installed and properly configured  
All networking facilities have been installed and properly configured  
The communications software has been installed and properly configured  
The operating software has been installed and properly configured  
The software has been installed and properly configured  
All system tables populated, and are accurate and complete  
All system interfaces function correctly  
System access user-ids and passwords have been distributed and work correctly  
Sufficient supplies of forms, etc are in stock  
Unrecoverable components of old system backed up and accessible in case of go-live failure  
Performance of the new system is satisfactory  
Initial installation and configuration of new system backed up and accessible for recovery purposes  
Initial data converted to the new system backed up and accessible for recovery purposes  
Standards and system documentation has been distributed and is available  
User and technical manuals have been distributed and are available  
All aspects of the system support function are in place  

Bookmark and Share
If you can read this text, it means you are not experiencing the Plone design at its best. Plone makes heavy use of CSS, which means it is accessible to any internet browser, but the design needs a standards-compliant browser to look like we intended it. Just so you know ;)