Ventiv Technology

Risk Management Software Deployment Your Guidebook to Success 10 Aon eSolutions share this guide So, how to start? As our team launches an implementation, we often find the client has some type of hierarchy in place. They may have an existing RMIS. They may be receiving data from one or more third-party administrator, each of whom has its own format. The client may have an in-house system. Or there may be a combination of all of the above. Even a loosely structured hierarchy is a starting point for discussing and mapping out a new structure. At this early stage we urge clients to understand how valuable it is to have all parties using the same structure. To that end, the RMIS structure should: Work for third-party administrators handling the organization's claims. Align with the organizational structure from, for example, an SAP or an Oracle system. Enable the risk management team to produce reports in line with how top management wants to see its data. To steer clients in their hierarchy decisions, we often provide them with generic examples of structures that similar organizations have in place and prepare examples using the client's own data. Chance for a fresh start Whether a client is implementing a RMIS for the first time or moving from an existing system, the setup of the organizational hierarchy offers a good checkpoint. The setup process is an opportunity to review: existing workflows, levels of user security, types and formats of reports and access, and processes and practices. Clients who have prior systems can look at what they have and confirm that it's the structure they want going forward. This may be a juncture to improve on that structure so that they're able to create reports that are the same across the board. They can consider introducing best practices at this point. They may want to modify business workflows to gain efficiencies, to improve reporting or to redefine levels of users that better reflect security needs. With the guidance of the RMIS provider, clients can validate that this is still the best way to structure these elements to manage the risk management side of their business. We remind clients: You've bought new risk management software for a reason. Take this opportunity to address the areas that were disjointed or weren't working well; then modify the system's structures to remedy them.

• Cover