MAISUI MES connects ERP plans to real shop-floor execution: it schedules and dispatches work, captures production and quality data in real time, and builds unit-level genealogy for traceability.
Key facts at a glance
- Category
- Manufacturing execution system (MES), Level 3 of ISA-95
- Primary users
- Production planning, supervisors, operators, quality engineers
- Core scope
- Scheduling, dispatching, data collection, quality, OEE, genealogy
- Reference model
- ISA-95 / IEC 62264 manufacturing operations management
- Integrates with
- ERP, WMS, PLC/SCADA, MS7, station printers and scanners
What is MES Smart Manufacturing System?
A manufacturing execution system (MES) manages production operations in real time between the business planning layer and the shop floor. In the ISA-95 / IEC 62264 model it sits at Level 3, alongside other manufacturing operations management functions such as quality and warehouse management.
Where ERP answers “what should we make”, MES answers “what is happening now”: which order is running on which line, which materials were consumed, which units passed or failed, how much scrap was produced, and where a specific unit is in the process. MES is therefore the system of record for production execution, genealogy and shop-floor quality data.
Core modules and functions
| Module | What it covers |
|---|---|
| Production scheduling | Finite or infinite scheduling by line, work centre and shift, with changeover and priority rules. |
| Work order release and dispatching | Split, release and dispatch orders to stations with routings, instructions and material lists. |
| Shop-floor data collection | Barcode, RFID, PDA and machine signals capture start, stop, quantities, scrap and downtime. |
| WIP and material tracking | Real-time location and status of work-in-process, material issue and consumption backflush. |
| Quality management | In-process checks, sampling plans, non-conformance records, rework and hold disposition. |
| Equipment and OEE | Run time, downtime reasons, performance and quality losses, OEE by line and shift. |
| Genealogy and traceability | Unit- or batch-level links between materials, process parameters, operators and test results. |
| Dashboards and reporting | Andon, production attainment, yield, scrap, cycle time and shift handover reports. |
Operational problems it addresses
- Paper travelers: routing sheets are filled by hand, lost or illegible, and data is entered days later.
- Invisible WIP: nobody can say how many units are between operations without walking the floor.
- Late or missed orders: bottlenecks are discovered at the end of the shift, not when they occur.
- Quality records in filing cabinets: a customer complaint takes days to investigate.
- OEE guesswork: downtime reasons are estimated rather than measured, so improvement projects target the wrong losses.
- Recall scope unknown: when a defect appears, the affected units cannot be identified quickly.
How it works
- Receive production orders from ERP with BOM and routing data.
- Schedule orders to lines and shifts, respecting material and capacity constraints.
- Dispatch operations to workstations with instructions and material requirements.
- Operators scan material and start/complete operations; machines report signals where available.
- Capture in-process quality results, scrap and downtime reasons.
- Build genealogy records that link each unit or batch to its inputs and process data.
- Report actual quantities, scrap and quality results back to ERP and update dashboards.
Integration with other systems
- ERP: production orders, BOMs and routings in; actual quantities, scrap and quality results out.
- WMS: material issue, line-side replenishment and finished-goods receipt.
- Equipment: PLC, SCADA and sensors through OPC UA or vendor interfaces; printers and scanners at stations.
- MS7: serial number generation, printing and unit-level traceability for one-item-one-code requirements.
- Quality systems: non-conformance, CAPA and calibration records where a dedicated QMS is in use.
Implementation phases
| Phase | Main activities | Outputs |
|---|---|---|
| 1. Process mapping | Define routings, work centres, data capture points and quality gates. | To-be process and data model |
| 2. Data preparation | Materials, BOMs, routings, equipment list, operators and reason codes. | Validated master data |
| 3. Configuration and integration | Configure workflows, screens, labels and interfaces to ERP and equipment. | Tested MES environment |
| 4. Pilot line | Run one line in parallel with paper records; compare data and fix gaps. | Pilot results and sign-off |
| 5. Rollout and stabilization | Extend line by line, train operators and establish daily data review. | Live lines, operating routine |
Selection checklist
- Is production discrete, process or mixed, and does the MES model your routings?
- Which data must be captured manually, and which can come from machines?
- How will operators interact with the system: station PC, tablet, PDA or scanner?
- Which ERP integration is mandatory: orders in, confirmations out, or both?
- What quality records must be retained, and for how long?
- Does the design support offline or degraded operation?
- Who reviews production and quality data daily after go-live?
Frequently asked questions
Is MES the same as ERP?
No. ERP plans business resources at Level 4 of ISA-95; MES manages manufacturing operations at Level 3. ERP creates a production order and asks for a quantity on a date; MES decides the sequence, dispatches work to stations, captures what actually happened and reports the real quantity, scrap and quality data back.
Do small factories need MES?
If production is simple, a single line and quality records are light, an ERP with basic production reporting may be enough. MES pays off when routing is multi-step, work-in-process is hard to see, quality data must be retained per unit or batch, or customers require documented traceability.
Should data be collected with barcodes or RFID?
Barcode is usually the lowest-cost starting point for material, WIP and labour tracking. RFID suits automated reading, reusable containers or harsh environments where labels are hard to scan. Many plants start with barcode and add RFID at selected points.
Can MES run offline?
Shop-floor networks are not always reliable. A practical design buffers transactions on the device or edge server and synchronizes when the connection returns. The amount of offline capability needed is a design decision that should be made during process mapping.
How does MES support traceability?
MES records the genealogy of each unit or batch: which materials, equipment, operator, process parameters and quality results were involved. Combined with serialization (MS7), this makes it possible to trace a finished unit back to its inputs and forward to its customers.