India’s Leading Domain & Web Hosting Provider
Support
Domain & Login
Blog
Cloud Operating Model Assessment: CCoE, Roles, Skills and RACI
A cloud operating model assessment examines how an organisation will run cloud: who decides, who builds, who operates, which skills exist, and how processes such as change, cost control and security work once workloads are in cloud. NTSPL scores maturity across roles, skills, processes and vendor boundaries and designs a target model, often a small CCoE, sized to your team and footprint.
Delivered on
In scope
Why an On-Premises Operating Model Breaks in Cloud
Organisations move workloads to cloud with an on-premises operating model: a change board that meets weekly, a network team that owns every firewall rule, procurement that approves each new server. The result is either cloud that moves at data-centre speed, or teams that bypass the process and create unmanaged accounts. Neither IT nor finance can say who owns cost, who approves new services or who answers when the MSP and application vendor disagree.
NTSPL interviews leaders and practitioners across IT, security, finance and key vendors, maps current roles and decision rights, measures skills by role, and scores 24 processes for cloud fitness. We then design a target model: CCoE shape and size, RACI across internal teams, MSP and vendors, a skills plan with certification targets, and the process changes needed, sized for organisations from 5 to 500 IT staff.
When the Operating Model Needs Redesign
Signals you need Cloud Operating Model Assessment
- Cloud spend has passed about ₹50 lakh a year with no named owner for cost or governance
- More than three teams or vendors create resources in cloud with inconsistent standards
- A managed service provider and application vendors dispute responsibility after incidents
- Provisioning a new environment still takes over two weeks because of on-premises approval steps
When to choose something else
- You need recurring governance run, such as policy compliance reviews, exceptions and account vending: that is a managed governance operations service.
- Cloud footprint is a single SaaS-like workload run entirely by a vendor: a simple vendor RACI is enough.
Operating Model Dimensions We Assess
Decision rights and structure
Who approves new services, accounts, spend and exceptions, and whether a CCoE or platform team exists.
Roles and skills
Current roles mapped to cloud roles, with certification and hands-on experience measured per person.
Process maturity
24 processes, including change, incident, provisioning, cost review, security exception and capacity, scored 1-5.
Vendor and MSP boundaries
Contracts and actual practice compared, with RACI gaps between internal teams, MSPs and application vendors.
Financial ownership
Budget owners, tagging and showback practice, and how cost decisions reach business units.
Roles-Skills-Process Maturity Model
Roles-Skills-Process Cloud Operating Model Maturity Model
Interviews, skills surveys and contract reviews build a current-state picture across structure, roles, processes and vendors. Maturity scoring identifies gaps, and a target model with a CCoE, RACI and skills plan closes them.
Select any component
Roles-Skills-Process Cloud Operating Model Maturity Model: click any of its 8 components to see its role and the design choice NTSPL makes for it, or trace the 7-step primary path.
Adoption Framework Guidance From Each Provider
The CAF people and governance perspectives frame role design, and Account Factory shows how self-service provisioning changes approval processes.
CAF's Plan phase guidance on cloud skills and role-based skills matrices informs CCoE shape, and subscription vending replaces manual environment requests.
The Adoption Framework's maturity scale grounds process scoring, and folder and policy hierarchy show how decision rights translate into controls.
Organisation Design Choices for Cloud
CCoE size and form
Under 30 IT staff: a virtual CCoE of 2-3 people at 20-40 percent time, plus MSP. 30-150 staff: a dedicated team of 3-6 covering architecture, platform, security and FinOps. Over 150: a platform team operating the landing zone as a product, with a small governance group. A CCoE larger than about 5 percent of IT tends to become a bottleneck.
What the MSP owns versus you
Keep architecture decisions, security policy, cost ownership and vendor management internal. Give the MSP monitoring, patching, backup operations and incident first response with clear SLAs. Write the boundary in a single RACI covering application vendors too, because most disputed incidents sit between MSP and vendor, not between you and either.
Skills thresholds
Aim for at least two certified practitioners per cloud in use, one architect-level certification for each major platform, and FinOps awareness for budget owners. Hands-on experience matters more than certificates; pair certification targets with rotation into live operations.
Changing on-premises processes
Replace per-server approvals with guardrails: pre-approved patterns, policy-as-code and budget alerts. Keep a change board for production-impacting changes but allow standard changes through pipelines. Target environment provisioning in under one day for pre-approved patterns.
Five-Week Operating Model Assessment
Interviews and document review
Leaders, practitioners, MSP and vendors interviewed; contracts reviewed.
Skills survey
Skills and certifications captured and validated for key roles.
Process and RACI scoring
24 processes scored and RACI gaps identified from incidents.
Target model design
CCoE, RACI, skills plan and process changes designed.
Roadmap and leadership review
Six to twelve month roadmap agreed with CIO and HR.
What you receive
Operating Model Health Indicators
| KPI | Typical target |
|---|---|
| Average process maturity score | Up by 1 level within 12 months |
| Environment provisioning time for standard patterns | Under 1 day |
| Incidents with disputed ownership | Down 80 percent |
| Certified practitioners per cloud | At least 2 |
Operating Model Failure Modes
| Risk | How NTSPL prevents it |
|---|---|
| CCoE becomes a new approval bottleneck | Charter defines guardrails and self-service, with approval only for exceptions. |
| Role changes resisted by staff | HR involved early, with career paths and training tied to new roles. |
| RACI written but MSP contract unchanged | Contract amendments listed in the roadmap with renewal dates. |
Do we need a full Cloud Centre of Excellence or is a managed service provider enough?
An MSP is enough for operating tasks, monitoring, patching, backup and first-response incidents, but not for decisions. Someone inside your organisation must own architecture standards, security policy, cost and vendor accountability. For small IT teams, that can be a virtual CCoE of two or three people spending part of their time, working with the MSP. Mid-sized organisations usually need a dedicated team of three to six. Relying entirely on an MSP tends to produce good operations but drift in standards and cost, because the MSP is not accountable for business outcomes.
Key facts: Cloud Operating Model Assessment
Cloud Operating Model Assessment in Practice
2 Cloud Operating Model Assessment scenarios, from Spice processing and export and Architecture and design, plus related platform case studies.
Spice exporter builds a 3-person virtual CCoE and ends MSP-vendor blame on AWS
Architecture firm gives Azure desktops and AWS collaboration one owner and one RACI
Telecom VAS provider cuts daily pages from 2,300 alerts to 9 actionable incidents
IT services firm brings 43 Azure subscriptions under one policy hierarchy
Cloud Operating Model Assessment: Frequently Asked Questions
How long does a cloud operating model assessment take?
Five weeks for most organisations. Interviews and the skills survey take two to three weeks; scoring, design and roadmap take the rest. Large groups with several IT functions may need seven weeks. A re-score after six months is included to measure progress.
What does a cloud operating model assessment cost?
Typically 15-24 consultant days, depending on interview count and the number of vendors involved. Smaller organisations with one MSP and a single cloud sit at the lower end. Organisations running several clouds and MSPs sit at the upper end.
Does the assessment include regulatory roles?
Yes. For regulated entities, roles required by RBI, SEBI or IRDAI governance and outsourcing directions, such as oversight of outsourced IT and incident reporting to CERT-In within 6 hours, are included in the RACI and decision rights. Reporting lines to the board or its IT committee are mapped too.
Will it recommend headcount changes?
It recommends roles and skills, and whether to build, hire or contract them. Headcount decisions stay with management and HR, but we show the cost of each option. Contracting a role is often cheaper for niche skills such as FinOps or Basis.
How does this differ from a cloud readiness assessment?
Readiness checks whether foundations such as identity, network and landing zone are in place to start migrating. The operating model assessment designs how the organisation runs cloud long term: structure, roles, skills and processes. Many organisations run readiness first and the operating model assessment second.
Can the MSP take part?
Yes, and it should. MSP staff are interviewed, their contract is reviewed and the target RACI is agreed with them, so changes can be reflected at renewal. Their commitment to the RACI matters more than the document itself.