Blog post

Real-Life Case Studies of Four iPaaS-Based Architectures

By Mei Selvage | April 04, 2016 | 1 Comment

Many Gartner clients are interested with case studies so they can study best practices and lessons learned. In my recent research “Comparing Four iPaaS-Based Architectures for Data and App Integration in Public Cloud“, I shared some real-life case studies of four iPaaS-based architecture. This blog complements my previous blog on “Why You Need Integration Platform as a Service“.

Case Study of the Cloud-to-Cloud Architectural Pattern

A10 Networks is a leader in application networking and security and is experiencing fast growth. To scale the business, it chose Oracle E-Business Suite (EBS) Financials for enterprise resource planning (ERP), which is hosted on the public cloud. A10 Networks also used Salesforce customer relationship management (CRM), a cloud application. Previously, staff needed to manually enter data in two systems, which did not scale well and led to many errors and high costs. A10 Networks needed to integrate the two systems automatically to meet the demand of its fast growth and reduce data errors and application costs.

Based on the cloud-to-cloud integration model, A10 Networks adopted Dell Boomi to connect two SaaS applications: Oracle EBS and Salesforce CRM. The workflow-driven nature of Dell Boomi AtomSphere allows A10 Networks to quickly visualize interactions. All of A10 Networks’ customer information is now bidirectionally integrated between Salesforce and Oracle EBS.

This integration through Dell Boomi AtomSphere immediately eliminated manual data entry, decreased data errors by 90%, lowered IT application costs by 10% and reduced staff hours by 40%.

Case Study of the iPaaS-Centric Architecture

Splunk’s software and cloud services collect, search, monitor and analyze machine data to help organizations capitalize on the digital transformation. To support year-over-year growth of more than 50%, Splunk urgently needed to streamline its internal operations. Its existing on-premises ETL tool was incompatible with the company’s fast-moving processes and the goal to be a 100% cloud platform. In short, Splunk wanted to adopt an agile, scalable cloud integration platform that would improve operational efficiency between sales and finance, as well as speed up order processing and fulfillment.

Based on the iPaaS-centric architecture, Splunk used MuleSoft to connect its SaaS applications such as Salesforce and NetSuite. MuleSoft’s Anypoint Platform became the backbone of a streamlined, automated quote-to-cash process. Meanwhile, existing ETL is treated as a black box to continue handling existing integration for on-premises systems without expanding its footprint. Over time, Splunk plans to migrate its on-premises ETL tool to MuleSoft to allow it to move and innovate faster.

In just 20 days, Splunk was able to streamline its quote-to-cash process and reduce transaction processing time from minutes to real time, which helped it complete order processing by the year’s end and serve its customers faster.

Case Study of the On-Premises-Centric Architectural Pattern

One large health insurance company offers diverse business that serves millions of people in the U.S. To provide customers with excellent experience, its multiyear IT strategy aims to make data easily available for business users to create more personalized plans and programs. The insurance company needs to bring together interaction details from numerous systems — sales campaigns, clinical, customer service and digital systems — to provide a comprehensive view of all the interactions.

The insurance company has adopted a variety of Informatica solutions, including Informatica PowerCenter and Informatica Cloud. The hybrid integration architecture has enabled it to analyze information from a variety of angles and create personalized programs and plans. Many use cases use an on-premises-centric architectural pattern to fully leverage their existing on-premises investment while handling cloud integration.

Case Study of the On-Premises Deployment Architecture

DJO Global manufactures and sells a broad range of orthopedic medical devices such as knee and hip replacements and conservative care products. It also developed the MotionMD Software that provides a paperless product dispensing experience, automates inventory management and allows physicians to create diagnosis-driven protocols. DJO Integrator is DJO Global’s interface that shares patient demographic data from a clinical electronic medical record (EMR) system with MotionMD. With hundreds of different EMR providers and other software solutions that healthcare practices use, DJO Global needed MotionMD and DJO Integrator to be able to integrate data in a variety of data formats with a straightforward, streamlined approach.

DJO Global used Dell Boomi to empower MotionMD and DJO Integrator to securely transform and transport patient data in a variety of formats: HL7, flat files, database pulls or APIs. The Boomi Atom — an on-premises runtime engine with a small footprint — is easy to install and manage. Using the on-premises deployment architecture, Boomi can control access to patient data and ensure that data remains secure. This is critical for HIPAA compliance.

Partnering with Dell Boomi, MotionMD and DJO Integrator can help clinics reduce billing lead time and improve financial results by improving “first pass” collection rates — claims paid on the “first pass” by the insurance companies without being rejected.

iPaaS is real with the growing trend of “cloud-first” strategy adopted by many organizations. For more information on iPaaS, please see Gartner’s document “Comparing Four iPaaS-Based Architectures for Data and App Integration in Public Cloud“.

Leave a Comment

1 Comment

  • joe says:

    Interesting read, thought provoking