> 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-project-preparation-checklist-before-engineering-start.md).

# ✅ Selmo project preparation – Checklist before engineering start

This checklist helps to clarify all basic requirements, **before** starting the modeling and implementation of a project in Selmo Studio.

Objective:

* clear technical prerequisites,
* complete process definition,
* secure scheduling,
* avoidance of gaps in the model.

***

### 🔧 1. Project definition & goal

| Acceptance criterion                | Compliant? | Remark |
| ----------------------------------- | ---------- | ------ |
| Project goal clearly described      | ✅ / ❌      |        |
| Function of the machine fully known | ✅ / ❌      |        |
| Responsible roles defined           | ✅ / ❌      |        |
| CE and safety officers appointed    | ✅ / ❌      |        |

***

### 🧩 2. Process description (PFT)

| Acceptance criterion                                              | Compliant? | Remark |
| ----------------------------------------------------------------- | ---------- | ------ |
| **process**: What should the machine do?                          | ✅ / ❌      |        |
| **Function**: Which actions are required?                         | ✅ / ❌      |        |
| **technology**: Which components are used?                        | ✅ / ❌      |        |
| PFT has been documented and coordinated with all parties involved | ✅ / ❌      |        |

***

### 📐 3. Structural planning (Selmo basic structure)

| Acceptance criterion                                    | Compliant? | Remark |
| ------------------------------------------------------- | ---------- | ------ |
| Plant (overall system) is clearly delimited             | ✅ / ❌      |        |
| Planned HWZs with stations / modules defined            | ✅ / ❌      |        |
| Per HWZ defined SEQs for each subprocess planned        | ✅ / ❌      |        |
| Zones (signals) per SEQ roughly known                   | ✅ / ❌      |        |
| Zone types determinable (Input / Output / In-Out / Mem) | ✅ / ❌      |        |

***

### ⚙️ 4. Technical prerequisites (Hardware / IO / Safety)

| Acceptance criterion                                  | Compliant? | Remark |
| ----------------------------------------------------- | ---------- | ------ |
| PLC is IEC-61131-3 compatible                         | ✅ / ❌      |        |
| IO cards / safety modules specified                   | ✅ / ❌      |        |
| Sensors/actuators fully drawn into the plan           | ✅ / ❌      |        |
| Safety functions designed (emergency stop, door etc.) | ✅ / ❌      |        |
| Signal naming system available (for zone assignment)  | ✅ / ❌      |        |

***

### 🔍 5. Requirements for safety & operation

| Acceptance criterion                               | Compliant? | Remark |
| -------------------------------------------------- | ---------- | ------ |
| Operating modes: manual / automatic provided       | ✅ / ❌      |        |
| Restart conditions defined                         | ✅ / ❌      |        |
| Operator guidance planned (HMI / buttons)          | ✅ / ❌      |        |
| Safety functions CMZ/MXIC considered in the design | ✅ / ❌      |        |
| Operator logic (SEQ Control) taken into account    | ✅ / ❌      |        |

***

### 📄 6. Documentation and data base

| Acceptance criterion                              | Compliant? | Remark |
| ------------------------------------------------- | ---------- | ------ |
| Signal directory in preparation                   | ✅ / ❌      |        |
| Parameter requirements roughly known              | ✅ / ❌      |        |
| CE risk assessment started / available            | ✅ / ❌      |        |
| Specification with PFT and process flow described | ✅ / ❌      |        |
| Project structure released for engineering start  | ✅ / ❌      |        |

***

### 📝 Conclusion

* Check carried out on: `_____________`
* Project designation: `_____________`
* Preparation team: `_____________`
* Status: 🔲 ready for implementation 🔲 incomplete 🔲 consultation required

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-project-preparation-checklist-before-engineering-start.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.