> 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-as-a-process/selmo-ptf/ptf-checklists/selmo-ptf-acceptance-protocol.md).

# 🧾 Selmo PTF – Acceptance protocol

### **1. Project Data**

| Field                        | Description                  |
| ---------------------------- | ---------------------------- |
| **Project Name:**            |                              |
| **Project No. / Order No.:** |                              |
| **Customer / Operator:**     |                              |
| **Project Management:**      |                              |
| **PTF Lead:**                |                              |
| **Date of Acceptance:**      |                              |
| **PTF Version:**             |                              |
| **Status of Documents:**     | (e.g. PTF\_v1.3, 05.10.2025) |
| **Location / Meeting:**      |                              |

***

### **2. Purpose of the Acceptance**

The acceptance of the PTF process confirms that:

1. **All PTF phases have been fully completed** were (Process, Technology, Function).
2. **All relevant PTF artefacts** are available, reviewed and released.
3. **Selmo compliance** is established (determinism, traceability, formal verifiability).
4. **Risk assessment and standard requirements** are taken into account and documented.
5. The PTF output as a basis for the **Selmo modelling and digitization** is released.

***

### **3. Overview of the reviewed PTF documents**

| No. | Document / Artefact                        | Version | Date | Release available | Remark |
| --- | ------------------------------------------ | ------- | ---- | ----------------- | ------ |
| 1   | PTF-SCOPE (project scope)                  |         |      | ☐ Yes ☐ No        |        |
| 2   | PTF-PROC (process description)             |         |      | ☐ Yes ☐ No        |        |
| 3   | PTF-PARAM (parameter list)                 |         |      | ☐ Yes ☐ No        |        |
| 4   | PTF-TECH (technology matrix)               |         |      | ☐ Yes ☐ No        |        |
| 5   | PTF-IO (signal list)                       |         |      | ☐ Yes ☐ No        |        |
| 6   | PTF-FUNC (function sheets)                 |         |      | ☐ Yes ☐ No        |        |
| 7   | PTF-SAFE (safety concept)                  |         |      | ☐ Yes ☐ No        |        |
| 8   | PTF-IF (interface description)             |         |      | ☐ Yes ☐ No        |        |
| 9   | PTF-HMI (operator concept)                 |         |      | ☐ Yes ☐ No        |        |
| 10  | PTF-RISK (risk assessment)                 |         |      | ☐ Yes ☐ No        |        |
| 11  | PTF-NORM (standards & guidelines evidence) |         |      | ☐ Yes ☐ No        |        |
| 12  | PTF-RELEASE (release document)             |         |      | ☐ Yes ☐ No        |        |

***

### **4. Assessment of PTF completeness**

| Acceptance criterion         | Description                                           | Assessment (☐ Yes / ☐ No / ☐ n. a.) | Comment |
| ---------------------------- | ----------------------------------------------------- | ----------------------------------- | ------- |
| **Formal completeness**      | All PTF documents are present and versioned           |                                     |         |
| **Process completeness**     | All states, parameters and procedures are defined     |                                     |         |
| **Technology completeness**  | All technologies, interfaces and components described |                                     |         |
| **Function completeness**    | All functions, triggers, monitoring documented        |                                     |         |
| **Risk assessment**          | All risks assessed, measures defined                  |                                     |         |
| **Selmo compliance**         | Process model deterministic and verifiable            |                                     |         |
| **Standards compliance**     | CE, ISO, MVO requirements considered                  |                                     |         |
| **Interface check**          | MES/ERP/IT connections described and tested           |                                     |         |
| **Deviations documented**    | Deviation list (PTF-RISK) maintained                  |                                     |         |
| **Importability into Selmo** | PTF data usable in Selmo Studio                       |                                     |         |

***

### **5. Summary of the test results**

**Overall assessment:**\
☐ PTF complete and released\
☐ PTF partially released (with conditions)\
☐ PTF not released (revision required)

**Short justification / conditions:**\
*(e.g. missing parameter limits, incomplete interface description, standards check open)*

***

### **6. Deviations & Actions**

| No. | Deviation / Risk | Category (P/T/F) | Assessment                         | Action / Responsible | Deadline |
| --- | ---------------- | ---------------- | ---------------------------------- | -------------------- | -------- |
| 1   |                  |                  | ☐ critical ☐ moderate ☐ acceptable |                      |          |
| 2   |                  |                  | ☐ critical ☐ moderate ☐ acceptable |                      |          |
| 3   |                  |                  | ☐ critical ☐ moderate ☐ acceptable |                      |          |

***

### **7. Release decision**

**Recommendation of the PTF Lead:**\
☐ Release granted\
☐ Release with conditions\
☐ No release

**Date:**\
**Signature:**

***

### **8. Official PTF Acceptance**

| Role                   | name | Organization / Department | Signature | Date |
| ---------------------- | ---- | ------------------------- | --------- | ---- |
| Project management     |      |                           |           |      |
| PTF lead               |      |                           |           |      |
| Process owner          |      |                           |           |      |
| Mechanics / Electrical |      |                           |           |      |
| Software / automation  |      |                           |           |      |
| Quality / Safety       |      |                           |           |      |
| Customer / Operator    |      |                           |           |      |

***

### **9. Handover and Archiving**

**Responsible:** PTF lead\
**Storage location:** e.g. `/PTF/06_Release/PTF-Release_v1.0.pdf`\
**Version:**\
**Archiving date:**

***

### **10. Comment / Lessons Learned**

Brief description of key findings from the PTF process:

* Process improvements
* Identified bottlenecks
* Potentials for standardization
* Need for changes in the workflow

***

### **11. Final note**

> By signing this protocol it is confirmed\
> that the PTF has been fully reviewed, documented and released.\
> The PTF forms the binding basis for modelling, programming\
> and later commissioning of the plant in accordance with the Selmo standard.

***

#### **Recommendation for use**

* This acceptance protocol should **be used in every project** with the milestone **M6 – PTF release** be used.
* It replaces, in terms of content, the classical *requirements/specifications acceptance form*.
* It serves as the official **quality and release document** according to **MVO 2027** and **Selmo methodology**.

***

#### **Conclusion**

The PTF acceptance protocol ensures:

* the formal and substantive quality of the entire PTF process,
* compliance with standards and safety requirements,
* and the official responsibility and traceability of all parties involved.

Thus the **Selmo requirement – documented, deterministic, verifiable –** is transferred into a clear, traceable release process.


---

# 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-as-a-process/selmo-ptf/ptf-checklists/selmo-ptf-acceptance-protocol.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.