> 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/automatic-mode.md).

# Automatic mode

## 6.2 Automatic operation

The **Automatic operation** is the operating mode in which the system executes the modelled sequence autonomously.

A central principle applies:

> **In automatic mode the system drives the sequence –**\
> **not the operator.**

Automatic mode is **not its own logic**,\
but a **system-driven execution of the same model**.

***

### Prerequisites for automatic mode

For a sequence to run in automatic mode, the following conditions must be met:

* the hardware zone is set to **Automatic operation** switched on
* a valid **automatic enablement** is present
* no interlock (`i`) deviation is active
* no CMZ deviation is active

Only when these prerequisites are met may the sequence continue automatically.

***

### Sequence in automatic mode

In automatic mode the following applies:

* the sequence is in **exactly one state**
* this state defines expected behaviour (system layer)
* the system continuously evaluates:
  * whether expectations are met
  * whether mandatory conditions are complied with

The sequence proceeds deterministically:

1. A state becomes active
2. `S`-zones define expected behaviour
3. The system waits for fulfilment
4. The state is considered fulfilled
5. The transition to the next state occurs automatically

> **The sequence does not react to events,**\
> **but to the current model state.**

***

### Behaviour in case of deviations

#### Interlock deviation (`i`)

If a condition defined as `i` is violated:

* the automatic release is **immediately revoked**
* the affected sequence stops
* the current state is retained
* a clear diagnosis is generated

There are:

* no continuation
* no transition
* no interpretation

***

#### CMZ deviation

If a CMZ is violated:

* the reaction takes place **hierarchically**:
  * sequence level
  * hardware zones level
  * plant level
* all affected sequences are stopped
* **no movement is possible anymore**

CMZ deviations act:

* state-independent
* independent of operating modes

***

### Diagnosis in automatic mode

Diagnosis is created in automatic mode **automatically** from the model.

A diagnosis can be uniquely assigned to:

* a sequence
* a state
* a zone
* an expectation or condition

There are:

* no aggregated messages
* no manually programmed error texts
* no interpretation-dependent messages

> **The diagnosis explains,**\
> **why the sequence does not continue.**

***

### Distinction from manual mode

To clarify:

* Automatic operation
  * System drives the process
  * Transitions occur automatically
  * Operator does not intervene in the sequence
* Manual operation
  * Operator influences zones
  * States are deliberately fulfilled
  * Sequence is not continued automatically

Both operating modes:

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

***

### Typical misconceptions about automatic mode

Common misunderstandings are:

* ❌ “Automatic is a faster manual operation”
* ❌ “Automatic skips states”
* ❌ “Automatic briefly ignores deviations”
* ❌ “Automatic is more tolerant than manual mode”

All of these assumptions are false.

> **Automatic is the strictest operating mode,**\
> **because it is completely model-driven.**

***

### Summary

Automatic mode:

* executes the modelled sequence autonomously
* reacts deterministically to deviations
* generates automatic, unambiguous diagnosis
* knows no special cases or shortcuts

> **Automatic means:**\
> **The model is in control.**


---

# 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/automatic-mode.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.