THE MISSING TECHNICAL OBJECT
BDM, BCE and the Behavior Reference — clearly explained.
Three terms, one principle: make behavior explicit before it disappears into code. This page makes them clear in a few minutes.
Three terms, one principle: make behavior explicit before it disappears into code. This page makes them clear in a few minutes.
BCE (the approach) produces a Behavior Reference (the artifact) so the machine becomes a Behavior-Defined Machine (the result).
Concept terms stay in English — abbreviations after first spelled-out use.
A machine whose intended behavior is formally defined, verified and controlled — before code exists, independent of vendor and personnel.
The way of working that defines behavior explicitly before implementation: intent → behavior → code → reality. The programmer no longer invents behavior — they realize a verified definition.
The authoritative, technology-independent representation of intended behavior — the shared language of all disciplines. No syntax, no compiler. In the Selmo method the process model is the BR.
The Behavior Reference is the leading object — everything refers to it or is derived from it.
No step is skipped. Code, HMI, documentation and data structure are derived 1:1 from the same BR.
PTF clarifies, the process model becomes the Behavior Reference — Selmo Studio & standard generate four results from it.
PLC logic via PLCOpen XML, vendor-independent, verified against the BR.
Operation & visualization: states and deviations visible.
Operating, diagnostic & behavior docs derived from the model.
Object-centric data model, clearly named, four data views.
One source, four results — consistent, derivable and provable.
From L3 the behavior model becomes the WhiteBox — L4–L5 is the Behavior-Defined Machine.
To avoid misunderstandings.
15–30 minutes, concretely on one of your machines. Free and without obligation.
Request an intro call