Contact Us
Help Desk

Post: Catlin Insurance Group Improves BI Management & Control with MotioCI

MotioCI Manages Catlin’s Growing Cognos Implementation

BI in the Insurance Industry

Catlin Group Limited, which was acquired by XL Group in May 2015, is a global specialty and casualty insurer and re-insurer, writing over 30 lines of business. Catlin has six underwriting hubs located in the UK, Bermuda, the United States, Asia Pacific, Europe and Canada. Catlin has a worldwide team consisting of over 2,400 underwriters, actuaries, claims specialists, and support staff. The insurance industry centers on managing risk. Insurers are tasked with identifying and quantifying the “what ifs” associated with human and natural disasters and then making sound business decisions based on these many variables. The goal of insurers is not to eliminate risk, but to understand it and manage it effectively. The insurance industry deals with volumes of data from many different sources in order to make timely decisions, provide superior service to its clientele, and to stay competitive. In 2013 Catlin made the decision to overhaul its existing Management Information Systems implementation, which included Business Objects, and move to a more comprehensive platform with additional capabilities and transparency into their business. Catlin chose IBM Cognos.

Obstacles in BI Growth

The move to Cognos increased the capabilities of Catlin’s BI environment significantly, which allowed Catlin to better meet the demands of claims teams and business users. As with any industry, the business side wants and needs information fast, but IT needs to ensure what they deliver is accurate and reliable. In a highly regulated industry such as insurance, these standards cannot be compromised. Catlin’s BI team is geographically spread across the UK, India, and the United States. The development and testing work at Catlin is shared and dispersed among these three locations. The expanded size and scope of the new BI environment at Catlin, as well as increases in user adoption began to surface issues relating to the BI team’s ability to manage the implementation and still provide timely information across the organization. These issues began to negatively impact development, release time, and the ability to quickly transition new or updated BI content to production. Catlin recognized the need to implement more control over its disparate teams and to address the following life cycle management requirements:

  • Control of BI assets and change/dev management
  • Managed method of promoting content between environments
  • Quality control over development work – ensuring accuracy, reliability, and consistency
  • Ability to accurately predict performance and measure the impact of new development

Manual to Streamlined BI Promotions

One process at Catlin that had to be immediately addressed was the way in which BI content was promoted into new environments. Prior to MotioCI, only two people in the entire organization were authorized to promote BI content from development to testing (QA) and to production environments. This approach resulted in a significant bottleneck in getting new or updated BI content into the hands of end users in a timely fashion. Catlin’s stalled deployment issues were solved almost immediately through the self-service promotion and version control features of MotioCI. With version control enabled, every BI asset that gets promoted at Catlin can be traced back to who promoted it, when it was promoted, and what version was promoted. Version control and release management together have empowered more Cognos users at Catlin with the responsibility of ad-hoc and release-based deployments while still maintaining governance and control over the entire BI implementation.

Safeguard Accuracy with Testing & Version Control

In the insurance industry, data manipulation is common among end users such as actuaries, for the purpose of analyzing the impact of claims payouts. Confidence in accuracy is imperative for end users relying on the assets delivered by the BI team. Before MotioCI, the amount of time required to implement quality assurance checks on BI content developed oshore began impacting Catlin’s ability to develop, test, and release new BI content in an agile fashion. Catlin has implemented MotioCI testing to automate and control the quality of the development work, which has substantially reduced time spent on this task. Testing greatly reduces the amount of reports with errors that get delivered to end users, which in turn diminishes the time spent on support issues and improves the business user experience. Both the BI team and end users at Catlin can confidently access BI assets in their day-to-day, knowing the information they’re working with has been tested for accuracy but can safely be reverted back to previous versions without hesitation.

The Results Delivered by MotioCI

In the first year of implementing MotioCI, Catlin has benefitted from the following as a result of the version control, release management, and automated testing features:

  • A clear-cut way to manage the dispersed BI teams and environments
  • Reduced development time
  • Increased amount of BI assets deployed to production
  • Greater confidence in the accuracy of BI content
  • Improved satisfaction among the end users

Catlin turned to MotioCI to manage their Cognos implementation. Their deployment issues were solved almost immediately. They replaced their manual method of content promotions with MotioCI’s self-service promotion capabilities. The combination of version control, release management, and testing capabilities that MotioCI provided, helped Catlin achieve results in these areas:

  • Improved management of BI teams and environments
  • Reduced development time
  • Increased the amount of BI assets released to production
  • Boosted confidence in BI content accuracy
  • Raised end user satisfaction
Ready to streamline and automate your BI & analytics platforms?
Get A Demo
Solutions
Services
Products
About Us
Resources
Contact
  • Tel:1 (972) 447-9595
  • Toll Free:1 (833) 855-3073
Follow Us
Youtube Linkedin Twitter
© 2024 Motio. All rights reserved
Scroll to Top
As the BI space evolves, organizations must take into account the bottom line of amassing analytics assets.
The more assets you have, the greater the cost to your business. There are the hard costs of keeping redundant assets, i.e., cloud or server capacity. Accumulating multiple versions of the same visualization not only takes up space, but BI vendors are moving to capacity pricing. Companies now pay more if you have more dashboards, apps, and reports. Earlier, we spoke about dependencies. Keeping redundant assets increases the number of dependencies and therefore the complexity. This comes with a price tag.
The implications of asset failures differ, and the business’s repercussions can be minimal or drastic.
Different industries have distinct regulatory requirements to meet. The impact may be minimal if a report for an end-of-year close has a mislabeled column that the sales or marketing department uses, On the other hand, if a healthcare or financial report does not meet the needs of a HIPPA or SOX compliance report, the company and its C-level suite may face severe penalties and reputational damage. Another example is a report that is shared externally. During an update of the report specs, the low-level security was incorrectly applied, which caused people to have access to personal information.
The complexity of assets influences their likelihood of encountering issues.
The last thing a business wants is for a report or app to fail at a crucial moment. If you know the report is complex and has a lot of dependencies, then the probability of failure caused by IT changes is high. That means a change request should be taken into account. Dependency graphs become important. If it is a straightforward sales report that tells notes by salesperson by account, any changes made do not have the same impact on the report, even if it fails. BI operations should treat these reports differently during change.
Not all reports and dashboards fail the same; some reports may lag, definitions might change, or data accuracy and relevance could wane. Understanding these variations aids in better risk anticipation.

Marketing uses several reports for its campaigns – standard analytic assets often delivered through marketing tools. Finance has very complex reports converted from Excel to BI tools while incorporating different consolidation rules. The marketing reports have a different failure mode than the financial reports. They, therefore, need to be managed differently.

It’s time for the company’s monthly business review. The marketing department proceeds to report on leads acquired per salesperson. Unfortunately, half the team has left the organization, and the data fails to load accurately. While this is an inconvenience for the marketing group, it isn’t detrimental to the business. However, a failure in financial reporting for a human resource consulting firm with 1000s contractors that contains critical and complex calculations about sickness, fees, hours, etc, has major implications and needs to be managed differently.

Acknowledging that assets transition through distinct phases allows for effective management decisions at each stage. As new visualizations are released, the information leads to broad use and adoption.
Think back to the start of the pandemic. COVID dashboards were quickly put together and released to the business, showing pertinent information: how the virus spreads, demographics affected the business and risks, etc. At the time, it was relevant and served its purpose. As we moved past the pandemic, COVID-specific information became obsolete, and reporting is integrated into regular HR reporting.
Reports and dashboards are crafted to deliver valuable insights for stakeholders. Over time, though, the worth of assets changes.
When a company opens its first store in a certain area, there are many elements it needs to understand – other stores in the area, traffic patterns, pricing of products, what products to sell, etc. Once the store is operational for some time, specifics are not as important, and it can adopt the standard reporting. The tailor-made analytic assets become irrelevant and no longer add value to the store manager.