The Deployment and Post-Implementation Support phases ensure complete and correct implementation of the new software and databases. ATERAS may be involved in this phase at any level, depending upon the requirements.

The deployment phase can take on several forms based upon the target processing environment. The DB-Shuttle^TM automated conversion process does not require any code freeze. All source code that has changed since the initial collection is re-collected in the final days before the cut-over night or weekend. All code that has been changed by customer teams since the prior collection is re-collected, re-converted and re-delivered for final testing. This final testing window is generally scheduled for the last few days before the cut-over date.

The customer’s end-user community may need minimal training in how to access the new processing environment. If the conversion includes an entire platform change, more detailed training and additional information may be required for the end-user community.

From the technical side, the converted software can be staged prior to the cut-over so that the activity during the cut-over period will revolve around the data rather than around the software. At the cut-over point, the former database data will be extracted and the new databases will be populated using the same processing streams that were used throughout the testing phases. These streams are benchmarked and documented during the testing phase, and the results of these benchmarks are used to define the cut-over plan in detail.

On the cut-over night or weekend, the ATERAS Conversion Team will be on hand to assist with any issues. The Conversion Team will also assist with any plans for de-commissioning the old databases and applications.

The ATERAS conversion includes training and education for customer teams. ATERAS Project Management teams will present the new databases, languages and tools to customer teams. The education for the transition between languages and databases is based upon the comparison of the new technologies to the existing knowledgebase of the customer teams. The final conversion results in 100% functionally equivalent code and is maintainable n-tier architecture.Therefore; the level of user retraining is relatively small and is customized for each customer.

Training and education takes on many forms throughout the conversion cycle. Informal training on special topics is performed on an as needed basis for the customer team members who are involved in the migration aspects. Formal training is generally held at the customer site prior to implementation of the new databases and languages. The new databases, languages and tools are presented using the customer applications, databases and desktop setup for any new tools. In many cases, the classroom exercises can be based upon changes that may be planned for the customer databases or applications.