Services & Products

Seven services.
One path.

Orient · Establish the reference · Implement · Operate

The order on this page is the path, not the revenue. You can enter at any point — but not every point presupposes the same thing, and that is stated at the top of every service page.

01 — Why there is an order

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. That can be changed — but not in an arbitrary order. The Behavior Reference (BR) is not after-the-fact documentation of the code. It exists before the code. Which is why no implementation project can come before the reference and no reference before the intent.

What the order is not

Not a package sale

Nobody has to buy all seven services, and most plants do not. The order only says what builds on what — not what you should commission.

WhiteBox does not mean you can see the code. WhiteBox means conformity becomes decidable instead of a matter of judgment.
Where most people start

With a question, not with a project

The most common first step is not an order but a conversation about one specific line. After it, it is usually clear whether a workshop or an assessment is the right start.

Verification asks: was it built right? Validation asks: was the right thing built? The services differ mainly in which of the two questions they make answerable.
02 — The seven services

In the order of the path,
not of size.

Every service page states at the top what it presupposes and at the bottom what it explicitly does not contain. The edge is described just as carefully as the content.

03 — The four steps

Four steps,
seven services.

The services fall into four steps. The step says what is at stake right now — the service says how far you go with it.

OrientStrategy Workshop · WhiteBox Assessment — target picture, scope, and the finding of where conformity is decidable today.
Establish the referencePTF- & Behavior-Reference-Pilot — capture behavior and determine it bindingly as a Behavior Reference (BR).
ImplementBehavior Defined Machine (BDM) Engineering Project · Enterprise Transformation — derive, integrate, check against the reference.
Operate & enableLifecycle Services · Certification & Training — evidence across changes, qualification in house.
04 — The product core

Three products.
The method is none of them.

Selmo is a method. The products are what it is applied with — they do not replace the method and therefore do not belong in the same list.

Selmo Studio (licence)

The working environment in which the Behavior Reference (BR) comes into being and from which code, HMI, documentation and data structure are derived.

Selmo Standard

The structure by which behavior is determined — states, transitions, operating modes. It makes references readable across lines.

Selmo Activation Code

The activation of a line for the runtime reference — with it, the Behavior Reference (BR) is present on the machine at runtime.

Why this stays separate

A method that only works with its author would not be a method. Which is why the structure is described and the reference is readable in the exchange format.

What the method does not do

None of these services performs a conformity assessment. They provide the material for the evidence trail — the assessment remains with the machine builder.

The question before the first service

Which document do you check against to know whether the machine behaves correctly?

Discuss this question

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