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

# Structure proposal

Very good idea – a **user-friendly Selmo knowledge base** (e.g. for internal teams, customers or training) provides:

* 📚 Clarity about terms, structure, operation
* 🔄 Reusability in projects
* ✅ Traceability for CE, development, service

***

### 🧠 Suggestion: Structure for the Selmo knowledge base (Knowledge Base)

The knowledge base should **be divided into topic areas** be logically structured and visually supported with **icons, screenshots, model graphics and state diagrams**.

***

#### 🗂️ **1. Overview – What is Selmo?**

| Content                   | Goal                                    |
| ------------------------- | --------------------------------------- |
| Introduction              | What is Selmo? Why model-based?         |
| Principle of the SDEA     | Process as an automaton, `S`, `i`, `0`  |
| Advantages & benefits     | Structure, safety, diagnosis, export    |
| Comparison to classic PLC | Differences in methodology and behavior |

**Visuals:** Icon “Automaton”, process model, Selmo main logo\
**Format:** Explanatory article + animated SVG or .gif illustrating the process idea

***

#### 🗂️ **2. Structure & Terms**

| Content         | Description                           |
| --------------- | ------------------------------------- |
| Selmo structure | PLANT → HWZ → SEQ → Zones             |
| Zone types      | Input, Output, In-Out, Mem            |
| Layer concept   | Logic Layer, System Layer, Parameters |
| Parameter types | IN / OUT / INOUT, usage in the model  |

**Visuals:** Layer overview, diagram with model hierarchy\
**Extras:** Clickable glossary + mouseover explanations

***

#### 🗂️ **3. Operation – Selmo Studio**

| Content                | Explanation                             |
| ---------------------- | --------------------------------------- |
| Create project         | Create Plant, HWZ, SEQ                  |
| Define zones           | Signal assignment, HMI text, IO address |
| Model states           | `State`, `Timer`, `Decision`            |
| Edit bit control       | `S`, `i`, `0` assign                    |
| Create parameters      | Times, values, OPC UA variables         |
| Perform validation     | HMI test, interlock check               |
| Export & documentation | CSV, PDF, PLC code                      |

**Visuals:** Screenshots with highlighted areas, mini-tutorials\
**Extras:** Video tutorials, .gif animations “step by step”

***

#### 🗂️ **4. Safety & modes of operation**

| Topic                | Description                   |
| -------------------- | ----------------------------- |
| Interlock (`i`)      | Mandatory conditions          |
| Sequence Check (`S`) | Expected actions              |
| CMZ                  | Continuous safety monitoring  |
| MXIC                 | safe manual releases          |
| Modes of operation   | Manual / Auto, reset behavior |

**Visuals:** Colors in the HMI (Blue = valid, Red = error), symbol icons\
**Extras:** MXIC logic examples, CMZ scenarios explained graphically

***

#### 🗂️ **5. Documentation & export**

| Content                | Goal                             |
| ---------------------- | -------------------------------- |
| Export formats         | PLC, HMI, CSV, documentation     |
| Signal directory       | IO ↔ Zone ↔ Terminal             |
| Parameter export       | CSV, OPC UA mapping              |
| Revision documentation | `Model_ChangeLog.csv`            |
| CE-compliant evidence  | Documentation package from model |

**Visuals:** Sample files for download, PDF excerpt with link to explanation

***

#### 🗂️ **6. Practical examples**

| Category               | Content                                |
| ---------------------- | -------------------------------------- |
| Tension station        | Model graphic + process description    |
| Slider logic           | SEQ with Decision / Repeater           |
| Error case CMZ         | Impact + fallback level                |
| HMI: operator guidance | Screenshots + explanation of the logic |

**Visuals:** Flow diagrams, excerpts of bit-control matrix, real screenshots from the Studio

***

#### 🗂️ **7. Glossary & references**

| Term                     | Explanation                                   |
| ------------------------ | --------------------------------------------- |
| All Selmo terms          | alphabetical + with cross-reference to topics |
| Norm reference           | EN ISO 13849, ISO 12100, IEC 62061 etc.       |
| Linking to documentation | Downloadable PDFs, Word, Markdown files       |

***

#### 📦 Bonus: Content types

| Type         | Purpose                               |
| ------------ | ------------------------------------- |
| 📝 Article   | Background, explanation, CE relevance |
| 🎥 Video     | Step-by-step, onboarding              |
| 📊 Diagram   | Model structure, process, state logic |
| 🧪 Checklist | Validation, project approval          |
| 💬 FAQ       | typical questions from users          |

***

### 🔧 Tools for implementation

| Platform                | Recommendation for ...                       |
| ----------------------- | -------------------------------------------- |
| **Confluence**          | internal + rights management                 |
| **MkDocs / Docusaurus** | Web-based technical documentation (Markdown) |
| **Notion**              | for training & informal documentation        |
| **GitBook**             | Developer-friendly, easy to version          |


---

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