> 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-how-it-works/selmo-training/chapter-8-the-new-state-of-the-art.md).

# Chapter 8 – The new state of the art

**Summary:**\
Chapter 8 concludes the theoretical part.\
It describes why Selmo represents the new state of the art:\
Because it formalizes machine behavior, integrates safety into the structure, and permanently documents knowledge.\
The reader recognizes that Selmo is not a new PLC, but a **new way of thinking** –\
a language that connects machines, people and standards.\
Selmo fulfills the central demands of modern automation: determinism, traceability, sustainability and transparency.

The *state of the art* describes, **what is technically justifiable and reproducibly possible today**.\
Selmo raises this standard to the next level:

> **With Selmo the process becomes code – and the code becomes certainty.**

Thus Selmo not only meets legal requirements, but defines, **how machine behavior in the age of digital responsibility** must be designed:\
**formal, verifiable, safe and transparent.**

<details>

<summary>Why Selmo is the new state of the art</summary>

Selmo redefines the state of the art **in machine automation**, by **formally describing the behavior of the machine and automatically translating it into control code.**\
In doing so Selmo meets key criteria that constitute the state of the art:

| Criterion            | Description                                                          | Selmo reference                                                      |
| -------------------- | -------------------------------------------------------------------- | -------------------------------------------------------------------- |
| **equivalent**       | Machine behavior is clearly documented and traceable.                | The Selmo process model formally maps every signal and every state.  |
| **safety**           | Fault states and state transitions are deterministically verifiable. | Interlock (`i`), Sequence Check (`S`) and CMZ ensure safe states.    |
| **Reproducibility**  | The behavior can be reproduced identically at any time.              | Model = Code = Documentation – automatically synchronized.           |
| **Error prevention** | Programming errors due to interpretation are eliminated.             | Code is generated from formal models, not written manually.          |
| **Efficiency**       | Engineering effort and commissioning time are reduced.               | Standardized structure, automatic diagnosis, clearly defined states. |
| **Compatibility**    | Existing standards (IEC 61131, PLCopen XML) are integrated.          | Selmo exports and imports standards-compliant code.                  |

Selmo thus shifts the boundary of the state of the art **from programming to modeling**:\
The human describes **the process**, no longer the code.\
The machine behaves **provably exactly as**, the process was defined.

</details>

<details>

<summary>Proof of the state of the art with Selmo</summary>

Selmo enables manufacturers **to demonstrably comply with the state of the art**, because:

* The formal model **is verifiable and documentable** is.
* Every safety-relevant function **be automatically checked** and **is diagnosed** is.
* Changes to the model **traceable** and **are version-controlled** are.
* The generated PLC programs **are standards-compliant (IEC 61131, PLCopen)** are.
* The machine in **virtual commissioning (Digital Twin)** can be tested.

Thus Selmo offers **objective evidence** for the requirements from:

* EU Machinery Regulation (safety through state of the art),
* product liability law (traceable behavior),
* quality management (ISO 9001 ff.),
* functional safety (ISO 13849, IEC 62061).

</details>


---

# 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-how-it-works/selmo-training/chapter-8-the-new-state-of-the-art.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.