> 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-structure-and-standard/selmo-technical-standard-and-structure/selmo-method-in-practice/process-modeling-with-selmo-inputs-activities-outputs.md).

# 🔷 Process modeling with Selmo – Inputs, activities, outputs

#### 🔹 1. **Inputs – What is needed?**

| Category                          | Description                                                                         |
| --------------------------------- | ----------------------------------------------------------------------------------- |
| **process description**           | Rough sequence from the PTF phase (e.g. loading → clamping → machining → unloading) |
| **Functions & Conditions**        | Logically formulated functions (e.g. “clamp when part detected”)                    |
| **Signal overview**               | Complete list of inputs and outputs, sensors, actuators, manual buttons             |
| **Zoning concept (draft)**        | Initial grouping of signals into zones (Input, Output, In-Out, Mem)                 |
| **Parameter list**                | Times, positions, repetition counts, tolerance values, etc. from the PTF            |
| **Operating mode specifications** | Which operating modes are required (manual, automatic, setup mode)                  |
| **Safety requirements**           | Requirements for interlocks, monitoring, locking (CMZ, MXIC)                        |

***

#### 🔹 2. **What is done? (Activities in the modeling)**

| Step                       | Description                                                           |
| -------------------------- | --------------------------------------------------------------------- |
| **Build sequence**         | Logical flow with states, transitions, decision points                |
| **Assign zones**           | Assign signals to states via zones                                    |
| **Define bit control**     | Define behavior of each zone per state (0, i, S)                      |
| **Integrate safety logic** | Create CMZ, MXIC, pair-check                                          |
| **Link parameters**        | Insert parameterizable values and integrate them into the flow        |
| **Add sequence cross**     | Synchronization between sequences if needed                           |
| **Check completeness**     | Define logic and system layers completely, check for consistent flows |

***

#### 🔹 3. **Outputs – What is the result of the modeling?**

| Result                                    | Description                                                     |
| ----------------------------------------- | --------------------------------------------------------------- |
| ✅ **Finished sequence(s)**                | State-based model with clear process structure                  |
| ✅ **System layer with bit control**       | Each zone is fully linked to the logical flow                   |
| ✅ **Safety functions integrated**         | Error response, interlock logic, operator protection integrated |
| ✅ **Parameterization implemented**        | Time values, switching points, etc. centrally configurable      |
| ✅ **Export-ready model**                  | Handover to PLC, HMI, diagnostics, simulation possible          |
| ✅ **Basis for automatic code generation** | Everything is documented traceably in a model-based way         |


---

# 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-structure-and-standard/selmo-technical-standard-and-structure/selmo-method-in-practice/process-modeling-with-selmo-inputs-activities-outputs.md?ask=<question>&goal=<endgoal>
```

`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.