> 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/work-breakdown-structure-selmo-process-modeling.md). # 🧩 Work breakdown structure – Selmo process modeling ### **Project goal** Creation of a fully documented, deterministic and Selmo-compliant process model\ based on released PTF, including * Code generation, * HMI structure, * Safety function (CMZ, MXIC), * Integration with Digital Twin, * virtual commissioning (vIBN), * and final review and acceptance phase. *** ### **1. Project overview (top level)** | WBS no. | Phase | Goal | Main deliverable | | ------- | ----------------------------------------- | ------------------------------------------------------------------ | -------------------------------------------- | | **1.0** | Project kick-off | Project start, responsibilities, PTF review | Kick-off minutes, released PTF | | **2.0** | Structure modeling – Plant | Build-up of the top-level structure (TCMZ, parameters, interfaces) | Complete plant structure | | **3.0** | Structure modeling – Hardware zones (HWZ) | Build-up of station or module structure | Complete HWZ with safety and parameters | | **4.0** | Structure modeling – Sequences (SEQ) | Create process logic at SEQ level | Complete SEQs with logic, safety, parameters | | **5.0** | Integration & test | Linking SEQCross, simulation, vIBN | Validated overall model | | **6.0** | Commissioning (IBN) | Real operation, verification with hardware | Accepted machine | | **7.0** | Project closure & review | Documentation, lessons learned, audit | Review report, project release | *** ### **2. Detailed WBS structure** *** #### **1.0 Project kick-off** | WBS no. | Work package | Description | Responsible | Result | | ------- | ---------------------------- | ------------------------------------------------ | ------------------ | ----------------------- | | 1.1 | Project start & organization | Set project team, roles, dates | Project management | Kick-off agenda | | 1.2 | PTF review | Check PTF for completeness & release | PTF lead, process | Released PTF | | 1.3 | Data handover | Handover PTF-XML, I/O, functions, parameters | PTF lead | Importable PTF data | | 1.4 | Set up tools & structure | Create Selmo Studio project, set up repositories | Automation | Project structure ready | | 1.5 | Project start approval | Start approval by project management & customer | Project management | Start minutes | *** #### **2.0 Plant modeling** | WBS no. | Work package | Description | Responsible | Result | | ------- | ---------------------- | ------------------------------------------------- | -------------------- | ------------------------- | | 2.1 | Create plant structure | Create plant in Selmo Studio (plant level) | Automation | Plant structure created | | 2.2 | Define TCMZ | Create Total Constantly Monitoring Zone | Safety / CE | Plant safety logic active | | 2.3 | Define parameters | Plant parameters (e.g. total cycle, power supply) | Process / Automation | Plant parameter list | | 2.4 | Configure interfaces | Communication MES / ERP / SCADA | IT / automation | Interface matrix | | 2.5 | Plant validation | Structure check, safety test | Automation / Quality | Plant level validated | *** #### **3.0 Hardware zones (HWZ) modeling** | WBS no. | Work package | Description | Responsible | Result | | ------- | -------------------- | ------------------------------------------------------------ | ----------------------- | ------------------ | | 3.1 | Create HWZ structure | Create the hardware zones (stations) | Automation / mechanics | HWZ created | | 3.2 | Define TCMZ | Safety zones per HWZ (local CMZ) | Safety / CE | HWZ safety active | | 3.3 | Add parameters | Parameters per station (e.g. cycle time, process parameters) | Process / Automation | HWZ parameters | | 3.4 | Create zones | Zones with signals (sensors, actuators) | Electrical / automation | HWZ zone structure | | 3.5 | HWZ test | Safety and structure check | Quality / automation | HWZ validated | *** #### **4.0 Sequences (SEQ) modeling** This is the core of Selmo modeling: each SEQ is its own controllable model section. | WBS no. | Work package | Description | Responsible | Result | | ------- | ---------------------------- | ------------------------------------------------------- | ----------------------------- | ------------------------ | | 4.1 | Create SEQ structure | Create sequence in the model (function block) | Automation | SEQ object created | | 4.2 | Create logic layer | Model states, transitions, timers, decisions | Automation | SEQ sequence complete | | 4.3 | Define system layer | Bit control: assign signals (0, i, S, M) | Automation / electrical | System layer defined | | 4.4 | Add parameter layer | SEQ-specific parameters (times, tolerances) | process | Parameter layer complete | | 4.5 | Assign functions | Integrate standard functions (adders, timers, checkers) | Automation | Functional logic active | | 4.6 | Configure CMZ | Enable SEQ-related safety monitoring | safety | SEQ safety configured | | 4.7 | Create MXIC | Define manual operation interlocks per zone | Automation / safety | MXIC active | | 4.8 | Connect Digital Twin | Couple SEQ data to simulation (SoftFAT) | Automation / simulation | Virtual connection | | 4.9 | I/O check | Signal test with EPLAN references | Electrical / automation | Signal test OK | | 4.10 | vIBN (virtual commissioning) | Sequence verification in the Digital Twin | Automation / process | vIBN test passed | | 4.11 | IBN (real commissioning) | Sequence verification with real hardware | Automation / service | IBN completed | | 4.12 | Model SEQCross | Logical connection of multiple SEQs | Automation / process | Synchronized sequences | | 4.13 | SEQ acceptance | Function test, documentation, release | Project management / customer | SEQ released | *** #### **5.0 Integration & test (overall model)** | WBS no. | Work package | Description | Responsible | Result | | ------- | ------------------------------ | ------------------------------------------------- | ----------------------- | -------------------------- | | 5.1 | SEQCross overall check | Review all sequence dependencies | Automation | Logic complete | | 5.2 | Full simulation (Digital Twin) | Connect all SEQs in the simulation system | Automation / simulation | Simulation model validated | | 5.3 | Overall model review | PTF reconciliation, safety check, parameter check | PTF lead / Quality | Overall model released | *** #### **6.0 Commissioning (IBN)** | WBS no. | Work package | Description | Responsible | Result | | ------- | ------------------- | ---------------------------------------------- | ----------------------------- | -------------------- | | 6.1 | Hardware check | Check installation and signal availability | Electrical / mechanics | Installation checked | | 6.2 | Load software | Load PLC code to controller | Automation | PLC running | | 6.3 | Test automatic mode | Sequence verification, error responses, safety | Automation / safety | IBN test passed | | 6.4 | Customer acceptance | Joint testing phase | Project management / customer | Acceptance protocol | *** #### **7.0 Project closure & review** | WBS no. | Work package | Description | Responsible | Result | | ------- | -------------------------------- | ---------------------------------------------- | ----------------------------- | ---------------------- | | 7.1 | Documentation & archiving | Model documentation, code, safety, reports | Quality / PTF lead | Complete documentation | | 7.2 | Lessons learned | Evaluation of process & implementation | Project management / team | Improvement measures | | 7.3 | Audit / CE inspection | Check for conformity and safety | Quality / CE | Audit passed | | 7.4 | Project review / closing meeting | Presentation of results, customer satisfaction | Project management / customer | Final report | *** ### **3. Milestone overview** | Milestone | Description | Target date | Acceptance criterion | | --------- | ------------------------------- | ----------- | ------------------------------------ | | **M1** | Project kick-off | Week 0 | PTF release | | **M2** | Plant model completed | Week 2 | Structure, parameters, safety | | **M3** | HWZ complete | Week 4 | Safety logic checked per station | | **M4** | First SEQs modeled | Week 6 | Logic, system, parameters, CMZ, MXIC | | **M5** | All SEQs released | Week 10 | SEQCross validated | | **M6** | Virtual commissioning completed | Week 12 | Simulation error-free | | **M7** | Real commissioning completed | Week 14 | PLC and safety tests passed | | **M8** | Project review & acceptance | Week 16 | Documentation complete | *** ### **4. Project control / organization** | Domain | Responsible | Reporting | | -------------------------- | ---------------------------------------- | -------------------------------------- | | **Project management** | Overall coordination, milestone tracking | Weekly status report | | **PTF lead** | Data integrity, interface PTF ↔ model | Review before start & after completion | | **Automation / Software** | Model construction, simulation, code | Daily engineering review | | **Mechanics / Electrical** | Zone structure, hardware integration | Interface meeting every 2 weeks | | **Safety / CE** | CMZ / MXIC check, standards compliance | Audit protocols | | **Quality** | Approvals, documentation, evidence | Project QA check | | **Customer / Operator** | Acceptance, feedback | Milestone meetings | *** ### **5. Conclusion** > The WBS according to Selmo unites the **technical structure (Plant → HWZ → SEQ)**\ > with the **formal project flow** (Kick-off → modeling → test → review). This creates: * A plannable, controllable engineering approach, * Clear responsibilities for each layer, * Verifiability of each phase, * And a directly auditable project result. **Selmo thus becomes not only the method, but the project management structure for automation.** --- # 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/work-breakdown-structure-selmo-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.