Perpetual – Service Mapping and CSDM lifecycle alignment

Overview

Delivered a large-scale CMDB uplift to support reliable service visibility: aligned lifecycle status to CSDM standards, strengthened CI↔Asset consistency, and introduced practical governance controls. Implemented Azure tag-based service mapping and DPM configuration to improve infra-to-app relationship clarity and service oversight.

Platform: ServiceNow · Focus: CSDM lifecycle alignment + Service Mapping · Engagement: Large-scale remediation + controls uplift

The situation

The organisation needed clearer visibility of which infrastructure underpinned which services and applications to support a business separation (sale of a portion of the company). Existing CMDB lifecycle values had drifted into custom/invalid combinations, and relationships between infrastructure and applications weren’t reliable enough for impact analysis and service mapping. The work needed a controlled approach that improved trust without breaking dependent scripts, workflows, integrations, and reporting.

What I delivered

  • Implemented Azure tag-based service mapping to establish reliable infra-to-application relationships
  • Configured Digital Portfolio Management (DPM) to improve service instance and business application oversight
  • Large-scale remapping of lifecycle status fields to align with CSDM lifecycle standards
  • Review and update of dependent logic (scripts, workflows, policies, mappings) to prevent regressions
  • CI↔Asset lifecycle mapping and synchronisation during cutover to ensure consistency

Approach

  • Data profiling first: identify invalid combinations and high-risk areas
  • Controlled mapping approach with validation checks and stakeholder sign-off
  • “Don’t break production” discipline: update downstream logic and integrations before cutover
  • Governance introduced as practical BAU controls, not heavy bureaucracy

Outcomes

  • Consistent lifecycle handling across applications, infrastructure and assets
  • Improved CMDB integrity and reduced future lifecycle drift
  • Improved service-to-infrastructure visibility to support separation planning and impact analysis
  • Better portfolio-level views of services/applications for governance and prioritisation

Key decisions and design choices

  • Standardised to out-of-box lifecycle values to reduce long-term maintenance burden
  • Treated lifecycle as a system-wide behaviour (CMDB + Asset + automation), not just field changes
  • Used tag-based mapping where automation could reduce manual relationship upkeep

What this enabled next

  • Improved impact analysis readiness through more reliable relationships
  • Strong foundation for “trusted” CMDB usage across ITSM processes
  • Better structure for ongoing governance, ownership, and quality control

Tools and capabilities

ServiceNow CMDB + CSDM lifecycle standards, lifecycle mapping, data quality controls, Azure tag-based mapping, and Digital Portfolio Management configuration.

If you’re tackling something similar

If lifecycle fields are messy, reporting is unreliable, or CMDB governance feels hard to sustain, I can help you realign lifecycle standards and implement controls that keep data trustworthy without slowing delivery.

Start the conversation

Scroll to Top