Skip to main content
An asset can be created by hand and given its ITAM core fields without a scan. The workflow takes minutes to understand on one device — and is the same on a thousand.

​
Creating the asset

Open ITAM › Assets; in a new tenant that has not been scanned, the list is empty. The Asset button opens the creation dialog. Only ITAM-capable types are offered — the types the data model provides ITAM for.
ITAM-capable and managed are two different things. The metrics above the list show both: ITAM-capable assets is everything that could carry ITAM data, managed assets is what actually does. In a freshly scanned tenant the two numbers are far apart.

​
Setting the core fields

Open the new asset and use its ITAM tab to set the seven core fields: the phase in the Lifecycle, Asset Owner, Technical Owner, Criticality, Commission Date, and End of Life and End of Service. On the right of the tab, Completeness keeps pace and shows for each core field whether it is set.
End of Life and End of Service can be marked as not assessable — for a device without vendor support, for instance. They then drop out of both the numerator and the total, and the asset reaches 100 % without either date being set.

​
Why completeness matters

At 100 % a validation can be requested: the Asset Owner confirms that the data is correct. After that it falls due again at fixed intervals. That is the difference from a well-kept spreadsheet: not just that the data exists, but that a named person stands behind it and confirms it on a cycle.
The full walkthrough with every field and its special cases is in Capturing ITAM Data.
Assets created by hand are the entry point, not the goal. Once they arrive automatically from your network, vulnerability analysis, relationships and every evaluation work on captured data. The next step is Scanning Your Network.