Check first.
Then talk.
Why these documents exist
The question no document can answer for you.
Against which document do you check today whether your machine behaves correctly? That question can only be answered on your line, not in a whitepaper. What these documents do: they hand you the criteria for it — and a yardstick to hold your own answer against.
A passed acceptance test is a snapshot of a sample: it holds for the section that was checked and for the moment it was checked. What was never observed has not been tested — it simply did not come up.
Four documents, a self-check, a study.
Each with a result, not with a message.
Two of them are self-checks: you enter something and receive a rating you keep even if you never speak to us. Two are briefings for decision-makers. Plus the self-check with 30 questions and the study, in which we take a look on site at your line.
The BlackBox Self-Check
Twelve statements, four dimensions. The result is a maturity level between L0 and L5 — a rating, not a recommendation. Five pages.
The Behavior Defined Machine (BDM) Playbook
For decision-makers: what changes when behavior gets an engineering object of its own — and how you notice that there is none. Six pages.
The Legacy Machine Rescue Check
For existing lines: where behavioral knowledge sits today, what of it is transferable and what disappears with the next change of staff. Five pages.
AI and the new Machinery Regulation
A briefing on Regulation (EU) 2023/1230, applicable from January 2027 — and on why AI accelerates translating and not checking. Five pages.
The self-check with 30 questions
Five properties of a WhiteBox: defined, decidable, diagnosable, changeable under control, transferable. About ten minutes; the short evaluation appears right away — we go through the full evaluation in the intro call.
The machine behavior study
We are looking at 100 lines. Strategy Workshop or WhiteBox Assessment on site — your result belongs to you; anonymized, it flows into the study.
Alongside these, the existing whitepapers and checklists remain available — Digital Transformation, Smart Manufacturing, the Selmo Method brochure, the comparison, the Machinery Regulation whitepaper and the six-point checklist.
What a cockpit shows
when behavior is defined.
Two interactive examples with simulated data — and how a specification becomes a Behavior Defined Machine (BDM). What is detected is the deviation from the defined behavior; what is not modeled is not covered.
OEE Cockpit · Example 1
Loss overview: where does the time go? Availability, performance, bottleneck and waiting time — with a measured reason for every loss source.
OEE Cockpit · Example 2
Pareto 80/20: which few positions explain most of the loss? Every position in plain language from the Behavior Reference (BR).
From specification to Behavior Defined Machine (BDM)
The V-model stays. What is new: the Behavior Reference (BR) as a checkable object and derivation with Selmo Studio — all the way to the cockpit in operation.
AI accelerates translating.
Not checking.
This is not a warning about the technology. It is a statement about which part of engineering gets faster — and which does not.
AI produces software today in hours instead of weeks. The evidence that this software realizes the defined behavior still depends on observation — and observation does not scale with computing power but with real time on a real line.
Without a normative behavior reference, AI does not accelerate your engineering; it accelerates the production of unverified translations.
If you want to go deeper,
start here.
Four pages carry the complete argument — read in this order: why, what, how. The knowledge base answers the questions in between. Verification asks: was it built right? Validation asks: was the right thing built? Whoever knows that distinction reads everything else faster.
The terms — why and what
Why everything has a plan except behavior — and what changes that: Behavior Reference (BR), Behavior-Centric Engineering (BCE) and Behavior Defined Machine (BDM) — precisely, in the order of the argument. The Behavior Reference (BR) is not after-the-fact documentation of the code. It exists before the code.
The path — how
From the BlackBox via the WhiteBox to the Behavior Defined Machine (BDM), in six maturity levels and four steps.
The method in detail
How behavior becomes something you can check: the derivation, the four gates and the distinction between verification and validation.
Services and products
Seven services, one product core — and the rule which reference comes before which tool.
The knowledge base
Answers to the questions before the decision, and guides for working with Selmo Studio.
WhiteBox does not mean you can see the code. WhiteBox means conformity becomes decidable instead of a matter of judgment. That is the difference all four documents are about.
When we name numbers,
we also name where they come from.
The causal chain holds without a number: less interpretation → less uncertainty → less searching → shorter engineering, commissioning and diagnosis cycles. The magnitude of the effect does not hold in general.
Ranges from delivered customer projects. The actual value is project-specific and is measured in the assessment on your machine.
You will find these ranges again in our documents — everywhere at the same magnitude and with the same footnote. If you ever come across a second range for the same quantity, that is a mistake, and we will gladly correct it.
What comes into being
between the documents.
A document appears rarely and wants to be complete. Articles and announcements come continuously. That is why they stand apart here — and not as a fifth tile among the four documents.
Articles
Articles, checklists and white papers on proof and verification, on the engineering method, on the Machinery Regulation 2027 and on AI in automation. Sorted by topic, one topic per post.
News
Releases, trade fairs, awards and partnerships. Kept short — what stands here is an announcement, not an argument.
A post explains a structure. Whether it holds on your line is shown by measurement — in the assessment, with a stated baseline.
Decidability requires technology. Where no reaction is detectable, nothing can be decided formally either — the method makes that visible, it does not remove it.
After reading
Which of these questions can you answer today, on your line?
Go through the open ones together15–30 minutes. No offer, no presentation — just your line and the questions that stayed open.