Integration Strategy Empowerment Team (ISET) vs. Integration Competency Center (ICC): What's the Difference?

Posted by Brooke Lester on Nov 20, 2019 3:40 PM

Integration Strategy Empowerment Team (ISET) vs. Integration Competency Center (ICC)

There is more than one approach to integration. When thinking about integration methodology, you want to choose the right one, but how do you know which to choose?

Experts from Gartner recommend the Integration Strategy Empowerment Team (ISET) approach as opposed to the Integration Competency Center (ICC) approach. Read on to learn what the differences in these methods are and why those differences matter.

What Is the ICC Model of Integration?

We will start off by exploring what an ICC is. Essentially, an ICC is a knowledge base of data integration information. It should be shared across the entire enterprise so that everyone has the facts they need to properly carry out data integration.

An ICC is a centralized model. It does not take into account the technological changes that have taken place over the past few years – specifically, the advent of APIs for B2B integration. APIs for B2B integration have ushered in a new era of integration.

What Is the Gartner ISET Approach to Integration?

Before we launch a discussion of what an ISET is, we must delve into what a Hybrid Integration Platform (HIP) is, because an ISET cannot really exist without a HIP.

Gartner defines a HIP as “a capability framework that combines on-premises and cloud-based integration and governance capabilities, and supports a wide range of integration use cases.” While you can implement a HIP as a variety of technology building blocks (from a single provider or more than one), you manage it as a comprehensive, federated whole.

“An ISET can’t exist without a hybrid integration platform.”

A HIP supports a number of integration categories: application, data, B2B integration, and process integration. Moreover, there are a variety of use cases for which a HIP makes sense, including IoT, mobile, and cloud information. A HIP also allows for self-service.

That is where the ISET comes into the picture. An ISET is responsible for designing, implementing, and delivering the HIP. The team provides training, support, consultation, and help desk services to everyone involved in the integration project. In addition, an ISET runs a “community of practices” so that users understand how to derive the greatest value from integration.

“An ISET is responsible for designing, implementing, and delivering the HIP.”

Part of the ISET’s task is to put self-service integration capabilities into place, which is closely tied into APIs for B2B integration. APIs for B2B integration allow users to gain information that would not otherwise be available, such as details on when a shipment is due to arrive. An ICC cannot put APIs for B2B integration into place, and APIs are becoming a crucial part of the enterprise IT landscape.

When you are considering integration approaches, you want to select one that reflects current best practices. You want an integration strategy that takes the latest technological advancements into account, not one that relies on outmoded information. The Gartner ISET model allows you to embrace the digital transformation by implementing cutting-edge APIs for B2B integration.


Subscribe to Email Updates

Stay Connected

Recent Posts