Twelve weeks to a CMDB worth trusting. Twelve more to an ITSM platform worth upgrading.
A premier assessment body running high-stakes licensing examinations could not map its own IT estate, and had customised its service platform to the point where upgrades had become a project in themselves. VYNQOR fixed the order of operations: foundation first, simplification second.
When you certify professionals, your IT estate is part of the assurance chain.
This organisation is a century-old non-profit evaluation body responsible for the standardised assessment tools, shelf exams and high-stakes licensing benchmarks that thousands of candidates sit each year across multiple countries. An examination that cannot be delivered is not an IT incident. It is a candidate whose licensure is delayed.
Two problems had developed in parallel and were reinforcing each other. The configuration management database could not be trusted, so nobody could say with confidence which infrastructure supported which examination service. Meanwhile the ITSM platform had accumulated custom tables, bespoke customisations and process deviations over years of well-intentioned change, producing complexity, maintenance burden and an experience that pushed users away from the tools meant to serve them.
The two problems were treated as one engagement, deliberately sequenced. Standardising service management on data nobody trusts produces a tidy platform reporting on fiction.
High-stakes examination delivery depended on infrastructure relationships that existed in nobody's system of record, only in individual expertise.
Over-customisation had made every ServiceNow upgrade a bespoke engineering exercise rather than a routine platform activity.
Configuration items created and corrected by hand, consuming skilled effort that produced no durable improvement in accuracy.
- No trusted CMDB, with fragmented infrastructure data across a distributed global environment.
- Manual configuration item creation and persistently poor data quality.
- No visibility of service impact or dependency relationships.
- Limited ITOM adoption, with discovery largely unexploited.
- Over-customisation and custom tables driving platform complexity and upgrade difficulty.
- Process deviation from standard ITSM practice, poor user experience and low adoption.
- Limited knowledge availability, and correspondingly low self-service usage.
How we approached it
Two programmes, one thesis: establish data you can trust, then remove everything built on top of it that should not be there.
Sequence the programmes deliberately
Discovery and CMDB first, ITSM simplification second. Standardising service management on untrusted data produces a platform that reports confidently on the wrong picture. The order was the strategy.
Align to CSDM from the outset
Core CI taxonomy and Common Service Data Model alignment were designed in at architecture stage rather than retrofitted, so the CMDB is upgrade-safe and ready to carry AIOps rather than needing rework to support it.
Make correctness a system property
Authoritative data source strategy, IRE configuration and automated discovery replaced manual CI creation, so data quality is enforced by the platform rather than sustained by effort.
Return ITSM to the box, as a discipline
Custom tables and redundant customisations were removed rather than documented. Out-of-the-box capability was configured in their place, with governance and change control established to hold the position after go-live.
Enable users rather than train them
Knowledge Management and an enhanced Service Portal were treated as the adoption mechanism. Self-service is not a deflection tactic; it is what makes a simplified platform feel better rather than merely cheaper.
The architecture behind the outcome
A trusted data foundation carrying a deliberately standard service layer - governed sources feeding a CSDM-aligned CMDB, with out-of-the-box ITSM configured on top.
Measured, not estimated.
Metrics we would instrument next to extend value measurement beyond the delivered baseline. These are recommendations, not achieved results.
- Self-service deflection rate - proportion of requests resolved through knowledge and portal without agent involvement
- Custom table count and configuration drift, tracked release over release to protect the back-to-box position
- Elapsed time and effort for the next ServiceNow family upgrade, against the pre-simplification baseline
- SLA adherence and mean time to resolution, measured against the pre-transformation baseline
Delivered through VynImpact™
Every VYNQOR engagement runs on the IMPACT methodology, so delivery health is visible continuously rather than reported retrospectively. This programme ran 6 months end to end.
Enterprise CMDB assessment and discovery readiness review established the true state of configuration data against the distributed global estate.
Enterprise CMDB architecture, core CI taxonomy with CSDM alignment, and the authoritative data source strategy that determines which system wins for which class of data.
Governance operating model and relationship model established, then Discovery, Service Mapping, IRE configuration and CMDB Workspace implemented against them.
Current-state assessment of custom tables, customisations and process deviations, with the to-be state designed against ServiceNow best practice rather than existing behaviour.
Unnecessary custom tables and redundant customisations removed, ITSM processes standardised on out-of-the-box capability, workflows simplified through Flow Designer and UI policies.
Knowledge Management integrated with a structured knowledge base and contribution model, and the Service Portal enhanced to make self-service the path of least resistance.
Scope, grouped by discipline
Platform Engineering
- ServiceNow Discovery implementation
- Service Mapping implementation
- IRE configuration and CMDB Workspace
- Removal of unnecessary custom tables and redundant customisations
- Out-of-the-box ITSM reconfiguration
Governance
- CMDB governance operating model
- Core CI taxonomy and CSDM alignment
- Authoritative data source strategy
- Standards and change control to protect the back-to-box position
Data
- Enterprise CMDB architecture
- Relationship and dependency model
- CMDB data quality and health dashboards
- CMDB integration with ITSM processes
Automation
- Workflow simplification through Flow Designer and UI policies
- Automated notifications
- SLA management configuration
User Experience
- Enhanced Service Portal for intuitive access
- Integrated Knowledge Management for self-service
- Knowledge base structuring and contribution model
Operations
- Reporting and dashboards using out-of-the-box tooling
- ITOM Visibility enablement
- Foundation prepared for AIOps and intelligent operations
Client testimonial pending approval. This engagement is available as a named reference on request.
Reference available on requestWhat made the difference
We argued for the sequence, not just the scope
Running ITSM simplification first would have been faster to show progress and would have standardised the platform on data nobody trusted. Foundation before simplification was the decision that made both programmes hold.
Back to box was executed, not just recommended
Plenty of assessments recommend removing customisation. Custom tables and redundant configuration were actually removed, and governance was established to stop them returning.
CSDM designed in, not retrofitted
Aligning taxonomy to the Common Service Data Model at architecture stage is why this CMDB can carry AIOps later without being rebuilt for it.
More client stories
Facing a comparable challenge?
Every engagement starts with understanding the business outcome you need, not the platform you already own.