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

# Manage equipment

> Model locations, assets, meters, documents, and scannable identifiers in Canary.

Canary's equipment model connects each maintenance event to the physical place and maintainable item where it occurred. A consistent structure improves field lookup, history, and reporting.

## How the records fit together

| Record     | Use it for                                  | Key rule                                                         |
| ---------- | ------------------------------------------- | ---------------------------------------------------------------- |
| Location   | Sites and direct areas                      | Location hierarchy supports a parent and its direct sublocations |
| Asset      | Equipment and maintainable components       | Each sub-asset has at most one parent                            |
| Meter      | Usage, condition, counters, or on/off state | Each meter belongs to exactly one asset or location              |
| Document   | Manuals and equipment knowledge             | Ask Canary searches processed documents in asset context         |
| Identifier | QR code or barcode lookup                   | A value resolves to one active record in the organization        |

## Recommended setup order

1. Create locations from broadest site to direct work area.
2. Create assets and place them at locations.
3. Add parent and sub-asset links only for components maintained separately.
4. Link compatible parts and meters.
5. Upload equipment documents and wait for processing.
6. Attach existing identifiers or generate Canary labels.
7. Test search, hierarchy, and mobile scans with a technician.

## Model with maintenance in mind

Create an asset level when the team needs distinct work history, status, documents, meter readings, or parts for that component. Use a location for physical placement and an asset hierarchy for machine composition.

## Lifecycle safeguards

* Deleting an asset archives the selected asset and its descendants together. Work history remains connected, and the batch can be restored.
* Active meters and automation dependencies can block asset deletion until they are resolved.
* Deleting a location is permanent. Canary requires its children and all dependent records to be moved or detached first.
* Archiving a meter preserves its readings and requires automation dependencies to be removed first.

## Related pages

* [About assets](/help/assets/overview)
* [Locations](/help/assets/locations)
* [Meters](/help/meters/overview)
* [QR codes and barcodes](/help/assets/qr-codes)
* [Asset documents](/help/assets/documents)