CreditRate(TM) stores models and associated resources, such as source data sets, analyses, discussion histories, etc. all in a single place. If RFM's's FutureSim(TM) is used, simulation runs are also stored. So as well as providing secure storage for current and historical models, RFM's model repository will also become your organization's institutional momory.

Secure enterprise repository.
Models are version and access controlled in a way that blends the features of document management and source code control system. All changes are logged and are fully traceable and able to support the most granular audit functions. The unique Production Key feature ensures that only models that have been digitally signed by authorized personnel are used on production operations.

For the modeler, an intuitive graphical interface is provided. This can either be used to create models natively using the in-built support for the  C#  and  R  languages, or integrate any other modeling platform that offers a .NET interface (e.g. Python, MatLab, F#, SAS, etc.).

The modeler is fully integrated with the repository and production servers, making model workflow and deployment to production a "one-click" operation and slashing months from typical deployment cycles.

The modeler accesses the full mathematical power of the R language, the Math.NET library, and allows analysts to create custom function libraries. Excel spreadsheets can also be integrated, and their data read and formulas run from an Excel execution engine embedded within the model server. Other third party tools with .NET interfaces can also be loaded and integrated with any model.

For development and what-if analysis, the modeler supports "sketch" functions which allow approximations of functions to be visually sketched and used until further analysis or empirical data is available.

A challenge unique to commercial lending that distinguishes it from retail lending is that the true credit risk of a borrower often depends not only on attributes of the borrower, but also on the relationships that may exist between the borrower and other entities whose assets may potentially be available to secure the credit facility, or affect the borrower's ability to meet loan obligations under different circumstances. These relationships typically include such things as parent-subsidiary relationships between companies, lines of credit or promissory notes, common directors, joint title to assets/obligations under liabilities, associations with trust funds, etc. Furthermore, these relationships may change with time, not only because associations between entities are made and dissolved as entities are merged, acquired, divested, etc., but also because the valuation of the entire ensemble of related assets may change over time.

CreditRate(TM) includes a powerful credit rating relationships modeler which allows customer-configured grouping models to be tracked against loans, no matter how complex these relationships become. The risk characteristics of the entire group are automatically updated when when an event occurs that impacts any of the group members. As the group structure evolves over time, CreditRate(TM) will maintain the current group configuration, in addition to historical versions of the group as it evolved.

It can easily be initially deployed to integrate with existing systems, using Model Injection(TM) to take over the credit rating functions, and disrupting little else. As the organization travels further down the RFM roadmap, additional RFM modules may be added, building up to the complete RFM Suite(TM), or some subset of it, following a timetable that suits the organization's needs.

Our typical deployment roadmap is shown below.

Proof of Concept Standalone, self-contained system Focus on evaluating functionality Discover and plan model, integration, and business process requirements for later stages Minimal enterprise integration Typically 2- 5 months			Pilot Cloud/on-premise deployment as desired Basic enterprise integration Train pilot users & IT staff Limit to one geography or business unit Develop extract/transform/load (ETL) and QA process for data Analyze production needs and plan/test roll-out and cut-over procedures May continue to run legacy processes in parallel Typically 6 -12 months*			Cut-over and Rollout Develop roll-out plan repeating process developed from pilot over all geographies / business units. Full enterprise integration System configuration and data migration continue from Pilot deployment Typically 1-2 years*			Production and Support Day to day operations support (web support, wiki, help desk, option for developer master services) Upgrades and bug fixes included in maintenance Refresher and upgrade training as requried Customization, extension and integration projects as required. On-going