> 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/ptf-checklists/selmo-ptf-checklist-supplier-and-inputs.md). # ✅ Selmo PTF Checklist – Supplier & Inputs #### **Objective of the checklist** This checklist ensures that all **necessary information, documents and data** for the PTF process are available, reviewed and released.\ It defines **who delivers what**, in **which format**, **when**, and **who checks**, whether the information is ready for the PTF. The PTF can only be started when all mandatory inputs are available or are bindingly scheduled. *** #### **1. Supplier checklist** | No. | Supplier / role | Area of responsibility | Delivers (PTF artifact) | Format | Checked by | | --- | -------------------------------------- | ---------------------------------------------------------------------- | ----------------------- | -------------------- | --------------------- | | 1 | Process owner / Industrial Engineering | Process description, sequence, parameters, cycle time, quality targets | PTF-PROC, PTF-PARAM | Excel / PDF | PTF lead | | 2 | Mechanics / Design | Construction, kinematics, layout, end positions, interfaces | PTF-TECH, PTF-IO | STEP / Excel | PTF lead / Electrical | | 3 | Electrical / Control (E-Plan) | Sensors, actuators, addressing, safety circuits | PTF-IO, PTF-SAFE | Excel / EPLAN export | Automation | | 4 | Software / Automation (Selmo) | Function sheets, state logic, bit-control rules | PTF-FUNC, PTF-SAFE | XML / PDF | PTF lead | | 5 | IT / OT / MES / ERP | Interfaces, communication protocols, data fields | PTF-IF | JSON / YAML / PDF | Automation / PTF lead | | 6 | Quality / Safety / CE | Standards requirements, risk assessment, safety level | PTF-SAFE, PTF-RISK | PDF / Excel | Project management | | 7 | Management / project management | Project goals, scope, budget, schedule | PTF-SCOPE, PTF-RELEASE | PDF / Word | Customer | | 8 | Customer / Operator | Requirement description, process objective, operating conditions | PTF-REQ | PDF / Word | PTF lead | | 9 | IT security / data protection | Security, access, communication policies | PTF-SEC | PDF / YAML | Quality / IT | | 10 | Maintenance / operations | Requirements for operation, diagnosis, maintenance | PTF-HMI | Excel / CSV | PTF lead / Quality | *** #### **Supplier quality characteristics** Each supplier must confirm before PTF start that their data: * are unambiguous (no contradictory terms or states), * are complete (contain all relevant information), * are verifiable (testable by test cases, measurement points or limits), * comply with standards (CE, ISO 12100, ISO 13849, MVO 2027), * are versioned (with date, author and reason for change), * are released (internally reviewed and documented). *** #### **2. Input checklist** | No. | PTF artifact | Description | Mandatory / optional | Source (supplier) | Format | | --- | ------------ | ---------------------------------------------------------------------- | -------------------- | ----------------------------- | ------------------ | | 1 | PTF-PROC | Complete process description with states, transitions and conditions | Mandatory | Process owner | Excel / PDF | | 2 | PTF-PARAM | Process parameters (times, forces, temperatures, limits) | Mandatory | Process / quality | Excel / CSV | | 3 | PTF-TECH | Overview of all technologies, devices, media, systems used | Mandatory | Mechanics / Electrical | Excel / PDF | | 4 | PTF-IO | Signal list with addresses, signal names, CMZ level, zones | Mandatory | Electrical / control | CSV / EPLAN export | | 5 | PTF-FUNC | Definition of functions (inputs, outputs, triggers, test cases) | Mandatory | Automation | XML / PDF | | 6 | PTF-SAFE | Safety concept (interlocks, CMZ, MXIC, PLr/SIL) | Mandatory | Safety / CE | Excel / PDF | | 7 | PTF-IF | Interface description (MES, ERP, SCADA, robot, cloud) | Mandatory | IT / OT | JSON / YAML / PDF | | 8 | PTF-HMI | Operation concept, texts, messages, diagnostics | Optional | Maintenance / software | Excel / CSV | | 9 | PTF-RISK | Risk list and assessment of deviations (process, technology, function) | Mandatory | Quality / Safety | Excel / PDF | | 10 | PTF-RELEASE | Release document with signatures of all responsible parties | Mandatory | Project management | PDF | | 11 | PTF-SCOPE | Project scope, boundaries, system definition | Mandatory | Project management / customer | PDF / DOCX | | 12 | PTF-SEC | Security and communication policies | Optional | IT / security | PDF / YAML | *** #### **Structuring of inputs in the project directory** Recommended project structure: * **00\_Scope** → PTF-SCOPE * **01\_Process** → PTF-PROC, PTF-PARAM * **02\_Technology** → PTF-TECH, PTF-IO, PTF-IF * **03\_Function** → PTF-FUNC, PTF-SAFE * **04\_Quality** → PTF-RISK, PTF-NORM * **05\_HMI** → PTF-HMI * **06\_Release** → PTF-RELEASE Example path:\ /PTF/03\_Function/PTF-FUNC\_v1.0.xml *** #### **Input control (before PTF start)** Before starting the PTF phase the following points must be fulfilled: * [ ] All suppliers named and confirmed in writing * [ ] All mandatory inputs are fully available * [ ] All documents are versioned and stored * [ ] All relevant standards have been considered (ISO 12100, ISO 13849, IEC 62061, MVO 2027) * [ ] Risks and deviations are documented or scheduled * [ ] Project management has granted PTF release *** #### **Recommendations for practice** * Consistent naming conventions (e.g. `PTF-PROC_v1.0.xlsx`) * Conduct regular PTF reviews * Regularly check inputs for Selmo conformity (determinism, verifiability, documentation) * Provide all inputs with change and release history * Immediately report incomplete or non-verifiable data back to the supplier *** #### **Conclusion** The success of the Selmo PTF depends directly on the **completeness and quality of the supplier inputs** depending on it.\ Only when all information is unambiguous, verifiable and documented can a deterministic, traceable and standards-compliant process model be created. This checklist is the basis for **a clean start to the PTF process** and thus for a successful project implementation according to 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/ptf-checklists/selmo-ptf-checklist-supplier-and-inputs.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.