With their deep business and technical knowledge and experience, our consultants draw up a clear picture of your needs and give you the best system architecture and design.
Key Benefits/Deliverables
Gap Analysis and Functional Specification
-
Review your business and product needs versus immense Avaloq Banking System capabilities
-
Review control procedures, information and work flows under the Avaloq Banking System environment
-
Development of a Gap Report to identify missing functionality and to propose and prioritize the development of relevant solutions
-
Development of a Functional Specification that will outline all the menus, screens, enquiries, reports and advices-and the associated control procedures, information and work flows that will be in the delivered system
System Architecture Design
-
Review existing systems that will survive after Avaloq Banking System is implemented and their integration and interfacing requirements
-
Review current and projected business volumes and expected performance times (online as well as End-of-Day batch)
-
Development of a Systems Architecture Report that will specify the interfaces to be developed and their related automated reconciliation controls, implementation design (modules to be used, single versus multi company set-up, etc.), platforms
(hardware, database and network) that will satisfy the performance requirements
Data Conversion and Reconciliation Strategy
Review existing systems that will be replaced by Avaloq Banking System and the condition of available data in them with the view to migrating this data to Avaloq Banking System.
Review the computation of derived data (accruals and revaluations) between existing systems and Avaloq Banking System to determine possible known reconciliation difference behavior Development of a Data Conversion and Reconciliation Strategy Report that will describe the data migration approach (manual versus automated), automated data conversion and reconciliation routines required, reconciliation approach to be used (given know differences in derived data behavior)