From the Blogosphere
Enterprise Cloud Maturity Model – How to Guide | @CloudExpo #Cloud
The ECMM provides an openly available tool set that exploits what is an already available goldmine of industry resources
Apr. 5, 2016 02:00 PM
Enterprise Cloud Maturity Model - How to Guide
Introducing the ECMM – Enterprise Cloud Maturity Model
As this IDC report shows only 25% of organizations have repeatable strategies for Cloud adoption, with 32% having no Cloud strategy at all.
Therefore the goal of our Enterprise Cloud Maturity Model (ECMM) is to address this market need through a best practice based repeatable framework for planning Cloud adoption that drives business transformation maturity, encompassing:
Digital Platforms – From a top define perspective we focus on the key relationship between the underlying technical architecture and innovative, revenue-generating business models. How can this capability be defined as a repeatable blueprint for driving new strategic initiatives?
Enterprise Cloud Transformation – From the bottom up we reference a number of Cloud adoption materials so that organizations can advance their enterprise-wide Cloud maturity.
The purpose of the ECMM is to provide an openly available tool set that simply exploits what is an already available goldmine of industry resources focused on the practices and goals of migrating to new Cloud services, mainly focused on the process of cataloguing them and defining their integrated synthesis.
Adoption Planning Framework
It is accessible as one document to support an overall adoption program like our TRANSFORM Lifecycle, as well as being organized by five distinct journey modules for organizations seeking those isolated benefits:
Best Practice Reference Models
It’s a framework that leverages simple but powerful principles, most notably that ‘aaS’ denotes adherence to a core common model, that the application is virtualized and can run on public IaaS, and therefore the terms all represent solution packaging of complex IT scenarios into a standardized, service-centric approach that integrates with the existing environment of Cloud Management tools.
This means customers can approach their Cloud Solution Design process as a “lego brick assembly” process, where they can de-compose their business model goals, eg Launch New Mobile Banking Service, into a series of Cloud modules, like IDaaS and iPaaS, each adding critical application level functionality that’s common to any digital enablement scenario, and that can be provisioned into a pre-defined DevOps environment that operates from this common Cloud platform.
ECMM Solution Guides
In this modular fashion they build atop the ECMM to describe its application to specific customer scenarios, such as DRaaS, as well as to define the individual building blocks, like IDaaS. Identity as a Service is a solution in its own right that can facilitate a variety of customer functions, and also it can act as a foundation higher level capabilities that leverage the integrated identify ecosystem that the technology makes possible.
Vendor Capability Maps
Each guide is based around a common solution guide model, with ‘VCMs’ – Vendor Capability Maps, being one of the central foundations.
This is because typically to define a maturity journey, in Cloud service terms, there is usually a process of deploying vendor infrastructure (including VMs) that then results in new capabilities within the Cloud provider portfolio. A simple example being use of a vendor like Veeam to enable core DRaaS and Backup functions.
As we explore the different domains of the ECMM, from DevOps through portability, then so different permutations of vendors yield different service capabilities. These can build out common Cloud platform building blocks as well as enable scenario-specific features.
Guides are further augmented with industry reference documents that also work around these same Cloud service terms, such as Gartner Magic Quadrants. For exampe in their MQ Critical Capabilities for DRaaS they say the MQ “assists IT leaders in developing a list of DRaaS providers and evaulate each on critical capabilities to be considered when choosing a DRaaS provider in order to best meet the needs of an organization.”
Our goal is to use theirs and other similar recommendations to offer ready-to-implement solution programs built around these design themes.
For example for our Mobile Enterprise guide:
Mobile applications are demanding scenarios and these application components will need to be able to scale dynamically in response to fluctuating, high volume demand, as well as ensure security. Apprenda provides the core Cloud platform components that meet these needs, such as multi-tenancy scalability and security policy enforcement.
The Apprenda PaaS is a software layer that can stitch together any number of server OS instances and load balancers into a distributed, logical, single-instance, shared services and data container. Apprenda aggregates all CPU, memory and storage capacity across OS nodes into an aggregate resource pool where enterprises can publish their mobile back-end web services and data models as “guests” to the hosting platform.
Hybrid Cloud Outsourcing
This deliver is contextualized within an overall trend of ‘Hybrid Cloud Outsourcing’, to reflect the best practice and practical needs of enterprise organizations. Hybrid Cloud simply means a combination of some public IaaS with on-premise IT, but in practical implementation terms the types of issue that need addressed can include simple co-location of existing servers and legacy IT, not yet ready for Cloud migration.
A full service solution provider is able to meet this spectrum of needs and leverage IaaS as a core solution building block to quickly assemble next generation digital solutions, via an outsourcing framework that also yields short term efficiencies and cost savings through outsourcing best practices.
Tweets by @WebRTCSummit
Digital Transformation Blogs