VerOps ITAM — overview

What VerOps ITAM is

VerOps IT Asset Management turns what your agents already observe into a defensible asset position: what you own, who uses it, what it costs, what it is worth, whether it is licensed, and whether it is patched. It is not a separate product bolted onto the platform — it reads the same governed estate that VerOps Scout and the Machine Agent inventory module feed, and it surfaces through the same dashboards, alerts and reports as the rest of VerOps.

The chain, end to end

Stage	What happens	Sources
1. Collect	Agents report hardware, installed software, running usage, logged-in users, network facts and OS update posture	VerOps Scout (workstations) · Machine Agent inventory module (servers) · MDM ingest (tablets) · CSV / API import for assets no agent can reach
2. Resolve	Executables and packages normalize into the products humans reason about; usernames resolve to real people; assets get an identity that survives renames and re-images	Normalization & matching rules · Directory enrichment
3. Analyse	Consumption is measured against entitlements, cost against depreciation, update state against thresholds	Licenses & compliance · Financials · Patch posture
4. Act	Status pills and KPI tiles in Inventory, charts on dashboards, violations through the existing alerting engine, and audit packs on a schedule	Inventory surfaces · Dashboards · Alerts · Reports & exports

The questions it answers

What do we have? Every asset an agent can see, plus everything it cannot — printers, switches, spare stock — imported from your spreadsheet of record. See Assets and lifecycle.
Who is using it? Historical user↔device associations, the current user, and — with directory enrichment — the actual person, department and manager behind CORP\jsmith. See Users and devices.
Where is it? Office or remote, inferred from the networks the device is on. See Presence.
Are we licensed? Entitlements versus measured consumption, a compliance position per license, and a true-up with cost-to-cure. See Licenses and compliance.
What is it worth? Purchase cost, warranty state and straight-line book value. See Asset financials.
Is it a risk? Which machines are behind on OS updates, bucketed and alertable. See Patch posture.
Can I prove it? Six report types on a daily, weekly or monthly schedule, as CSV or PDF. See Reports and exports.

Two design rules worth knowing

Two principles run through every ITAM surface, and they explain a lot of the product's behaviour:

One source of truth per question. Book value, license consumption, the posture bucket and every report section are each computed in exactly one place. A scheduled report and the on-screen table it mirrors cannot disagree, because they call the same code.
Never guess silently. An ambiguous import match becomes an error row, not a merge. An unmeasured host reads unknown, not current. An ambiguous username goes to a review queue, not an automatic link. Where VerOps cannot be sure, it says so and asks you.

Where it lives

Everything described in this category is under Inventory in the VerOps app — the Overview, Hosts, Software, Products, Licenses, Agents, Policy, Violations, Review and Reports tabs — plus the asset detail page reached by clicking any host.

Note: Inventory and ITAM are gated by the operator inventory feature, and every surface is permission-checked: reading requires inventory.view, and every change — entitlements, financials, imports, thresholds, catalogs, report definitions, directory configuration — requires inventory.manage. Where the feature is not enabled, none of these surfaces appear.