Lifecycle Manager uses the data from your integrations to provide a detailed view of your hardware assets. The more integrations that are added to your ScalePad account, the more detail you get. This article explains how to interpret the information shown in the Asset Information Map.

How assets are identified and combined

Each of your individual integrations syncs data into Lifecycle Manager. Lifecycle Manager scans the incoming data and determines whether each data point belongs to an asset that's already been identified, or whether it represents a new one. This prevents duplicate assets from appearing in Lifecycle Manager.

Because more than one integration can report the same asset, Lifecycle Manager also needs a way to show you what each source contributed, and which value it's actually using. That's what the Asset Information Map shows.

Accessing the Asset Information Map

From an asset's detail pane, click Data Sources to open the Asset Information Map.

Understanding the Asset Information Map

The Asset Information Map is a table showing a particular asset's data field-by-field, and which connected integration each value came from. The number of integration columns depends on how many of your connected integrations are reporting data for the asset.

The table includes these columns:

• Field
  The name of the data point (For example, Model or Serial Number)
• Summary
  The value Lifecycle Manager actually displays for this field elsewhere in the app
• One column per connected integration
  The value that specific integration reported for each field.

Fields shown in the table include: Name, Location, User, Serial Number, Make, Model, Type, OS Version, CPU Model, RAM, Purchased Date, Expiry Date, and MAC Addresses.

Sometimes, two or more of your connected integrations report different information for the same field. For example, one might say an asset's warranty is active, while another says it's expired. When this happens, Lifecycle Manager needs to pick one value to show as the Summary. It does this by trusting some integrations more than others, so the more reliable source's value is the one that's shown.

See: How Lifecycle Manager prioritizes data from your integrations

For resolved source dates, Lifecycle Manager uses the earliest reported Purchased Date and latest reported Expiry Date. A manually saved purchase- or warranty-expiry-date override normally takes precedence over that resolved source date until removed. A warranty-expiry override cannot shorten purchased ScalePad coverage; the purchased coverage date remains effective unless the manual date is later. See Manually editing hardware assets for overriding or restoring a date.

See: About Purchase and Expiry dates in Lifecycle Manager

NEW Join our MSP Power-Ups - Free 15-minute micro-workshops + live Q&A with our Lifecycle Manager experts. Sign up here to reserve your spot.