> For the complete documentation index, see [llms.txt](https://docs.biscit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.biscit.com/ekr-user-guide/how-to/how-to-create-equipment.md).

# How to Create Equipment

This guide provides instructions on how to create and add new equipment profiles within the Kinetic system to be used in EKR.

{% hint style="warning" %}
This documentation contains instructions that are done in Epicor Kinetic and might be outdated. For more detailed and updated instructions, refer to the Epicor Kinetic Web Help.
{% endhint %}

**Note: EKR** can be used with Epicor's maintenance module where equipment is created and maintained within **EKR**.

1. In the Kinetic Equipment page, click on the add icon.&#x20;

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FLoeLu7VTeSA7FReXifKY%2Fimage.png?alt=media&amp;token=9c2a1f75-3d9b-4b00-be5e-0efbe82ffe91" alt=""><figcaption></figcaption></figure>

2. In the Equipment page, complete all the details required.

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FpgqWkqYGV1hn8IwRBwgI%2Fimage.png?alt=media&amp;token=11aa98bc-1a48-4329-a374-7af2a5e79da8" alt=""><figcaption></figcaption></figure>

**Note:** Ensure that the Type field is set to Rental for it to show up in **EKR**.

**Note:** Fields marked with an asterisk (\*) are typically mandatory for saving the record.

3. Once all details are completed, click on the **Save** icon.

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FRIxH60sJL49VVOL8gCFH%2Fimage.png?alt=media&amp;token=addfb78f-fee5-4a5e-be97-a410fa82094a" alt=""><figcaption></figcaption></figure>

4. Afterwards, go to **EKR** and click on the **Equipment** section.
5. Search for the newly created equipment in the **EKR** in the **Equipment** list.

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FpdMn0Dv54UWjvwpIyd5L%2Fimage.png?alt=media&amp;token=38473e19-e583-4668-ad3a-e065f9227829" alt=""><figcaption></figcaption></figure>

6. Once the newly created equipment has been selected, go to the **Pricing** tab.

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2F0GRkE1o3wsMzFUAWS6eR%2Fimage.png?alt=media&amp;token=e1458429-36bd-4f11-93fd-8a806d16e67f" alt=""><figcaption></figcaption></figure>

7. Assign the Pricelist that is relevant to the Equipment.

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2F3wAXazZjZ8i10qYai4Ud%2Fimage.png?alt=media&amp;token=cf7f90aa-7f5a-4be7-9834-8f4e760c981d" alt=""><figcaption></figcaption></figure>

8. Once the **Pricelist** has been set, click on the **Save** icon. The **Equipment** can now be used in **EKR**.&#x20;


---

# 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://docs.biscit.com/ekr-user-guide/how-to/how-to-create-equipment.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.
