> ## Documentation Index
> Fetch the complete documentation index at: https://www.docusnap.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Making Scanned Systems Manageable

> Turn scanned systems into validated assets: set owners, criticality and lifecycle — for many assets at once and one at a time.

We turn scanned systems into validated assets with owners, criticality and
lifecycle. Shared values we set for many assets at once, device-specific ones
one at a time.

**Prerequisite:** a completed scan. The systems stand under *ITAM › Assets*.

## Starting point

Docusnap Sports GmbH has completed its first scan. Around 900 systems are
recorded, and on none of them are the ITAM fields set. We work on the ten
servers of the sales department.

## 1. Check the starting state

Under *ITAM › Assets* stand the figures *ITAM-Capable Assets* (around 900) and
*Managed Assets* (close to zero). The difference is the work ahead.

A click on a server row opens the detail panel. Its *Completeness* section
shows *Not Edited*: no core field is set.

## 2. Set shared values

<Steps>
  <Step title="Select the servers">
    We filter the list down to the sales servers and select all ten.
  </Step>

  <Step title="Open bulk editing">
    *Edit Entries* opens bulk editing in the side panel.
  </Step>

  <Step title="Set the values">
    *Asset Owner*: the IT contact for sales. *Criticality*: *High*. Both
    values apply to all ten servers.
  </Step>
</Steps>

The *Completeness* of the ten servers is no longer 0 % afterwards.

<Tip>
  Set the values many assets share first, for all of them at once. What is then
  left per asset is only the device-specific part.
</Tip>

## 3. Complete one asset

The remaining core fields are device-specific. We open one server, tab
*ITAM*, and set through the pencil icon:

| Field | Value |
| - | - |
| *Technical Owner* | the technically responsible person |
| Phase in *Lifecycle* | *Operation* |
| *Commission Date* | the date the asset went into operation |
| *End of Life*, *End of Service* | date, if known; otherwise *Not assessable – excluded from completeness* |

*Completeness* shows 100 %. The asset is ready for validation.

<Note>
  All fields and the justification required at a phase change:
  [Recording ITAM Data](/docs/en/itam/manage-data).
</Note>

## 4. Validate

At 100 % the button *Request* in the *Validation* section is active. After
*Request*, the asset has the status *Requested*. *Validate* completes it: the
asset is *Validated*, with a date and the next due date.

<Note>
  With *Strict Mode* active, only the *Asset Owner* can validate. See
  [Validating Assets](/docs/en/itam/validate-assets).
</Note>

## Result

Ten servers have moved from *Not Edited* to *Validated*: shared values through
bulk editing, device-specific ones one at a time. The same approach applies to
the remaining systems.

## Next steps

* Record warranties: [Warranties](/docs/en/itam/warranties)
* Allocate costs: [Finding Unused Licenses](/docs/en/itam/tutorial-costs)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.