“What do we own, what do we use, and what renews next?”
Every part of ISO/IEC 19770-1 — the ITAM system, trustworthy asset data and the asset lifecycle — across hardware, software, SaaS, cloud and AI, mapped to where it lives in Dotwork. Contracts, purchase orders, renewals and depreciation sit on the same model as the applications, capabilities, teams and budgets they serve, so a renewal decision sees the commitment, the owner, the end-of-support date and the roadmap at once. Keep the discovery and license tools you run; Dotwork connects what they find to the money and the decisions. Set your own asset classes and depreciation rules; when ISO revises the standard, your records move only where you approve. And TBM, FinOps and app rationalization read the same contracts and costs.
Runs in
Covers
ISO/IEC 19770 · licenses, contracts and renewals
The pressure
Discovery tools count installs. SaaS tools count logins. Contracts sit with procurement, depreciation in the fixed-asset system and end-of-support dates in an architect’s spreadsheet. Each knows part of the asset; none knows what it costs, who owns it, what depends on it or whether the business still needs it. So renewals go through at last year’s terms and audits arrive as surprises.
What it looks like today
Full coverage
Each clause of the standard and each asset class maps to where it is managed — next to the money, the architecture and the plan.
Aligned to ISO/IEC 19770-1:2017
The management-system clauses of ISO/IEC 19770-1.
An asset record people can rely on.
From the request to retirement.
Contracts, licenses and subscriptions.
Everything else the business runs on.
Where ITAM changes what happens next.
What changes
An inventory with no price
Every asset with its contract, its cost and its owner
Renewals tracked by expiry date
Renewals tracked by notice date, with end of support and the roadmap beside them
Asset data spread across four systems
Discovery, contracts, the ledger and the architecture on one model
ITAM as audit defense
ITAM as an input to budgets, rationalization and the roadmap
Decide before the notice date
Software, SaaS, hardware support and cloud agreements are tracked against the date you must give notice, not the date they expire. Each carries its owner, the annual commitment riding on the decision and how much has already been drawn — with the applications it serves and their end-of-support dates on the same model. Renew, renegotiate or exit while there is still leverage.
Where other tools stop
Asset tools count what is installed. SaaS tools count who logs in. Neither knows what the contract is for, what the roadmap will do to it or what it does to the budget.
Flexed to how you run
ISO/IEC 19770-1 says what an ITAM system must achieve, not how to run it. Start from the data you trust, keep the tools you have and set your own classes and rules.
Begin where the data is good
Begin with contracts and renewals, or with the hardware register, and add software, SaaS and cloud as the data arrives.
Keep your discovery tools
Discovery, license and SaaS management tools keep doing what they do. Dotwork connects their results to the money and the decisions.
Your asset classes and names
Define the classes, lifecycles and owners your company uses, with ISO/IEC 19770 underneath.
Your depreciation rules
Straight-line, declining balance or manual schedules by asset class, set by finance.
Edition to edition
ISO/IEC 19770-1 was rewritten in 2017 as a management-system standard, and ISO/IEC TS 19770-10:2025 added guidance for putting it into practice. When the standard is revised again, the new edition is laid against your classes, processes and objectives, and each move waits for the ITAM owner’s approval. Past periods keep the structure they were reported under.
Scope widened from software asset management to all IT assets
Hardware, software, SaaS, cloud and AI on one register
Rewritten in the common ISO management-system structure
Each clause mapped to the owners, policies, objectives and reviews already on the model
The four tiers moved from the body of the standard to an annex
Tiers kept as a maturity view, scored from your own records
Prescriptive process lists replaced by outcomes to achieve
Your processes, named your way, mapped to the outcomes they serve
Implementation guidance added in ISO/IEC TS 19770-10:2025
Adopt in increments — trustworthy data first, then lifecycle and cost
Every framework, one model
Asset data feeds cost, cloud, architecture and security — usually by export. Here each framework reads the asset where it lives, so its cost and its risk never drift apart.
IT spend taxonomy
Depreciation, licenses and contracts land in the same cost pools and towers TBM allocates.
Explore TBMCloud accountability and billing data
Cloud commitments and SaaS billing sit beside the rest of the estate, in one book.
Explore FinOps & FOCUSTIME model · 7 Rs
Every application carries its contracts and renewal dates into the decision to keep or retire it.
Explore App RationalizationASC 350-40 · ASU 2025-06 · IAS 38
Capitalized software joins the register with its owner, its cost and its useful life.
Explore Software CapitalizationNIST CSF · ISO 27001 · SOC 2 · COBIT · SEC cyber rules
The asset inventory your controls depend on, with an owner on every asset.
Explore Security & IT GovernanceEU DORA · NIS2 · UK op-res
Suppliers, contracts and dependencies mapped to the important services they support.
Explore Operational ResilienceAI-native ITAM
Notice dates are counted down, drawdown read, owners proposed and schedules run without anyone chasing them. Dot drafts the brief for each decision; the owner decides whether to renew, renegotiate or exit. Every change is logged.
Counts down to every notice date, flags auto-renewals and shows the annual commitment riding on each decision.
Drafts a brief for each renewal — commitment, drawdown, owner, applications served, end-of-support dates and usage where your tools supply it.
Reads order forms and statements of work inside their master agreement and flags envelopes that are over- or under-drawn.
Proposes an owner for assets, subscriptions and vendors that have none, from the teams and applications they serve.
Tracks vendor support, internal end of life and contract notice dates, and flags exposure with no funded plan.
Runs depreciation schedules for hardware and amortization for capitalized software, and allocates the result with the rest of the book.
Tracks dated obligations from each contract’s clauses and flags anything overdue or closed without evidence.
Compares your ITAM records with the new edition and proposes how each class, process and objective should move.
Where it runs in Dotwork
Dotwork does not ask you to adopt a new method. The framework becomes a view over the same model these solutions already read and write.
How it compares
ITAM and SaaS management tools discover assets and calculate license positions. Spreadsheets and CMDB exports fill the gaps. IT Asset Management on Dotwork takes what those tools find and connects it to contracts, the ledger, the architecture and the plan.
| Capability | ITAM & SaaS management tools | Spreadsheets & CMDB exports | IT Asset Management on Dotwork |
|---|---|---|---|
| Discovery and license compliance positions | Partly | ||
| Hardware, software, SaaS, cloud and AI in one register | Partly | Partly | |
| Renewals on notice dates, with an owner | Partly | ||
| Agreements read inside their master agreement | Partly | Partly | |
| Depreciation and book value by asset | Partly | Partly | |
| Asset cost from the contract, ledger and depreciation schedule | Partly | ||
| End of support beside the renewal and the roadmap | Partly | ||
| A new edition of the standard, with past periods as reported | Partly | ||
| Contracts and costs shared with TBM, FinOps and app rationalization | Partly | ||
| Wired to budgets, the portfolio and architecture |
Who it is for
“Which assets have no owner, and which renew next?
“What are we paying for that the business no longer needs?
“Which renewals need a decision before the notice date?
“Which products are losing support, and are we still renewing them?
“Is depreciation by asset the same number the ledger shows?
“Is every asset our controls depend on in the inventory, with an owner?
Before you buy
How to get a number instead of a pitch.
1
Good answer · Notice date, commitment, drawdown, owner, end of support and the applications it serves — on one screen.
Bad answer · A reminder email thirty days before expiry.
2
Good answer · The ledger, the contract and the depreciation schedule, traced to the line.
Bad answer · A list price someone typed in.
3
Good answer · A proposed owner, shown for someone to confirm.
Bad answer · Nobody, until the audit finds it.
More in Finance & Cost
Finance & Cost
The standards finance and IT finance use to say what technology costs and who uses it.
The model underneath
Steer, Fund & Optimize and Govern & Deliver all read and write the same Enterprise Operating Model. The first module you license builds the model. Every module after it adds context instead of another silo — and Dotwork AI reads all of it, stopping where the decision is yours.
See the Enterprise Operating Model© 2025-2026 Dotwork, Inc. All rights reserved.