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. Anyone turning that into a number has to say where it came from. So every case carries the same grid — and where a figure is missing, it says so.
Industry · project type · scope of the model · baseline before the project · result afterwards · assumptions marked as open. Without a baseline the result stands without a number — an improvement without a starting value is not a measurement but an impression.
No baseline, no number. No measurement note, no effect claim.Structural figures — sequences, steps, zones — come from the Selmo project and can be counted there. Time and effect figures come from the project reports. Where the source has not been named yet, that is stated on the number itself, not in the small print.
A number without a named source stays marked rather than quietly counting.Every case comes with the material you need to check it: the recording of the line, the project documentation as a PDF and — where it exists — the technical recording from Selmo Studio. The companies named here have consented to being named.
Retrofit of an automatic panel cutting line. The process was recorded from video and the wiring plan and modelled in full before anyone touched the control. Control: TwinCAT 3.
Robot welding cell, a new installation and the customer's first Selmo project. Modelled by one engineer with no conventional PLC background.
Test station (end-of-line tester) for quality control, retrofit of an existing line. Preparation: analysis of the current state and process capture.
Modernisation of an existing raw-material handling plant. The process was captured on site, modelled in Selmo Studio and virtually commissioned against the digital twin of the 3D model. Hardware: Beckhoff.
Full automation of a camshaft assembly line as a proof of concept. Two weeks of preparation, three days on site.
Digitalisation of a juice mixing plant, new installation. The starting point was a manual process with BlackBox risk; the behaviour was modelled as WhiteBox logic. The customer stays unnamed at their own request.
Intelligent press-tool control in the R&D phase. An extremely dynamic process, structured entirely in Selmo.
Test rig, the first live use of Selmo Studio. Starting point: the system could not be put into operation. Hardware and process were defined exactly.
These values do not come from a single case but from several completed projects. They are project-specific and therefore carry a condition.
Ranges from completed customer projects. The actual value is project-specific and is measured on your line during the assessment.
That is not caution, it is the statement itself: structure transfers, effect is measured.
What was measured on one line holds for that line. On yours it is measured anew — in the assessment, with a stated baseline.
These are all the applications for which material exists — including the ones where the grid has gaps. Where a figure is missing, it says so on the tile instead of the case disappearing.
The industry of a case says where it happened — not that it would yield the same elsewhere.
It exists before the code. What these cases evidence is therefore the path, not a result explained in hindsight.
Verification asks: was it built right? Validation asks: was the right thing built? The cases above evidence the first question. The second was answered in each project by the operator. WhiteBox does not mean you can see the code. WhiteBox means conformity becomes decidable instead of a matter of judgment — and that is what a case here can evidence.
Selmo replaces neither commissioning nor experience — it reduces the space of possible causes. And what is checked is always the defined behavioral space: what is not modeled is not covered.
The question we like most
15–30 minutes. We bring the answer, not the presentation.