enterprise platforms · it service and operations management
A CMDB that change approvers and incident responders actually trust.
The ServiceNow instance went live years ago. Since then the CMDB has drifted, Discovery covers part of the estate, events flood the queue and every family upgrade gets pushed back. We fix the data first, then the processes and automation that depend on it.
MID Serverscredentials · schedulesDiscovery and Service MappingCIs · relationshipsEvent Managementrules · correlation
03 · CMDB
CMDBclasses · owners · services
04 · ITSM
Incidentservice impactChangerisk · approvals
ServiceNowTerraformOktaMicrosoft Entra ID
in short·20-second read
This is the work of running IT itself, incidents, changes and requests and the infrastructure underneath, which mostly happens on ServiceNow ITSM and ITOM.
Cohash configures the incident, change and request processes. We build a CMDB that Discovery and Service Mapping actually keep current, and tune Event Management so alerts turn into incidents worth opening. Instance upgrades to current families and certified ServiceNow staff are part of it too.
you probably need this if
Change approvers ignore the impact analysis because the CMDB is wrong.
Discovery runs, but large parts of the network and cloud estate never show up.
Monitoring fires thousands of alerts a day, and operations has quietly muted most of them.
From the first call to a setup your own team can run.
Here's what usually prompts a call about your IT Service & Operations Management, what we do about it and in which order, and where you end up.
01 · where it hurts02 · what we change03 · how it runs04 · where you end up
incident board · it service & operations management3 open
openChange approvers ignore the impact analysis because the CMDB is wrong.
recurringDiscovery runs, but large parts of the network and cloud estate never show up.
blockedMonitoring fires thousands of alerts a day, and operations has quietly muted most of them.
exposure
CMDB repair and data modelDiscovery and Service MappingEvent Management and alert noiseITSM process configurationFamily upgradesCertified ServiceNow staffing
startrehearsehandover
Instance health review
Data first
Build and tune
Run and hand over
we are here
ready to hand over
Change impact lists only the services that really depend on the server.
A storage issue now opens one incident against the affected service, not hundreds of…
Instance health report with customization and skipped-record counts
CMDB class model and identification rule design
chapter 01 · where it hurts
Why teams reach out
Change approvers ignore the impact analysis because the CMDB is wrong.
Discovery runs, but large parts of the network and cloud estate never show up.
Monitoring fires thousands of alerts a day, and operations has quietly muted most of them.
chapter 02 · what we change
How we solve it
CMDB repair and data model
Discovery and Service Mapping
Event Management and alert noise
ITSM process configuration
Family upgrades
Certified ServiceNow staffing
chapter 03 · how it runs
Our approach
Instance health review
Data first
Build and tune
Run and hand over
chapter 04 · where you end up
What changes
Change impact lists only the services that really depend on the server.
A storage issue now opens one incident against the affected service, not hundreds of alerts.
Instance health report with customization and skipped-record counts
CMDB class model and identification rule design
what we do
Where we spend the hours
6 areas of work, each one done by an engineer who has run it in production.
Impact analysis is only as good as the CMDB under it. We clean up the class model, write identification rules, remove duplicates and give every CI class an owner, so change and incident impact land on the right service and team.
MID Server placement, credentials and schedules for ServiceNow Discovery across data centers and cloud accounts, then Service Mapping for the business services that change approvers ask about most.
Monitoring tool integrations into Event Management, with alert rules and correlation tuned so a storage failure opens one incident against the right service instead of hundreds of alerts.
We keep incident, problem, change and request near base. Change risk comes from CMDB data, so nobody types a free-text guess about impact.
Upgrade to a current ServiceNow family. Review the skipped records. Build automated test framework coverage. Keep customizations small so the next upgrade stays routine.
ServiceNow developers, ITOM engineers, CMDB data managers and platform admins on contract, contract-to-hire or permanent terms, onsite, nearshore or offshore.
capability 01 / 06in production
CMDB repair and data model
Impact analysis is only as good as the CMDB under it. We clean up the class model, write identification rules, remove duplicates and give every CI class an owner, so change and incident impact land on the right service and team.
MID Server placement, credentials and schedules for ServiceNow Discovery across data centers and cloud accounts, then Service Mapping for the business services that change approvers ask about most.
Monitoring tool integrations into Event Management, with alert rules and correlation tuned so a storage failure opens one incident against the right service instead of hundreds of alerts.
Upgrade to a current ServiceNow family. Review the skipped records. Build automated test framework coverage. Keep customizations small so the next upgrade stays routine.
ServiceNow developers, ITOM engineers, CMDB data managers and platform admins on contract, contract-to-hire or permanent terms, onsite, nearshore or offshore.
We pieced these together from IT Service & Operations Management situations that come up a lot. They're patterns. You won't find a specific client in them.
case file 01
Change approvals built on a CMDB full of duplicate servers
composite · not a client story
Beforethe situation
Discovery, a spreadsheet import and an asset tool all load servers into the CMDB. Many servers appear more than once. Change impact lists the wrong services, so approvers have stopped looking at it.
What we dothe work
Count duplicates by source. Write identification rules so one source wins for each attribute. Merge or retire the duplicates in batches. Then give each CI class a named owner who reviews its health once a month.
Afterwhere you end up
Change impact lists only the services that really depend on the server. Run another import and the duplicates don't come back.
case file 02
Operations muting alert sources after thousands of alerts a day
composite · not a client story
Beforethe situation
Every monitoring tool sends raw alerts straight into Event Management with no correlation. One storage issue can produce hundreds of alerts, and operations has muted entire sources.
What we dothe work
Sort the alerts by source and frequency, then write rules that drop the informational noise. What's left gets correlated to CIs and mapped services. An incident only opens when a service is actually hurt.
Afterwhere you end up
A storage issue now opens one incident against the affected service, not hundreds of alerts. The muted sources can be turned back on.
Discovery and Service Mapping populate the CMDB from infrastructure and cloud accounts through MID Servers. Monitoring alerts are correlated in Event Management, which opens incidents against mapped services, and change requests use the same CMDB for impact and risk.
MID Servers → Discovery and Service Mapping: results
Discovery and Service Mapping → CMDB: CIs and maps
Monitoring tools → Event Management: alerts
Event Management → Incident: incidents
CMDB → Incident: impacted service
CMDB → Change: impact analysis
how it runs
A typical engagement
We don't start a step until the last one has produced something you can check.
step 01
Instance health review
Measure it all on your instance. Customizations and skipped records from past upgrades. How complete the CMDB is and how many duplicates it holds. Discovery coverage and alert volumes.
step 02
Data first
Fix the CI classes and relationships that change and incident processes depend on before adding new automation.
step 03
Build and tune
Discovery, Service Mapping, Event Management and ITSM changes delivered in releases with test coverage.
step 04
Run and hand over
CMDB health dashboards, data owner routines and runbooks for the platform team.
you keep
What you're left with
We write these for your IT Service & Operations Management setup, and they're working documents. Your team should be able to keep things running from them long after we've gone.
report01
Instance health report with customization and skipped-record counts
yours to keep
design02
CMDB class model and identification rule design
yours to keep
plan03
Discovery schedule, credential and MID Server plan
yours to keep
document04
Service maps for priority business services
yours to keep
document05
Event rules and correlation settings with before-and-after alert volumes
talent and delivery · it service & operations management
Certified engineers, wherever you need them.
Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.
Onsite
Engineers at your sites in the US
Nearshore
Overlapping hours with US teams
Offshore
Overnight progress on your backlog
All time zones
Coverage handed over across time zones
24-hour coverage · US Central time
OnsiteUS business hours
Nearshoreoverlapping US hours
Offshoreovernight progress
Combinedhandover, not hand-off
00:0006:0012:0018:0000:00
roles we staff
ServiceNow ITOM engineer (Discovery, Service Mapping)
ServiceNow CMDB data manager
ServiceNow ITSM developer
ServiceNow platform administrator
Event Management integration engineer
ServiceNow upgrade lead
due diligence · it service & operations management
Questions to ask any partner, including us.
Put these to anyone bidding on your IT Service & Operations Management work. The ones who've done it answer differently from the ones who've read about it.
Q1
How will you measure our CMDB's health before proposing fixes?
Completeness, duplicates, stale CIs and ownership gaps decide the work. Ask for numbers from your instance, not a generic maturity model.
Q2
What will Discovery need from our network and security teams?
MID Server placement, firewall rules and credentials usually take longer than configuration. A good plan names those requests in week one.
Q3
How many skipped records from past upgrades are still unresolved?
Unreviewed skipped records hide behavior differences that show up after the next upgrade. The answer shows how much upgrade debt you carry.
Q4
Who will own each CI class after you leave?
CMDBs decay without owners. The engagement should end with named data owners and a routine. Clean data alone decays again.
Q5
How will you test the upgrade, and what is automated?
Manual testing is the usual reason upgrades are postponed. Ask what coverage the automated test framework will have before the next family.
01Which ServiceNow families are current?
ServiceNow's patching program for Q4 2026 lists Australia, Zurich and Yokohama, with Australia patches still shipping in October 2026. Check the available versions page for your exact family and patch status before planning an upgrade.
02Why does our CMDB keep getting worse?
Usually several sources write to it with no consistent identification rules, individual CI classes have no owner, and Discovery only sees part of the estate. The fix is mostly about who owns the data and what the rules are. Buying another tool rarely helps.
03How long does an ITOM rollout take?
It depends on how many networks and cloud accounts Discovery has to reach, how quickly firewall rules and credentials get approved, and how many services you want mapped. Access approvals often take longer than the configuration.
04Should we customize or stay close to base?
Keep it near base where you can. Every customization adds review work to every family upgrade, so we document the ones worth keeping and why they exist.
05Do you also do ServiceNow automation and HR or security workflows?
Yes. Our intelligent automation and workflow automation pages cover automation on ServiceNow, and we work on identity integrations with the platform.
06Can you provide ServiceNow ITOM engineers on contract?
Yes, and ITOM is one of the harder ServiceNow skills to hire. We place ITOM, CMDB and platform engineers through our staffing practice, on contract, contract-to-hire or permanent terms.
related
Often paired with
Projects on IT Service & Operations Management usually end up touching one of these, so they're worth a look.
