# Tools

ION **Tools** can record assets and calibrated equipment in your factory. Tools are laid out in a very similar way to [**Parts**](/api/examples/parts-and-part-revisioning.md) with a few changes.

* Tools are always serialized - there are no lot-tracked tools
* Tool models can optionally have a **maintenance interval** and individual tools can have a **last maintained date**
* Tools can be assigned a **type** used to group tools beyond part number. For example, all torque wrenches of different model numbers can be combined under a single "Torque Wrench" type. This is useful if you want to call out use of a tool in a Run but don't need a specific part number.

![The Tool Library interface used to add tools](/files/ca2QZxLDZLKDvfb4cj4E)

![Tool inventory showing tool serial number barcode, service status and location](/files/300DBAfmfDJhCbSIbE0B)

## Maintenance Interval

The maintenance interval is set in the part in tool library and applies to all tool inventory using that part. The interval is entered with as a list of format {**number**}{**unit**} using the following unit shorthand:

<table><thead><tr><th width="374">Shorthand</th><th width="374">Unit</th></tr></thead><tbody><tr><td>s</td><td>Second</td></tr><tr><td>m</td><td>Minute</td></tr><tr><td>h</td><td>Hour</td></tr><tr><td>d</td><td>Day</td></tr><tr><td>w</td><td>Week</td></tr><tr><td>month</td><td>Month</td></tr><tr><td>y</td><td>Year</td></tr></tbody></table>

For example, entering an interval of "1d20m" means an inverval of 1 day and 20 minutes, or 1480 minutes

## Tool Status

Tools have two statuses, **Available** and **Unavailable**.

The status of a tool can be determined by a couple of factors but also comes with a way to override the built in calculations:

1. If the tool has a maintenance interval and a last maintenance date, their maintenance status is calculated as **Available** depending if the next maintenance date is in the future. If the next maintenance date is in the past, the tool is **Unavailable**.
2. Tools located at an unavailable location they are marked unavailable.
3. Either of these calculations can be manually overridden by toggling the **Available / Unavailable** indicator within the tool inventory panel. This provides flexibility to adjust tool availability based on factors of your choosing, such as integration with a tool management system.

*Note: If you are interested in enabling this functionality please reach out to your Customer Success Manager.*

<figure><img src="/files/MStLfp9b3MjIGHOGDCUo" alt=""><figcaption></figcaption></figure>

## Tool Barcodes

Printing barcodes and using tool [barcodes](/features/barcode-labels.md) works just like Part Inventory. Tools also share [barcode templates](/features/barcode-labels/templating.md) with Inventory.&#x20;

## Tracking tool usage

Tool usage can be tracked by using a **Tool Field** on a step in a run. When a technician is working on the run they will fill out the tool field and create an auditable log of the tool's usage.

When creating the data collection field, you can set the field name and help text as usual. Selecting the **Available** checkbox limits valid tool input to tools with the available status.&#x20;

<figure><img src="/files/6ZSi8gIalDcSTjc9Bo6E" alt=""><figcaption><p>Adding a tool field to a step</p></figcaption></figure>

Use the **Validations** menu to constrain what kind of tools are valid input. Acceptable validations are **Type** for multiple models of tools or **Part Number** for a specific model.

<figure><img src="/files/jXL8hX88viFuyI4GocJV" alt=""><figcaption><p>Adjusting tool field validations</p></figcaption></figure>

When executing a run, select the tool you are using from the list to complete the field.

<figure><img src="/files/BVosME9lv0tClusjSVC9" alt=""><figcaption><p>Successful record of tool usage</p></figcaption></figure>

## Tools on Runs

Tools can be associated with [Runs](/features/runs.md) to inspect or maintain them. Associate a tool with a run just like you would a part during run creation.

<figure><img src="/files/S1AJ8n8mBdA8naaZikGP" alt=""><figcaption><p>Creating a run to maintain a tool</p></figcaption></figure>

## Tools on Issues

[Issues](/features/quality/issues.md) can be opened on tools just like part inventory. Tools will appear in the part inventory dropdown when creating or modifying an issue.

## Tools on Kits

Tools can be used in [Kits](/features/kitting.md) to move tools between different [Locations](/features/locations.md), or to request tools in a specific area or to a specific user. Requesting or moving a tool works the same as requesting or moving inventory.


---

# Agent Instructions: 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:

```
GET https://manual.firstresonance.io/features/tools.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.