> 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-process-modeling/checklists-_templates/selmo-process-modeling-checklist-for-supplier-and-input-startup-phase.md). # ✅ Selmo process modeling – Checklist for supplier & input (startup phase) ### **Purpose of the checklist** This checklist ensures that **all professional and technical foundations from the PTF** are available before modeling begins.\ It is intended to prevent work in Selmo Studio based on assumptions or missing information leading to interpretation errors. > Process modeling may **only start**, when all mandatory inputs **are complete, released and reviewed** are present. *** ### **1. Supplier checklist – Who delivers what** | No. | Supplier / Role | Area of responsibility | Delivers | Format | Released by | Status | | --- | --------------------------------- | ------------------------------------ | --------------------------------------------------- | ------------------ | --------------------- | ---------------------------- | | 1 | **PTF lead / Project management** | Overall coordination, PTF release | Released PTF dataset (Report, Scope, Release) | PDF / XML | Management / Customer | ☐ open ☐ reviewed ☐ released | | 2 | **Process owner (IE)** | Process description and parameters | Process flow (PTF-PROC), parameter list (PTF-PARAM) | Excel / PDF | PTF lead | ☐ open ☐ reviewed ☐ released | | 3 | **Mechanics / Design** | Construction, layout, components | Technology matrix (PTF-TECH), structure definition | Excel / PDF | PTF lead / Mechanical | ☐ open ☐ reviewed ☐ released | | 4 | **Electrical / Control (E-Plan)** | Sensors, actuators, signal structure | I/O list (PTF-IO), safety circuits | CSV / EPLAN export | Automation / PTF lead | ☐ open ☐ reviewed ☐ released | | 5 | **Automation / Software** | Functional logic, states, safety | Function sheets (PTF-FUNC), safety (PTF-SAFE) | XML / PDF | PTF lead | ☐ open ☐ reviewed ☐ released | | 6 | **Quality / Safety / CE** | Standards, risk, safety | Risk assessment (PTF-RISK), CMZ/MXIC specifications | Excel / PDF | Quality / CE | ☐ open ☐ reviewed ☐ released | | 7 | **IT / OT / MES / ERP** | Data interfaces | Communication description (PTF-IF) | JSON / YAML / PDF | Automation | ☐ open ☐ reviewed ☐ released | | 8 | **Operation / Maintenance** | Operator concept | HMI texts and diagnostic requirements (PTF-HMI) | CSV / Excel | Automation / Quality | ☐ open ☐ reviewed ☐ released | *** ### **2. Input checklist – What must be available** | No. | Input / Data object | Description | Source | Format | Status | | --- | ------------------------------------ | ------------------------------------------------------------------ | ------------------------------- | ------------------ | --------------------- | | 1 | **Released PTF report** | Contains all reviewed requirements (Process, Technology, Function) | PTF lead | PDF | ☐ available ☐ missing | | 2 | **PTF-XML / JSON** | Machine-readable data basis for import into Selmo Studio | PTF lead / Automation | XML / JSON | ☐ available ☐ missing | | 3 | **Structure definition** | Plant, HWZ, SEQ, Zone – hierarchy plan | Mechanical / Project management | PDF / Excel | ☐ available ☐ missing | | 4 | **I/O list** | Complete signal list incl. type, address, CMZ level | Electrical | CSV / EPLAN export | ☐ available ☐ missing | | 5 | **Function sheets** | Defined functions with inputs, outputs, triggers, test cases | Automation | XML / PDF | ☐ available ☐ missing | | 6 | **Parameter list** | Process parameters (units, limits, default values) | Process / Quality | Excel / CSV | ☐ available ☐ missing | | 7 | **Safety definition (CMZ/MXIC)** | Safety zones, interlock rules, safety levels | Safety / CE | Excel / PDF | ☐ available ☐ missing | | 8 | **Interface description (MES/ERP)** | Communication structure, tags, topics, payloads | IT / OT | JSON / YAML | ☐ available ☐ missing | | 9 | **HMI texts & messages** | Operator guidance, error messages, colors | Operation / Maintenance | CSV / Excel | ☐ available ☐ missing | | 10 | **Risk assessment & deviation list** | Documented risks / non-Selmo conformities | Quality / PTF lead | Excel / PDF | ☐ available ☐ missing | *** ### **3. Structure-relevant minimum information** Before starting modeling the following information must be available: | Category | Must contain | Source | | ------------------------ | ----------------------------------------------------------- | ------------------------------- | | **Plant** | Name, plant ID, parent CMZ, communication interfaces | Project management / Mechanical | | **Hardware zones (HWZ)** | Zone name, operating modes, safety assignment, power supply | Mechanics / Electrical | | **Sequences (SEQ)** | States, transitions, parameters, process objective | Process / Automation | | **zones** | Signal name, type (Input, Output, InOut, Mem), CMZ level | Electrical | | **Bit control table** | Assignment State ↔ Zone (0, i, S, M) | Automation | | **parameter layer** | Process variables, units, value ranges | process | | **CMZ & MXIC** | Safety and manual operation definitions | Safety / CE | | **HMI level** | Texts, colors, messages | Operation / Automation | *** ### **4. Quality and start criteria** The **Start of modeling** is only approved when: * [ ] The **PTF release** is available (released and versioned). * [ ] The **I/O list** is complete and reviewed. * [ ] All **Zones, signals and CMZ levels** are defined. * [ ] All **Parameters** are described with units, limits and default values. * [ ] The **Function sheets** are complete (inputs, outputs, behavior, test cases). * [ ] The **Safety rules (CMZ/MXIC)** are agreed. * [ ] The **HMI data** are available (texts, colors, diagnostics). * [ ] The **Interface description** is reviewed. * [ ] The **Risk assessment** is completed and documented. * [ ] The **Project management** has formally approved the start of modeling. *** ### **5. Responsibility overview (RACI)** | Phase / Task | Responsible (R) | Accountable (A) | Consulted (C) | Informed (I) | | ------------------------------------ | ---------------------- | --------------------- | ------------------- | ------------------ | | Provision of PTF data | PTF lead | Project management | Process, Automation | Customer | | Process description / Parameters | Process owner | PTF lead | Quality | Automation | | Structure definition (Plant/HWZ/SEQ) | mechanics | Project management | Electrical, Process | PTF lead | | I/O and safety definition | Electrical / CE | PTF lead | Automation | Quality | | Function definition / Logic | Automation | PTF lead | Process, Safety | Project management | | HMI and diagnostics | Automation / Operation | PTF lead | Quality | Customer | | Interface description | IT / OT | PTF lead | Automation | Project management | | Start approval modeling | Project management | Customer / Management | all | all | *** ### **6. Review questions before modeling begins** Before the modeler begins, the PTF lead must check the following points: * [ ] Are all PTF data released and importable (XML / JSON)? * [ ] Is the structure (Plant, HWZ, SEQ, Zones) clearly defined? * [ ] Are function definitions (adders, timers, test logic etc.) available? * [ ] Are CMZ and MXIC rules clearly and comprehensibly described? * [ ] Is the safety level (PLr / SIL) documented? * [ ] Are there open risks or known non-Selmo conformities? * [ ] Are interfaces (MES, ERP, robotics) specified? * [ ] Is responsibility for changes clearly defined? * [ ] Has a review meeting with all suppliers been held? * [ ] Is the start date and the person responsible for modeling determined? *** ### **7. Result of the checklist** **Release recommendation:** * ☐ Modeling can start (all prerequisites met) * ☐ Modeling delayed (missing data) * ☐ Start with reservation (risks documented) **Released by:**\ Project management / PTF lead\ **Date:**\ **Version:** *** ### **8. Conclusion** > The start of process modeling is not a creative act, but a formal step. > > Only when all information from the PTF, the mechanical design, electrical planning and safety is fully available,\ > can the model be built deterministically and traceably. > > This checklist is the “zero measurement” –\ > it shows whether the project is ready to move from the **definition** to the **implementation** . --- # 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-process-modeling/checklists-_templates/selmo-process-modeling-checklist-for-supplier-and-input-startup-phase.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.