> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/documentation/modules/assets/pdus.md).

# PDUs

`PDU (Power distribution unit)` lists all the item used to manage and monitor electrical distribution in a rack or datacenter.

![global view PDUs](https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2Fgit-blob-c677e1c2f13d1bcf3c32e5904c9aed2bf64a90f2%2Fpdu.png?alt=media)

In a PDU form, the following information is available:

{% hint style="info" %}
It is possible to use [templates with PDUs](/documentation/modules/overview/templates.md).
{% endhint %}

![Details view PDUs](https://3503800744-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIiEHKRx5AeABNDLcRlWX%2Fuploads%2Fgit-blob-5a836316854ae2caa07727afce51f511fac8e08c%2Fpdu-details.png?alt=media)

* Name
* [Data center position](/documentation/tabs/common_fields/data_center_position.md)
* [Location](/documentation/tabs/common_fields/location.md)
* [Technician in charge](/documentation/tabs/common_fields/technician_in_charge.md)
* [Model](/documentation/tabs/common_fields/model.md)
* [Inventory number](/documentation/tabs/common_fields/inventory_number.md)
* [Comments](/documentation/tabs/common_fields/comments.md)
* [Status](/documentation/tabs/common_fields/status.md)
* [Device type](/documentation/tabs/common_fields/asset_type.md)
* [Manufacturer](/documentation/tabs/common_fields/manufacturer.md)
* [Serial number](/documentation/tabs/common_fields/serial_number.md)
* [User](/documentation/tabs/common_fields/user.md)

## Impact Analysis

[Impact analysis](/documentation/tabs/impact_analysis.md) enables an infrastructure diagram to be drawn up, showing the dependencies and impacts in the event of item loss. This can be saved and exported

## Plugs

[Plugs](/documentation/modules/assets/tabs/plugs.md) shows the number of sockets available on the PDU

## Network Ports

This tab allows to manage the [network ports](/documentation/tabs/network_ports.md) attached to current item.

The information that can be viewed is:

* Name
* Port number
* MTU
* Speed
* Internal status
* Last change
* Number of I/O bytes
* Number of I/O errors
* Duplex
* VLAN
* Connected to
* Connection
* Deleted

## Management

[Management](/documentation/modules/tabs/management.md) of financial and administrative information, this information is visible in the 'Management' tab on the item's form.

## Contracts

GLPI supports [contracts](/documentation/modules/management/contract.md) management, in order to manage contract types such as loan, maintenance, support...

Contracts management allows to:

* make an inventory of all contracts related to the organization assets
* integrate contracts in GLPI financial management
* anticipate and follow contract renewal.

## Documents

The [document](/documentation/modules/management/documents.md) tab lets you link different types of files to the item (PDF, txt, png, etc.) You can attach a document already uploaded to GLPI or add a new one directly from this tab.

## Tickets

View all [tickets](/documentation/modules/tabs/tickets.md) linked to the item.

## Problems

This tab refers to all hardware-related [problems](/documentation/modules/assistance/problems.md). Problems can also be linked to tickets, projects, etc. This allows you to have a complete scenario when necessary.

## Changes

[Changes](/documentation/modules/assistance/changes.md) lists all changes related to a material. From this tab, you can't link a change directly, you can do it from **Assistance** > **Changes** > **Items**. You can create a new change from this page, which will be linked to the item you have selected.

## History

The *History* tab is used to show any changes made to an item. The following information about the changes is available:

* ID of the change.
* Date and time the change was made.
* User who made the change. If this field is not filled, it means that the action was done automatically (For example: automatic inventory update).
* Field that was changed.
* Description of the change that was made.

The description of the change represents either the difference between the old and the new value (For example with location field: Change HQ to Remote Office A), or the explanation of the action which was carried out (For example: Uninstallation of a software: "Gimp 2.0").

{% hint style="info" %}
For dropdowns or objects with a parent/child relationship, the modification of a child will appear in the history of the parent element.
{% endhint %}

## All Information

For an item, all information is displayed on one page from the *All* tab. This shows all of the tabs of an object's form in one view, one below the other.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.glpi-project.org/documentation/modules/assets/pdus.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.