News

03:43 PM
Connect Directly
Google+
LinkedIn
Twitter
Facebook
RSS
E-Mail
50%
50%

Q&A: Atlantic Casualty CIO Greg Ricker

Atlantic Casualty CIO Greg Ricker discusses why the E&S carrier implemented Oracle Documaker to improve ease of doing business for its MGA partners.

Goldsboro, N.C.-based excess and surplus lines insurer Atlantic Casualty distributes its products through 100 managing general agencies. The company was looking to make it easier for those partners to do business, keep costs down and reduce the risk of errors in document and policy preparation. So, the company migrated all of its wholesalers to Web-based issuance using Oracle Documaker. The insurer also enabled MGAs to populate Web-based forms with data from their own agency’s systems, without rekeying data, helping cut total policy creation time by 75% and reduced the critical error ratio to less than 3% for policy documents. We caught up with CIO Greg Ricker to discuss the process.

Insurance & Technology: What was the business problem you were trying to solve by implementing Documaker?

Greg Ricker: The systems we had in place weren't well connected. The integration wasn't seamless and required the user community to make a pretty significant investment in keeping forms and libraries current with the most recent carriers rules and forms. The process needed to be changed, and it had to happen quickly.

I&T: What were some of the brokers' major complaints with the previous system?

GR: Our customers had complaints in three major areas. First, there was the cost of maintaining forms and libraries. If an update failed, there was additional support required to resolve those errors. Second, the forms updates were coming at a very quick pace. No sooner than one update was completed and another one was ready to be applied. This frustrated the user community. Third, the policy issuance process wasn't seamlessly integrated with rating. So there was a lot of duplication of effort. This duplication led to more errors, which drove up expenses.

I&T: What were some of the procedures you had to change in order to implement this web-based system?

GR: The process we used to update and distribute forms to our wholesalers had to be completely re-engineered. Going from a distributed system to a web-based required an entirely new process. Some of our edits we had in the old forms library had to be rewritten. Most importantly, we had to implement the use of web services to push rating data into policy issuance. Having forms pre-populated with data was the key element to reducing steps and the potential for issuance errors. And with a web-based system, there was no longer a need to have our customers upload data. Once a policy was issued - our company system had the data immediately.

I&T: How vocal is your agent/broker population in demanding new technological capabilities? Who is responsible for staying in contact with them and managing that relationship?

GR: The wholesale community has been under extreme expense pressure since about 2007. With pricing and risk exposures going down for several year in a row, this directly impacts agency commissions. The challenge now became how can expense levels be reduced without sacrificing customer service. The wholesalers weren't shy in asking for more efficient ways to do business. We not only met their challenge, but we did it quickly and our solution exceeded their expectations. As a result - the amount of business we write with them has increased. In terms of the relationships we have with our wholesalers, we really work hard to stay in touch with not only the front line underwriters and customer service reps, but also with their IT and management teams. By listening through the various levels within the organization, we get a good handle on the needs throughout the company.

I&T: Because you're an E&S carrier, were there any unique issues that came up in trying to implement policy automation?

GR: In the E&S space there are a number of different systems in use. From rating, to portals, agency management systems, policy issuance systems, and data interface solutions. In addition, there isn't a formally adopted data standard for which data is easily passed from one system to another. So there have been a number of custom interfaces built over the years. In our project we weren't looking to develop another set of standards or build another system. Our goal was to leverage as much as possible from the systems already implemented. We also decided we would open our systems to allow for a greater level of transparency into our solution. We are no longer required to be involved in all the interface efforts. Our customers can now see deeper into the functionality and look for creative ways to improve their internal efficiencies. We've very pleased with how our customers have responded to this.

Nathan Golia is senior editor of Insurance & Technology. He joined the publication in 2010 as associate editor and covers all aspects of the nexus between insurance and information technology, including mobility, distribution, core systems, customer interaction, and risk ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Janice, I think I've got a message from the code father!
Current Issue
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.

Dark Reading Radio
Archived Dark Reading Radio
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.