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
Unstructured code growth
Programs grow historically β often without clear separation of logic, engineering and operation
Hardly traceable for third parties
Lack of transparency
Why is something not running? β hard to find out
State logic and signal behavior often hidden deep in the code
Time-consuming troubleshooting
No direct link between fault cause and HMI message
Fault diagnosis usually must be programmed manually
Unclear operator guidance
Operators do not see what is expected or what is missing
Manual operation often set up insecurely or illogically
Lack of reusability
Code is too individual, hard to standardize
No clear structure for copy-paste or modular processes
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
π 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?

