Realisation PDF Print E-mail

The purpose of the realisation phase is to implement and test the financial solution and to enable it to go live in a productive environment. This is done according to the design documents that were created during the design phase.

The realisation phase consists of four elements:

  • Implementation
  • Test
  • Preparation
  • Go Live

These are presented below.

Implementation

During the implementation phase, the financial solution is set up based on the design documents. The implementation approach will differ depending on whether it is related to a system implementation, a process implementation or an organisational change.

In a system implementation, the system is set up according to the design set out in the design phase. This includes e.g. configuration of system settings, master data, interfaces, reports, and conversion strategy.

In a process implementation, processes are detailed and documented according to the design set out in the design phase.

In the implementation of a new organisation, the new roles and tasks are defined and people are identified so that the new organisation can be realised.

Test

During the test phase it is ensured that the final solution has the characteristics that are required according to the design as reflected in test cases. During this phase, module tests, integration tests as well as user acceptance tests (UAT) are performed.

Test cases are developed covering ordinary use and special areas such as e.g. negative test, roles, effect of limited access rights, and segregation of duties. Once the test cases are developed the module tests and solution integration tests are performed using these test cases.

Testing of a system is performed to verify e.g. system configuration, master data, interfaces, reports, and special development.

Testing of data is performed to verify e.g. the quality of stored data after testing, including deal data, audit trail, log, accounting and payments.

Testing of processes is performed to verify e.g. that automated and manual processes are well defined, that the individual process steps are well defined and correctly interpreted by the users.

Testing of organisational structures is performed to verify that e.g. reporting lines, roles, tasks and support functions are communicated and understood.

The phase ends with the UAT of the solution. When the UAT has been signed off by the customer, the solution is ready for preparation to go into production.

Preparation

During the preparation phase, the solution is transported to production environments and production data are migrated to the new system solution.

The users check that the agreed system functionality, together with processes and new organisational roles and responsibilities, works in the production environment as well as it did during the test period. 

Finally responsibility for support is transferred to the competence centre personnel.

Go Live

During the go-live phase, end users are given permission to use the new solution. During this phase competence centres are standing by with support functions to solve any potential issues immediately. The most important task onwards is for the competence centres to provide end users with training and solution support.

If the implementation is of a new system solution, a parallel run with the old solution may be carried out.