Integration Maturity Model: Where Does Your Digital Enterprise Fall?

By Jackie Rebrovic in Enterprise Integration Posted Feb 23, 2017

Today’s digital enterprise leaders must reshape their integration strategy to meet the demands of transformation in an increasingly digital world. For example, CIOs, IT leaders, and Enterprise Architects must unify enterprise APIs to enable cloud application portfolio agility. CTOs, Digital Strategists, and Product Management need to connect digital business apps to the ecosystems of SaaS apps used by their employees, partners and customers. Further, API Product Owners must create peronalized API experiences and workflows that are unique to their ecosystem of users. 

It’s imperative for these digital leaders to assess their integration approach, identify their enterprise’s current integration capabilities, and learn how to improve and move their integration strategy towards self-service and collaborative approaches.

At Cloud Elements, we’ve developed a five-tier integration maturity model. Each tier is defined by  the level of maturity, or proficiency, in each of the 5 key categories: Management, Pre-Packaged Endpoints, Patterns, Technology, and Users.

 

Maturity Model-01.png

Manual
This tier is categorized as:

  • The company has no integration strategy in place and no published APIs
  • Integration is not recognized as a major need or pain point from the IT organization
  • No endpoints or connectors are availabile
  • Each integration is manual, custom, typically point-to-point, and done on a one-off basis
  • File (CSV or FTP) or SDK-based
  • Users: IT specialist

Published
This tier is categorized as:

  • The company has an API or APIs published
  • The company and/or IT department are beginning to recognize integration as a challenge
  • No endpoints or connectors are availabile
  • Integration is still point-to-point, custom, and basic CRUD/S
  • APIs are REST, SOAP, or Web-Based
  • Users: IT specialist and developer
 
 
Let’s discuss which tier your organization falls into 

  

Consume
This tier is categorized as:

  • The API is configured and declarative
  • The organization may offer external, third party integrations but there is no integration service embedded into their product
  • The organization is competent in integrations offerings
  • A few, limited cloud connectors and services are offered
  • Synchronization of APIs
  • API documentation and a developer portal may be available
  • Users: IT Specialist, developer, LOB integrator

Self-Service
This tier is categorized as:

  • Embedded integrations offered as self-service or role-based access
  • An API integration strategy has been implemented, exposing APIs
  • Many cloud connectors and on-premise apps are available
  • There is a single integration strategy group that is responsible for putting multi-step workflows (such as Formulas) in place and creating pre-packaged templates
  • Sophisticated integration user interface, orchestration layer and abstraction layer exist
  • Users: IT Specialist, developer, LOB integrator, and citizen integrator

Ecosystem
This tier is categorized as:

  • An integration cloud is in the product offering
  • Many pre-packaged connections are offered along with the ability to integrate to things and distribute endpoints into leading platforms and marketplaces (such as AWS)
  • Capable of experience APIs, creating new connections and workflow templates
  • A serverless architecture, or the ability to run code without configuring and managing servers, is supported
  • Users: IT Specialist, developer, LOB integrator, citizen integrator, and contributors

If you’re looking to assess your organization’s integration competency, discover how you can improve, or determine the best next steps in your integration maturity, we would be happy to schedule a call.

Let's Chat!