Migration reference projects

Development bank

Migration reference project

Company: development bank
Initial situation: Migration Front Arena 2.2 to Front Arena 2011.1

  • Migration of all productively used Front Arena components
  • Connection and migration of the real time interace to SAP
  • Adaption of ARENA functions, development workarounds
  • Training and introduction of employees to the new release

  • Migration of subledgers
  • Performance optimisation
  • Change of back office processes to the operations manager
  • Adaption and test of extensive interfaces from and to FRONT ARENA
  • Migration and test scenario functions
  • Analysis and migration of bank owned MtM scripts and day end and year end processing
  • Adaption and test of validation rules

  • Development of a test architecture
  • Execution of regression tests
  • Analysis and adaption of used ARENA functions
  • Plausibility of differences of the regression test
  • Project and milestone planning
  • Development of a migration manual
  • Communication with departments and the producer
  • Support of the system and the applicant
  • Consolidation and optimisation of the used modules
  • Adaption and test of the bidirectional interfaces to SAP

  • Usage of the operations manager to standardise back office processes
  • Unification of evaluation functions with the help of calculation spaces, ACM and ADFL
  • Usage of vertical portfolio sheets
  • Optimisation and development of the scenario analysis functionality (Trading Manager, RF scenario functions)
  • Integration of adaptive into the streamlining and inification fo bank specific processes
  • Direct exertion of influence on development of the releases with the help of close dialogues between bank, service providers and producers by named partnership

Mortgage bank

Company: Mortgage bank
Initial situation: Migration Front Arena 1.5 to Front Arena 2.1

  • Migration of all productively used Front Arena components
  • Connection and migration of the real time interface to SAP
  • Analysis and adaption of used ARENA functions
  • Training and introduction of staff to the new release

  • Migration within a timeframe of 3 months
  • Conversion of the client (Prime) from Unix (Exceed) to Windows
  • Analysis and adaption of used ARENA functions
  • Training and introduction of staff to the new release

  • Support with the development of the test architecture
  • Support with the execution of regression tests
  • Analysis and adaption of used ARENA functions
  • Plausibility of differences of the regression test
  • Support with project planning
  • Preparation of the migration manual
  • Communication with the departments and the producer
  • Follow-up support with the system for applicants
  • Consolidation and optimisation of used modules

  • Optimised display and evaluation of traded financial products
  • Optimisation and extension of used reportings
  • Integration of the client to the Windows architecture of workstation computers
  • Operative separation of server hosting (Unix) by the computer centre and Client (Windows NT) on-site
  • Higher application acceptance of applicants of the departments
  • Release-conform and audit-proof documentation of all modules, interfaces and processes

Investment bank

Company: Investment bank
Initial situation: Migration of Front Arena 1.6 to Front Arena 2.1

  • Migration of all productively used Front Arena components
  • Migration of interfaces
  • Analysis and adaption of BDP (MtM, year-end evaluation)
  • Analysis and migration of all ASQL reports

  • Conversion of the client (Prime) from Unix (Exceed) to Windows
  • Introduction of new Python versions
  • Extensive portfolio of financial products
  • Exotically structured products
  • Introduction of real time contributing and quoting out of Front Arena

  • Project and milestone planning
  • Adaption and test of ASQL reports
  • Plausibility of differences of reporting tests
  • Adaption and tests of year-end evaluations
  • Introduction of ACM and ARENA Python
  • Preparation of the migration manual
  • Communication with the departments and the producer
  • Migration and productive rollout
  • Follow-up support with the system for applicants

  • Optimised display and evaluation of in-stock financial products
  • Optimisation and extension of used reportings
  • Performance improvement
  • Higher application acceptance of applicatants of the departments
  • Introduction of new functionalities by ACM
  • Exact compliance of the project budget