Custom MES (Manufacturing Execution
System) Development in 2026

A UK specialty chemicals manufacturer we spoke to last quarter had been sold SAP MII by a systems integrator at £2.4m implementation cost plus £280k annual maintenance. Six months into implementation, the systems integrator had discovered that the manufacturer's batch process (multiple ingredient additions, temperature ramping across 8 hours, in-process quality testing at 4 stages, blend-to-order recipe management) did not match any SAP MII template. The customisation required to fit SAP MII to the process would take another 14 months and £1.6m additional investment. Total: £4m and 20 months for something that would still not fit their process cleanly.

The alternative we scoped was a custom MES built specifically for the batch chemical process: £380k over 8 months for the initial deployment. Real-time recipe management with operator wet-tablet interfaces, temperature and pressure logging integrated with existing PLCs, in-process quality test capture with lab integration, batch genealogy for regulatory traceability, integration with their existing bespoke ERP. Simpler, faster, cheaper, and fitting the process rather than forcing the process to fit generic manufacturing patterns.

They chose custom. Delivered on time in 8 months. OEE improved 14 percentage points in the first year. Batch cycle time dropped 22 percent through better recipe management. Regulatory audit findings dropped from 8 per quarter to 1.

That is the custom mes development conversation across UK and US mid-market manufacturers in 2026. SAP MII, Siemens Opcenter, Rockwell FactoryTalk are excellent for standardised discrete or process manufacturing where the manufacturer's process fits one of the templates. They are expensive and painful for manufacturers whose process is genuinely different. Custom MES is the right answer for those manufacturers, but only when the manufacturing engineering plus software engineering capacity is real.

This article is a candid guide for UK and US mid-market manufacturing operations and IT leaders scoping MES investment. Three approaches. When each is the right answer. Real cost bands. Features that actually matter. ISA-95 integration. What we learned building real-time operations tracking systems that share the technical DNA MES requires.

The Three MES Approaches in 2026

Approach 1: Off-the-shelf enterprise MES. SAP MII, Siemens Opcenter, Rockwell FactoryTalk, Aveva System Platform, GE Proficy. Mature platforms with pre-built templates for common manufacturing patterns (discrete, batch, process). Vendor-managed integrations with matching ERP (SAP MII with SAP ERP, Siemens Opcenter with Siemens PLM). Long implementations (12-24 months). Best for standardised manufacturing at enterprise scale.

Approach 2: Custom MES. Built specifically for the manufacturer's process, equipment, and existing IT stack. Full control over data model, workflows, and integrations. Faster build (6-12 months for single-site). Best for manufacturers with unique processes, non-standard ERP, or where off-the-shelf would require significant customisation.

Approach 3: Hybrid. Off-the-shelf MES core (typically SAP MII, Siemens Opcenter, or open-source such as Aveva) plus custom modules for specific workflows (unique recipe management, non-standard quality processes, specialised reporting). Balances vendor stability with process fit. Increasingly common at mid-market scale.

Per MESA International's 2026 MES benchmarks, roughly 42 percent of MES implementations that started as pure off-the-shelf ended up with significant custom modules or full custom rebuilds due to process misfit. This is why the hybrid approach has gained ground.

When Off-The-Shelf Enterprise MES Is the Right Answer

Off-the-shelf enterprise MES is the right starting point when at least four apply:

• Manufacturing processes fit standard patterns (discrete manufacturing, common process manufacturing)

• Company already runs matching ERP stack (SAP MII with SAP, Siemens Opcenter with Siemens)

• Budget over £500k for MES plus multi-year implementation

• Ops team has manufacturing IT capacity or long-term systems integrator relationship

• Regulatory or certification requirements need vendor-backed compliance documentation (pharmaceutical GMP, aerospace AS9100)

• Company plans multi-site rollout where vendor's cross-site tooling reduces per-site cost

• Manufacturing footprint is large enough that vendor pricing amortises well

Realistic expectation: 12-24 month implementation. £500k-£3m+ total. Requires strong internal or external systems integration capability. Delivers vendor-backed feature roadmap and compliance documentation.

When Custom MES Is the Right Answer

Custom MES is the right starting point when at least three apply:

• Manufacturing process is genuinely unique (specialty chemicals, custom fabrication, niche materials, one-of-a-kind production, prototype manufacturing)

• Off-the-shelf MES would require significant customisation that eats vendor benefits (past 30-40 percent customisation, custom is often better)

• Existing ERP is bespoke or non-standard (custom ERP, older systems, multi-ERP environment where no single vendor matches)

• Budget under £500k for MES with faster deployment required

• Team has manufacturing engineering plus software engineering capacity or willing to partner

• Manufacturing footprint is single-site or small multi-site where vendor pricing does not amortise

Realistic expectation: 6-12 month build for single-site. £150k-£450k for single-site single-product-line. Requires manufacturing engineering domain expertise plus software engineering execution. Delivers process-fit MES without customisation compromises.

When Hybrid MES Is the Right Answer

Hybrid MES is the right approach when:

• Company has matching ERP stack (SAP, Siemens, Rockwell) making core off-the-shelf MES natural

• Some workflows are genuinely non-standard requiring custom modules

• Budget over £250k for hybrid deployment

• Team wants vendor stability for core plus process fit for edge workflows

• Multi-site rollout benefits from off-the-shelf core with per-site custom modules

• Regulatory documentation from vendor for core plus custom-documented modules

Realistic expectation: 8-14 months. £250k-£800k. Requires systems integrator relationship for core plus internal or partner software engineering for custom modules.

Real 2026 Cost Bands

Two rules that hold at every approach. Total 5-year TCO for MES is typically 2-3x initial implementation cost due to ongoing customisation, integration maintenance, and evolution. And systems integrator services typically represent 40-60 percent of off-the-shelf enterprise MES cost; underestimating this creates the second-year budget shock most manufacturers experience.

Features Modern MES Needs in 2026

Eight capabilities every modern MES should have.

1. Real-time production monitoring. Live view of production floor status (running, idle, changeover, breakdown) with equipment-level detail. Feeds OEE calculation and downtime analysis. Requires integration with PLCs, SCADA systems, or IIoT sensors.

2. OEE (Overall Equipment Effectiveness) tracking. Automated calculation of availability, performance, and quality metrics per equipment and per shift. Dashboards for supervisors and operations leaders. Root cause analysis for OEE losses.

3. Recipe and batch management. For process manufacturing: recipe versioning, batch execution with parameter recording, in-process quality checks, batch genealogy for traceability. Regulatory requirement in pharmaceutical, food, chemicals.

4. Work order and dispatch management. Digital work orders replacing paper travellers. Operator wet-tablet interfaces on production floor. Real-time work order status. Integration with ERP for order sync.

5. Quality management integration. In-process quality inspections, non-conformance capture, corrective action tracking, integration with quality lab systems. Increasingly, machine-vision-based inspection integration.

6. Traceability and genealogy. End-to-end traceability from raw materials through production to finished goods and customer delivery. Regulatory requirement in regulated industries. Critical for recall management.

7. ERP integration (ISA-95 Level 3 to Level 4). Bi-directional integration with ERP for order sync, inventory movements, production reporting, and cost accounting. Standardised on ISA-95 or MES/ERP integration middleware.

8. Reporting and analytics. Configurable dashboards for operations leaders, supervisors, operators. KPI tracking including OEE, first-pass yield, on-time delivery, cost per unit. Increasingly, ML-powered predictive analytics for downtime and quality.

Per ISA-95 international standards documentation, MES sits at Level 3 of the ISA-95 hierarchy, bridging Level 2 (SCADA and process control) and Level 4 (ERP and business planning). Integration compliance with ISA-95 makes both directions cleaner.

Real ROI Expectations for MES

OEE improvement. 8-20 percentage points within 12 months of deployment for manufacturers moving from paper-based operations tracking to real-time MES. Bigger gains when starting OEE is low (under 55 percent); smaller gains when starting OEE is already high (over 80 percent).

Production downtime reduction. 15-30 percent through real-time visibility, faster response to equipment issues, and better root cause analysis of stops.

Quality defect reduction. 20-40 percent through in-line inspection integration, faster feedback loops, and non-conformance root cause tracking.

Manufacturing labour efficiency. 12-25 percent improvement through paperless work instructions, reduced hunting for information, and clearer task dispatch.

Regulatory audit findings. 60-85 percent reduction in audit findings for regulated manufacturers (pharmaceutical, food, medical devices) through documented batch genealogy and electronic records.

ROI break-even. Off-the-shelf enterprise MES typically breaks even at 24-36 months for manufacturers with over £50m annual production. Custom MES typically breaks even at 12-18 months due to faster deployment and lower initial cost.

What We Learned Building Real-Time Operations Tracking Systems

WhiteStone has shipped TrackVid (real-time video quality tracking for ecommerce fulfilment across 4000+ merchants) and SiteFlow (construction site operations tracking with real-time worker and equipment visibility for UK property developer). Both share the technical DNA MES requires: real-time event processing, integration with physical operations, dashboards for operations leaders, mobile-first operator interfaces. Three lessons transfer directly to any UK or US manufacturer scoping MES.

Real-time event processing at scale is the hardest part. TrackVid processes millions of video events daily with sub-second latency for claim triggers. SiteFlow processes thousands of site events across multiple concurrent projects. The technical challenge in both is the same as MES: reliable event capture from physical operations, resilient processing under load, and operations-ready dashboards. Teams that underestimate this build MES that falls behind reality during production peaks, and operators stop trusting the system.

Operator interfaces matter more than management dashboards. Both TrackVid and SiteFlow succeeded because operators (ecommerce packers, construction workers) had interfaces they actually used. Same for MES: operator wet-tablet or ruggedised interfaces on the production floor are what determines whether MES data reflects reality or is a compliance exercise. Management dashboards are secondary.

Integration with existing systems is 30-40 percent of the build. For TrackVid: integration with ecommerce platforms, marketplaces, courier APIs. For SiteFlow: integration with existing project management tools and financial systems. For MES: integration with PLCs, SCADA, ERP, lab systems, quality systems. Underestimating integration effort is the most common cause of MES implementation overrun.

See our portfolio of shipped work for real-time operations tracking case studies. For a scoped MES conversation, book a manufacturing software call with WhiteStone.

Common Failure Modes

Buying enterprise MES when process is too unique. Manufacturer buys SAP MII expecting standard implementation. Discovers process needs 40+ percent customisation. Implementation blows past £2m and 18 months without going live. Fix: honest process-fit assessment before committing; if past 30-40 percent customisation, custom MES is often the better answer.

Building custom MES without manufacturing engineering capacity. Software team builds MES without deep understanding of production process. Delivered system does not match how the floor actually works. Operators work around it. Fix: manufacturing engineering plus software engineering must be jointly scoped; software-only teams building MES for manufacturing they do not understand consistently fail.

Underscoping integration with existing systems. MES scoped as standalone system without full integration mapping (PLCs, SCADA, ERP, lab, quality, warehouse). Integration effort during build exceeds MES core effort. Timeline blows. Fix: integration surface mapped as part of initial MES scope, not as an afterthought.

Ignoring operator interface reality. MES designed with management dashboards but weak operator interfaces. Operators use paper or spreadsheets alongside MES. Data quality degrades. Management dashboards become misleading. Fix: operator interfaces are the first design priority, not the last; ruggedised tablets, gloved-hand operation, clear status indicators.

Frequently Asked Questions

What is custom MES development and what does it include in 2026?

Custom MES (Manufacturing Execution System) development builds a software system that bridges the production floor and enterprise systems. Includes: real-time production monitoring, OEE tracking, recipe and batch management (for process manufacturing), work order dispatch and execution, quality management integration, traceability and genealogy, ERP integration (ISA-95 Level 3 to Level 4), and configurable reporting. Custom means built specifically for the manufacturer's process, equipment, and existing IT stack rather than adopting SAP MII, Siemens Opcenter, Rockwell FactoryTalk, or Aveva.

When should a manufacturer build custom MES instead of buying SAP MII or Siemens Opcenter?

Build custom when at least three apply: manufacturing process is genuinely unique (specialty chemicals, custom fabrication, niche materials), off-the-shelf MES would need over 30-40 percent customisation, existing ERP is bespoke or non-standard, budget under £500k for MES with faster deployment required, team has manufacturing engineering plus software engineering capacity, and manufacturing footprint is single-site or small multi-site where vendor pricing does not amortise.

How much does custom MES development cost in 2026?

Off-the-shelf enterprise MES (SAP MII, Siemens Opcenter, Rockwell FactoryTalk, Aveva): £500k-£3m+ implementation, 12-24 months. Custom MES single-site single-product-line: £150k-£450k, 6-12 months. Custom MES multi-site with ERP integration: £400k-£1.2m+, 12-20 months. Hybrid (off-the-shelf core plus custom modules): £250k-£800k, 8-14 months. Total 5-year TCO typically 2-3x initial implementation.

What features does a modern MES need in 2026?

Eight capabilities: real-time production monitoring, OEE tracking with availability/performance/quality metrics, recipe and batch management for process manufacturing, work order and dispatch management with digital operator interfaces, quality management integration including in-line inspection, traceability and genealogy for regulatory compliance, ERP integration (ISA-95 Level 3 to Level 4), and configurable reporting with predictive analytics.

How does custom MES integrate with existing ERP systems?

Bi-directional integration typically via ISA-95 standards or MES/ERP integration middleware. MES sends production reporting, actual costs, inventory movements, and completion status to ERP. ERP sends production orders, bills of material, routing, and demand forecasts to MES. Common integration technologies: REST APIs, message queues (Kafka, RabbitMQ), or vendor-specific connectors (SAP RFC, Oracle integration).

What are the biggest failure modes for MES implementations?

Four categories. Process-fit failure: buying enterprise MES when process needs 40+ percent customisation. Capacity failure: building custom MES without manufacturing engineering domain expertise. Integration failure: underscoping integration with PLCs, SCADA, ERP, lab, quality systems. Operator interface failure: MES designed for management dashboards but weak operator interfaces, causing floor to work around the system.

Why choose WhiteStone Infotech for custom MES development?

We build real-time operations tracking systems that share MES's technical DNA. TrackVid processes millions of video events daily for 4000+ ecommerce merchants with sub-second latency. SiteFlow tracks construction site operations for UK property developer with real-time worker and equipment visibility. Both required exactly the same technical discipline MES requires: reliable event capture from physical operations, resilient processing at scale, and operator interfaces that get used on the floor. Contact WhiteStone Infotech at whitestoneinfotech.com/contact.

The One Thing to Remember

Custom MES development in 2026 has three approaches: off-the-shelf enterprise MES (SAP MII, Siemens Opcenter, Rockwell FactoryTalk, Aveva at £500k-£3m+ over 12-24 months), custom MES built for specific process (£150k-£450k over 6-12 months for single-site), and hybrid (£250k-£800k over 8-14 months). Choose based on process uniqueness, existing ERP, and whether the manufacturer has manufacturing engineering plus software engineering capacity. Real ROI: 8-20 percentage points OEE improvement, 15-30 percent downtime reduction, 20-40 percent quality defect reduction. The single decision that determines success: is the MES scoped to actual production floor reality (equipment, protocols, operator workflows, existing IT), or scoped to a generic manufacturing template. Floor reality delivers ROI. Generic templates deliver a compliance system operators work around.