It holds for the section that was checked and for the moment it was checked. In a company with several plants a second limit is added: even where checking happened, passed evidence in plant A does not mean the same as in plant B — as long as both check against different notions.
Without a shared reference architecture, maturity levels are not comparable across plants, reuse stays a matter of chance, and every statement about the company is a sum of statements that do not measure the same thing.
WhiteBox does not mean you can see the code. WhiteBox means conformity becomes decidable instead of a matter of judgment.With it, the work on behavior gets the order electrical engineering has had for a century: planning produces the document, execution implements it, commissioning checks against it.
Today one person does both at once — planning and executing — and carries both alone. That is not a question of missing qualification but of missing division of work.The order is not new — it is taken from another trade where it has worked for more than a hundred years. What is new is only that behavior has a plan at all for it to apply to.
Produces the Behavior Reference (BR) as a normative document. In electrical engineering that is the design office producing the circuit diagram. This role decides about behavior, it does not implement it.
Code, HMI, documentation and data structure are derived from the reference; hardware and interfaces are added. Craft that stays craft — with the difference that a plan exists to check it against.
What is checked against experience today is checked against the reference. A deviation then is a named deviation — not an observation someone has to classify.
Electrical design, cabinet building, mechanics. Nothing changes here, and that is a statement about the size of the change: it affects one trade, not all of them.
A transformation that depends on us would not be one. The result is an order your company carries itself — with named roles and people able to fill them.
A shared structure for the Behavior Reference (BR) across plants — so the same statement means the same everywhere.
Who plans, who executes, who checks. With interfaces, release paths and the question of who may change a reference.
Which unit modules occur repeatedly and can be modeled once — the actual leverage across several plants.
L0 to L5 per site and section, surveyed on a shared basis and therefore comparable.
Which people should fill which role and which qualification is missing for it — delivered through Certification & Training.
A gate is a decision, not a date. At company level one more is added: whether the standard from the first plant is transferable or has to be changed first.
Maturity per site on a shared basis, reuse potential, today's picture of roles.
Gate 0
Shared structure, release paths, responsibilities. In writing, before the first plant starts.
—
From the reference to checked behavior on a real line — the proof that the order holds.
Verification Gate
Further plants to the same standard, with feedback into the reference architecture.
Validation Gate
An offer does not become stronger by covering everything. It becomes stronger when its edge is known.
Reference architecture, role model, release paths, reuse catalogue, maturity picture across plants.
We accompany the first complete run. At the second we are observers, at the third a point of contact.
Regulation (EU) 2023/1230 applies from January 2027, with raised requirements for systems with self-evolving behavior. A normative behavior reference provides the material for the evidence — the conformity assessment remains the machine manufacturer's responsibility.
Creating the individual Behavior Reference (BR) per line is the PTF- & Behavior-Reference-Pilot or the Behavior Defined Machine (BDM) Engineering Project.
We name roles at the object. How your company staffs them is your decision.
Training the named people is part of Certification & Training.
Behavioral integrity after handover belongs to Lifecycle Services.
The order is the path, not the revenue. Enterprise Transformation is the fifth step and presupposes at least one completed run. A standard that has never held on a real line is a declaration of intent. The Behavior Reference (BR) is not after-the-fact documentation of the code. It exists before the code — at company level that means the architecture exists before the rollout, not during it. Verification asks: was it built right? Validation asks: was the right thing built? Across several plants a third question is added: does the same answer mean the same thing everywhere.
Target picture, use case and roadmap.
Where conformity is decidable today and where behavior has no reference.
One released Behavior Reference (BR) for a bounded unit module.
Implementation derived from the Behavior Reference (BR) and verified against it.
Behavior-Centric Engineering (BCE) as the standard across several plants.
Behavioral integrity across the lifecycle, changes as change verification.
Enabling the team, Selmo-owned qualifications.
A shared architecture makes statements comparable. It does not make a line better that was not built to it — existing plant stays existing plant until it is converted.
The question every transformation starts from
15–30 minutes. We bring the answer, not the presentation.