When the plant never stops, every friction costs you margin

Demand and supply planning

The master schedule lives in a spreadsheet only one person knows how to maintain. Order changes never reach purchasing, and the shortage surfaces on the shop floor, when the only way out is expedited freight or a stopped line.

Bills of materials and routings

Bills of materials (BOM) and manufacturing routings are maintained outside the system and in different versions by department. Engineering changes a formula and production keeps working from the previous one.

Capacity and production orders

Scheduling is built on the plant manager’s judgment, with no real visibility of load by work center. Nobody knows which order is late until the customer complains about the delivery date.

Production costing

Standard cost is never updated, and actual cost per order is rebuilt by hand after the close. Variances from materials, labor, and downtime go unexplained, so they go uncorrected.

Quality, nonconformances, and traceability

Quality checks are recorded on paper, and nonconformances are not linked to the lot or to the supplier. When a complaint or a product recall hits, reconstructing the path of a lot takes days.

Warehouse and inventory

Raw material, work in process, and finished goods are counted in different systems. Inventory discrepancies surface during the physical count, and the adjustment is absorbed as a loss with no identified cause.

Operational analytics

Every department presents its own metrics with its own criteria, so the results meeting is spent arguing about where each figure came from instead of deciding what to do.

OT/IT integration and industrial security

Plant networks (OT, operational technology) and corporate networks (IT, information technology) grew separately, with unpatched equipment and shared credentials. One incident on a control device can stop production.

Executive leadership (CEO)

Sees the real status of the production plan, customer service levels, and margin by product line without waiting for the financial close. Capacity investment decisions rest on actual work center load, not on impressions.

Finance (CFO)

Gets actual cost per production order broken down into materials, labor, and overhead, and can explain variances against standard cost. Inventory valuation stops being an estimate, and the close rests on transactions rather than on manual reconciliations.

Operations and plant (COO)

Schedules with visibility of capacity and available materials, releases orders with supply confirmed, and follows progress by work center. Rework and nonconformances are recorded against the order and the lot that caused them.

Supply chain and purchasing

Buys against calculated requirements instead of intuition. Supplier agreements, lead times, and inventory minimums are configured once, and the system proposes the orders.

Quality

Records inspections, releases, and rejections tied to the lot, the supplier, and the production order, so a complaint can be traced backward and forward from the same record.

Information technology (IT)

Reduces the number of systems to maintain and manages identities, access, and backups inside the Microsoft cloud. Integrations with plant equipment run through documented interfaces instead of files someone copies every night.

1. 1

   Business layer (ERP): Dynamics 365 Business Central holds finance, purchasing, inventory, sales, manufacturing, and warehouse. It is the master record for items, bills of materials, routings, costs, and transactions.

2. 2

   Data and analytics layer: Power BI consolidates ERP data with data from other systems into a governed model, with single metric definitions and control over who sees what.

3. 3

   Collaboration and productivity layer: Microsoft 365, Teams, and SharePoint bring approvals, operating procedures, shifts, and checklists to the operator’s and the supervisor’s device.

4. 4

   Automation layer: Power Platform lets you build approval flows and shop floor capture apps without duplicating data or creating parallel systems.

5. 5

   Integration layer: documented interfaces to manufacturing execution systems (MES), plant control (SCADA), scales, barcode scanners, and lab equipment, with defined data contracts instead of manually copied files.

6. 6

   Security and governance layer: identity and conditional access in Microsoft Entra, information protection, and backup in the Microsoft cloud. For industrial networks we add specialized OT/IT protection with Kaspersky, with segmentation and policies designed to coexist with the Microsoft tools.

Case studies pending client authorization.

Is Business Central enough for a plant, or do I need a larger manufacturing solution?

Business Central covers bills of materials, routings, work centers, production orders, requirements planning, costing, and warehouse, which is what most midsize plants need to move beyond spreadsheets. The right answer depends on transaction volume, the number of plants, and how complex your production processes are; that is exactly what the initial assessment determines, before any scope is committed.

Can I start with only one part, for example costing or analytics?

Yes, and in most cases that is the sensible route. You can start with the finance and inventory core, add manufacturing in a second phase, and layer on analytics, automation, or industrial security afterward. What we do not recommend is starting with dashboards: without reliable transactional data, analytics only shows you the mess faster.

Do we have to stop production to implement?

No. Configuration and testing run in parallel with the operation, and go-live is planned in a window agreed with your team, usually tied to an inventory cutoff. In projects with several plants or lines we move in waves to limit the risk of each step.

How does it integrate with my plant systems, scales, or SCADA?

Through interfaces built on the standard Business Central APIs or on integration components designed for the case. The principle is that every piece of data has a single system of origin and a defined contract: what is sent, how often, and what happens if it fails. Integration scope is set during the design stage, after the assessment.

What about lot traceability and customer audits?

Lot and serial number traceability is part of the Business Central standard and is configured to match your receiving, production, and shipping rules. From there, the path of a lot is queried from the system, backward to the supplier and forward to the customer, with the associated quality checks.

Where does industrial cybersecurity fit in an ERP project?

As a protection layer, not as the center of the project. During the assessment we build a risk map between the plant network and the corporate network, and from there we define segmentation, identity management, and endpoint protection. We work with the Microsoft security tools and, for industrial environments, with Kaspersky.

How long does an implementation take?

It depends on the number of plants, the volume and quality of master data, the manufacturing scope, and the integrations required. We do not publish generic timelines, because committing to a date without knowing your operation helps no one: the initial assessment, which is complimentary, delivers a schedule with explicit assumptions.