Perpetual – Discovery implementation at scale
Overview
Delivered a multi-phase ServiceNow Discovery and CMDB uplift engagement to improve infrastructure visibility, increase CMDB trust, and create a stronger foundation for service modelling and governance. The work combined current state review, phased improvement planning, and practical design decisions around coverage, security alignment, and data quality from day one.
Platform: ServiceNow · Focus: Discovery + CMDB trust · Engagement: Multi-phase delivery
The situation
The client needed a more reliable and scalable Discovery capability across a mixed environment including servers, endpoints, network and security devices, certificates, databases, and cloud. Existing CMDB records included duplicates, inconsistent entries, and trust issues that limited broader use. Security approvals were also essential for credential and access approaches. The work required not just technical setup, but a practical path to improve quality, confidence, and operational ownership over time.
What I delivered
- Current state review of Discovery and CMDB quality issues to identify priority gaps and uplift focus areas
- End-to-end Discovery setup (MID Servers, credentials approach, schedules, and coverage model)
- Pattern configuration and tuning to improve identification and enrichment
- Data reconciliation and deduplication approach to lift CMDB quality
- Custom discovery extensions for devices and platforms not covered cleanly out of the box
Approach
- Established an initial baseline of Discovery coverage, CMDB trust issues, and practical constraints
- Used a phased rollout to build confidence, reduce risk, and prioritise the highest value coverage first
- Engaged security stakeholders early to align access methods, protocols, and approval paths
- Applied iterative validation through sample sets, reconciliation checks, and trust gates before scaling
- Structured the handover so Discovery could operate as a sustainable BAU capability rather than remain consultant dependent
Outcomes
- Improved Discovery coverage across core infrastructure domains (servers, network/security, certificates, databases, cloud)
- Improved identification and enrichment accuracy through tuned patterns and targeted custom extensions
- Reduced duplicate records and improved CMDB consistency through reconciliation and deduplication controls
- Established a scalable, BAU ready operating approach with clearer ownership, validation rhythm, trust gates, and a stronger base for future CMDB and service modelling uplift
Key decisions and design choices
- Prioritised data quality and dedupe before “maximum coverage”
- Built custom pattern capability where out-of-box identification was insufficient
- Designed Discovery as an operating capability (ownership, rhythm, and controls), not a one-off project
What this enabled next
- A more reliable baseline for future service mapping, relationship modelling, and broader CMDB maturity work
- Better incident and change context through more trustworthy CI data
- Improved readiness for lifecycle governance, CSDM aligned practices, and phased follow on uplift planning
Tools and capabilities
ServiceNow Discovery, MID Servers, credential strategy, pattern tuning, custom pattern extensions, and CMDB quality controls.
If you’re tackling something similar
If Discovery results are inconsistent, slow, or untrusted, I can help you establish a scalable approach (coverage model, security alignment, patterns, and quality controls) that your team can run confidently. Send me a note and I’ll suggest the fastest path based on your current setup.