Field notes on manufacturing digitalization—no buzzwords, just judgment criteria、breakpoint checklistsANDgo-live sequence。Each piece starts from one shop-floor breakpoint, with the rule and the counterexample in the body.
59 articles · 10 topics, all practical notes you can put to work
If last year's conclusion is only basically conforming, it cannot be rechecked the next year. Nonconformances should enter supplier status, performance, and order constraints, with JEDP-QMS and JEDP-SRM sharing the same record.
Read articleOpening the work instruction at the station does not prove the bolt was tightened to specification. JEDP-MES issues the revision to the station, checks material and parameters, and blocks an out-of-tolerance result while keeping the measured value.
Read articleCost of quality loses credibility not because it is calculated wrong, but because pieces are missing: rework hours, downtime awaiting disposition, re-inspection and complaint travel have no document entry point. This article gives the four-category collection basis, the account table, the allocation rules, the three dashboards and six demonstrable acceptance checks.
Read articleA part number only answers whether this is the same interchangeable item. Supplier, customer, lot and location do not go into the number. If material or the drawing changes so the parts are no longer interchangeable, issue a new number. Freeze new duplicates first, then deactivate the old number. Historical documents keep their number.
Read articleAI query is not a new data exit: the runtime agent trims rows and columns by the permission groups configured when the list page was published - applicable people, data scope and field permissions share the same source as the list page, and out-of-scope requests must be rejected and logged. This article explains how permission groups are resolved and where the fallback lands, risk tiers for export and write actions, a rollout order and six demonstrable acceptance checks.
Read articleEnterprise AI usually stalls on four gaps: scattered data, no domain knowledge, no foothold in the process, and unclear economics. Each comes with questions you can check on the spot plus a recommended order, and with guidance on when to hold off, so data problems are not blamed on the model.
Read articleMost invoice-goods disputes are not due to calculation errors, but because invoices are issued before reconciliation. The reconciliation statement should be compiled by shipping/settlement, and only after the customer confirms it (through a portal or a light link) should it enter the invoicing pool; standardized invoicing applications should be connected to finance, with customers and internal staff sharing the same shipping—reconciliation—invoicing status.
Read articleSalary disputes often arise because attendance, piecework, and subsidy inputs are not reliable. Starting from the paycheck without attaching supporting documents, it explains how input freezing, trial calculation review, payment locking, and permission separation form a trusted channel, and how it connects with the official performance results.
Read articleThe root cause of attendance disputes is that rules are passed down by word of mouth and anomalies are corrected manually. Starting from the end-of-month timesheet reconciliation on-site, it explains how shift rule configuration, anomaly classification deadlines, pre-salary confirmation and freezing, and organizational position switching form the minimal closed loop.
Read articleThe root cause of performance formalization is the disconnect between goals and business results, lack of process review, and results not being applied. Starting from the end-of-year form-filling scenario, it illustrates how goal setting, process review, calibration checkpoints, and result-based pay are linked into a closed loop within the EHR.
Read articleThe confusion in permissions after organizational adjustments is because multiple systems each maintain their own organizational tree. The fact that people still contact the old manager after the transfer order takes effect indicates how to implement the single source of authority, the effective date of appointments and removals, the boundaries of concurrent positions, secondments, proxies, and pre-onboarding permissions.
Read article"If 'completion' was never documented at the start of the project, the closing phase will only leave disputes over positions. Clearly write the evidence methods using four layers of standards: functional availability, data accuracy, user usability, and metric improvement, and provide scenario sampling, phased acceptance, the three contract matters, and the observation criteria for 30/60/90 days after launch."
Read articleThe in-transit and actual received amounts do not match. It is common that different segments are managed separately by the shipping plan, shipping details, dock occupancy, and posting feedback. Suppliers and the warehouse need to share the same set of statuses, and purchasing will no longer rely on screenshots to communicate.
Read articleROI debates often get stuck, mostly because the metrics aren't aligned. Starting from the project kickoff meeting, it involves providing four types of verifiable benefits—manpower, scrap rework, compliance audits, and cash delivery—seven potential cost omissions, the cost structure differences between base and custom, and how to honestly list items separately when they cannot be quantified.
Read articleCorporate AI failures are often due to unclear responsibilities. Starting from the 'one chat window does everything' approach, it illustrates the asymmetry between the cost of building systems and the cost of business judgment, why design and operation must have separate entry points, and how human-in-the-loop, traceability, and the three bottom lines can be implemented.
Read articleDealers and self-service ordering on the portal often fail due to unsynchronized available catalog, customer pricing, credit, and commit-to-promise. Clearly explain the portal boundaries, minimum order multiples, price matching, credit control, and delivery date notifications, as well as how orders enter internal fulfillment, to avoid manual entry via WeChat and over-selling that damages trust.
Read articleAcceptance disputes often erupt before payment, and the root cause is that milestones only have dates without evidence. Create an evidence package consisting of the deliverable list, checklists, three-state conclusions, and conditional leftover items, then align it with payment triggers and scope changes, moving disputes forward to the stage of standard alignment.
Read articleFailures at sea rarely stem from the list of features, but more from data boundaries, language types, and operational reach. Starting from incidents on delivery day, explain the six thresholds: tenant segmentation, data-level multilingual support, fallback for missing translations, time zone formats, compliant data residency, and nearby deployment, as well as scenarios unsuitable for multi-tenancy.
Read articleKey personnel overload is often overlooked because scheduling only assigns names without considering available work hours. Use calendars, availability percentages, and task estimates to calculate load rates, exposing conflicts during the planning period; roles and named individuals are layered, priority arbitration results are written back into plan changes, and included in program-level meetings.
Read articleIf only the quantities are changed for rework and scrapping, the progress, completeness, and cost will all be misleading. Nonconforming disposition must drive the work order status and the whereabouts of work-in-progress, and closure must be verified; when combined with QMS, isolate conclusions to write back to the execution chain.
Read articlePayment mismatches are usually due to the write-off granularity being at the customer level. Clearly explain the sequence: write-offs by invoice/order line, partial payments and allowance deductions formalized as documents, layered follow-up on overdue items, and then discuss automatic matching after the main chain of invoices and goods is verified.
Read articleWhen the manufacturing industry chooses a digital foundation, first set the benchmark before discussing the price. Use 8 questions that can be verified on the spot to cover modeling limits, process engine, data ownership, secondary development boundaries, multi-organization multi-tenant, internationalization, implementer capabilities, and exit costs, and provide a scoring sheet that can be used directly.
Read articleConsignment mess is rarely “too few counts”—ownership, consumable point, and invoice trigger were never written. Consumption, ownership transfer, and AP must share one event; both portals see the same available qty.
Read articleCost explosions after the fact occur because labor hours, procurement, and expenses each go their separate ways. By approaching from the perspective of the 'budget still sufficient' false surplus, it explains how from estimates to final accounts can be aggregated according to WBS/accounts, how provisional estimates and items in transit can eliminate false safety, and how to use ETC/EAC for weekly warnings rather than just looking at the percentage spent.
Read articleStockouts at picking locations are often caused by a disconnect between replenishment triggers and waves. Tasks are triggered based on minimum stock levels, occupying storage batches; waves require full preparation in advance or explicit exceptions; direct picking requires authorization for backwriting.
Read articleCommission disputes often arise due to dirty funnels, inconsistent revenue recognition standards, and uncoupling of expenses from business opportunities. First, freeze the events eligible for commission accrual and the reversal rules, then discuss tiered and behavior-based rewards; use parallel trial calculations to clarify differences and avoid verbally changing standards at the end of the month.
Read articleScope creep rarely occurs due to malice, but rather because verbal requests directly enter the plan. Starting from adding requirements on WeChat onsite, it explains how baseline freezing, the pending evaluation pool, progress/cost/risk impact assessment, and CCB-level approval can allow the completion rate to have a fixed denominator again, while being compatible with both waterfall and agile formats.
Read articleAndon failure is mostly due to call no-response time limit, optional reason code, and no verification on shutdown. Downtime must proceed from call → response → reason → shutdown into the shift, sharing the same source as OEE availability, restricting 'Others'.
Read articleChaotic returns are mostly due to disconnections in the four stages: RMA, receiving, quality inspection, and restocking. Returns need to be scheduled to occupy the platform, sorted according to reasons, locked before quality inspection, and restocking should clearly record the owner and batch. Piling first and recording later is prohibited.
Read articleTraceability depth is not an issue of the system function list, but a problem of collection points and document specifications. Starting from the time-limited review backtracking, it breaks down material batching, human-machine binding, time window and shipment mapping, as well as the acceptance method of completing forward and backward checks in one chain.
Read articleQuality claims never tie when claim, 8D, debit notice, and AP offset run apart. Bind claims to IQC/NCR and PO lines; put debit into auditable AP; close disputes with evidence.
Read articleThe discrepancies between accounts and actual inventory arise during daily receipt and dispatch, not from insufficient stocktaking. By approaching it from year-end full inventory fatigue, it explains how ABC and discrepancy rates distribute frequency, how storage locations/batches/material granularity are frozen, how reason codes drive corrective actions, and how blind counting, recounting, and adjustment permissions are separated.
Read articleDistortion in the closure rate is mostly because closing only changes the status. Starting from on-site audit sampling, provide the three essential controls for implementing measures, verifying effectiveness, and synchronizing documents, four methods for identifying padding, as well as the honest reading method for the three indicators of timely closure, effectiveness verification, and recurring issues.
Read articleThe on-time delivery rate being too high is mostly because the numerator and denominator have been redefined. Line-level OTIF, commitment date benchmarks, early windows, and nonconformities not counted in full quantity, and only when they are sourced the same as order confirmation, receipt, and incoming material judgment, can their ranking be considered in the share.
Read articleThe root cause of the OEE disputes is the inconsistency between planned production time, downtime classification, and first-pass yield count. Starting from the sense of 'something feels off,' break down availability, performance, quality, and points of water injection, explain micro-stops, ideal cycle time, cross-line benchmarking, as well as the implementation sequence of aligning MES data collection with shifts.
Read articleQuote-to-cash breaks when quote, contract, ship, invoice, and cash each run alone. Cover how price tiers and specials enter quote versions, contracts inherit effective price, shipments reference order lines, and invoice/cash apply back to lines.
Read articleIf the picking accuracy cannot improve, it is mostly due to overly large waves, similar items being adjacent, or the review only involving signing. First, classify according to error types, then adjust wave segmentation, location isolation, and dynamic review, and use the same inventory account for FIFO/batch verification to avoid disguising progress with inflated figures.
Read articleIncoming material inspection is not the end point for the quality department, but the starting point for supplier quality management. From pending inspections backlog, concession disputes, verbal corrections to 'evaluating is useless,' break down the task triggers, determine diversion, transmit exceptions, and return performance at four breakpoints, and explain how to connect with the full-process inspection of QMS, CAPA, and the supplier portal.
Read articleOutsourced reconciliation differences almost never stem from accounting errors, but rather from the lack of mutually recognized vouchers when the business occurs. Breaking it down to the document level according to five checkpoints—material issuance receipt, loss measurement, direct process delivery, rework scrap, and account period cutoff—illustrates how the SRM side firmly links confirmation, comparison, and payment processes.
Read articleThe root cause of inaccurate work reporting data is usually not that employees are uncooperative, but that the data collection point was chosen in the wrong location. How far the data is collected determines how deep the traceability, OEE, and work dispatch feedback can go; if the location is wrong, the subsequent links in the chain all break together.
Read articleThe registry becoming zombie-like is not due to a lack of forms, but a lack of owners, review dates, alerts, and closure evidence. Starting from the PMO regular meeting site, it explains how deviations get into the registry, how closures retain evidence, and how key projects first run through the rhythm.
Read articleThe system shows completion, but the site skips key processes — the problem often lies in the route not enforcing station stops or the SOP not being linked to the workstation. Starting from an after-the-fact customer complaint, it explains how key station gates, WI versions, and in-process change rules are incorporated into the execution chain.
Read articleIssuing a job offer and immediately activating the system as if the person is an active employee is a common high-risk practice. Pre-employment should follow a task checklist and minimum privileges, with the official permission package switched on the effective date of employment, and aligned with organizational position and attendance records.
Read articleFunnel distortion is often caused by stages being freely dragged and zombie opportunities not being cleared. Explain the evidence required for stage entry, rules for removing overdue items, weighted forecast calibration, and the sequence of discussing incentives and operational commitments only after hygiene standards are met.
Read article"The system shows it was sent, but the workstation says it wasn't seen" — this usually happens when the delivery isn't updated in the system or the line-side hasn't scanned it as received. Separate the process clearly into material requisition — picking — delivery — receiving closed loop, the three-part method for shortages, and the division of labor between MES/WMS master accounts, so that in-process logistics become a planning constraint.
Read articleThe most costly mistake in the warehouse is treating uninspected or nonconforming batches as available inventory. Follow inspection strategies according to the type of goods; items pending inspection cannot be picked. The QMS conclusion single-point drives shelving and wave availability. Rejected items follow return coordination to avoid mistakenly shipping frozen batches.
Read articleAfter the central warehouse, workshop warehouse, and outsourced warehouse run in parallel, inventory disputes become a matter of 'which account the goods are in.' Cross-warehouse transfers require issuing locks, making in-transit items visible, confirming receipts, and documenting discrepancy reasons. Owner segregation and ERP posting allow reconciliation, preventing end-of-month scrambling.
Read articleReview point deductions often occur because reports are still issued for overdue measuring instruments. The ledger, internal and external calibration plans, barcode flow, and submission gateways should be the same chain: overdue or non-conforming items are locked and inspection submission is blocked, and certificates and SN can be obtained within minutes.
Read articleThe list of qualified suppliers keeps getting longer, but those willing to increase volume have not increased. Performance must be linked to 8D, OTIF, and license red lines, with overdue rectifications visible in procurement. Observation, quantity limits, and exit should have trigger conditions and alternative plans, rather than just issuing a score sheet at the end of the year.
Read articleThe color change of non-conforming tags cannot prevent picking and passing through stations. Starting from the warehouse line site, explain how the isolation conclusion writes back point-by-point to the WMS batch location and MES work order, how concessions are controlled and marked, and how the incoming material chain and process chain are connected through pilot tests.
Read articleThe purchasing department says the goods have arrived, the warehouse says they have been stocked, and the finance department says the invoices don't match. Reconciliation confirmation, invoice verification, and payment applications need to fall under the same business key. Any discrepancies should be traceable to receipts, returns, and price versions, rather than reconciling three parties on Excel at the end of the period.
Read articleFIFO failures are usually not because the warehouse is being uncooperative, but because the recommendations can be easily bypassed. They are designed with three levels of enforcement: reminders, verification, and locking, and exceptions require authorization and review; inventory checks and batch separation are prerequisites, and they are linked to wave picking and batch/SN traceability in the same chain.
Read articleBreak down the parts in the IATF16949 audit that are most prone to losing points to the evidence level: what traces to leave, who leaves them and when, how the system receives them, and then arrange them in the sequence online according to 'high record density, hardest to collect evidence'.
Read articleOrder collaboration chaos is usually not due to the supplier being uncooperative, but because confirmations, changes, and delivery date feedback are not on the same document. Confirmation timestamps, change versions, and secondary confirmations, as well as feedback and commitments, are separated, yet the interface status on both sides is consistent.
Read articleProduction scheduling implementation failure is commonly due to incomplete material readiness constraints, dispatching that can be changed at will, and feedback not being returned. Starting from changing the sequence in the morning meeting chalkboard, it explains the planning—material readiness—dispatch—feedback closed loop, the visibility of insert order authorization and impact, as well as the sequence of first dispatching with limited daily/weekly capacity before applying advanced algorithms.
Read articleThe source tracing is interrupted during chatting and spreadsheets, and pricing cannot be traced back. The process of inquiry, bidding, and tendering must be recorded, price comparison must be auditable, finalization of the bid must be approved, and the results should be written back to the price master data before being transferred to procurement execution.
Read articleReceiving congestion is often caused by appointments that are only registered without occupying resources. Create a closed loop of occupancy—check-in—closure by linking the time window, dock, unloading capacity, and ASN. Incorporate late arrivals, no-shows, and emergency priority entries into the rules and performance evaluation. On peak days, schedule strategic suppliers first, then expand to full delivery.
Read articleShift QMS selection from 'whether it has features' back to 'how the workflow is closed and where the evidence is.' The 20 questions are organized into six groups: boundaries, traceability, supplier collaboration, customer complaint improvement, data permissions, and deployment/retirement. For each question, provide follow-up actions and A/B/C scoring tiers, and highlight the three most easily glossed-over points.
Read articleDirectory expansion has occurred, but those willing to increase volume have not; most likely, the entry process has only completed the filing. Data, capabilities, business, and observation periods need to be unlocked sequentially for volume growth; as long as the red line is not crossed, entry into the directory is allowed, and the evidence chain is more important than the total score.
Read articleSelf-test first, then decide on a system.Resources offers 8 self-assessments and 28 templates—book a live demo when ready.