Blog: Manufacturing Defects: One Weld Crack, Four Ways to Classify It

nuxt/content/blog/2024/01/revolutionizing-manufacturing-impact-ai-chatgpt-technologies.md

@@ -29,7 +29,7 @@ AI is adept at handling repetitive tasks, speeding up manufacturing and allowing
 
 ### Elevating Quality Control
 
-AI algorithms consistently ensure high-quality standards, quickly identifying and fixing product defects or deviations.
+AI algorithms consistently ensure high-quality standards, quickly identifying and fixing [product defects](/blog/2026/10/manufacturing-defects/) or deviations.
 
 ### Enabling Customization and Flexibility
 

nuxt/content/blog/2024/03/using-kafka-in-manufacturing.md

@@ -68,7 +68,7 @@ As we explore the capabilities of Kafka, we realize that it goes beyond being ju
 
 **1. Manufacturing Operations Optimization:**
 - Real-time Production Monitoring: Kafka is used in manufacturing for continuous monitoring of production lines, equipment status, and inventory levels. This real-time visibility aids in optimizing production efficiency, reducing downtime, and enhancing overall supply chain management.
-- Quality Assurance and Yield Management: Companies utilize Kafka to monitor quality control metrics in real-time, enabling proactive measures to maintain product quality standards, minimize defects, and optimize production yield.
+- Quality Assurance and Yield Management: Companies utilize Kafka to monitor quality control metrics in real-time, enabling proactive measures to maintain product quality standards, minimize [defects](/blog/2026/10/manufacturing-defects/), and optimize production yield.
 
 **2. [Predictive Maintenance](/blog/2025/09/preventive-maintenance-equipment-failure/):** Organizations use Kafka to collect and analyze sensor data from machinery and equipment to predict potential failures. This helps them optimize scheduled maintenance tasks to prevent costly downtime and disruptions
 

nuxt/content/blog/2025/07/quality-control-automation-spc-charts.md

@@ -45,7 +45,7 @@ Most manufacturers still rely on [end-of-line inspection](/blog/2026/10/automoti
 When inspection finds a defect, you've already invested in material, machine time, labor, and energy. That investment is now scrap. Worse, how many parts did you make between when the problem started and when you caught it?
 
 **Problem 2: The borderline parts you miss**
-Not all defects are obvious. Parts that barely pass inspection today might fail in the field tomorrow. These marginal parts slip through because traditional inspection only catches clear failures, not process degradation.
+Not all [defects](/blog/2026/10/manufacturing-defects/) are obvious. Parts that barely pass inspection today might fail in the field tomorrow. These marginal parts slip through because traditional inspection only catches clear failures, not process degradation.
 
 **Problem 3: No insight into root causes**
 Finding bad parts tells you nothing about why they're bad. Was it temperature drift? Tool wear? Material variation? Without process data, you're guessing at solutions.

nuxt/content/blog/2025/08/pareto-chart-manufacturing-guide.md

@@ -127,7 +127,7 @@ A Pareto diagram combines the best of both worlds, the immediate clarity of a ba
 ![Pareto diagram showing defect categories in manufacturing with bars for scratches, cracks, color issues, and other defects, alongside a cumulative percentage line.](./images/pareto-chart-image.png){data-zoomable}
 _Pareto diagram showing defect categories in manufacturing with bars for scratches, cracks, color issues, and other defects, alongside a cumulative percentage line._
 
-Look at this real Pareto diagram from a manufacturing facility. The bars show different types of defects found in one month, arranged from most common (scratches) to least common (other defects).
+Look at this real Pareto diagram from a manufacturing facility. The bars show different [types of defects](/blog/2026/10/manufacturing-defects/) found in one month, arranged from most common (scratches) to least common (other defects).
 
 Here's the key insight: See where the orange line crosses the 80% mark? It happens after just three defect types, scratches, cracks, and color issues. This means:
 

nuxt/content/blog/2025/09/creating-pareto-chart.md

@@ -98,7 +98,7 @@ To view the dashboard, click the **Open Dashboard** button in the top-right corn
 ![Pareto Chart showing defect categories in manufacturing with bars for scratches, cracks, color issues, and other defects, alongside a cumulative percentage line.](./images/pareto-chart.png){data-zoomable}
 _Pareto Chart showing defect categories in manufacturing with bars for scratches, cracks, color issues, and other defects, alongside a cumulative percentage line._
 
-The chart visualizes defect types using bars. The cumulative line and the 80% threshold indicate the cutoff point: bars to the left of this intersection represent the vital few defects that contribute most to the total, and these are the areas where you should focus your improvement efforts.
+The chart visualizes [defect types](/blog/2026/10/manufacturing-defects/) using bars. The cumulative line and the 80% threshold indicate the cutoff point: bars to the left of this intersection represent the vital few defects that contribute most to the total, and these are the areas where you should focus your improvement efforts.
 
 ![Pareto Chart showing defect categories in manufacturing. The bars on the left, highlighted with a red box, represent the vital few defects](./images/pareto-chart-decoded.png){data-zoomable}
 _Pareto Chart showing defect categories in manufacturing. The bars on the left, highlighted with a red box, represent the vital few defects_

nuxt/content/blog/2025/09/poka-yoke-mistake-proofing.md

@@ -62,7 +62,7 @@ Toyota engineer [Shigeo Shingo](https://en.wikipedia.org/wiki/Shigeo_Shingo) int
 
 Originally called **"baka-yoke" (idiot-proofing)**, the technique was renamed **poka yoke** after a worker objected, emphasizing that human errors are natural, not a reflection of intelligence.
 
-Shingo made a key distinction between human mistakes and production defects. Mistakes happen, they're part of being human. Defects occur when those mistakes reach the customer. Poka yoke focuses on designing processes so mistakes are immediately detected and corrected, eliminating defects at the source. This philosophy, which Toyota traces in its own account of the system, [*Toyota Production System: Beyond Large-Scale Production*](https://www.routledge.com/Toyota-Production-System-Beyond-Large-Scale-Production/Ohno/p/book/9780915299140) (Productivity Press, 1988), and which Jeffrey Liker later analyzed in [*The Toyota Way*](https://en.wikipedia.org/wiki/The_Toyota_Way) (McGraw-Hill, 2004), shifts manufacturing focus: rather than trying to perfect human behavior, perfect the systems in which humans work.
+Shingo made a key distinction between human mistakes and [production defects](/blog/2026/10/manufacturing-defects/). Mistakes happen, they're part of being human. Defects occur when those mistakes reach the customer. Poka yoke focuses on designing processes so mistakes are immediately detected and corrected, eliminating defects at the source. This philosophy, which Toyota traces in its own account of the system, [*Toyota Production System: Beyond Large-Scale Production*](https://www.routledge.com/Toyota-Production-System-Beyond-Large-Scale-Production/Ohno/p/book/9780915299140) (Productivity Press, 1988), and which Jeffrey Liker later analyzed in [*The Toyota Way*](https://en.wikipedia.org/wiki/The_Toyota_Way) (McGraw-Hill, 2004), shifts manufacturing focus: rather than trying to perfect human behavior, perfect the systems in which humans work.
 
 ## Poka Yoke Definition?
 

nuxt/content/blog/2025/09/what-is-5s-checklist.md

@@ -79,7 +79,7 @@ Companies that implement 5S checklists consistently report dramatic improvements
 
 Safety improvements often exceed expectations. When everything has a proper place and workspaces stay clean, accident rates can drop. Spills get noticed and cleaned immediately instead of becoming slip hazards. Tools don't get left in walkways where someone might trip.
 
-Quality improvements follow naturally from better organization. Clean, well-organized environments make it easier to spot problems before they become defects. When workers aren't rushed or frustrated from searching for materials, they make fewer mistakes. The predictability of well-organized processes reduces variability in outcomes.
+Quality improvements follow naturally from better organization. Clean, well-organized environments make it easier to spot problems before they become [defects](/blog/2026/10/manufacturing-defects/). When workers aren't rushed or frustrated from searching for materials, they make fewer mistakes. The predictability of well-organized processes reduces variability in outcomes.
 
 Perhaps surprisingly, employee engagement often increases significantly. Teams take pride in maintaining organized workspaces, especially when they participate in regular evaluations and see their scores improve over time. The checklist process gives everyone a voice in work area improvement.
 

nuxt/content/blog/2025/12/five-whys-root-cause-analysis-definition-examples.md

@@ -73,7 +73,7 @@ Our [5 Whys template](/blog/2026/09/five-whys-template/) provides a ready-made s
 
 ## When to Use the 5 Whys (and When Not To)
 
-The 5 Whys works best when a problem has a relatively straightforward causal chain. Common applications include equipment failures, quality defects, process bottlenecks, safety incidents, and customer complaints.
+The 5 Whys works best when a problem has a relatively straightforward causal chain. Common applications include equipment failures, [quality defects](/blog/2026/10/manufacturing-defects/), process bottlenecks, safety incidents, and customer complaints.
 
 It is less suitable when a problem has several independent or interacting causes. A major product recall involving design, materials, manufacturing, and distribution may require methods such as a [fishbone diagram](/blog/2026/07/ishikawa-fishbone-diagram/) or fault tree analysis to examine multiple pathways. Our [5 Whys vs. fishbone diagram](/blog/2026/09/5-whys-vs-fishbone-diagram/) guide covers how to choose between the two and how to combine them.
 

nuxt/content/blog/2026/01/what-is-system-integrator.md

@@ -58,7 +58,7 @@ System integrators connect both. And that's where things get complicated.
 
 ### Discovery and Diagnosis
 
-The work begins with understanding the actual problem. A line keeps jamming because two machines won't sync. Production data sits trapped in SCADA and can't reach your ERP for scheduling decisions. Quality defects have no connection to process parameters. These aren't isolated issues: they're integration failures.
+The work begins with understanding the actual problem. A line keeps jamming because two machines won't sync. Production data sits trapped in SCADA and can't reach your ERP for scheduling decisions. [Quality defects](/blog/2026/10/manufacturing-defects/) have no connection to process parameters. These aren't isolated issues: they're integration failures.
 
 A system integrator walks your plant with a specific lens. They document what equipment you're running, which protocols each device speaks, where IT and OT systems touch or fail to. They identify the gaps: a PLC speaking [Modbus](/blog/2023/05/integrating-modbus-with-node-red/) trying to feed a cloud platform, an MES that can't pull real-time SCADA status, a quality database disconnected from traceability. They map not just what's broken, but why, and what fixing it actually requires.
 

nuxt/content/blog/2026/02/edge-ai-is-80-percent-pipeline-and-20-percent-ai.md

@@ -50,7 +50,7 @@ The OT engineer who has spent fifteen years learning one plant's quirks is not g
 
 FlowFuse starts from that same premise and takes it further, into the territory Node-RED was never designed to handle alone.
 
-Take what happens when you want to put a model in production. You have a data scientist who trained something useful, a predictive maintenance model, an anomaly detector, a vision system for defect classification. The model is accurate. It works on their laptop. And then there is the question of where it actually lives, how OT can interact with it, what happens when it needs to be retrained, and who owns it when something goes wrong at 2 a.m. on a Saturday.
+Take what happens when you want to put a model in production. You have a data scientist who trained something useful, a predictive maintenance model, an anomaly detector, a vision system for [defect classification](/blog/2026/10/manufacturing-defects/). The model is accurate. It works on their laptop. And then there is the question of where it actually lives, how OT can interact with it, what happens when it needs to be retrained, and who owns it when something goes wrong at 2 a.m. on a Saturday.
 
 In most deployments, nobody has a good answer to any of those questions. The model ends up in a container somewhere that only the data scientist understands, connected to the plant by a fragile handshake that no one wants to touch. The OT team treats it like a black box because it is a black box.
 

nuxt/content/blog/2026/02/what-is-event-driven-architecture-in-manufacturing.md

@@ -77,7 +77,7 @@ EDA closes that gap. When something happens, every system that needs to know fin
 
 The scale of what's at stake makes this worth stating plainly. Unscheduled downtime costs the world's largest manufacturers trillions annually, representing a double-digit percentage of revenue. Nearly three-quarters of manufacturing leaders report that delays in reporting problems trigger chain reactions across their operations. These aren't technology metrics. They're business outcomes produced by architectures that were never designed to respond in real time.
 
-Quality compounds the same way. The 1-10-100 rule of manufacturing quality states that a defect costs $1 to catch pre-production, $10 to catch during production, and $100 once it reaches the customer. Every minute a failed inspection goes unbroadcast to downstream systems, that multiplier is running. EDA stops the propagation at the source by ensuring the result is instantly visible to every process that needs to act on it.
+Quality compounds the same way. The 1-10-100 rule of manufacturing quality states that a [defect](/blog/2026/10/manufacturing-defects/) costs $1 to catch pre-production, $10 to catch during production, and $100 once it reaches the customer. Every minute a failed inspection goes unbroadcast to downstream systems, that multiplier is running. EDA stops the propagation at the source by ensuring the result is instantly visible to every process that needs to act on it.
 
 Integration debt follows the same logic. Enterprise-level manufacturing software implementations routinely take many months to multiple years. Every new capability your team wants requires a project. EDA changes the economics entirely. New systems subscribe to the broker. Existing systems stay untouched. What once consumed quarters now requires configuration.
 

nuxt/content/blog/2026/03/ai-usecases-in-factory.md

@@ -44,7 +44,7 @@ That's the shift. Not better alarms, but a system that knows the difference betw
 
 Manual inspection has a hard ceiling. Put someone at a line running 200 units a minute for four hours and their defect detection rate drops. That's not a training problem. It's physiology.
 
-Computer vision doesn't have that ceiling. A camera at the inspection station sees every unit, not a sample, at full line speed, catching surface defects, dimensional drift, solder bridges, and weld inconsistencies. In semiconductor fabrication, where a particle smaller than a human hair destroys yield, vision-based inspection isn't an upgrade. It's the only option that makes sense at volume.
+Computer vision doesn't have that ceiling. A camera at the inspection station sees every unit, not a sample, at full line speed, catching [surface defects](/blog/2026/10/manufacturing-defects/), dimensional drift, solder bridges, and weld inconsistencies. In semiconductor fabrication, where a particle smaller than a human hair destroys yield, vision-based inspection isn't an upgrade. It's the only option that makes sense at volume.
 
 BMW's [AIQX platform](https://www.press.bmwgroup.com/global/article/detail/T0449729EN/artificial-intelligence-as-a-quality-booster?language=en) runs camera and sensor-based AI quality checks across every plant globally. At Spartanburg, it monitors roughly [half a million weld studs daily](https://www.automotivemanufacturingsolutions.com/smart-factory/quality-visions-ai-inspection-systems-that-learns-from-the-line/2623126). At Regensburg, the [GenAI4Q system](https://www.press.bmwgroup.com/global/article/detail/T0449729EN/artificial-intelligence-as-a-quality-booster?language=en) generates a custom inspection checklist for each of 1,400 vehicles built daily, adapting to every model variant in real time.
 

nuxt/content/blog/2026/03/edge-ai-vs-cloud-ai-in-iiot.md

@@ -49,7 +49,7 @@ Think about what happens in the seconds after a sensor detects something abnorma
 
 This is the environment edge AI was built for. Manufacturing lines running at speed, assets in remote locations, facilities where network connectivity is inconsistent or restricted. In these situations, the model needs to live close to the source, processing data as it arrives and producing a result before the next event occurs.
 
-Quality inspection is one of the clearest examples. A vision system identifying surface defects, dimensional errors, or assembly faults on a fast-moving line has a window measured in milliseconds. The same logic applies to condition monitoring on rotating equipment, anomaly detection on process instrumentation, and real-time control adjustments based on live sensor feeds.
+Quality inspection is one of the clearest examples. A vision system identifying [surface defects, dimensional errors, or assembly faults](/blog/2026/10/manufacturing-defects/) on a fast-moving line has a window measured in milliseconds. The same logic applies to condition monitoring on rotating equipment, anomaly detection on process instrumentation, and real-time control adjustments based on live sensor feeds.
 
 Edge AI also matters where data cannot easily leave the facility. Regulatory requirements, network constraints, or simple operational practicality all create situations where keeping data local is not optional. Running the model at the edge removes the dependency entirely.
 

nuxt/content/blog/2026/07/defect-and-quality-monitoring.md

@@ -48,7 +48,7 @@ cta:
 tldr: "This tutorial builds a defect tracking and quality monitoring dashboard in FlowFuse. Defects live in one table, a single query computes every KPI in one pass, and the dashboard renders stat cards, a Pareto chart, trend and breakdown charts, an SLA table, and a status funnel, all filtering live by line, shift, and date range."
 ---
 
-Every production line produces defects. On their own they're easy to wave off, a bit of scrap here, an hour of rework there. But add them up and the cost is real, and that's the part most teams never see. The defects are sitting in a spreadsheet nobody sorts, or locked inside a quality system you can't get a live view out of. So the recurring problems stay invisible until someone runs a report, and by then the bad batch has already shipped.
+Every production line produces [defects](/blog/2026/10/manufacturing-defects/). On their own they're easy to wave off, a bit of scrap here, an hour of rework there. But add them up and the cost is real, and that's the part most teams never see. The defects are sitting in a spreadsheet nobody sorts, or locked inside a quality system you can't get a live view out of. So the recurring problems stay invisible until someone runs a report, and by then the bad batch has already shipped.
 
 <!--more-->
 

nuxt/content/blog/2026/07/digital-work-instruction.md

@@ -89,7 +89,7 @@ Before we build anything, let's walk through what the app does and how the piece
 
 1. **Home.** After logging in, the application uses the operator's username to retrieve only the work orders assigned to them from the ERP or [MES](/blog/2025/06/what-is-mes/). It displays their station, production summary, the highest-priority work order, and the remaining queue. Selecting **Start Work Order** opens the instructions.
 2. **Instructions.** Operators follow step-by-step instructions with images, checklists, and target cycle times. They can progress through each step, complete the operation, or report an issue at any time.
-3. **Report Issue.** Operators can quickly log defects by selecting the issue type, severity, affected part, and description, with the issue automatically linked to the current work order.
+3. **Report Issue.** Operators can quickly log [defects](/blog/2026/10/manufacturing-defects/) by selecting the issue type, severity, affected part, and description, with the issue automatically linked to the current work order.
 
 The logged-in username acts as the application's lookup key. It retrieves the operator's assigned work orders and stores their active work order and current step, allowing them to resume exactly where they left off, even on shared production stations.