Foranx LLC is Temenos Certified Services partner. It has a right to to participate in T24 implementation projects as a service partner.
This stage of the methodology covers the Client Service activity necessary prior to a sale to determine the budgeting cost, team construction, governance, time-scales and best approach to a project.
There will be a handover meeting where the Sales department discusses with the project team all the documents produced and the areas discussed during the sales process. The next task of initiation will be to create a project agreement detailing the overall structure, key areas for consideration, a budget, agreement on resources and a project plan with clear objectives and the process detailing how those objectives will be met.
Both the project agreement and plan should be agreed and signed off by all parties involved.
This stage will also cover the process design for the monitoring and control of the project budget and the initial installation of T24 and a blank environment for build purposes.
The preferred method of training is for the user training to take place prior to the Analysis stage. This involves identifying all the key users (‘Super Users’) and arranging the appropriate training programme. From the business prospective the Super Users will be the main personnel involved in the project.
Once the users that require training have been identified, the training manger will contact the client to discuss the training approach. They will discuss items such as where and when the training will be delivered and what type of training best suits the Client’s requirements.
Analysis is completed by business area and is achieved by completion of a BRADD (Business Review and Design Document) for each of the areas relevant to the client.
Each area is divided into sections, e.g. Treasury is divided into money market, foreign exchange, FRA’s and SWAP’s.
The order in which each of the business area BRADD’s are completed is detailed within the project plan dependencies, as well as in the individual guides, and will be agreed at the initiation stage.
In addition to any contractual GAPS, i.e. any discrepancies identified during the sales process, the analysis stage is likely to identify some lesser issues, for example, localized field requirements.
The system build stage covers the physical configuration of information captured during the analysis process as well as guidelines on T24 environment management. The methodology itself can provide guidelines on the initial and secondary build of the system.
With respect to the initial build, the documentation highlights all of the relevant tables that need to be built and the sequence in which this should be executed. This has logically been split into complete business areas to enable BRADD completions to be synchronized with system build efforts. In addition, the build document provides information on some of the additional files that may be populated after initial build / migration tasks have been completed, with guidance on their effect within the system and the functionalities they provide.
Any part of the required system, which is not standard Temenos T24, will be covered during this stage. Any non-contractual client-specific off site developments will be priced and discussed with the client. The consultant will discuss any alternative solutions and the client will then decide if the development should proceed.
The development stage will also include agreement from all parties to the analysis stage results, all identified GAPs (from all stages) and solutions.
The internal development process has its own set of procedures, however, the implementation methodology seeks to clarify how we interface with development to achieve optimal management of project deliverables.
This stage will define the approach that should be adopted for the project-testing phase. This will not only include formalized user acceptance testing, but also pre-delivery testing of on-site developments, regression testing on receipt of new releases or patches.
The testing stage is standardized to ensure that all new functionality, irrespective of its source, has been tested to the same standard and in line with the same principles.
The testing will ensure the correct operation of parameter settings within the system and guarantee the client can use the system to meet all their business requirements.
This area will cover on site support after project go-live date and will usually involve keeping at least one member of the implementation team for a period of 1 – 3 months.
Their duties during this time consist of a range of tasks including help with any overnight failures, ad hoc informal user training and assisting with the first end of month batch run process. This stage will also cover the control and management of clearance of the GO LIVE issue list, as well as guidance on set up and administration. Once completed, the project will be passed to the Help Desk for the provision of any further support.
This stage will also include a full post implementation review wherein any areas for future beneficial associations, between Foranx/Temenos and our client may be identified.
Foranx specialists cover almost all stages of implementation process: from Initiation to Post Live.