> For the complete documentation index, see [llms.txt](https://infosys.selmotech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://infosys.selmotech.com/selmo-solution/selmo-solution-en/selmo-structure-and-standard/selmo-technical-standard-and-structure/selmo-method-in-practice/commissioning-ibn-with-selmo.md).

# 🔷 Commissioning (IBN) with Selmo

###

**Inputs – What is needed – What is done – What is the result**

***

#### 🔹 1. **Inputs – What is needed?**

| Category                                       | Description                                                |
| ---------------------------------------------- | ---------------------------------------------------------- |
| **Finished, exported control model**           | PLCOpen XML imported, control code loaded into PLC         |
| **HMI project created and loaded**             | HMI generated from Selmo model, connected to control       |
| **Hardware commissioned**                      | Sensors, actuators, communication are available            |
| **Signal verification completed**              | Feedback of all inputs/outputs checked with real wiring    |
| **Commissioning checklist / release criteria** | Specifications for tests, safety functions, operator logic |
| **Test parameters**                            | Times, repetitions, HMI approvals for step operation etc.  |

***

#### 🔹 2. **What is done? (Activities during commissioning)**

| Step                                     | Description                                                            |
| ---------------------------------------- | ---------------------------------------------------------------------- |
| **Test automatic release**               | Check behavior when automatic release button is pressed                |
| **Run through states (sequence)**        | Observe and log state changes in automatic mode                        |
| **Test manual operation (MXIC)**         | Each state is triggered individually, manual movement is checked       |
| **Simulate error messages (i, CMZ)**     | Deliberately trigger interlock and CMZ functions and validate response |
| **Check operator guidance (S-behavior)** | Expected operator actions and HMI texts in automatic mode              |
| **Visualize signal status**              | Real-time tracking via HMI: states, signal status, diagnostics         |
| **Test limits and parameters**           | Check all parameterized values for correctness and effectiveness       |
| **Test sequence cross (if present)**     | Validate transitions between sequences                                 |

***

#### 🔹 3. **Outputs – What is the result of the commissioning?**

| Result                                     | Description                                               |
| ------------------------------------------ | --------------------------------------------------------- |
| ✅ **Validated model execution**            | All states, zones, signals behave as defined in the model |
| ✅ **Safe manual and automatic function**   | Controlled and secured behavior in all operating modes    |
| ✅ **Error handling works**                 | Interlock deviations and safety functions act correctly   |
| ✅ **Operator guidance correctly visible**  | HMI reliably displays states, prompts, messages           |
| ✅ **Parameters checked and adjusted**      | All process-relevant values are aligned                   |
| ✅ **Commissioning documentation complete** | All tests, releases and acceptances documented traceably  |

***

#### 🧩 Conclusion:

Commissioning in Selmo is not "trial and error", but a **model-based proof**, that the machine does what was specified in the model.

➡️ **The model is the reference – the PLC executes it.**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://infosys.selmotech.com/selmo-solution/selmo-solution-en/selmo-structure-and-standard/selmo-technical-standard-and-structure/selmo-method-in-practice/commissioning-ibn-with-selmo.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.