Is Business Central enough as a MES, or do I still need a separate system?

For most discrete manufacturers between 80 and 300 employees with 1–3 plants, Business Central plus dvproduction covers the MES functions that matter: order release, dispatch, shop-floor data collection, traceability and production reporting. A standalone MES becomes necessary when you operate in heavily regulated industries (FDA 21 CFR Part 11, aerospace AS9100 with deep electronic batch records), or when you run more than 5 plants with diverging local processes. Below that threshold, a separate MES usually creates more integration debt than value.

How does dvproduction capture real OEE from the shop floor?

dvproduction installs shop-floor terminals (touchscreens, ruggedized tablets, or PLC/IoT gateways) that record machine start/stop, micro-stops, downtime reasons, scrap counts and operator IDs in real time. Availability, performance and quality are calculated automatically per work center and shift. OEE dashboards refresh continuously inside Business Central, with drill-down to the specific work order, operation and downtime code. No spreadsheets, no end-of-shift reconciliation.

Can dvproduction handle make-to-order, make-to-stock and engineer-to-order in the same instance?

Yes. dvproduction supports mixed-mode manufacturing in a single Business Central tenant. Make-to-stock items use MRP with reorder policies; make-to-order items trigger production from sales orders with project-level visibility; engineer-to-order flows attach BOM and routing variants to specific customer projects. The planning board shows all three flows together, which is the common reality of mid-sized industrial manufacturers.

How long does a typical implementation take?

For a single-plant discrete manufacturer with 80–150 employees, the Business Central + dvproduction implementation lands between 5 and 8 months end-to-end: 2 months of analysis and master-data cleanup, 2–3 months of configuration and integration (MES terminals, CAD/PDM connectors, label printers), 1 month of parallel run, and a month of stabilization. Multi-plant rollouts add 2–4 months per additional site after the template is stable.

Does the maintenance module (dvgmao) actually integrate with production, or is it a separate silo?

dvgmao shares the same Business Central database as dvproduction, which means a machine breakdown on the shop floor automatically creates a corrective work order in maintenance, blocks the affected work center in the planning board, and updates MTBF/MTTR statistics. Preventive maintenance windows are visible to production planners so they can schedule around them. It is not a federated integration; it is the same data model.

What about quality control and non-conformance tracking?

dvquality adds inspection plans, sampling rules (AQL tables), non-conformance reports and CAPA workflows on top of Business Central. Inspections can be triggered at goods receipt, in-process at routing operations, or at finished-goods release. Failed batches are quarantined automatically and trigger traceability reports — by lot, by raw material supplier or by production order — usable in under a minute, which is what auditors actually test.

Volver a dvproduction Volver a dvgmao Volver a dvquality

Microsoft Business Central

Manufacturing Operations Management in Business Central

How Business Central + dvproduction covers MOM (ISA-95 level 3) for discrete SMB manufacturers without a separate MES. Real scope, real limits.

7 min

Manufacturing Operations Management on Microsoft Dynamics 365 Business Central with dvproduction

Manufacturing Operations Management on Microsoft Dynamics 365 Business Central, deployed by Davisa — Microsoft Solutions Partner for Business Central since 2003

If you run a discrete manufacturing plant between 80 and 300 employees, you have probably been pitched a standalone MES at least three times. The pitch is always the same: ERP cannot run the shop floor, you need a dedicated execution layer. That was true in 2005. It is no longer true in 2026 for most SMB manufacturers, and the integration debt of a separate MES is now bigger than the gap it closes.

This article explains, in concrete terms, what Manufacturing Operations Management (MOM) means at ISA-95 level 3, what Business Central plus dvproduction covers natively, and where you genuinely still need a dedicated MES.

REQUEST A TECHNICAL DEMO

What MOM means in practice

MOM is the layer between business planning (ISA-95 level 4, the ERP) and the physical process control (level 2, PLCs and SCADA). Level 3 — operations management — covers four function groups defined by the standard:

Production operations management: order release, dispatching, execution tracking, production reporting.
Quality operations management: inspection planning, sampling, non-conformance, CAPA.
Maintenance operations management: preventive scheduling, corrective work orders, asset history.
Inventory operations management: WIP tracking, internal logistics, lot/serial traceability.

A MES is the historical software category that automated some of these — primarily production execution and data collection. MOM is the broader umbrella that recognizes none of these functions actually live in isolation: maintenance affects production capacity, quality affects inventory availability, and all of them feed cost accounting back at level 4.

This is exactly the boundary where a single integrated platform beats best-of-breed.

Why standalone MES fails for SMB

Three reasons, in order of how often we see them at Davisa client sites before migration:

Cost structure. Tier-1 MES vendors price per work center, per named user and per module. A 4-line plant with 60 shop-floor users routinely lands at €180k–€350k in licenses over 5 years, before integration. For an SMB doing €30–80M in revenue, that is a disproportionate slice of IT budget for a function that overlaps 70% with what the ERP already does.

Integration debt. Every MES-ERP interface is a moving target: BOM changes, production confirmations, scrap, lot genealogy — all must stay in sync. We have audited customers running 14 interface jobs between SAP and a Tier-1 MES, with a full-time integration engineer just to keep them alive. That cost never appears in the original business case.

Double entry and master-data divergence. When master data lives in two systems with different ownership, it diverges. Routings get updated in MES but not in ERP. Standard costs drift. Operators trust the MES screen and ignore the ERP — which is the same as saying your cost accounting is wrong.

BC + dvproduction native MOM coverage

dvproduction is a Davisa extension built on top of Business Central manufacturing. It is not a separate database, not a federated MES — it extends the standard tables and pages to cover ISA-95 level 3 inside the ERP.

Order management. Production orders inherit from sales orders, forecasts or manual entry. Planning board shows a Gantt with finite-capacity scheduling per work center, with drag-and-drop rescheduling and constraint highlighting.

Execution and dispatch. Work orders are released to shop-floor terminals by work center. Operators see only their queue, in priority order. Setup, run, scrap and downtime are recorded by reason code with a single touch.

Data collection. Terminals integrate with PLCs via OPC-UA gateways, with barcode/RFID scanners for material consumption, and with weight stations for batch dosing. Manual entry is the fallback, not the primary path.

Quality. Inline checks at routing operations halt the work order on out-of-spec results. Non-conformances generate full traceability trees automatically.

Maintenance. Breakdowns recorded on the terminal create maintenance work orders and block the work center in the production planning board within seconds.

Traceability. Forward and backward genealogy by lot, batch or serial number — supplier → raw material → WIP → finished good → customer shipment — in a single query, with a printable audit trail for regulators.

See dvproduction technical sheet

Integration with maintenance (dvgmao) and quality (dvquality)

The argument for an integrated MOM is not that any single module is “better” than its best-of-breed competitor. It is that the seams disappear.

A real example: a finished-good batch fails QC. With dvquality + dvproduction + dvgmao on the same Business Central:

The QC inspector marks the batch as non-conforming in dvquality.
dvquality traces the batch backward through the routing and identifies the work center and operator at the suspect operation.
dvgmao history reveals that work center had three micro-stops on the relevant shift, all on the same axis.
A preventive maintenance work order is scheduled before the next production run.
dvproduction reassigns the pending orders to an alternative work center while the maintenance is performed.

All of this happens in the same database, in the same UI, with the same master data. No interface, no batch sync, no reconciliation report.

Explore dvgmao for maintenance management

Real OEE / MTBF / MTTR capture from shop floor

OEE is the metric most often promised and least often delivered, because capturing it accurately requires reliable, real-time data — not end-of-shift forms filled in by tired operators.

dvproduction captures the three OEE components from the physical sources:

Availability: machine signals via OPC-UA (run/stop/fault states) timestamped to the second, with downtime reasons selected by the operator on the terminal when a stop exceeds the configurable threshold (typically 5 minutes).
Performance: cycle counts from PLC tags or photocells, compared to the standard cycle in the routing.
Quality: scrap and rework counts entered at the terminal by reason code, with optional automatic capture from inline vision systems.

MTBF and MTTR feed automatically from dvgmao corrective work order data: time between consecutive breakdowns and time to restore are calculated per asset, per line and per plant. The KPIs that boards actually ask for — first-pass yield, schedule adherence, throughput per shift — are dashboards in Business Central, not custom Power BI builds (though Power BI works too, on the same data).

When you still need a dedicated MES

We tell prospects honestly when BC + dvproduction is the wrong fit:

FDA-regulated pharma or medical device manufacturing with full 21 CFR Part 11 electronic batch records, e-signatures per process step, and validated computer system lifecycle requirements. The specialized MES vendors here (Werum PAS-X, Körber, Rockwell PharmaSuite) carry the validation package as part of the product.
More than 5 plants with significantly diverging processes, especially if regionally autonomous. A federated MES with a global template plus local extensions makes more sense than stretching a single BC tenant.
Heavy semiconductor or wafer fab environments, where the wafer-level tracking model differs structurally from discrete lot/serial.
High-frequency process manufacturing with sub-second control loops (specialty chemicals, continuous casting). Those workloads belong in DCS/MES territory, not ERP.

For the rest — typical discrete SMB manufacturing in industrial equipment, automotive tier-2, food and beverage (non-pharma), metal fabrication, plastics, packaging — BC + dvproduction is the right scope.

Implementation: typical roadmap for SMB manufacturer

A pragmatic 6-month plan for a single-plant 120-employee discrete manufacturer:

Month 1 — Discovery and master data. Item master cleanup, BOM and routing audit, work center capacity model.
Month 2 — Core configuration. Manufacturing setup, planning policies, costing methods, terminal layout.
Month 3 — Integration. PLC/OPC-UA gateways, label printers, scales, barcode infrastructure.
Month 4 — Pilot line. One line live in dvproduction with full data capture. Maintenance and quality connected on pilot scope.
Month 5 — Plant rollout. Remaining lines onboarded, KPI dashboards stabilized, parallel run with legacy.
Month 6 — Cutover and stabilization. Legacy decommissioned, support handover.

Davisa runs this roadmap end-to-end with a single team — same Microsoft Solutions Partner, same consultants, no subcontracting.

Next step

If you are evaluating whether to add a Tier-1 MES on top of your ERP, or whether to replace your ERP and MES with an integrated platform, talk to us before signing anything. The honest answer depends on your regulatory exposure, plant count and process complexity — and we have walked clients into both directions, including telling some they should stay on their existing MES.

REQUEST A TECHNICAL DEMO