BEHAVIOR-DEFINED MACHINES

Make your machines' behavior provable.

Today behavior sits invisibly in the code. Selmo makes it explicit, verifiable and your property — with method, Studio and standard. From the BlackBox to the WhiteBox.

up to −40 %Project time
up to −50 %Commissioning
up to −70 %Downtime
Request an intro callHow it works
Control is a decision. Behavior you can prove.
THE PROBLEM

Today, your machine is a BlackBox

As long as behavior lives only in code, it is neither verifiable nor transferable — and only becomes visible on failure.

Invisible

Behavior buried in code

Undocumented, scattered across PLC blocks. No one can show what the machine is actually meant to do.

Dependent

Person- & vendor-dependent

Knowledge sits with a few individuals and a single PLC partner. Every change becomes a risk.

Late

Only visible on failure

Deviations surface when it gets expensive — downtime, scrap, lost OEE.

THE SOLUTION

From BlackBox through WhiteBox to BDM

Six maturity levels describe the path. From L3 the behavior model becomes the WhiteBox — L4–L5 is the Behavior-Defined Machine.

See the full path →
L0
BlackBox
Behavior in code.
L1
Documented
not formal.
L2
Explicit states
made visible.
L3
Controllable
turning point WhiteBox.
L4
Lifecycle
integrity over time.
L5
Architecture
fully model-driven.
BlackBox → WhiteBox → BDM.
L0–L2 = BlackBox zone · L3 = turning point · L4–L5 = Behavior-Defined Machine. Selmo systems operate at L3–L5.
THE SYSTEM

One Behavior Reference — four results

PTF clarifies, the process model becomes the Behavior Reference — Selmo Studio & standard generate four results from it.

BDM · BCE · BR in detail →
PTF
Process · Technology · Function
→
Process model = BR
Logic + System Layer
→
Selmo Studio + Standard
verifies & generates

Code

PLC logic via PLCOpen XML, vendor-independent, verified against the BR.

HMI

Operation & visualization: states, expectation and deviations visible.

Documentation

Operating, diagnostic & behavior docs, fully derived from the model.

Data structure

Object-centric data model, clearly named, four data views.

One source, four results — consistent, derivable and provable.

VALUE & AUDIENCES

Provable behavior has measurable impact

Value levers for management, engineering, production, quality and maintenance.

OEE +3–10%
higher overall effectiveness
−50 to −80 %
faster programming & commissioning
−40 to −70 %
less unplanned downtime from fault-finding
−25 to −50 %
less time spent on maintenance
+5 to +20 %
more output through better cycle time
MR 2027
provably compliant
ManagementEngineeringOperations / OEEMaintenance / RetrofitCE / Compliance
SERVICES

Modular — you choose what your path to the BDM needs

One product core and services tuned to it. Each leads to a clear next step.

View all services →
Services

Strategy Workshop

Target picture, use case and roadmap for your path to the BDM.
Request a workshop →

WhiteBox Assessment

Capture a critical machine's behavior and verify it as a Behavior Reference.
Request assessment →

Engineering Maturity Assessment

Determine maturity (L0–L5) and potential across your machines.
Request assessment →

Behavior Engineering & Prototype

Build the Behavior Reference and realize it as a running prototype.
Intro call →

Rollout / Implementation

From reference to series: implementation, integration, accelerated commissioning.
Intro call →

Selmo Academy

Enable your team — apply method, Studio and standard confidently.
View Academy →

Support & Care

Secure and support behavioral integrity across the lifecycle.
View Support →
Product

Selmo Studio (License)

The model-based platform: model behavior, generate code/HMI/docs.
Trial / Demo →

Selmo Activation Code

Activation/license layer for the provable operation of generated behavior.
Intro call →
Request an intro call
THE PATH TO THE BDM

Step by step — as a retrofit

A clear, modular path from orientation to safe operation.

1

Orient

Clarify position and goal: where is value/risk?

Strategy Workshop · Maturity Assessment
2

Verify

Capture behavior and make it provable as a Behavior Reference.

WhiteBox Assessment · Process Model Pilot
3

Implement

Build the BR, generate code/HMI, prototype & roll out.

Engineering & Prototype · Rollout
4

Operate & Enable

Maintain integrity, enable the team, secure it.

Academy · Support & Care
Request an intro call
PROOF

Provable — patented and in use

Bosch · Red Bull
in use on demanding lines
Andritz AG
ecosystem partner
Patented
globally validated
Beckhoff · CODESYS · ctrlX · EPLAN · SAP · Andritz · Raitec · Steco
OEE +3–10%
measurable asset value
MR 2027
compliant & auditable
vendor-independent
no lock-in
WHY NOW

Market timing meets provable behavior

Regulation, AI pressure and aging plants make provable behavior a must.

2027

EU Machinery Regulation 2023/1230: AI can make machines high-risk — provable behavior secures conformity.

AI

AI in production needs a deterministic core. Selmo makes it trustworthy.

Retrofit

Aging controls (S5) and know-how loss — a huge brownfield market, addressable as a retrofit.

Know-how

Behavior sits in heads and in code — Selmo turns it into operator-owned, verifiable knowledge.

RESOURCES

To get started: guides & self-checks

Start low-friction — understand before you talk.

White Paper

MR 2027 compliant

Download
Checklist

Risk-mitigation checklist

Download
Standard

Selmo Automation Standard

Download
Brochure

The Selmo method

Download

Take the first step out of the BlackBox.

15–30 minutes, concretely on your most critical machine. Free and without obligation.

Request an intro call