Evidence

What can be evidenced.
And what on request.

Eight applications · baseline per case · open assumptions stated

Evidence is what someone can verify without asking us. Everything else we call an assumption — and write it down as one.

01 — How this is measured

Before the first case:
what to measure it 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. 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.

What every case states

Six entries, always the same

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.
Why many cases are anonymous

A name belongs to the one who carries it

We name customers only with written consent. Until it exists, the case stands here with industry and project type — complete in substance, without the name. That is not hiding, it is the rule we set ourselves.

A logo without consent is not evidence, it is a claim about a third party.
02 — The applications

Eight cases,
the same grid.

The videos for individual cases are published together with the name — a video shows the hall and the line and cannot be anonymized.

Metallverarbeitung — Stabilität in wenigen Tagen

Scope of the modelto be added
Baseline before the projectto be added
Resultto be added
Open assumptionsto be added
Consent pending — anonymous

Robotersysteme — Kompetenz skalierbar gemacht

Scope of the modelto be added
Baseline before the projectto be added
Resultto be added
Open assumptionsto be added
Consent pending — anonymous

Automotive-Zulieferung — Verbesserte Qualität und einfachere Handhabung

Scope of the modelto be added
Baseline before the projectto be added
Resultto be added
Open assumptionsto be added
Consent pending — anonymous

Anlagenbau, Schüttgut — Retrofit mit voller Entscheidbarkeit

Scope of the modelto be added
Baseline before the projectto be added
Resultto be added
Open assumptionsto be added
Consent pending — anonymous

Automotive — Von der Idee zur Produktion

Scope of the modelto be added
Baseline before the projectto be added
Resultto be added
Open assumptionsto be added
Consent pending — anonymous

Getränkeabfüllung — Rückverfolgbarkeit jeder Charge

Scope of the modelto be added
Baseline before the projectto be added
Resultto be added
Open assumptionsto be added
Already anonymous

Automotive, Umformtechnik — Präzision bei hoher Taktzahl

Scope of the modelto be added
Baseline before the projectto be added
Resultto be added
Open assumptionsto be added
Consent pending — anonymous

Prüftechnik — Klein im Aufwand, groß im Ergebnis

Scope of the modelto be added
Baseline before the projectto be added
Resultto be added
Open assumptionsto be added
Consent pending — anonymous
03 — What can be generalized

Ranges from completed projects,
kept apart from the individual cases.

These values do not come from a single case but from several completed projects. They are project-specific and therefore carry a condition.

−50 bis −80 %commissioning time
−40 bis −70 %unplanned downtime
+3 bis +10 %OEE
−25 bis −50 %maintenance
+5 bis +20 %output

Ranges from completed customer projects. The actual value is project-specific and is measured on your line during the assessment.

04 — What is not claimed here

No case evidences an effect
on a different line.

That is not caution, it is the statement itself: structure transfers, effect is measured.

No transfer of numbers

What was measured on one line holds for that line. On yours it is measured anew — in the assessment, with a stated baseline.

No selection of the best cases

These are the applications for which the grid could be filled in completely. Cases without a baseline stand without a number instead of disappearing.

No statement about your industry

The industry of a case says where it happened — not that it would yield the same elsewhere.

The Behavior Reference (BR) is not after-the-fact documentation of the code

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.

What the method does not do

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

What would we have to show you for you to believe us?

Ask this question

15–30 minutes. We bring the answer, not the presentation.