ISO 20000 Maturity · IT Service Management (aligned with ITIL)
Your IT service management practices, measured against ISO 20000 and turned into a costed action plan.
10 themes, a 5-level scale. And the action that moves each level to the next.
The framework’s 10 themes, already written from L1 to L5. One company, one business unit, or 300 at once.
ISO 20000 Maturity · IT Service Management (aligned with ITIL)
10 themes, 5-level scale.
Nordhavn Industries
53 / 100
They measure their maturity with Datamensio
An example
This could be your situation.
Take one company as an example: three sites, three spreadsheets, no shared answer.
Nobody can consolidate.
Nordhavn Industries, 2,400 people in Hamburg, Lyon and Porto. A client asks where the group stands. Each site answers in its own spreadsheet, with its own scales.
Three weeks, a single base.
One ISO/IEC 20000-1:2018 assessment launched across all three sites at once, from the managers’ interview notes. The framework was already written, its 10 themes and levels L1 to L5 too.
Two costs avoided before being committed.
A score of 53 out of 100, with the gap concentrated on three themes. The AI companion spotted that two actions duplicated those of another audit. The committee report took one sentence to request.
What it saved them
- 3sites measured on the same base, instead of three questionnaires to reconcile
- 2duplicate actions caught before the spend
- 1committee report, with no manual rework
These figures are an example. They could be yours.
The standard imposes processes. Datamensio says where you stand.
01
The framework is already written
Themes, questions and levels L1 to L5, all written. You do not start from an empty spreadsheet.
02
The score lands the same day
Online, by self-assessment link or in interview. Theme by theme, comparable over time.
03
The gap becomes a costed plan
Every step up carries its action. The AI prioritises on expected effect, not on the order of the standard.
04
Progress can be demonstrated
Campaign after campaign, against your target and against your own past. That is what your board asks for.
The maturity scale
One level, the next, and the action that links the two.
This mechanism, a level, the level above, and the action linking the two, is what turns an observation into a trajectory.
Are changes assessed, approved and reviewed after release?
- N1
Changes are made on the fly. No formal record of the request, the approval, or the observed consequences.
- N2
A procedure exists and a board meets, but some changes bypass the circuit, particularly emergencies and application deployments.
- N3
All changes are logged and classified. Risk assessment and a rollback plan are required before approval.
- N4
Changes are tracked through indicators (failure rate, emergency changes, induced incidents) presented at the service review.
- N5
The indicators feed into the revision of classification rules and approval thresholds, with a documented history of adjustments.
Action to move from L2 to L3
Make it mandatory to log every change, including emergency and application changes, requiring risk assessment and a rollback plan within the ITSM tool’s form, then check for unlogged changes at the weekly board meeting.
« With Datamensio, we meet our objectives far more efficiently. The ERDF inspection services and our supervising ministry particularly appreciated an approach that gives them reliable data. »
Director, CCI 94CCI Île-de-France
« We believe this is the most suitable solution to scale our transformation project and measure impact according to our needs. »
Maja SucekChief Operating Officer, Interreg Danube
Rarely on its own
Frameworks combine. Put several together to cover your business, or have the AI write yours.
Take your first measurementon ISO 20000.
What this framework covers
ISO/IEC 20000-1 is the international standard for service management systems. Its 2018 version imposes the high level structure common to ISO management standards: context, leadership, planning, support, operation, performance evaluation, improvement. It requires a service catalogue, service level agreements, and documented management of incidents, requests, problems, changes, releases, capacity, availability and continuity. It is certified by an accredited body, over a defined scope of services. ITIL is not a standard but a body of best practice: it describes how to do what ISO 20000 requires.
In practice, the same points tend to resist scrutiny. Does the service catalogue describe services delivered to the business, or a list of applications and servers? Are SLAs negotiated with client departments and measured against real data, or rolled over year after year without review? Does problem management exist beyond post-mortems of major incidents? And when a change causes an outage, does the loop feed back into a review of the process, or stop once service is restored?
Two developments often blur the picture. First, the move to ITIL 4, which drops the phased lifecycle in favour of a service value system and 34 practices: many organisations have adopted the vocabulary without revisiting their processes. Second, the industrialisation of cloud and DevOps pipelines, which shifts part of the change flow outside the classic circuit. One common confusion worth clearing up: ISO 20000 does not certify people trained in ITIL, it certifies a service management system over a given scope.
The maturity assessment answers a different question from the certification audit. The audit checks that requirements are met and concludes with conformity or non conformity. The assessment places each practice on a progressive scale, from improvised action to data driven management, and points to the action that moves it up a level. It prepares for the audit, it does not replace it and issues no certificate.
Within Datamensio, the framework is ready to use and remains fully yours. You adjust the themes to your certified scope, to outsourced managed services, or to a multi entity organisation. AI rephrases the questions, refines the levels using the CMMI method, or builds a variant from your service manual and existing procedures.
Reference standard: ISO/IEC 20000-1:2018
The themes assessed
Governance of the service management system
Service policy, SMS scope, roles and responsibilities, management commitment, governance of services provided by third parties.
Service catalogue and client relationship
Description of services delivered to the business, service owners, communication with client departments, complaints and satisfaction management.
Service levels and reporting
Service level agreements, measured indicators, data sources, periodic reviews with internal clients, service dashboards.
Incident and request management
Logging and qualification, prioritisation, escalation, major incident procedure, user communication, restoration times.
Problem management
Detection of recurring causes, root cause analysis, known errors and workarounds, tracking of corrective actions through to closure.
Change and release management
Change classification, approval board, risk assessment, rollback plans, testing, deployment schedule, post release review.
Configuration and asset management
Configuration model, maintenance of the CMDB, relationships between items, data accuracy checks, alignment with software asset management.
Capacity, availability and continuity
Demand forecasting, sizing, availability targets, service continuity and recovery plans, documented tests.
Information security applied to services
Access controls, access rights management, handling of security incidents, alignment with the ISMS and ISO 27001 requirements.
Measurement and continual improvement
Internal audits, management review, non conformity management, improvement register, comparison of results over time.
A short version of the framework is available for the online self-assessment.
Frequently asked questions
Does the assessment grant ISO 20000 certification?
No. Certification is issued by an accredited body, following an audit over a defined scope of services. The assessment measures the maturity of your practices, identifies uncovered requirements, and produces the action plan that prepares for that audit.
What is the difference between a maturity assessment and a certification audit?
The audit concludes with conformity or non conformity on each requirement. The assessment places the practice on a progressive scale and points to the action that raises it a level. One validates, the other charts the trajectory.
Do we need to have moved to ITIL 4 to use this framework?
No. The themes follow the requirements of ISO/IEC 20000-1 and the corresponding service management practices, whichever ITIL version has been adopted. The questions focus on what the organisation does, not on the vocabulary used to describe it.
How long does the assessment take?
The self assessment can be run in a short session. The full version, run collaboratively with process owners, typically spans one to two weeks: most of the time goes into gathering input from operations, support and supplier teams.
Can the framework be adapted to our scope?
Yes. You can amend the questions, levels and themes, particularly to reflect outsourced services or a narrower certified scope. AI can also generate a variant based on your service manual and procedures.
Can several entities be compared with each other?
Yes. The same framework applies to each business unit or service centre, and scores can be compared by theme, across entities, and against your previous assessments. A cross entity roadmap consolidates the action plans from several assessments.
How does this assessment relate to ISO 27001 or ISO 22301?
Security, continuity and availability requirements overlap significantly. Findings from the ISO 20000 assessment can be reused, and the cross framework roadmap avoids duplicating actions common to all three schemes.
Where is the data hosted?
In France, with OVH, backed up at Scaleway. No transfer outside the European Union. The AI models used can be selected, including from European providers.