Ventiv Technology

RISK MANAGEMENT SOFTWARE DEPLOYMENT: YOUR GUIDEBOOK TO SUCCESS 21 It's best not to make an initial implementation too large. Instead, start with an implementation — and the scope of the RMIS — within a scale that's comfortable to work with. There's nothing wrong with a phased implementation, especially for a client who is implementing an RMIS for the first time. The ideal scenario is to roll it out to a scale they can support. But we also don't want clients hampered by a system that can't go beyond the deliverables in the initial implementation. So, we encourage thinking a couple of years out about what they're expecting their RMIS system to provide and how that will impact the effectiveness of their risk management operations. KEEP WITHIN A MANAGEABLE SCALE, THEN EXPAND Many times, we see first-time clients who are migrating to an RMIS from using an Excel spreadsheet method of data capture. The risk manager is looking for an RMIS to bring in spreadsheets submitted from the field, update property values and produce a statement of values on an annual basis. Their initial implementation meets the goal: It enables them to pull in basic data quickly and provide some basic reporting. But frequently the next step is to have the field-level staff logging on to the RMIS, updating their information in the system and allowing the risk manager to review and make sure the numbers make sense. Here, the client is moving away from a very labor-intensive process of pulling together multiple spreadsheets or statements of values and consolidating them into one that can produce actionable reports. By taking a forward-looking approach, we can deploy the implementation by understanding what fields users will update regularly, and what approval process needs to be put in place. BEYOND MANUAL SPREADSHEETS

• Cover