> 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/shift-assignment.md).

# Equipment Shift Assignment

Optionally assign one of the Site's Shift Calendars so OEE facts get tagged with the active shift for downstream slicing.

The **Shifts** tab on an Equipment selects one of the parent Site’s Shift Calendars and tags every OEE fact this equipment produces with that shift. The OEE engine itself calculates and stores facts **regardless of whether a shift is assigned** — the shift is metadata that lets downstream queries and dashboards filter or group results by shift.

The tab is intentionally minimal — shifts themselves are defined once per Site (see [Site Shifts](/management-portal/oee/sites/site-shifts.md)), and each equipment just picks one.

***

## Fields

| Field                | Required | Notes                                                                                                                                                                                                                     |
| -------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Shift Assignment** | Optional | Drop-down listing every Shift Calendar defined on the Site (`Production`, `Office`, `Continuous`, …). Pick exactly one if you want OEE results to be filterable by shift; leave unassigned if you don’t need the slicing. |

The Site’s **time zone** is shown next to the heading so you don’t have to remember which zone the schedule is interpreted in.

***

## Read-only scheduler preview

Below the drop-down is a read-only scheduler showing the selected calendar’s shifts plus this equipment’s [Planned Stops](/management-portal/oee/equipment/planned-stops.md) on top. This is purely a verification view — you can switch between Day / Week / Month / Timeline / Agenda using the toolbar, but you cannot create, edit or delete events here.

<figure><img src="https://570593659-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYMGRODsc2QD3N3wmfwTl%2Fuploads%2Fgit-blob-48eacc9e4aa62af4385216216409d82ffb982170%2Foee-shift-scheduler-week.png?alt=media" alt=""><figcaption><p>Equipment Shifts tab — the Shift Assignment drop-down selects the calendar; the read-only scheduler below shows the assigned calendar's shifts for verification</p></figcaption></figure>

* To change a **shift**, edit it on the Site’s [Shifts](/management-portal/oee/sites/site-shifts.md) tab.
* To change a **planned stop**, switch to this equipment’s [Planned Stops](/management-portal/oee/equipment/planned-stops.md) tab.

The combined view is useful for spotting:

* Planned stops that fall **outside** any shift (they have no effect — there’s no scheduled time for them to subtract from).
* Gaps in shift coverage where the equipment is expected to run but no shift is defined.
* Overlap between two calendars when reorganizing — assign the new calendar and verify the result before saving.

***

## What changes downstream

When the assignment is saved:

* New OEE facts the engine writes are **stamped with the new shift’s id and metadata**, so dashboards and queries pick up the change forward in time.
* Existing **Planned Stops** keep their absolute times — they don’t move with the calendar change. Verify the overlay still makes sense after a reassignment.
* Facts already stored against the previous calendar are not rewritten; the change applies forward only.

{% hint style="info" %}
A common pattern is one **Production** calendar shared by every line in a plant, and a separate **Continuous** calendar (24/7) for buffers and storage equipment that doesn’t follow shifts. Equipment that doesn’t need shift-based slicing can also be left unassigned — OEE is still calculated, just without a shift tag on the facts.
{% endhint %}

***

## Validation

| Condition                                      | Behavior                                                                                                                                        |
| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Shift Assignment unset                         | Allowed. The engine still produces OEE facts; the shift fields on each fact are emitted as empty (`ShiftId = empty GUID`, `ShiftDetails = {}`). |
| Selected calendar has zero shifts defined      | Allowed (useful for staging a calendar before populating it). Facts carry the calendar id but no shift events to filter on.                     |
| Selected calendar is deleted at the Site level | The dropdown shows the saved id without a label; reassign before saving any other change.                                                       |

***

## Related

* [Site Shifts](/management-portal/oee/sites/site-shifts.md) — define the calendars and their shift events.
* [Planned Stops](/management-portal/oee/equipment/planned-stops.md) — recurring downtime that subtracts from scheduled time inside the assigned shift.