> 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-documentation/6-operation-of-the-machine-user-view.md).

# 6 Operation of the machine (user view)

## 6. Operation of the machine

This chapter describes, **how a modeled machine is operated**.\
It is not about user interfaces or specific buttons, but about the **fundamental interaction of model, operator and system**.

Operation is in Selmo **no additional logic layer**,\
but a **Perspective on the same model**.

***

### 6.1 Basic principle of operation

A central principle in Selmo is:

> **Operation does not change the logic.**\
> **It only changes who has influence on the model.**

This means:

* Sequences remain unchanged
* States remain valid
* Bit control remains active
* Monitoring remains effective
* CMZ operates independently of the operating mode

There are:

* no second sequence definition
* no bypass
* no special code for operation

***

### Shared state space

Regardless of the operating mode, the following applies:

* every sequence is always in **exactly one state**
* this state defines expectations and monitoring
* Deviations are unambiguously assessable

Manual and automatic operation work **in the same state space**.

> **Manual operation is not a parallel world,**\
> **but targeted interaction within a valid state.**

***

### Roles in operation

Operation clearly distributes responsibility:

* **System**
  * evaluates the model state
  * monitors conditions
  * responds deterministically
* **Operator**
  * influences zones purposefully
  * establishes states
  * does not make logic decisions
* **hardware zone**
  * provides operating modes
  * manages automatic releases
  * coordinates starts and stops

***

### Automatic and manual operation – classification

Selmo distinguishes two operating modes:

* **Automatic operation**
  * the system drives the sequence
  * state transitions occur automatically
  * Monitoring reacts immediately to deviations
* **Manual operation**
  * the operator influences zones manually
  * The goal is the fulfillment of state conditions
  * Monitoring remains fully active

Both operating modes:

* use the same model
* are subject to the same rules
* produce the same diagnostics

***

### Safety in operation

Safety-relevant mechanisms take effect **always**, regardless of operation:

* Interlocks (`i`) protect the sequence
* CMZ protects system integrity
* MXIC protects against unauthorized manual actions

There are:

* no “service mode” without monitoring
* no manual operation without safety
* no exception to the model logic

> **Operation is not a safety concept –**\
> **Safety is anchored in the model.**

***

### Structure of this chapter

Chapter 6 is divided into the following parts:

#### 6.1 Basic principle Operation

→ shared state space\
→ operation ≠ logic

#### 6.2 Automatic operation

→ system-driven sequence\
→ error responses\
→ diagnostic behavior

#### 6.3 Manual operation

→ state-by-state work\
→ visual feedback\
→ safe positioning

#### 6.4 MXIC – Manual Cross Interlock

→ protection logic for manual actions\
→ diagnosis instead of movement

***

### Transition to the details

The following sections describe:

* how automatic operation works concretely
* how manual operation works safely
* how manual actions are limited

> **Operation makes the model usable –**\
> **without changing it.**


---

# 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-documentation/6-operation-of-the-machine-user-view.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.