> 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/overall-project-workflow-with-ptf-integration-according-to-selmo-standard.md).

# 🧩 Overall project workflow with PTF integration according to Selmo standard

## Overview Processes and Lanes

{% @mermaid/diagram content="flowchart TB

%% Lane 1
subgraph L1\["Kunde / Management"]
A1\["Anfrage, Zieldefinition, Problemstellung"]
A2\["Anforderungen (funktional, technisch, wirtschaftlich)"]
A3\["Uebergabe an PTF-Lead als Problemdefinition"]
A1 --> A2
A2 --> A3
end

%% Lane 2
subgraph L2\["PTF-Lead / Projektleitung"]
B1\["Projektstart, Scope, Normen & Standards festlegen"]
B2\["Koordination aller Supplier (Prozess, Technik, Funktion)"]
B3\["Durchfuehrung des PTF-Prozesses (P, T, F)"]
B4\["Review, Risikobewertung, Freigabe"]
B5\["Uebergabe: Freigegebener PTF-Report + Modelldaten"]
B1 --> B2
B2 --> B3
B3 --> B4
B4 --> B5
end

%% Lane 3
subgraph L3\["Prozessverantwortlicher / Industrial Engineering"]
C1\["Beschreibung des realen Prozesses (Ablauf, Takt, Parameter)"]
C2\["Definition von Zustaenden, Uebergaengen, Abbruchkriterien"]
C3\["Erstellung PTF-PROC + PTF-PARAM"]
C1 --> C2
C2 --> C3
end

%% Lane 4
subgraph L4\["Mechanik / Elektro (Engineering)"]
D1\["Erstellung Technologiematrix (Sensorik, Aktorik, Layout)"]
D2\["Definition I/O-Liste, Sicherheitskreise, Schnittstellen"]
D3\["Bewertung der Selmo-Konformitaet"]
D1 --> D2
D2 --> D3
end

%% Lane 5
subgraph L5\["Software / Automation"]
E1\["Definition standardisierter Funktionen"]
E2\["Erstellung PTF-FUNC & PTF-SAFE"]
E3\["Review der logischen Konsistenz"]
E4\["Nach Freigabe: Umsetzung im Selmo-Studio"]
E1 --> E2
E2 --> E3
E3 --> E4
end

%% Lane 6
subgraph L6\["Qualitaet / Sicherheit / CE"]
F1\["Pruefung aller PTF-Artefakte auf Normen & Konformitaet"]
F2\["Bewertung von Risiken und Abweichungen (PTF-RISK)"]
F3\["CE- und ISO-Dokumentation vorbereiten"]
F1 --> F2
F2 --> F3
end

%% Lane 7
subgraph L7\["Management / Controlling"]
G1\["Abnahme PTF-Report & Risikobewertung"]
G2\["Wirtschaftliche Bewertung & Entscheidung zur Umsetzung"]
G1 --> G2
end

%% Lane 8
subgraph L8\["Konstruktion / Umsetzung (Mechanik, Elektro, Software)"]
H1\["Umsetzung basierend auf PTF-Modelldaten"]
H2\["Integration, Test, Inbetriebnahme"]
H3\["Abnahmeprotokoll + CE-Dokumentation"]
H1 --> H2
H2 --> H3
end

%% Lane 9
subgraph L9\["Betrieb / Service / Kunde"]
I1\["Nutzung der Maschine gemaess PTF-Prozessmodell"]
I2\["Diagnose, Wartung, Erweiterung mit klarer Traceability"]
I3\["Rueckmeldung in PTF fuer kontinuierliche Verbesserung"]
I1 --> I2
I2 --> I3
end

%% Uebergaben zwischen Lanes
A3 --> B1
B5 --> C1
C3 --> D1
D3 --> E1
E4 --> F1
F3 --> G1
G2 --> H1
H3 --> I1" %}

### 🔷 **Overview – Project Phases (Top-Level)**

```
2. Position in the project lifecycle
   ↓
Customer inquiry
   ↓
PTF process (process – technology – function)
   ↓
Mechanical and Electrical Design
   ↓
Mechanical & electrical design
   ↓
Software development (Selmo modeling)
   ↓
Integration & commissioning
   ↓
Validation & CE documentation
```

***

```mermaid


```

### 📘 **Phase Handoffs at a Glance**

| Phase                                | Input                  | Result / Handover                             | acceptors                        |
| ------------------------------------ | ---------------------- | --------------------------------------------- | -------------------------------- |
| 2. Position in the project lifecycle | Problem, Goal          | Requirements Specification                    | PTF lead                         |
| PTF (P–T–F)                          | Requirements           | PTF Report, Risk Assessment, Function Catalog | Mechanical, Electrical, Software |
| Design                               | PTF output             | CAD, Schematic, Model Structure               | Quality, Software                |
| Software / Selmo                     | PTF + Engineering Data | Process Model (Sequence, Zones, Bit-Control)  | Commissioning                    |
| Commissioning                        | Model & Tests          | Validated Operation                           | Customer, CE                     |
| Operation                            | Acceptance             | Feedback, Improvements                        | PTF Lead, Service                |

***

### 🔎 **Risk Filter – Effect of the PTF**

```
Customer Requirement
   ↓
[ PTF – Process Understanding & Risk Review ]
   ↓
      ▫ Non-Selmo-compliant items identified
      ▫ Risks documented
      ▫ Measures defined
   ↓
Mechanical / Electrical / Software only start
when all PTF topics are released.
```

→ Thus the **PTF becomes the first risk barrier** in the project\
and ensures that **every subsequent technical implementation is standards-compliant, verifiable and deterministic** is.

***

### 🧱 **Target Image – Equal Standing of the Disciplines**

| Discipline | Document                      | Goal                     | , follow the same basic principles: |
| ---------- | ----------------------------- | ------------------------ | ----------------------------------- |
| mechanics  | Technical drawing             | Form, movement, geometry | Dimensional inspection              |
| Electrical | Schematic / EPLAN             | Energy, signal flow      | Wiring test                         |
| Software   | **Selmo PTF & Process Model** | Behavior, logic, safety  | Formal verification                 |

→ The PTF is therefore the **"drawing of the machine behavior"**,\
formal, traceable and verifiable – equivalent to the classic design documents.

### 🎯 **Key Message for Kick-off and Management**

> The PTF is **at the beginning of every project**.\
> It is not an additional document, but the **common denominator of all disciplines**.
>
> It describes the process before anything is built –\
> checks technologies before they are ordered –\
> and defines functions before they are programmed.
>
> In doing so, Selmo creates a **new standard of digital engineering**:\
> documented, formally verifiable, deterministic and standards-compliant.


---

# 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/overall-project-workflow-with-ptf-integration-according-to-selmo-standard.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.