Financial-Risk-Manager application suite

Foreword

Financial-Risk-Manager is designed to simplify trade and portfolio management, analysis definition and credit terms and conditions and data needed to run a Risk Management department.

As such Financial-Risk-Manage acts as your front and back-office system.

Financial-Risk-Manager was specifically designed to steer data for Risksvr™, it is however an open system and has been used successfully to drive many other applications.

Financial-Risk-Manager provides all the interfaces to define:

Trades, including Cash-Flows and implied Volatility Surfaces
Credit Data. (Counterparties, Accounts, etc)
Credit Risk Factors (Credit Curves transition Matrices, etc)
Analysis and Methodologies
What-If Stress test, Predictive Scenarios, etc.,..
Risk Factor Control
Custom Reports
Standardized Reports, etc

The standalone version of Financial-Risk-Manager available for download is an "enhanced" versions of the Financial-Risk-Manager interface available on-line.

The difference lies essentially in the Credit Risk Management capabilities available from the CreditRiskManager module included in the Win32 version.

CreditRiskManager provides an advanced Grid / Curve Editor interface to manage credit risk factors, such as Credit Curves drag & drop what-if , Transition Matrix Management (Time scaling and Rating System Translation) , Transition to Credit Curve Conversion, rating System Management, Asset/Obligor Correlations for time-To-Default computations, etc,

Although, both versions share the exact same source code, this module is not available due to web-browser interface limitations.

Are you trying out Risksvr™ ?

Risksvr™ is designed to work with Both Online and / or Standalone versions of Financial-Risk-Manager.
If you just want to try Risksvr™ out, you do not need to download Financial-Risk-Manager.

Instead run Risksvr™ directly by clicking on Run rather than Save during download. (internet Explorer Users only!) If you are using another browser you might only be given the choice to save.
If this is the case,

If you choose to run Risksvr™ online bear in mind you will need to maintain an active internet connection so that Risksvr™ can keep in sync with the online versions of Financial-Risk-Manager and time-Series-Manager.

Get Started

To run Financial-Risk-Manager on your computer two prerequisites must be satisfied:

A Database Server to which FRM can connect must be running with the Risksvr™ Database Schema installed.
A default Realm is necessary. The default Realm acts as the default data repository where data can either be sourced or sinked.

These two tasks are performed automatically for you during setup.

Setup will actually check you computer for any valid previous pre-requisites. if no valid database is already installed on your computer

Setup will install a database server with the necessary RiskServer Schema. This Database will not interfer with other existing databases running on your computer. .

Important:

If setup installs the database server, you will be asked to define your own administrator account and password. If your are not the administrator of your computer you might want to ask your administrator to do this for you

If a valid database is already configured on your computer, you will need to ask your system administrator to either:

create a new user with read/write /create permissions

Or provide a temporary access to the administrative user rights.

Once the database is installed you will be asked again to enter this administrative username and password.

Note: This is the username / password pair just defined or provided by your administrator.

This is important because setup needs proper user rights to install the Risksvr™ Database Schema. If you do not provide the proper user name (i.e. the user that has (read /write) privileges setup will fail!

For further information on database user access please see user access.

Once setup has installed the Schema, it will create a standard user account will lower privileges. Create user account by setup:

login	:	risksvr
password	:	risksvr

You are obviously free to you use this account or you can delete it and define other user accounts with lower or higher privileges.

If you haven't installed Risksvr™ and you are running setup for the first time, a wizard will offer to setup Realm path, name and alias for you.

In most cases, we recommend you accept the default values provided by the wizard

You can configure Realms and DataSources manually in the Settings Tab of the main dialog once setup has been completed.

For more information on Realms see Realms and DataSources section below

Minimum System Requirements

Currently Financial-Risk-Manager holds on 2.8 Mb of disk space. This highly compact footprint allows it to run on very tight configurations!

1. System Requirements for Installing Financial-Risk-Manager

Processor	Minimum: 400 megahertz (MHz) Pentium processor Recommended: 1 gigahertz (GHz) Pentium processor Dual processor if used in real-time or near real-time. If you run risk on a real-time basis or near-real time basis, we recommend you use a dual processor so other tasks can be performed in the background
Operating System	Risksvr™ can be installed on any of the following systems: Microsoft Windows 2003 Server Service Pack 1 (SP1) Windows XP SP2 with updates Windows Vista
RAM	Minimum: 96 megabytes (MB) Recommended: 256 MB
Hard Disk	Up to 100 MB of available space may be required, depending on the amount of data stored.
CD or DVD Drive	Not required.
Display	Minimum: 800 x 600, 256 colors Recommended: 1024 x 768 high color, 32-bit

Financial-Risk-Manager Installation: Known Issues

2.1 Download Failure due to Bad Administrative Password rights

The download and installation of Financial-Risk-Manager might fail if the Database connection is badly specified.

To resolve this issue

Define a proper root account. This procedure is explained in detail in the Database connection topic in the Help file.

2.2 Financial-Risk-Manager fails because the database cannot be installed.
This happens when users have installed previous versions of MySql.
Unfortunately, MySql does not remove it's database properly ! alas!
To resolve this issue
Check the Services utility and disable the MySQL running service. Remove the MySql Path in the Program Files directory. Finally check the LOCAL_MACHINE Registry Hive and Clean up the MySql Keys.