> 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/settings-and-targets.md). # Equipment Settings & OEE Targets Equipment name, OEE master switch, the three pillar toggles, and target percentages. The **Equipment** tab is the front door for any unit you want to measure. It sets the equipment’s identity and tells the platform which OEE pillars to calculate and what targets to compare them to.

Equipment tab — name, description, and the OEE Calculation block (master switch + per-pillar enable and target)

*** ## Equipment info | Field | Required | Notes | | ------------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------ | | **Equipment name** | Yes | Display name shown in the tree and on dashboards. | | **Description** | No | Free-text, multi-line. Use it to capture model number, vendor, location notes, or anything operators need to know at a glance. | *** ## OEE Calculation The **OEE Calculation** block defines what is measured and what counts as "good". It contains a master switch, a total OEE target, and three pillar rows. ### Master switch | Field | Required | Notes | | -------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **OEE Enabled** | — | Turns OEE calculation on/off for this equipment. When off, the platform does not calculate or persist OEE for this unit; configuration is preserved so you can switch it back on later. | | **Total OEE Target** | Yes | The combined-OEE goal as a percentage (`0`–`100`). Used by dashboards to compare the actual score against the expected score. | ### Pillar toggles Each of the three pillars has its own enable switch and target. The target field is disabled until the pillar’s enable switch is on. | Pillar | Enable switch | Target field | When the target applies | | ---------------- | ---------------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | **Performance** | Calculate Performance | Performance Target (%) | When Performance is enabled — uses Current Product’s Ideal Cycle Time vs. observed cycle time. | | **Availability** | Calculate Availability | Availability Target (%) | When Availability is enabled — uses Run Time vs. Net Scheduled Time. | | **Quality** | Calculate Quality | Quality Target (%) | When Quality is enabled — uses approved-vs-total-units math driven by [Data Quality](/management-portal/oee/equipment/tag-mapping/data-quality.md). | All targets accept three decimals (e.g. `87.500`) so you can mirror exact KPIs from existing reporting systems. {% hint style="info" %} Disabling a pillar does **not** zero its contribution — it removes that factor from the OEE product. With Quality disabled, OEE = Availability × Performance. This is intentional: you can roll out OEE in stages as your data matures, without temporarily under-reporting. {% endhint %} *** ## What each pillar requires elsewhere Enabling a pillar here only sets the *intent* to measure it. The actual signal still has to be wired up on the [Tag Mapping](/management-portal/oee/equipment/tag-mapping.md) tab before calculation produces meaningful values. | Pillar enabled | What you also need to configure | | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Availability** | Equipment Run State tag + a complete [States Mapping](/management-portal/oee/equipment/states-mapping.md). Optionally Error Code tag(s) and [Stop Causes](/management-portal/oee/equipment/stop-causes-and-error-codes.md). A [Shift Calendar](/management-portal/oee/equipment/shift-assignment.md) is optional — assigning one tags facts with the active shift so dashboards can slice by shift. | | **Performance** | Current Product Id tag (so the platform can look up Ideal Cycle Time from [Equipment Products](/management-portal/oee/equipment/equipment-products.md)) and Ordered Products tag for the unit count. | | **Quality** | Two of the three counts (Total / Approved / Rejected) per [Data Quality](/management-portal/oee/equipment/tag-mapping/data-quality.md). | The validation summary on the Equipment tab surfaces missing prerequisites once you switch **OEE Enabled** on, but it’s easier to wire things in the order recommended in [Equipment](/management-portal/oee/equipment.md#recommended-order-to-fill-the-tabs). *** ## Saving Equipment Settings participates in the page-level Save / Cancel toolbar. Changes here are saved together with any pending changes on the other Equipment tabs (Tag Mapping, Shifts, Planned Stops, Stop Causes, States, Products). The tree is locked while there are unsaved changes. Validation errors (missing Total OEE Target, missing per-pillar Target on an enabled pillar) are surfaced under the offending field and the **Equipment** tab header is marked invalid until they’re resolved.