> For the complete documentation index, see [llms.txt](https://docs.tricloudnexus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tricloudnexus.io/management-portal/oee/equipment.md).

# Equipment

Where OEE actually runs. Enable Availability, Performance and Quality on a piece of equipment, wire it to your tags, and configure shifts, stops and states.

An **Equipment** node in the OEE Sites tree represents a single machine, line, cell, or any unit you want to score with OEE. Everything about *how* OEE is calculated for that unit is configured on the Equipment, across **seven tabs**:

| Tab               | What it covers                                                                                                                                                                              | Reference                                                                                    |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| **Equipment**     | Name, description, and the OEE Calculation toggles & targets (Total OEE Target plus per-pillar Enable + Target).                                                                            | [Equipment Settings & OEE Targets](/management-portal/oee/equipment/settings-and-targets.md) |
| **Tag Mapping**   | Three groups of tag inputs: State & Error Codes, Product & Order, Data Quality. Each input slot can be a Single Tag, a JSONata expression on a string tag, or a multi-variable Calculation. | [Tag Mapping](/management-portal/oee/equipment/tag-mapping.md)                               |
| **Shifts**        | Picks one of the Site’s Shift Calendars to define when the equipment is expected to run.                                                                                                    | [Equipment Shift Assignment](/management-portal/oee/equipment/shift-assignment.md)           |
| **Planned Stops** | Recurring downtime windows (changeovers, breaks, maintenance) that subtract from scheduled time.                                                                                            | [Planned Stops](/management-portal/oee/equipment/planned-stops.md)                           |
| **Stop Causes**   | Named stop reasons categorized as Planned / Unplanned, plus a vendor-error-code → Stop Cause mapping table.                                                                                 | [Stop Causes & Error Codes](/management-portal/oee/equipment/stop-causes-and-error-codes.md) |
| **States**        | Maps each raw state value the equipment emits to an Availability Category (Running, Unplanned Stop, …).                                                                                     | [States Mapping](/management-portal/oee/equipment/states-mapping.md)                         |
| **Products**      | Selects the Site’s Product List the equipment runs and a default Ideal Cycle Time used when no per-product value is set.                                                                    | [Equipment Products](/management-portal/oee/equipment/equipment-products.md)                 |

The active tab is remembered per browser session, so navigating away and back returns you to where you were.

***

## Recommended order to fill the tabs

When configuring a new piece of equipment, work through the tabs in this order — each step depends on the previous one:

1. **Equipment** — set the name, then enable the pillars you intend to measure (you can come back and turn more on later). Leave **OEE Enabled** off for now if you’re still wiring tags.
2. **Tag Mapping** — point each enabled pillar at the tags it needs:
   * **Availability** needs at least the Equipment Run State tag.
   * **Performance** needs Current Product Id (for ideal cycle time lookup) and Ordered Products / Order Id depending on your tracking model.
   * **Quality** needs two of the three counts (Total / Approved / Rejected) — see [Data Quality](/management-portal/oee/equipment/tag-mapping/data-quality.md).
3. **States** — translate the raw values the run-state tag emits (`Running`, `Stopped`, …) into Availability Categories.
4. **Stop Causes** — list the business-friendly stop reasons, then map vendor error codes onto them.
5. **Shifts** — assign one of the Site’s Shift Calendars.
6. **Planned Stops** — schedule recurring downtime that should not count against Availability.
7. **Products** — select a Product List from the Site and set a default Ideal Cycle Time.
8. Return to **Equipment** and switch **OEE Enabled** on.

{% hint style="info" %}
**OEE Enabled** is the master switch. Until it’s on, the platform doesn’t calculate or persist OEE results for this equipment — but the tree’s safety check still treats the configuration as "in use", so reuse and reorganization stay safe.
{% endhint %}

***

## How tabs surface validation

Each tab header shows an `invalid` badge when validation finds an issue on that tab. Save is blocked until the badges clear. Common causes:

* Missing Total OEE Target / per-pillar target on the Equipment tab.
* Required tag not selected for an enabled pillar on Tag Mapping.
* Stop Cause selected on a Planned Stop but no Availability Category assigned.

The page-level Save / Cancel toolbar applies to **all** tabs at once — you can edit Tag Mapping and Stop Causes in the same session and save them together.

{% hint style="warning" %}
Cancelling discards changes on every tab, not just the active one. If you need to keep some edits, save first and then continue.
{% endhint %}

***

## Disabling vs. deleting

* **Disable** an Equipment by switching **OEE Enabled** off on the Equipment tab. Calculation stops; configuration is preserved; the node can be moved or its parent deleted (the tree’s "enabled equipment blocks deletion" guard only triggers when OEE Enabled is on).
* **Delete** an Equipment from the tree’s kebab / right-click menu. Disable OEE first if it’s currently enabled, otherwise the delete is rejected with a message naming the equipment.

See [Site Structure](/management-portal/oee/sites/site-structure.md) for the full tree-edit rules.