[{"data":1,"prerenderedAt":85},["ShallowReactive",2],{"legacy:product\u002Fmes:en":3},{"id":4,"title":5,"description":6,"keywords":7,"author":8,"robots":9,"bodyClass":10,"image":11,"jsonld":12,"html":84},"product\u002Fmes","JEDP-MES Intelligent Manufacturing Execution System - JEDP Digital Platform","JEDP-MES Manufacturing Execution System: APS scheduling and dispatch, scan reporting and equipment monitoring, process quality and product traceability closed loop, with OEE \u002F MTBF statistics for a transparent, traceable and controllable shop floor.","JEDP, MES, manufacturing execution, code scanner, quality traceability, equipment OEE, digital platform, Lang Bowan","Shenzhen Langbowan Information Technology Co., Ltd.","index, follow","page-products","https:\u002F\u002Fwww.jedp.cn\u002Fres\u002Fimages\u002Fproduct\u002Fmes-slide6.webp",[13,30,58],{"@context":14,"@type":15,"itemListElement":16},"https:\u002F\u002Fschema.org","BreadcrumbList",[17,22,26],{"@type":18,"position":19,"name":20,"item":21},"ListItem",1,"Home","https:\u002F\u002Fwww.jedp.cn\u002F",{"@type":18,"position":23,"name":24,"item":25},2,"Products","https:\u002F\u002Fwww.jedp.cn\u002Fproducts",{"@type":18,"position":27,"name":28,"item":29},3,"JEDP-MES Smart Manufacturing Execution","https:\u002F\u002Fwww.jedp.cn\u002Fproduct\u002Fmes",{"@context":14,"@type":31,"@id":32,"name":28,"applicationCategory":33,"applicationSubCategory":34,"operatingSystem":35,"inLanguage":36,"description":6,"url":29,"provider":40,"isPartOf":42,"offers":44,"featureList":51},"SoftwareApplication","https:\u002F\u002Fwww.jedp.cn\u002Fproduct\u002Fmes#software","BusinessApplication","Manufacturing Execution System","Web (browser access; SaaS multi-tenant, private deployment assessed by scenario)",[37,38,39],"zh-CN","zh-TW","en",{"@id":41},"https:\u002F\u002Fwww.jedp.cn\u002F#organization",{"@id":43},"https:\u002F\u002Fwww.jedp.cn\u002F#software",{"@type":45,"url":46,"availability":47,"priceSpecification":48},"Offer","https:\u002F\u002Fwww.jedp.cn\u002Fcontact?from=mes","https:\u002F\u002Fschema.org\u002FInStock",{"@type":49,"priceCurrency":50},"PriceSpecification","CNY",[52,53,54,55,56,57],"Scheduling & Dispatch: APS \u002F Limited capacity provides executable daily\u002Fweekly scheduling; authorization for inserting or changing orders is recorded. When completeness is not met, it should be blocked or explicitly noted as an exception, to avoid the achievement rate being distorted by 'the plan looks good, but everything is changed on site.'","Execution & Monitoring: Barcodes \u002F RFID are used to collect the start and completion of key work steps, personnel, output, and process parameters; Kanban and Andon expose abnormalities. Collection points are placed where the status actually changes, rather than scanning more for the sake of data.","In-process Quality Management: First-piece inspection, routine inspection, sampling inspection, and OQC enter the execution chain; the defect database and non-conforming rework\u002Fscrap\u002Fquarantine form a closed loop. Quality results serve traceability and improvement, rather than creating another pass rate sheet at the end of the month.","Product Traceability: Batch\u002Fserial traceability of raw materials, processes, quality inspection, and delivery, with bidirectional positioning of people, machines, and materials. The goal is to advance from the 'batch level' to the 'station level,' supporting customer complaints and recall time requirements.","Equipment & OEE: Equipment ledger, inspection and maintenance, and repair work orders are linked to shutdowns; OEE is broken down into availability, performance, and quality rates. Minor stoppages and reason codes can be managed to avoid having only a single comprehensive score that feels unmatched.","Process & WIP Logistics: SOP \u002F Mistake-proofing and process key points are pushed according to work steps; material calling and delivery and shortage warning are connected to WMS \u002F supply. Make in-process logistics a constraint for plan achievement, rather than temporary material urging on site.",{"@context":14,"@type":59,"@id":60,"mainEntity":61},"FAQPage","https:\u002F\u002Fwww.jedp.cn\u002Fproduct\u002Fmes#faq",[62,68,72,76,80],{"@type":63,"name":64,"acceptedAnswer":65},"Question","How are scheduling and dispatching implemented in JEDP-MES?",{"@type":66,"text":67},"Answer","APS produces executable daily\u002Fweekly 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.",{"@type":63,"name":69,"acceptedAnswer":70},"What data can be collected by scanning the code for reporting work?",{"@type":66,"text":71},"Barcode \u002F 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.",{"@type":63,"name":73,"acceptedAnswer":74},"How can process quality management be implemented?",{"@type":66,"text":75},"MES focuses on workstation-side process inspection (first article, patrol inspection, sampling inspection) and the linkage of nonconformance rework\u002Fisolation, and SPC warnings can be enabled by scope. When combined with JEDP-QMS, inspection standards, defect library, CAPA\u002F8D, and incoming\u002Ffinal 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.",{"@type":63,"name":77,"acceptedAnswer":78},"What level of granularity can tracing locate?",{"@type":66,"text":79},"Lot \u002F 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.",{"@type":63,"name":81,"acceptedAnswer":82},"How to calculate equipment management and OEE?",{"@type":66,"text":83},"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.","\u003Csection class=\"product-detail-section page-section\">\n    \u003Cdiv class=\"detail-container\">      \u003Cnav class=\"breadcrumb\" aria-label=\"Breadcrumb\">\n        \u003Ca href=\"\u002F\">Home\u003C\u002Fa>\n        \u003Cspan class=\"breadcrumb-sep\">\u002F\u003C\u002Fspan>\n        \u003Ca href=\"\u002Fproducts\">Products\u003C\u002Fa>\n        \u003Cspan class=\"breadcrumb-sep\">\u002F\u003C\u002Fspan>\n        \u003Cspan>MES\u003C\u002Fspan>\n      \u003C\u002Fnav>\n      \u003Cdiv class=\"product-detail\">\n        \u003Cdiv class=\"detail-header\">\n          \u003Cdiv class=\"detail-icon\">\u003Ci class=\"fas fa-cogs\">\u003C\u002Fi>\u003C\u002Fdiv>\n          \u003Cdiv>\n            \u003Ch1>JEDP-MES Smart Manufacturing Execution\u003C\u002Fh1>\n            \u003Cp class=\"detail-subtitle\">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.\u003C\u002Fp>\n          \u003C\u002Fdiv>\n        \u003C\u002Fdiv>\n\n        \u003Cdiv class=\"detail-content\">\n                    \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Solution Positioning\u003C\u002Fh2>\n            \u003Cp class=\"detail-lead\">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\u002Fserial traceability, equipment checks and OEE—welding plan–kitting–dispatch–feedback into a manageable execution chain. With JEDP-QMS, standards, CAPA, and IQC\u002FOQC evidence stay in QMS.\u003C\u002Fp>\n            \u003Cp class=\"detail-lead\">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.\u003C\u002Fp>\n          \u003C\u002Fdiv>\n\u003Cdiv class=\"detail-section\">\n            \u003Ch2>Where It Fits\u003C\u002Fh2>\n            \u003Cul class=\"pain-list\">\n              \u003Cli>APS \u002F The scheduling is very good, but on-site frequent reassignments due to kit readiness, model changes, and urgent orders cause the plan fulfillment rate to be distorted, making it difficult for management to see the real constraints.\u003C\u002Fli>\n              \u003Cli>Paper-based or delayed reporting, with progress, output, and abnormalities not transparent; incorrect placement of collection points leads to 'data in the system still being inaccurate'\u003C\u002Fli>\n              \u003Cli>Process inspections and nonconformities are scattered across forms, SPC and the defect database have not been integrated into the execution chain, and quality relies on post-statistical analysis, making it difficult to close the loop.\u003C\u002Fli>\n              \u003Cli>Traceability only reaches the batch number and cannot trace to the workstation, personnel, materials, or methods; equipment downtime and OEE definitions are not consistent, making it impossible to align improvement meetings\u003C\u002Fli>\n            \u003C\u002Ful>\n          \u003C\u002Fdiv>\n          \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Core Process\u003C\u002Fh2>\n            \u003Col class=\"process-flow-steps\">\n              \u003Cli>APS Scheduling\u003C\u002Fli>\n              \u003Cli>Kit Check & Dispatch\u003C\u002Fli>\n              \u003Cli>Scan Reporting\u003C\u002Fli>\n              \u003Cli>In-process Quality\u003C\u002Fli>\n              \u003Cli>Traceability & Closeout\u003C\u002Fli>\n            \u003C\u002Fol>\n          \u003C\u002Fdiv>\n          \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Core Capabilities\u003C\u002Fh2>\n            \u003Cul class=\"capability-list\">\n              \u003Cli>\u003Cstrong>Scheduling & Dispatch\u003C\u002Fstrong>\u003Cspan>APS \u002F Limited capacity provides executable daily\u002Fweekly scheduling; authorization for inserting or changing orders is recorded. When completeness is not met, it should be blocked or explicitly noted as an exception, to avoid the achievement rate being distorted by 'the plan looks good, but everything is changed on site.'\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Execution & Monitoring\u003C\u002Fstrong>\u003Cspan>Barcodes \u002F RFID are used to collect the start and completion of key work steps, personnel, output, and process parameters; Kanban and Andon expose abnormalities. Collection points are placed where the status actually changes, rather than scanning more for the sake of data.\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>In-process Quality Management\u003C\u002Fstrong>\u003Cspan>First-piece inspection, routine inspection, sampling inspection, and OQC enter the execution chain; the defect database and non-conforming rework\u002Fscrap\u002Fquarantine form a closed loop. Quality results serve traceability and improvement, rather than creating another pass rate sheet at the end of the month.\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Product Traceability\u003C\u002Fstrong>\u003Cspan>Batch\u002Fserial traceability of raw materials, processes, quality inspection, and delivery, with bidirectional positioning of people, machines, and materials. The goal is to advance from the 'batch level' to the 'station level,' supporting customer complaints and recall time requirements.\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Equipment & OEE\u003C\u002Fstrong>\u003Cspan>Equipment ledger, inspection and maintenance, and repair work orders are linked to shutdowns; OEE is broken down into availability, performance, and quality rates. Minor stoppages and reason codes can be managed to avoid having only a single comprehensive score that feels unmatched.\u003C\u002Fspan>\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Process & WIP Logistics\u003C\u002Fstrong>\u003Cspan>SOP and error-proofing follow the operation. Material calls and shortages connect to WMS. A route cannot be reported complete if a step was skipped, and work instructions are issued to the station and checked by barcode.\u003C\u002Fspan>\u003C\u002Fli>\n            \u003C\u002Ful>\n          \u003C\u002Fdiv>\n          \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Scope of functions\u003C\u002Fh2>\n            \u003Cp class=\"detail-lead\">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.\u003C\u002Fp>\n            \u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Core Capabilities\u003C\u002Fth>\u003Cth>Modules in scope\u003C\u002Fth>\u003Cth>Rule advance\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Scheduling & Dispatch\u003C\u002Ftd>\u003Ctd>Work orders, daily and weekly schedules, kit checks, and logged rescheduling\u003C\u002Ftd>\u003Ctd>Incomplete kitting blocks dispatch, or leaves an explicit exception.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Execution & Monitoring\u003C\u002Ftd>\u003Ctd>Dispatch, reporting, WIP, and barcodes\u003C\u002Ftd>\u003Ctd>A station pass can report completion. A skipped step cannot close the job.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>In-process Quality Management\u003C\u002Ftd>\u003Ctd>First-article, patrol, sampling, and nonconforming quarantine\u003C\u002Ftd>\u003Ctd>The operation triggers inspection, and a failure creates a hold. Standards and CAPA stay in QMS.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Product Traceability\u003C\u002Ftd>\u003Ctd>Lots, serials, stations, and traced components\u003C\u002Ftd>\u003Ctd>A key part must be scanned before the job can pass the station.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Equipment & OEE\u003C\u002Ftd>\u003Ctd>Equipment register, inspection, maintenance, repair, and the three OEE rates\u003C\u002Ftd>\u003Ctd>An expired maintenance plan creates a repair order.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Process & WIP Logistics\u003C\u002Ftd>\u003Ctd>Lines and stations, routings, work instructions, material calls, and issue or return\u003C\u002Ftd>\u003Ctd>Line stock below the safety level calls material. The shortage clears only after delivery is written back.\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n          \u003C\u002Fdiv>\n          \u003Cdiv class=\"detail-section\">Solution Snapshot\u003C\u002Fdiv>\n          \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Platform Boost\u003C\u002Fh2>\n            \u003Cdiv class=\"platform-boost\">\n              \u003Carticle>\u003Ch3>AI Agents\u003C\u002Fh3>\u003Cp>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.\u003C\u002Fp>\u003C\u002Farticle>\n              \u003Carticle>\u003Ch3>Reports and dashboards\u003C\u002Fh3>\u003Cp>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.\u003C\u002Fp>\u003C\u002Farticle>\n              \u003Carticle>\u003Ch3>Multi-language\u003C\u002Fh3>\u003Cp>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.\u003C\u002Fp>\u003C\u002Farticle>\n              \u003Carticle>\u003Ch3>Multi-tenant\u003C\u002Fh3>\u003Cp>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.\u003C\u002Fp>\u003C\u002Farticle>\n            \u003C\u002Fdiv>\n          \u003C\u002Fdiv>\n                              \u003Cdiv class=\"detail-section\">\n            \u003Ch2>Boundaries & Composition\u003C\u002Fh2>\n            \u003Cp class=\"detail-lead\">MES owns shop-floor execution, labor reporting, in-process quality, and station-level traceability; the master plan and cost settlement can stay with APS\u002FERP. Actuals write back to the plan, and the shop does not keep a second plan book.\u003C\u002Fp>\n            \u003Cp class=\"detail-lead\">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.\u003C\u002Fp>\n          \u003C\u002Fdiv>\n          \u003C!-- product-depth:BEGIN -->\n\u003Cdiv class=\"detail-section\">\n\n            \n            \n            \u003Ch2>Typical breakpoints\u003C\u002Fh2>\n\u003Cdiv class=\"table-scroll\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Breakpoint\u003C\u002Fth>\u003Cth>Common cause\u003C\u002Fth>\u003Cth>Control lever\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Gantt is visually appealing but does not assign tasks on site\u003C\u002Ftd>\u003Ctd>Plan not bound by completeness constraints\u003C\u002Ftd>\u003Ctd>Kit Verification + Dispatch Interception\u002FException\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Missing processes are still reported as completed\u003C\u002Ftd>\u003Ctd>The route does not require passing through stations\u003C\u002Ftd>\u003Ctd>Process route anti-skipping station + Collection and verification\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Tracing can only go back to the production date\u003C\u002Ftd>\u003Ctd>Key component not scanned and bound\u003C\u002Ftd>\u003Ctd>Tracking Item List + Workstation Scan\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>OEE only has one total score\u003C\u002Ftd>\u003Ctd>The reason for shutdown is not standardized\u003C\u002Ftd>\u003Ctd>Three-rate split + Cause code management\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Process defects do not proceed to CAPA\u003C\u002Ftd>\u003Ctd>MES\u002FQMS responsibilities not defined\u003C\u002Ftd>\u003Ctd>Nonconforming triggers QMS 8D MES isolation\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>The requested materials have arrived at the workstation but are still missing from the account\u003C\u002Ftd>\u003Ctd>WMS delivery not written back\u003C\u002Ftd>\u003Ctd>Delivery scanning closed loop + Line-side inventory\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>The SOP version is inconsistent with the on-site version\u003C\u002Ftd>\u003Ctd>WI is not bound to a workstation\u003C\u002Ftd>\u003Ctd>Workstation SOP Release + Barcode Verification\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n            \u003Ch2>Responsibility and Integration\u003C\u002Fh2>\n            \u003Cp class=\"detail-lead\">\u003Cstrong>Primary Responsibility:\u003C\u002Fstrong>MES has workshop execution, job dispatch and reporting, work-in-progress status, workstation-level traceability, material call and delivery execution, and equipment\u002FOEE operation data; the master production plan and financial costs can be divided in ERP\u002FAPS, and MES writes back actual performance.\u003C\u002Fp>\n            \u003Cp class=\"detail-lead\">\u003Cstrong>Integration Direction (Typical):\u003C\u002Fstrong>ERP ←→ Orders\u002FWork Orders\u002FInbound Feedback; PLM → BOM\u002FProcess; MES → WMS initiates material issuance\u002Freturns\u002Fdelivery, WMS main inventory ledger updates; QMS ↔ Process inspection triggers and conclusions (inspection standards, CAPA\u002F8D primarily managed by QMS); MES → SRM material shortage\u002Fcompletion requirements (optional). When MES is deployed independently, workshop inspections can be enabled, but it does not replace the QMS evidence chain.\u003C\u002Fp>\n            \u003Ch2>Promote phased implementation and acceptance\u003C\u002Fh2>\n            \u003Cul class=\"accept-list\">\n              \u003Cli>\u003Cstrong>Phase One (Process and Reporting)\u003C\u002Fstrong>: Process route, work order release, job dispatch and reporting, and work-in-progress; demonstration of the key workstation collection point list\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Phase II (Logistics and Quality)\u003C\u002Fstrong>Material call and delivery integration with WMS; process inspection and division of responsibilities acceptance with QMS; defect isolation and work order status\u003C\u002Fli>\n              \u003Cli>\u003Cstrong>Phase Three (Scheduling and Equipment)\u003C\u002Fstrong>: APS\u002Fschedule adjustment traceability, OEE three rates and downtime reasons, batch\u002Fsequence limited-time backtracking drills\u003C\u002Fli>\n              \u003Cli>The reasons for plan completion and reassignment can be counted, and when the set of parts is not complete, dispatching can be intercepted or show explicit exceptions.\u003C\u002Fli>\n              \u003Cli>WI\u002FSOP version is bound to the workstation, and the correct documents are issued during model change\u003C\u002Fli>\n            \u003C\u002Ful>\n            \u003Ch2>When not to apply\u003C\u002Fh2>\n            \u003Cul class=\"pain-list\">\n              \u003Cli>Use MES to undertake the complete IATF document system and CAPA library — should combine with QMS or clarify the scope\u003C\u002Fli>\n              \u003Cli>Pursuing error-proofing without a process route — MBOM\u002Froute should be frozen before collection\u003C\u002Fli>\n              \u003Cli>Plans can be changed at any time without authorization — inserting orders and changing assignments must leave a record and affect the completeness commitment.\u003C\u002Fli>\n              \u003Cli>Equipment OEE is for display only, reason codes are not maintained — unable to support continuous improvement\u003C\u002Fli>\n            \u003C\u002Ful>\n          \u003C\u002Fdiv>\n          \n          \n          \u003C!-- product-depth:END -->\n\n\u003Cdiv class=\"detail-section\">\n            \u003Ch2>Related Practices\u003C\u002Fh2>\n            \u003Cp class=\"detail-lead\">MES acceptance looks at collection points, completeness constraints, and traceability depth; it compares and combines boundaries and primary responsibilities with warehousing and quality cases.\u003C\u002Fp>\n            \u003Cul class=\"related-cases\">\n              \u003Cli>Supply-chain manufacturing: plan to shop-floor execution\u003C\u002Fli>\n              \u003Cli>Combined Quality: From Incoming Materials to Customer Complaint Closure (QMS Main Evidence)\u003C\u002Fli>\n              \u003Cli>Product: QMS inspection standards, CAPA\u002F8D and main responsibility for system evidence\u003C\u002Fli>\n              \u003Cli>Combined Warehousing: Material Calling Distribution and Account Reality\u003C\u002Fli>\n              \u003Cli>Scan reporting is live but data is still wrong—put capture points where status actually changes\u003C\u002Fli>\n              \u003Cli>Resources: Workshop Reporting and Process Traceability Self-Test\u003C\u002Fli>\n            \u003C\u002Ful>\n          \u003C\u002Fdiv>\n                                                                                                                                            \u003C!-- related-insights:BEGIN -->\n          \u003Cdiv class=\"detail-section\" id=\"related-insights\">\n            \u003Ch2>Related insights\u003C\u002Fh2>\n            \u003Cul class=\"related-cases\">\n              \u003Cli>Rework raised but progress still shows complete? Scrap and rework must enter the WO state machine—not only yield\u003C\u002Fli>\n              \u003Cli>Andon is on but nobody owns the stop? Downtime codes must close with the shift—not as “Other” later\u003C\u002Fli>\n              \u003Cli>Traceability cannot stop at lot ID—three gates from lot-level to station-level\u003C\u002Fli>\n            \u003C\u002Ful>\n            \u003Cp class=\"related-more\">\u003Ca href=\"\u002Finsights\">Browse all insights\u003C\u002Fa> · \u003Ca href=\"\u002Fresources?from=mes#selftest\">Take an online self-test\u003C\u002Fa> · \u003Ca href=\"\u002Fresources?from=mes#kits\">Download kits\u003C\u002Fa> · \u003Ca href=\"\u002Fresources?from=mes#demo\">Book a demo\u003C\u002Fa>\u003C\u002Fp>\n          \u003C\u002Fdiv>\n          \u003C!-- related-insights:END -->\n          \u003Cdiv class=\"product-detail-cta scroll-reveal\">\n            \u003Ca href=\"\u002Fproducts\" class=\"btn btn-outline\">Back to product solutions\u003C\u002Fa>\n            \u003Ca href=\"\u002Fresources?from=mes#selftest\" class=\"btn btn-outline\">Take a self-test\u003C\u002Fa>\n            \u003Ca href=\"\u002Fresources?from=mes#kits\" class=\"btn btn-ghost\">Download kits\u003C\u002Fa>\n            \u003Ca href=\"\u002Fresources?from=mes#demo\" class=\"btn btn-ghost\">Book a demo\u003C\u002Fa>\n            \u003Ca href=\"\u002Fcontact?from=mes\" class=\"btn\">Get a demo\u003C\u002Fa>\n          \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n      \u003C\u002Fdiv>\n    \u003C\u002Fdiv>\n  \u003C\u002Fsection>\n\n  \u003C!-- GEO:faq-visible:BEGIN · 由 scripts\u002Finject_geo.py 生成，请勿手改 -->\n  \u003Csection class=\"contact-faq page-section\" id=\"faq\">\n    \u003Ch2 class=\"section-title\">FAQ\u003C\u002Fh2>\n    \u003Cp class=\"section-subtitle\">For common questions about the capabilities on this page, take a look here first; if you still have questions, you can contact us.\u003C\u002Fp>\n    \u003Cdiv class=\"faq-list\">\n        \u003Cdetails class=\"faq-item\" open>\n          \u003Csummary>How are scheduling and dispatching implemented in JEDP-MES?\u003C\u002Fsummary>\n          \u003Cp>APS produces executable daily\u002Fweekly 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.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>What data can be collected by scanning the code for reporting work?\u003C\u002Fsummary>\n          \u003Cp>Barcode \u002F 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.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>How can process quality management be implemented?\u003C\u002Fsummary>\n          \u003Cp>MES focuses on workstation-side process inspection (first article, patrol inspection, sampling inspection) and the linkage of nonconformance rework\u002Fisolation, and SPC warnings can be enabled by scope. When combined with JEDP-QMS, inspection standards, defect library, CAPA\u002F8D, and incoming\u002Ffinal 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.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>What level of granularity can tracing locate?\u003C\u002Fsummary>\n          \u003Cp>Lot \u002F 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.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>How to calculate equipment management and OEE?\u003C\u002Fsummary>\n          \u003Cp>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.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n    \u003C\u002Fdiv>\n  \u003C\u002Fsection>\n  \u003C!-- GEO:faq-visible:END -->\n\n  \n  \n\n  \n  \n  \n  \u003C!-- GEO:software-app:BEGIN · 由 scripts\u002Finject_geo.py 生成，请勿手改 -->\n  \n  \u003C!-- GEO:software-app:END -->\n  \u003C!-- GEO:faq:BEGIN · 由 scripts\u002Finject_geo.py 生成，请勿手改 -->\n  \n  \u003C!-- GEO:faq:END -->",1793937990180]