Ventiv Technology

Risk Management Software Deployment Your Guidebook to Success 18 Aon eSolutions share this guide Understanding workflows Understanding workflows We often find it works well to understand the organization's current workflows. We focus on what their pain points are today, and then look at what's not working. Once we have a good understanding of the workflows, we discuss where they see the RMIS in the next two years, three years–even five years. Are there other modules or capabilities they'll need, or other critical data they'd like to capture? We realize that these are longer term, even visionary questions, particularly for a first- time RMIS client. But even having a basic wish list of how the RMIS could support them gives us a jump start on deploying the new system. Beyond manual spreadsheets Many times, we see first-time clients who are migrating to a RMIS from using an Excel spreadsheet method of data capture. The risk manager is looking for a RMIS to bring in spreadsheets submitted from the field, updating property values, and producing 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 statement 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. Keep within a manageable scale, then expand 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 a 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.

• Cover