🧩 Overall project workflow with PTF integration according to Selmo standard

Overview Processes and Lanes

🔷 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

---

📘 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.