Shop Floor Data Collection (BDE)
Shop floor data collection (BDE) is the systematic capture of actual data from ongoing operations – above all order, machine and labour times as well as quantities, good parts and scrap counts. It supplies the feedback used to reconcile production orders, costing and capacity planning in the ERP with reality.
Shop floor data collection (BDE, from the German Betriebsdatenerfassung) refers to the systematic and, ideally, near-real-time capture of actual data from ongoing production and its feedback to the planning systems. What gets recorded is above all order data (which production order is running, at what progress), machine data (run, downtime and setup times, states), labour times (clock-in/clock-out, order times) as well as quantity and quality data such as good-part and scrap counts. BDE therefore answers the question of what actually happened on the shop floor – in contrast to planning, which prescribes what should happen.
The heart of BDE is the target-actual comparison: an ERP or production planning and control (PPC) system schedules production orders with standard times from the routing; BDE reports back how long the operations really took and how many parts they produced. Only this feedback closes the control loop of production: without actual data, progress, cost and utilisation remain guesswork. BDE is thus less a single tool than a data layer that connects real manufacturing with the commercial and planning view of the ERP.
At a glance
- Captures actual data from operations: times, quantities, downtime reasons, states
- Four classic data types: order, machine, labour and quality data
- Supplies the feedback for the target-actual comparison in the production order
- Basis for post-calculation, schedule tracking and capacity utilisation
- Link between the shop floor (machine/terminal) and the ERP/PPC system
What shop floor data collection (BDE) captures
Traditionally, BDE distinguishes four types of data. Order-related data documents the progress of a production order: start and end of an operation, good and scrap quantities produced, rework and material consumption. Machine data – often distinguished as machine data collection (MDE) – covers run times, stoppages with downtime reasons, setup operations, part counts and states read directly from the machine control. Labour data records attendance (clock-in/clock-out) and the times employees book against individual orders. Quality data, finally, captures inspection results, defect reasons and scrap causes.
Today, data capture is mostly digital: at BDE terminals on the shop floor, via barcode or RFID scan of the order ticket, through handhelds, tablets or directly from the machine control. The goal is to keep the recording effort for operators low and to avoid media breaks: ideally an employee logs on to an operation with a single scan and reports it complete with the quantity. The more automated the capture, the more complete and less error-prone the data.
BDE, MDE and PZE – the distinction
The terms overlap in practice. BDE is the umbrella term for capturing actual operational data. Machine data collection (MDE) is the subset that automatically reads states and counters directly from machines and plant – without any manual input. Personnel time recording (PZE) captures the attendance and working times of employees and at the same time serves as the basis for payroll and working-time accounts. Many systems combine all three, so that one terminal books the order, the machine and the labour time alike.
How shop floor data collection (BDE) works
The BDE data flow follows a control loop. The ERP or PPC system creates a production order with operations and standard times from the routing and makes these orders available to the BDE terminals. On the shop floor, the operator logs on to the operation, works it off and reports it complete with the good and scrap quantities achieved; in parallel, the machine supplies its run and downtime times. This feedback flows back into the ERP, where it updates the order status, sets the actual times against the standards and triggers stock movements (material withdrawal, completion posting).
BDE thus fulfils two functions at once: it is both a progress reporter and a data supplier. As a progress reporter it shows in near real time which order stands where – the basis for reliable schedule tracking and for information given to the customer. As a data supplier it feeds post-calculation (actual cost from actual times times the cost rate), capacity analysis (actual utilisation of work centres) and metrics such as overall equipment effectiveness (OEE), which combines the availability, performance and quality of a plant.
Why BDE matters: benefit and relevance
Without reliable actual data, production planning flies blind. Standard times from the routing are initially only assumptions; only the comparison with the reported actual times shows whether they hold. If they deviate systematically, costing and scheduling run permanently off – orders are quoted too cheaply or promised too late. BDE supplies the data basis to correct these standards and to improve planning quality step by step.
The second benefit is real-time transparency. Whoever can see at any time which orders are running, where bottlenecks arise and why machines stand still can intervene earlier, analyse downtime reasons systematically and reduce waste. This makes BDE a central building block of lean manufacturing and of the digital factory (Industry 4.0): it makes manufacturing measurable and creates the basis for continuous improvement. Not least, a well-integrated BDE relieves administration, because handwritten feedback slips and their later re-entry become unnecessary.
BDE in the ERP and MES context
In the system landscape, BDE sits between the shop floor and the ERP. Smaller ERP systems with a production module already come with a simple BDE for order and time feedback. More demanding manufacturers deploy a manufacturing execution system (MES), which contains BDE as one of its functions and additionally handles detailed scheduling, operator guidance, quality and material control in real time. In this constellation the ERP supplies the orders and master data, the MES controls and captures execution, and the condensed actual data flows back into the ERP.
Seamless integration is decisive: BDE data only unfolds its value when it flows without a media break into the production order, stock level and post-calculation. An isolated stand-alone solution whose data is transferred manually gives away exactly the timeliness that makes BDE valuable. That is why a clean connection – via standard interfaces or an API – is a central selection criterion.
DACH specific: BDE and personnel time recording
In the DACH region, BDE is closely intertwined with personnel time recording, which raises co-determination and data-protection questions. If personal performance and behavioural data is captured via BDE, its introduction in Germany regularly requires the co-determination of the works council (Section 87 (1) no. 6 BetrVG) and compliance with the GDPR. On top of this, since the working-time ruling of the ECJ (2019) and the German Federal Labour Court (BAG) decision of 2022, there is an obligation to record working time objectively – one reason why PZE and BDE are frequently introduced together.
Example
Example: mid-sized metalworking supplier
A supplier with around 40 employees produces turned parts in series. A BDE terminal stands at every machine. In the morning the operator scans their badge (labour time) and the barcode of the production order, logs on to the operation "turning" and begins. Via MDE, the CNC machine automatically supplies run time and part counter; on a stoppage the operator selects the downtime reason "tool change" at the terminal. At the end they report back 480 good parts and 12 scrap parts.
This data runs into the ERP: the production order is updated to 480 units, the finished-goods stock is posted, and the actual time of 6.2 hours stands against the standard of 5.5 hours. The post-calculation reveals that the order was more expensive than costed – the cause being the frequent tool changes that the downtime-reason analysis makes visible. The company adjusts the standard time in the routing and plans a buffer for this part in future.
Frequently asked questions
Matching ERP systems
Related services
Sources
Questions about Shop Floor Data Collection (BDE) in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.