> 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/embedding-the-selmo-ptf-into-the-overall-project-workflow.md). # Embedding the Selmo-PTF into the overall project workflow ### **1. Basic idea** The **Selmo-PTF (Process – Technology – Function)** is the **first and binding phase** of every machine or plant project, where the specification or the concept is created.\ It is **carried out** before * **mechanical, electrical and software design and defines:** * **the problem (what should be achieved?)** * **the process (how does the sequence run physically and logically?)** * **the technology (which means, components, interfaces are used?)** the functions (how is the behavior formally represented and verified?) **The PTF is therefore the**formal problem description and solution definition **from which** all other engineering disciplines **derive their work.**\ **It stands on the same level as** and **mechanical drawing**electrical schematic **, but forms the** digital behavior description **Process model**. *** ### **– the** ``` 2. Position in the project lifecycle ↓ Customer inquiry ↓ Requirements analysis (Requirements) ↓ → PTF process (Process – Technology – Function) ↓ Mechanical & electrical design ↓ Software development (Selmo modeling) ↓ Integration & commissioning ↓ Validation & CE documentation ``` #### Handover to operations & service * The **PTF** forms the **🔹 Classification:**. * Transition phase between customer and engineering **All requirements (functional, safety-related, economic) are**verified here * before anything is designed or programmed. **Changes are**. > **cheapest and least risky**\ > in this phase *** ### **Principle:** 1. **Errors detected in the PTF cost hours.**\ **Errors that only appear in the code cost weeks.**\ 3\. Objective of the early PTF phase 2. **Understand the problem before solutions are created.**\ – Focus on process understanding and customer benefit. 3. **Establish engineering conformity.**\ – Alignment of all disciplines to common standards. 4. **Ensure Selmo conformity.**\ – Only deterministic, verifiable process models are accepted. 5. **Identify and assess risks.**\ – Early risk assessment (technical, organizational, economic). *** ### **Create traceability.** | – Seamless documentation from requirement to code. | 4. Integration into the engineering process | Engineering phase | | --------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------- | | **Role of the PTF** | Result / benefit | Pre-sales / proposal | | **Clarifies the process goal with the customer, provides reliable data for proposal & effort estimation** | Better costing, clear expectations | Requirements engineering | | **Formulates the problem in PTF structure (process, technology, function)** | Unambiguous, verifiable requirements | Mechanical / electrical design | | **Uses PTF to determine the required components & signal structure** | Avoidance of design errors | Software / automation | | **Quality / Safety / CE** | Creates Selmo process model directly from PTF output | Complete traceability, no room for interpretation | | **Operations / Service** | Assesses PTF risks & standards compliance | Demonstrable safety & documentation | *** ### **Uses PTF documentation for training & diagnosis** Transparent operation & maintenance **5. Early verifiability and changeability** Since the PTF * **is created before design** the following can be done: * **Process sequences can still be changed** and **before they are implemented expensively,** Non-Selmo-compliant technologies can be identified * **and** adapted * **Functions can be standardized** and made reusable, * and **Costs and complexities** can be reduced, Risks are proactively assessed **instead of being treated reactively.**→ Thus the PTF becomes the *** ### **strategic filter** :\ Only what is methodical, normative and technically consistent may go into implementation.\ **6. PTF as a formal description language of digital engineering** | Discipline | Formal language | With the Selmo method applies: | Goal | | ------------------------- | ------------------------------------------------------------------- | ------------------------------ | ------------------------- | | **mechanics** | As the drawing describes the mechanics, the PTF describes the code. | Evidence | CAD / technical drawing | | **Electrical** | Bill of materials, dimensions, tolerances | Form and function | Circuit diagram / E-plan | | **Automation / Software** | **Wiring, circuit, protection circuits** | Energy and signal flow | Selmo-PTF / process model | Process, logic, monitoring **Behavior and control**→ All three disciplines are * Documentation * equivalent * , follow the same basic principles: * Traceability Verifiability **MVO 2027** formal correctness\ **Thus Selmo meets the demands of** *** ### **and other regulations for** "complete documentation, formal verifiability and deterministic behavior". * **7. Dealing with deviations and risks** . **During the PTF:**Non-conforming requirements or technologies are **not discarded**. * but * transparently documented and assessed **Each deviation receives:** a * risk rating **(critical / moderate / acceptable)** * risk rating **a** responsible person **a planned action path**→ This creates a *** ### **controlled risk landscape** | that can be actively managed. → Changes in the PTF are traceable and verifiable – no "telephone-game knowledge" in the project. | Benefit | | ----------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | | **8. Benefits of early integration** | Dimension | | **Technical** | Early detection of conflicts between mechanics, electrical and software | | **Organizational** | Unified language, clear responsibilities | | **Economic** | Lower change and commissioning costs | | **Qualitative** | Higher stability, lower failure risks | | | | Legal / normative * Demonstrable conformity (MVO 2027, CE, ISO 12100 etc.) * The PTF process serves to: * Understand the customer's problem exactly, * Describe the process completely, * Check the technologies used for Selmo conformity, Define the functions in a documented and verifiable way, ### **9. Conclusion** > The **Detect risks, deviations and regulatory requirements early.** → Result: A complete, verifiable machine model – as a basis for mechanics, electrical and software. **Selmo-PTF**. > > is the new starting point of every project.\ > It replaces incomplete specifications with a **formal, verifiable and deterministic description** > > Even before mechanics are drawn or circuit diagrams are created,\ > it is clear **what the machine should do, with what it does it and how it behaves.** Thus the PTF becomes the **engineering standard**–\ > for the --- # 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/embedding-the-selmo-ptf-into-the-overall-project-workflow.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.