Contents
1. Preface
1.1 Introduction
1.2 Audience
1.3 Documentation Accessibility
1.4 Organization
1.5 Abbreviations and Abbreviations
1.6 Glossary of Icons
2. The Homework
2.1 Structure of Implementation Teams
2.2 The Project Plan
2.3 Methodology for Status Reports
2.3.1 Support Status Report
2.4 Components of the Project Plan
2.4.1 Management Summary of the Project
2.4.2 Project Plan for the Bank
2.4.3 Implementation Team
2.4.4 Project Monitoring
2.4.5 Hardware Planning
2.4.6 Hardware/Software Installation
2.4.7 Client Workstation Requirements
2.4.8 User Documentation
2.4.9 Oracle FLEXCUBE User Training
2.4.10 Security Management System and Controls
2.4.11 Branch Database Design
2.4.12 Static Data Input
2.4.13 Oracle FLEXCUBE System Trial Run
2.4.14 Contingency Plan
2.4.15 Stationery
2.4.16 Job stream formulation
2.4.17 Pre-conversion trial run
2.4.18 Financial conversion
2.4.19 Parallel Run
2.4.20 Index
3. Audit Requirements
3.1 Controls
3.1.1 Controls during Software Installation
3.1.2 Controls during database Set-Up
3.1.3 Controls during System Trial Run
3.1.4 Controls while making a change to the Code
3.2 Project Documentation
3.2.1 Management Documentation
3.2.2 System Documentation
3.2.3 Software Installation
4. Database Design
4.1 The Designers
4.2 The Design Process
4.3 Review of Products
4.4 Review of Account and Ledger Structure
4.5 Outlining Basic Core Parameters
4.6 Gathering Customer Data
4.7 Outlining Product Level Parameters
4.8 Review of Advice, Reports and MIS Requirements
4.8.1 User Profiles Including Access Rights, Transaction and Authorization Limits
4.8.2 System Performance Parameters
4.8.3 Other Activities
4.8.4 Review of the Design
5. Data Input
5.1 Approach
5.2 Methodology
5.3 Core Parameters and Tables Input Sequence
5.3.1 Core Parameters (Miscellaneous) Maintenance
5.3.2 Bank/ Branch Parameters
5.3.3 Accounting Period Maintenance (Bank/ Branch Parameter)
5.3.4 Holiday Maintenance
5.3.5 System Date Maintenance (Bank/Branch Parameter)
5.3.6 Customer Maintenance
5.3.7 Other Bank/Branch Parameters
5.3.8 Revaluation
5.3.9 Limits
5.3.10 Customer Accounts
5.3.11 Front-End Module Product Set-up
6. Database Callback
6.1 Suggested List of Reports for Callback
7. System Trial Run
7.1 The Logistics
7.1.1 The Database for Trial Run
7.1.2 The Approach
7.1.3 Components of the Trial Run
7.1.4 Components of the Test Plan
7.1.5 Handling Errors
7.1.6 The Schedule
7.1.7 Phase One
7.1.8 Phase Two
7.1.9 Phase Three
8. Financial Conversion
8.1 The Players
8.2 Scope
8.3 Planning
8.3.1 How to do
8.3.2 When to do
8.3.3 Methodology
8.3.4 Conversion Sequence
8.3.5 Pre-conversion Checklist
8.3.6 Standard Instructions for Conversion
8.4 Conversion Procedure
8.5 Sample Conversion Accounting Entries
9. Parallel Run
9.1 Callbacks
9.1.1 Training
9.1.2 Dummy Conversion/Parallel
9.1.3 Summary
10. Contingency Plan
10.1 Operation Risk Assessment
10.1.1 Brief Description of Location and Operations
10.1.2 Major Causes of the Operational Risks
10.2 Contingency Planning
10.3 Software Errors Outside Normal working Hours
10.3.1 Contingency Plan Distribution List
10.3.2 People who can Authorize Emergency Measures
10.3.3 Contact Points in Case of Hardware and Software Problems
10.4 Potential for Exposure and Containment Measures
10.4.1 Hardware Failure
10.4.2 Containment Measures
10.4.3 Disk Drive Failure
10.4.4 Remote Branch Communications/Modem Failure
10.4.5 Software Failure
10.4.6 Utilities Failure
11. Post Implementation Review
11.1 Overview
11.2 Post Implementation Review Guidelines
11.2.1 System Environment
11.2.2 System Administration Issues
12. Implementation Sign-Off
12.1 The Sign-Off Procedure