Knowledge and Practice
Bring concepts down to data definitions, shop-floor actions, and validation methods
This section addresses specific questions in lean digital implementation: how signals are interpreted, how metrics are calculated, how exceptions are closed, and which shop-floor work systems cannot replace.
5S Layered Audits: Move from Scoring Inspections to Sustaining Standards and Solving Problems
The direct answer for a 5S layered audit is to establish area-specific standards for Sort, Set in Order, Shine, Standardize and Sustain, have different management levels inspect according to their distinct responsibilities, and route every finding through ownership, correction, verification and standard updates. The goal is not to maximize scores, but to expose abnormalities more readily and sustain basic working conditions. The audit checklist is only the vehicle; the closed loop on the shop floor is what matters.
Andon Response Loop: From Abnormality Calls to Review and Improvement
The direct answer for an Andon response loop is to give every abnormality a clear type, owner, status and escalation path, then complete discovery, calling, acknowledgment, arrival, treatment, recovery, closure and review in sequence. Lights and dashboards are only information entry points. Andon effectiveness depends on clear response ownership, consistent timing definitions, and whether abnormalities become evidence for sustained improvement.
Manual Batching Error-proofing Guide: From Scan Prompts to a Closed Weighing Loop
The direct answer for manual batching error-proofing is to combine recipe version, material identity, addition sequence, live weight, tolerance and exception authorization into an execution chain that cannot be skipped at will. Scanning answers ‘Is this the right material?’ Weighing comparison answers ‘Is the quantity within the allowed range?’ Lot linkage answers ‘Can the event be traced afterward?’ All three must be designed together with material issue and return, lot changeover and exception handling. On-screen prompts alone cannot justify a claim that errors have been eliminated.
Forward and Backward Traceability: Connect Product Identity and Process Evidence in One Graph
The direct answer for forward and backward traceability is to support both query directions around the same identity relationships. Backward tracing starts with a finished product or lot and identifies the materials used, equipment and processes involved, operators and quality results. Forward tracking starts with a suspect material, equipment item, tool or process abnormality and identifies potentially affected work in process and finished goods. Both share one event chain; they are not two separately built reports.
The Seven Wastes of Lean Production: From Shop-floor Identification to Data-supported Improvement
The direct answer for the seven wastes is to classify activities that do not create customer value as overproduction, waiting, transportation, overprocessing, inventory, motion and defects, then use shop-floor observation and process data to locate where they occur, how long they last and what triggers them. Classification alone does not improve anything. Waste moves from being seen to being reduced only when it is connected to ownership, standard work, abnormality handling and a regular review cadence.
MES, ERP and SCADA Boundaries: Draw Lines by Object Ownership, Not Department
The direct answer for dividing MES, ERP and SCADA boundaries is to confirm, object by object, who creates, modifies, executes, retains and reconciles. ERP typically owns enterprise resources and business planning; MES owns shop-floor execution and process coordination; SCADA owns equipment-process monitoring, alarms and history; PLC and safety-related control remain in validated control systems. Boundaries are designed around objects, states, time and accountability, not guessed from software names.
OEE Loss Tree: Trace the Three Factors to Actionable Losses
The direct answer for an OEE loss tree is to calculate Availability, Performance and Quality within the same Planned Production Time boundary, then break the gaps in those three factors down into downtime, minor stops, reduced speed, startup and quality losses. OEE = Availability × Performance × Quality, where Availability = Run Time ÷ Planned Production Time, Performance = Ideal Cycle Time × Total Count ÷ Run Time, and Quality = Good Count ÷ Total Count. The formulas must use the same equipment, period and production-count definitions.
OEE and TPM Working Together: How Metrics, Improvement Methods and Software Divide the Work
The direct answer for OEE–TPM synergy is to use OEE to identify and quantify equipment losses, TPM to organize autonomous maintenance, planned maintenance, skills and improvement activities, and software to preserve event, work-order and validation evidence. OEE is a metric, not a maintenance method. TPM is a management system, not a software module. Data collection and dashboards are supporting tools and do not automatically create maintenance results.
SMED Quick Changeover: Break Changeover Losses into Work That Can Be Reorganized
The direct answer for SMED quick changeover is to break the changeover into observable work elements, distinguish internal work that must be completed while equipment is stopped from external work that can be completed earlier or later while it runs, and then shorten actual production occupancy through externalization, parallel work, simplification and standardization. The goal is not to rush people or reduce first-piece, safety or quality confirmation, but to eliminate waiting, searching, repeated adjustment and disorganized coordination.
SPC and Process Capability: Establish Stability Before Discussing Cp/Cpk
The direct answer for SPC and process capability is to use control charts first to determine whether a process is statistically stable, then calculate capability indices only when specifications, distribution and the measurement system are appropriate. Cp = (USL − LSL) ÷ (6σwithin), and Cpk = min[(USL − μ) ÷ (3σwithin), (μ − LSL) ÷ (3σwithin)]. Pp and Ppk use the overall standard deviation rather than the within-subgroup standard deviation. Control charts answer whether special causes are present; capability indices describe process spread and centering relative to specifications. One cannot replace the other.
How to Calculate Unit Energy Consumption: Align Boundaries Before Discussing Energy Savings
The direct answer for unit energy consumption is to divide energy consumed within a clearly defined boundary by the corresponding useful output over the same reporting period: Unit Energy Consumption = Energy within the Boundary ÷ Output within the Boundary. The formula is simple; the difficulty lies in whether utilities and idling are included, whether Total Count or Good Count is used, how multiple products are converted, and whether product, output, environment and operating conditions are normalized for comparison. Without these definitions, a rise or fall may reflect nothing more than a changed accounting basis.
How to Collect Value-stream Data: Make the Current-state Map a Verifiable Improvement Baseline
The direct answer for value-stream data collection is to select a product family and start/end boundaries first, record cycle time, changeover, available time, work in process, quality and batching rules along material and information flows, and then calibrate system data with shop-floor observation. A value-stream map is not an MES report drawn as a flowchart. It explains how demand triggers production, where materials wait, where information becomes distorted, and which losses belong in future-state design.
Turn article methods into a shop-floor question list
If you are assessing a similar scenario, submit your current data conditions and questions so we can first check whether the method applies.