3.5 Parallel Run

This topic explains how the postings on Oracle FLEXCUBE and the existing system (manual or otherwise) will be conducted, the callbacks and reconciliation to be performed.

Parallel Run

The parallel run is an exercise which is applicable in all cases other than start up organizations. This milestone begins on completion of the User Acceptance Test. During a parallel run, the client will start using the system for its every day operations while retaining its existing system. Both the existing system and FCIS will run parallel with each other during this phase.

The parallel run is a method used for the smooth transition of the organization from an existing system to a new system. The existing system could be either manual or automated. During the parallel run, both systems are run so that in the event of one system failing, the other is available to fall back on. The period for the parallel run is influenced by the time perceived by the client to develop sufficient confidence in the new system so as to cut off the existing system.

This could vary based on,
  • The size and complexity of operations
  • The level to which the end users are comfortable with the usage of the new system.

The duration could vary from between 15 days to 1,2 or 3 months as the case may be. The duration of this phase is normally decided by the client.

Verification
During the parallel run, the transaction information from the system should be compared with the existing system on a daily basis before moving to the business day. It is important to reconcile all differences before moving to the next day. The information to be verified includes:
  • Transaction details
  • Allocation details
  • Fees / Incentives applied
  • Fund & Unit Holder unit balances
  • Dividend & Reinvestment Processing information (when applicable)
  • Unit holder accounts created / modified / closed
  • Standing Instructions set up / generated

The parallel run is a phase during which the end users are stretched as they would have to carry out the same work in two systems. As a result of this, it is imperative that the system should perform smoothly and problems, if any, should be handled by the team keeping in mind the sensitivity of the situation. A smooth parallel run increases the comfort level of the end users and helps in the acceptance of the system by the users.

In a normal situation, only one Oracle Financial Services Software Limited consultant will be available on site during the parallel run with the other leaving on completion of the UAT. However, this is not a rule and could vary from one implementation to another.