# How Do You Structure Your Asset IDs in FaciliWorks?

**URL:** <https://forum.cybermetrics.com/t/how-do-you-structure-your-asset-ids-in-faciliworks/322>\
**Category:** FaciliWorks\
**Created:** [September 3, 2026, 8:37pm UTC](https://forum.cybermetrics.com/t/how-do-you-structure-your-asset-ids-in-faciliworks/322 "2026-09-03T20:37:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![aavila](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@aavila](https://forum.cybermetrics.com/u/aavila)\
**Post date:** [September 3, 2026, 8:37pm UTC](https://forum.cybermetrics.com/t/how-do-you-structure-your-asset-ids-in-faciliworks/322/1 "2026-09-03T20:37:19Z")

</div>

One thing that comes up during a FaciliWorks training is how much information to include in an Asset ID.

Some organizations keep their IDs simple and sequential, such as **0001** or **0002**. Others use something more descriptive, such as **PUMP-001** or **BLDG1-PUMP-001**.

A descriptive ID can make an asset easier to recognize, but it can also create problems later if the asset moves to another building or department.

I’m curious what has worked for other FaciliWorks users. Do you keep Asset IDs simple and store details such as location and equipment type in their own fields, or do you build that information into the ID?

Has your approach held up as your asset inventory has grown?