Hardware Lifecycle Report

These will be your bread-and-butter to manage ALM Policies with clients

Our Hardware Lifecycle Report helps you see a clear summary of hardware assets in an organization. You can quickly and accurately check on how many hardware assets are covered under warranty, due soon, or are in need of renewal.

Access the Hardware Lifecycle Report for an organization

  1. Navigate to your Organizations page
  2. Click into an organization
  3. Click the Hardware Lifecycle Report button on the right-hand side of the page

Using these reports

Hardware Lifecycle Reports have a variety of use cases. Update your clients with a quick phone call, or show them the facts in-person for an at-a-glance status update of their assets. They don't need to know that you crafted the report with the click of a button.

Let's dive into the report

We'll go page-by-page, pointing out the important parts so you get to know your way around without being overwhelmed.

Cover page

This is an overall summary for your client. The thick, outer circle represents hardware asset status by category. The thinner, inside circle shows OS support status.

Hardware list page

The device list page acts as a view similar to the Hardware page, but specifically for this client.

Evergreen / replacement budget page

This page is a sample replacement budget, based on the current status of your supported hardware assets.
It can help get your hardware assets back in line with your ALM replacement refresh policy


Hardware Lifecycle Reports walkthrough complete

Now that you understand our Hardware Lifecycle Report, it's worth looking into the Settings for our Hardware Lifecycle Report.

Updated about a month ago

Related articles

You know how to generate it, but let's take a closer look at our Hardware Lifecycle Report

Settings for our Hardware Lifecycle Report

Hardware Lifecycle Report

These will be your bread-and-butter to manage ALM Policies with clients

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.