Close Close
Popular Financial Topics Discover relevant content from across the suite of ALM legal publications From the Industry More content from ThinkAdvisor and select sponsors Investment Advisor Issue Gallery Read digital editions of Investment Advisor Magazine Tax Facts Get clear, current, and reliable answers to pressing tax questions
Luminaries Awards

Practice Management > Building Your Business

Panel Weighs In On When To Dump Administration Systems

Your article was successfully shared with the contacts you provided.

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


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.”

Hersh pointed to what he called an aversion to risk in the insurance industry, an attitude that carries over to information technology (IT). Rather than using IT to gain a competitive advantage, many carriers simply look to IT to enable them to remain competitive, he noted. “IT can be used for competitive advantage, if it’s done properly,” he asserted. The key is knowing which business problems to solve via technology.

Panelist Bill Jenkins, CIO of Penn National Insurance, based in Harrisburg, Pa., disagreed with the idea that older systems could be part of a competitive enterprise, noting that, “Legacy systems won’t allow carriers to remain competitive. There’s no real-time flexibility.

“Legacy systems inhibit the business from introducing new products,” he continued, adding that they also keep carriers from bringing products to market quickly. Hersh noted, however, that if a company can “extend legacy systems to do real-time business, you are okay.”

According to Hersh, when it comes to policy administration systems, servicing producers is the key to “gaining wallet share. You risk losing business by not being up-to-date with core administration systems.” Newer systems, he said, would yield “up-to-the-minute and accurate data, which reduces costs. That is a competitive advantage.”

Another advantage of newer systems is that they are built to upgrade more easily than older systems, which must be “drilled into after the fact,” he said.

Costs to upgrade remain a major hurdle, however. Jenkins pointed to a project in which another carrier replaced 28 legacy systems, which cost between “$35 million and $50 million–and that was 10 years ago.”

“You must spend time up front to figure out how to get everyone off the mainframe,” said Hersh of the systems update process. “Make sure you can get off it first.” This involves a thorough ROI review and cost-benefit analysis, including the cost of converting data, he noted. “This should be the most challenging project you’ve had on the business side. Outsource tasks while you can; don’t waste retraining of your IT staff.”

Both Jenkins and Steward, however, were less enthusiastic about outsourcing core processes. “I want control; I want the source code in my pocket,” said Jenkins.

Hersh maintained that outsourcing “could be helpful to this industry. Yes, you lose some control, but you also lose some of the costs. There is a tremendous unwillingness in the insurance industry to allow anyone else to manage anything for you. We’re seeing some core systems outsourced now.”

“Most CIOs are bringing mission-critical systems back in-house,” Jenkins said. Looking at his own experience with outsourcing, he noted, “I’ve been hurt many times.

“Data quality is the industry is a huge problem,” he continued. “There must be some control over building files and how they use it.”

The panelists agreed that a critical aspect of the success of any upgrade project is commitment of the organization to the project, from the top down. “Senior management must vocally approve it or others will slow down the process,” said Hersh.


© 2024 ALM Global, LLC, All Rights Reserved. Request academic re-use from All other uses, submit a request to [email protected]. For more information visit Asset & Logo Licensing.