BT: Platform Architecture for Enterprise Data Centre Consolidation


The Platform Business Model is mostly referenced in terms of exciting new peer to peer business models, like Uber Taxis and Airbnb.

However a critical aspect of the model and its technical design is that it offers a very practical tool set with dealing with less lofty but equally demanding enterprise IT goals, especially those in the areas related to application and data centre consolidation, a common theme and requirement across the world.

bullseyePlatform as a Target Operating Model

Indeed when you consider the role and challenge of legacy technologies, such as banks aspiring to become Digital but are based entirely on COBOL mainframes. Governments too, and most other large enterprises, are typically faced with one primary IT challenge: Maintaining and modernizing a vast estate of thousands of applications, from SAP through Microsoft and now of course multiple SaaS too.

While users may interact via their mobile devices most of the apps they want to access are running somewhere in that estate, and so integration and/or modernization is one of the primary transformations digital leaders will have to undertake.

What is most notable about the Platform model is that it can be used as a 'Target Architecture', the destination goal of a business transformation exercise, which defines and describes what the resulting end state will look like, in Business and Enterprise Architecture terms.

Architecture-Driven Data Centre Consolidation

This is particularly important when CIO's marry their digital strategies with common enterprise IT requirements, most notably data centre consolidation, one of the primary benefits of the trends of virtualization and Cloud computing.

The primary business benefit outputs of a business transformation-driven virtualization project are achieved through multiple levels of consolidation, and the Platform can represent this model.

This includes migrating multiple aged hardware platforms to multi-tenant virtualized environments, and with a Business Architecture scope also addresses duplicated business process functions as well, yielding multiple levels of cost saving and process efficiency improvement.

Keynote Reference Model

An especially well-detailed case study of implementing this approach is "How Platforms and API’s enable businesses to participate in the Digital Eco-systems of the future", the TMF Live 2016 presentation from George Glass, Chief Systems Architect at BT.

pdf2Download: 17 page PDF


This presentation details:

  • Problem Statement - The complexities of enterprise systems comprised 4,500 systems with 3,000+ APIs, causing very long development cycles = poor innovation rates.
  • A real-world implementation of Platforms, APIs and Digital Ecosystems, documenting the benefits and how they were realized, via their 'Matrix Platform Architecture'.
  • A Cross Domain Orchestration layer - Unifying multiple legacy estates into one "e2e" workflow channel.
  • Reusable process blocks and APIs, designed around a "Customer Oriented Architecture".
  • An end result To Be architecture - 26 platforms and 700 systems, via simplicity and ruthless standardization.
  • Driving continual results delivery - Consolidating and closing hundreds of applications each year.


Key best practices principles defined in this presentation include:

Architecture-Driven Transformation

This is the main content.

  • Slide 16 - "Architecture enabled business transformation". ACF - Architectural Conformance Framework.

Service Innovation Lifecycle

This defines ADT: Architecture-Driven Transformation

Community Review

This is the synopsis of the Agenda Review.

Neil McEvoy
About Neil McEvoy 18 Articles
Founder and CEO of the Cloud Best Practices Network.

Be the first to comment

Leave a Reply

Your email address will not be published.