> 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-structure-and-standard/selmo-technical-standard-and-structure/selmo-method-in-practice/ptf-inputs-activities-and-outputs.md).

# 📌 PTF – Inputs, activities and outputs

#### 🔷 **1. Inputs – What is needed?**

To start the PTF process, we need **information, requirements and basic knowledge**:

| Category                            | Description                                                                                 |
| ----------------------------------- | ------------------------------------------------------------------------------------------- |
| **process description**             | rough procedure, purpose of the process, machine function                                   |
| **product requirements**            | quality characteristics, tolerances, test conditions                                        |
| **technology ideas**                | suggestions or specifications for technologies to be used (e.g. screwing, bonding, testing) |
| **mechanical concepts**             | information about the planned mechanics (e.g. cylinders, grippers, positionings)            |
| **electrics & sensor technology**   | use of planned sensors, actuators, signal types                                             |
| **previous experience**             | lessons learned from similar plants or predecessor projects                                 |
| **standards & safety requirements** | technical rules, functional safety, test requirements                                       |
| **interface requirements**          | requirements for control, HMI, MES, data flow                                               |

***

#### 🔷 **2. Activities – What is done? (analysis phase)**

| Phase                   | Description                                                                    |
| ----------------------- | ------------------------------------------------------------------------------ |
| **analyze process**     | identify steps, sequences and logical flows                                    |
| **assess technology**   | select, compare and, if necessary, test technologies                           |
| **formulate functions** | derive control logic from physical, mechanical and electrical relationships    |
| **derive parameters**   | define time, position, force, tolerances, etc.                                 |
| **check feasibility**   | alignment between idea, technology and implementation (if necessary iteration) |
| **prepare structure**   | create initial outline into Plant – Tasks – Functions                          |

***

#### 🔷 **3. Output – What is the result of the PTF?**

| Result                                           | Description                                                            |
| ------------------------------------------------ | ---------------------------------------------------------------------- |
| ✅ **cleaned and structured process description** | clearly understandable procedure for modeling                          |
| ✅ **technology decisions**                       | documented selection of the methods used                               |
| ✅ **Function definitions**                       | logically described control functions as a basis for sequence modeling |
| ✅ **Parameter list**                             | time values, positions, test thresholds, etc. with technical relevance |
| ✅ **model structure template**                   | outline for later modeling in Selmo (Plant – Task – Function)          |


---

# 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-structure-and-standard/selmo-technical-standard-and-structure/selmo-method-in-practice/ptf-inputs-activities-and-outputs.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.