> 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/configuration/equipment/on-and-off-hire-maintenance-jobs.md).

# On and Off-hire Maintenance Jobs

On and off-hire maintenance jobs are automated maintenance tasks generated by the system when equipment is either **On-Hire** which is sent out for a rental  or **Off-Hire** which is returned from a rental.

To automate **Maintenance Job Creation** during equipment **Hire and Return**, this will show how to configure templates and triggers.

## Creating a Maintenance Job Template

This section is done in the EPICOR Kinetic Maintenance Module.

To automate maintenance workflows such as On/Off Hire inspections, you must first create a Master Job Template. This template acts as the blueprint from which future live maintenance jobs will be copied.

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2F7RlLEcYPe01Bj3DOYeq0%2Fimage.png?alt=media&amp;token=0f63e970-92dc-49b6-b5c5-64e5343f9f99" alt=""><figcaption></figcaption></figure>

#### Job Detail Section

| **Section**       | **Field**       | **Detail**                                      |
| ----------------- | --------------- | ----------------------------------------------- |
| Job               | Job             | The unique identifier for this maintenance job. |
| Scheduling        | Priority        | The urgency level assigned to the job.          |
|                   | Schedule Locked | Check-box                                       |
| Equipment Details | Equipment ID    | The specific asset being serviced.              |
|                   | Description     | Description of the asset.                       |
|                   | Location        | Where the equipment is physically located.      |
|                   | Model           | The manufacturer model number.                  |
|                   | Serial Number   | The unique serial ID of the unit.               |
|                   | OEM             | Original Equipment Manufacturer.                |
| Dates             | Required By     | The deadline for the job.                       |
|                   | Start           | The scheduled start date.                       |
|                   | Due             | The scheduled completion date.                  |
| Project           | Project ID      |                                                 |
|                   | Project Phase   | Drop-down                                       |
| Status            | Template        | Check-box                                       |
|                   | Engineered      | Check-box                                       |
|                   | Released        | Check-box                                       |
|                   | Hold            | Check-box                                       |
|                   | Preventative    | Check-box                                       |
|                   | Machine MES     | Check-box                                       |
|                   | Mass Print      | Check-box                                       |

## Assign Template in EKR Equipment Maintenance <a href="#assign-template-in-rms-equipment-maintenance" id="assign-template-in-rms-equipment-maintenance"></a>

{% hint style="info" %}
This screenshot shows the Maintenance tab in the Equipment screen in EKR.
{% endhint %}

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2F1WDJP1tvkR48GFnpguRC%2Fimage.png?alt=media&amp;token=990ed9ce-8be4-4179-85ec-1fd1b7f763dd" alt=""><figcaption></figcaption></figure>

## Triggering the Maintenance Template in EKR

This process automates the creation of maintenance jobs when equipment is On Hire or Off Hire. It involves creating a master template in Kinetic and linking it to specific triggers within EKR.

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FCOcMv3H7sAZevSaRn7gh%2Fimage.png?alt=media&amp;token=849155ef-8852-4420-bdc1-ccbeeabed8fc" alt=""><figcaption></figcaption></figure>

Refer to the information on triggers accordingly:

#### Triggers <a href="#triggers" id="triggers"></a>

EKR has triggers that invoke the maintenance job creation, below are the types of maintenance job triggers EKR supports:

**Confirm On-Hire**: Maintenance Job will be created when the Confirm On Hire button is pressed on the Logistics Dashboard

**Confirm Off-Hire**: Maintenance Job will be created when the Confirm Off Hire button is pressed on the Logistics Dashboard

#### Required By Dates <a href="#required-by-dates" id="required-by-dates"></a>

EKR automatically sets the **Required By** date on the **Maintenance Job** based on the bookings in EKR.

* **On Hire Confirmation**: The required date is set to the **on hire date** of the booking
* **Off Hire Confirmation**:
  * If there’s a **future booking**, the required by date is set to the **next booking’s on hire date**
  * If there’s **no future booking**, the required by date defaults to **2 days after the return date**

## Scheduling Maintenance Jobs <a href="#scheduling-maintenance-jobs" id="scheduling-maintenance-jobs"></a>

### In Kinetic

Scheduling Maintenance Jobs is to assign a specific completion timeframe to a maintenance job within Kinetic. Proper scheduling ensures the job is tracked correctly on the timeline and resources are allocated effectively.

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FRgslM3vpclBmCUMb7zd6%2Fimage.png?alt=media&amp;token=415381bb-56c5-4ad8-8f0e-96cabe410305" alt=""><figcaption></figcaption></figure>

#### Scheduling Options Section

| Field                         | Details                                                                                                                             |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Schedule                      | The scheduling direction is set to calculate backwards from a due date.                                                             |
| Start Date                    | The proposed start date for the job.                                                                                                |
| Start Time                    | The start time (midnight).                                                                                                          |
| Due Date                      | Action Item: This field is highlighted in a red box, indicating it is the critical field to update based on the "Required By" date. |
| Due Time                      | The time the job is due.                                                                                                            |
| Override Material Constraints |                                                                                                                                     |
| Finite Capacity               |                                                                                                                                     |
| What-If-Schedule              |                                                                                                                                     |
| Recalculate Expected Yield    |                                                                                                                                     |
| Minimize WIP                  |                                                                                                                                     |

#### Multi-Job Section

| Field              | Details   |
| ------------------ | --------- |
| Schedule Multi-Job | Check-box |
| Schedule Type      | Drop-down |
| Ignore Locks       | Check-box |

#### In EKR

This process utilizes the standard scheduling workflow for Maintenance Jobs in Kinetic but requires specific date configurations to align with EKR deadlines.

{% hint style="info" %}
This screenshot shows that the red in the timeline view are maintenance jobs.
{% endhint %}

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FgmI6sny8S2SousvRUCwi%2Fimage.png?alt=media&amp;token=62d10a74-3a53-406c-aa31-e99de8452101" alt=""><figcaption></figcaption></figure>


---

# 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/configuration/equipment/on-and-off-hire-maintenance-jobs.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.
