Evidence

What can be evidenced.
And what on request.

Eight applications · five with a baseline · 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 no improvement is stated — only what holds without comparison: scope, effort, duration. An improvement without a starting value is not a measurement but an impression.

No baseline, no number. No measurement note, no effect claim.
Why two cases are anonymous

A name belongs to the one who carries it

We name customers only with written consent. Six of the eight cases therefore carry their name. Two stand without one — at the customer's request, complete in substance.

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

Five cases with a baseline.
Three without.

Where a baseline is documented, the full grid stands and the effect may be named. Where none is documented, only figures that hold without a point of comparison are given.

With a baseline — full grid
01

Velox Werk GmbH

Building materials - cement-bonded particleboard · Retrofit of an automatic board cutting line

20 sequences · 254 steps · 330 zones · 236 PLC inputs · 172 outputs · 12 servo axes · 5 asynchronous motors. View case ↘
Maria Rojach, Austria

Retrofit of an automatic board cutting line

20sequences 254steps 330zones
Baseline

Existing line with Beckhoff control (TwinCAT 3), operator interface and ERP link. Faulty sensor behavior was not detectable in operation.

Result

Core software commissioned in five days. Actuators and sensors taken over from EPLAN, the process recorded on video and modeled. Monitoring exposed hidden sensor faults.

Context

A trade article reports 25% higher throughput for a line with identical figures, without naming the company. We do not state that number until the attribution is confirmed.

02

igm Robotersysteme AG

Welding automation · New robotic welding cell with virtual commissioning

11 sequences · 218 steps · 380 zones · 12 constantly monitored zones · 165 PLC inputs and outputs · 22,700 lines of code. View case ↘
Wiener Neudorf, Austria

Robotic welding cell with virtual commissioning

11sequences 218steps 380zones
Baseline

Usual commissioning time for a machine of this kind: three person-months.

Result

Two weeks to the finished process model, one week of virtual commissioning. One engineer modeled the machine without classic PLC experience.

Context

The three person-months are igm's experience figure, not a measured comparison on the same machine.

03

MAHLE Filtersysteme Austria GmbH

Automotive · Retrofit of an end-of-line test station for quality control

2 sequences · 192 steps · 196 zones · 6 constantly monitored zones · 90 PLC inputs and outputs · 249 parameters. View case ↘
St. Michael ob Bleiburg, Austria

Retrofit of an end-of-line test station for quality control

2sequences 192steps 196zones
Baseline

Outdated proprietary control mastered only by individual specialists. A necessary change could not be made because the people responsible were no longer available.

Result

A few weeks from analysis to commissioning. Migration to an open, standardized platform. Higher quality, lower complexity and shorter cycle times. A second test station followed.

Context

The shorter cycle times are not quantified in the source.

04

Austrian beverage manufacturer

Beverage industry · New juice blending and filling plant

5 sequences · 177 steps · 255 zones · 10 constantly monitored zones · 189 PLC inputs and outputs · 50 parameters. View case ↘
Austria · Name withheld at customer's request

New juice blending and filling plant

5sequences 177steps 255zones
Baseline

Manual process without continuous recording of recipe, parameters and cycle.

Result

Process model in two weeks, tested and commissioned virtually. The real plant was built afterwards to the tested specification. Recipe, parameters and cycle are traceable per batch.

Context

Traceability covers recipe, parameters and cycle, not the entire plant.

05

Cosma Engineering — Magna

Automotive supply, tool making · New machine controlling two intelligent press tools

3 sequences · 41 steps · 206 zones · 113 PLC inputs and outputs · 9,248 lines of code. View case ↘
Weikersdorf, Austria

New machine controlling two intelligent press tools

3sequences 41steps 206zones
Baseline

High-strength sheet in difficult grades caused elevated scrap rates.

Result

Less scrap, higher forming accuracy and better quality. 250 ms process accuracy at high speed, without special code.

Context

The scrap reduction is not quantified. Electrical design and installation came from Duatec Automation GmbH, so the effect cannot be attributed to the method alone.

06

AZO Group

Plant engineering, raw material handling and bulk solids · Modernization of an existing plant

213 zones View case ↘
Plant engineering

Modernization of an existing plant

213 zones <80 hengineering
Baseline

No documented baseline.

Result

Under 80 hours of engineering effort for the complete modernization. The process was visible and verifiable before commissioning.

Context

No further figures are available. No improvement is claimed without a documented baseline.

07

thyssenkrupp Automotive Technology

Automotive · Proof of concept, full automation of a camshaft assembly line

7 sequences · 187 steps · 236 zones. View case ↘
Automotive · Proof of concept

Full automation of a camshaft assembly line

7sequences 187steps 236zones
Baseline

No documented baseline.

Result

Under two weeks from the first workshop to live commissioning. The behavior was known before the start of production.

Context

A proof of concept evidences feasibility, not series operation.

08

Firmware test machine

Test equipment · New machine

2 days commissioning View case ↘
Name withheld at customer's request

Firmware test machine

2 dayscommissioning 6 yearsoperation
Baseline

No documented baseline.

Result

Commissioned in two days. Six years of operation without retraining and without a service call.

Context

The six years are an operating period, not a comparison with another solution.

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 to −80 %commissioning time
−40 to −70 %unplanned downtime
+3 to +10 %OEE
−25 to −50 %maintenance
+5 to +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

All eight applications stand here — including the three without a documented baseline. They stand without an improvement claim 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.