> 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-documentation-of-the-logic/advantages-and-benefits.md).

# Advantages & benefits

#### 1.4 Advantages of Selmo

✅ **Structured modeling**\
→ No loose code snippets, but consistent logic

✅ **Automated documentation**\
→ Signal directory, safety logic, process flow, parameters, HMI

✅ **CE-compliant and verifiable**\
→ Restart behavior, reset conditions, fault reactions documented

✅ **Modular structure**\
→ Each station/function as its own SEQ → reusable, maintainable

✅ **Safe operation**\
→ Only allowed actions visible, diagnostics automatic, HMI guided

### 🎯 **Core benefit of Selmo summed up**

* 🔍 **Clarity** – What happens when, why, and what is missing
* 🛠️ **Maintainability** – All processes are modeled, not "programmed"
* 🚀 **Commissioning becomes faster**, because errors are visible earlier
* 🧠 **Knowledge is documented instead of hidden**
* 🔁 **Standard instead of individual chaos**

### 🚫 **Problems of classic PLC programming**

1. **Unstructured code growth**
   * Programs grow historically – often without clear separation of logic, engineering and operation
   * Hardly traceable for third parties
2. **Lack of transparency**
   * Why is something not running? → hard to find out
   * State logic and signal behavior often hidden deep in the code
3. **Time-consuming troubleshooting**
   * No direct link between fault cause and HMI message
   * Fault diagnosis usually must be programmed manually
4. **Unclear operator guidance**
   * Operators do not see what is expected or what is missing
   * Manual operation often set up insecurely or illogically
5. **Lack of reusability**
   * Code is too individual, hard to standardize
   * No clear structure for copy-paste or modular processes
6. **High training and documentation effort**
   * New employees need a long time to find their way around
   * Documentation often incomplete or outdated

***

### ✅ **Advantages & direct benefits of Selmo – the solution**

| Problem                           | Solution with Selmo                                           | Benefit                                                                |
| --------------------------------- | ------------------------------------------------------------- | ---------------------------------------------------------------------- |
| 🔄 Unstructured code              | **Model-based structure** (Plant → HW-Zone → Sequence → Zone) | Clear, clean structure instead of grown code blocks                    |
| 🕵️‍♂️ Lack of transparency       | **Bit control (S, i, 0)** + **HMI linking** automatic         | Operator immediately sees what the machine expects or what is blocking |
| 🧯 Time-consuming troubleshooting | **Automatic diagnosis** from model state                      | No manual fault logic needed – faults are located and explained        |
| ❓ Unclear operation               | **Sequence Check** + **MXIC** + **Zone status in the HMI**    | Operator is guided – always knows what is allowed and what is missing  |
| 🧩 No reusability                 | **Standardized zone structure** (One zone = one function)     | Modules can be duplicated, parameterized, maintained                   |
| 📚 High training effort           | **Visual process model + readable logic**                     | Everyone sees at a glance what is happening – no more "black box"      |
| ❌ Missing safety concept          | **Integrated interlocks, CMZ, MXIC**                          | Safety is part of the model – no additional code, no logic gaps        |
| ⚙️ Different manual/auto logic    | **Unified model for both**                                    | Same behavior in manual & automatic – traceable and safe               |

***

###


---

# 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-documentation-of-the-logic/advantages-and-benefits.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.