1.1 Structure of the Implementation team
This topic explains the structure of the Implementation team.
The first step, on receiving information of a proposed implementation, is to constitute the team for the implementation.
The size and structure of the team could vary across implementations based on the size of the client and other factors. The team size in the case of a normal implementation would be two with a mix of one functional and one technical person.
Table 1-1 Personnel and Responsibilities
Personnel | Responsibilities |
---|---|
Functional Member |
User Training (Functional) Requirements study Data Setup / Conversion |
Technical member |
Installation Data Center Training Resolving of errors Data Conversion |
- Project Manager identified from one of the two persons in the implementation team on the client site.
- A Project Manager identified from the client’s side who would be the single point of communication from the client’s side.
- A Project Manager for the implementation stationed at Bangalore.
- A designated member of the Oracle Flexcube Investor Servicing Support team.
Reporting Structure for Implementation
Figure 1-1 Reporting Structure for Implementation
Table 1-2 The nature of interaction between each communication
Between | And | Nature of communication | Frequency |
---|---|---|---|
Project Manager (Client) | Project Manager (Implementation team onsite) |
Implementation issues Status Reporting |
Periodic (e.g., daily / weekly) |
Project Manager (Client) | Project Manager (Bangalore) | Implementation issues | As and when required |
Project Manager (Implementation team onsite) | Project Manager (Bangalore) |
Status Reporting Implementation issues New requirements |
Periodic (e.g., daily / weekly) |
Project Manager (Implementation team onsite) | Oracle FLEXCUBE Investor Servicing Support |
Errors encountered on site Upgrades from Support |
Periodic (e.g., daily / weekly) |
Parent topic: Pre Implementation Tasks