Introduction: The Practitioner’s Perspective on Data Debt
Recently, the Technology Business Management (TBM) Council hosted a highly engaging open forum titled “From Wild to Wrangled: Lassoing TBM adoption with CMDB data”. Featuring candid, real-world insights from Justin Graff, Director of IT at Bone & Joint Clinic, and Paul Kranz, a ServiceNow Strategy and Architecture Consultant, the session explored the critical—and frequently chaotic—intersection of Configuration Management Databases (CMDB) and TBM adoption.
Their conversation focused heavily on data, which serves as a foundational element of the TBM Framework. By combining the speakers’ frontline experiences with the structural guidance of the TBM Council, this article provides a comprehensive guide for TBM Practice Leads and Administrators seeking to change how decisions are made by bringing their CMDB under control.
The Linchpin and the “Wild West” of IT Finance
During the forum, Justin Graff identified the CMDB as the absolute “linchpin” of any mature TBM practice. It represents the core component required to understand how raw technology infrastructure equates to financial investments and, ultimately, to the services delivered to end-users.
However, attempting to build a TBM cost model without a reliable CMDB leaves organizations navigating what Graff aptly described as the “Wild West” of IT financial management. When configuration item (CI) data is missing or unmanaged, cost allocation quickly devolves into a guessing game. Without accurate data linking infrastructure to specific applications or services, IT finance teams are forced to rely on inaccurate allocation methods—such as spreading costs evenly across departments or allocating purely by headcount. As Graff noted, when business leaders ask what a service costs and IT responds with a headcount-based guess, the organization is missing the point of financial visibility.
To tame this frontier, Paul Kranz advises organizations to measure CMDB health rigorously using the “Three Cs“: Completeness, Compliance, and Correctness. Completeness ensures that all expected CIs and their critical attributes exist within the database. Compliance confirms that the required, business-ready fields—such as departmental ownership and cost roll-up tags—are accurately populated. Finally, correctness verifies that the data perfectly mirrors the live, operational environment. Establishing and monitoring these three parameters creates the structural Transparency needed to stop guessing and start tracking actual total cost of ownership (TCO) across the enterprise.
Overcoming Analysis Paralysis to Build a Virtuous Cycle
A recurring theme throughout the conversation between Graff and Kranz was the cultural hurdle of “analysis paralysis”. Organizations frequently stall their TBM implementations because they believe their CMDB is too messy, choosing instead to wait for their data to reach a state of perfection before tying it to financial models.
Kranz emphasized that waiting for perfection means you will be waiting forever. Graff emphatically echoed this sentiment, stating plainly that “there’s never perfect data,” and the only true way to make data reliable is to start using it immediately. Using flawed data is not a liability; it is the catalyst for continuous improvement. As highlighted by audience member Nan Braun during the forum, when CMDB owners see their data tied to dollars, “suddenly there’s a lot more impetus for people to take action and clean up the data”.
To operationalize this cultural shift and overcome initial resistance, the TBM Council recommends a proven five-step workflow for breaking through data debt:
- Get directional insight: Start with the data you have to point to directional insight, even if it is incomplete.
- Present to leadership: Take these initial findings and present them to executives, appropriately caveated to manage expectations.
- Let stakeholders call out missing data: When various stakeholders see the potential—and the inaccuracies—they will naturally identify what is missing, creating accountability for data quality.
- Use the momentum: Leverage this newfound visibility and executive desire for accuracy to gain access to the data you need.
- Rinse and repeat: Continue the cycle with increased precision until a complete version is achieved.
Treating data improvement as an agile sprint rather than a waterfall project generates immediate, directional Insights that leaders can act on to prioritize investments and optimize resources.
The Mechanics of Integration: Linkage, Structure, and Strategy Moving beyond cultural hesitation requires a firm grasp of the mechanical integration between CMDB records and the TBM cost model. At a practical level, integration depends on three core elements: financial linkage (join keys), a structural model (CSDM tables), and a mapping strategy (tagging and hierarchy).
- Financial Linkage (Join Keys): Graff pinpointed “join keys” as the essential elements that marry IT configuration items to financial general ledger data. Attributes such as vendor and manufacturer data serve as the vital links for mapping hardware and software maintenance, while asset tags and serial numbers allow an organization’s fixed asset registry to connect seamlessly to operational CIs. Cost centers are equally critical, identifying exactly who owns and consumes the assets.
- Structural Model (CSDM Tables): To structurally manage these relationships at scale, organizations frequently leverage the ServiceNow Common Service Data Model (CSDM). Understanding the distinction between different ServiceNow record types is vital for this mapping. For instance, a Business Application (cmdb_ci_business_app) is a logical, non-operational listing of an application, whereas an Application (cmdb_ci_appl) represents the actual deployed instance of the software installed on a specific server. TBM models primarily query the Business Application table to represent the application portfolio, while querying the CMDB’s relationship tables to identify the underpinning infrastructure assets.
- Mapping Strategy (Tagging and Hierarchy): When mapping these records into a TBM framework, practitioners must approach the alignment strategically. The TBM Solutions layer is primarily designed as an out-of-the-box framework for organizations that either do not have an existing service catalog or have one in such a degraded state that they need to rebuild it from scratch. Organizations that already possess a healthy, highly functional service catalog do not need to force a mapping exercise into the standard TBM Solutions layer. Furthermore, practitioners should note that the current published guidance for ServiceNow CSDM integration relies on the older v4.x TBM Taxonomy and does not natively reflect the updated structures of the TBM Taxonomy v5.0.1.
To keep this mapping sustainable, Kranz stressed that 90% or more of CMDB data should be curated through automated discovery tools, ensuring data remains fresh without requiring constant manual intervention. Furthermore, Kranz championed tag-based mapping, mandating that every new piece of infrastructure be tagged with its associated business application and environment upon creation.
Enforcing Governance, Federated Ownership, and Managing Fallout Even with automated discovery and tag-based mapping, organizations must implement robust governance. Kranz offered a critical warning: if relationship creation within the CMDB is not strictly governed, the database will inevitably degrade into a “spaghetti plate of relationships” where the data becomes entirely useless for accurate financial allocation.
To prevent this sprawling chaos, Graff recommended instituting rigid, standardized service request processes. By utilizing a governed server request catalog item that automatically captures the required CPU, memory, cost center, and application relationships at the exact moment of infrastructure deployment, the data effectively manages itself.
Graff further emphasized that successfully maintaining this ecosystem requires a shared governance model. The TBM Council formally defines this concept as establishing clear, federated data ownership. Because no single team can effectively maintain all enterprise data, accountability must be distributed to the teams closest to the information. Best practices dictate that IT Operations must own the CMDB, Enterprise Architecture must own Application Portfolios, and Procurement must own Vendor Contracts.
When inevitable data gaps or unmapped costs—known in TBM as “fallout”—do occur, organizations must operationalize Kranz’s “Compliance” standard (ensuring data has the required fields to be business-ready). Fallout is a standard operational reality that must be continuously monitored. To sustainably manage this, the TBM Council recommends adding actionable metadata tracking directly to mapping tables. Whenever a data gap is resolved, data stewards should consistently log specific fields, including mapping_method (e.g., Manual, Keyword, Tag), mapping_confidence (High, Medium, Low), and data_source (e.g., CMDB, Cloud Billing).
This rigorous metadata tracking guarantees that data resolutions are transparent and auditable for future cycles, ultimately driving continuous Optimization of the cost model by revealing exactly where mapping rules can be automated or improved over time.
Conclusion: Delivering the Speed of Value Bringing CMDB data under control and successfully lassoing it to a TBM framework changes how decisions are made. As the open forum speakers concluded, the ultimate measure of success for this integration is the speed and quality of enterprise decision-making.
Graff painted a vivid picture of what this success looks like in everyday practice: instead of IT and Finance teams taking weeks to manually pull spreadsheets and numbers together, leaders sitting in high-stakes budget meetings can instantly pull up a reliable cost model. Armed with accurate data that is available to the quarter or even to the hour, executives can make on-the-spot choices regarding service costs, portfolio optimization, and future deployments.
By acknowledging that perfect data is an illusion, embracing automated discovery tools, structuring mapping through the CSDM, and enforcing strict federated ownership, TBM Practice Leads can turn their CMDB from an untrusted inventory into a reliable engine for business value. Ultimately, wrangling the CMDB removes manual reporting cycles and replaces them with a real-time, auditable source of truth that powers faster, smarter business behavior.
