BDM Engineering Project (EN)

FOR WHOM & WHY

The complete implementation

For whom

For engineering teams and project owners implementing a critical machine completely and standard-compliantly.

The problem

After the pilot the machine must be implemented for real and in full — without behavior drifting apart in the code. The project derives all artifacts from one Behavior Reference and accepts them standard-compliantly.

THE FLOW

Six phases — from BR to accepted machine

Each phase has a result gate. Changes go through the model, never directly in the code.

Phase 0

Project setup

Scope/modules (Plant › Sequence › Zone), target platform.

Gate: scope confirmed

Phase 1

Complete BR & freeze

Extend pilot BR to full scope; layers consistent.

Gate: BR freeze

Phase 2

Implementation (derivation)

Code, HMI, diagnostics, data structure & docs from the BR.

Gate: derivation complete

Phase 3

Verification

Check against acceptance logic (sequence check, interlock, monitoring).

Gate: test cases passed

Phase 4

(Virtual) commissioning

Align behavior on the target platform.

Gate: behavior stable

Phase 5

Acceptance & handover

Acceptance, all artifacts, open points, KPI proof.

Gate: accepted

SCOPE

What's included — and what's not

Included

Behavior Reference (complete, frozen)
Code (PLCOpen XML), HMI, diagnostics
Data structure & documentation
Test & acceptance logic
(virtual) commissioning

Not included

Company-wide standard rollout (Stage 5)
Ongoing operation / service (Stage 7)

DELIVERABLE ARCHITECTURE

Four results from one Behavior Reference

All artifacts stem from the same behavior logic. Normative order: PTF → process model (BR) → derivation.

Code

PLC logic via PLCOpen XML, verified against the BR.

HMI

Operation & visualization from the behavior logic.

Documentation

Operating, diagnostic & behavior docs from the model.

Data structure

Object-centric data model, clearly named.

The model has priority: changes are described in the BR and re-derived — never directly in the code.

YOUR RESULT

Acceptance & handover protocol

A formal protocol documents acceptance and the handover of all artifacts.

Project & acceptance overview
Deliverable acceptance
Test & acceptance results
Open points / defect list
KPI proof
Handover package
Next stage
Sign-offs

Accepted, standard-compliant

Code, HMI, diagnostics, data structure and documentation are derived from the BR and congruent. Acceptance is against the acceptance logic in a four-eyes review.

Confidential · for you only

Duration

project-dependent (weeks–months)

Prerequisite

Successful pilot with released BR

Next step

Enterprise Transformation / Lifecycle

Request an intro call

Delivered to aproven delivery standard(Selmo delivery playbook) based on the patented Selmo method. In use on demanding lines — including Bosch and Red Bull.