L25IASAlegacy, Life week 25 tech–Slug–go page xx, with –126 lines plus suggested art: a dump truck dumping old computers onto a garbage heap
Banner:
Flag: IASA Meeting Coverage
How long should carriers keep legacy systems?
Anaheim, Calif.
Call them outdated, slow and limited, but legacy administration systems continue to be used by insurers despite calls for updates that some feel would allow more product development and marketing flexibility.
The question of how long to hold on to such systems was the central focus of a panel discussion entitled "Pulling the Trigger: Knowing When to Change Core Administration Systems" presented during the annual conference of the Insurance Accounting & Systems Association (IASA) held here earlier this month.
Chris Steward, CIO of Arabella Insurance Group, based in Quincy, Mass., said that approximately 10 years ago, his company had spent "millions" in an effort to update its policy systems, but the project "went badly wrong." Despite that failure, however, the company is about to give it a second try.
"We can't afford not to do it," Steward said. "It's a money decision; the process is not cheap."
The company considered "bolting" other products onto its legacy applications to get desired improvements, he said, "but that would have been much more expensive. We've added some bolt-on technology, but that's all really window dressing. We had no choice but to replace it."
He added that the systems in question are batch-driven and date back to the late 1970s. "To make it a true, Web-based real-time system, we must re-craft six or seven different systems," he explained.
According to panel member Chad Hersh, senior analyst with New York-based Celent Communications, however, "in some cases, legacy systems are doing the job."