Presentation on theme: "Capital Banking Solutions A Fresh Start in Banking Systems By Vantage Business Systems."— Presentation transcript:
Capital Banking Solutions A Fresh Start in Banking Systems By Vantage Business Systems
Capital Banking Solutions Background Driving factors Technology Main features Sample functional features Client systems Implementations Shariah products Conventional products
Capital Banking Solutions Background Vantage Business Systems was founded to fill a glaring gap in the market for banking solutions The Capital Banking System was developed: –By a team of banking experts –Using the latest proven technology –For innovation, not renovation –Using open and simple design techniques
Innovation, not renovation Capital is a brand new banking system It is not a repackaged dinosaur Dinosaur Repackaged dinosaur
Capital Banking Solutions Driving Factors Ease of implementation and enhancement Fast product development Security Top performance Unlimited scalability Non stop 24/7 processing Design simplicity and flexibility Hardware platform and database independence Ease of interfacing to other systems Reporting flexibil ity
Technology Latest proven open technology: –Java EE –EJB3.0 –Web services –SOA compliant –XML based messaging –Platform independent –Database independent –User interface independent
Capital keeps things simple With one Java bean per transaction Simple Complex
Capital features Fast and intuitive user interfaces Multi-language, multi-time zone and multi- calendar Flexible interfaces (XML, ISO8583, Web Services, proprietary formats) – Clearing, data feeds, rate updates, data warehouse etc Security can be interfaced to any encryption / compression method –All messages are encrypted and compressed –Role based access to data and transactions –Local, remote and central transaction authorization
Capital features Choice of internal Capital GL and / or external corporate GL Complete audit trails (financial and non- financial) Versioned parameters Drilldown inquiries to the lowest level Automated documentation Automated data dictionary (from screens down to database) Robotized front-end regression testing Back-end regression tests using JUnit test plans
Sample functional features Centralise reporting IFRS/PSAKCalculator Workflows Vault Management Integrated debit card and cheque system Controlled and secure transaction reversal Sweep and standing order processing Fees and charges Customer / Account access and transaction restrictions Local and centralised supervisor override Alerts Teller Limits
Client systems and interfaces Internet banking (integrated system available) SMS banking (integrated system available) Mobile banking (integrated system available) ATM / EDC / EFTPOS Payments (RTGS, Swift) Payroll Bill payments Clearing Remittances Treasury
Implementations Shariah and Conventional Both implementations are independent –The Shariah system is not built as an extension of the Conventional system We can deliver: –Pure Shariah –Pure Conventional –Mixed Shariah and Conventional with a logical separation of funds and accounting
Banking System Implementation Overview Tasks Pre Sales (Business Partner / VBS) Sales (Business Partner / VBS) * Project Management (Business Partner) * Business Analysis (Customer / Business Partner / VBS) Marketing (Business Partner / VBS) * Gap Analysis (VBS / Business Partner) Technical Analysis (VBS / Business Partner) Customization (VBS) Data Conversion (Customer / Business Partner / VBS) * Hardware Sizing (Business Partner / VBS) *
Banking System Implementation Overview Tasks (continued) Database Tuning (VBS / Business Partner)* Unit Testing (VBS) System Testing (Business Partner / VBS) * Regression Testing (Business Partner / VBS) * Benchmarking (VBS) QA Testing (Customer) Pre Production Testing (Customer) Operations Setup (Customer / Business Partner / VBS) Production (Customer)
System Configuration and Sizing Overview These sizings are suggestions/guidelines only. Actual sizing and requirements are dependent upon many factors, such as: number of accounts number of customers data retention policies system usage and procedures etc.
System Configuration and Sizing Small Bank A typical Small Bank would have 1,000 – 100,000 accounts and process 1,000 - 20,000 transactions per day. Total data storage would likely be under 4GB, this makes Oracle XE a possibility to lower costs. This may not be acceptable to the bank as this removes the possibility of using Oracle DataGuard for DRC and limits vendor support, this is a cost/benefit decision for the customer to make. A small bank can comfortably run this system on a single CPU server with 4GB of memory.
System Configuration and Sizing Medium Bank A typical Medium Bank would have 100,000 – 1,000,000 accounts and process 20,000 - 100,000 transactions per day. Total data storage would likely be between 10GB and 50GB. We recommend full Oracle Enterprise Edition with Oracle DataGuard for live data copy to DRC. A Medium bank can comfortably run this system on a six CPU server with 8GB of memory. Typically, they might run 4CPUs with 4GB of memory for the application server and 2CPUs with 4GB for the database server. Application and Database clustering is a likely requirement here and is a cost/benefit decision for the customer to make.
System Configuration and Sizing Large Bank A typical Large Bank would have 1,000,000 – 20,000,000 accounts and process 100,000 - 5,000,000 transactions per day. Total data storage would likely be between 50GB and 2TB. We recommend full Oracle Enterprise Edition with Oracle DataGuard for live data copy to DRC. A Large bank can comfortably run this system on a 48 CPU server with 200GB of memory. Typically, they might run 24CPUs with 100GB of memory for the application server and 24CPUs with 100GB for the database server. Application and Database clustering is highly recommended for a large bank.