> 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/08-appendix-and-templates/requirements-for-the-realization-of-a-machine-with-selmo.md).

# 📘 Requirements for the realization of a machine with Selmo

### 🎯 Objective

Secure, verifiable, CE-compliant realization of a machine based on the **Selmo standard**.\
→ Clear specifications for mechanics, electrical, control and documentation.

***

### 🔧 1. Technological prerequisites

**Sensing:**

* Every relevant position must be uniquely identifiable by a sensor.
* Safety-relevant sensors must be implemented redundantly / reliably.

**Actuation:**

* Actuators must be switchable and, if necessary, provide feedback.
* Every movement must be safeguarded via `i` or CMZ.

**Safety interfaces:**

* Emergency stop, door contacts, air pressure etc. must be representable as CMZ.
* Safety behavior must be able to be modeled deterministically.

***

### 🧱 2. Structural requirement (Selmo principle)

```
markdownCopyEditPLANT
└── HWZ
    └── SEQ
        └── ZONE
```

* Every logical subprocess must be represented in a SEQ.
* Each zone must unambiguously have: type, IO, signal, function.
* Each zone must be defined per state (`0`, `S`, `i`).
* Zones may **not be used multiple times** – no overlap.

***

### 🔁 3. Sequence logic

* Every sequence must be modelable as a **state machine** model.
* No behavior may be “hidden” in code or side effects.
* All interlocks, CMZ, MXIC must **be visible in the model** be.
* Reset behavior and restart must be clearly described and testable.

***

### 💻 4. Requirements for PLC + engineering

* Control system must support IEC-61131-3 (ideally Structured Text).
* Code is **fully generated from the model** – no side coding.
* Project structure with GVL, POUs, Zones, SEQs is mandatory.

***

### 📋 5. Documentation & traceability

* Complete IO mapping (`Zone ↔ IO ↔ Address ↔ Terminal`)
* CMZ and MXIC matrices with description and reaction
* Parameter structure: IN/OUT, function, interface
* Change log (`Model_ChangeLog.csv`)
* Validation evidence (e.g. HMI test, sequence check)

***

### ✅ Project approval – checklist

| Criterion               | Must be fulfilled                    |
| ----------------------- | ------------------------------------ |
| Structure complete      | PLANT → HWZ → SEQ → Zone             |
| Logic modeled           | State-driven sequence (DEA)          |
| Safety represented      | CMZ, MXIC, interlock in the model    |
| IO clearly assigned     | Signal = Zone = Address = Terminal   |
| Documentation generated | Model → Export → PDF/CSV             |
| Validation performed    | Test run + fault check               |
| Restart described       | Reset logic + HMI guidance available |

***

📌 **These requirements are binding for every Selmo project.**\
They create the basis for:

* safe machines,
* clear interfaces between trades,
* automated documentation,
* and legally secure CE conformity.


---

# 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/08-appendix-and-templates/requirements-for-the-realization-of-a-machine-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.