> 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/checklist-execution-of-process-modeling.md). # ✅ Checklist – Execution of process modeling ### **Goal** This checklist ensures the **methodically correct, comprehensible and verifiable execution** of the process modeling.\ It serves the modeler, the PTF lead and the project management as a reference for status, quality and release status. *** ### **1. Preparation** | Checkpoints | Responsible | Status | | ---------------------------------------------------------------------- | ----------------------- | ------ | | \[ ] Project created in Selmo Studio (Plant level defined) | Automation | ☐ | | \[ ] PTF data successfully imported (XML / JSON) | PTF lead | ☐ | | \[ ] Structure plan (Plant → HWZ → SEQ → Zone) created | Automation / mechanics | ☐ | | \[ ] All signals (inputs, outputs, inouts, mems) imported and assigned | Electrical / automation | ☐ | | \[ ] CMZ and MXIC data available and assignable | Safety / CE | ☐ | | \[ ] Function sheets imported into the function editor | Automation | ☐ | | \[ ] Parameter lists imported (parameter layer) | Process / Automation | ☐ | | \[ ] Responsibilities in the model team clearly defined | Project management | ☐ | *** ### **2. Model structure – systematics and layers** | Checkpoints | Responsible | Status | | --------------------------------------------------------------------------- | ----------------------- | ------ | | \[ ] Plant level created with overarching CMZ | Automation / Quality | ☐ | | \[ ] Hardware zones (HWZ) created with operating modes (manual / automatic) | Automation / mechanics | ☐ | | \[ ] Sequences (SEQ) created and named (according to process steps) | Automation | ☐ | | \[ ] Zones assigned in each SEQ (sensors, actuators, mems) | Automation / electrical | ☐ | | \[ ] System layer (bit control) created: 0, i, S, M defined | Automation | ☐ | | \[ ] Logic layer created: states, timers, decisions, jumps | Automation | ☐ | | \[ ] SEQCross modeled (dependencies between sequences) | Automation / process | ☐ | | \[ ] Parameter layer supplemented (times, tolerances, limits) | process | ☐ | | \[ ] CMZ defined at plant, HWZ and SEQ level | Safety / CE | ☐ | | \[ ] MXIC defined (manual operation logic / interlocks) | Automation / safety | ☐ | | \[ ] HMI texts and diagnostic points assigned | Automation / Operation | ☐ | *** ### **3. Testing & simulation** | Checkpoints | Responsible | Status | | ------------------------------------------------------- | ----------------------------- | ------ | | \[ ] Model validator (consistency check) without errors | Automation / Quality | ☐ | | \[ ] CMZ/MXIC behavior tested | Safety / CE | ☐ | | \[ ] SEQCross logic checked (sequence order correct) | Automation / process | ☐ | | \[ ] Parameter functions tested (simulation mode) | Automation / process | ☐ | | \[ ] Automatic and manual operation checked | Automation / Operation | ☐ | | \[ ] Simulation (SoftFAT or digital twin) executed | Automation / Quality | ☐ | | \[ ] Review meeting documented (results, open items) | PTF lead / Project management | ☐ | *** ### **4. Output creation** | Checkpoints | Responsible | Status | | ------------------------------------------------------------------- | ----------------------------- | ------ | | \[ ] PLC code generated and version documented | Automation | ☐ | | \[ ] HMI project generated and checked | Automation / Operation | ☐ | | \[ ] Documentation (system, logic, parameters, safety, HMI) created | Automation / Quality | ☐ | | \[ ] Safety document (CMZ/MXIC) exported | Safety / CE | ☐ | | \[ ] Function library updated (standard functions) | Automation | ☐ | | \[ ] Digital twin export created (JSON/FMUs) | Automation / simulation | ☐ | | \[ ] Review & approval by PTF lead completed | Project management / customer | ☐ | *** ### **5. Final check and approval** | Checkpoints | Responsible | Status | | ----------------------------------------------- | ----------------------------- | ------ | | \[ ] Model fully documented and versioned | PTF lead | ☐ | | \[ ] All test protocols filed | Quality | ☐ | | \[ ] Review report created and approved | Project management | ☐ | | \[ ] Customer / operator informed and confirmed | Project management / customer | ☐ | | \[ ] Model released as "Selmo-Ready" | PTF lead | ☐ | *** ### **6. Notes for quality assurance** * Changes to the model may only be made by authorized modelers. * Every change must be versioned and documented. * Non-Selmo-conforming deviations are marked in the model as **risk points** marked. * The PTF lead performs a complete validation before each release. *** ### **7. Release status** | Assessment | Meaning | | ------------------------------- | ------------------------------------------------- | | 🟢 **Released** | All checkpoints met, no open risks | | 🟡 **Approved with conditions** | Model correct, but outstanding evidence | | 🔴 **Not approved** | Missing inputs, deviations or safety deficiencies | --- # 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/checklist-execution-of-process-modeling.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.