Mulesoft Case Studies PacificComp ensures future-proof business transition with integration

Edit This Case Study Record

	PacificComp ensures future-proof business transition with integration Mulesoft

PacificComp ensures future-proof business transition with integration

Mulesoft

Technology Category	Platform as a Service (PaaS) - Connectivity Platforms Application Infrastructure & Middleware - Data Exchange & Integration
Applicable Functions	Sales & Marketing Business Operation
Use Cases	Process Control & Optimization Supply Chain Visibility
Services	System Integration Software Design & Engineering Services
Challenge	In 2010, Pacific Compensation Insurance Company (PacificComp) decided to change its business model from direct sales to utilizing insurance brokers. This significant shift required a major systems overhaul and posed substantial integration challenges. The company needed to integrate their policy management, billing management, and other systems to support its new business initiatives. The overall goal of PacificComp's business initiatives was to decrease costs and increase ease of use for both underwriters and their broker partners. This became the mandate for the architecture PacificComp's technical team was tasked to build. As much as possible PacificComp chose to invest in software as a service (SaaS) applications as these allowed the company to increase and decrease its usage as the market dictated. However, they also had several existing systems so it was necessary to integrate both current and new systems, whether cloud or on-premise. Read More
About Customer	Pacific Compensation Insurance Company (PacificComp) is a California-based insurance company that specializes in workers' compensation insurance. In 2010, the company decided to fundamentally change its business model from direct sales to utilizing insurance brokers. This strategic shift was in response to the demands of an increasingly competitive workers' compensation insurance marketplace in California. The company believed that partnering with insurance brokers would provide more and better opportunities for California's employers. However, this transition required a major systems overhaul and posed substantial integration challenges. PacificComp chose to invest in software as a service (SaaS) applications to increase and decrease its usage as the market dictated. However, they also had several existing systems, so it was necessary to integrate both current and new systems, whether cloud or on-premise. Read More
Solution	PacificComp chose Anypoint Platform to integrate their policy management, billing management, and other systems to support its business initiatives. The company hired Erich Leipold (evolsolutions LLC) as a contract architect to select an integration platform. They decided utilizing an enterprise service bus was the right architecture for their needs. From an architectural perspective, Pacific Comp used substantial numbers of SaaS applications. They decided the best architecture for their needs actually involved two Mule instances: a public and private instance. This provided appropriate security models for both external and internal Mule 'users'. Using Anypoint Platform, PacificComp began implementing the most critical and time-sensitive use cases required for their 2010 re-launch. First amongst these was integration between DCo, a policy management application for the AS/400 platform that managed all PacificComp policies, and STG billing, a billing application offered by MajescoMastek. Read More Log in to view content
Contents

Technology Category

Platform as a Service (PaaS) - Connectivity Platforms

Application Infrastructure & Middleware - Data Exchange & Integration

Applicable Functions

Sales & Marketing

Business Operation

Use Cases

Process Control & Optimization

Supply Chain Visibility

Services

System Integration

Software Design & Engineering Services

Challenge

In 2010, Pacific Compensation Insurance Company (PacificComp) decided to change its business model from direct sales to utilizing insurance brokers. This significant shift required a major systems overhaul and posed substantial integration challenges. The company needed to integrate their policy management, billing management, and other systems to support its new business initiatives. The overall goal of PacificComp's business initiatives was to decrease costs and increase ease of use for both underwriters and their broker partners. This became the mandate for the architecture PacificComp's technical team was tasked to build. As much as possible PacificComp chose to invest in software as a service (SaaS) applications as these allowed the company to increase and decrease its usage as the market dictated. However, they also had several existing systems so it was necessary to integrate both current and new systems, whether cloud or on-premise.

About Customer

Pacific Compensation Insurance Company (PacificComp) is a California-based insurance company that specializes in workers' compensation insurance. In 2010, the company decided to fundamentally change its business model from direct sales to utilizing insurance brokers. This strategic shift was in response to the demands of an increasingly competitive workers' compensation insurance marketplace in California. The company believed that partnering with insurance brokers would provide more and better opportunities for California's employers. However, this transition required a major systems overhaul and posed substantial integration challenges. PacificComp chose to invest in software as a service (SaaS) applications to increase and decrease its usage as the market dictated. However, they also had several existing systems, so it was necessary to integrate both current and new systems, whether cloud or on-premise.

Solution

PacificComp chose Anypoint Platform to integrate their policy management, billing management, and other systems to support its business initiatives. The company hired Erich Leipold (evolsolutions LLC) as a contract architect to select an integration platform. They decided utilizing an enterprise service bus was the right architecture for their needs. From an architectural perspective, Pacific Comp used substantial numbers of SaaS applications. They decided the best architecture for their needs actually involved two Mule instances: a public and private instance. This provided appropriate security models for both external and internal Mule 'users'. Using Anypoint Platform, PacificComp began implementing the most critical and time-sensitive use cases required for their 2010 re-launch. First amongst these was integration between DCo, a policy management application for the AS/400 platform that managed all PacificComp policies, and STG billing, a billing application offered by MajescoMastek.

Impact #1	With the integration between policy management and billing in place, the most critical blocker to PacificComp's re-launch was removed.
Impact #2	The company also had several other needs that Anypoint Platform was well suited to solve. For example, they chose to use SpringCM as their enterprise content management system and Anypoint Platform provided a platform to integrate this with a number of internal applications that processed documents involved in the day-to-day operation of the insurance company.
Impact #3	Given the large number of documents printed daily in the insurance business as well as the substantial call volume, Pacific Comp also developed several smaller applications. The first of these printed groups of files delivered to PacificComp from STG billing as part of their billing workflow. A second logged calls to a database. Still others moved data between SQL databases, AS/400 databases and file shares as needed.

Impact #1

With the integration between policy management and billing in place, the most critical blocker to PacificComp's re-launch was removed.

Impact #2

The company also had several other needs that Anypoint Platform was well suited to solve. For example, they chose to use SpringCM as their enterprise content management system and Anypoint Platform provided a platform to integrate this with a number of internal applications that processed documents involved in the day-to-day operation of the insurance company.

Impact #3

Given the large number of documents printed daily in the insurance business as well as the substantial call volume, Pacific Comp also developed several smaller applications. The first of these printed groups of files delivered to PacificComp from STG billing as part of their billing workflow. A second logged calls to a database. Still others moved data between SQL databases, AS/400 databases and file shares as needed.

Download PDF Version

Overview

PacificComp ensures future-proof business transition with integration

Operational Impact