How a Full-Service Insurance Claims Administrator, Migrated Legacy Reporting and Lowered Their Total Cost of Ownership

Executive Summary

Anchor Risk and Claims Management is a full-service insurance claims administrator in Texas. They provide claims administration for workers' compensation, occupational injury, and commercial auto markets. Their third-party administration services have been recognized among the best in the industry. Anchor has an in-house team that oversees network administration, software development, and other IT objectives.

We spoke with Anchor Risk about their recent decision to migrate their legacy reporting system (Crystal Reports) to Wyn Enterprise. We wanted to understand Anchor Risk Management, what they do, and how Wyn Enterprises helps them.

We discussed their reasoning for making the switch, the process of implementing Wyn, how they're using it, and the benefits they're seeing.

According to Anchor Risk's IT staff, main requirements were:

  • Needed to be cost-effective
  • Responsive support team
  • Ease of use and easy migration

The Challenge: The Need to Modernize Reports

Wyn Enterprise (Wyn):

What spurred the decision to switch to Wyn Enterprise?

Anchor Risk and Claims Management (ARM):

We had aging reporting software and were trying to get Wyn to serve our purposes. That's why we initiated the request for a search for a reporting solution.

Wyn:

You're migrating from your internal legacy systems and now have all your reporting on Wyn. When you were looking at solutions, you mentioned ActiveReports. Did you look at any other companies for professional out-of-the-box report solutions?

ARM:

Our legacy system was Crystal Reports. We started out with Crystal Reports 5 or 6, which was about 25 years ago. Then, they ramped up the owner licensing fees. So that was it for us.

Then we looked at several other reporting products. We looked at a couple of Java solutions. There wasn't anything out there big enough to absorb all that we were doing. And when we say absorb, we're talking about making API calls directly into the product, the ability to schedule and drive the ending report format and distribution.

Wyn:

What was the difference in the other products that you were evaluating?

ARM:

At the time we were evaluating, Wyn seemed like it handled everything that we were looking for. The main problem we were trying to solve was what we could get here to work with our system. Also, we needed a cost-effective solution.


The fact that Wyn (formerly ActiveReports Server) has been around for well over 20 years, we knew they were already established and offered great support. That was another big thing.

Low TCO (was cost-effective for us), the support, ease of use, availability of the product, and how quickly we could get up and running with it. These were the primary consideration factors when we were shopping for a BI solution.

[SECTION-BACKGROUND-GREY]

Outstanding Support

Wyn:

With the support, how long did it take you to get it up and running?

ARM:

We were up and running in eight to ten weeks. There were a couple of tech issues configuring reports. The Wyn Support Team plugged in a couple of hotfixes for us. The turnaround time was pretty quick. Usually, within the same day, support responded to assist.

Wyn:

I'm glad that you were able to experience that during installation. Once you install it, then that's where it really kicks in on the support side.

ARM:

One of the biggest things, and it is a testament to the Wyn Support Team's knowledge, helped us understand the API calls to Wyn reports. That's probably the most substantial piece we were trying to leverage. How can we do this stuff automatically? So, the time to market reference was basically how do we get it plugged in. And because we had several large clients who wanted specific reports that we already had in Crystal, our legacy product was difficult.

[/SECTION-BACKGROUND-GREY]

Learn how to modernize your data visualization with our new guide.
Read More

[SECTION-BACKGROUND-GREY]

Quick to Market

Wyn's implementation saved us about half a million dollars.

Wyn:

Wyn was up and running within 90 days. If you were to build that internally, what do you think the time difference would have been? Was there a cost-saving?

ARM:

If we tried to build our own product like Wyn, it would probably take one to two years. If we're talking about designing our own report builder, that's maybe two years' worth of work. Wyn's implementation saved us about half a million dollars.

We can develop pretty fast, but we don't want to be in the report building business, which is why we didn't even consider it.

When we initially got Wyn up and running, there were two needs. Number one is we wanted to have to replace our legacy reports so our clients could run their own reports. They were calling us saying hey, "can you run this report for me?"zx We were going through and pulling CSV files into an Excel template then sending it out manually.

Wyn:

Clients (the end-users) can make their own reports. That saves you the time of pulling it, modifying it, updating it, and sending it out?

ARM:

Yes. End-users can run their own reports, but they don't necessarily create them. We control their access. We give them parameter values like dates or dollar amounts—things of that nature.

[/SECTION-BACKGROUND-GREY]

A Lower Total Cost of Ownership

Wyn:

Under your legacy system, if you exposed the ability to run reports to your customer base, would you have to license each of them to do that? Is that where the expense came in?

ARM:

Yes. We had to buy concurrent access licensing slots to make that happen. You could buy, I think, five, ten or fifteen at a time. The cost of even five was astronomical for us (as a small company).

The other thing we considered was it would be cost-effective if we made our clients happy. When you start exposing those reports, you will need to have more than five users on the system at a time (especially during closeout periods), so clients would be waiting for a license to become available.

[SECTION-BACKGROUND-GREY]

Easy Adoption and Ease of Use

I'd say to other insurance companies that implementation and report designing cannot get any easier than Wyn Reports.

ARM:

The drag-and-drop, web-based type reporting with tables make it easy to use.

Wyn:

How are you using Wyn on a day to day basis?

ARM:

Our primary focus is on tailoring reports based on the client. We have a lot of reports that we generate directly from the PDF, like financial reports with tabular information and exporting directly into Excel. Many times, clients only want a spreadsheet that looks good. It saves us time from not having to format CSV files.

Wyn:

What kind of reports are you using?

ARM:

We need to distribute professional-looking reports with our unique branded style (logos, color palates, etc.). Wyn offered this white-labeling capability right out of the box. We set up a template with detailed information, and if we need data visualization and graphs included, no problem. The reporting mechanism provides detailed information with graphs and charts, depending on our needs.

Wyn:

What do you say to other claim risk professionals when you're talking about Wyn?

ARM:

I'd say to other insurance companies that implementation and report designing cannot get any easier than WynReports.

We appreciate the support team. They were vital to our success. We appreciate your partnership!

[/SECTION-BACKGROUND-GREY]

Gartner Peer Insights reviews constitute the subjective opinions of individual end users based on their own experiences and do not represent the views of Gartner or its affiliates.