Glossary · Systems engineering and MBSE
Operating assumption
German: Betriebsannahme
In systems engineering, an operating assumption is a documented condition under which the system is expected to operate correctly, such as network, timing, role or maintenance conditions. If the condition does not hold, the analyses and evidence that rely on it may no longer be valid.
- Systems engineering
- Functional safety
- German source term
In one sentence
An operating assumption records a condition the system relies on in operation, such as network timing or trained staff, so it can be monitored and handed over.
Example
The safety concept of an AGV fleet assumes that floor markings are kept clean and that the wireless network delivers stop commands within 100 ms; both are recorded as operating assumptions and passed to the operator.
How it applies
- Evidence: Link every operating assumption to the analyses and claims that depend on it. When the assumption is violated, those items need review.
- Technical documentation: Assumptions that the user must maintain belong in the information for use as conditions or instructions, for example maintenance intervals or network requirements. An assumption known only to the designer is not controlled.
- Machine safety: Assumptions are closely related to intended use. They should be realistic and, where possible, monitored by the system.
- Integrated systems: Assumptions about neighboring systems (timing, stop behavior) should appear in the interface documents and be confirmed by the other party.
- Operation: Operational feedback is the main way to detect assumptions that do not hold in the field.