Web development, SEO and design by Interon Solutions (Pty) Ltd - South Africa
Disclaimer - Terms and Conditions
Disclaimer - Terms and Conditions
Copyright © 2008 Riskflow (Pty) Ltd - All Rights Reserved
SERVICES - Software Implementation
SOFTWARE IMPLEMENTATION:
Riskflow prides itself in participative implementations, where our highly skilled financial consultants work side-by-side with the bank’s key stakeholders. Each implementation is headed by a Riskflow Project Manager, working in close conjunction with the client’s Project Manager.
During project definition phase, logistical issues are addressed, a project governance structure is set up, the project scope is confirmed and users are briefed as to how the project will unfold.
During finalization of the implementation project plan (between the Riskflow project manager and the project manager appointed by the bank), key bank resources required during the various implementation stages are identified.
ALMAN Implementation
The implementation starts with a thorough analysis of the bank’s balance sheet, identifying the bank’s product offering (current and future), as well as other items on the Balance Sheet and Income Statement.
The process of model-building is done in collaboration with the bank’s appointed ALMAN modeler who, together with other identified users, undergoes product training throughout the implementation period.
Data extraction for importing into ALMAN - although a responsibility of the bank’s IT department - is performed with assistance by members of the ALMAN technical team.
A typical ALMAN implementation takes 12 - 16 weeks, with the time frame being dependant on the complexity of the bank’s balance sheet and the availability of extracted data.
An ALMAN implementation is not considered completed before the ALMAN model balances with the bank’s Management accounts and is signed off by all parties identified as key stakeholders such as the project owner and sponsor.
To obtain final project sign-off, the ALMAN model is presented to ALCO, with all of the bank’s positions, forecasts, future strategies, statutory requirements and modeling scenarios loaded. The presentation takes the form of a typical ALCO strategic planning session, where a Riskflow Executive consultant steps through the ALCO process whilst the ALMAN modeler runs what-if analyses on all the risk management strategies under consideration. This is a highly interactive final hand-over session, ensuring that Riskflow leaves the system in the hands of a trained user-base and a management committee that fully appreciates the vast horizon of possibilities available for pro-active ALCO.
TASMAN Implementation
After project definition sign-off, the implementation project starts with information gathering, during which the client’s existing Treasury business processes and existing systems are reviewed. This leads to the compilation of a complete business requirement specification document, which is submitted to key stakeholders for briefing and sign-off.
Based on the business requirement document, TASMAN is implemented by means of integration with existing internal systems, external systems (e.g. SWIFT, Reuters etc) and development based on user customisation requirements.
On user-acceptance of unit testing and integration testing, data conversions start, whilst at the same time, users are trained in term of the general usage of the TASMAN system, as well as the Front, Middle and Back Office modules. This means that, at the end of the implementation, users are trained on their own data and the training takes the form of simulation of actual treasury activities.
A typical TASMAN implementation takes 10 - 14 weeks, with the time frame being dependant on the complexity of the bank’s products, the number of modules that the client purchases and the availability of extracted data.
Riskflow prides itself in participative implementations, where our highly skilled financial consultants work side-by-side with the bank’s key stakeholders. Each implementation is headed by a Riskflow Project Manager, working in close conjunction with the client’s Project Manager.
During project definition phase, logistical issues are addressed, a project governance structure is set up, the project scope is confirmed and users are briefed as to how the project will unfold.
During finalization of the implementation project plan (between the Riskflow project manager and the project manager appointed by the bank), key bank resources required during the various implementation stages are identified.
ALMAN Implementation
The implementation starts with a thorough analysis of the bank’s balance sheet, identifying the bank’s product offering (current and future), as well as other items on the Balance Sheet and Income Statement.
The process of model-building is done in collaboration with the bank’s appointed ALMAN modeler who, together with other identified users, undergoes product training throughout the implementation period.
Data extraction for importing into ALMAN - although a responsibility of the bank’s IT department - is performed with assistance by members of the ALMAN technical team.
A typical ALMAN implementation takes 12 - 16 weeks, with the time frame being dependant on the complexity of the bank’s balance sheet and the availability of extracted data.
An ALMAN implementation is not considered completed before the ALMAN model balances with the bank’s Management accounts and is signed off by all parties identified as key stakeholders such as the project owner and sponsor.
To obtain final project sign-off, the ALMAN model is presented to ALCO, with all of the bank’s positions, forecasts, future strategies, statutory requirements and modeling scenarios loaded. The presentation takes the form of a typical ALCO strategic planning session, where a Riskflow Executive consultant steps through the ALCO process whilst the ALMAN modeler runs what-if analyses on all the risk management strategies under consideration. This is a highly interactive final hand-over session, ensuring that Riskflow leaves the system in the hands of a trained user-base and a management committee that fully appreciates the vast horizon of possibilities available for pro-active ALCO.
TASMAN Implementation
After project definition sign-off, the implementation project starts with information gathering, during which the client’s existing Treasury business processes and existing systems are reviewed. This leads to the compilation of a complete business requirement specification document, which is submitted to key stakeholders for briefing and sign-off.
Based on the business requirement document, TASMAN is implemented by means of integration with existing internal systems, external systems (e.g. SWIFT, Reuters etc) and development based on user customisation requirements.
On user-acceptance of unit testing and integration testing, data conversions start, whilst at the same time, users are trained in term of the general usage of the TASMAN system, as well as the Front, Middle and Back Office modules. This means that, at the end of the implementation, users are trained on their own data and the training takes the form of simulation of actual treasury activities.
A typical TASMAN implementation takes 10 - 14 weeks, with the time frame being dependant on the complexity of the bank’s products, the number of modules that the client purchases and the availability of extracted data.
