> 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-of-the-logic/requirements-for-the-realization-of-a-machine-with-selmo.md). # Requirements for the realization of a machine with Selmo ### Purpose of the document This document describes the mandatory technical, structural and process-related requirements for a machine that is to be **Selmo standard** modeled, implemented and documented. It serves as: * Basis for technical realization (mechanics, electrical, control) * Basis for specification, planning and system design * Template for validation and verification * Evidence in terms of CE conformity * Interface between design, electrical planning, software development and documentation *** ### 1. General prerequisites * The machine behavior must be fully **modelable** be. * Every sequence must be describable in **logical states** be (state machine). * All safety-related signals must be representable as **zone in the model** be. * No functions may be implemented outside the model. *** ### 2. Technological requirements #### Sensors * All relevant end positions and states must be **detectable by sensors** be. * Sensors must be **uniquely assignable** and **safely evaluable** be. * Redundancy must be provided for safety-relevant sensors (e.g. door contacts). #### Actuators * Actuators must be switchable digitally and, if applicable, provide feedback. * Movements must be clearly completed or securable via interlock. #### Safety interfaces * Emergency stop, main air, door contacts etc. must be **CMZ** representable. * Faulty states must **completely lead to an automatic stop** lead. *** ### 3. Structural specifications #### Machine structure according to Selmo ``` PLANT └── Hardware zones (HWZ) └── Sequences (SEQ) └── Zones (Input, Output, In-Out, Mem) ``` #### Requirements * Each subprocess must be modeled in at least one **Sequence** . * Each zone must serve exactly one purpose (sensor, actuator, logic). * Each zone receives behavior in the state (`0`, `S`, `i`) via bit control. * Zones must be documented unambiguously to IO, address, terminal. *** ### 4. Process and functional logic #### Modelability * Every step of the process must be formulable as a **state with defined function** . * There must be no hidden logic or jumps outside the model. #### Safety behavior * Interlocks (`i`) must be set when a condition **mandatorily** must be fulfilled. * CMZ signals must be **constantly** monitored. * MXIC must be present for each manual zone. #### Restart * System must be able to be returned to a definable start state. * Reset may only occur when all fault conditions have been eliminated. *** ### 5. Requirements for engineering and code #### Control system * PLC must support IEC-61131-3 (Structured Text preferred). * Project structure must be representable with GVL, POUs and standardized blocks. #### Code generation * There must be no manually created code sections outside the Selmo model. * Changes to the sequence must be traceably documented in the model. *** ### 6. Requirements for documentation and testing #### Documentation * Signal directory with Zone ↔ IO ↔ Address ↔ Terminal * Model structure with Plant / HWZ / SEQ / Zone * Parameter list, bit control, CMZ-, MXIC matrices * Change log: `Model_ChangeLog.csv` #### Validation * Each SEQ must be validated by a **test protocol** . * Error cases (Interlock, CMZ, MXIC) must be **specifically tested** . #### Verification * Structure must match requirements from CE documentation * Reset/restart behavior, operating modes and safety logic must be verifiable *** ### 7. Summary: Requirements for the release of a Selmo machine | Domain | Must be fulfilled | | ------------------ | ----------------------------------------------- | | Model structure | Fully mapped (Plant → HWZ → SEQ → Zone) | | Signal assignment | Documented, verifiable, unambiguous | | Safety logic | CMZ, MXIC, interlock modeled and tested | | Sequence control | State-driven, deterministic, testable | | Restart / reset | Safe, documented, traceable | | Documentation | Automatically generated from model, audit-proof | | CE demonstrability | Interfaces for risk analysis fully available | *** These requirements are mandatory for every project implemented with the Selmo system. They provide the basis for: * technical quality * formal verifiability * standards-compliant safety * audit-proof implementation 📌 Compliance is a prerequisite for project acceptance, CE approval and long-term maintainability. --- # 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-of-the-logic/requirements-for-the-realization-of-a-machine-with-selmo.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.