Yes, it is supported via online model updates, where an automatic, highly flexible mapping to new or changed models ensures version compatibility. The mapping relates to GUI, database and business logic.
RFW license policy enables customers to pay only for modules they really need. There is the option to get a test license that enables free access to all RFW modules for a limited period of time to test their usability.
It means that various institutional sub-units, e.g. bank branches, business centers, departments, etc. are physically represented in one database, but work in separate, access-protected logic areas within the same database. All sub-units can have different local settings and can access other sub-units through corresponding hierarchy rights.
Rights and roles that are assigned to users enable the realisation of a multi-step workflow. For example, a simple approach can be: User A creates and modifies a session of a loss event in the operational risk module for the first time. He / she then enters additional data and calculates the losses. User B confirms the latest session state of User A and the session freezes. It can not be changed any longer, only new versions can be created. The business logic, however, accepts the session at this point as being in its final state and thus obtains data and results.
Processor cores are used for parallel calculations of sessions, e.g. for parallel calculations of portfolios, as well as during Monte Carlo simulations, where the simulation runs are distributed on processor cores. The actual speed-up depends on each test case. Many tests show performance speed-ups from 3 to 3.5 times, at real 4-core processor. An additional speed-up factor of 1.5 to 2 can be obtained, if using a 64-bit processor.