> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/library-packs/hardware-management/physical-endpoint-rightsizing/usage-guide-physical-endpoint-rightsizing.md).

# Usage guide: Physical endpoint rightsizing

{% hint style="warning" %}
This page outlines various ways to use the pack, including use case examples.

Administrators can refer to the [Configuration guide: Physical endpoint rightsizing](/platform/library-packs/hardware-management/physical-endpoint-rightsizing/configuration-guide-physical-endpoint-rightsizing.md) to set up and customize the installed content.
{% endhint %}

The **Physical endpoint rightsizing** library pack helps you align endpoint hardware with employee requirements. It enables you to:

* Assess whether endpoint hardware capacity matches employee workloads.
* Identify devices that are overpowered or underpowered.
* Optimize hardware refresh decisions based on real usage.
* Improve employee productivity by matching devices to mobility and display requirements.
* Reduce hardware costs by identifying opportunities to rightsize device specifications.

The library pack includes preconfigured **Live dashboards** that help you evaluate compute capacity, mobility requirements, and external display usage across your environment.

## Library pack uses

{% hint style="info" %}
Jump to [Use cases](#use-cases) on this page to see relevant scenario applications.
{% endhint %}

Use the library pack content for the purposes listed below.

### Monitoring compute fit

The **Physical endpoint rightsizing** dashboard provides an overview of whether endpoint CPU, memory, and GPU resources match employee requirements.

Use the **Compute fit** tab to:

* Review the distribution of rightsized, oversized, and undersized devices.
* Identify which hardware component (CPU, RAM, or GPU) requires adjustment.
* Prioritize hardware refresh initiatives based on device categories.
* Filter results by **CPU performance class**, **Memory**, **Device type**, **Mobility profile**, and **External display profile**.

The dashboard helps you quickly identify opportunities to reduce unnecessary hardware costs while maintaining employee productivity.

### Evaluating mobility fit

Use the **Mobility fit** tab to determine whether employees have devices appropriate for their mobility patterns.

The tab enables you to:

* Compare employee mobility behavior with assigned device types.
* Identify devices that are too heavy or unsuitable for frequent travel.
* Review potential optimization opportunities.
* Detect mobility mismatches that may affect employee experience.

This information helps ensure employees receive hardware appropriate for their working style.

{% hint style="info" %}
Query results by [investigating KPIs from the live dashboard](https://docs.nexthink.com/platform/latest/using-live-dashboards) or from [your own investigations](https://docs.nexthink.com/platform/latest/investigations).
{% endhint %}

### Assessing external display fit

The **External display fit** tab evaluates whether device graphics capabilities support employees' display requirements.

Use this tab to:

* Review employee display profiles.
* Identify devices experiencing GPU degradation.
* Detect devices whose hardware does not match display complexity.
* Prioritize graphics hardware upgrades where required.
* Identify opportunities to reduce costs by reallocating overpowered devices.

This tab helps balance employee productivity with hardware investment.

## Use cases

In addition to the relevant use cases covered below, you may uncover other troubleshooting scenarios specific to your environment.

### **Identifying oversized devices**

Use the **Compute fit** tab to identify devices with excess hardware capacity that could be replaced with lower-specification hardware during the next refresh cycle.

From the **Compute fit** tab:

1. Review the **Oversized** indicator.
2. Identify whether CPU, RAM, or GPU is driving the oversized classification.
3. Filter devices by **Performance class** or **Device type**.
4. Drill down into the affected devices using the **Live dashboard**.
5. Validate that employees are not experiencing sustained hardware utilization before recommending lower specifications.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FbWBZRlJfZV3YSfv64iG3%2Fimage.png?alt=media&amp;token=17bdf567-cbb9-4611-b1b2-303ec9940a05" alt=""><figcaption></figcaption></figure>

### **Identifying devices requiring hardware upgrades**

Use the **Compute fit** tab to identify devices that lack sufficient hardware resources.

From the **Compute fit** tab:

1. Review the **Undersized** indicator.
2. Determine whether CPU, RAM, or GPU capacity is insufficient.
3. Drill down into affected devices.
4. Prioritize devices experiencing sustained resource constraints.
5. Include these devices in upcoming hardware refresh planning.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FEjpVbYnXJ9lxOZoCdazZ%2Fimage.png?alt=media&amp;token=1cf79aba-fc2b-47c5-b05a-8b952f4e7f79" alt=""><figcaption></figcaption></figure>

### **Optimizing devices for employee mobility**

Use the **Mobility fit** tab to ensure employees have devices suited to their working patterns.

From the **Mobility fit** tab:

1. Review the **Potential optimization** and **Mobility mismatch** indicators.
2. Examine employee mobility profiles.
3. Identify users whose assigned device type does not match their mobility requirements.
4. Prioritize highly mobile employees using heavier desktop-oriented devices.
5. Plan replacement devices that better align with employee mobility.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FDoq2CBXPBdJv3TcCWElF%2Fimage.png?alt=media&amp;token=623f5e4f-1ef2-430b-96a2-a3ce3d7b5bb4" alt=""><figcaption></figcaption></figure>

### **Validating graphics hardware requirements**

Use the **External display fit** dashboard to identify devices that may require improved graphics capabilities.

From the **External display fit** tab:

1. Review employee **Display profiles**.
2. Examine devices reporting **GPU degradation**.
3. Identify devices with complex display profiles and insufficient graphics capability.
4. Prioritize graphics upgrades for affected employees.
5. Review workstation devices with simple display profiles to identify potential optimization opportunities.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2F3Af6QLNgAovVLe4Yq0j2%2Fimage.png?alt=media&amp;token=08da3211-eea1-48ba-ae09-1995da256ea9" alt="" width="375"><figcaption></figcaption></figure>

***

RELATED TOPICS

* [Configuration guide: Physical endpoint rightsizing](/platform/library-packs/hardware-management/physical-endpoint-rightsizing/configuration-guide-physical-endpoint-rightsizing.md)
* [Manage live dashboards](https://nexthink.gitbook.io/opd/user-guide/live-dashboards/managing-live-dashboards)
* [Manage workflows](https://nexthink.gitbook.io/opd/user-guide/workflows/managing-workflows)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexthink.com/platform/library-packs/hardware-management/physical-endpoint-rightsizing/usage-guide-physical-endpoint-rightsizing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
