From Configuration to Value: How the VMDB Transforms the CMDB into a Value Management Engine

For decades, the Configuration Management Database (CMDB) has been a cornerstone of IT service management (ITSM). It catalogues configuration items (CIs), tracks relationships, and supports change, incident, and problem management. Yet, despite its critical role, the CMDB remains fundamentally technical – a system of record for how IT services work, but not why they matter. Enter the Value Management Database (VMDB) – a natural evolution of the CMDB that extends beyond configuration to capture and manage the value delivered by digital products and services.

The VMDB introduces a new layer of business intelligence within service management tools, linking the technical configuration of services (managed in the CMDB) with their intended and realized value (defined in the Value Register). This integration provides the missing bridge between IT operations and business outcomes – enabling organizations to configure, measure, and optimize value with the same discipline they apply to technology.

The VMDB becomes a cornerstone of operational value realization, ensuring that the services catalogued in CMDBs are recognized not only for what they do but for what they deliver.

The CMDB’s Limitations in Driving Business Value

The CMDB has long promised visibility and control over IT environments. However, many organizations face the same persistent issue: the CMDB is rich in data but poor in meaning.

It describes components, applications, and services, but it rarely explains why those services exist, what value they generate, or who ultimately benefits.

This limitation has three main causes:

1. Technical ownership – The CMDB is typically owned by IT, focused on accuracy, compliance, and change traceability. Business stakeholders often see it as irrelevant or overly technical.
2. Disconnected from outcomes – CMDBs describe service dependencies, not the business outcomes those services support.
3. Static view – While the business continuously evolves, the CMDB structure is rarely adapted to capture the changing value expectations of digital services.

In other words, the CMDB has become a mirror of IT infrastructure – not of enterprise value.

To make the CMDB relevant again, we need to enrich it with the dimension it has always lacked: value.

Introducing the VMDB – The Next Evolution in Service Management

What Is the Value Management Database (VMDB)?

The VMDB is an evolution – not a replacement – of the CMDB. It extends configuration management with value management capabilities, adding a layer that links services, assets, and processes to their expected and realized value.

How the VMDB Complements the CMDB and AMDB

In the ITSM ecosystem:

• The AMDB (Asset Management Database) records financial and lifecycle data of physical and digital assets.
• The CMDB records the technical and functional composition of services.
• The VMDB records the value attributes of services – the measurable outcomes they enable.

Turning “What IT Does” into “Why It Matters”

These three repositories together form a Value-Aware Digital Ecosystem:

• AMDB answers “What do we own?”
• CMDB answers “How does it work?”
• VMDB answers “Why does it matter?”

Redefining Ownership Between IT and Business

The VMDB redefines ownership boundaries between IT and business.

• The CMDB remains under IT ownership, responsible for configuration accuracy.
• The VMDB, however, is co-owned: IT curates the data structures and automation; the business owns the value data.

Every service in the CMDB has a corresponding Value Owner in the VMDB – a business stakeholder accountable for defining, validating, and sustaining the service’s value contribution.

This co-ownership ensures that value becomes a shared responsibility, embedded into governance, not a vague post-project reflection.

How the VMDB Works – From Value Tokens to Realization

At its core, the VMDB operationalizes three concepts:

1. Value Tokens – Defined in the Value Register, these represent expected value outcomes (e.g., “reduce cycle time by 15%”).
2. Value Attributes – Derived from those tokens, stored within service configuration records in the VMDB.
3. Value Measurements – Actual realized outcomes collected from operational data and performance indicators.

This process forms a closed loop, aligning with the principle of Dynamic Value Continuity (DVC): value expectations are continually validated against realized outcomes, ensuring digital products and services remain aligned with evolving business goals.

Sample Data Model for Value-Enabled Services

Each CI in the CMDB (particularly services) gains additional value attributes such as:

Attribute	Description	Source
Expected Value	The quantified value promise (e.g., +10% satisfaction)	Value Register / User Story
Value Owner	The business role accountable for value realization	Business Function
Measurement Metric	The key performance indicator (KPI) used to track value realization	Value Register
Realized Value	The latest measured performance	Monitoring / Analytics
Variance	Difference between expected and realized value	Calculated
Status	(Planned / In progress / Realized / Sustained)	Governance process

By introducing these fields into CMDB-managed services, the VMDB turns the service catalog into a living value catalog.

A Real-World Example: Tracking Value Through User Stories

Consider a product team delivering a new feature through an Agile sprint, with the User Story:

“As a warehouse operator, I want real-time inventory updates so I can reduce order fulfillment time by 15%.”

Step 1: Create the Value Token

From the “so that…” statement, we extract a Value Token:

• Token ID: VT-001
• Description: “Reduce order fulfillment time by 15%”
• Measurement Metric: “Order Fulfillment Cycle Time”
• Expected Value: -15%
• Source: User Story US-421
• Linked Service: Inventory Management Service

This token is recorded in the Value Register.

Step 2: Create the Value Attribute

In the VMDB (an extension of the CMDB), the Inventory Management Service CI is updated:

• Expected Value Impact: -15% cycle time
• Value Owner: Supply Chain Manager
• Metric: Order Fulfillment Cycle Time
• Source Token: VT-001

Step 3: Capture the Realized Value

After deployment, monitoring data shows the average fulfillment time decreased by 12%.
The VMDB records:

• Realized Value Impact: -12%
• Variance: -3%
• Status: Partially Realized
• Last Update: 2025-12-04

Step 4: Aggregate Value

Over time, multiple value tokens link to the same service. The VMDB aggregates realized outcomes:

Inventory Management Service – Service Value Profile

• Expected Aggregate Value: -25% cycle time
• Realized: -22%
• Achievement Rate: 88%
• Key Value Indicators (KVIs): Cycle Time, Cost per Order, User Satisfaction
• Value Owner: Supply Chain Manager

This Service Value Profile provides actionable insight for continual improvement, directly connecting technical changes with business results.

Implementing a VMDB in Your ITSM Platform

The VMDB is not a new tool – it’s an enhancement of existing service management platforms.

For CMDB administrators using ITSM tools or platforms like ServiceNow or Jira Service Management, it can be implemented with minimal customization.

Extending ServiceNow for Value Management

Extend the cmdb_ci_service table with new fields: expected_value, realized_value, variance, value_owner.

• Create a related table u_value_measurements linked to services, allowing multiple timestamped value entries.
• Integrate data feeds from Performance Analytics or BI tools for automatic updates.
• Build reports and dashboards showing Value Realization Rates across services or portfolios.

Configuring VMDB in Jira Service Management (Assets/Insight)

• Define object types: Service, Value Token, and Value Measurement.
• Add attributes such as Expected Impact, Realized Impact, and Linked Metric.
• Automate data synchronization with Jira epics or user stories to extract “so that…” outcomes as Value Tokens.
• Create dashboards comparing expected vs. realized value per service or product area.

Integrating with the Value Register for Full Traceability

The Value Register remains the single source of truth for expected value.

Each Value Token carries a unique ID that can be linked from any CMDB/VMDB record. This creates full traceability:

• Value Register → VMDB → Operational Data → Value Reports

Governance and Value Accountability

The introduction of the VMDB requires clear governance.

Unlike the CMDB, which is owned by IT for operational accuracy, the VMDB introduces shared ownership between IT and business.

Roles, Responsibilities, and Ownership Matrix

Role	Responsibility
CMDB Administrator	Ensures data structure, accuracy, and integration of value fields
Value Owner	Defines and validates expected value; accountable for realization
Value Analyst	Monitors value data, identifies variances, and supports continual improvement
Service Owner	Aligns service delivery and improvement initiatives with value expectations

Joint Governance: Bridging IT Accuracy and Business Meaning

• IT governs structure and reliability. The VMDB must follow CMDB best practices for relationships, audits, and dependencies.
• Business governs content and interpretation. Value data must be validated by business stakeholders and reviewed in regular Value Review Meetings.
• Joint governance ensures evolution. As business value expectations evolve, VMDB attributes are updated – not just technical details.

This dual ownership model turns the VMDB into a living bridge between IT configuration and business value.

Conclusion – The Future of Value-Driven ITSM

The VMDB represents a critical step in the evolution of digital management practices.

By extending the CMDB beyond configuration accuracy into value accountability, organizations can finally connect the technical and business dimensions of digital transformation.

The VMDB:

• Links services and assets to measurable business outcomes
• Enables shared ownership of value between IT and business
• Provides a factual foundation for value discussions, benefit realization, and continual improvement.

In a world where digital services define competitive advantage, value has become the ultimate CI. The VMDB ensures that every service in your organization’s ecosystem not only runs, but matters.