Skip to content

MES Requirements: Specification Structure, RFI/RFP & Pitfalls

Published Updated 20 min read

Learning path Step 1 of 4
Contents
  1. What MES requirements actually are — and where most specifications go wrong
  2. The three formal contexts where MES requirements appear
  3. The functional-requirements layer — what the MES has to do
  4. The MoSCoW prioritization — or, why the Must-Have Inflation kills procurement
  5. Technical and integration requirements — the 5 % of the document that drives 50 % of the cost
  6. The structure of a serious MES requirements specification
  7. Fit/Gap assessment — the mechanism the specification exists to enable
  8. Cybersecurity requirements in 2026 — NIS2, Cyber Resilience Act, and the new procurement reality
  9. Common MES specification failures — a field taxonomy
  10. How this fits into the SYMESTIC platform
  11. FAQ
By Martin Brandel · Last updated: October 2026

What MES requirements actually are — and where most specifications go wrong

MES requirements are the functional, technical, organizational, and commercial criteria that a Manufacturing Execution System has to satisfy to fit a specific company's production processes, IT landscape, regulatory obligations, and long-term strategy. They are typically assembled into a formal document — variously called a requirements specification, Pflichtenheft, Lastenheft, or SRS (Software Requirements Specification) — that becomes the contractual and operational foundation for vendor selection (RFI/RFP), implementation planning, and post-go-live acceptance. The document is not bureaucracy. It is the mechanism by which a plant translates its actual operational reality into terms a vendor can bid against and that an implementation team can deliver against.

The quality of the requirements specification predicts the outcome of an MES implementation far more reliably than the quality of the MES product being bought. A mediocre MES installed against a well-structured, clearly prioritized, operationally grounded specification will succeed. A world-class MES installed against a bloated, un-prioritized, integration-underspecified checklist will struggle. This piece describes the discipline that separates the two outcomes.

The three formal contexts where MES requirements appear

The term "MES requirements" does not describe a single artefact. It shows up in at least three distinct procurement contexts, each with different information goals, different formality levels, and different vendor expectations. Confusing them is one of the most common and most expensive mistakes in MES procurement.

Instrument Purpose Typical length & timeline
RFI — Request for Information Early-stage market scan. Buyer describes the problem space and operational context; asks vendors to describe how they would approach it. Used to build the vendor shortlist. 5–15 pages, 4–6 weeks.
RFP — Request for Proposal Detailed specification against which shortlisted vendors submit formal, binding proposals including solution architecture, project plan, and pricing. 30–100 pages, 8–14 weeks.
RFQ — Request for Quotation Narrow commercial exercise when technical solution is already agreed and only pricing and commercial terms are being negotiated. 10–20 pages, 2–4 weeks.

The RFP is where most of the requirements-specification work actually lives, and where most of the failure modes originate. The RFI is often skipped — which is usually a mistake, because the RFI is the cheapest mechanism to calibrate scope and surface fundamental architectural incompatibilities (cloud vs. on-premise, multi-tenant SaaS vs. single-tenant, process-industry-oriented vs. discrete-manufacturing-oriented) before anyone has invested months writing a detailed specification.

The functional-requirements layer — what the MES has to do

Functional requirements describe the production-management capabilities the MES must provide. The German reference framework, VDI 5600 (published in blätter 1–7, Blatt 1 in the October 2016 edition), structures these into ten task areas: order management, operational fine-scheduling, resource management, material management, personnel management, data collection and processing, performance analysis, quality management, information management, and energy management. The international reference is ISA-95, whose Part 3 activity model covers four operations areas — production operations, quality operations, maintenance operations, and inventory operations — each broken down into eight activities (definition, resource management, detailed scheduling, dispatching, execution management, data collection, tracking, and performance analysis). These two frameworks cover roughly the same territory from different angles; most serious MES specifications in the German-speaking market reference VDI 5600 explicitly, while specifications written for global or multi-national scope use ISA-95.

The mistake that almost every first-time MES specification makes is to translate the full VDI 5600 or ISA-95 taxonomy into an exhaustive checklist of 300+ individual features, each rated independently against vendor responses. This is the feature checklist trap: the specification becomes a comprehensive enumeration of every function an MES could theoretically provide, with no meaningful priority, no linkage to actual business use cases, and no way for the vendor to distinguish what matters operationally from what is being asked because it sounded thorough. The checklist is measurable — you can count how many of the 300 items a vendor claims to support — but the measurement is worse than useless, because every vendor checks most boxes, and the real differences are in which functions are supported at what depth, integrated with what, and deliverable within which timeline.

The discipline that produces actually useful functional requirements is a prioritized, use-case-grounded structure organized around the plant's real operational problems:

Weak requirement (typical checklist) Strong requirement (use-case grounded)
"System must support downtime capture." "Machine stoppages of >30 seconds must be automatically captured via PLC signals, categorized into a predefined 3-level taxonomy (technical/organizational/planned), and attributable to a specific work order within 5 seconds of stoppage. Operator-assisted reclassification must be possible via the line terminal within the current shift."
"System must be user-friendly." "Line-side terminals must support single-touch booking on industrial touchscreens (10-inch, with gloves). Maximum booking-to-acknowledgement latency: 2 seconds. Five most-used functions accessible with no more than two taps from the main screen."
"System must provide traceability." "Serial-level genealogy capture for all safety-relevant characteristics of products in Line 3, Line 5, and Line 7, linking finished-unit serial number to component lot numbers, machine IDs, operator IDs, and captured process-parameter time-ranges. Forward and backward query response time <10 seconds for any unit produced within the last 90 days."
"System must integrate with SAP." "Bidirectional integration with SAP S/4HANA (version 2023) via IDoc/ABAP interfaces for: (a) production-order download including BOM and routing; (b) confirmation postings of quantities, times, downtime; (c) material consumption postings at lot/batch level. Initial order download <5 seconds for orders with <100 operations. Interface to be operated in test and production environments per SAP transport-path conventions."

The strong-requirement format does three things the checklist cannot: it specifies the operational context (what the plant is actually trying to achieve), it specifies measurable acceptance criteria (so "done" can be proven rather than negotiated), and it constrains the vendor's solution space enough to allow meaningful fit/gap assessment but not so much that it prescribes the implementation. The principle for every requirements workshop: specify what and why; leave how to the vendor. Customers who specify how — "must use PostgreSQL", "must run on Ubuntu 22.04", "must use webhook-based integration to ERP" — are either accidentally excluding better solutions or specifying constraints they do not actually care about.

The MoSCoW prioritization — or, why the Must-Have Inflation kills procurement

A requirements specification without prioritization is operationally indistinguishable from having no requirements at all, because prioritization is the mechanism by which the buyer communicates what matters when (inevitably) tradeoffs have to be made during implementation. The standard framework for this is MoSCoW — Must have, Should have, Could have, Won't have — and its disciplined application is among the most reliable predictors of project success.

Priority Definition Target share of total requirements
Must have Project fails without this. Go-live is conditional on satisfying these. ~60 % (NOT more)
Should have Important but not go-live-blocking. Workarounds acceptable for a limited time. ~20 %
Could have Desirable if included without significant cost or timeline impact. ~15 %
Won't have (this release) Explicitly out of scope. Named here to prevent scope creep during implementation. ~5 %

A failure mode in many first-draft specifications is must-have inflation — the pattern in which every stakeholder's pet requirement ends up marked "Must have" because no one wants to be the person whose concern gets downgraded. When nearly every line item is classified Must-Have, the specification has no prioritization at all. Vendors reading such a document have no way to propose a pragmatic phased rollout, project managers have no way to make the inevitable scope-vs-timeline tradeoffs during implementation, and the first major project crisis becomes a political fight rather than a management decision, because everyone's requirement is equally Must-Have. The discipline that prevents this is a single named owner for the requirements-prioritization decision — typically the sponsoring COO or plant manager — with explicit authority to overrule stakeholder preferences when the Must-Have share exceeds the target of roughly 60 %. Without that ownership, the specification becomes an accumulated wishlist rather than an operational plan.

Technical and integration requirements — the 5 % of the document that drives 50 % of the cost

A consistently undervalued section of MES specifications is the technical and integration-requirements chapter. It typically runs 3–8 pages in a 60-page specification — roughly 5–10 % of the document volume — and it drives somewhere between 40 % and 60 % of the actual implementation effort and cost. This integration underspecification is a reliable predictor of implementation overruns.

The reason integration drives so much cost and is so consistently underspecified is structural: the functional-requirements team (production managers, quality managers, plant controllers) does not see integration — it sees features. The technical-requirements team (IT, automation engineering) sees integration — but is usually not the team writing the specification. The specification inherits the blind spots of its authors, and the integration gap appears first during implementation, when every underspecified interface turns into an unbudgeted engineering project.

A properly scoped technical-and-integration-requirements section covers at least the following dimensions:

Dimension What must be specified
Deployment architecture Cloud (which cloud), hybrid, on-premise; single-tenant or multi-tenant; data-residency constraints (EU vs. global); disaster-recovery RTO/RPO targets.
ERP integration Which ERP (system and version), which transactions, which direction, which cadence, which volume (orders/day, confirmations/day), which test and cutover approach. Named technical protocol (IDoc, BAPI, OData, REST).
Machine connectivity — greenfield OPC UA server models, PackML compliance requirements, namespace conventions, security-policy requirements (Sign+Encrypt, certificate management).
Machine connectivity — brownfield Per-machine inventory of PLC types (Siemens S5/S7/TIA, Allen-Bradley, Beckhoff, Mitsubishi, legacy proprietary), available signals, acceptable connection methods (digital I/O tap, existing PLC block extension, retrofit gateway), no-PLC-intervention constraints.
Data model & master-data governance Canonical identifiers (work-order, unit, lot, batch, machine, operator, tool), master-data ownership (where each entity is sourced, where it can be edited), version-control approach.
Other system integrations CAQ, CMMS, WMS, LIMS, PLM, BI platforms, historian, energy-management systems — each with direction, protocol, cadence.
Identity & access management SSO via SAML/OIDC, role model, MFA requirements, AD/Azure AD integration, shop-floor-terminal badge/RFID sign-on.
Cybersecurity & compliance NIS2 obligations (essential/important entity designation, incident reporting, supply-chain security), Cyber Resilience Act alignment (from 2027), ISO 27001 certification requirements for the vendor, IEC 62443 compliance for OT-layer components, GDPR data-protection commitments.
Non-functional requirements Availability SLA (typically 99.9 % = <8.8 hours/year), response times under named load profiles, data-retention windows, audit-trail requirements.
Scaling & multi-site rollout Number of plants, sequence, timeline, shared-template approach, local-variation allowances, language requirements.

Every one of these dimensions has to appear in the specification with the same discipline as functional requirements — measurable, prioritized per MoSCoW, grounded in the actual IT/OT landscape. A plant that specifies "integrate with ERP" without specifying which ERP, which transactions, and what volume, has done zero integration specification. A plant that specifies "OPC UA compatible" without auditing its actual installed base of PLCs has ignored the brownfield problem entirely, which means discovery of fifty 1990s-era PLCs without OPC UA happens during implementation rather than during specification.

The structure of a serious MES requirements specification

A requirements document that has been disciplined through the principles above typically has the following structure, in roughly the following proportions:

Section Typical length Content
1. Executive summary & strategic context 2–4 pages Company context, current operational pain points, project objectives, success criteria, decision-maker alignment.
2. Scope & timeline 2–3 pages Plants, lines, work centers in scope; phased-rollout plan; target go-live dates; named out-of-scope items.
3. Operational context 4–8 pages Product families, production modes (discrete, batch, process), shift models, production volumes, KPIs in use, regulatory context (IATF 16949, FDA, ISO 9001).
4. Functional requirements 15–30 pages Structured per VDI 5600 or ISA-95; use-case-grounded; MoSCoW-prioritized; measurable acceptance criteria.
5. Technical & integration requirements 10–20 pages Deployment architecture, ERP integration, machine-connectivity inventory (brownfield detail!), data model, identity/access, cybersecurity (NIS2, CRA, ISO 27001), multi-site rollout. This is where most specifications fail.
6. Non-functional requirements 2–4 pages Availability SLA, response times, scalability, usability, data retention, audit-trail, backup/DR.
7. Implementation & service requirements 3–6 pages Implementation methodology, training, documentation, acceptance-test approach, ongoing support SLA, release-management expectations, escalation path.
8. Commercial & contractual 2–4 pages Pricing model (CapEx/OpEx, per-seat, per-machine, per-plant), contract terms, payment milestones, IP and data-ownership provisions.
9. Response template Variable Structured vendor-response format: named contact, solution overview, requirement-by-requirement fit/gap response, reference customer case, pricing.

Specifications that run materially longer than 60–80 pages in total usually suffer from one of two failure modes: either they have drifted into prescribing implementation details that should belong to the vendor, or they have fallen into the Feature Checklist Trap. Specifications materially shorter than 30 pages usually suffer from Integration Underspecification. The right length is whatever it takes to cover the nine sections above with disciplined prioritization; for a typical mid-market multi-plant MES programme that is usually a few dozen pages.

Fit/Gap assessment — the mechanism the specification exists to enable

The point of a requirements specification is to make possible a structured fit/gap assessment of vendor responses. Fit/Gap is the comparison of each requirement against what each vendor proposes, classified per requirement into one of four states: fully supported as standard (green), supported with configuration (yellow), supported with customization (orange), or not supported (red). A disciplined fit/gap for a 150-requirement specification produces a clear quantitative picture of which vendor fits which part of the scope at what cost, and gives the procurement team a defensible basis for vendor selection.

The fit/gap exercise only works if the requirements are properly prioritized. Must-Have requirements that fall in the red or orange column are deal-breakers or major-cost items; Should-Have requirements in red are acceptable with workarounds; Could-Have requirements in any color are essentially cost-comparison factors. A specification without MoSCoW prioritization cannot be fit/gap-analysed meaningfully, because every red cell becomes equally alarming, which is to say none of them do. The specification structure and the prioritization discipline are mutually reinforcing: neither works without the other.

Cybersecurity requirements in 2026 — NIS2, Cyber Resilience Act, and the new procurement reality

The regulatory landscape around cybersecurity for MES procurement has changed materially in the last 18 months, and requirements specifications drafted before October 2024 typically do not reflect the current reality. Three specific obligations now shape MES procurement for any manufacturer selling into or operating within the EU:

  1. NIS2 Directive. The EU's Network and Information Security Directive 2 had to be transposed into national law by 17 October 2024 (in Germany, the implementing law has applied since 6 December 2025). It designates manufacturers across broad sectors — including significant parts of manufacturing, food production, chemicals, and automotive supply — as either "essential" or "important" entities, with direct cybersecurity obligations that flow down to all software vendors in the supply chain. For MES procurement, this translates into specific requirements on vendor incident-reporting capabilities, supply-chain-security attestations, and ongoing security-governance evidence.
  2. Cyber Resilience Act (CRA). Enters into force progressively through 2027, imposing mandatory cybersecurity requirements on products with digital elements sold into the EU — which includes MES platforms. For buyers, this means vendor statements of CRA compliance will become a standard RFP requirement from 2026 onward.
  3. ISO 27001 certification. Long-standing requirement in enterprise procurement.

Specifications drafted in 2026 should include these three as first-class requirements in the technical-and-integration section, with evidence requirements (named certifications, copies of attestations, incident-response-process documentation) rather than self-attestation. Vendors that cannot produce the evidence will not pass procurement screening at NIS2-regulated customers, regardless of functional fit.

Common MES specification failures — a field taxonomy

The failure modes of MES specifications cluster into a consistent taxonomy. Recognizing them early is much cheaper than discovering them during implementation:

Failure mode Symptom Corrective discipline
The Feature Checklist Trap 300+ requirements, no linkage to use cases, every vendor checks most boxes. Rewrite around 15–25 operational use cases; derive requirements from each.
Must-Have Inflation >80 % of requirements marked Must-Have; no prioritization effectively exists. Named owner with authority to downgrade; target 60 % Must-Have ceiling.
Integration Underspecification 3–5 pages on integration in a 60-page document; no brownfield machine inventory. Expand technical section to 10–20 pages; include per-machine PLC inventory.
Prescribed Implementation Specification dictates technical implementation details (database, programming language, deployment platform). Strip all "how" — keep only "what" and "why"; let vendors propose how.
Acceptance Criteria Drift Requirements describe what system should do but not how "done" will be measured. Every Must-Have requirement gets a measurable acceptance criterion.
Regulatory Blind Spot Specification written before Oct 2024 with no NIS2/CRA/ISO 27001 treatment. Add first-class cybersecurity-and-compliance section with evidence requirements.
Scope Ambiguity "All plants eventually" — no clear Phase 1 / Phase 2 boundary. Explicit phased-rollout plan with named plants and named timelines.

How this fits into the SYMESTIC platform

SYMESTIC is the cloud-native MES platform the SYMESTIC implementation team deploys across automotive, metal-processing, food, building, and general manufacturing customers. The platform is designed to satisfy the MES requirements landscape described here — API-first integration via REST and OPC UA and native multi-site rollout with shared-template governance. The implementation approach follows these requirements-discipline principles: per-machine brownfield connectivity inventory during the pre-contract phase, measurable acceptance criteria per Must-Have requirement, and phased-rollout scoping with named go-live dates. For plants writing their first MES specification, a requirements workshop is usually better than a cold RFP; the workshop produces a better specification in less time than a cold-authored document because the vendor's engineering team participates in the brownfield and integration scoping before the specification is finalized. For plants that already have a finished specification, SYMESTIC responds to the standard RFP format and produces fit/gap documentation per requirement. Relevant product modules and supporting glossary material: production metrics, production control, production planning, alarms, process data; background on specific capabilities via process documentation, E2E traceability, change control, shop floor control, predictive quality, alarm management, industrial data historian, recipe management, and composable MES.

FAQ

What are MES requirements?
The functional, technical, organizational, and commercial criteria an MES must satisfy to fit a specific manufacturer's production processes, IT landscape, regulatory obligations, and strategy. They are typically assembled into a formal requirements specification (Pflichtenheft, Lastenheft, or SRS) that becomes the contractual and operational foundation for vendor selection, implementation planning, and acceptance.

What is the difference between an RFI, RFP, and RFQ?
An RFI (Request for Information) is an early-stage market scan used to build a vendor shortlist. An RFP (Request for Proposal) is a detailed specification against which shortlisted vendors submit binding proposals. An RFQ (Request for Quotation) is a narrow commercial exercise when the technical solution is already decided and only pricing is being negotiated. The RFP is where most requirements-specification work lives.

What reference frameworks structure MES functional requirements?
In the German-speaking market, VDI 5600 (blätter 1–7) is the definitive reference, structuring MES functions into ten task areas. Internationally, ISA-95 Part 3 defines the activity model for Level 3 operations management across production, quality, maintenance, and inventory. Most serious MES specifications reference one or more of these explicitly.

What is MoSCoW prioritization?
MoSCoW stands for Must-have, Should-have, Could-have, Won't-have. Must-have requirements are go-live-blocking; Should-have are important but not go-live-blocking; Could-have are desirable if low-cost; Won't-have are explicitly out of scope for this release. A healthy distribution puts roughly 60 % of requirements in Must-have, 20 % in Should-have, 15 % in Could-have, and 5 % in Won't-have. More than 80 % Must-have is Must-Have Inflation and means the specification is effectively unprioritized.

What is The Feature Checklist Trap?
The failure mode in which an MES specification becomes an exhaustive 300+ item enumeration of every conceivable function, with no linkage to actual business use cases, no prioritization, and no acceptance criteria. Vendors check most boxes, the specification cannot distinguish meaningful fit, and the checklist becomes worse than useless as a selection basis. The corrective discipline is to rewrite the specification around 15–25 concrete operational use cases and derive requirements from them.

What is Integration Underspecification?
The pattern in which the technical-and-integration-requirements section of an MES specification runs 3–8 pages (5–10 % of document volume) but drives 40–60 % of actual implementation effort and cost. Root cause: functional-requirements authors don't see integration; technical-requirements authors are often not the team writing the specification. Corrective discipline: expand the technical section to 10–20 pages with per-machine brownfield connectivity inventory, explicit ERP-integration scope, and first-class cybersecurity-and-compliance treatment.

How long should an MES requirements specification be?
Typically 40–60 pages for a mid-market multi-plant MES programme. Specifications materially longer than 80 pages usually suffer from prescribed implementation or the Feature Checklist Trap. Specifications materially shorter than 30 pages usually suffer from Integration Underspecification. The right length is whatever it takes to cover the nine standard sections (executive summary, scope, operational context, functional, technical/integration, non-functional, implementation, commercial, response template) with disciplined prioritization.

What cybersecurity requirements belong in an MES specification in 2026?
Three regulatory regimes now materially shape MES procurement: NIS2 Directive (EU, transposition deadline October 2024) with supply-chain-security obligations for essential/important entities; Cyber Resilience Act (progressive rollout through 2027) mandating cybersecurity requirements for products with digital elements sold into the EU; and ISO 27001 certification. Specifications drafted before October 2024 typically do not address these and need to be updated.

Should each plant have its own MES specification?
No. The working pattern is a shared core specification (typically 80–90 % of requirements) with per-plant annexes for genuinely local specifics (typically 10–20 %). A fully separate specification per plant produces vendor and implementation fragmentation; a single specification with no local flexibility produces rollout friction. The balance is a core-and-annex structure with named governance over what belongs in core vs. annex.

Is specifying functional requirements or integration requirements more important?
In practice, integration requirements and the brownfield connectivity inventory are more predictive of implementation success than functional-requirements detail. Most modern MES platforms cover the bulk of VDI 5600 / ISA-95 functionality adequately for most use cases; the differences that matter operationally are in how cleanly the MES integrates with the specific ERP, with the specific machine park, and with the specific regulatory environment. Plants that under-specify integration end up with MES functionality they cannot actually use because the data it needs doesn't flow into it.


Related: MES: definition, functions & benefits · OEE: definition, calculation & practice · MES software compared · OEE software · Composable MES (architecture frame) · Process documentation (ISA-95 baseline) · E2E traceability · Change control · Recipe management · Alarm management · Shop floor control · Predictive quality · Industrial data historian · Schedule adherence · On-Time Delivery · Rolled Throughput Yield · Scrap rate vs. rework rate · A3 problem solving · MDE (machine data acquisition) · BDE (production data acquisition) · Production metrics · Production control · Production planning · Alarms · Process data · Automotive · Metal processing · Food & beverage · For COOs & plant managers · For operational excellence. External references: VDI 5600 Blatt 1 (German MES functional standard) · ISA-95 standard committee (international activity model) · NAMUR (process-industry MES working groups) · NIS2 Directive portal (European Commission) · ISO/IEC 27001 (information security management).

Live demo30 minutes · free

See an MES against your requirement list

In a free 30-minute live demo a product expert shows the running platform along the requirements that matter most to you.

In use in over 20 countriesYanfengNidecCarcoustics

Potential analysis30 minutes · free

Your losses in euros, calculated with your figures

In a free 30-minute potential analysis we go through downtime, changeovers and scrap with you and turn the losses into euros using your own figures. No software demo.

In use in over 20 countriesYanfengNidecCarcoustics

About the author

MES Consultant & Project Lead · SYMESTIC

More than 30 years in industrial automation and machine connectivity, from Simatic S5 to OPC UA. Dipl.-Ing. in communications engineering.

  • Machine Data Collection (MDC)
  • Operational Data Collection
  • Machine Connectivity
  • PLC Programming (S5 / S7 / TIA)

Updated