> 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/4.-overall-view-selmo-ptf-who-delivers-who-checks-who-uses.md).

# 4. Overall view Selmo-PTF – Who delivers, who checks, who uses

### **1️⃣ Phase: Initiation & Scope**

**Objective:** Define project boundaries, roles, standards, deliverables.

| Role                              | Delivers                                 | Checks             | Uses                        |
| --------------------------------- | ---------------------------------------- | ------------------ | --------------------------- |
| **Project management / PTF lead** | Project mandate, scope, RACI/role matrix | Management         | all following disciplines   |
| **Management / Customer**         | Requirements, goal definition            | PTF lead           | Project management, process |
| **Quality / Safety**              | Standards and CE framework               | Project management | all (as rule base)          |

***

### **2️⃣ Phase: Process Definition (P – Process)**

**Objective:** Describe physical & logical sequence.

| Role                                       | Delivers                                                   | Checks            | Uses                 |
| ------------------------------------------ | ---------------------------------------------------------- | ----------------- | -------------------- |
| **Process owner (Industrial Engineering)** | Process description (PTF-PROC), parameter list (PTF-PARAM) | PTF lead, quality | Technology, software |
| **Mechanics / electrical (supporting)**    | Layout, kinematics, sensor/actuator assignment             | Process, PTF lead | Automation, safety   |
| **Quality / Safety**                       | Assessment of process risks                                | Process, PTF lead | Risk management      |

***

### **3️⃣ Phase: Technology Analysis (T – Technology)**

**Objective:** Define technologies, components and interfaces.

| Role                                     | Delivers                                                             | Checks               | Uses                       |
| ---------------------------------------- | -------------------------------------------------------------------- | -------------------- | -------------------------- |
| **Electrical / mechanical / automation** | Technology matrix (PTF-TECH), I/O list (PTF-IO), interfaces (PTF-IF) | PTF lead, safety     | Software, CE documentation |
| **Safety / CE**                          | Safety requirements, CMZ structure, interlocks                       | PTF lead             | Software, quality          |
| **IT / OT**                              | Data and communication interfaces                                    | PTF lead, automation | Integration, MES, SCADA    |

***

### **4️⃣ Phase: Function Definition (F – Function)**

**Objective:** Define functions, monitoring and test logic.

| Role                                  | Delivers                                                      | Checks            | Uses           |
| ------------------------------------- | ------------------------------------------------------------- | ----------------- | -------------- |
| **Automation / software development** | Function sheets (PTF-FUNC), monitoring (PTF-SAFE), test cases | PTF lead, process | Selmo modeling |
| **Process / technology**              | Feedback on feasibility                                       | PTF lead          | Software       |
| **Quality / Safety**                  | Function risk assessment                                      | PTF lead          | Audit / CE     |

***

### **5️⃣ Phase: Review & Risk Assessment**

**Objective:** Document completeness, conformity, deviations and risks.

| Role                   | Delivers                              | Checks             | Uses              |
| ---------------------- | ------------------------------------- | ------------------ | ----------------- |
| **PTF lead / Quality** | Review protocol, risk list (PTF-RISK) | Project management | all stakeholders  |
| **Safety / CE**        | Assessment of normative deviations    | Quality            | Management, audit |
| **Project management** | Release decision                      | Management         | Selmo modeling    |

***

### **6️⃣ Phase: Release & Handover**

**Objective:** Release of the PTF as basis for Selmo modeling.

| Role                              | Delivers                                                                            | Checks             | Uses                |
| --------------------------------- | ----------------------------------------------------------------------------------- | ------------------ | ------------------- |
| **Project management / PTF lead** | Release document (PTF-RELEASE), PTF report                                          | Management         | Software, customer  |
| **Software / automation**         | Import into Selmo Studio, model structure (Plant → HWZ → SEQ → Zones → Bit-Control) | PTF lead           | Commissioning       |
| **Customer / Operator**           | Release for implementation                                                          | Project management | Production, service |

***

### **7️⃣ Use of results after release**

**Objective:** Each stakeholder uses the PTF output to fulfill their tasks.

| Role                         | Uses                       | For what                    | Benefit                      |
| ---------------------------- | -------------------------- | --------------------------- | ---------------------------- |
| **Software / automation**    | Selmo model structure      | Code generation             | deterministic implementation |
| **Quality / Safety**         | PTF-RISK, PTF-SAFE         | CE evidence, audit          | Legal certainty              |
| **Operation / Maintenance**  | HMI, MXIC, CMZ information | Operation, diagnostics      | safe maintenance             |
| **Management / Controlling** | PTF report, deviation list | Project and risk management | Transparency & cost control  |
| **Customer / end user**      | Complete documentation     | Acceptance, operation       | Trust & evidence             |

***

### **8️⃣ Overall flow – short text diagram**

```
[Supplier provides input]
    ↓
[PTF lead collects & checks]
    ↓
[Process definition (P)]
    ↓
[Technology analysis (T)]
    ↓
[Function definition (F)]
    ↓
[Review & risk]
    ↓
[PTF release]
    ↓
→ Use:
   • Software: modeling in Selmo Studio
   • Quality/Safety: audit & CE
   • Operations: operation & diagnostics
   • Management: control & release
   • Customer: acceptance & evidence
```

***

### **9️⃣ Core statement**

> The PTF creates **a continuous flow of information**:\
> **Delivery → Check → Use**,\
> in which every role knows exactly\
> **what it delivers, what it checks and what it uses**.
>
> Thus knowledge becomes responsibility –\
> and from responsibility arises a **deterministic, safe machine process** 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/4.-overall-view-selmo-ptf-who-delivers-who-checks-who-uses.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.