Selmo Behavior you can prove.DE
BEHAVIOR-DEFINED MACHINES

Make the behavior of your critical machines provable.

BlackBox is yesterday: with the Behavior Reference you define, verify and generate deterministic machine behavior — vendor-independent, before the code. Let's talk for 15–30 minutes about one of your lines.

BoschRed BullAndritz AGEU Machinery Regulation 2027
Request an intro callFree · 15–30 min · no obligation

Request an intro call

A few details — we'll prepare the call around your specific situation.

We use your details only to prepare.No sharing.

THE CHAIN

From intent to a provable result

Behavior is defined before code. The Behavior Reference is the leading object — code, HMI, documentation and data structure are derivations.

01 · Intent

Intent

What should the machine do? Requirement and context — the starting point.

02 · Reference

Behavior Reference

The intended behavior, defined and verified formally and vendor-independently.

03 · Realization

Code

Generated from the reference — not hand-invented, vendor-independent.

04 · Operation

Operation & Monitoring

Behavior runs provably and is monitored — across the whole lifecycle.

No step is skipped.Code, HMI, documentation and data structure are derived 1:1 from the same Behavior Reference.

THE MISSING OBJECT

BDM, BCE and the Behavior Reference

Three terms, one principle: make behavior explicit before it disappears into code.

BDM

Behavior-Defined Machine

A machine whose intended behavior is formally defined, verified and controlled — before code exists. WhiteBox instead of BlackBox. The target picture.

BCE

Behavior-Centric Engineering

The path there: intent → behavior → code → reality. The programmer no longer invents behavior, but realizes a verified definition.

BR

Behavior Reference

The authoritative, technology-independent object of behavior — the shared language of all disciplines. The missing technical object between intent and code.

SELMO METHOD & STUDIO

From method to result

PTF clarifies, the process model becomes the Behavior Reference — Selmo Studio and the Selmo standard translate it automatically.

PTF
Process · Technology · Function
Process model = BR
Logic + System Layer
Selmo Studio + Standard
verifies & generates

Code

PLC logic generated from the model via PLCOpen XML — vendor-independent, verified against the reference.

HMI

Operation and visualization: active state, expectation and deviations visible — from the model.

Documentation

Operating, diagnostic and behavior documentation, fully derived from the model and consistent.

Data structure

The object-centric data model (Plant → HardwareZone → Sequence → Zone) with clear naming and four data views.

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

WHY IT MATTERS

Provable behavior has measurable impact

OEE ↑ · TCO ↓
Less unplanned downtime, lower lifecycle cost.
Vendor-independent
Behavior stays, even when hardware and language change.
2027-ready
Conformity to EU Machinery Regulation 2023/1230 demonstrable.
Know-how secured
Behavior owned by the operator — not locked in one person.

Provable machine behavior runs today atBoschandRed Bull, withAndritz AGas an ecosystem partner.

See where value leaks on one of your lines.

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

Request an intro call