Skip to content
Dispatching · New York Metro
(347) 262-9435
Field guide · Field operations

Asset tagging

What a field technician actually owes an asset database, and why most of what goes wrong is not the tagging. Covers the difference between an asset record and a configuration item — the distinction ServiceNow builds on and the one most site work gets wrong — what to capture at the desk, how to run a floor audit that produces a usable reconciliation, and what to do about the machines that are on the floor and in no system at all.

Plate 01Procedure

Doing it

What a technician owes the database, in the order the floor walk happens — and the handover that makes the audit worth what it cost.

Tools
  • Barcode or QR scanner, or a phone with the client's app
  • Label printer
  • Torch
Materials
  • Asset labels in the client's own scheme
  • Isopropyl wipes for surface prep
  1. 01

    Find out which system you are feeding, and which record

    In ServiceNow the asset record and the configuration item are two different things pointing at the same physical box — the asset is the financial and lifecycle view, the CI is the operational one. They are related, not identical, and a tech updating one when the client meant the other creates a reconciliation problem rather than solving one. Ask which, and ask for a worked example before you touch a hundred machines.

    CautionNever create new records on a live CMDB unless you have been asked to. Duplicate CIs are far more expensive to unpick than missing ones.

  2. 02

    Agree the capture set before the first desk

    Serial number, asset tag, model, location to whatever granularity the client uses, and assigned user. Anything beyond that is negotiable and anything short of it is a return visit. Confirm how location is expressed — building, floor, and a desk or grid reference — because a floor audit recorded to the wrong granularity is not usable.

  3. 03

    Put the tag where it can be read without moving the machine

    Consistent position on each model, flat surface, wiped clean first, and never over a vent, a label the manufacturer needs, or a screw somebody will have to remove. A tag on the underside of a desktop means the next audit involves crawling under two hundred desks.

    CautionDo not tag over the manufacturer's own serial label. The day the machine goes to warranty, that label is what the vendor asks for.

  4. 04

    Scan the serial rather than typing it

    Transcription is where audit data goes wrong, and it goes wrong invisibly — a serial with an O for a zero looks correct and matches nothing. Scan the manufacturer barcode wherever one exists, and photograph the label where it does not.

  5. 05

    Walk the floor systematically, not opportunistically

    Take the floor in a fixed order and record every seat, including empty ones. An audit that covers the desks somebody pointed you at is a sample, not an audit, and it produces a reconciliation nobody can act on because they cannot tell absence from omission.

  6. 06

    Record what does not fit

    The machine with no tag, the tag with no machine, the device in a drawer, the monitor with a tag belonging to a different site. These exceptions are the entire value of the audit — a list confirming what everybody already believed is worth very little.

  7. 07

    Hand back a reconciliation, not a spreadsheet

    Three lists: found and matching, found and different, expected and not found. That is what lets somebody decide what to do. A raw export of what you scanned puts the comparison work back on the client, which is the work they were paying to have done.

Plate 02Questions
Questions people actually ask
What is the difference between an asset and a configuration item?
An asset is the commercial and lifecycle view of a thing — what it cost, who owns it, when it was bought, when it is due for replacement. A configuration item is the operational view — what it is, what it connects to, what depends on it. ServiceNow keeps both and relates them, and one physical laptop is represented in each. Which one you are updating changes what your data is for, so establish it before the first scan.
Where should an asset tag go?
Somewhere readable without moving or opening the machine, in the same place on every unit of the same model, on a flat surface that has been wiped first. Not over vents, not over the manufacturer's serial label, not on a removable panel. The test is whether the next person can audit the floor standing up.
The CMDB is wrong about half the floor. Do I fix it?
Report it, do not silently correct it. A field technician bulk-editing a live CMDB is how one bad assumption propagates into the system everybody else trusts. Deliver the discrepancy list and let the person who owns the data decide — that is exactly what the audit was for.
What about a machine that is not in the system at all?
Record it as found-unknown with everything you can capture — serial, model, location, who is sitting at it — and photograph the label. Untracked hardware is the single most useful thing an audit surfaces, because it is the category nobody could have queried for.
Do we need a scanner, or is a phone enough?
A phone with the client's own app is usually fine and often preferred, because it writes straight into their system rather than into an intermediate spreadsheet somebody has to import. A dedicated scanner earns its place on high-volume audits where battery life and speed start to matter.
Plate Other guides

The rest of the section

Free guidesNo sign-upNothing trackedWritten on the job
Rather it was just done

We do this work
as well as document it

Anyone tagging hardware for a client who runs ServiceNow or a similar CMDB, and anyone asked to audit a floor and report what is actually on it.

Or call and speak to someone who does the work(347) 262-9435inquiries@jcitsystems.com