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

# Assets and asset types

> An asset type is a kind of plant. An asset is one item of that kind.

An asset type is a kind of plant. An asset is one physical item of that kind. One type can have many assets.

For a hire fleet:

* The asset type is `20T Excavator`. It stores the SKU, mass, dimensions, and useful life for every machine of that kind.
* The assets are the machines: `EX-101` and `EX-102`. Each stores its own unique ID, status, location, and owner.

Use an asset type when the plan names a kind of plant and the machine is not chosen yet. An allocation can book the type. A [placeholder](https://useidalia.com/docs/assets/placeholders.md) works the same way. Pick the asset when you know which machine will go.

Use an asset when you need one item: where it is, whether it is on hire, and which job it is on.

You can leave Asset type blank when you create an asset.

> [!TIP]
>
> You add crane `LTM-01` and leave Asset type blank. The crane is on the Assets list. Nothing new shows on Asset types.
>
> To put this kind of crane in the catalog, open the `LTM-01` menu and choose **Use as catalog type**. Planners can then book the type on an allocation, and you can add more assets of that type.

A category groups asset types, such as cranes or excavators. Set it on the asset type overview.

An asset type can be an [assembly](https://useidalia.com/docs/assets/assemblies.md) of other asset types. The assembly is still one type. Each built unit is an asset of that type.

To create, update, or delete either record, see [Manage assets](https://useidalia.com/docs/assets/manage.md).


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