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

# Selmo structure

### 📘 Selmo structure – the blueprint for modeled machine logic

The Selmo method is based on a fixed, logical structure with which every machine is built uniformly, modularly and traceably.\
This structure is the foundation for **modeling, code generation, safety functions and documentation**.

***

#### 🔷 1. Structural overview

```
scssCopyEditPLANT
└── Hardware zones (HWZ)
    └── Sequences (SEQ)
        └── Zones (Input, Output, In-Out, Mem)
```

Each level fulfills a clear task and is explicitly visible in the model.

***

#### 🧱 2. The four levels in detail

**✅ PLANT**

* Represents the **entire machine or line**
* Contains global parameters, safety monitoring (e.g. TCMZ)
* Controls the overarching structure and interfaces (OPC UA, MES)

**✅ HWZ – Hardware zone**

* Controllable functional unit of the system (e.g. station, module)
* Has its own operating modes: Manual / Auto
* Contains one or more SEQs
* CMZ and safety logic can act at the HWZ level

**✅ SEQ – Sequence**

* The **Core of the modeled machine logic**
* Describes the **process flow in logical states**
* Uses states such as `State`, `Timer`, `Decision`, `Repeater`
* Is coupled with:
  * Bit control (system layer)
  * parameters
  * safety rules (MXIC, CMZ)
  * HMI texts

**✅ Zone**

* Link between logic and real technology
* Types:
  * `Input` → sensor
  * `Output` → actuator
  * `In-Out` → actuator with feedback
  * `Mem` → internal state / marker
* Each zone receives a behavior per state: `0`, `S`, `i`
* Is documented with: address, function, description, HMI text

***

#### 🎯 3. Why this structure?

| Advantage          | Description                                                 |
| ------------------ | ----------------------------------------------------------- |
| **Modularity**     | Each SEQ is a self-contained process module                 |
| **Reusability**    | SEQs can be copied, extended or varied                      |
| **Diagnosability** | Each zone is logically assigned and monitored               |
| **Exportability**  | Documentation (CSV, PDF) is generated automatically from it |
| **safety**         | Safety functions definable at SEQ, HWZ or PLANT level       |

***

#### 🧾 Conclusion

The Selmo structure is the key to model-based automation.\
It is **uniform**, **clearly documentable**, **fully exportable** – and ensures that machine behavior, code and documentation **always match**.

📌 *Each modeled machine is thus not only logical – but also verifiable, safe and CE-compliant in its construction.*


---

# 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-structure.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.