Making the Marriage Work
Insurance Networking News, January 2007
Reality: Two years later, implementation continues to slog at a snail's pace, the systems won't talk, your team is overworked, the vendor has been bought by a behemoth that has lost you in the shuffle, and your boss, users and other stakeholders are screaming. You are stuck.
Advertisement
"Even determining your basic requirements takes a disciplined approach," says George Grieve, president of CastleBay Consulting, Austin, Texas. Grieve tells his insurance clients to establish cross-functional teams that can share the "buy-in" to feature/functionality requirements.
Using a policy administration replacement project as the example, Grieve recommends combining personnel from technology, product development, policy services, underwriting, and others with a vested interest in the project, such as the business side. "The first thing to do is have everyone have an honest conversation," Grieve says.
START INTERNALLY
Indeed, long before discussions begin with the technology provider, many insurers make the establishment of good partnerships with internal clients the priority.
"We start with informal conversations and, from that, articulate requirements into a project statement," notes Bill Garvey, an IT director for The Main Street America Group, Jacksonville, Fla. Garvey's team takes the project statement and builds in higher-level requirements, which specify why the technology is needed and how it will potentially benefit any one particular area. Once the project is approved, the team goes into fuller planning mode.
Garvey typically establishes a task force that includes representatives from the business side, IT project management, systems engineering, quality assurance and oftentimes security.
"We talk to everyone involved and ask all the questions: 'What exactly do we need?' 'How long will programming take?' 'What is the labor allocation?' They all have input to the scope and timeline. Then we take it to a more task-oriented vendor selection approach."
International Catastrophe Insurance Managers LLC (ICAT), a North American catastrophe insurance brokerage based in Boulder, Colo., investigates technology suppliers only when a specific business requirement has been identified. The growing, $140-million company, which provides catastrophe insurance to more than 60,000 buildings in 36 states, has identified several business requirements over the past couple of years, chief among them the need to replace its existing third-party claims administrator (TPA) with its own TPA, Boulder Claims. ICAT and Boulder set its sights on San Mateo, Calif.-based Guidewire Software's ClaimCenter. The three-month project included integration to ICAT's policy administration system and to Oracle Financials.
VERIFY BUSINESS REQUIREMENTS
"The business requirements can come from a business unit or from IT," says Joan Zerkovich, ICAT senior vice president, information technology. "As part of the budget process, we present the proposal to investigate the technology to our strategic leadership team, and from there create a set of functional and technical requirements for evaluation."
The technical team assesses the alignment of the application with ICAT's architectural framework, data warehouse and document management environments. The business team assesses functionality. The workgroups are then given a short timeline to narrow down the field to two to three supplier options through online materials, telephone conferences and online meetings with the vendors. Vendors that delay in providing information or demonstrating functionality are eliminated because they don't meet ICAT's responsiveness and partnership criteria.
Timelines-from identification of a vendor through proof of concept-typically require two to three months. Like Main Street America Group, once both business requirements and vendor selection is identified, ICAT believes in working closely with its internal teams to help the vendor "get it done."
Most recently, ICAT tested its process with the U.K.-based Thunderhead Ltd. ICAT will use Thunderhead's platform to power multi-channel generation of its insurance policies, policy endorsements and cancellation notices. ICAT will initially deploy Thunderhead's document generation platform to scale its insurance operations to enable high-volume production and delivery of its business communications across multiple channels, including print, Web and PDF.
For more information on related topics, visit the following channels:
- Enterprise Technologies
- Insurance Network
- Outsourcing
- Policy Administration
- Technology & IT Management
