Blog

Introducing SOA's Latest Role Models

Joe McKendrick
Insurance Experts' Forum, January 12, 2010

The insurance industry's work with SOA (service oriented architecture) dominated a new report published by ComputerWorld's John Webster. Webster cites two insurance company implementations as examples of SOA reaching a new stage of maturity – moving past the coding and bits and bytes and being applied to address real business problems.

Massachusetts Mutual Life Insurance Co. maintains a service oriented architecture with about 40 services, including distribution management, premium collections, customer information management, new business and underwriting. "These services integrate applications across business units, each of which markets different products. Instead of replacing an existing application wholesale, business units select an appropriate combination from the company's array of shared services," Kinam-Peter Kim, manager of enterprise SOA at MassMutual, is quoted as saying.

Cigna Corp. has been working with SOA approaches for about a decade, and eventually applied it to enterprise-wide systems such as call centers and customer relationship management software. Services and data are shared and reused between business units. "We built out the existing hardware and software infrastructure, and now there are pieces of SOA in nearly every mission-critical application," according to Stephen Bergeron, senior director of architecture at Cigna.

The common denominator for both MassMutual and Cigna is that their SOA infrastructures are designed from a business perspective, and not for technical optimization – though that may have been a benefit as well. And, just as importantly, the SOAs reach across all business units, and are intended as a joint effort that stretches across departmental walls and silos.

There's been a lot of debate across the information technology space as to whether service reuse should be a goal of SOA, and whether it even pays off for companies. For these two insurance company, there was no question that reuse resulted in business value – and they clearly are reaping the competitive advantage these more flexible services provide. I like the way MassMutual's Don Carten described the ultimate goal of his company's SOA effort: "To us, SOA is not a technology. It is an approach to modernize our business -- an approach to create an adaptable enterprise."

Joe McKendrick is an author, consultant, blogger and frequent INN contributor specializing in information technology.

Readers are encouraged to respond to Joe using the “Add Your Comments” box below. He can also be reached at joe@mckendrickresearch.com.

The opinions of bloggers on www.insurancenetworking.com do not necessarily reflect those of Insurance Networking News.

 

 

 

Comments (0)

Be the first to comment on this post using the section below.

Add Your Comments...

Already Registered?

If you have already registered to Insurance Networking News, please use the form below to login. When completed you will immeditely be directed to post a comment.

Forgot your password?

Not Registered?

You must be registered to post a comment. Click here to register.

Blog Archive

The Other Auto Insurance Telematics Shoe Drops

Progressive's decision to charge Snapshot drivers more if their driving data indicates higher risk has started the industry down a road of data-driven adverse selection.

Core Transformation – Configuring in the Rain

The whole point of core transformation is that changes at the micro level can be used as a stimulus for changes at the macro level.

6 Ways to Develop a Productive IT-Business Dialog

Relationship management 101 for keeping IT and business on the same page.

Unified Digital Strategy: Succeeding in the Digital Revolution

A unified digital strategy recognizes that all business strategies and technologies touch the customer in some way and that a one-size-fits-all channel model is obsolete.

Agile and Continuous Delivery in a Regulated Environment

Just because a development team is doing continuous delivery or packaging releases into two-week sprints doesn’t mean that code is being moved to production.

Dealing with the COBOL Brain Drain

Documentation on aging systems often is akin to tribal knowledge, and the potential for things to go bump in the night increases as these environments face generational transition.