> 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/selmo-audit-checklist-functional-safety-and-standards-compliance.md).

# ✅ Selmo audit checklist – Functional safety & standards compliance

## ✅ Selmo audit checklist – functional safety & standards compliance

This checklist is used for the structured review of a project that was modelled and implemented with **Selmo Standard** It can be used for:

* internal approvals,
* external audits,
* CE documentation reviews,
* project releases.

***

### 🔍 1. Model structure & composition

| Acceptance criterion                                                | Compliant? | Remark |
| ------------------------------------------------------------------- | ---------- | ------ |
| Machine fully represented as Selmo model (PLANT → HWZ → SEQ → Zone) | ✅ / ❌      |        |
| Each zone assigned unambiguously (type, IO, signal, terminal)       | ✅ / ❌      |        |
| Each SEQ modelled as a state graph with valid transitions           | ✅ / ❌      |        |
| Bit control fully filled out (`0`, `S`, `i`)                        | ✅ / ❌      |        |

***

### 🔍 2. Functional logic & sequence control

| Acceptance criterion                                   | Compliant? | Remark |
| ------------------------------------------------------ | ---------- | ------ |
| Each state named uniquely and logically                | ✅ / ❌      |        |
| Sequence is deterministic (no jumps outside the model) | ✅ / ❌      |        |
| Interlocks (`i`) set sensibly and safely               | ✅ / ❌      |        |
| Sequence checks (`S`) used correctly                   | ✅ / ❌      |        |
| Timers, repeaters, decisions parameterized correctly   | ✅ / ❌      |        |

***

### 🔍 3. Safety functions

| Acceptance criterion                             | Compliant? | Remark |
| ------------------------------------------------ | ---------- | ------ |
| CMZ zones set correctly on SEQ/HWZ/PLANT         | ✅ / ❌      |        |
| MXIC matrix present, complete, traceable         | ✅ / ❌      |        |
| Fault reaction on `i` and CMZ violation correct  | ✅ / ❌      |        |
| Reset logic clearly represented in the model     | ✅ / ❌      |        |
| Restart only possible in a valid state + release | ✅ / ❌      |        |

***

### 🔍 4. HMI, operation & diagnostics

| Acceptance criterion                                  | Compliant? | Remark |
| ----------------------------------------------------- | ---------- | ------ |
| SEQ control shows current state & next step           | ✅ / ❌      |        |
| Error display localized with HMI text, color and zone | ✅ / ❌      |        |
| Button behaviour secured by MXIC                      | ✅ / ❌      |        |
| Stepwise operation possible in manual mode            | ✅ / ❌      |        |
| Automatic start only with valid process state         | ✅ / ❌      |        |

***

### 🔍 5. Documentation & export

| Acceptance criterion                            | Compliant? | Remark |
| ----------------------------------------------- | ---------- | ------ |
| IO mapping complete (Zone ↔ Address ↔ Terminal) | ✅ / ❌      |        |
| Parameter list with IN / OUT / INOUT complete   | ✅ / ❌      |        |
| CMZ and MXIC definition exported                | ✅ / ❌      |        |
| Change log (`Model_ChangeLog.csv`) present      | ✅ / ❌      |        |
| Exported documentation matches the model        | ✅ / ❌      |        |

***

### 🔍 6. Standards compliance (verifiable)

| Acceptance criterion                                 | Compliant? | Standards reference             | Remark |
| ---------------------------------------------------- | ---------- | ------------------------------- | ------ |
| Operating modes modelled, switchable, safe           | ✅ / ❌      | ISO 12100                       |        |
| Safety functions documented & verifiable             | ✅ / ❌      | EN ISO 13849, IEC 62061         |        |
| Restart behaviour CE-compliant                       | ✅ / ❌      | ISO 12100, Machinery Regulation |        |
| PLC code generated from model, IEC 61131-3 compliant | ✅ / ❌      | IEC 61131-3                     |        |
| Risk assessment can be linked to the model           | ✅ / ❌      | ISO 12100                       |        |

***

### 📝 Conclusion

* Review performed on: `_____________`
* Project name / model version: `_____________`
* Reviewer / role: `_____________`
* Status: 🔲 passed 🔲 with conditions 🔲 failed

Signature / approval: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_


---

# 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/selmo-audit-checklist-functional-safety-and-standards-compliance.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.