> 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.md).

# Decisyon Lean Operations Optimizer (LOOP)

User & Administration Manual

## <i class="fa-building-magnifying-glass" style="color:$primary;">:building-magnifying-glass:</i> Overview

**Lean Operations Optimizer (Decisyon LOOP)** is an enterprise digital platform designed to standardize, structure, and accelerate daily factory management routines from the production line to plant-level strategic governance.

LOOP replaces manual and disconnected tools such as paper, whiteboards, spreadsheets, and email threads with a unified digital workspace powered by Artificial Intelligence (AI).

The platform enables:

* Real-time monitoring of Key Performance Indicators (KPIs)
* Structured anomaly detection and escalation
* Digital Tier meeting execution
* Centralized action accountability
* Continuous improvement across operational levels

LOOP operates across two integrated domains:

* [**Plant Configuration**](#id-1.-plant-configuration-area-amministratore) **(Administration Layer)**
* [**Operational Boards**](#daily-operations) **(Daily Management Layer)**

Together, these layers create a structured, data-driven Lean governance system.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2Ffarm1lsSArSr1ljWHOeK%2Fimage.png?alt=media&amp;token=9539dd4f-2238-43ca-92a1-3d7dd6e59748" alt=""><figcaption></figcaption></figure>

#### How time drives your data

In LOOP, every KPI value is tied to a **shift**. The shift is the lowest level of time granularity: data is recorded shift by shift, according to the shifts configured for each line.

Each Tier Board then reads the data at the time granularity and at the hierarchy level that match its meeting:

| Tier        | When the meeting takes place | Data shown                | Time granularity     | Hierarchy level |
| ----------- | ---------------------------- | ------------------------- | -------------------- | --------------- |
| **Tier L1** | At the end of each shift     | The **last closed shift** | Single shift         | Module / Line   |
| **Tier L2** | Once a day                   | **Yesterday**             | Day (all its shifts) | Module          |
| **Tier L3** | Once a day                   | **Yesterday**             | Day (all its shifts) | Plant           |

**Example** — A plant works three shifts per day: 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 L1 Board shows the data of the 06:00–14:00 shift only; the shift currently running is not visible until it closes.
* The next morning, the L2 and L3 Boards show the previous day as a whole, combining the three shifts.

Data can only be entered for the past, never for the future. From the L1 Board, values always refer to the **last closed shift**: at 15:00, a value entered on the L1 Board is recorded for the 06:00–14:00 shift.

How shift values are combined into a daily value depends on the **Aggregation Rule** set for each KPI: values can be summed (**SUM**), averaged (**AVG**), or entered manually at each Tier, with no roll-up from Tier 1.

## <i class="fa-user-gear" style="color:$primary;">:user-gear:</i> Administration

The Administration area is dedicated to the initial setup and structural governance of the platform.

The Application Administrator configures:

* Physical assets (plant hierarchy)
* Shift models and calendars
* KPI structure and categorization
* Tier assignments
* Attendance roles
* Safety taxonomies

This ensures that the digital environment accurately reflects the real operational structure of the plant.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FrThFjGXCUquIgIqahtlp%2Fimage.png?alt=media&amp;token=c79318a5-74fc-4156-9b8f-3e79f6229812" alt=""><figcaption></figcaption></figure>

## <i class="fa-gear-complex" style="color:$primary;">:gear-complex:</i> Plant Configuration

Plant Configuration defines the factory’s digital architecture.

Through dedicated configuration boards, the administrator creates the plant’s Digital Twin, mapping the relationships between physical assets and organizational levels. This ensures that every data point whether KPI value, downtime event, or safety issue is correctly contextualized and aggregated.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FFtwKlIL5Rkb4G1kEtWQ9%2Fimage.png?alt=media&amp;token=98b6a97f-8260-4270-aa30-2ee8a4873c07" alt=""><figcaption></figcaption></figure>

#### Plant Hierarchy Configuration <a href="#a.-plant-hierarchy-configuration" id="a.-plant-hierarchy-configuration"></a>

The hierarchy configuration is the structural backbone of LOOP.

It defines the full physical structure:

**Modules → Lines → Machines → Components**

This layered model ensures that:

* An anomaly at component level aggregates correctly to machine
* Machine data rolls up to line performance
* Line performance contributes to module and plant KPIs

#### **Configuration Boards**

* **Plant Configuration** - Defines the primary plant entity within the system, including geographical and production boundaries.
* **Module Configuration -** Creates logical production areas that group multiple lines for simplified monitoring and Tier aggregation.
* **Line Configuration -** Defines individual production lines, their module association, and production targets.
* **Machine Configuration -** Configures machine-level details to support monitoring of availability, performance, and reliability.
* **Component Configuration -** Defines critical subcomponents for maintenance diagnostics and root cause analysis.

This hierarchical structure enables both macro visibility and micro-level traceability.

*For a comprehensive guide on all administrative settings, please refer to the*

{% content-ref url="/pages/wW2g7I33jf5UG4TlOf84" %}
[Plant Hierarchy](/decisyon-lean-operations-optimizer-loop/plant-configuration/plant-hierarchy.md)
{% endcontent-ref %}

## <i class="fa-user-clock" style="color:$primary;">:user-clock:</i> Shift Management

Accurate Lean governance requires performance to be measured only during actual working time — and at the right level of detail.

The Shift Management module defines the operational "heartbeat" of the plant. Shifts are not only a scheduling tool: they are the **time unit in which all KPI data is recorded**, and the basis on which Tier Boards display and aggregate performance.

The module manages:

* Work rotations and shift times
* Calendar exceptions
* Production downtime windows
* The link between the shifts and the production lines shown on the Tier Boards

**Key Components**

* **Shift Pattern -** Defines recurring rotation logic (e.g., 3-shift cycle, 2-shift cycle, single shift).
* **Shift Definition -** Defines the shifts of each pattern, with their start and end times. Each shift becomes a data slot for KPI values.
* **Shift-Line Association -** Assigns a shift pattern to each production line for each day of the week. This is what links the shifts to the Tier Boards.
* **Non-Working Days -** Defines holidays, maintenance shutdowns, or planned closures to prevent KPI distortion.
* **Shift Calendar -** Consolidated view of the resulting schedule: shifts per line and day, with start, end and duration (in minutes).

{% hint style="info" %}
Plants that work a single shift per day use the same configuration: a Shift Pattern with one Shift Definition.&#x20;
{% endhint %}

*For a comprehensive guide on all administrative settings, please refer to the*

{% content-ref url="/pages/KC4JzUZh0EudSzJhmHXO" %}
[Shifts](/decisyon-lean-operations-optimizer-loop/plant-configuration/shifts.md)
{% endcontent-ref %}

### Tier Configuration <a href="#tier-configuration" id="tier-configuration"></a>

The Tier Configuration board governs how KPIs are strategically distributed across organizational levels:

* Tier 1 (Operational)
* Tier 2 (Tactical)
* Tier 3 (Strategic)

This ensures the correct performance indicators are reviewed at the appropriate frequency and decision level.

### KPI Configuration <a href="#tier-configuration" id="tier-configuration"></a>

KPI Configuration is the technical engine of LOOP.

It standardizes the plant’s performance language by defining:

* KPI categories
* Units of measurement
* Target logic
* Data source (automated integration or manual input)

#### KPI Structure

* **KPI Category -** Classifies KPIs into continuous improvement pillars:
  * Safety
  * Quality
  * Delivery
  * Inventory
  * Productivity
* **KPI Group -** Aggregates KPIs for structured meeting visibility and reporting.
* **KPI List** - Master repository of all system KPIs. Administrators determine which KPIs are visible and editable on Tier boards, and how each KPI is aggregated from shift to day through its **Aggregation Rule**.

### KPI Association (Tier & Line Mapping)

This board controls:

* Which KPI appears on which production line
* At which Tier level it is reviewed

This prevents KPI misalignment and ensures governance clarity.

*For a comprehensive guide on all administrative settings, please refer to the*

{% content-ref url="/pages/jK9CsJQSz8FSrKBUeEWA" %}
[KPI Configuration](/decisyon-lean-operations-optimizer-loop/plant-configuration/kpi-configuration.md)
{% endcontent-ref %}

### Attendance Management

Operational stability requires structured workforce planning.

This section enables administrators to:

* **Attendance Roles -** Define professional profiles (Supervisor, Technician, Maintenance Lead, etc.).
* **Attendance Configuration -** Associate required roles to shifts to guarantee proper coverage.This supports structured staffing alignment with production demands.

*For a comprehensive guide on all administrative settings, please refer to the*

{% content-ref url="/pages/DBdzNWAZWUwve8FzhNQ1" %}
[Attendance](/decisyon-lean-operations-optimizer-loop/plant-configuration/attendance.md)
{% endcontent-ref %}

### Safety Configuration

Safety is a foundational Lean pillar. This module standardizes safety reporting and categorization to enable rapid risk mitigation and analytics.

**Safety Category**\
Defines classification of risk types such as:

* Electrical hazards
* PPE violations
* Falls
* Unsafe conditions

Standardization improves trend analysis and compliance tracking.

*For a comprehensive guide on all administrative settings, please refer to the*

{% content-ref url="/pages/6noUt2k9encEd1QeQ6vM" %}
[Safety](/decisyon-lean-operations-optimizer-loop/plant-configuration/safety.md)
{% endcontent-ref %}

### System Configuration (Read-Only Reference)

This section acts as a technical reference library summarizing system-level parameters:

* Frequency Options
* Safety Types
* Attendance Status Definitions

It ensures transparency into the logic powering the application.

### Raw Data Management

Raw Data boards provide unfiltered access to system data for auditing, validation, and bulk modification.

**KPI Raw Data -** Global view of Target and Actual values across all lines and dates.

Color logic is driven by Target Tendency:

* Lower-is-better → Green when below target
* Higher-is-better → Green when above target

**Pareto Raw Data -** Manages detailed occurrence data for downtime and defects.

**Safety Raw Data -** Central repository of accidents, near-misses, and unsafe conditions.

### Data Import Tools

Bulk data upload through standardized Excel templates:

* Import KPI Data (values and targets per shift, or per day)
* Import Pareto Data
* Import Safety Data

Each template includes mapping guidance to ensure correct system alignment.

## <i class="fa-user-pen" style="color:$primary;">:user-pen:</i> Daily Operations

The Daily Operations layer is designed for:

* Line operators
* Shift supervisors
* Department managers
* Plant leadership

It transforms performance visibility into structured action and escalation.

<figure><img src="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FgU5rchPSFpvKUYK0PfKx%2Fimage.png?alt=media&amp;token=2499e4cf-a5bf-4999-a298-83803eca1e25" alt=""><figcaption></figcaption></figure>

## <i class="fa-people-group" style="color:$primary;">:people-group:</i> Meeting & Governance Structure

LOOP digitizes Lean Tier meetings to ensure disciplined execution and traceability.

### Tier Governance Model

The Tier system ensures that the right information reaches the right decision-maker at the right time — and at the right level of detail.

**Tier L1 – Operational (End of Shift, Module / Line)**

Primary objective: Immediate problem solving on the shift that has just ended.

* Meeting held at the end of each shift
* KPI dashboard for the **last closed shift** — one shift at a time
* Shop-floor action creation
* Immediate escalation
* Rapid anomaly containment

Used by operators, team leaders and shift supervisors.

**Tier L2 – Tactical (Daily, Module)**

Primary objective: Area-level coordination.

* **Yesterday's** performance, aggregating all the shifts of the day
* Aggregated module KPIs
* Recurring issue analysis
* Action validation and support
* Daily and monthly trend toggling

Supports cross-line synchronization.

**Tier L3 – Strategic (Daily, Plant)**

Primary objective: Plant-level governance.

* **Yesterday's** performance, aggregating all the shifts of the day
* Strategic plant-level KPI review
* 7-day historical trend analysis
* Global action oversight
* Formal meeting traceability

<table data-view="cards"><thead><tr><th align="center"></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td align="center"><p><a href="/decisyon-lean-operations-optimizer-loop/tier-meeting/tier-meeting-l1.md"><strong>Tier Meeting L1</strong></a></p><p>Focuses on immediate coordination and rapid resolution of the issues of the shift that has just ended, directly on the shop floor, to maintain production flow.</p></td><td></td><td data-object-fit="contain"><a href="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FbkhQQkpHCdMYqzSqpvKA%2FTier%20L1.png?alt=media&amp;token=6826a890-c5f1-476d-8e15-3f43948314b4">Tier L1.png</a></td></tr><tr><td align="center"><a href="/decisyon-lean-operations-optimizer-loop/tier-meeting/tier-meeting-l2.md"><strong>Tier Meeting L2</strong></a><br>Aggregates the previous day's KPI data, combining all its shifts, for specific production modules. It facilitates the identification of recurring trends versus isolated events, ensuring formal tracking of actions and decisions.</td><td></td><td data-object-fit="contain"><a href="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FGFmVRg5IfNs4qZIGI0yZ%2FTier%20L2.png?alt=media&amp;token=be30fc99-dda7-4382-afa9-b14a38c1e7dc">Tier L2.png</a></td></tr><tr><td align="center"><p><a href="broken://pages/b5052e02e4b95841c7cb5735936e5227819f9c9f"><strong>Tier Meeting L3</strong></a></p><p>Centralizes the previous day's plant-level performance data, combining all its shifts. It manages systemic issues and strategic actions using data integrated from factory systems (MES/ERP).</p></td><td></td><td data-object-fit="contain"><a href="https://2053082126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqrHVhCk9lMTXtHEk2BVJ%2Fuploads%2FJPvG21jFJuKeuU3ofdBl%2FTier%20L3.png?alt=media&amp;token=b4fe3da0-47e4-421e-8a40-8a32f2c6257a">Tier L3.png</a></td></tr></tbody></table>

## <i class="fa-gear-complex" style="color:$primary;">:gear-complex:</i> Core Functionalities Across All Tiers

To ensure consistency, LOOP maintains a standardized interface across L1, L2, and L3.

### Context Filtering

Before analysis, users define the context of the board:

| Filter | Tier L1                                                     | Tier L2                   | Tier L3                   |
| ------ | ----------------------------------------------------------- | ------------------------- | ------------------------- |
| Module | ✔                                                           | ✔                         | —                         |
| Line   | ✔                                                           | —                         | —                         |
| Shift  | ✔ (one shift at a time — defaults to the last closed shift) | —                         | —                         |
| Date   | ✔                                                           | ✔ (defaults to yesterday) | ✔ (defaults to yesterday) |

This ensures KPI relevance and contextual accuracy.

### KPI Management

Users can:

* View performance vs. target
* Edit KPI values
* Upload Excel data
* Synchronize parameters

Data can originate from MES/ERP integration or manual input.

### Action & Task Management

The Action Overview board centralizes all corrective and preventive actions.

Users can:

* Create new actions
* Assign owner and responsible party
* Define due dates
* Monitor status and priority
* Escalate to higher Tier

This enforces accountability and structured follow-through.

### Meeting Execution & Traceability

In Tier L2 and L3:

* “Start Meeting” activates session recording
* Timer tracks duration
* Decisions are digitally recorded
* Actions can be created and escalated live

This ensures governance discipline and full traceability.

*For a comprehensive guide on how to use this board, please refer to the*

{% content-ref url="/pages/0cf0f254792015eb04c1251e2f215cbe1c4a77c4" %}
[Tier Meeting L2 & L3](/decisyon-lean-operations-optimizer-loop/tier-meeting/tier-meeting-l2-and-l3.md)
{% endcontent-ref %}

## <i class="fa-user-key" style="color:$primary;">:user-key:</i> Access & Authentication

#### **Decisyon App Composer Portal**

Secure entry gateway to the Decisyon ecosystem.

*For a comprehensive guide on how to use this board, please refer to the*

{% content-ref url="/pages/fm23ioOCt97GgclO1PdF" %}
[Decisyon App Composer Portal](/decisyon-lean-operations-optimizer-loop/decisyon-app-composer-portal.md)
{% endcontent-ref %}

#### **Identity Provider Selection**

Supports Single Sign-On (SSO) integration, including providers such as Google, ensuring secure and compliant authentication.

#### **Lean Operations Optimizer Tile**

Launches the LOOP workspace where users manage:

* Digital meetings
* KPIs
* Escalations
* Action workflows