> 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-process-flow-checklist-and-milestone-overview.md).
# ✅ Selmo PTF – Process flow checklist & milestone overview
#### **Goal**
This checklist describes the **process, the checks and approvals** within the PTF process.\
It serves as guidance for the project team and as a basis for **project controlling, scheduling, and quality assurance**.
Each phase of the PTF ends with a **defined milestone**, the fulfillment of which is checked and documented.
***
### **1. Process flow – step-by-step checklist**
| No. | Process step | Goal | Result / deliverable | Responsible | Acceptance criterion |
| ------ | --------------------------------- | ------------------------------------------------------------ | ---------------------------------- | ----------------------------- | ------------------------------------------------------------- |
| **1** | **PTF start / scope definition** | Clarify project boundaries, objectives, standards, and roles | PTF-SCOPE document, supplier list | Project management / PTF lead | - All suppliers named
- Project scope approved
|
| **2** | **Process capture (P)** | Understand the physical flow and logic | PTF-PROC, PTF-PARAM | Process owner | - Flowchart complete
- Parameters defined
|
| **3** | **Technology analysis (T)** | Define technologies, devices, interfaces | PTF-TECH, PTF-IO, PTF-IF | Mechanics / Electrical / IT | - Technology matrix complete
- Signals assigned
|
| **4** | **Function definition (F)** | Describe functional logic, monitoring, test cases | PTF-FUNC, PTF-SAFE | Automation / Software | - Function sheets created
- Safety logic documented
|
| **5** | **Data integration & review** | Check completeness and Selmo compliance | PTF review protocol | PTF lead / Quality | - All artifacts submitted
- no open items
|
| **6** | **Risk assessment & deviations** | Document and assess non-conformities | PTF-RISK | Quality / Safety | - Risks assessed
- Measures assigned
|
| **7** | **PTF review meeting** | Technical and organizational approval | PTF review report | Project management / PTF lead | - All disciplines present
- Decisions documented
|
| **8** | **PTF approval (release)** | Official authorization for modeling | PTF-RELEASE document | Project management / customer | - Signatures present
- Version archived
|
| **9** | **Transfer to Selmo modeling** | Import PTF data into Selmo Studio | PTF-XML / model export | Automation / Software | - Import successful
- Structure mappable
|
| **10** | **Project closure / audit trail** | Retrospective, lessons learned, archiving | PTF final / lessons learned report | PTF lead / Quality | - Documentation complete
- Audit trail secured
|
***
#### **Additional check for each phase**
Before completing each phase, it must be checked that:
* [ ] All associated artifacts are created and versioned
* [ ] Responsible person has given technical approval
* [ ] Standards requirements (ISO / CE / MVO 2027) were considered
* [ ] Risks and open items are documented
* [ ] Changes are recorded in the change log
* [ ] Artifacts stored in the PTF directory
***
### **2. Milestone overview (PTF lifecycle)**
| Milestone | Time | Result / approval | Responsible | Decision criterion |
| -------------------------------------- | ----------- | ---------------------------------------------- | ----------------------------- | -------------------------------------------- |
| **M1 – project start** | Week 0 | PTF scope, supplier list, objective definition | Project management | Project objective and boundaries approved |
| **M2 – process definition completed** | Week 2–3 | PTF-PROC, PTF-PARAM | Process owner | Process complete and reviewed |
| **M3 – technology analysis completed** | Week 4–5 | PTF-TECH, PTF-IO, PTF-IF | Mechanics / Electrical / IT | Interfaces, signal structure aligned |
| **M4 – function definition completed** | Week 6–7 | PTF-FUNC, PTF-SAFE | Automation / Software | Functional logic consistent, safety assessed |
| **M5 – PTF review meeting** | Week 8 | PTF review protocol, PTF-RISK | PTF lead / Quality | All artifacts complete, risks assessed |
| **M6 – PTF release** | Week 9 | PTF-RELEASE | Project management / customer | Official approval for Selmo modeling |
| **M7 – Selmo model imported** | Week 10 | Selmo model (Plant → HWZ → SEQ → Zones) | Software / automation | Import successful, code generatable |
| **M8 – SoftFAT (digital twin)** | Week 11–12 | Simulation / emulation successfully tested | Automation / Quality | Communication and sequences validated |
| **M9 – project closure (PTF final)** | Project end | Lessons learned, audit trail, archiving | PTF lead / Quality | Documentation complete, audit passed |
***
#### **PTF process flow (simplified)**
```
M1 ─► M2 ─► M3 ─► M4 ─► M5 ─► M6 ─► M7 ─► M8 ─► M9
| | | | | | | | |
Scope Process Tech Func Review Release Model SoftFAT Closure
```
***
#### **Quality assurance per milestone**
Each milestone is only reached when:
* The **preceding steps are fully completed** are
* The **Check and review documents** have been approved
* The **PTF lead** a formal confirmation for handover has been given
* The **Project management** the result is approved in writing
***
#### **Recommendation for project practice**
* Plan **each PTF phase as a standalone work package** with deliverables and review.
* Use the milestones M1–M9 as **mandatory points in the project schedule**.
* Conduct **review meetings in an interdisciplinary manner** (mechanics, electrical, software, quality, management).
* Store all approved artifacts **in a versioned PTF repository** there.
* Link PTF milestones with the project milestones in your PM tool (MS Project, Jira, Notion etc.).
***
#### **Conclusion**
This checklist and milestone overview ensure:
* clear structure and responsibilities,
* traceable progress,
* plannable reviews,
* and verifiable approvals.
This makes the **PTF process a measurable part of project management** –\
and the result **a fully documented, standards-compliant, and deterministic system** according to the Selmo standard.
---
# 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-process-flow-checklist-and-milestone-overview.md?ask=&goal=
```
`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.