Advantages & benefits

1.4 Advantages of Selmo

βœ… Structured modeling β†’ No loose code snippets, but consistent logic

βœ… Automated documentation β†’ Signal directory, safety logic, process flow, parameters, HMI

βœ… CE-compliant and verifiable β†’ Restart behavior, reset conditions, fault reactions documented

βœ… Modular structure β†’ Each station/function as its own SEQ β†’ reusable, maintainable

βœ… Safe operation β†’ Only allowed actions visible, diagnostics automatic, HMI guided

🎯 Core benefit of Selmo summed up

  • πŸ” Clarity – What happens when, why, and what is missing

  • πŸ› οΈ Maintainability – All processes are modeled, not "programmed"

  • πŸš€ Commissioning becomes faster, because errors are visible earlier

  • 🧠 Knowledge is documented instead of hidden

  • πŸ” Standard instead of individual chaos

🚫 Problems of classic PLC programming

  1. Unstructured code growth

    • Programs grow historically – often without clear separation of logic, engineering and operation

    • Hardly traceable for third parties

  2. Lack of transparency

    • Why is something not running? β†’ hard to find out

    • State logic and signal behavior often hidden deep in the code

  3. Time-consuming troubleshooting

    • No direct link between fault cause and HMI message

    • Fault diagnosis usually must be programmed manually

  4. Unclear operator guidance

    • Operators do not see what is expected or what is missing

    • Manual operation often set up insecurely or illogically

  5. Lack of reusability

    • Code is too individual, hard to standardize

    • No clear structure for copy-paste or modular processes

  6. High training and documentation effort

    • New employees need a long time to find their way around

    • Documentation often incomplete or outdated


βœ… Advantages & direct benefits of Selmo – the solution

Problem
Solution with Selmo
Benefit

πŸ”„ Unstructured code

Model-based structure (Plant β†’ HW-Zone β†’ Sequence β†’ Zone)

Clear, clean structure instead of grown code blocks

πŸ•΅οΈβ€β™‚οΈ Lack of transparency

Bit control (S, i, 0) + HMI linking automatic

Operator immediately sees what the machine expects or what is blocking

🧯 Time-consuming troubleshooting

Automatic diagnosis from model state

No manual fault logic needed – faults are located and explained

❓ Unclear operation

Sequence Check + MXIC + Zone status in the HMI

Operator is guided – always knows what is allowed and what is missing

🧩 No reusability

Standardized zone structure (One zone = one function)

Modules can be duplicated, parameterized, maintained

πŸ“š High training effort

Visual process model + readable logic

Everyone sees at a glance what is happening – no more "black box"

❌ Missing safety concept

Integrated interlocks, CMZ, MXIC

Safety is part of the model – no additional code, no logic gaps

βš™οΈ Different manual/auto logic

Unified model for both

Same behavior in manual & automatic – traceable and safe


Last updated

Was this helpful?