When Should You Change Systems?
One of the most challenging technology issues that a risk or
claims manager faces is when to change systems. Changing
systems can be fraught with many issues ranging from learning
new software routines, altering integration points, changing
workflows, and getting used to a new vendor service team.
94
©2022 Redhand Advisors. All rights reserved.
As independent consultants, we advise
our clients to carefully evaluate if their
problems with the system and vendor
cannot be repaired with an updated
business review. Certain conditions may
require such a move.
Reasons why
a change may be warranted:
1. Your organization has outgrown
the vendor and system.
A good example would be that
your company has acquired a new
business with different exposures,
such as a self-administered worker's
compensation claims unit. Your
current RMIS provider cannot handle
this issue; therefore, you need more
powerful features. The organization
has grown so significant to it requires
a lot more service hours than the
resources of your current vendor can
provide.
2. The system has old technology.
A frequent problem that we have
these days is clients with systems
utilizing outdated technology. Either
they are older legacy-based systems
or home-grown ones that were
developed in the 1990s or early
2000s.
