This is not a mission statement for the wall. It is the task from which every decision of this company follows: which service we offer, which we do not, and which sentence is allowed onto a page.
We give behavior what electrical engineering has long had in the circuit diagram and process engineering in the P&ID: an artifact with normative authority over implementation and runtime. The Behavior Reference (BR) is not after-the-fact documentation of the code. It exists before the code.
Without a reference, “verified” is an opinion.An industry in which the question “does the real behavior match the reference?” is answered like a measurement and not like an assessment. The turning point is not visibility but decidability.
WhiteBox does not mean you can see the code. WhiteBox means conformity becomes decidable instead of a matter of judgment.Every statement carries its class openly: definition, structural statement or effect statement. Effect statements carry a condition and a note on measurement. Where something is not decidable, we say so — even when it does not help our case at that moment.
Behavior you can prove.Competence does not show in the number of projects but in what a statement can fail against. So what follows is how the method came about and what about it can be checked.
Selmo Technology was founded in 2019; the idea of leading machine behavior through a process model instead of through code goes back to 1998. It comes from commissioning — from the nights in which it turns out that two parties understood the same behavior differently, and no one has a document that decides.
The method was not published as a concept and tried out afterwards, but the other way round: developed on real lines, corrected there, and only then described as a standard. What could not be checked against a reference did not become part of the method.
The Selmo Standard is an open set of rules, PLCOpen XML the exchange format. The Behavior Reference (BR) stays in the operator’s ownership and is transferable as an object — including to someone not called Selmo. A method you can only apply with us would not be a method but a dependency.
They are not here because they sound good. They are in our language rulebook, and every text that leaves this house is checked against them. Where you find a breach, that is a mistake of ours — not small print.
An effect statement holds project-specifically. It always carries a condition and a note on measurement, never the tone of a definition. Where we name ranges, they come from delivered projects and are re-measured in the assessment on your machine.
Every longer text states what the method does not do. A text without a limit reads like advertising, and advertising is not evidence.
We do not criticize manufacturers, tools, people or previous ways of working. The BlackBox is a missing object, not a missing capability. Whoever attacks their audience has already lost the argument.
We name references on request and only with written consent. Until then it reads: in use on demanding lines in automotive and beverage filling. A logo in a band is not evidence but a claim about third parties.
Regulation (EU) 2023/1230 applies from January 2027, with raised requirements for systems with self-evolving behavior. A normative behavior reference provides the material for the evidence — the conformity assessment remains the machine manufacturer’s responsibility.
Verification asks: was it built right? Validation asks: was the right thing built? Derivation is not generation. WhiteBox is not transparency. These distinctions are the method — not its vocabulary.
An offer does not become stronger by covering everything. It becomes stronger when its edge is known.
WhySelmo Studio is a license, not an entry point. Without a clarified PTF (Process · Technology · Function) and a released Behavior Reference (BR) it only models into the approximate faster.
WhySelmo qualifications are vendor-issued credentials of Selmo Technology GmbH. They evidence the ability to apply the method — they are not an accredited certification under ISO/IEC 17024.
WhyWe deliver the object and the evidence against that object. Whether the intended behavior is the right one is your decision — that is exactly what validation is for, and it stays with you.
WhyBehavioral knowledge is not outsourced, it is made transferable. Whoever knows the line is still needed — just no longer as the only source.
Selmo delivers in named roles: Behavior Model Engineer, Selmo Studio Engineer, Behavior Defined Machine (BDM) Auditor — a Selmo qualification, not an accredited certification. Each role is tied to a qualification, each qualification to a passed examination. Whoever stands in your project has passed it — and the state of validity is kept traceably.
See the qualificationsEvidence is what someone can check without asking us. Everything else we call an assumption.
We name references and partners on request and with the consent of those named.
The Behavior Reference (BR) can only be as good as the intent and the PTF (Process · Technology · Function) it comes from. An unclear intent does not become clear through modeling.
The question we like most
15–30 minutes. We bring the answer, not the presentation.