Insurers Keep Software Current with Continuous Delivery Updates
“This process has put our company in a very advantageous position.”
Linda Squires
Senior Executive
North Carolina Farm Bureau Insurance
“Instead of a waterfall delivering huge amounts of code all at once, we’re providing a steady stream of updates.”
Sloan Plumer
Chief Technology Officer, Property and Casualty Insurance Division
CSC
GET MORE INFORMATION
For more information about CSC’s Continuous Delivery program, contact us by phone or email. Only CSC will use the information you provide.
Insurance companies face a continuing battle trying to keep enterprise software up to date. Companies can either upgrade to the latest release every year or so, which can pose a long and risky project to the IT staff, or they can do nothing and risk falling behind on system security, regulatory compliance and usability enhancements.
For most insurers, software release upgrades are highly visible projects with many touch points. A relatively straightforward upgrade can impact multiple lines of business and numerous downstream systems.
“The longer a company waits to upgrade their software, the more complex and challenging the upgrade can become,” said Sloan Plumer, chief technology officer for CSC’s Property and Casualty Insurance Division. “Unfortunately, too many insurers fall so far behind that the prospect of ever becoming current is out of reach. Essentially, the code is so outdated and heavily modified that it becomes obsolete.”
Agile Approach to Upgrades
A growing number of insurers working with CSC have found a way to turn the traditional upgrade process on its head. These companies are receiving continuous updates as they become available rather than waiting for the next annual release, which typically funnels hundreds of requests and requirements into one large delivery.
“The Continuous Delivery approach is based on proven, agile software development methods,” Plumer said. “We’re taking it to large-scale insurance applications that had a very different development model. Instead of a waterfall delivering huge amounts of code all at once, we’re providing a steady stream of updates.”
With most companies running heavily modified versions of the same software, vendors must typically develop many unique versions of the same release simultaneously. Each customer then initiates a complicated implementation project to work hundreds of system enhancements into its unique base code. These customizations prevent across-the-board installation of software upgrades.
But software has changed. Most business rules are externalized and completely configurable, rendering the majority of customized code modifications unnecessary.
“There are variances, of course, but the elements to compose an insurance process are becoming fairly universal,” Plumer explained. “If one insurer needs to change a system, we’ve found that other organizations on the same system will benefit from that change also. We incorporate those types of modifications into one version of the base code that benefits all of the users.”
If additional modifications are necessary, there are new ways to attach them outside of the base code, which remains consistent across all installations and easier to update.
More than 200 insurers routinely submit software enhancements as part of the Innovation Community program at CSC. With CSC assuring quality and maintaining the code in the base system, these companies no longer need to manage complex coding modifications in-house.
Up and Running, Up-to-Date
Continuous Delivery is also a key strategy in the implementation of new software. CSC clients receive continuous updates throughout the conversion process, keeping them current with the latest features and enhancements during the rollout.
One of the contributors to and early adopters of the Continuous Delivery process is North Carolina Farm Bureau (NCFB) Mutual Insurance Company. NCFB recently transitioned to Exceed C.0, the base version for Continuous Delivery. To support this transition, the company has been actively involved in the Innovation Community program, through which it has sponsored nearly 35 enhancement projects to date.
NCFB also has taken advantage of enhancements that originated with other insurers’ projects. For example, Tennessee Farmers Insurance, a carrier in a neighboring state using Exceed, introduced several claims enhancements of which some were subsequently leveraged at NCFB.
“We’ve got a really great team on the CSC side, and they keep us in the loop with what’s coming down the pipeline and what other companies are doing that we might be interested in,” said Pam Hiovich, Operations Division Manager for North Carolina Farm Bureau Insurance.
According to Linda Squires, NCFB senior executive, “We have been incorporating Continuous Delivery releases, so we are in a very good position to leverage the newest functionality immediately. This process has put our company in a very advantageous position.”
