✅ Selmo PTF – Output & Customer checklist
1. Purpose of the checklist
This checklist serves to Ensure completeness, quality and usability of all PTF results. It describes:
Which Outputs arise from the PTF process,
How they are approved and distributed Non-Selmo-compliant technologies can be identified
And which Customer (Stakeholder) use the results in which form use.
2. Output checklist
1
PTF report (complete document)
Summary of all PTF results (Process, Technology, Function)
Mandatory
PDF / DOCX
Project management / PTF lead
Complete, consistent, approved
2
PTF model data (structural model)
Exported machine model (Plant → HWZ → Sequence → Zones → Bit-Control)
Mandatory
XML / PLCopen / JSON
Automation / PTF lead
Structure complete, importable into Selmo
3
PTF-RISK
Risk assessment of all deviations and non-Selmo conformities
Mandatory
Excel / PDF
Quality / Safety
Risks assessed, measures defined
4
PTF-RELEASE
Formal approval for implementation (signatures of all responsible parties)
Mandatory
Project management / customer
Signed, approved, versioned
5
PTF-FUNC
Complete function sheets (inputs, outputs, limits, test cases)
Mandatory
XML / PDF
Automation / Quality
Testable, tested, documented
6
PTF-HMI
Operating concept with HMI texts, colors, messages and diagnostics
Optional
CSV / JSON
Maintenance / Quality
HMI texts correctly assigned
7
PTF-TECH
Technology matrix with components, media, interfaces
Mandatory
Excel / PDF
Mechanics / Electrical
All components represented
8
PTF-IF
Interface description to external systems (MES, ERP, SCADA)
Mandatory
JSON / YAML
IT / OT
Communication structure defined
9
PTF-SAFE
Safety logic (interlocks, CMZ, MXIC, PLr/SIL)
Mandatory
Excel / PDF
Safety / CE
Safety concept complete and traceable
10
PTF-Q
Quality plan and test strategy (SPC, limit patterns, DoE)
Optional
Excel / PDF
Quality
Test processes defined
11
PTF-FINAL / Lessons Learned
Documentation after completion (audit trail, improvements)
Optional
PTF lead / Project management
Complete traceability
12
PTF-NORM / Compliance
Proof of considered standards and guidelines (MVO 2027, ISO 12100 etc.)
Mandatory
Quality / CE
Standards listed, conformity assessed
3. Testing and approval criteria for outputs
Before approval the following points must be met:
4. Distribution / storage of outputs
Recommended directory structure:
/PTF/Output/
PTF-Report_v1.0.pdf
PTF-Model_v1.0.xml
PTF-RISK_v1.0.xlsx
PTF-RELEASE_v1.0.pdf
PTF-FUNC_v1.0.xml
PTF-SAFE_v1.0.xlsx
PTF-HMI_v1.0.csv
PTF-IF_v1.0.json
PTF-NORM_v1.0.pdf
Distribution recommendation:
All stakeholders receive access via a central repository (e.g., Git, SharePoint, PLM system).
Only approved documents may be distributed (status: Released).
Archiving requirement for every approved version.
5. Customer checklist
This overview describes, who uses the PTF results, for what, and which concrete benefit they derive from it.
1
Project management / PTF lead
Entire PTF report, PTF-RISK, PTF-RELEASE
Project control, Quality, Decision-making
Transparency, control, traceability
Project management
2
Process owner (IE)
PTF-PROC, PTF-PARAM, PTF-FUNC
Process validation, parameter alignment
Process quality, early fault detection
Process owner
3
Mechanics / Design
PTF-TECH, PTF-IO
Implementation and layout coordination
Avoidance of design errors
mechanics
4
Electrical / control
PTF-IO, PTF-SAFE, PTF-IF
Hardware integration, addressing
Clear assignment of signals
Electrical
5
Software / automation
PTF-FUNC, PTF model data
Creation of the Selmo process model
Deterministic programming, code traceability
Automation
6
Quality / Safety / CE
PTF-RISK, PTF-SAFE, PTF-NORM
Audit, risk assessment, CE documentation
Standards compliance, demonstrability
Quality / CE
7
IT / OT / MES / ERP
PTF-IF, PTF model data
Communication and data integration
Early system tests, stable data exchange points
IT / OT
8
Operation / Maintenance
PTF-HMI, PTF-FUNC, PTF-RISK
Operation, diagnosis, training
Transparent maintenance, reduced downtime
Maintenance
9
Management / Controlling
PTF-Report, PTF-RISK, PTF-RELEASE
Economic evaluation, governance
Project decisions, budget transparency
Management
10
Customer / Operator
PTF-Report, PTF-NORM, PTF-FINAL
Acceptance, operation, audit
Trust, proof of safety and quality
Customer / Operator
6. Approval and communication process
PTF outputs created → by specialist departments
Internal review → by PTF lead, Quality and Safety
Review meeting → all disciplines present
Deviations documented → PTF-RISK updated
Approval → PTF-RELEASE signed
Distribution → central storage + access for all customers
Feedback / Lessons Learned → collected in PTF-FINAL
7. Use of outputs during the project
After PTF release
Basis for Selmo modeling and digital twin
During design
Reference for signal definition and hardware concept
Before commissioning
Preparation SoftFAT / simulation
During operation
Use of HMI, diagnostics, parameter management
In audit / CE inspection
Proof of standards compliance
In service
Fault diagnosis, change management
8. Completion criteria for the output
A PTF is considered fully completed, when:
All PTF documents are created, reviewed and approved
The PTF report is archived as version “Released”
The Selmo model can be imported without deviations
All deviations are assessed and documented
The customer / operator has acknowledged or confirmed the results
9. Conclusion
The Output of the PTF is not a paper document, but a digital twin of the machine logic – complete, verifiable and deterministic.
The Customer receive from it:
Process clarity (Process & logic visible),
Risk transparency (assessed & documented),
equivalent (from requirement to behavior),
trust (through standards compliance & data quality).
The PTF output is the link between engineering and operations, and the basis for Software, audit, quality and digital simulation in the Selmo system.
Last updated
Was this helpful?