Resources

Manufacturing Insights

Quick answers and short guides on how manufacturing organizations digitize product development, production, quality and supply chain. Written in points, not prose, for plant leadership, operations teams and the IT leaders who support them.

Quick answers

Manufacturing digitalization, answered

The questions plant and business leaders ask most often, answered in a few points each. Open a question to read the answer; the guides further down go deeper.

QWhat is a Manufacturing Execution System (MES)?
  • Software that manages and records what happens on the shop floor between the release of a production order and the confirmation of finished goods.
  • It receives what needs to be made, guides how it is made, records what actually happened, and hands the outcome back to inventory, quality and reporting.
  • It sits between enterprise planning (ERP) and the people and equipment that make the product.
Read the guide: What is MES and why does it matter?
QHow is an MES different from ERP?
  • ERP plans and accounts for the enterprise: demand, materials, cost, finance. Its unit is the order and the cost centre; its horizon is days to months.
  • MES executes and records production: which line is running which order, what was consumed, what was produced, what went wrong. Its unit is the batch, the operation and the shift; its horizon is minutes to hours.
  • ERP knows what should be made and what it should cost. MES knows what is being made right now and what actually happened.
See the side-by-side comparison
QOur ERP has a production module. Do we still need an MES?
  • For some plants the ERP module is enough: it creates orders, back-flushes materials and posts confirmations.
  • What it does not naturally record is the sequence of operations, the lots consumed at each step, the stoppages in between and who confirmed what. That detail then lives on paper or in spreadsheets.
  • The test: does the information your plant needs during the shift exist anywhere except on paper? If not, the gap is an execution gap, and that is what an MES is for.
QHow do we know a plant is ready for an MES?

An MES is usually justified by the cost of not knowing. If several of these apply, the plant is carrying an execution gap:

  • Production status is known only at shift end or month end.
  • A traceability request takes hours of document searching.
  • Material consumption is reconciled by hand and rarely matches inventory.
  • Different lines or plants run the same product in different ways.
  • Operators spend a meaningful share of each shift on paperwork.
QWhere should a digitalization program start?
  • Where the process is most manual. Paper batch records point to MES, audit files and supplier scorecards to QMS, requisition emails to Supply Chain.
  • Where traceability risk is highest. Start with the module that creates the missing record: production genealogy, quality history or batch inventory.
  • Where the plan and the floor disagree most. Connect planning with execution so plans are built on actual stock and progress.
  • Every module works on its own and connects to the others later; the first one should remove the most friction now.
Three ways to pick the first module
QWhat does a digital QMS change?
  • It moves the quality system out of folders and spreadsheets: the audit program, CAPA, supplier ratings, controlled documents, lab results and specifications in one governed record.
  • One released specification master feeds both the shop floor (the MES Quality module) and the lab (LIMS), so nobody tests against an old version.
  • Audit findings, escalated deviations and complaints become CAPA with an owner, a due date and effectiveness verification.
  • Audit preparation becomes a report from the record instead of a document hunt.
Explore QMS
QWhy is traceability easier to build in than to reconstruct?
  • Genealogy is a by-product of recording each material issue and consumption against the order and batch as it happens.
  • Reconstructing it afterwards means matching paper batch cards, stock ledgers and dispatch notes by hand, hours per request.
  • Built in, a forward or backward trace from supplier lot to shipped order is a query, not a project.
QWhat does Industry 4.0 mean for a mid-sized plant?
  • Strip the vocabulary away and the durable idea is simple: information created once, at the point of work, and shared across functions.
  • For most plants the first steps are not sensors and robots but a digital record of production, quality and material movement that the whole organization can act on.
  • Once that record exists, analytics and AI have something reliable to work from.
QHow does a digital supply chain help a manufacturer?
  • Plans start from demand and current stock rather than last month's report.
  • Material availability is confirmed before a production order is released, so shortages are known before the line is committed.
  • Dispatch is promised on released, available finished goods, and consumption from the floor feeds the next plan.
Explore Supply Chain Management
QWhat does a digital EHS system change?
  • Incidents and near misses are reported at the point of work and closed through investigation and CAPA, so the same event stops recurring.
  • Permits, risk assessments and competencies are checked against the job, the area and the asset before work starts.
  • Environmental readings are recorded against limits as they are taken, and the data behind every return is already on record.
  • Licences, obligations and training records sit with their evidence, so an inspection is a report rather than a document hunt.
Explore EHS
QWhat does a digital asset management system change?
  • The asset register moves from a spreadsheet onto the plant model, with every job, part and cost accumulated against each asset.
  • Preventive plans generate the work when it is due, and overdue jobs are visible instead of slipping quietly.
  • Breakdowns become work orders with labour, parts, downtime and findings, so the same failure stops recurring unnoticed.
  • Repair-or-replace and budget decisions are made on the asset's own history rather than on the loudest breakdown.
Explore Asset Management
QHow is AI used with these systems?
  • Each of our solutions exposes its data through a native AI connector, so the AI platform you choose can connect to it, process it, and detect, predict, plan, optimize and control on what it measures.
  • You decide what is exposed: only the data sets a given problem needs, under the same roles and audit trail as the application.
  • The connector is platform-neutral; it works with any AI service or model your organization adopts.
See the native AI connector

Guides

Three guides, in pointers

Each guide is written for plant leadership, operations teams and the IT leaders who support them: the trade-offs and the practical steps, in short points and simple visuals, without assuming a particular product.

MES · Explainer

What is MES and why does it matter?

A Manufacturing Execution System (MES) manages and records what happens on the shop floor between the release of a production order and the confirmation of finished goods. It sits between enterprise planning and the people and equipment that make the product.

The gap an MES fills

  1. ERPPlans the order, values the stock, closes the period.
  2. The execution gapPaper batch cards, whiteboards, logbooks and end-of-shift spreadsheets. Data that arrives late and unlinked.
  3. Shipments and invoicesRecorded back in ERP and finance.
  • The problem is not a lack of data. It is data that arrives late, in inconsistent formats, without a reliable link to the order, material or machine it describes.
  • An MES closes the gap: it receives what needs to be made, guides how it is made, records what actually happened, and hands the outcome back to inventory, quality and reporting.

What an MES actually does

Work order management

  • An ERP order becomes a digital work order with its bill of materials, routing or recipe, instructions and status.
  • Sequenced to a line and shift; released when materials and resources are available.

Operator guidance and capture

  • Operators see the current step, its instructions and the confirmations expected.
  • Quantities, consumption, downtime reasons and process values recorded at the workstation as they occur.

Material tracking and genealogy

  • Every issue and consumption tied to the order and batch it went into.
  • Forward and backward traceability follows from the record, not from a document search.

Monitoring and reporting

  • Supervisors see order progress, exceptions and downtime during the shift.
  • Shift, daily and period reports come from the same records, with no manual consolidation.
An MES does not add reporting on top of production. It changes where production information is created, which is what makes reliable reporting possible.

Why it matters to leadership

  • Visibility while it can still be acted on. Deviations and stoppages seen during the shift, not in tomorrow's report.
  • One standard process across lines and plants. The same steps and records everywhere, the basis for comparison and audits.
  • Traceability on record. Customer queries, audits and recalls answered from the genealogy.
  • Better inputs to inventory and costing. Consumption and output feed ERP from actuals, not estimates.
  • Less manual work. Fewer forms, less re-keying, fewer reconciliation spreadsheets.

Signals that a plant is ready

  • Production status is known only at shift end or month end.
  • A traceability request takes hours of document searching to answer.
  • Material consumption is reconciled by hand and rarely matches inventory.
  • Different lines or plants run the same product in different ways.
  • Operators spend a meaningful share of each shift on paperwork.

Several of these apply? The plant is carrying an execution gap that an MES is designed to close. An MES does not replace ERP or a QMS: it exchanges orders, confirmations and movements with ERP, and works to the specifications the QMS releases while sending deviations and samples back to it.

Where our MES software fits

We implement MES as part of a connected set of production, quality, product-development and supply-chain solutions, configured to the way work is governed on the floor. The same production record is available to the AI platform you choose through a native AI connector. See Manufacturing Execution System for scope and capability areas.

Back to quick answers

Strategy · Explainer

MES vs ERP: understanding the difference

ERP and MES are often discussed as alternatives. They are not. They answer different questions, at different levels of detail, for different people, and a plant that runs well usually has both.

Two systems, two questions

ERP

What should we make, and what should it cost?

  • Demand, purchasing, inventory value, costing, finance
  • Unit of thinking: the order, the material, the cost centre
  • Horizon: days, weeks, months

MES

What is being made right now, and what actually happened?

  • Which line, which order, which step; what was consumed and produced
  • Unit of thinking: the batch, the operation, the machine, the shift
  • Horizon: minutes and hours

Side-by-side comparison

DimensionERPMES
PurposePlan and account for the enterprise's resources.Execute, track and record production against the plan.
Time horizonDays to months; planning cycles, period close.Minutes to a shift; events as they occur.
GranularityOrder, material, cost centre, period totals.Operation, batch, machine, operator, individual event.
Typical usersPlanners, procurement, finance, management.Operators, supervisors, production and quality engineers, plant management.
Data capturedOrders, receipts, issues, confirmations, inventory values, costs.Step confirmations, quantities, consumption by lot, downtime and reasons, process values, genealogy.
Questions answeredWhat do we need to buy? What did this order cost? What is our inventory worth?Which line is behind plan? Which lot went into this batch? Why did line 3 stop?

Where confusion starts

  • Most ERP systems include a production module: it creates orders, back-flushes materials and posts confirmations. For some plants that is enough.
  • What it does not naturally record: the sequence of operations, the lots consumed at each step, the stoppages in between, the operator who confirmed each one. That detail ends up on paper or in spreadsheets, reconciled later.
  • The right question is not "does our ERP have a production module?" but "does the information the plant needs during the shift exist anywhere except on paper?"
ERP tells you what the order should have cost. MES tells you why it cost what it did.

How the two work together

  1. ERP releasesProduction orders, bills of materials, routings.
  2. MES executesRecords consumption and output at the operation level, as it happens.
  3. ERP receivesConfirmations and inventory movements. ERP keeps the financial picture; MES keeps the operational record that explains it.
  • Define the boundary early. Which system masters bills of materials and routings, how often confirmations post, and whether the MES reports actual consumption by lot or ERP keeps back-flushing from standards.
  • There is no single right answer, but an undefined boundary is the most common cause of integration friction later.

Deciding what to invest in

Planning and inventory are the problem

  • Stock accuracy, purchasing lead times, costing.
  • Look at ERP and its master data first.

Execution is the problem

  • Late visibility, manual traceability, inconsistent processes across lines.
  • An MES addresses it directly; ERP changes will not.

Both are problems

  • Sequence matters: reliable ERP master data speeds the MES; MES actuals make ERP data reliable.
  • Start where the operational pain is greatest and connect from there.

Where our MES software fits

We implement the execution layer and connect it to the enterprise systems a manufacturer already runs: orders, confirmations and inventory movements exchanged with ERP, and production linked to quality, product development and supply chain. See Manufacturing Execution System and Integrated Manufacturing Digitalization.

Back to quick answers

Digitalization · Guide

Moving from Excel-driven operations to digital workflows

Spreadsheets run more manufacturing operations than any enterprise system. They are quick to build, familiar and free to change. That is exactly why they accumulate, and why replacing them is a process decision before it is a technology decision.

Why spreadsheets win first

  • A planner needs a schedule the ERP cannot produce in the shape the lines need, so a workbook appears. Quality needs an inspection log, so a second one appears. Someone reconciles the two, so a third links them.
  • None of this is a mistake. The spreadsheet is usually the first honest map of how the process actually works. That map is worth keeping when the workflow is digitized.

Where the problems start

  • No single version. Copies on shared drives and email diverge; nobody is certain which is current.
  • No record of who changed what. A cell is overwritten with no previous value, author or reason.
  • Data entered late and twice. Written on paper on the floor, typed into a workbook later, re-keyed into ERP after that.
  • Knowledge held by one person. The macro works until its author is on leave.
  • No link to the record of truth. The workbook, the batch record and the ERP each say something different.

A practical path

  1. Map the workflows, not the workbooksList the processes the spreadsheets support and, for each, who creates the information, who consumes it and what decision it drives.
  2. Decide the record of truth for each data typeOrders, material masters, inspection results and stock balances each need one owning system. Ownership removes the reconciliation instead of digitizing it.
  3. Digitize capture at the point of work firstThe confirmation at the workstation, the inspection at the line, the receipt at the dock. Reports follow from clean capture.
  4. Standardize master data before automatingProduct codes, units, line and machine names, reason codes. Differences between workbooks become differences between screens.
  5. Connect, then retire deliberatelyOnce a workflow is digital and connected, retire the spreadsheet on a date, with its owner's agreement. A workbook "kept for reference" becomes the working copy again within a quarter.
The goal is not fewer spreadsheets. It is information created once, at the point of work, with an owner, a history and a connection to the process that needs it.

What changes for the team

  • Operators enter information once, on a screen designed for the step they are performing.
  • Supervisors see status without asking for it.
  • Planners work from actuals rather than yesterday's consolidation.
  • Quality and production share one record of the batch.
  • Management reporting becomes a by-product of the process, not a monthly project.

Common mistakes

  • Digitizing everything at once. Start with the workflow whose failure is most expensive or most visible, prove it, then extend.
  • Copying the spreadsheet layout onto a screen. Design for the step and the role, not for the grid.
  • Leaving the owners out. The people who built the workbooks know the exceptions; leave them out and the exceptions return as new workbooks.
  • Skipping integration. A digital form that still needs re-keying into ERP has removed the paper, not the double entry.

Where our software fits

We digitize the workflows that run product development, production, quality and supply chain, starting from the plant's process map rather than a screen layout, with configurable workflows that accommodate plant-specific practice without custom development for every variation. See Integrated Manufacturing Digitalization or Manufacturing Challenges.

Back to quick answers

In preparation

More insights are being prepared

The following articles are in progress and will be published on this page as they are completed. Each follows the same approach: general manufacturing-technology knowledge first, product specifics last.

  • How Digital QMS improves manufacturing quality In preparation
  • Digital Transformation in Manufacturing In preparation
  • Connecting NPD with Manufacturing In preparation
  • Manufacturing Traceability In preparation
  • Industry 4.0 and the Connected Factory In preparation
  • Digital Supply Chain for Manufacturers In preparation
  • Digital EHS for Manufacturing Plants In preparation
  • From Reactive to Planned Maintenance In preparation