AI Agents
Design-time speeds up labor-report pages and process and exception flows. Runtime can query and complete reviews within that person's own permissions through the API; it does not change dispatch or production master data directly.
Ensure that the production schedule can accommodate complete sets and dispatching, and let work reporting be done on the 'actual changes' of the process steps — with on-site transparency, quality, and traceability closed-loop, rather than just another beautiful Gantt chart.
At shift close, reported qty, planned qty, and QC qty each tell a different story—wrong capture points, freely editable dispatch, and traceability that stops outside the station make more scans make more mess. JEDP-MES targets discrete shops: APS dispatch, scan reporting and process monitoring, station QC and NCR linkage, lot/serial traceability, equipment checks and OEE—welding plan–kitting–dispatch–feedback into a manageable execution chain. With JEDP-QMS, standards, CAPA, and IQC/OQC evidence stay in QMS.
Execution has to block starts on an empty kit and verbal rush orders: dispatch, reporting, and downtime share one execution chain, and the Gantt cannot float free of the floor. Combines with WMS call-off, QMS in-process quality, and SRM shortage plans; multi-plant isolation and multilingual shop terminals.
The table lists the modules under the six capabilities, and how a rule advances the next document. Approval, judgment, and write-off stay with a person.
| Core Capabilities | Modules in scope | Rule advance |
|---|---|---|
| Scheduling & Dispatch | Work orders, daily and weekly schedules, kit checks, and logged rescheduling | Incomplete kitting blocks dispatch, or leaves an explicit exception. |
| Execution & Monitoring | Dispatch, reporting, WIP, and barcodes | A station pass can report completion. A skipped step cannot close the job. |
| In-process Quality Management | First-article, patrol, sampling, and nonconforming quarantine | The operation triggers inspection, and a failure creates a hold. Standards and CAPA stay in QMS. |
| Product Traceability | Lots, serials, stations, and traced components | A key part must be scanned before the job can pass the station. |
| Equipment & OEE | Equipment register, inspection, maintenance, repair, and the three OEE rates | An expired maintenance plan creates a repair order. |
| Process & WIP Logistics | Lines and stations, routings, work instructions, material calls, and issue or return | Line stock below the safety level calls material. The shortage clears only after delivery is written back. |
Design-time speeds up labor-report pages and process and exception flows. Runtime can query and complete reviews within that person's own permissions through the API; it does not change dispatch or production master data directly.
Progress, OEE three rates, Andon, and first-pass yield can be displayed on the workshop board and management cockpit; downtime reason codes and work reporting share the same source, and improvement meetings can align with the same set of data.
Overseas workshop terminals and work instructions can switch languages; key process step prompts, error-proofing prompts, and exception buttons are prioritized for translation to ensure consistent execution by foreign teams.
Multi-factory manufacturing execution data isolation operation; the group can view aggregated progress and OEE under authorization, while on-site factory permissions are still tailored according to the organization, and cross-factory work reassignment is prohibited.
MES owns shop-floor execution, labor reporting, in-process quality, and station-level traceability; the master plan and cost settlement can stay with APS/ERP. Actuals write back to the plan, and the shop does not keep a second plan book.
Touchpoints: WMS for call-off and shortages, QMS for in-process and final inspection and nonconformances, SRM for shortage-driven purchasing. An interface failure has to be visible on the shop floor, not only in the integration log.
| Breakpoint | Common cause | Control lever |
|---|---|---|
| Gantt is visually appealing but does not assign tasks on site | Plan not bound by completeness constraints | Kit Verification + Dispatch Interception/Exception |
| Missing processes are still reported as completed | The route does not require passing through stations | Process route anti-skipping station + Collection and verification |
| Tracing can only go back to the production date | Key component not scanned and bound | Tracking Item List + Workstation Scan |
| OEE only has one total score | The reason for shutdown is not standardized | Three-rate split + Cause code management |
| Process defects do not proceed to CAPA | MES/QMS responsibilities not defined | Nonconforming triggers QMS 8D MES isolation |
| The requested materials have arrived at the workstation but are still missing from the account | WMS delivery not written back | Delivery scanning closed loop + Line-side inventory |
| The SOP version is inconsistent with the on-site version | WI is not bound to a workstation | Workstation SOP Release + Barcode Verification |
Primary Responsibility:MES has workshop execution, job dispatch and reporting, work-in-progress status, workstation-level traceability, material call and delivery execution, and equipment/OEE operation data; the master production plan and financial costs can be divided in ERP/APS, and MES writes back actual performance.
Integration Direction (Typical):ERP ←→ Orders/Work Orders/Inbound Feedback; PLM → BOM/Process; MES → WMS initiates material issuance/returns/delivery, WMS main inventory ledger updates; QMS ↔ Process inspection triggers and conclusions (inspection standards, CAPA/8D primarily managed by QMS); MES → SRM material shortage/completion requirements (optional). When MES is deployed independently, workshop inspections can be enabled, but it does not replace the QMS evidence chain.
MES acceptance looks at collection points, completeness constraints, and traceability depth; it compares and combines boundaries and primary responsibilities with warehousing and quality cases.
For common questions about the capabilities on this page, take a look here first; if you still have questions, you can contact us.
APS produces executable daily/weekly dispatch. Incomplete kits should block dispatch or be an explicit exception; inserts and re-dispatch need authorization with a trail. A Gantt chart without kit constraints is a wish list, and plan attainment will not match the floor.
Barcode / RFID capture start, finish, people, output, and process parameters; boards show progress, equipment status, and Andon. Scan points must sit where the real status changes—do not add scans just to raise the scan rate.
MES focuses on workstation-side process inspection (first article, patrol inspection, sampling inspection) and the linkage of nonconformance rework/isolation, and SPC warnings can be enabled by scope. When combined with JEDP-QMS, inspection standards, defect library, CAPA/8D, and incoming/final inspection evidence are primarily managed by QMS, while MES is responsible for triggering and writing back results to workshop execution; when MES is deployed independently, workshop-side inspection can be enabled, but it does not replace the system-level CAPA evidence chain.
Lot / serial links raw material, process, inspection, and shipping for forward and reverse people-machine-material-method localization. The goal advances from lot level to station level; if critical parts are not scanned and bound, you only reach daily output—finish the tracked-item list first.
OEE splits into availability, performance, and quality; downtime reason codes must be governed. A single composite score that does not match the shop floor cannot drive improvement. Inspections, maintenance work orders, and preventive work share one ledger with reported downtime.