ServiceNow ITOM, ITAM, CMDB, custom apps, AI and managed services.

Work / Field notes

What the work looks like, in practice.

Three notes on the kind of engagement each area takes on: the situation a team was in, the decisions that mattered, how the work was delivered, and what was different afterwards.

These are composites. Each describes a pattern seen across ServiceNow platforms rather than a single client, so no client is identified and no figures are claimed. Named client references are available on request where a client has agreed to be named.

Written by

Brandon Wilson

Founder & Chief Architect

ServiceNow Certified Technical Architect (CTA)

verify on Credly (opens in a new tab)

Case file 01

ITOM / Discovery and Event Management

A Discovery environment that ran every night and told nobody anything.

Discovery had run since go-live. Nobody on the operations side used what it produced.

Composite note. No client is identified; the details are typical of this kind of engagement rather than a record of one.

The situation

The schedules were the ones set up at go-live. Since then the network team had re-addressed two sites, credentials had rotated more than once, and a cloud account had been added without anyone telling the platform team. Two of four data centres had MID Servers; the other two were covered by a single MID Server across a slow link.

The Discovery error log held thousands of entries that nobody read, mostly credential failures and timeouts. The CMDB still showed servers retired years earlier as operational. Event Management had been switched on, so every one of those gaps also produced alerts, and the on-call engineer had learned to ignore the integration altogether.

The decisions

  1. D1

    Ownership before tuning.

    Before touching a schedule, we agreed who owned credentials, who owned IP ranges, and who would read the error log each week. Without that, the same drift would return within a quarter.

  2. D2

    Baseline against the real environment, not against Discovery.

    The network team's address plan and the cloud account inventory became the reference. Schedules were rebuilt from that list, with overlap and duration designed rather than inherited.

  3. D3

    Retire through lifecycle, not deletion.

    Servers Discovery had not seen for a long period moved to a retired operational status through a rule, so history and relationships survived and nobody had to argue about a bulk delete.

  4. D4

    Event rules tied to what is mapped.

    Alerts were kept only where a CI, a service and an owner existed. Everything else went to a review queue rather than to the on-call phone.

The delivery

A baseline first: coverage, errors, credentials, MID Server health and schedule design, measured against what the teams actually relied on. Then fixes in root-cause order: credentials and MID placement, then schedules and patterns, then the event rules.

Handover was a runbook for the platform team, a weekly check they could run in under an hour, and the ownership list written down where the next person would find it.

What changed

On-call could use the server list without a second source. Alert volume fell to the ones that had an owner and an action. The error log became a weekly task rather than a monument.

The platform team kept the environment in that state because the checks were theirs and the ownership was explicit.

Case file 02

CMDB / CSDM

Duplicates that came back every quarter.

Three cleanups in two years. Each time, the duplicate and orphaned CIs returned within months.

Composite note. No client is identified; the details are typical of this kind of engagement rather than a record of one.

The situation

The CMDB was fed by Discovery, by an endpoint management import, and by hand. The import had been written against the table directly, so every run that could not match a record created a new one. There were no identifier entries for the imported classes and no reconciliation rules, so Discovery overwrote ownership fields that people had filled in by hand.

CSDM had been adopted in name: tables had been renamed and a few business services created, but application services and business services were used interchangeably, so incident routing rules pointed at the wrong layer. A health dashboard existed, and its score was high, because the rules it checked were the ones that had been configured, not the ones that mattered.

The decisions

  1. D1

    Decide the sources before cleaning the data.

    For each class and each attribute we agreed which source was authoritative, and encoded that as reconciliation rules and data source precedence. Ownership fields were owned by people, and Discovery was no longer allowed to touch them.

  2. D2

    Identification before import.

    The import was rewritten to go through the Identification and Reconciliation Engine with identifier entries per class, so that a record either matched or was flagged, never silently created.

  3. D3

    CSDM in sequence.

    Foundation and the technical layer first, with application services modelled from what Discovery and Service Mapping could actually populate. Business services came later, once there was something real to attach them to.

  4. D4

    Cleanup last, and only once.

    With the rules in place, the existing duplicates and orphans were merged or retired through the engine, so the result would hold.

The delivery

A trust check first: where the duplicates came from, which rules were missing, what the dashboard was and was not measuring. A written fix list with owners followed, then the rule and import changes, then the one-time cleanup, then the dashboard tuned to the rules that had been decided.

What changed

The duplicates stopped recurring because the thing that created them no longer existed. Incident routing used application services with named owners. When an auditor asked which data source a CI attribute came from, the platform team could answer from the record.

Case file 03

Custom applications

The process that lived in a shared mailbox.

A compliance review process ran on a spreadsheet, a shared mailbox and one person's memory. The team wanted an app.

Composite note. No client is identified; the details are typical of this kind of engagement rather than a record of one.

The situation

Requests arrived by email, were logged in a spreadsheet, and were reviewed in a sequence that depended on who was available. Evidence was attached to emails. Nobody could say how many reviews were open or which were overdue without asking the one person who ran it.

A catalog item had been built once, but approvals and evidence still happened outside the platform, so it was abandoned. The team's request was for a custom application; what they needed was a decision about where the process should live.

The decisions

  1. D1

    Boundary first.

    The scoping session drew the line between intake, review and record-keeping. Intake belonged in the Service Catalog, because it already handled requesters, approvals and notifications. The review record, with its own lifecycle, evidence and roles, had no home on the platform and justified a scoped application.

  2. D2

    Do not extend Task for the review record.

    The review was not work assigned to a queue; it was an entity with a history. A scoped table with its own states kept it out of the global task model and out of the way of upgrades.

  3. D3

    Flows at the edges.

    Approvals and notifications ran in Flow Designer; the feed from the HR system came through Integration Hub rather than a custom script. Evidence was attached to the record, not to email.

  4. D4

    Ownership after go-live.

    The platform team owned the application, with a named person on the business side owning the process. That was agreed before build, not at handover.

The delivery

The scoping session produced a process boundary, a data model, roles, the integration list and an estimate. The build ran in short increments with automated tests on the state model, and handover included the documentation the platform team asked for rather than the documentation the build produced by default.

What changed

The process became visible: open reviews, overdue reviews and evidence were on one record with an audit trail. The person who had carried it in their head could take leave. The platform team could change the flow without calling anyone.

Recognize one of these?

Tell us the symptom. Each area starts with a fixed-scope engagement, so the first step is easy to approve.

Discuss your project We reply within 24 hours on business days.