> For the complete documentation index, see [llms.txt](https://docs-dloop.decisyon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-dloop.decisyon.com/decisyon-lean-operations-optimizer-loop/tier-meeting/tier-meeting-l1.md).

# Tier Meeting L1

## Introduction

The Tier L1 module supports the operational meetings held on the production line **at the end of each shift**. It is the primary touchpoint for operators, team leaders and shift supervisors to review the performance of the shift that has just ended and to address immediate operational issues.

The board always refers to **one shift at a time**: by default, the **last closed shift**. For example, with shifts 06:00–14:00, 14:00–22:00 and 22:00–06:00, the L1 meetings take place at 14:05, 22:05 and 06:05; at 15:00 the board shows the 06:00–14:00 shift, while the shift in progress is not visible until it closes.

The system centralizes Key Performance Indicators (KPIs) grouped into configurable categories such as **Safety, Quality, Delivery, Inventory, and Productivity**. Data is populated through automated system integration (MES/ERP), manual entry, or bulk Excel imports. Beyond data visualization, the module enables real-time task management, allowing teams to create, modify, and escalate actions directly during the meeting to ensure continuous improvement and accountability across organizational levels.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FD7DdUkgfTpvt738cSvo4%2Fimage.png?alt=media&amp;token=d9f1b8e3-97af-4bc7-90e8-f052553b386c" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
&#x20;For an overview of how shifts drive the data shown on each Tier Board, see the **How shifts drive the Tier Boards** section of the [Tier Meeting ](/decisyon-lean-operations-optimizer-loop/tier-meeting.md)page.
{% endhint %}

### Overview

Access the **Tier Meeting L1** page from the Lean Operations Optimizer main menu to begin the review of the shift.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FN3KXhjaoc9CU7PAl444W%2Fimage.png?alt=media&amp;token=3a442d5a-d422-4496-bc04-7defc79e8f6b" alt=""><figcaption></figcaption></figure>

The upper section of the page features the selectors that define the context of the board:

* **Module** and **Line**: Select the production area and line to be reviewed.
* **Date**: The day of the shift to be reviewed.
* **Shift**: The shift to be reviewed. Only one shift can be selected; by default, the board shows the last closed shift.

The control buttons allow for the following operations:

* **New Action**: Records a task or issue identified during the meeting.
* **Safety event**: Records a safety event for the selected context.

The left-hand sidebar lets you switch between three views without leaving the page:

* **Board**: The default view — KPI tiles and open actions for each category.
* **KPI Overview** : A monthly performance calendar for each KPI.
* **Actions Overview**: A full-page table of all the Tier L1 actions.

The bottom section of the page contains a summary table:

* **Open Actions section:** The **Open actions** section at the bottom of each category column displays the actions created on the **selected date** and assigned to Tier L1.

## How to ..

### Define the Operational Context

Upon accessing the Tier Meeting L1 page, the user defines the context of the board: the plant hierarchy (module and line) and the shift to be reviewed.

{% stepper %}
{% step %}

#### Select Module

Selection of the specific production module or area (e.g., Module 1) to filter relevant operational data.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FEXRYX6ufdHrcQLCcuVKI%2Fimage.png?alt=media&amp;token=399255bc-adeb-42d8-811c-e8b9d90769e7" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Select Line

Selecting a specific production line (e.g., LINE 1 M1) within the selected module.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FDCFxjWvI9egwufrqCclv%2Fimage.png?alt=media&amp;token=0dae7b45-5f08-48fc-9487-c97c92aefb4d" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Select date

Select the day of the shift to be reviewed. By default, the date is the day of the last closed shift. For a night shift ending on the next day (e.g., 22:00–06:00), the date is the day on which the shift starts.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FveY9W9O4j6XKErDoaUhv%2Fimage.png?alt=media&amp;token=6926f3c3-5283-49a2-88c2-cd7e32e6ad8e" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Select Shift

Select the shift to be reviewed from the **Shift** dropdown. The list contains the shifts assigned to the selected line on the selected date, identified by their **Shift Description** (e.g., *Shift1*).

* When the page is opened, the board shows the **last closed shift**.
* Only **one shift** can be selected at a time: shifts cannot be aggregated or combined.
* The shift currently **in progress** and future shifts are not available: their data is not visible until the shift closes.

The shifts available for each line are those configured in **Plant Configuration › Shifts** and assigned to the line in the **Shift-Line Association**. On a non-working day, no shift is available.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FWdPBNfvdBZvSRcBt0IET%2Fimage.png?alt=media&amp;token=427b0255-4254-4b36-a5da-ab48f4228724" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### KPI Visualization and Analysis

After selecting the context, the board shows the KPIs of the selected shift, organized in columns by category (e.g., **Safety**, **Quality**, **Delivery**, **Inventory**, **Productivity**). Each tile shows the value of the KPI for the shift compared to its target, color-coded according to the KPI's Target Tendency: green when on target, red when off target, neutral when no value has been entered yet (*No value*).

**Entering or correcting a KPI value**

For manual KPIs, click the ✏ icon next to the value to enter or correct the value and the target directly from the board, then click ✓ to save or ✗ to cancel.

* Values are recorded for the **shift being viewed** — by default, the last closed shift.
* Data can never be entered for the shift in progress or for future shifts.
* To correct the values of older shifts or days, you can also use **Raw Data › KPI Raw Data**.

Automatic KPIs are read-only: their value is populated by the system.

For a complete description of the tiles, color coding and badges, see the **Board Mode** section of the Tier Meeting page.

#### **KPI Trend**

Click the trend icon on a KPI tile to open the **Trend kpi** overlay. It shows, for the selected category, module and line, a bar chart for every KPI of the category over the last 7 days, with the target line.

* Each bar represents the **total of the day**, not a single shift.
* Days that were not worked show no value.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FKjP6SYjSeU4eiyCfmotz%2Fimage.png?alt=media&amp;token=62e40387-261d-4cf9-a02f-1c0bd1764070" alt=""><figcaption></figcaption></figure>

**KPI Overview**

Select the KPI Overview icon in the left-hand sidebar to display a monthly calendar for each KPI. As in the KPI Trend, each day shows the total of the day (green when on target, red when off target); days that were not worked show no value.

For details on how to read the calendar, see the KPI Overview section of the Tier Meeting page.

**Calendar**

Select the **Calendar** icon in the left-hand sidebar to display a monthly calendar for each KPI. As in the KPI Trend, each day shows the **total of the day** (green when on target, red when off target); days that were not worked show no value.

For details on how to read the calendar, see the **Calendar Mode** section of the Tier Meeting page.

### Action Escalation

Trigger the escalation process to move an unresolved L1 action to the L2 management level for further intervention.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FFD8jeDIk2pYQfLwO5qXe%2Fimage.png?alt=media&amp;token=f4609e51-e2e5-4f27-abff-8d60f40155ed" alt=""><figcaption></figcaption></figure>

### New Action Creation

The **New Action** button facilitates the immediate recording of tasks or issues identified during the meeting.&#x20;

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FyCyJDLX1JBLYuYW3xLeI%2Fimage.png?alt=media&amp;token=97d38343-d4ef-417c-80c5-4e8766f2ff23" alt=""><figcaption></figcaption></figure>

You can also create an action already linked to a specific KPI by clicking **+ Action** on its tile.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FqhIH2tRlSZH3LqM7Nu4s%2Fimage.png?alt=media&amp;token=40193d09-bdfc-47c0-957c-ff653aaed26b" alt=""><figcaption></figcaption></figure>

The form allows for the definition of the key parameters of the action:

* **Context:** **Category**, **Module**, **Line** and **Shift** — pre-filled from the board; the Category is locked when the action is created from a KPI tile.
* **Shift:** the shift the action refers to, shown with its time range (e.g., *Shift (6:00 - 14:00)*). It is pre-filled with the shift selected on the board and can be changed from the dropdown.
* **Hierarchy:** **Source Tier** (the level where the issue was identified) and **Target Tier** (the level to which the action is assigned for resolution).
* **Identification:** a descriptive **Title** and a **Description**, with the **AI Enhance** tool to improve the text and the **Voice** tool to dictate it.
* **Time Management:** the **Creation Date** is set automatically by the system; use the calendar to select the **Due Date**.
* **Classification:** **Priority**, **Severity** and **Status**.
* **Responsibility:** the **Raiser** (the person who logged the action, filled in automatically with the current user), the **Team** and the **Owner** (the person accountable for completing it).

Fields marked with an asterisk (\*) are required: **Category**, **Module**, **Line**, **Title**, **Description**, **Due Date**, **Team** and **Owner**.

{% hint style="info" %}
Once created, the action is displayed in the **Open actions** section of its category, for its creation date, and in the **Actions Overview**, provided that the assigned level remains Tier L1. If a different Target Tier is selected, the action is only visible on the board of that Tier.
{% endhint %}

For more details about the creation of actions, see the documentation.

{% content-ref url="/pages/69e108e1e1e43143581d5803f7e0f62e65c5dd37" %}
[Create Action](/decisyon-lean-operations-optimizer-loop/actions/create-action.md)
{% endcontent-ref %}

### Actions Overview L1

To view the consolidated list of all Tier L1 actions, select the Actions Overview icon in the left-hand sidebar. The view replaces the board with a table of all actions, automatically filtered according to the Module and Line selected on the board. Unlike the board, this view has no time filter: it displays the full action log regardless of the creation date.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2Fm137GIyPqraQmX4UVpd5%2Fimage.png?alt=media&amp;token=f0709aa4-43c4-4274-a293-386ebc11f584" alt=""><figcaption></figcaption></figure>

For each action, the table shows title, category, source and assigned tier, priority, status, raiser, owner, creation date and due date. A red indicator identifies overdue actions, whose Due Date is earlier than the plant's current date.

At the end of each row, two management options are available:

* [**Edit:**](/decisyon-lean-operations-optimizer-loop/actions/edit-action.md) modify the content, deadlines, or assignees of the action.
* **Escalate**: escalate the action to the next level (Tier L2) when the resolution requires tactical intervention.

#### Action Escalation

Escalate an unresolved L1 action to the Tier L2 management level using the escalation icon (↗) in the Actions Overview, or the Tier selector of the action in the **Open actions** section of the board.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FbN5hPAxe1WZaqMjMciAo%2Fimage.png?alt=media&amp;token=76cb8fa4-4431-4595-8500-2ed2dbdc3fbe" alt=""><figcaption></figcaption></figure>

#### Safety Event

Click the **Safety event** button to open the list of safety events recorded for the selected context and add, edit, clone or delete events. The data entered is linked to the *Safety Events* KPI in the **SAFETY** column of the board.

For the full procedure, see the **Safety event** section of the Tier Meeting page.
