# Mobile2b - full site text > Machine-readable long-form description of mobile2b.com. Generated from the site's own content files, so it cannot drift from the pages themselves. The short version is at https://www.mobile2b.com/llms.txt. Mobile2b is an enterprise software company in Cologne, Germany, founded in 2010. We build software that runs operational work: audits and inspections, and custom AI agents that do routine business work end to end. More than 100 companies use the platform, among them Bayer, Mercedes-Benz, Porsche, Audi, Bosch and Magna. We sell four things: 1. **Audit and inspection platform.** Plan, run and close audits across a whole organisation. Works offline, deploys in the EU cloud or on-premise. This is the established business. 2. **Managed AI agents.** We build, run and maintain custom AI agents for a company's own processes, on self-hosted LLMs, GDPR-compliant, on-premise if wanted. We run this on ourselves first: agents handle our customer-success monitoring, email-deliverability reporting, SEO and growth work, infrastructure watchdog and the daily product digest, on a schedule, every working day. 3. **Fieldcast.** Frontline workers report by WhatsApp or Telegram. An agent reads the intent and creates the right ticket or action. No app, no login, no forms. 4. **Narrator.** Experienced employees speak freely into a voice note. Agents turn it into a knowledge base their successor can query. Built for Mittelstand succession, where the knowledge leaves with the person. Deployment: EU cloud or fully on-premise. Certification: ISO 27001. Languages: German and English. ## Company ### Software that runs your operations. URL (DE): https://www.mobile2b.com/ URL (EN): https://www.mobile2b.com/en Summary: Audits and inspections - digitized, automated, always audit-ready. **Solutions: Software that runs your operations.** **Results: Real results. Real customers.** **Trust: Enterprise-grade. No compromises.** ### Always audit-ready. Always compliant. URL (DE): https://www.mobile2b.com/audits-inspections URL (EN): https://www.mobile2b.com/en/audits-inspections Summary: Digitize your audits and inspections. Complete traceability, automatic escalation, real-time dashboards. **The Problem: Paper audits cost more than you think.** **The Solution: Audits that manage themselves.** **Audit Types: One platform. Every audit type.** ### Managed AI agents on your terms URL (DE): https://www.mobile2b.com/solutions/ai-agents URL (EN): https://www.mobile2b.com/en/solutions/ai-agents Summary: We build, run, and maintain custom AI agents for your company. On trusted servers, with self-hosted LLMs, GDPR-compliant, and fully on-premise if you want it. **The problem: Off-the-shelf AI tools send your data to foreign clouds** Most AI tools are thin wrappers on a US model. Your quotes, contracts, customer data, and internal processes leave the company and land on servers you do not control. For regulated industries and the German Mittelstand, that is not an option. At the same time, repetitive work eats capacity every day: writing quotes, checking invoices, answering requests, compiling reports. A generic chatbot does not solve this, because it does not know your processes and nobody runs it for you. **The solution: Agents we build and run for you** We build AI agents tailored to your specific processes and connected to your systems. They run on trusted infrastructure: self-hosted LLMs on our EU servers, or directly inside your own network. You do not get another tool to operate yourself, you get an outcome. We build, monitor, update, and improve the agents continuously. You keep control, we run the operation. We run these agents on our own business first. At Mobile2b they work in production every day: customer success, a daily product briefing, email deliverability monitoring, optimization of this website, and a watchdog agent that repairs failed runs of the others. What we sell you, we keep running on ourselves. **How it works: Three steps to a managed agent** From process to a production AI agent running on your infrastructure. - Understand the process - We analyze a concrete process that fits automation and define the goal, the data sources, and the points where a human should approve. - Build and integrate the agent - We build the agent, connect it to your systems such as ERP, CRM, email, or file storage, and test it on real cases from your operation. - Run and improve - The agent runs monitored on trusted infrastructure. We maintain, update, and improve it continuously. You can see what it does at any time. **What you get: An agent that fits your company** - Tailored to your processes - Not a generic chatbot. Each agent is built for a concrete workflow in your company and speaks the language of your operation. - Integrated with your systems - Connected to ERP, CRM, email, document storage, and other tools. The agent works where your data and processes already live. - Fully managed - We build, monitor, update, and improve. No maintenance burden on your side: you get an outcome, not another project to run. - Transparent and traceable - You see what the agent does and why. Every action is logged and auditable, no black box. - Human stays in control - Critical steps go to a human for approval. The agent acts autonomously where it is safe and asks where it matters. - Gets better over time - Every agent learns your cases, terms, and exceptions. The value compounds over time instead of being obsoleted by the next model. **Examples: Agents we build** Concrete use cases from the daily reality of mid-market and industry. Your agent is tailored to your process. - Quoting and invoicing agent - Drafts quotes from inquiries, checks incoming invoices against orders, and prepares the approval. You decide, the agent does the groundwork. - Support and communication agent - Answers recurring requests, drafts replies, and escalates complex cases to the right person with the right context. - Reporting and monitoring agent - Collects data from your systems, produces regular reports, and flags anomalies before they become a problem. **Agent types: AI agent pricing and capability levels** The level depends on how many systems the agent works across, how much judgement the task needs, and how independently it acts. - Assistant - 199 € - Works in one system plus email. Follows a fixed sequence and prepares work for a person to approve. - Specialist - 499 € - Works across two to four systems. Applies your rules and exceptions, acts within defined limits, and escalates edge cases. - Expert - 899 € - Works across five or more systems, or inside your own network. Handles open tasks that need judgement and coordinates other agents. 12-month minimum term. Hosted in the EU. On-premise operation available. All prices exclude VAT. - Included in every monthly price: Model and token costs; Hosting, monitoring, and incident response; Model upgrades as better models ship, at no change in price; Tuning and corrections within the agent's defined scope - Setup and integration: Setup is quoted per customer, based on how many systems we connect; Systems that need custom or on-premise integration are priced separately, from 1,200 € per system; We tell you which category your systems fall into before you sign - Adding more agents: No setup fee for additional agents on systems we already connect; From six agents, 20 percent off the monthly price; Move an agent up a level when it outgrows its scope **Security and data protection: Built for European data protection requirements** - Self-hosted LLMs - The models run on our trusted EU servers or in your own data center. Your data does not train foreign models. - Data stays in the EU - Processing and storage in Germany or the EU. GDPR-compliant, with clear data processing agreements. - On-premise available - On request, the entire agent runs inside your own network. Nothing leaves your infrastructure. - Auditable and certified - Every action is logged. Role-based access, encryption, and an information security management system run to ISO 27001 are included. **Frequently asked questions** - What is an AI agent? - An AI agent is a program that completes a task on its own instead of just answering questions. It understands a goal, accesses your systems, executes steps, and requests approval for critical decisions. We build such agents for concrete processes in your company and run them for you. - Does our data leave the company? - No, not if you do not want it to. We run self-hosted LLMs on trusted EU servers or directly inside your own network. On request, everything runs fully on-premise, so no data leaves your infrastructure. - Which language models do you use? - We prefer open, self-hosted models that we run on our own infrastructure. If a commercial model is clearly better for a given use case, we use it only with your explicit approval and with appropriate data protection agreements in place. - Can the agents run on-premise? - Yes. The entire agent including the model can run in your own data center or private cloud. This is especially relevant for regulated industries and sensitive data. - Which systems can this integrate with? - Common systems such as ERP, CRM, email, document storage, and internal tools, through their interfaces. If there is an API or a defined access path, an agent can work with it. - What does a managed AI agent cost? - An agent costs between 199 € and 899 € per month depending on its level. An Assistant is 199 €, a Specialist 499 €, and an Expert 899 € per agent per month. Model and token costs, hosting, monitoring, and model upgrades are included. On top of that there is a one-time setup fee that depends on how many systems we connect. - How quickly can we go live? - We work in days, not quarters. A first, clearly scoped agent can be in production within a few weeks. We deliberately start with one concrete process and build from there. - What happens when something goes wrong? - Critical steps always go to a human for approval. The agent is monitored, every action is logged, and we step in on anomalies. You keep control at all times and can stop the agent. - What does an additional agent cost? - There is no setup fee for additional agents that use systems we already connect. From six agents the monthly price drops by 20 percent. The minimum term is 12 months. - Do you use AI agents in your own company? - Yes, and that is why this offering exists at all. Managed agents run in production at Mobile2b every day: customer success, a daily product briefing, email deliverability monitoring, optimization of this website, and a watchdog agent that diagnoses and repairs failed runs of the other agents. Each one has access to real systems, a full log, and a human approval step where it matters. We build your agent on the same pattern. **FlowForward: free of charge for nonprofit organizations** Registered nonprofit organizations get these AI agents free of charge. Through our FlowForward initiative we build and run the agents at no cost, so nonprofits can focus on what truly matters: their mission. ### Frontline messages become structured actions URL (DE): https://www.mobile2b.com/solutions/fieldcast URL (EN): https://www.mobile2b.com/en/solutions/fieldcast Summary: Workers report via WhatsApp or Telegram. AI understands the intent and makes sure the right thing happens: no app, no login, no forms. **The Problem: Workers don't report: because the reporting process is too cumbersome** Every shift, operators and technicians see things the company needs to know: a valve that's been dripping for days, a sound that wasn't there last week, an idea that could cut a process in half. This knowledge is lost, every day, every shift. Not because workers don't care: but because they'd need to grab a form, walk to a terminal, or open an app, log in, and fill out required fields. Whether paper or software: the reporting process takes five minutes they don't have. So nothing happens. **The Solution: Meet workers where they already are** Fieldcast lets workers report through the messenger they already use every day. A photo, a voice message, a short sentence: that's enough. AI understands the intent, drafts an action: maintenance ticket, safety report, or improvement suggestion, and presents it to a reviewer. Only after approval does the action execute. Every correction makes the system smarter. **How It Works: Three steps. Zero friction.** From observation to structured action: in seconds, not hours. - Send a message - The worker sends a photo, voice note, or short text through their messenger. No login, no app, no form. - AI interprets - Fieldcast identifies the intent, assigns machine, category, and priority, and drafts an action: maintenance ticket, safety report, or improvement suggestion. - Review and execute - A shift lead reviews the draft and approves it. The action is created in the target system. Every correction trains the AI. **Features: Everything you need to close the loop** - Multi-channel input - Text, photos, voice messages, and documents via WhatsApp, Telegram, or SMS. Workers choose how they report. - AI intent engine - Understands the intent behind every message: even with blurry photos, dialect, and industry jargon. Gets better with every correction. - Human-in-the-loop - Every AI interpretation is reviewed by a human before any action executes. Trust through control. - Compound learning - The system builds a company-specific knowledge base: machine nicknames, terminology, typical failure patterns. After three months, it understands your factory better than a new hire. - Transparent intelligence - Customers can see and edit what the system has learned. No black box: full control over terminology and mappings. - Multilingual by default - Workers report in their native language. The system translates and structures automatically. Ideal for international operations. **The Learning Flywheel: A system that understands your factory** Every message, every correction, every resolved action makes the system more precise. After three months, it understands your abbreviations, your machines, and your most common problems. - Terminology and mapping - Nicknames become asset IDs. Jargon becomes a glossary. Person-specific expressions are decoded. The system learns your factory's language. - Behavioral patterns - Who reports what, when, and how often? Shift-specific patterns, machine-specific failure modes, temporal correlations: all feed into interpretation. - Resolution knowledge - Similar past incidents and their resolutions are automatically retrieved. The system detects recurring problems and suggests proven actions. **Enterprise-ready: Built for industrial operations** - End-to-end encryption - All data encrypted in transit and at rest. RBAC and audit trail included. - On-premise or cloud - Your data stays where you decide: in the cloud (hosted in Germany) or on your own infrastructure. - Productive in days - No training project, no change management. Workers use their existing messenger: the first value is created on the day of introduction. - Seamless integration - Connects to Mobile2b, Jira, ServiceNow, SAP, and more. Actions land exactly where your team expects them. **Frequently asked questions** - How does Fieldcast work as idea management software? - Workers submit improvement suggestions via WhatsApp or Telegram. The AI categorizes the suggestion, assigns it to the right area, and routes it to the responsible person. No suggestion box, no paper form, no separate software: idea management through the messenger everyone already uses. - Is Fieldcast a continuous improvement (CI) tool? - Yes. Fieldcast supports continuous improvement by radically lowering the barrier to reporting. More reports mean more data points for patterns and trends. The system detects recurring problems and suggests proven solutions: CI software that learns from practice. - How does mobile maintenance work with Fieldcast? - Workers report faults and maintenance needs directly via messenger. The AI identifies the intent and creates structured maintenance tickets with machine assignment and priority: mobile maintenance without a separate app, without login, without forms. - Does Fieldcast replace our existing maintenance app? - Fieldcast complements your existing system. It connects to Jira, ServiceNow, SAP, and Mobile2b. Workers report via messenger, the AI drafts the ticket, and after approval it lands directly in your CMMS or maintenance software. - What makes Fieldcast a shop floor management tool? - Fieldcast captures all types of reports directly from the shop floor: improvement suggestions, fault reports, and safety observations. The AI assigns machine, category, and priority. Reviewers check the draft. The system learns from every correction: shop floor management that starts with the worker. - Can Fieldcast support lean production? - Yes. Lean production depends on early detection of problems and improvement potential. Fieldcast lowers the reporting threshold so workers actually report: more signal, earlier detection, faster response. Ideal for Kaizen, continuous improvement, and employee suggestion programs. - Do workers need a new app? - No. Workers use WhatsApp or Telegram, the messenger they already have. There is no app to install, no login to remember, and no required fields. Adoption takes minutes, not months. - How secure is the data? - All data is encrypted end-to-end. Fieldcast offers role-based access control and complete audit trails. The system can be hosted in the cloud (hosted in Germany) or on-premise on your own infrastructure. ### When your best operator retires, the knowledge stays in the plant URL (DE): https://www.mobile2b.com/solutions/narrator URL (EN): https://www.mobile2b.com/en/solutions/narrator Summary: Experienced employees talk freely into a voice message. No login, no forms, no follow-up questions. AI agents turn it into a knowledge base their successor can ask. **The problem: Every retirement walks 30 years of experience out the gate** The person who knows why the line behaves differently in damp weather retires in two years. That knowledge is in no manual and in no work instruction. It sits in a head that will soon not be in the plant. Documentation projects do not fix this. They ask for effort from the one person who is already busiest. And they ask for knowledge the holder does not know is special. After a three month handover the successor has a fraction of it. **The solution: Talking instead of documenting** Narrator inverts the task. The experienced employee writes nothing. They talk whenever it suits them, for as long as they want, with no structure and no template. A voice message in the messenger they already use. The system never replies. It does not ask, it does not correct, it does not judge. The work happens in the background: AI agents transcribe, assign topics, link recordings, and build a knowledge base that grows with every recording. **How it works: Three steps. No project.** From free talking to a knowledge base you can query, without anyone filling in a form. - Talk - The employee sends a voice note over WhatsApp or Telegram. No login, no app, no template. They say whatever comes to mind. - Agents structure - In the background, AI agents transcribe the recording and place it: asset, procedure, exception, context. Every new recording is linked to what is already there. - The successor asks - The successor asks in their own words. The knowledge base answers and links to the original recording, so they can hear the source themselves. **Capabilities: Built for people who do not want a software project** - Voice first - Talking is ten times faster than writing and carries more. Photos, video, and short text work too, whenever they fit better. - The system only listens - Narrator does not reply and does not ask questions. No interview, no time pressure, no assessment. That is what lowers the barrier for people who have never handed knowledge to software. - The recording stays canonical - The raw recording is never changed. Every structured artefact is derived from it and regenerated as transcription and models improve. Your knowledge base gets better retroactively. - Dialect, jargon, and nicknames - The system learns the language of your plant: what the machines are really called, which abbreviations apply, and what a term means specifically here. - Knowledge that connects - Each recording is linked to the existing body of knowledge. Contradictions and gaps become visible, so you can follow up while the holder is still there. - Your knowledge stays yours - Recordings and knowledge base belong to you and export in open formats. Hosted in Germany or on premise on your own infrastructure. **The knowledge store: A body of knowledge that improves as the technology does** Classic documentation starts ageing the day it is written. A store of original recordings gets more valuable with every better model. - Raw store - Every recording is kept unchanged. Nothing is lost, not even the side remark whose meaning nobody understands yet. - Derived artefacts - Transcript, summary, work instruction, glossary, and knowledge graph are generated from the raw store and fully recomputed when needed. - Knowledge on demand - The successor asks in their own words and gets an answer with its source. The same base later feeds onboarding, maintenance, and audits. **Workable in practice: Built for the realities of a European plant** - Voluntary and co-determination ready - Participation is voluntary. Every employee sees their own recordings and can delete them. Purpose, scope, and retention can be agreed cleanly with the works council. - On premise or cloud in Germany - Recordings are personal voice data. They stay where you decide: in our cloud in Germany or on your own infrastructure. - GDPR, roles, and audit trail - Encryption in transit and at rest, role based access control, and a complete audit trail over every access to a recording. - Start with three people - No rollout and no change project. You start with the people whose knowledge is closest to leaving. **Frequently asked questions** - What is Narrator? - Narrator is a knowledge retention solution. Experienced employees talk freely into voice messages, with no structure and no forms. AI agents transcribe and organise the recordings in the background and build a knowledge base that successors can query later. - How does knowledge transfer before retirement work with Narrator? - Instead of a handover phase full of documentation tasks, the departing employee talks over many months whenever something comes to mind. Every recording is structured and linked to the previous ones. The successor later works with a knowledge base instead of a folder. - Why does the system not reply? - Because a reply forces a conversation and a conversation creates expectations. People who do not want a software project talk more freely when nobody asks, corrects, or judges. Structuring happens in the background, not in a dialogue. - How is works council co-determination handled? - Voice recordings of employees are personal data and usually subject to co-determination. Narrator is designed for that: voluntary participation, access and deletion rights for every speaker, a clearly bounded purpose, and no performance or behaviour monitoring. These points belong in a works agreement, and we support the preparation. - What happens to the recordings after the employee has left? - You define retention and deletion periods, usually in the works agreement. Technically the raw recording remains the canonical store for as long as it is kept. All derived artefacts can be regenerated from it at any time. - How is Narrator different from a wiki or a document database? - A wiki requires somebody to write, structure, and maintain. That is exactly where knowledge projects fail. Narrator only requires talking. Structure is produced by agents and recomputed as the technology improves, instead of ageing from the day it was written. - How does Narrator relate to Fieldcast? - Both rest on the same idea: people report or talk through the messenger they already use, and AI agents turn it into something usable. Fieldcast produces actions from daily operations. Narrator produces a body of knowledge from experience. Both run on the same platform. ### About Mobile2b URL (DE): https://www.mobile2b.com/about URL (EN): https://www.mobile2b.com/en/about Summary: We build software that digitizes operational processes - pragmatic, reliable, and Made in Germany. **From the Founder** **Trusted by Leading Companies** **Made in Germany: Built, hosted, and supported in Germany** Mobile2b is a German company headquartered in Cologne. Our team works across the EU, our servers are hosted in Germany, and your data never leaves the European Union. For customers who need full control, we offer on-premise deployment - your infrastructure, your rules. **FlowForward: Technology that drives positive change.** FlowForward is our nonprofit initiative: we provide the Mobile2b platform at no cost to registered nonprofit organizations. So they can automate their operations, reduce manual work, and focus on what truly matters - their mission. ### Become a Mobile2b partner URL (DE): https://www.mobile2b.com/partner URL (EN): https://www.mobile2b.com/en/partner Summary: Refer, resell or implement: you bring the access and the domain knowledge, we deliver the platform. Three tracks, clear commissions, protected leads. No joining fee and no revenue commitment. **Why Mobile2b: A product that sells because it is proven in the field** You are not referring a beta. Large industrial customers have run the platform in production for years, across multiple plants and sites. - Proven in enterprise use - Automotive, food and industrial customers work with the platform every day. You sell practice, not a promise. - Broad solution range - Audits, maintenance, field service, compliance and AI agents on one platform. One customer, many reasons for follow-on business. - Software made in Germany - GDPR-compliant, hosted in the EU, on-premise on request. The argument that opens doors in industry and the German Mittelstand. - Configuration instead of development - Processes get configured, not coded. You can deliver yourself without waiting for our roadmap. - Recurring revenue - Subscriptions instead of one-off projects. Your share grows with the customer and does not end at the first signature. - Direct contact - You talk directly to the people who build the product. No channel bureaucracy and no layers in between. **Three partner tracks: Pick the track that fits your business** From pure referral to full sales and delivery ownership. You can switch tracks or combine them. All tracks are free, with no joining fee and no minimum revenue. We pay on results only: commission once the customer has paid, with no retainers and no upfront fees. - Referral partner - Reseller partner - Implementation partner **Deal registration: Your lead stays your lead** You register the customer by email to partner@mobile2b.com. We reply within one business day and confirm the registration. From that confirmation the lead is protected for you for 90 days, no matter who else at that company talks to us next. If the customer is already in our pipeline, we tell you straight away. We never pay a commission twice, and we never hide an existing contact either. If the deal takes longer and the conversation is live, we extend the protection. **How to start: Three steps to your first registered deal** From first contact to first deal typically takes two weeks. - Intro call - Send us a short note about who you reach. Then a 30-minute call about your market, your customers and the right track. - Onboarding and certification - You get a sandbox tenant, product training and sales material. Certification typically takes two days. - Register deals and earn - Register the lead, get 90 days of protection, receive commission once the customer has paid. Settled monthly, with an overview of your open deals. **What you get from us: We stand behind you, not just a logo on a list** - Sandbox tenant - Your own environment to test, demo and configure. Free and permanent. - Certification - Product and configuration training for your team, with an exam and a certificate. - Sales and marketing - Demo scripts, decks, reference stories and joint appearances on your channels. - A named contact - One person for both technical and commercial questions. No ticket queue. **Is this you: Who earns most with us** If you recognise your business in one of these profiles, we should talk. - Quality and lean consultancies - You advise on VDA 6.3, IATF 16949, 5S or continuous improvement, and your clients keep asking for a tool to run it. - Auditors and assessors - You assess sites and see exactly where evidence and corrective actions disappear into spreadsheets and mail attachments. - System houses and integrators - You look after ERP, MES or IT for mid-sized manufacturers and need a product for the shop floor between those systems. - Associations and networks - You reach many companies in one industry and want to offer members real value, not just a discount. - Distributors in new markets - You know a market where we have no presence yet and want to build it yourself. - Machine and plant builders - You deliver the equipment and want to sell maintenance, inspection and field service as your own service. **Partner program questions** - What does it cost to join the partner program? - Nothing. There is no joining fee, no revenue commitment and no minimum volume. We earn when you earn. - Do you pay retainers, setup or upfront fees? - No. We pay on results only: commission on closed and paid business. Retainers, setup fees, monthly flat fees and lead generation budgets are not part of the program. If your model requires payment upfront, we are not a fit. We would rather say that now than after three calls. - When and how is commission paid? - Once the customer has paid us, settled monthly. As a referral partner you receive 10% of the first-year contract value, paid once. As a reseller partner you keep a 25% margin on the subscription, recurring for as long as you own the account. - How does deal registration work? - You register the customer by email to partner@mobile2b.com. We confirm within one business day. From that confirmation the lead is protected for you for 90 days. If the deal takes longer and the conversation is live, we extend the protection. - What if the customer is already in your pipeline? - Then we tell you straight away at registration. We never pay a commission twice, and we never hide an existing contact either. In those cases we look for a joint role for you in the project. - Do I need deep technical knowledge? - Only if you want it. As a referral partner you need no product knowledge beyond the demo. For the reseller and implementation tracks certification is required, and it typically takes two days. - Can I offer the platform under my own brand? - White-label is possible for reseller partners. Scope and conditions are agreed in the partner contract, because they depend on volume and hosting model. - Which countries can I sell in? - Historically most of our customers come from Germany, Austria and Switzerland. That describes where we come from, not a limit: we want to grow internationally and are actively looking for partners who will build a new market for us. The platform is multilingual by design, EU hosting and on-premise operation are standard, and where a region has its own data residency requirements we find a way. - How many partners do you take per region? - As many as we can support properly. We do not hand out exclusive territories by default. We do discuss territory protection with partners who demonstrably build a market. ### Book a Demo URL (DE): https://www.mobile2b.com/book-demo URL (EN): https://www.mobile2b.com/en/book-demo Summary: See in 30 minutes how Mobile2b digitizes your processes. No sales pitch - a real demo with your use cases. **What to Expect** ## Audit type guides ### LPA software for Layered Process Audits URL (DE): https://www.mobile2b.com/audits-inspections/layered-process-audit URL (EN): https://www.mobile2b.com/en/audits-inspections/layered-process-audit Summary: Run Layered Process Audits per CQI-8 digitally. Automatic layer scheduling, mobile execution, escalation and live dashboards. Offline, on-premise, made in Germany. **What is a Layered Process Audit?** A Layered Process Audit (LPA) is a systematic quality assurance tool where processes are regularly reviewed by multiple management levels. Unlike traditional audits conducted once a year by specialists, LPAs are short, frequent checks by all levels of management - from team leads to plant managers. **The Layers of an LPA** Each level has a specific role and frequency. The overlay of these layers creates a tight net of quality assurance. **Why Layered Process Audits Work** LPA isn't just "another audit". The multi-layered system creates effects that traditional audits cannot achieve. **CQI-8: The Standard Behind LPA** While CQI-8 originates from the automotive industry, its principles are universally applicable. Any company with standardized processes benefits from a multi-layered audit system. - How LPA questions are developed and prioritized - What frequency is appropriate for each management level - How deviations are documented and escalated - Which KPIs measure the success of the LPA program - How LPA integrates into existing quality management systems **Implementing LPA Successfully - Step by Step** **Common Challenges - and How to Solve Them** **LPA Software: Digital LPA with Mobile2b** Paper and Excel eat the LPA, not the shift. Mobile2b digitizes the process from automatic layer scheduling to management review. Magna Powertrain saves 2,500 hours per year by digitizing the entire audit process. **Frequently Asked Questions About Layered Process Audits** ### VDA 6.3 Process Audit: Complete Guide URL (DE): https://www.mobile2b.com/audits-inspections/vda-6-3-process-audit URL (EN): https://www.mobile2b.com/en/audits-inspections/vda-6-3-process-audit Summary: Process elements P1 to P7, turtle diagram, scoring methodology, and practical execution for quality managers in automotive. **What is VDA 6.3?** VDA 6.3 is the process-oriented audit standard of the German Association of the Automotive Industry (VDA) for the supply chain. First published in 1998 and currently issued as VDA 6.3:2023, the standard describes how production processes at suppliers are systematically evaluated - not whether a quality management system exists, but whether processes are actually capable and stable. VDA 6.3 is not a certification standard like ISO 9001 or IATF 16949. It is an audit tool used by OEMs and tier-1 suppliers to assess and ensure process quality throughout the supply chain. A successful VDA 6.3 audit is a prerequisite for series approval or new business awards in many German OEM supply chains. Who needs VDA 6.3?: Any supplier delivering parts or services to German OEMs (VW, BMW, Mercedes, Porsche, Audi) or their tier-1 suppliers must be prepared for VDA 6.3 audits. The standard applies to production processes, logistics processes, and explicitly to service processes as well. The 2023 edition adds software aspects, purchasing in P3/P4, and notes on remote audits. For product-level verification (rather than process evaluation), see VDA 6.5, the companion standard for product audits. **What a successful VDA 6.3 audit delivers** VDA 6.3 is more than a compliance exercise. Suppliers who take the standard seriously see measurable improvements in quality, delivery performance, and customer satisfaction. - Supplier approval and contract wins - Many OEMs and tier-1 suppliers require a VDA 6.3 audit with a minimum result (typically a B rating or better) as a prerequisite for series approval. A well-prepared supplier wins contracts that less capable competitors lose. - Process stability and zero-defect goal - The VDA 6.3 methodology forces a deep look at process risks, failure modes, and control measures. Suppliers who audit seriously identify weaknesses before the customer does. - Early warning system for the supply chain - The structured evaluation of process elements P1-P7 surfaces risks in planning, procurement, personnel, production, and shipping - preventively, not after a customer complaint. - Objective supplier evaluation - The standardized scoring system (0-10 per question) enables supplier comparisons. Procurement can quantify risk and steer supplier development activities with precision. - Foundation for continuous improvement - VDA 6.3 audits deliver structured findings with prioritization. Every improvement potential becomes a concrete action. Regular re-audits make progress measurable. - Reduction in quality costs - Defects identified during process assessment cost a fraction of those that reach series production. The 1-10-100 rule applies especially in automotive with its high rework and recall costs. **The seven process elements P1 to P7** VDA 6.3 divides a supplier's entire value stream into seven process elements. P1 and P2 cover the customer project management and product development phase (APQP/PPAP). P3 through P7 apply to the ongoing series process. Each element is assessed with a set of questions requiring observable evidence - no self-declarations, no pure document reviews. P1 (Potential Analysis) evaluates the supplier's basic prerequisites: management system, financial stability, technical competence. P2 (Project Management) checks whether product development and launch planning are structured. P3 assesses FMEA and control plan development. P4 evaluates sampling and series launch. P5 (Supplier Management) reviews the supplier's own procurement management. P6 (Process Analysis/Series Production) is the core element: evaluation of the running manufacturing process using the turtle diagram. P7 (Customer Service/Satisfaction) assesses complaint handling and continuous improvement. **Conducting a VDA 6.3 audit: step by step** A structured approach is critical - for both auditor and supplier. These six phases cover the complete audit execution. - Audit preparation and questionnaire selection - The auditor selects the relevant questionnaire (series process, service, or project) and aligns scope with the supplier. Control plans, FMEAs, and process flow diagrams are requested in advance. The supplier prepares evidence - not to stage appearances, but as an efficiency measure. - Opening meeting and process overview - The auditor gains an overview of the production process using the turtle diagram structure: inputs, outputs, resources (machines, personnel, materials), methods, and measurement. This step prevents critical sub-processes from being overlooked during the audit. - Process walkthrough and questionnaire completion - At the heart of the audit, questions are evaluated directly at the process. Each question receives 0, 4, 6, 8, or 10 points - no intermediate values. Deviations are documented with specific findings, not just point deductions. - Completing the turtle diagram - The turtle diagram is the central analysis tool for P6. It visualizes for each sub-process: inputs, outputs, resources (equipment, personnel, environment), methods (work instructions, standards), and metrics (KPIs, inspection characteristics). Gaps in the turtle diagram are direct audit findings. - Scoring, degradation rules, and overall result - The overall result is the percentage of points achieved. Degradation rules apply when individual questions score 0: a zero on a key question can degrade the overall result to B or C regardless of the average. Classes: A (100-90%), B (89-75%), C (below 75%). Class C typically means immediate escalation to the customer. - Action plan, re-audit, and approval - All findings lead to an action plan with owners, deadlines, and effectiveness evidence. Re-audits verify implementation through process walkthrough, not self-declaration. Supplier approval can only be granted after a successful re-audit. **Common weaknesses - and how to fix them** The same weaknesses recur across hundreds of VDA 6.3 audits. Here are the most frequent ones - and how suppliers address them systematically. - Control plan and FMEA not synchronized with the actual process - FMEAs and control plans must be living documents, not one-time PPAP submissions. Implement a change management process that automatically triggers an FMEA review whenever a process change occurs. Mobile2b can map this workflow digitally. - Missing or incomplete process parameter monitoring (P6) - Critical process parameters must be monitored statistically (SPC), not just visually inspected. Define control charts for key parameters and train operators to interpret them. Cp/Cpk values below 1.33 for class A characteristics are an immediate audit finding. - Supplier management (P5) without own audit activities - Sub-suppliers are explicitly evaluated in VDA 6.3. If you do not conduct your own supplier audits, you will lose points. Build a pragmatic supplier audit program - digital support minimizes the effort. - Action plans without effectiveness verification - An action plan is only as good as its follow-up. OEMs explicitly evaluate the effectiveness of corrective actions. Document not just the action, but the effectiveness check with date and measurement result. Digital systems enforce this evidence in a structured way. **Conducting VDA 6.3 audits digitally** Paper-based VDA 6.3 audits in Excel are error-prone, time-consuming, and produce no analyzable data. Mobile2b digitizes the entire audit process - from questionnaire to action plan. - Digital VDA 6.3 questionnaire with scoring logic - The complete VDA 6.3 questionnaire (P1-P7) is digitally mapped. Scoring rules (0/4/6/8/10 points), degradation logic, and automatic overall calculation are built in. No manual calculation, no transcription errors. - Digital turtle diagram capture - Create turtle diagrams for each sub-process directly in the audit. Photos, notes, and findings are assigned directly to the diagram. Gaps in process understanding become immediately visible. - Automatic action plan and tracking - Every finding automatically generates an action with owner and deadline. Re-audit dates are planned automatically. Effectiveness evidence is captured and documented in a structured way. - Supplier dashboard and benchmarking - All audit results across all suppliers in one view. Trend analysis, weakness comparison, and risk traffic light at the click of a button. Supplier development becomes measurable and manageable. **Frequently asked questions about VDA 6.3** - What is the difference between VDA 6.3 and IATF 16949? - IATF 16949 is a certification standard for quality management systems - it describes what system requirements a company must meet. VDA 6.3 is a process audit standard that evaluates whether actual production processes are capable and stable. Both complement each other: IATF 16949 is the 'what', VDA 6.3 is the 'how'. Many OEMs require both. - How long does a VDA 6.3 audit take? - A complete process audit (P1-P7) typically takes 1-3 days depending on the complexity of the production process and the number of production lines. A pure P6 audit for a familiar supplier can be compressed to one day. Preparation (document review, questionnaire selection) requires an additional 0.5-1 days. - What does a C rating in VDA 6.3 mean? - A C rating (below 75%) means the process is not sufficiently capable. In practice this leads to immediate customer escalation, a supplier development plan with binding deadlines, and often increased incoming inspections at the customer. A C rating threatens existing orders and prevents new business awards. - What are degradation rules in VDA 6.3? - Degradation rules can lower the overall result to B or C despite a good average, if certain critical questions score 0 points. Specifically: if a key question scores 0, the overall result cannot be A - regardless of how well all other questions scored. - Do I as a supplier need to master VDA 6.3 myself? - Yes. Suppliers who only experience VDA 6.3 audits reactively are permanently at a disadvantage. Knowing the standard lets you proactively close gaps, pass audits without surprises, and conduct supplier audits within your own supply network (P5 requirement). Internal VDA 6.3 audits before the customer audit are best practice. - Which edition of VDA 6.3 applies? - The current volume is VDA 6.3:2023. The 2016 edition has been superseded. Auditors need the corresponding upgrade before auditing to 2023. Service processes and software suppliers remain in scope; the binding questionnaire is the VDA volume. ### VDA 6.3 Potential Analysis: Guide URL (DE): https://www.mobile2b.com/audits-inspections/vda-6-3-potential-analysis URL (EN): https://www.mobile2b.com/en/audits-inspections/vda-6-3-potential-analysis Summary: How the potential analysis works, when to use it instead of the full process audit, and how the traffic light system supports supplier decisions. **What is the VDA 6.3 Potential Analysis?** The VDA 6.3 Potential Analysis (P1) is a pre-qualification check used before a new supplier enters series delivery, or before an existing supplier takes on a new product. It does not evaluate whether a process is already running - it assesses whether the company has the potential to reliably build and operate the required processes. The potential analysis is shorter and less demanding than a full VDA 6.3 process audit because no series process yet exists to evaluate. The focus is instead on: management system, technical competence, capacity, personnel qualification, financial strength, and the ability to execute a structured product development process. The result is a risk assessment: is this supplier an acceptable risk for our supply chain? When is the potential analysis used?: Typical triggers: a new supplier is added to the Approved Supplier List, an existing supplier is assigned a new product program outside their established competence, a supplier is being reactivated after a period of inactivity, or a supplier from a new sourcing region is being evaluated. In many OEM procurement guidelines, the potential analysis is mandatory before the first PPAP approval. **Why the potential analysis prevents bad decisions** Supplier decisions based on data sheets and self-declaration are risky. The structured potential analysis provides objective decision-making input. - Risk-based supplier selection instead of gut feel - The potential analysis quantifies risks invisible during the quoting phase: QMS maturity, availability of qualified specialists, capacity reserves, experience with OEM-specific core tools. A yellow or red result before contract signing is worth more than a C rating after launch. - Early definition of development requirements - The potential analysis identifies not just whether a supplier is suitable, but where targeted development actions are needed. These can become part of the supply contract: the supplier commits to defined improvements as a condition for nomination. - Objectifying the purchasing decision - Buyers make supplier decisions under price pressure. The potential analysis delivers quality risk as a quantified unit that feeds into the total cost of ownership calculation. A cheap supplier with a red potential rating is more expensive than a more costly one with a green rating. - Compliance with OEM procurement guidelines - Many OEM procurement guidelines explicitly require potential analyses for new suppliers. Documented execution protects procurement in the event of later delivery problems and is part of supplier qualification documentation for external audits. - Comparability across suppliers and regions - Whether a supplier is in Bavaria, Poland, or China - the VDA 6.3 P1 scoring scheme is uniform. Supplier quality engineers can compare results from different auditors without concerns about subjective bias. - Foundation for the development plan in APQP - Identified gaps from the potential analysis feed directly into the APQP plan. Weaknesses in the supplier's process development capability require increased SQE involvement in the early APQP phases. **Potential analysis vs. full process audit** The decisive difference lies in the subject of evaluation. The potential analysis (P1) assesses prerequisites and capabilities - it looks at the management system, technical equipment, personnel, and process competence of the company, without a specific series process yet existing. The full VDA 6.3 process audit (P2-P7) evaluates the actual series process based on concrete process parameters, control plans, FMEAs, and measurement results. In practice, the potential analysis follows a different timeline: it takes place before nomination, while the full process audit is conducted before or shortly after series launch. A typical supplier qualification sequence: potential analysis (P1) before nomination, SQE support during APQP, process audit (P2-P7) before PPAP, re-audit after 12-24 months in series. Both instruments are not alternatives - they are complementary tools used at different points in time. **Conducting a potential analysis in a structured way** From scheduling to the final report - this is how a professional VDA 6.3 potential analysis is conducted. - Clarify scope and trigger - Define clearly why the potential analysis is being conducted: new supplier, new product, reactivation? Which product range and manufacturing processes are relevant? This clarity determines which question areas need to be assessed in greater depth. - Request documents in advance - Before the on-site visit, request: certificates (IATF 16949, ISO 9001, industry-specific), quality metrics from the last 12 months (PPM, complaint rate), org chart and qualification evidence for key personnel, list of key customers with OEM references, equipment inventory and calibration records. Document analysis saves time on-site and focuses the walkthrough. - On-site: management interview - Begin with a structured interview with management and quality leadership. Objectives: understand quality policy and goals, assess resource planning, gauge commitment to OEM requirements. Vague answers to specific questions are themselves a scoring point. - Process walkthrough and resource assessment - Walk through the relevant production areas. Look for: cleanliness and organization (5S maturity), availability and condition of measuring equipment, qualification evidence at workstations, handling of nonconforming parts, labeling and traceability. What you see is more telling than any documentation. - Scoring with the traffic light system - Each question group is rated green (fulfilled), yellow (conditionally fulfilled, development needed), or red (not fulfilled, knockout criterion). The overall result is a combination of individual ratings. A single red result on a knockout criterion leads to an overall red rating - regardless of all other results. - Closing meeting, report, and recommendation - Present results transparently in the closing meeting. The written report contains: overall rating (red/yellow/green) with rationale, list of all gaps with prioritization, a concrete recommendation (approval, conditional approval, no approval), and any conditions for nomination (development plan with deadlines). **Common mistakes in the potential analysis - and how to avoid them** The potential analysis is often treated as a formality. These four mistakes cost time, money, and nerves later. - Potential analysis as a box-ticking exercise with no real consequences - If a supplier is nominated despite a yellow or red rating because the price is right, the instrument loses its value. Anchor the potential analysis as a binding decision input in the procurement policy. Exceptions must be approved by management - not by the buyer alone. - Evaluation based on documents rather than observation - Certificates and manuals say nothing about what actually happens on the shop floor. The potential analysis requires an on-site walkthrough. What is on paper and what is lived in production often diverge significantly. Auditors who skip the factory walkthrough systematically underestimate risk. - No follow-up on conditional development requirements - Yellow ratings with conditions are only useful if the conditions are actually followed up. Define clear milestones - who does what by when - and schedule a re-audit or evidence review. Without follow-up, the yellow rating is effectively a green approval. - No alignment between potential analysis and the later process audit - Findings from the potential analysis should feed into the subsequent VDA 6.3 process audit. Areas rated weak in the potential analysis require special attention in the process audit. A digital system linking both audits makes this connection visible automatically. **Potential analyses - digital and standardized** Manual potential analyses with Word templates and email attachments are error-prone and not analyzable. Mobile2b digitizes the entire process - from pre-documentation to the supplier dashboard. - Digital P1 questionnaire with traffic light scoring - The VDA 6.3 P1 questionnaire is fully digitized. Traffic light scoring (red/yellow/green) with automatic knockout criteria logic. The overall result is calculated automatically, degradation rules applied automatically. - Document management before the on-site visit - Suppliers can upload documents in advance (certificates, quality metrics, org charts). The auditor sees all documents structured before the on-site visit. Missing documents are directly flaggable as findings. - Development requirements with automatic deadline monitoring - Every yellow or red rating automatically generates a development action with owner and deadline. Reminders go automatically to the supplier and SQE. Re-audit dates are proposed and tracked. - Link to the subsequent process audit - Findings from the potential analysis are visible in the later process audit (P2-P7). SQEs see at a glance which areas scored weak in the potential analysis and where to focus in the process audit. **Frequently asked questions about the VDA 6.3 potential analysis** - Who is authorized to conduct a VDA 6.3 potential analysis? - VDA 6.3 recommends that auditors hold a VDA 6.3 qualification. In practice, supplier quality engineers (SQEs) conduct the potential analysis - often with internal training provided by the OEM or tier-1. For external certification audits, a VDA-authorized assessor is required, but internal supplier audits can be conducted by qualified SQEs. - What is the difference between a potential analysis and a system audit? - A system audit (e.g., per ISO 9001 or IATF 16949) checks whether a quality management system meets normative requirements. The VDA 6.3 potential analysis is process-oriented and evaluates a supplier's actual capability to build and control a specific production process. System audits and potential analyses provide complementary information. - How long is a potential analysis valid? - There is no normatively defined validity period. In practice, OEMs assume 12-24 months before a reassessment is required - or immediately if the supplier's situation changes materially (ownership change, site relocation, major capacity changes). A green result from three years ago is no guarantee of the current state. - Can a supplier refuse a potential analysis? - Formally possible, but in practice it leads to non-nomination. In OEM supply chains, willingness to participate in a potential analysis is typically part of the supplier agreement or Approved Supplier List requirements. A supplier that refuses transparency is itself an elevated risk. - What happens with an overall red result? - A red overall result typically leads to non-nomination or non-award. Sometimes a development plan is agreed upon with defined improvements required before a re-audit. The decision lies with procurement and quality leadership - not with the auditor. The auditor documents the finding; the consequence is a management decision. - Are there industry-specific variants of the potential analysis? - VDA 6.3 applies primarily to the automotive industry. Other industries (aerospace, medical devices, defense) have their own equivalent instruments. The underlying principle - structured pre-qualification of supplier capability - is universal. Mobile2b can map industry-specific questionnaires, not just VDA 6.3. ### VDA 6.5 Product Audit: Complete Guide URL (DE): https://www.mobile2b.com/audits-inspections/vda-6-5-product-audit URL (EN): https://www.mobile2b.com/en/audits-inspections/vda-6-5-product-audit Summary: How to plan, execute, and evaluate product audits according to VDA 6.5. Sampling strategies, measurement techniques, and practical scoring for automotive quality managers. **What is VDA 6.5?** VDA 6.5 is the product audit standard of the German Association of the Automotive Industry (VDA). While VDA 6.3 evaluates processes and IATF 16949 certifies management systems, VDA 6.5 focuses on the finished product itself. The question is simple: does the product that reaches the customer actually meet all specified requirements? A product audit checks finished goods or near-finished assemblies against drawings, specifications, packaging instructions, and labeling requirements. Auditors take random samples from production or the finished goods warehouse and verify dimensional accuracy, surface quality, material properties, functional characteristics, and correct identification. VDA 6.5 provides the methodology: how to select samples, what to measure, how to score findings, and how to translate results into corrective action. How VDA 6.5 relates to VDA 6.3 and IATF 16949: These three standards work together. IATF 16949 (clause 8.6.2) explicitly requires product audits as part of the quality management system. VDA 6.3 process audits evaluate whether processes are capable; VDA 6.5 product audits verify whether that capability actually translates into conforming products. A strong process audit result with recurring product audit failures points to a gap between documented processes and shop-floor reality. **What product audits deliver** Product audits are the final verification before your product reaches the customer. Done well, they protect your reputation and reduce costs. Done poorly or skipped entirely, they leave your worst defects for the customer to discover. - Catch defects before shipment - Product audits inspect finished goods against every specification: dimensions, surface, function, packaging, labeling. Defects caught here cost a fraction of what they cost after delivery. In automotive, the ratio is roughly 1:10:100 between production, customer, and field failure. - Validate process capability in practice - A stable Cpk value on the control chart does not guarantee every part is good. Product audits verify the actual output. When SPC says the process is capable but the product audit finds issues, you know your measurement system, sampling plan, or process control needs attention. - Meet OEM and IATF 16949 requirements - IATF 16949 clause 8.6.2 requires product audits at appropriate intervals. German OEMs (VW, BMW, Mercedes) and their tier-1 suppliers expect documented product audit results. Not having a systematic product audit program is a certification risk. - Prioritize corrective actions with data - Product audit findings are scored and categorized. Critical findings (safety, function) trigger immediate containment. Minor findings (cosmetic, labeling) feed into continuous improvement. The structured scoring helps you allocate resources where they matter most. - Build customer confidence - When a customer visits your facility, a documented product audit program with trend data and closed corrective actions signals maturity. It demonstrates that you verify your own output systematically, not just when complaints arrive. - Drive continuous improvement with trend data - Individual audits reveal problems. Audit trends reveal patterns. Monthly product audit scores by product group, defect category, and production line show where quality is improving and where it is not. This data feeds 8D reports, management reviews, and supplier discussions. **How a VDA 6.5 product audit works** A product audit is not a 100% inspection. It is a systematic sample-based verification of finished products against all specified requirements. The auditor selects samples according to a defined plan (risk-based sampling, not random), then checks each sample against the complete specification: dimensions, material, surface, function, identification, and packaging. Each characteristic is evaluated and deviations are classified by severity: A-defects (critical, safety or function relevant), B-defects (major, functional limitation or significant cosmetic issue), and C-defects (minor, cosmetic or documentation). The audit result is a quality index (QKZ) calculated from the number and severity of findings relative to the sample size. This index is tracked over time and compared against target values. VDA 6.5 does not prescribe a fixed pass/fail threshold. Each organization sets its own target based on product risk and customer requirements. **Conducting a VDA 6.5 product audit: step by step** A well-structured product audit follows six phases. Each phase builds on the previous one to ensure consistent, comparable, and actionable results. - Define the audit plan and sampling strategy - Select which products to audit based on risk: new product launches, products with recent complaints, high-volume parts, and safety-critical components get higher audit frequency. Define sample sizes proportional to production volume and quality history. Document the plan so audits are scheduled, not ad hoc. - Prepare the audit checklist and specifications - Collect all relevant specifications for the product: drawings with tolerances, material specifications, packaging instructions, labeling requirements, customer-specific requirements (CSRs). Build the audit checklist from these documents. Every characteristic that can be verified on the finished product belongs on the checklist. - Sample selection and identification - Pull samples from the finished goods area or end-of-line. Record the production date, batch, machine, and shift for traceability. Do not sample from a curated display area. The goal is to evaluate what the customer will actually receive. - Execute measurements and inspections - Work through the checklist systematically. Verify dimensions with calibrated gauges, check surface quality visually and by touch, test functional characteristics, verify material certificates if applicable, and inspect packaging and labeling. Record actual values, not just pass/fail. Actual values enable trend analysis. - Classify findings and calculate the quality index - Categorize each deviation as A (critical), B (major), or C (minor). Calculate the quality index (QKZ) using the VDA 6.5 formula: QKZ = (number of deviations weighted by severity) / (number of inspected characteristics x sample size) x 100. A lower QKZ means better quality. Compare against your target value. - Initiate corrective actions and close the loop - A-defects require immediate containment: stop shipment, sort stock, notify the customer if affected product was shipped. B-defects trigger 8D or problem-solving activities. C-defects are logged for trend review. Every finding gets an owner, a deadline, and a verification step. Re-audit to confirm effectiveness. **Common product audit pitfalls** Product audits seem straightforward, but these four mistakes undermine their value. Each one reduces audit credibility and allows defects to reach customers. - Sampling only "good" products - Audit samples must come from normal production flow or the finished goods warehouse, not from pre-selected or reworked batches. Biased sampling produces artificially good scores and hides real quality issues. Define the sampling point in the audit plan and audit it. - Incomplete specification coverage - Checklists that only cover dimensional characteristics miss packaging, labeling, surface, and functional requirements. Build the checklist from the complete specification set: drawing, material spec, packaging instruction, CSR, and any additional customer requirements. Review the checklist annually or when specifications change. - Treating audits as pass/fail instead of trend data - A single product audit score tells you very little. The value is in the trend: is quality improving, stable, or declining? Track QKZ monthly by product group, defect category, and production line. Present trend charts in management reviews, not single-point scores. - No link between findings and corrective action - Audit findings without follow-up are waste. Every A and B finding needs a problem-solving activity (8D, 5 Whys, Ishikawa) with a defined owner and deadline. Track closure rates. If findings recur, the corrective action was ineffective. Escalate recurring findings to management review. **Mobile2b for Product Audits: Digital product audits with Mobile2b** Replace paper checklists and spreadsheet tracking with a system that connects audit execution, scoring, corrective actions, and trend analysis in one place. - Configurable product audit checklists - Build checklists from your specification documents with dimensional, visual, functional, and packaging characteristics. Define measurement types, tolerances, and severity classifications per characteristic. Reuse and version checklists across product groups. - Automatic QKZ calculation and scoring - Enter measurement values and deviations during the audit. Mobile2b calculates the quality index automatically, classifies findings by severity, and compares the result against your target value. No more spreadsheet formulas. - Integrated corrective action tracking - Create 8D reports or corrective actions directly from audit findings. Assign owners, set deadlines, attach evidence photos. Track closure rates and verify effectiveness through re-audit results. Nothing falls through the cracks. - Trend dashboards and management reporting - QKZ trends by product, line, and defect category are generated automatically. Export reports for management reviews, customer presentations, or IATF 16949 certification audits. Historical data is always available, no more searching through archived spreadsheets. **Frequently asked questions about VDA 6.5** - What is the difference between VDA 6.3 and VDA 6.5? - VDA 6.3 is a process audit standard that evaluates whether manufacturing and management processes are capable and controlled. VDA 6.5 is a product audit standard that checks whether the finished product actually meets its specifications. One evaluates how you produce, the other evaluates what you produce. - Is VDA 6.5 mandatory for IATF 16949 certification? - IATF 16949 clause 8.6.2 requires product audits at appropriate intervals. It does not prescribe VDA 6.5 specifically, but the VDA 6.5 methodology is the most widely used approach in the German automotive supply chain. Certification bodies expect a documented, systematic product audit program. - How often should product audits be conducted? - The frequency depends on product risk, production volume, and quality history. High-risk or safety-critical products may require weekly audits. Stable, mature products might be audited monthly or quarterly. New product launches should be audited more frequently during the ramp-up phase. Define the frequency in your audit plan and adjust based on results. - What sample size is required for a product audit? - VDA 6.5 does not prescribe a fixed sample size. The sample should be large enough to be representative of the production lot. Common approaches use AQL tables (ISO 2859) or risk-based sampling where higher-risk products get larger samples. Start with at least 5 samples per audit and increase based on findings. - Who should conduct product audits? - Product auditors need knowledge of the product specifications, measurement techniques, and the defect classification system. They should be independent of the production area being audited. In practice, quality engineers, quality technicians, or trained auditors from adjacent departments perform product audits. - How do product audit results relate to customer PPM targets? - Product audit results and customer PPM (parts per million defective) track different things, but they should correlate. If your product audit QKZ is improving but customer PPM is not, your audit is likely missing characteristics that the customer checks, or your sampling strategy does not cover the right failure modes. Use customer complaints to refine the audit checklist. ### IATF 16949: Automotive Quality Standard URL (DE): https://www.mobile2b.com/audits-inspections/iatf-16949 URL (EN): https://www.mobile2b.com/en/audits-inspections/iatf-16949 Summary: Requirements, certification process, core tools, and practical implementation - the complete guide for quality managers in the automotive supply chain. **What is IATF 16949?** IATF 16949 is the international quality management system standard for the automotive industry, issued by the International Automotive Task Force (IATF). Since 2016 it replaces the predecessor standard ISO/TS 16949 and extends ISO 9001:2015 with automotive-specific requirements. Over 60,000 sites worldwide are certified to IATF 16949. IATF 16949 is effectively mandatory for suppliers to OEMs that are members of the IATF (BMW Group, Daimler, FCA, Ford, General Motors, PSA Group, Renault, Volkswagen Group, and others). Without a valid IATF 16949 certification, listing as a series supplier is not possible in most OEM supply chains. The standard defines requirements for the entire QMS - from product planning through manufacturing to customer service. IATF 16949 vs. ISO 9001: what is the difference?: IATF 16949 contains all requirements of ISO 9001:2015 - it is a superset. In addition to the ISO 9001 base, IATF 16949 adds automotive-specific requirements: product safety, in-vehicle software development, core tools (APQP, FMEA, MSA, SPC, PPAP), customer-specific requirements (CSR), traceability, manufacturing feasibility, and specific launch requirements. An IATF 16949 certification includes ISO 9001 - but not the other way around. **What IATF 16949 means for your company** Certification is not the goal - process capability is. Companies that genuinely live IATF 16949 see measurable results. - Market access to the automotive supply chain - No IATF 16949 certificate, no contract. For suppliers entering automotive or securing existing customer relationships, certification is the baseline requirement. It opens doors to OEMs and tier-1 suppliers worldwide. - Reduced customer audits - OEMs and tier-1 suppliers reduce their own supplier audits for IATF-certified suppliers. This saves the supplier resources - less audit preparation, less visit overhead - and signals a proven quality level to the customer. - Structured framework for continuous improvement - IATF 16949 explicitly requires measurable quality goals, trend analyses, and continuous improvement projects. Companies that take the standard seriously build a structured CIP process that grows beyond the certification requirement. - Enforced engagement with core tools - IATF 16949 mandates the use of core tools (APQP, FMEA, MSA, SPC, PPAP). Companies that master these tools make better product development decisions, identify process risks earlier, and deliver more stable quality. - Global supply chain harmonization - A single standard worldwide enables suppliers in China, Mexico, and Germany to be evaluated against the same criteria. This simplifies global sourcing, reduces quality risk from differing requirement interpretations, and makes audits by external assessors easier. - Foundation for product safety and liability protection - IATF 16949 includes specific requirements for product safety management (Safety Characteristics, Customer Safety Representatives). In the event of a claim, documented conformity with the standard protects against liability risk and demonstrates due diligence to authorities and courts. **The five core tools of IATF 16949** IATF 16949 mandates the use of five core tools standardized by AIAG and VDA. APQP (Advanced Product Quality Planning) structures product development in five phases and ensures quality requirements are addressed at the design stage. PPAP (Production Part Approval Process) is the formal approval procedure for production parts - it consists of up to 18 evidence elements that the supplier presents before series launch. FMEA (Failure Mode and Effects Analysis) is the structured risk analysis for design and process - since 2019 in the harmonized AIAG/VDA format with five-level scoring (S/O/D) and action priorities (H/M/L) instead of RPN. MSA (Measurement System Analysis) ensures that measurement systems actually measure what they are supposed to measure - Gage R&R studies and calibration evidence are explicit IATF 16949 requirements. SPC (Statistical Process Control) monitors running production processes statistically to detect process drift before defects occur. Cp/Cpk values of at least 1.33 (for critical characteristics) are typical OEM minimum requirements. All five core tools are interlinked: APQP defines the framework, FMEA identifies risks, the control plan is derived from the FMEA, MSA validates measurement systems, SPC monitors the series process, PPAP documents the result. **The IATF 16949 certification process** From the decision to certify to a valid certificate - these six phases cover the entire process. - Gap analysis and project planning - Start with a structured gap analysis against IATF 16949:2016. Where does your current QMS deviate from the standard's requirements? Which core tools are not or not fully implemented? Prioritize gaps by effort and risk. Plan realistically: initial implementation without an ISO 9001 base takes 12-18 months; with an existing ISO 9001 certification, 6-12 months. - Building the QMS and core tools - Implement the IATF-specific requirements beyond the ISO 9001 base: revise the quality manual and process map, introduce or revise APQP processes, FMEA in AIAG/VDA format, PPAP process, MSA studies for all relevant measurement systems, SPC for critical characteristics. Train all relevant employees - IATF 16949 places particular emphasis on competence evidence. - Internal audits per IATF 16949 - IATF 16949 requires three distinct internal audit types: system audits (conformity with the standard), process audits (effectiveness of manufacturing processes), and product audits (product conformity with specifications). All three must be planned and conducted before the certification audit. Completion rate and deviation tracking are checked in the certification audit. - Management review - The IATF 16949 management review has specific required content: quality goals and achievement, customer complaints and field failures, internal and external audit findings, supplier performance, risks and opportunities. The minutes must demonstrably cover these points. Missing content items are typical minor nonconformities in the certification audit. - Stage 1 and Stage 2 audit by the certification body - Stage 1 (document review) evaluates whether the QMS is fully documented and addresses the standard's requirements. Stage 2 (implementation audit, 2-5 days depending on company size) checks whether the system is actually being lived. Nonconformities are classified as Major (blocking certification) or Minor (correction within 60 days). Customer-specific requirements (CSR) of relevant OEMs are explicitly checked. - Surveillance audits and recertification - The IATF 16949 certificate is valid for three years, with annual surveillance audits. These sample the QMS and respond to customer complaints or recalls. Zero tolerance applies to: missing internal audits, unresolved major nonconformities from prior year audits, and missing management reviews. After three years, the recertification audit follows. **Typical nonconformities in IATF 16949 audits - and how to avoid them** These four nonconformities appear disproportionately often in IATF 16949 audits. Knowing them allows targeted preparation. - Customer-specific requirements (CSR) not fully identified and implemented - Every OEM publishes CSRs that go beyond IATF 16949 (e.g., VW Group: Formel Q, BMW: VDA 6.3 audit requirement, Ford: MMOG/LE for logistics). These CSRs must be identified, transferred into internal process documentation, and demonstrably implemented. Create a CSR matrix mapping customer requirements to internal processes. - FMEA and control plan not kept current after process changes - Change management is a core requirement of IATF 16949. Every process change - new material, new supplier, changed machine settings - must trigger an FMEA review before the change goes live. Implement a change control process with documented FMEA review and updated control plan as a release prerequisite. - Internal audits not covering all three audit types - IATF 16949 explicitly requires system, process, and product audits. Many companies only conduct system audits and miss the obligation to audit processes and products. Create an annual audit plan covering all three types and all processes within a three-year cycle. The completion rate is checked in the certification audit. - Inadequate supplier development and missing supplier monitoring - IATF 16949 requires active supplier management: supplier evaluation, risk-based supplier classification, development actions for underperforming suppliers, and supplier audits for high-risk suppliers. Many companies have supplier evaluations on paper but no demonstrable development work. This is a typical minor to major nonconformity. **Managing IATF 16949 audits digitally** IATF 16949 requires complete documentation, demonstrable completion rates, and structured deviation tracking. Mobile2b digitizes these requirements in full. - Three audit types in one system - Plan, execute, and document system, process, and product audits per IATF 16949 in one platform. Annual audit plan with automatic progress tracking. Gaps in the audit program become immediately visible - before the certification body's auditor finds them. - CSR management and requirements mapping - Capture customer-specific requirements (CSR) of relevant OEMs digitally and map them to internal processes. Demonstrable implementation with direct links to process documentation. Audit checklists can be filtered at the CSR level. - Deviation tracking with escalation and deadline management - Every audit deviation - Minor or Major - is documented with owner, root cause analysis, corrective action, and effectiveness evidence. 60-day deadlines for minor deviations are automatically monitored. Overdue actions automatically escalate to the quality director. - Management review prepared automatically - All KPIs required for the IATF 16949 management review - quality goals, audit results, customer complaints, supplier performance - are automatically aggregated. The quality manager prepares the management review at the click of a button instead of manually pulling data from ten sources. **Frequently asked questions about IATF 16949** - Does IATF 16949 apply to tier-2 and tier-3 suppliers? - IATF 16949 primarily targets direct suppliers (tier-1) to OEMs. Tier-2 and tier-3 suppliers are not directly required to hold an IATF 16949 certification - but tier-1 suppliers can pass this requirement down through their CSRs. In practice, many tier-1 suppliers require IATF certification or at least ISO 9001 from their critical tier-2 suppliers. - What is the difference between a Major and a Minor finding? - A Major finding is a serious deviation from a standard requirement that fundamentally undermines the effectiveness of the QMS or exposes the customer to a product safety risk. A Major finding blocks certification and must be resolved before the certificate is issued. A Minor finding is a less critical deviation that must be corrected within 60 days - with effectiveness evidence. - How much does IATF 16949 certification cost? - Costs vary widely by company size, number of sites, and chosen certification body. As a benchmark: a first-time audit for a single site with 200-500 employees typically costs 8,000-20,000 EUR at the certification body, plus internal preparation effort (50-200 person-days depending on starting position). Annual surveillance audit costs are additional. - Can I use ISO 9001 as a stepping stone before IATF 16949? - Yes, and it is a recommended strategy for companies newly entering automotive. ISO 9001 lays the foundation (process documentation, management review, internal audit, CIP) that IATF 16949 builds upon. With a mature ISO 9001 system, the additional effort for IATF 16949 is typically 40-60% of the initial implementation effort. - What are Customer Specific Requirements (CSR) and where do I find them? - CSRs are OEM-specific requirements that go beyond IATF 16949. They are published by OEMs and accessible on the IATF website (iatfglobaloversight.org) and individual OEM websites. Key examples: VW Group Formel Q, BMW Group IATF 16949 Customer Specifics, Ford CSR, General Motors IATF 16949 CSR. CSRs change regularly - a process for continuously monitoring CSR updates is an IATF requirement. - How does the IATF 16949 audit differ from the VDA 6.3 audit? - IATF 16949 audits the quality management system as a whole - strategy, resources, processes, documentation, measurement, and improvement. It is a system audit. VDA 6.3 is a process audit that evaluates the capability of individual production processes - with concrete process parameters, control plans, and measurement results. Both are complementary: IATF 16949 shows whether the system is in place; VDA 6.3 shows whether it works in practice. ### The Complete Guide to Automotive SPICE URL (DE): https://www.mobile2b.com/audits-inspections/automotive-spice URL (EN): https://www.mobile2b.com/en/audits-inspections/automotive-spice Summary: Process reference model, capability levels, and assessment methodology - from the fundamentals to sustainable process improvement in series development. **What is Automotive SPICE?** Automotive SPICE (Software Process Improvement and Capability dEtermination) is a process reference and assessment model developed specifically for software development in the automotive industry. It is based on ISO/IEC 15504 (SPICE) and was adapted by the HIS consortium (Herstellerinitiative Software) of German OEMs for use in series development. The current version is Automotive SPICE 3.1, published in 2017 by the VDA Automotive SPICE working group. The model is today the de facto standard for suppliers with software content in embedded systems. The model distinguishes between the Process Reference Model (PRM), which describes which processes must be present, and the Process Assessment Model (PAM), which describes how their maturity is evaluated. For tier-1 and tier-2 suppliers with software content in safety-critical systems, an Automotive SPICE assessment is today a de facto prerequisite for OEM projects. The HIS scope defines 15 processes that OEMs typically evaluate in supplier assessments. HIS Scope: the relevant process selection for suppliers: The HIS Scope covers 15 processes: SYS.1-SYS.5 (System Engineering), SWE.1-SWE.6 (Software Engineering), MAN.3 (Project Management), SUP.1 (Quality Assurance), SUP.8 (Configuration Management), SUP.9 (Problem Resolution Management), SUP.10 (Change Request Management), and ACQ.4 (Supplier Monitoring). Capability Level 2 in all HIS Scope processes is the minimum requirement of most OEMs. **Why Automotive SPICE is essential for suppliers** Assessments are not a bureaucratic compliance exercise. Mature processes per Automotive SPICE reduce project risk, shorten development cycles, and secure supplier capability. - OEM prerequisite for project access - Without demonstrated Automotive SPICE maturity (typically CL2 in the HIS Scope), suppliers are not qualified in many projects. The assessment result is an integral part of supplier approval and is evaluated across projects. - Reduced project escalations - Mature requirements management and test processes (SWE.1, SWE.6) prevent late requirement changes and costly rework. Suppliers at CL3 demonstrably show significantly fewer field issues than those at CL1. - Traceability from requirement to test - SWE.1 through SWE.6 enforce complete traceability: from stakeholder requirement through software architecture to qualification test. This is simultaneously a prerequisite for ISO 26262 ASIL B/C/D projects. - Structured project management - MAN.3 requires project plans with measurable milestones, resource planning at activity level, and a risk register. This creates transparency for the OEM and reduces schedule overruns through early risk detection. - Configuration management as the traceability foundation - SUP.8 ensures that software versions, tools, and documents are versioned and reproducible. Without this process at at least CL2, reliable tracing of field issues back to defined software versions is not possible. - Continuous process improvement - Automotive SPICE is not a one-time certification goal but an improvement framework. Organizations that regularly assess internally and externally systematically improve their capability level and build a sustainable quality advantage. **Process reference model, PAM, and capability levels in detail** The PRM structures all processes into three groups: Primary Life Cycle Processes (Acquisition, Supply, Engineering), Supporting Life Cycle Processes (Quality Assurance, Configuration Management, Problem Resolution, Change Request), and Organizational Life Cycle Processes (Management, Process Improvement, Reuse). Each process is defined by its purpose and outcomes. The PAM adds measurable Base Practices (BP) and Work Products (WP) to each outcome, which serve as evidence in the assessment. Generic Practices (GP) and Generic Resources (GR) describe what is additionally expected at each capability level. The six capability levels build on each other: CL0 (Incomplete) - process not or only partially implemented. CL1 (Performed) - base practices are executed, process outcomes are achieved, but without systematic management. CL2 (Managed) - additionally: planning, monitoring, control of work, plus verification and configuration management of work products (GP 2.1-2.4). CL3 (Established) - additionally: defined standard process, tailoring guidelines, process description, and use of a process infrastructure (GP 3.1-3.2). CL4 (Predictable) - process performance is quantitatively measured and controlled. CL5 (Innovating) - continuous process innovation based on quantitative analysis. For most OEM projects, CL2 is mandatory; safety-critical systems increasingly require CL3 in engineering processes. **Implementing Automotive SPICE - step by step** A realistic roadmap from gap analysis to a successful assessment - designed for tier-1/2 suppliers with 50 to 500 developers. - Gap analysis against the HIS Scope - Internal assessment of all 15 HIS Scope processes: which base practices exist? Which work products are present and sufficient? The result is a prioritized gap matrix showing where CL1 is not yet achieved and which processes have the greatest distance to the target capability level. - Set target capability level per process - Capture OEM requirements for current and planned projects. Typical target: CL2 for all 15 HIS processes short-term, CL3 for SWE.1, SWE.2, SWE.4, SWE.6, and MAN.3 medium-term. The target level must be set per process - blanket statements without process reference are worthless in an assessment. - Build process definitions and work products - Create process descriptions, templates, and checklists for each HIS process. Work products must conform to a defined format and be stored in a revision-safe way. Special attention goes to the traceability matrix between SWE.1 (software requirements), SWE.2 (architecture), SWE.3 (detailed design), and SWE.6 (qualification test). - Pilot project and internal trial assessments - Pilot processes in a running development project. Internal assessors (intacs-trained practitioners or experienced senior developers) conduct gap assessments and document findings as improvement items. Findings are tracked as projects - with owners, deadlines, and effectiveness evidence. - Build competence for all roles - Automotive SPICE is not a pure QA topic: developers must understand what Unit Test Specification (SWE.4) requires as a work product; testers what a Software Integration Test Report (SWE.5) must deliver; project managers what artefacts MAN.3 requires at CL2. Role-specific training is more efficient than generic SPICE introductions. - External assessment and improvement action plan - An intacs-certified assessor conducts the formal assessment. Every weakness and non-conformance is documented as a finding. The resulting Improvement Action Plan (IAP) is the central management document: findings prioritized by severity, with actions, owners, and target dates. The IAP is checked for implementation at the next assessment. **Typical challenges - and how to solve them** Automotive SPICE implementations rarely fail because of QA knowledge. They fail due to insufficient project applicability of processes and missing tool support. - Processes exist on paper but not in lived project practice - Process definitions without lived practice are worthless - and experienced assessors detect this in minutes of interviewing. The only valid preparation: pilot projects with real documentation, real reviews, and real test results as evidence. Mobile2b makes it possible to maintain audit checklists for each HIS process and document proof of execution with a complete timestamp trail. - Traceability between requirements, design, and tests cannot be established - SWE.1 through SWE.6 require a complete traceability chain as a work product. Without dedicated tool support (Polarion, IBM DOORS, Jama Connect), this is not manageable with more than a few hundred requirements. The traceability matrix must be available for inspection in the assessment at any time - an Excel sheet is evaluated as insufficient from CL2 onward. - MAN.3 fails due to insufficient project plan detail - CL2 in MAN.3 requires more than a milestone plan: resource planning at activity level, a risk register with quantified assessment and countermeasures, regular documented plan-actual comparisons, and defined escalation paths. Generic Practice GP 2.2 (Work Product Management) checks whether the project plan itself is maintained and versioned as a work product. - Assessment preparation ties up too many resources at short notice - Assessment preparation as a sprint before the date creates duplicate work and delivers no sustainable process improvements. Processes must be anchored in daily development work. Digital audit tools enable continuous internal compliance checks per project, so the effort for the formal assessment shrinks to the unavoidable minimum. **Managing Automotive SPICE digitally with Mobile2b** Assessment preparation is not a one-time project but continuous process monitoring. Mobile2b creates the infrastructure to make Automotive SPICE compliance measurable and demonstrable. - HIS Scope checklists for internal assessments - Predefined audit checklists for all 15 HIS Scope processes with direct reference to base practices and generic practices per Automotive SPICE 3.1. Internal trial assessments are conducted in a structured way, findings immediately classified and created as improvement items. - Finding and improvement item tracking - Every weakness and non-conformance from internal or external assessments is captured as an improvement item: process reference, capability level impact, owner, actions, due date, and effectiveness evidence. The Improvement Action Plan is complete and current at all times. - Cross-project capability reporting - Capability level status across all running projects at a glance. Which processes are stable at CL2? Where do multiple projects show the same weaknesses in the same base practices? This is the data foundation for targeted organization-wide improvement initiatives. - Audit trail for external assessors - All internal audit results, findings, action evidence, and improvement histories are stored in a revision-safe way and exportable for external assessors at the click of a button. This accelerates external assessments and demonstrates proactive process management. **Frequently asked questions about Automotive SPICE** - What is the difference between Automotive SPICE and ISO 26262? - Automotive SPICE assesses the maturity of development processes: how well is a process defined, implemented, and controlled? ISO 26262 is a functional safety standard that prescribes specific methods and evidence for safety-critical systems (ASIL A-D). Both standards are complementary: Automotive SPICE maturity (CL2/3) is frequently a prerequisite to conduct ISO 26262-compliant development credibly and demonstrably. - Which capability level is required for OEM projects? - This varies by OEM and system criticality. As a rule of thumb: CL2 in all HIS Scope processes is the minimum requirement for most supplier approvals. CL3 is increasingly required for projects with high safety relevance (ADAS, powertrain, braking systems). Individual OEMs have their own requirement profiles that may deviate from the generic HIS Scope in process selection or target capability level. - How long does preparation for a Level 2 assessment take? - For an organization that already develops in a structured way but has no formal Automotive SPICE experience, 9-18 months is realistic. This includes gap analysis, process definition, pilot project, and internal trial assessments. Organizations with a mature ISO 9001 or IATF 16949 system often have less effort in MAN.3 and SUP.1, but engineering processes (SWE.1-SWE.6) almost always require substantial build-up effort. - What is the difference between an intacs assessment and an OEM assessment? - An intacs assessment (International Assessor Certification Scheme) is conducted by an accredited, independent assessor per the Automotive SPICE PAM and is considered a neutral third-party evaluation. OEM assessments are conducted by the OEM itself or commissioned assessors, often with OEM-specific extensions to the question catalog. The result of an OEM assessment is OEM-specific and only binding with respect to that OEM. - Does Automotive SPICE also apply to hardware development? - The standard PRM primarily covers software and systems engineering. There are no equivalent processes for hardware development in the generic Automotive SPICE PRM. OEMs wishing to assess hardware development processes use their own extensions or refer to ISO 26262 Part 5 for safety-critical hardware development. - How does Automotive SPICE relate to IATF 16949? - IATF 16949 is a quality management system standard covering the entire company (based on ISO 9001). Automotive SPICE focuses on software and systems development processes. Both are complementary and expected by OEMs in parallel: IATF 16949 for the company's QMS, Automotive SPICE for the maturity of development processes in software-relevant projects. ### The Complete Guide to 5S Audits in Manufacturing URL (DE): https://www.mobile2b.com/audits-inspections/5s-audit URL (EN): https://www.mobile2b.com/en/audits-inspections/5s-audit Summary: How to build 5S audits with clear scoring criteria, conduct them methodically, and anchor them as a lasting foundation for lean manufacturing. **What is a 5S Audit?** A 5S audit is a structured workplace inspection based on five lean principles: Seiri (Sort), Seiton (Set in order), Seiso (Shine), Seiketsu (Standardize), and Shitsuke (Sustain). Originally developed in Japanese manufacturing - shaped fundamentally by the Toyota Production System - 5S is today the most widely used workplace organization method in the world. The audit evaluates systematically whether the five principles are actually being practiced - not just whether they were introduced. For each of the five dimensions, criteria are defined and scored on a scale, typically 0-4 points per criterion. A meaningful 5S score is derived from the sum of all ratings relative to the maximum achievable score. Below 60% is considered unacceptable; 60-80% is a development phase; above 80% is considered sustainably established. 5S is not a clean-up program: The most common mistake: 5S is understood as a one-time cleaning action. In reality, 5S is a management system. The fifth S - Shitsuke (Sustain) - is the hardest and most critical: it ensures that the first four S are maintained permanently. Without regular audits with measurable criteria, every 5S initiative degrades within weeks. **Why 5S audits deliver measurable results** 5S is the foundation of every lean initiative. Without a stable 5S base, kaizen, TPM, and other improvement systems fail because the prerequisites are missing. - Waste becomes visible - Excess inventory, unnecessary movement, and hidden defect sources are uncovered through systematic assessment. What gets measured can be improved. - Accident risks demonstrably decrease - Clean, clearly structured workplaces reduce slip and trip hazards. OSHA data shows: good housekeeping standards reduce accident rates by 20-30%. - Quality problems occur less frequently - Disorder and missing standards at the workplace are direct causes of mix-ups, missing parts, and production defects. 5S eliminates these root causes. - Setup and search times are eliminated - When every tool has its defined place and is visually marked, search time disappears entirely. Studies show: without 5S, employees spend up to 30% of their working time searching. - Deviations are detected immediately - Visual management - floor markings, shadow boards, andon boards - allows anyone to see in seconds whether an area meets the standard. No expert knowledge required. - Lean projects succeed more reliably - 5S creates the stable foundation for kaizen, TPM, SMED, and other lean methods. Companies with an established 5S system achieve significantly higher success rates in improvement initiatives. **The 5S methodology in detail** Sort (Seiri) means removing everything from the workplace that is not needed for current work. Red-tagging is the classic tool: items that are uncertain are labeled and stored temporarily. After a defined period, unneeded items are removed permanently. Set in Order (Seiton) means defining a fixed place for every needed item and making it visually identifiable. The principle: the most frequently used items are closest and most accessible. Shine (Seiso) means systematically cleaning the workplace and using cleaning as an inspection: during cleaning, operators discover leaks, wear, and damage that would otherwise remain hidden. Standardize (Seiketsu) means documenting the results of the first three S - through photos, checklists, and workplace standards - so the desired state is reproducible and measurable. Sustain (Shitsuke) is the hardest S: it means making the first four S a habit through regular audits, visible scoring, and management attention. Shitsuke is the reason 5S needs an audit system. Without regular checking and feedback, the standard degrades. The audit is not a control instrument - it is the engine of sustainability. **Implementing a 5S audit system** From selecting the first pilot area to a company-wide 5S program - this structured approach works for production, warehouses, and offices. - Define scoring criteria for all five S - Develop observable, measurable criteria for each of the five S. Avoid vague formulations like 'workplace is clean' - instead: 'all work surfaces are free of parts not belonging to the current job'. A 5-point scale (0-4) per criterion is standard. Define visual anchor descriptions for each score level. - Select pilot area and conduct initial audit - Start with one area where the team is motivated. The initial audit establishes the baseline - typically a sobering result. That is the point: visible improvement from the baseline is the most powerful motivator for the next areas. - Develop improvement actions and assign owners - Every deviation from the audit generates a specific action: what, who, by when. Actions are not improvement projects - they should be completable within days. Quick wins in the first weeks after the audit are critical for acceptance. - Define audit frequency and responsibility - In the introduction phase: weekly self-audits by team leaders, monthly area audits by the lean coordinator. With an established 5S system: monthly area audits are sufficient. Management audits quarterly in any case. The frequency sends a signal: how often 5S is audited is how seriously it is taken. - Make 5S scores visible in the area - Display the 5S score trend visibly in the area - on the information board, or digitally on a screen. Social pressure works: teams that can see their score compared to other areas develop their own motivation for improvement. - Calibrate auditors and roll out to other areas - Every six months: calibration round with multiple auditors evaluating the same area independently. Compare results - differences reveal interpretation gaps in the criteria. After calibration, roll out systematically to the next areas. **Typical 5S problems - and the right countermeasures** Most 5S initiatives fail not because of the method, but because of implementation. These patterns are predictable and solvable. - 5S reverts to the old state after a few weeks - Without regular audits with measurable criteria, relapse is inevitable. Solution: weekly self-audits by team leaders as a fixed part of the shift handover. Display the 5S score visibly in the area - social pressure works. - Scores vary widely between different auditors - Missing calibration leads to comparability problems and demotivation. Solution: visually illustrated scoring anchors for each point value - a photo shows concretely what a '2' versus a '4' looks like. Calibration rounds every six months. - Employees see 5S as surveillance and resist - 5S is imposed from above, not developed together. Solution: involve employees in defining the standards. Those who defined what their workplace should look like defend that standard. Make quick wins visible - concretely measure search time reductions. - Good 5S scores but no improvement in KPIs - The audit measures compliance, not effectiveness. Solution: correlate 5S scores with operational KPIs - search times, setup times, accident rate. If the connection is not visible, either the audit methodology or the implementation of standards is off. **5S audits digital with Mobile2b** Paper-based 5S checklists are isolated solutions - results disappear in folders, trends stay invisible, actions are not followed up. Mobile2b closes these gaps. - Configurable scoring sheets - Define your 5S criteria and scoring scales exactly to your standard. Different checklists for different areas - production, warehouse, office. Changes available on all devices immediately. - Photo documentation on the spot - Document deviations with photos - directly in the audit on a smartphone or tablet. Photos are automatically assigned to the audit entry and archived immutably. No re-typing afterward. - Automatic action tracking - Every deviation automatically generates an action with owner and due date. Open actions are escalated automatically. Status visible on the dashboard at any time. - Trend dashboards and benchmarking - Compare 5S scores over time and across areas. Which area is improving? Where are there setbacks? Which of the five S are systematically weak? This transparency is not achievable with paper. **Frequently asked questions about 5S audits** - How often should 5S audits be conducted? - The frequency depends on maturity level. In the introduction phase: weekly self-audits by team leaders, monthly area audits by the lean coordinator. With an established 5S system, monthly area audits are sufficient. Management audits quarterly in any case. Too infrequent audits send the signal that 5S is not a priority. - Which scoring scale is recommended for 5S audits? - A 5-point scale (0-4) per criterion is the most widely used and proven approach. More important than the scale itself are the scoring anchors: for each point value, what it means must be clearly defined - ideally with photo examples. Without anchors, scores vary greatly between auditors. - What is 6S and how does it differ from 5S? - 6S extends the classic 5S methodology by adding Safety as a sixth pillar. While 5S covers Sort, Set in Order, Shine, Standardize, and Sustain, 6S explicitly integrates workplace safety into the audit framework as a standalone dimension. Organizations in industries with high safety requirements - chemical, pharmaceutical, food processing, heavy manufacturing - often prefer 6S because it ensures safety is assessed with dedicated criteria rather than being embedded implicitly in Seiso and Seiketsu. The audit approach itself remains the same: structured scoring with defined criteria, regular cadence, and action tracking. The difference is one additional assessment dimension covering hazard identification, PPE compliance, emergency equipment accessibility, and ergonomic conditions. If your organization already runs 5S audits, extending to 6S means adding safety-specific criteria to your existing checklist - no separate system required. - How do I avoid 5S becoming a pure compliance exercise? - The most common mistake: audits are announced, areas get cleaned up, and everything reverts after the audit. Countermeasures: conduct audits without advance notice. Place the focus on self-audits - teams measure themselves. Weight improvements more than absolute scores. And: link audit results to operational KPIs, not just a score. - How long does it take to implement a 5S audit system? - A pilot area can be set up in 4-6 weeks: 2 weeks for criteria development and training, then audits begin. A full rollout across multiple production areas typically takes 3-6 months. What matters is not speed but the quality of scoring criteria and consistency of execution. - Can 5S be applied in offices and service environments? - Yes. The principles are fully transferable: Sort (eliminate unnecessary files and clutter), Set in Order (defined storage locations for documents and materials), Shine (keep the workspace clean), Standardize (document digital and physical standards), Sustain (regular self-audits). Office 5S has specific adaptations but the same logic and the same need for regular auditing. ### TPM Audit Guide for Maintenance & OEE URL (DE): https://www.mobile2b.com/audits-inspections/total-productive-maintenance URL (EN): https://www.mobile2b.com/en/audits-inspections/total-productive-maintenance Summary: Assess the eight pillars of Total Productive Maintenance, increase OEE, and permanently reduce unplanned downtime with systematic TPM audits. **What is Total Productive Maintenance - and why is auditing critical?** Total Productive Maintenance (TPM) is a comprehensive maintenance concept developed from the foundations of the Toyota Production System and formalized by the Japan Institute of Plant Maintenance (JIPM). The goal: zero unplanned breakdowns, zero quality defects from equipment failure, zero accidents from equipment malfunction. TPM distributes responsibility for equipment condition and maintenance to all employees - machine operators take on basic care and early detection, while maintenance technicians focus on preventive and predictive activities. The TPM audit is the instrument that ensures this responsibility is actually exercised. It systematically evaluates all eight TPM pillars - from autonomous maintenance to the health and environment pillar - and delivers a quantifiable statement about the TPM maturity level of a machine, an area, or an entire plant. Without regular auditing, TPM remains a statement of intent. OEE: the key metric of TPM: Overall Equipment Effectiveness (OEE) is TPM's central measurement concept. OEE = Availability x Performance x Quality Rate. An OEE of 85% is considered world-class in discrete manufacturing. Each of the three components addresses specific loss sources: Availability covers unplanned breakdowns and changeover losses; Performance covers cycle time losses and minor stoppages; Quality Rate covers scrap and rework. TPM audits evaluate how consistently the eight pillars address these loss sources. **What consistent TPM measurably achieves** TPM companies that systematically audit and improve all eight pillars achieve results that are not attainable with reactive maintenance. - OEE increase of 15-25 percentage points - JIPM data from TPM-certified plants shows: the transition from reactive to preventive and autonomous maintenance typically increases OEE by 15-25 percentage points within 2-3 years - equivalent to a capacity increase without new investment. - Unplanned downtime reduced by 50-80% - Autonomous Maintenance (AM) and Planned Maintenance (PM) identify wear and defects before they lead to breakdowns. Early detection routines - daily operator inspections - drastically reduce emergency repairs. - Maintenance costs decrease despite higher prevention rate - Planned maintenance is 3-5x cheaper than reactive repair. Investment in training, inspection, and preventive replacement pays off through lower downtime costs and reduced spare parts consumption. - Quality rate rises through more stable processes - Equipment in a controlled condition produces reproducibly. Variations in equipment state - vibrations, temperatures, pressures outside tolerance - are direct causes of quality deviations. TPM eliminates these variation sources. - Operator knowledge and engagement increase - When machine operators are responsible for the basic care of their equipment, they develop deep process understanding. Anomalies are detected earlier, operating errors decrease, and identification with the workplace grows. - JIPM certification as a measurable goal - The Japan Institute of Plant Maintenance awards TPM prizes at four levels: Excellence Award Category 1, 2, Advanced Special Award, and World Class Award. The path to certification structures TPM implementation over several years and makes progress visible. **The eight TPM pillars - what each means and how it is audited** Pillar 1: Autonomous Maintenance (Jishu Hozen) - machine operators carry out cleaning, inspection, lubrication, and simple adjustments themselves. The audit evaluates: are there standardized inspection routines? Are operators qualified? Are CIL standards (Cleaning, Inspection, Lubrication) followed and regularly reviewed? Pillar 2: Planned Maintenance - maintenance technicians carry out time-based or condition-based maintenance per plan. Audit criteria: completeness of the maintenance plan, plan fulfillment rate, Mean Time To Repair (MTTR), Mean Time Between Failures (MTBF). Pillar 3: Focused Improvement (Kobetsu Kaizen) - loss sources are systematically eliminated using methods such as Why-Why analysis, P-M analysis, and kaizen workshops. The audit checks: are there active improvement projects? Are losses systematically captured and prioritized? Pillar 4: Training and Education - assessment of the skills matrix for operators and maintenance technicians. Are all necessary skills present? Are there structured development plans? Pillar 5: Early Equipment Management - new equipment is designed and introduced to be maintenance-friendly from the start. Audit: are maintenance technicians and operators involved early in procurement projects? Is there a structured launch process? Pillar 6: Quality Maintenance - the relationship between equipment condition and product quality is systematically analyzed and safeguarded. Pillar 7: TPM in Administration and Office - lean principles for indirect areas: identify and eliminate losses in administrative processes. Pillar 8: Health, Safety, and Environment - integration of occupational safety and environmental protection into all TPM activities. The overall maturity level of a TPM system is the weighted average of all eight pillars. JIPM Excellence plants typically score above 80% in every pillar. **Building a TPM audit system: the structured path** TPM audits are complex because they evaluate eight pillars each with their own criteria. The key is a step-by-step build, starting with the pillars that have the greatest OEE leverage. - Measure baseline: OEE measurement - Before any TPM program begins, take an honest inventory. Measure OEE for all key equipment over at least four weeks. Break OEE into its three components and identify which loss types dominate. This baseline is your starting point and your most important argument to management. - Select a pilot machine and pilot team - Start with a bottleneck machine whose operators and maintenance technicians are motivated. The pilot machine becomes the showcase project. All other areas should see what TPM concretely means - not in presentations, but on a running machine. - Develop audit criteria for all eight pillars - For each pillar, define 5-10 observable criteria scored on a 0-4 scale. Recommendation: start with pillars 1 (Autonomous Maintenance) and 2 (Planned Maintenance) - these have the most direct OEE impact and are easiest to measure. - Develop and train CIL standards - Cleaning, Inspection, Lubrication - for each machine, standardized routines are developed: what is cleaned, inspected, lubricated, with what, how often, in what sequence. These standards are the foundation for the autonomous maintenance audit and must be co-developed with operators. - Systematize loss recording - TPM audits require a data foundation. Implement structured failure recording by loss type (OEE loss tree): planned stoppages, unplanned breakdowns, changeovers, startup losses, cycle time losses, minor stoppages, scrap, rework. Without this data, Focused Improvement (Pillar 3) is blind. - Define audit rhythm and escalation - Autonomous maintenance audit: monthly, jointly by team leader and maintenance technician. Full TPM audit: quarterly by the lean/TPM coordinator. Management review: semi-annually with KPI trends and resource decisions. Critical deviations in the audit trigger immediate actions - not in the next quarter. **Why TPM implementations fail - and how to do it better** TPM is known to be difficult to implement. The causes are predictable. With the right approach, they are avoidable. - TPM stays a maintenance topic - operators don't feel responsible - Autonomous Maintenance is the culturally hardest pillar. Operators say: 'Repairs are not my job.' Solution: start with the simplest step - cleaning. Operators who clean their machine daily automatically discover anomalies. Only when this step is running should CIL standards be expanded step by step. Never skip Pillar 1. - OEE is measured but not improved - OEE dashboards without a Focused Improvement process are useless. The metric alone changes nothing. Solution: a structured loss analysis process - which three loss sources dominate? For each, a kaizen team is formed. Results are reported at the next OEE meeting. The loop must be closed. - Planned maintenance is deferred under production pressure - If planned maintenance windows are regularly cancelled for orders, that is a leadership problem, not a maintenance problem. Solution: integrate maintenance windows into the production plan with the same status as customer deadlines. Make the OEE impact of deferred maintenance transparent to management. - TPM audit becomes a bureaucratic compliance exercise - Too many criteria, too long audit sessions, no tangible consequences from results. Solution: focus the audit on the pillars with the greatest OEE leverage. Maximum 60 minutes per machine. Every deviation generates an action - this signals that audit results are taken seriously. **Conducting TPM audits digitally with Mobile2b** Coordinating TPM audits across eight pillars on paper is not operationally manageable. Mobile2b brings structure, transparency, and traceability to complex TPM programs. - Structured audit sheets for all eight pillars - Configure audit checklists for each TPM pillar with your own criteria weighting. Different checklists for different equipment types. Scores automatically feed into an overall maturity score. - Link OEE losses directly to actions - Deviations in the audit - missing CIL standards, open failure causes, maintenance not completed - automatically generate actions with owner and due date. No audit result gets lost. - Maturity tracking over time and across areas - Track TPM maturity per pillar, per machine, and per plant over time. Which pillars are systematically weak? Where are there setbacks? This transparency makes the path to JIPM certification plannable. - Mobile execution in production - Conduct audits directly at the machine on a tablet - no laptop, no paper, even offline in areas without Wi-Fi. Integrate photos of anomalies directly into the audit. Sync automatically on next network contact. **Frequently asked questions about TPM audits** - What is the difference between TPM and traditional preventive maintenance? - Traditional preventive maintenance is a function of the maintenance department. TPM distributes responsibility: operators take on basic care and early detection (autonomous maintenance), while maintenance technicians focus on more complex preventive and predictive tasks. TPM also encompasses loss reduction through kaizen, early equipment management, quality assurance through equipment stability, and safety - dimensions that traditional PM does not address. - How is OEE calculated correctly, and what is a good value? - OEE = Availability x Performance x Quality Rate. Availability = (Planned Production Time - Downtime) / Planned Production Time. Performance = (Actual Output x Ideal Cycle Time) / Operating Time. Quality Rate = Good Parts / Total Parts. An OEE of 85% is considered world-class for discrete manufacturing. Most plants start below 60%. More important than the absolute value is consistent measurement and the improvement trend. - Which TPM pillar should be introduced first? - Pillar 1 (Autonomous Maintenance) and Pillar 3 (Focused Improvement) are the usual starting point. AM creates the foundation - operators know their equipment and detect deviations early. Focused Improvement ensures the biggest loss sources are systematically addressed. Pillar 2 (Planned Maintenance) is built in parallel or shortly after. The other pillars follow step by step over 2-3 years. - How long does it take to implement a full TPM system? - JIPM recommends a three-year plan for the Excellence Award. Year 1: build awareness, pilot machine, introduce Pillars 1-3. Year 2: roll out to all machines, activate all eight pillars, measurably improve OEE. Year 3: stabilize, cultural anchoring, preparation for certification. Plants that move faster risk superficial implementation and relapse. - Can TPM work in small and medium-sized companies? - Yes, with adaptations. SMEs cannot introduce all eight pillars simultaneously with equal depth. Recommendation: start with Autonomous Maintenance and OEE measurement - these have the most direct ROI. Focused Improvement in a simplified form (monthly loss analysis session) as the third step. The remaining pillars as capacity allows. The core principle - operators care for their machines, losses are systematically reduced - applies regardless of company size. - How does TPM relate to predictive maintenance and Industry 4.0? - Predictive maintenance (PdM) and condition monitoring are enablers for TPM Pillar 2 (Planned Maintenance). Sensor data on vibrations, temperatures, and power consumption enables condition-based rather than time-based maintenance and further increases MTBF. But: predictive maintenance only works on a stable TPM foundation. Organizations that analyze sensor data but have no CIL standards and no structured loss recording are investing in the wrong problem. ### Safety Behaviour Index (SBI) Guide URL (DE): https://www.mobile2b.com/audits-inspections/safety-behaviour-index URL (EN): https://www.mobile2b.com/en/audits-inspections/safety-behaviour-index Summary: How to shift from reactive accident metrics to leading indicators using behavior-based safety observation (BBS) and build a measurable safety culture. **What is the Safety Behaviour Index?** The Safety Behaviour Index (SBI) is a quantitative metric describing the proportion of safe behaviors among all observed behaviors within a defined time period. SBI = (Number of safe observations / Total number of observations) x 100. An SBI of 85% means: in 85 of 100 observation moments, the defined safe behavior was exhibited. The SBI is the central output metric of Behavior-Based Safety (BBS) - the evidence-based approach to safety culture development. The theoretical foundation is Heinrich's Pyramid (also: Heinrich's Triangle): the ratio of 1 serious accident to 29 minor injuries to 300 near-misses to several thousand unsafe acts and conditions. Organizations that only measure serious accidents and near-misses see only the tip of the iceberg - and inevitably react reactively. BBS and SBI work at the base: the frequency of unsafe behaviors is directly measured and systematically reduced before accidents can occur. Leading indicators instead of lagging indicators: Lost Time Injury Frequency Rate (LTIFR), severity, and TRIR (Total Recordable Incident Rate) are lagging indicators - they measure events that have already happened. The SBI is a leading indicator: it measures preconditions for accidents before accidents occur. Organizations with well-developed leading indicator systems (SBI, near-miss rate, safety observation rate) can detect accident trends 3-6 months in advance. **Why SBI and behavior-based safety work** Behavior-based safety is not an approach that looks to blame employees. It is a data-driven system that makes safety behavior visible, measurable, and specifically improvable. - Accidents are predicted, not just counted - A declining SBI correlates with increasing accident probability. Organizations with an established BBS system can detect rising accident risk 4-8 weeks in advance and intervene before harm occurs. - Safety culture becomes tangible and measurable - Safety culture is often a soft concept without measurement. The SBI gives it a number. Improvements in safety culture become visible before they show up in lower accident rates - which is critical for sustaining motivation. - Leaders become actively involved - Safety walk programs and observation rounds by managers are an integral part of a BBS system. When plant managers and department heads regularly observe and give feedback, it changes the perceived priority of safety throughout the facility. - Positive reinforcement replaces pure sanctions - BBS is based on behavioral psychology: safe behavior is reinforced immediately, positively, and personally - not only when something goes wrong. This approach has demonstrably stronger and more lasting impact than exclusively sanctioning unsafe behavior. - System causes are separated from behavioral factors - Structured observation protocols distinguish: is unsafe behavior due to missing knowledge, missing equipment, time pressure, or a conscious decision? This distinction is critical for the right intervention. - Regulatory requirements are exceeded - ISO 45001:2018 explicitly requires proactive risk assessment and safety culture development. An SBI program delivers the evidence for these requirements and positions the company as a safety leader to customers and authorities. **BBS methodology and observation protocol** The core of BBS is the structured safety observation. An observer - a manager, team leader, or trained colleague - watches a specific work situation for a defined period and records whether predefined safe or unsafe behaviors are present. The observation protocol lists a Critical Behaviour Inventory (CBI): 10-20 specific, observable behaviors that have been identified from accident analyses and risk assessments as having the greatest risk contribution. After the observation, the observer gives immediate feedback: positive reinforcement for safe behaviors, constructive feedback for unsafe ones. The feedback conversation is the most important element of BBS - it is not a disciplinary measure but a coaching conversation. Data from all observations are aggregated into the SBI per area and over time. Monthly data reviews identify which behaviors are systematically unsafe, which system factors are behind them, and what targeted interventions are needed. **Building an SBI program step by step** A successful BBS program requires more than observation cards and a formula. These steps ensure sustainable implementation. - Conduct accident analysis and develop the Critical Behaviour Inventory - Analyze all accidents and near-misses of the last 3-5 years for behavioral causes. Which unsafe behaviors appeared most frequently? These become the core of the Critical Behaviour Inventory. The CBI must be validated by production managers and safety representatives - they know the actual risks. - Define observation protocol and train observers - The observation protocol defines: which behaviors are observed, how long an observation lasts (typically 10-15 minutes), how results are recorded, and how the feedback conversation is conducted. Train all observers thoroughly - the feedback conversation is the hardest element and requires practice. - Involve managers as observers - Management participation is not an optional feature - it is a core prerequisite. Safety walks by plant managers and department heads must be measurable and required as a KPI. If the management observation rate is visible in the management dashboard, behavior changes. - Define target SBI and observation frequency - Minimum 30 observations per calculation period (week or month) per area for a statistically valid SBI. Define a target SBI per area based on the current baseline. Improvement of 5-10 percentage points within 12 months is realistic for a well-implemented BBS program. - Establish monthly data review - Monthly data reviews with a concrete question: which three unsafe behaviors were observed most frequently? For each, a root cause analysis is conducted and an action defined. Without this step, the program is data collection without purpose. - Make SBI visible and communicate progress - Display SBI trends visibly in the area - on the safety board or digitally. Communicate improvements. Recognize areas with consistent improvement. The program must be experienced as a shared achievement, not as a control instrument. **Typical mistakes in SBI programs - and how to avoid them** Behavior-based safety is often introduced incorrectly - resulting in it being perceived as a control and blame instrument. These mistakes are known and avoidable. - Employees feel observed and only behave safely during observations - Observations without announcement, but with immediate positive feedback. More importantly: observers are colleagues and managers, not primarily EHS officers. When the program is communicated as a shared initiative rather than a control instrument, resistance decreases. Anonymous feedback on system factors builds trust. - SBI rises but accident rate stagnates or even increases - The observation protocol is not measuring the behaviors that are actually accident-relevant. Solution: review the Critical Behaviour Inventory. Are the observed behaviors really those with the greatest risk contribution? Compare accident analyses and near-miss reports with the behavior catalog. - Managers don't observe - the program stays an EHS task - Management participation is a core prerequisite, not optional. Safety walks by plant and department managers must be measured and required as a KPI, not just requested as an appeal. When observation rate by managers is visible in the management dashboard, behavior changes. - The program generates data but no improvements - Data is not being translated into actions. Solution: monthly data reviews with the concrete question: which three unsafe behaviors were observed most frequently? For each, a root cause analysis is conducted and an action defined. Without this step, the program is data collection without purpose. **SBI programs digital with Mobile2b** Paper-based safety observation cards pile up in folders, trends stay invisible, and management participation is not measurable. Mobile2b digitizes the entire BBS cycle. - Digital safety observation cards - Configurable observation forms for all areas and behavior categories. Conducted on a smartphone in under 10 minutes. Safe and unsafe observations are recorded separately, SBI calculated automatically. - SBI dashboard and trend analysis - SBI per area, per behavior category, and over time. Which behaviors are systematically unsafe? In which areas is the trend deteriorating? This analysis identifies the right intervention points. - Management KPI: observation rate - Who has conducted how many observations? Observation rate by managers as a measurable KPI - visible in the management dashboard. This makes management participation in safety accountable and transparent. - Convert system factors directly into actions - Identified system causes of unsafe behaviors - missing PPE, structural hazards, training needs - are created as actions directly from the observation record, with owner and due date. Complete traceability. **Frequently asked questions about SBI programs** - What is the difference between SBI and traditional safety metrics like LTIFR? - LTIFR (Lost Time Injury Frequency Rate) and similar metrics are lagging indicators - they count events after the accident. The SBI is a leading indicator: it measures behaviors that can lead to accidents before accidents happen. A company can have a low LTIFR and simultaneously a low SBI - meaning there hasn't been a serious accident yet, but safety behavior is deteriorating. The SBI warns earlier. - How many observations are needed for a statistically valid SBI? - Rule of thumb: at least 30 observations per calculation period (week or month) per area. Below 30 observations, random variation is too high for meaningful trend analysis. For areas with few employees, monthly aggregation may be necessary. - Does BBS blame employees for accidents? - No - when implemented correctly. BBS identifies unsafe behaviors, but its purpose is to understand the system conditions that make unsafe behavior more likely: time pressure, missing equipment, insufficient training, unclear instructions. The BBS feedback conversation is not disciplinary - it is a conversation about how to make safe behavior easier. Organizations that use BBS as a blame tool destroy the program's effectiveness. - What is the right size for the Critical Behaviour Inventory? - 10-20 behaviors is the proven range. Too few behaviors do not cover the relevant risks. Too many make observations cumbersome and reduce data quality. The CBI should be reviewed annually and updated based on new accident data and changed work conditions. - How long does it take to see results from a BBS program? - A measurable SBI improvement is achievable within 3-6 months with consistent implementation. A statistically significant reduction in accident rates is typically visible after 12-24 months. The leading advantage of the SBI is that it shows improvement before the accident rate falls - which is critical for motivation and management support. - Is BBS suitable for small companies? - Yes. BBS scales down well. For small companies: simplified observation cards with 5-10 behaviors, bi-weekly instead of weekly observations, the owner or plant manager as the primary observer. The core principle - systematically reinforcing safe behavior and identifying system causes of unsafe behavior - works regardless of company size. ### Six Sigma Management URL (DE): https://www.mobile2b.com/audits-inspections/six-sigma URL (EN): https://www.mobile2b.com/en/audits-inspections/six-sigma Summary: Track DMAIC projects, manage belt certifications, and measure process improvement across your organization. **What is Six Sigma?** Six Sigma is a data-driven methodology for eliminating defects and reducing process variation. Developed at Motorola in the 1980s and popularized by General Electric, Six Sigma aims for processes that produce fewer than 3.4 defects per million opportunities - a 6-sigma level of quality. The methodology relies on statistical analysis, structured project execution, and a belt-based certification system to drive measurable improvement. Six Sigma organizes practitioners into belt levels: Yellow Belts understand the basics and participate in projects, Green Belts lead smaller projects part-time, Black Belts lead complex projects full-time, and Master Black Belts mentor others and shape the program strategy. The primary project framework is DMAIC - Define, Measure, Analyze, Improve, Control - which provides a repeatable structure for solving problems with data. Six Sigma is deeply connected to quality management systems like ISO 9001 and IATF 16949, where its statistical rigor strengthens process capability and audit readiness. Six Sigma is not just statistics: The most common misconception: Six Sigma is a statistical toolkit only relevant to engineers. In practice, Six Sigma is a management system. The belt structure creates accountability, DMAIC provides project discipline, and tollgate reviews ensure that decisions are based on data, not opinions. Organizations that treat Six Sigma as a statistics course miss the point - the method works because it connects improvement projects to business outcomes through structured governance. **Why Six Sigma delivers measurable business results** Six Sigma connects improvement projects directly to financial and operational outcomes. Every project has a defined goal, a measurable metric, and a verified result. - Belt certifications tracked centrally - Know exactly who holds which belt, when certifications expire, and who is ready for the next level. No more spreadsheets and expired certificates going unnoticed. - DMAIC projects linked to audit findings - When an audit uncovers a process gap, a Six Sigma project is the structured way to fix it. Linking DMAIC projects to audit nonconformances ensures that findings lead to verified corrections, not just action items. - Sigma levels measured across processes - Calculate DPMO and sigma levels for your key processes. Track whether improvement projects actually move the needle on defect rates - with numbers, not gut feeling. - Improvement ROI becomes visible - Every DMAIC project documents expected and actual savings. Aggregate across your project portfolio and you know exactly what your Six Sigma program delivers in hard currency. - Belt holders actively lead projects - A dashboard showing project assignments, status, and results per belt holder keeps the program active. No more certified Black Belts who never run a project after training. - Cross-functional project governance - Tollgate reviews at each DMAIC phase gate ensure projects stay on track. Champions, process owners, and belt holders collaborate in a single system instead of scattered presentations. **The DMAIC process in detail** Define sets the project scope: what is the problem, who is the customer, what metric must improve, and by how much? A good project charter prevents scope creep and ensures leadership buy-in before work begins. Measure establishes the baseline: how does the process perform today? This phase relies on data collection plans, measurement system analysis (MSA), and process capability studies. Statistical process control (SPC) charts are the primary tool here. Analyze identifies the root causes of variation and defects. This is where tools from our knowledge base come into play - the 5 Whys method drills down to root causes, and Ishikawa (fishbone) diagrams map out cause categories systematically. Improve develops and tests solutions. Design of experiments (DOE), pilot runs, and before/after comparisons validate that the proposed changes actually reduce defects. CAPA processes are the natural bridge here - corrective actions from Six Sigma projects feed directly into your CAPA system. Control locks in the gains: updated work instructions, control charts for ongoing monitoring, and response plans if the process drifts. Without a solid control phase, improvements erode within months. The control phase is also where Six Sigma connects to your quality management system - updated process documentation becomes the new auditable standard. **Setting up a Six Sigma program with Mobile2b** From belt certification tracking to DMAIC project management - a structured approach that scales from pilot to enterprise-wide deployment. - Register belt holders and certifications - Import or create profiles for all certified belt holders. Record belt level, certification date, certifying body, and expiration date. Set up automatic renewal reminders so certifications never lapse unnoticed. - Create a DMAIC project template - Define the standard tollgate criteria for each DMAIC phase. What must be delivered at Define? What data is required at Measure? Standardizing the template ensures consistency across all projects and makes tollgate reviews efficient. - Link projects to business priorities - Every Six Sigma project should trace back to a strategic goal, an audit finding, or a customer complaint. Configure categories and tags that make this traceability visible and reportable. - Run tollgate reviews digitally - At each phase gate, the project lead submits deliverables. Champions and process owners review and approve - or send back with specific feedback. All decisions are documented and timestamped. - Track results and calculate savings - Each project documents baseline metrics, target metrics, and actual results after implementation. Mobile2b aggregates savings across the portfolio so program ROI is always current. - Monitor the program with dashboards - Active projects by phase, belt utilization rates, average project duration, cumulative savings - a Six Sigma program needs visibility to stay alive. Dashboards make the program status accessible to leadership without manual reporting. **Common Six Sigma challenges - and how to solve them** Six Sigma programs fail not because of the methodology, but because of organizational issues. These patterns are predictable and preventable. - Belt certifications tracked in spreadsheets - Spreadsheets go stale. Certifications expire without anyone noticing, and there is no overview of available skills. Solution: a central certification register with automatic expiry alerts and a skills matrix that shows belt coverage by department. - DMAIC projects disconnected from daily operations - Projects run in parallel to the real work, findings never reach the shop floor. Solution: link Six Sigma projects to audit findings, CAPA records, and process documentation. When a project improves a process, the updated standard is immediately visible to operators. - No visibility into improvement ROI - Leadership cannot justify the program budget because savings are not tracked. Solution: require financial impact estimation at Define and verified results at Control. Aggregate at portfolio level and report quarterly. - Belt holders not actively leading projects - People get certified but never apply what they learned. Solution: set a minimum project requirement per belt level per year. Make project assignments and completion rates visible on the belt holder dashboard. **Six Sigma digital with Mobile2b** Paper-based project tracking and spreadsheet certification lists cannot sustain a Six Sigma program. Mobile2b gives your program the infrastructure it needs. - Belt certification dashboard - Central register of all belt holders with certification level, date, certifying body, and expiry. Automatic renewal reminders. Skills matrix view by department and location. - DMAIC project workflow - Guided project execution through all five DMAIC phases with tollgate checklists, deliverable tracking, and approval workflows. Each project linked to its charter, team, and business case. - Integration with audit findings - Connect Six Sigma projects to audit nonconformances, CAPA records, and customer complaints. When an audit finding triggers a DMAIC project, the traceability is automatic and auditable. - Improvement metrics and portfolio reporting - Track sigma levels, DPMO, project savings, and cycle times across your entire portfolio. Dashboard views for program managers and executive sponsors with drill-down to individual projects. **Frequently asked questions about Six Sigma** - What are the Six Sigma belt levels? - Six Sigma uses a martial arts-inspired belt system. Yellow Belts have foundational knowledge and support projects. Green Belts lead smaller improvement projects, typically part-time alongside their regular role. Black Belts lead complex, cross-functional projects full-time. Master Black Belts train and mentor other belts and shape the overall program strategy. Some organizations also use White Belts for basic awareness training. - How long are Six Sigma certifications valid? - It depends on the certifying body. ASQ certifications are valid for three years and require recertification through continued education or re-examination. IASSC certifications do not expire. Company-internal certifications often require a minimum number of completed projects per year to remain active. Best practice: track validity periods centrally and set up automatic reminders regardless of the certifying body. - What is the difference between Six Sigma and Lean Six Sigma? - Six Sigma focuses on reducing variation and defects using statistical tools. Lean focuses on eliminating waste and increasing flow. Lean Six Sigma combines both: Lean tools address speed and waste, Six Sigma tools address quality and variation. In practice, most modern programs use Lean Six Sigma because most processes suffer from both waste and variation. The DMAIC framework remains the same - Lean tools are simply added to the toolkit at each phase. - How does Six Sigma relate to ISO 9001 and IATF 16949? - Six Sigma is not a standard but a methodology. However, it supports many ISO 9001 and IATF 16949 requirements directly: process capability analysis (clause 8.5.6 in IATF), statistical tools (clause 9.1.3), continual improvement (clause 10.3), and root cause analysis (clause 10.2.1). Running Six Sigma projects creates evidence for audit compliance. Some automotive OEMs require suppliers to demonstrate Six Sigma capability explicitly. - What is the minimum data requirement for Six Sigma statistical analysis? - It depends on the tool. For basic process capability analysis (Cpk), you need at least 30 measurements from a stable process. For hypothesis testing, sample size calculations depend on the effect size you want to detect and the acceptable risk of error - typically 30 to 100 data points per group. For control charts, 25 subgroups of 3-5 measurements each is the standard starting point. The Measure phase of DMAIC includes a data collection plan that specifies exactly what is needed. - Can Six Sigma be applied outside manufacturing? - Yes. Six Sigma originated in manufacturing but the DMAIC framework applies wherever processes have measurable outputs and defects can be defined. Healthcare uses Six Sigma to reduce medication errors and patient wait times. Financial services use it to reduce transaction processing errors. IT uses it for incident reduction and service level improvement. The key requirement is that you can define what a defect is and measure its frequency. ### The Complete Guide to GMP Inspections URL (DE): https://www.mobile2b.com/audits-inspections/good-manufacturing-practice-gmp URL (EN): https://www.mobile2b.com/en/audits-inspections/good-manufacturing-practice-gmp Summary: EU GMP guidelines, EMA and FDA inspections, Annex 1, and common findings - from preparation to complete CAPA documentation. **What are GMP Inspections?** Good Manufacturing Practice (GMP) is the framework of mandatory quality standards for the manufacture of pharmaceuticals, medical devices, food, and cosmetics. GMP inspections are regulatory reviews by national and international oversight authorities - in the EU by the relevant state authorities on behalf of the EMA, in the US by the FDA - ensuring that manufacturers continuously comply with applicable requirements. An inspection is not an exception in production operations - it is the norm for every regulated manufacturer. In the EU, GMP requirements for human medicines are governed by the EU GMP Guide (EudraLex Volume 4), divided into Part I (finished products, Chapters 1-9), Part II (active substances per ICH Q7), and Annexes 1-20. In the US, Current Good Manufacturing Practice (cGMP) requirements apply under 21 CFR Parts 210/211 (pharmaceuticals), 820 (medical devices), and 110/117 (food). Both systems are largely harmonized through PIC/S (Pharmaceutical Inspection Co-operation Scheme), enabling mutual inspection recognition between member countries. Finding categories: Critical, Major, Other: Inspection authorities classify findings by severity: Critical - direct risk to patient safety or the product; manufacturing ban possible. Major - significant deviation with risk to product quality or safety; CAPA required within 30-90 days. Other (Minor) - deviation without immediate risk, but improvement needed. The ratio of Major to Other findings and the quality of the CAPA plan determine the overall inspection outcome. **Why consistent GMP compliance is more than a regulatory obligation** Inspection preparation as a reactive project costs many times more than a continuous compliance culture. And it fails more often. - Authorization and market access - Without a valid GMP manufacturing license, no pharmaceutical product may be placed on the market. An FDA Warning Letter or serious regulatory finding can shut down production and jeopardize existing marketing authorizations. - Product quality and patient safety - GMP is the operational framework ensuring that every batch of a product has identical quality. Cleanroom controls, process validations, and calibration intervals are the foundation for reproducible manufacturing - not optional add-ons. - Reduced recall risk - The most common causes of pharmaceutical recalls are contamination, labeling errors, and manufacturing deviations - all points that a functioning GMP system catches early. Every prevented recall saves on average millions of euros in direct costs and incalculable reputational damage. - CAPA effectiveness as a quality indicator - Inspectors evaluate not only findings but also the quality of the CAPA response: is the root cause analysis thorough? Are the actions effective and closed with an effectiveness check? A weak CAPA plan significantly worsens the rating even for inherently good processes. - Data integrity as a central inspection focus - Since the establishment of ALCOA+ principles (Attributable, Legible, Contemporaneous, Original, Accurate, plus Complete, Consistent, Enduring, Available), data integrity is a priority inspection focus worldwide. Incomplete or retroactively altered records lead directly to Critical findings. - Supply capability and supplier qualification - Pharmaceutical value chains are international. Own GMP compliance is a prerequisite for access to regulated markets. Additionally, supplier qualification obligations apply (Annex 15, ICH Q10): raw material and service suppliers must be systematically audited. **The regulatory framework: EU GMP, FDA 21 CFR, and PIC/S** The EU GMP Guide (EudraLex Volume 4) is the central reference document for manufacturers in the EU and all PIC/S member states. The nine chapters of Part I cover all aspects of finished pharmaceutical manufacturing. The annexes specify requirements for particular areas: Annex 1 (sterile manufacture, fundamentally revised 2022, in force since August 2023) is the most extensive annex with central importance for the Contamination Control Strategy (CCS). Annex 11 (computerized systems) governs all digital manufacturing systems and their validation. Annex 15 (qualification and validation) defines the validation framework including MACO calculations for cleaning validation. In the US, 21 CFR Part 211 sets the cGMP requirements for finished pharmaceuticals. The FDA inspection follows the Establishment Inspection Report (EIR) process: the inspector documents observations on FDA Form 483, the manufacturer responds in writing within 15 business days (for Warning Letters), and the FDA determines the outcome: No Action Indicated (NAI), Voluntary Action Indicated (VAI), or Official Action Indicated (OAI). A Warning Letter is publicly available on the FDA website and has immediate implications for business relationships, market position, and for publicly traded companies, stock price. **Preparing for an EMA or FDA inspection - step by step** Inspection preparation is not a sprint immediately before the inspection date. It is a continuous process anchored in daily manufacturing practice. - Self-inspection and gap analysis - At least annual self-inspections per the EU GMP Guide (Chapter 9 requires regular self-inspections). Scope: all GMP chapters and relevant annexes, prioritized on a risk basis. Result: prioritized deficiency list with CAPA and owners. Self-inspections are also a legal requirement in Germany (§ 64 AMG). - Review documentation system for ALCOA+ compliance - Check GMP documentation for ALCOA+ conformity: are all records filled out in a timely and original manner? Are there gaps in batch records, calibration protocols, or cleaning validations? Data integrity audits with targeted sampling of electronic and paper-based records are today mandatory, not optional. - Review CAPA system for effectiveness - Capture all open CAPAs from previous inspections and internal audits and check for completeness. Effectiveness checks for closed CAPAs must be documented. Inspectors specifically ask about the current status of actions from the previous inspection cycle - missing effectiveness evidence is a frequent Major finding. - Update personnel and training records - Update the training matrix for all GMP-relevant activities and close backlogs. Review qualification evidence for key positions: Qualified Person (QP), QC manager, production manager. SOPs revised in the last 12 months must have training evidence for all affected personnel. - Critical equipment and qualification status - Review qualification and calibration status of all critical equipment and measuring instruments. Maintain requalification deadlines. Document and keep current the validation status for cleaning procedures (cleaning validation per Annex 15 with MACO calculation based on PDE values) and computerized systems (CSV per Annex 11 / GAMP 5 categories). - Mock inspection and communication training - Conduct an internal mock inspection with experienced GMP experts or external consultants. Train employees for the inspection situation: how to behave when the inspector arrives, what statements can be made, who may make commitments. Calm, fact-based communication without speculation is critical. **Common GMP findings - and how to avoid them** The list of most frequent FDA and EMA findings has been stable for years. These are not exotic edge cases - they are systemic weaknesses that are manageable with the right approach. - Data integrity violations: retroactive changes and missing audit trails - Computerized systems must be validated per 21 CFR Part 11 (FDA) or Annex 11 (EU) and maintain complete electronic audit trails with timestamps and user identification. Paper-based records may only be corrected with a single strikethrough, date, and initials - no correction fluid, no overwriting. Anchor periodic data integrity audits with documented sampling methodology in the quality system. - Ineffective CAPA: treating symptoms rather than root causes - Root cause analysis is mandatory, not optional. Methods such as Ishikawa diagram, 5-Why, or FMEA must demonstrably have been applied - the method used must be named in the CAPA document and the result documented. A complete CAPA plan shows: immediate action (containment), identified root cause, systemic corrective action, preventive action, and an effectiveness check with measurable acceptance criteria. - Inadequate cleaning validation per current standards - Cleaning validation per Annex 15 requires scientifically justified acceptance limits based on PDE values (Permitted Daily Exposure) per the EMA HBEL guideline concept (2018). Visual inspection alone is not a sufficient validation method. Changes to products, processes, or equipment trigger revalidation obligations that must be anchored in the change control process. - Deficiencies in the supplier qualification program - Every supplier of critical raw materials and services must be qualified: audit program with risk-based frequency, technical qualification (questionnaires, certificates, sampling where needed), quality agreements per ICH Q10. Audit intervals must be maintained and all activities documented. Gaps in audits or expired quality agreements are frequent Major findings. **Managing GMP compliance digitally with Mobile2b** GMP documentation on paper or in Excel is a manageable risk - until the next inspection. Mobile2b creates a revision-safe, always inspection-ready quality infrastructure. - GMP inspection checklists per EU and FDA - Predefined checklists for all GMP chapters and relevant annexes (EU GMP Part I/II, FDA 21 CFR). Internal audits and self-inspections are conducted in a structured way, findings immediately captured and classified as Critical / Major / Minor. All findings are documented with timestamp and auditor. - CAPA management with effectiveness check - Every finding from internal audits or external inspections is created as a CAPA: root cause analysis, action definition, owner, due date, and effectiveness check with acceptance criteria. The complete CAPA status is always evaluable and ready for regulatory submission. - Revision-safe audit trail - All audit activities, findings, and actions are stored with timestamp, user, and complete change history. This corresponds to ALCOA+ requirements for electronic records and is fundamentally compliant with 21 CFR Part 11. The audit trail is exportable for inspectors at the click of a button. - Supplier audit program - Plan, conduct, and document supplier audits - including risk-based frequency control, evaluation matrix, findings, corrective actions, and quality agreement status. The complete supplier qualification program is always ready for regulatory inspections. **Frequently asked questions about GMP inspections** - What is the difference between routine, pre-approval, and for-cause inspections? - Routine inspections occur cyclically (in the EU typically every 2-3 years for pharmaceutical manufacturers) and check general GMP compliance. Pre-Approval Inspections (PAI) are conducted by the FDA before approval of a new product or new manufacturing site and focus on validation of the specific manufacturing process. For-cause inspections are triggered by recalls, serious quality problems, or information from other authorities - and are the most intensive inspection type with the highest escalation potential. - What happens after an FDA Warning Letter? - A Warning Letter is publicly available on the FDA website. The manufacturer must respond in writing within 15 business days with a complete CAPA plan. The FDA can impose Import Alerts until CAPA effectiveness is confirmed and block approval of new products from that facility. The average time to official resolution of a Warning Letter is 2-4 years. - What does the revised Annex 1 (2022/2023) mean in practice? - The new Annex 1 (in force since August 2023) is significantly more extensive than the previous version and more strongly oriented toward the Contamination Control Strategy (CCS) concept. Every sterile manufacturer must present a documented, risk-assessed CCS addressing all contamination risk sources: environment, personnel, equipment, and process. This requires a fundamental revision of existing risk assessments and validation documentation at most companies. - How do we prepare for an EMA GMP inspection? - EMA does not inspect itself. In the EU, the competent national authority runs the inspection, and EMA coordinates it for centrally authorized products. Preparation starts six to eight weeks before the date with four documents: a current Site Master File, the CAPA status of every finding from the last inspection, the self-inspection reports, and the list of open deviations and change controls. Then comes the staffing: a front room team that works with the inspectors, a back room team that retrieves requested documents within minutes, and one named subject matter expert per process area. Teams that start when the announcement arrives spend the preparation window searching for documents instead of closing real gaps. - What role does the Qualified Person play in inspections? - The Qualified Person (QP) per Articles 48-51 of Directive 2001/83/EC is personally responsible for releasing every batch of medicinal product. In inspections, the QP is central: inspectors check their formal qualification, their actual working practice, and whether they genuinely live the responsibility. A QP who formally releases batches without reviewing the documentation is a Critical finding with personal legal consequences. - How often must internal GMP audits be conducted? - EU GMP Chapter 9 requires regular self-inspections without specifying a minimum frequency. In practice, an annual program with risk-based prioritization of areas is the standard - critical areas are audited more frequently than non-critical support areas. Many companies supplement this with unannounced internal audits and continuous process monitoring. ### The Complete Guide to HACCP URL (DE): https://www.mobile2b.com/audits-inspections/haccp URL (EN): https://www.mobile2b.com/en/audits-inspections/haccp Summary: The 7 HACCP principles, critical control points, Codex Alimentarius, and practical implementation - for food safety managers in production. **What is HACCP?** HACCP (Hazard Analysis and Critical Control Points) is a preventive, science-based system for identifying, evaluating, and controlling food safety hazards. Developed in the 1960s jointly by NASA, the US Army, and the Pillsbury Company, HACCP is today internationally standardized through the Codex Alimentarius guidelines (CAC/RCP 1-1969, Rev. 2020) and legally required in the EU under Regulation (EC) No. 852/2004 for all food business operators with limited exceptions. HACCP is not a standard you certify against - it is a management system concept that serves as the foundation for food safety standards such as ISO 22000:2018 and FSSC 22000. ISO 22000 integrates HACCP into a broader food safety management system framework and harmonizes it with the High Level Structure of other ISO standards. The HACCP plan is the core document of the system - it must be based on a thorough, documented hazard analysis and kept continuously current. Prerequisite Programs (PRPs) as an indispensable foundation: HACCP only works on a stable foundation of basic hygiene programs (Prerequisite Programs, PRPs). These include: cleaning and disinfection, pest control, personnel training and hygiene, traceability, supplier control, maintenance and calibration, allergen management, and recall procedures. PRPs prevent most hazards before the HACCP plan. Organizations that neglect PRPs and try to control everything through CCPs create an unmanageable system with too many critical control points. **Why a robust HACCP system is indispensable** HACCP is a legal requirement - but companies that treat it as a strategic quality instrument achieve far more than compliance. - Legal compliance and production authorization - Without a documented HACCP system, a food manufacturer in the EU may not produce. Authorities check HACCP documentation in every food inspection. Missing or incomplete HACCP plans lead to fines, plant closures, and forced recalls. - Preventive hazard control rather than reactive response - HACCP systematically identifies biological (Salmonella, Listeria monocytogenes, STEC), chemical (pesticides, allergens, cleaning agent residues), and physical hazards (glass, metal, bone) before production. Prevention is cheaper than recalls by a factor of 10-1000. - Targeted traceability in the event of an incident - A HACCP system with complete batch traceability enables targeted isolation of affected batches in a recall event rather than a full product withdrawal. CCP monitoring records are the foundation for drastically reducing the scope of a recall. - Access to retail and trade partners - Major retail chains require suppliers to hold certifications under IFS Food, BRCGS, or FSSC 22000 - all HACCP-based standards. Without a functioning HACCP system, access to these procurement channels is effectively blocked. - Liability reduction in the event of a claim - A documented, demonstrably practiced HACCP system is the most important evidence in product liability cases. The manufacturer must demonstrate the diligence of their manufacturing process. Incomplete HACCP documentation significantly increases liability risk in a crisis. - Efficiency through focus on what matters - HACCP forces prioritization: not every process step is a CCP. Concentrating resources on typically 2-6 CCPs per product is more efficient than undifferentiated quality control at every step. Everything else is covered through PRPs and operational PRPs (oPRPs). **The 7 HACCP principles in detail** Principle 1 - Hazard Analysis: systematically identify and evaluate all biological, chemical, and physical hazards at every process step. Evaluation criteria: likelihood of occurrence and severity of health impact. Result: list of significant hazards to be controlled in the HACCP plan. Principle 2 - CCP Identification: for each significant hazard, determine whether and at which process step it can be completely eliminated or reduced to an acceptable level. The decision tree approach per Codex Alimentarius is the standard tool. Principle 3 - Critical Limits: establish measurable, scientifically based limits for each CCP (e.g., core temperature 72 degrees C for 15 seconds during pasteurization, pH below 4.6 for acid preservation, water activity aw below 0.85). Limits must come from validated scientific sources or be validated independently. Principle 4 - Monitoring System: establish a continuous or sampling-based measurement system for each CCP that monitors compliance with critical limits in real time. Requirements: who measures? What? How? How often? With which calibrated instrument? Principle 5 - Corrective Actions: pre-defined responses to CCP deviations - immediate action (what happens to the affected product?) and corrective action (what is changed to prevent recurrence?). Principle 6 - Verification: regular checks that the HACCP system as a whole is working: internal audits, microbiological product and environmental controls, calibration checks, countersigning of monitoring records. Principle 7 - Documentation: all HACCP activities must be recorded: hazard analysis, HACCP plan, monitoring records, CCP deviations and corrective actions, verification activities, and training records. These records are mandatory evidence for authorities and certifiers. **Creating a HACCP plan - step by step** An effective HACCP plan is not created at a desk. It requires multidisciplinary expertise, deep production knowledge, and scientifically sound hazard assessment. - Assemble the HACCP team - The HACCP team must be multidisciplinary: food technology, microbiology or food chemistry, quality management, procurement (for raw material risks), and where needed, external expertise for specific hazards. The HACCP team leader must be demonstrably trained. A HACCP plan created by one person alone is rarely valid - assessors and inspectors recognize the missing multidisciplinarity. - Define product description and intended use - Create a complete product description: composition, pH, water activity (aw), preservation method, packaging format, storage temperature, and best-before date. Document the intended use and target group - especially critical for products for vulnerable groups (infants, elderly, immunocompromised), as this significantly affects the hazard assessment. - Create process flow diagram and verify on-site - Document every process step from raw material receipt to dispatch, including temperatures, times, environmental conditions, and contact materials. Critical: the flow diagram must be verified on-site in the production facility. Deviations between document and reality are immediately detected in audits and are a direct finding. - Conduct hazard analysis - For every process step and every raw material, identify all potential biological, chemical, and physical hazards and assess them by likelihood and severity. Hazards with a significant risk product are controlled in the HACCP plan. Sources for hazard identification: scientific literature, EU RASFF database, FDA Outbreak database, historical complaint data, and industry guidelines. - Determine CCPs, set critical limits, and define monitoring - Apply the Codex Alimentarius decision tree for each significant hazard. For identified CCPs: derive critical limits from scientific literature or own validation studies. For each CCP, fully define: critical limit, monitoring procedure, frequency, instrument, owner, corrective actions, and recording format. - Validation, implementation, and continuous verification - Before implementation: validate the HACCP plan (are the control measures scientifically appropriate to control the hazards?). After implementation: regular verification. The HACCP plan must be reviewed promptly - and updated if needed - when products change, processes change, new raw materials are introduced, or after deviation events. **Typical HACCP weaknesses - and how to fix them** Food inspections and certification audits regularly reveal the same systemic weaknesses. Most are not knowledge problems - they are implementation and documentation problems. - Too many CCPs make the system unmanageable - A common mistake: every risk-relevant step is classified as a CCP. The result is a system that cannot be managed in practice. CCPs are exclusively points where a significant hazard can be completely eliminated or reduced to an acceptable level, and where no later control is possible. All other critical steps are Operational Prerequisite Programs (oPRPs) per ISO 22000. - HACCP plan is not updated after product or process changes - A change management process for HACCP-relevant changes is mandatory: every change to formulation, raw materials, suppliers, equipment, or process parameters triggers a HACCP review. Anchor this process in the QMS and document the review obligation. HACCP plans that are not updated after demonstrable changes are a classic Major finding in IFS Food, BRCGS, and FSSC audits. - CCP monitoring records are incomplete or filled in retrospectively - CCP monitoring records must be ALCOA-compliant: timely (not at shift end or the next day), with an actual measured value (not just 'OK'), identification of the person measuring, and batch reference. Digital monitoring systems with mandatory timestamps and automatic deviation escalation reliably prevent the most frequent finding category in food inspections. - Corrective actions are not pre-defined and are improvised - Corrective actions must be in the HACCP plan before a CCP deviation occurs. For each CCP, it must be clearly defined: what happens to the product produced during the deviation? What happens to the process? Who decides? Only with pre-defined responses can production employees act correctly in the event of a deviation. **Implementing HACCP digitally with Mobile2b** Paper-based HACCP documentation is the most common criticism in food inspections. Mobile2b digitizes CCP monitoring, deviation management, and verification in an integrated system. - Real-time CCP monitoring - Digital monitoring forms for each CCP with required fields, critical limit validation, and automatic deviation escalation. Measured value outside the critical limit? Immediate notification to the responsible person, automatic product hold as the next step. No monitoring result is lost, no field left empty. - HACCP verification and internal audits - Structured verification checklists for all 7 HACCP principles and all PRPs. Internal HACCP audits are fully documented, findings directly linked to corrective actions. The complete verification history is exportable for authorities and certifiers at any time. - CCP deviation and CAPA management - Every CCP deviation is structured as an incident: affected batch, measured value, immediate action and product disposition, root cause analysis, corrective action with owner and due date. The complete deviation history shows trends and enables proactive system improvements. - Traceability and complete audit trail - All HACCP activities - monitoring, deviations, actions, verifications, training - are stored with batch reference, timestamp, and user. In a recall event, the affected batch can be isolated in minutes based on CCP records. **Frequently asked questions about HACCP** - What is the difference between a CCP and an oPRP? - A Critical Control Point (CCP) is a process step at which a control measure can and must be applied to prevent, eliminate, or reduce a significant food safety hazard to an acceptable level - and at which no later control is possible. An Operational Prerequisite Program (oPRP per ISO 22000) also controls food safety hazards, but with less stringent requirements: action limits rather than critical limits, corrections rather than immediate corrective actions, more flexible monitoring frequency. The distinction is methodologically critical - too many CCPs destabilize the system. - How often must a HACCP plan be reviewed? - The Codex Alimentarius requires a review upon significant changes: new raw materials or suppliers, formulation changes, process changes, new scientific knowledge on hazards, after food safety incidents. Additionally, a regular planned review (typically annual) is best practice and explicitly required by IFS Food, BRCGS, and FSSC 22000. The review must be documented - date, participants, outcome, and any updates. - Does HACCP apply to small food businesses the same as to large manufacturers? - In the EU, small businesses (especially primary production and direct sales) may apply simplified HACCP procedures where the nature and scale of operations justify it. Guidelines on good hygiene practice from national industry associations may be recognized as alternatives. However, in practice: as soon as a business supplies food retail or processors, a complete HACCP plan with documentation is effectively required. - How does HACCP relate to ISO 22000 and FSSC 22000? - HACCP is the core methodological concept (7 principles per Codex Alimentarius). ISO 22000:2018 integrates HACCP into a complete management system framework that is certifiable. FSSC 22000 builds on ISO 22000, adds sector-specific PRPs (e.g., ISO/TS 22002-1 for food manufacturing) and GFSI-recognized additional requirements. For retail and trade partners, FSSC 22000 or BRCGS is the preferred certification - HACCP alone typically does not suffice for a trade partner qualification. - What are the most important biological hazards HACCP must address? - Relevant biological hazards are product and process dependent. Most common: Salmonella spp. in poultry, eggs, nuts, and spices; Listeria monocytogenes in ready-to-eat products (RTE) with refrigeration as a CCP; Escherichia coli STEC in raw meat, raw milk, and unheated plant products; Bacillus cereus and Clostridium perfringens in cooked and reheated starchy products; Clostridium botulinum in anaerobic, low-salt products with pH above 4.6. Hazard identification must be based on current scientific and regulatory data (RASFF, EFSA, national food safety authorities). - How long must HACCP records be retained? - EU Regulation 852/2004 does not set a uniform minimum retention period. In practice: at least for the shelf life of the product plus a reasonable period, typically 2-5 years depending on product and national regulations. IFS Food 8 and BRCGS recommend risk-based determination of retention periods. For products with a long shelf life or for products targeting vulnerable groups, longer periods are appropriate. ### UVV Inspections: DGUV Compliance Guide URL (DE): https://www.mobile2b.com/audits-inspections/uvv-pruefung URL (EN): https://www.mobile2b.com/en/audits-inspections/uvv-pruefung Summary: DGUV regulations 3, 68, and 70, inspection intervals, qualified inspectors, and digital documentation for safety officers and fleet managers. **What are UVV Inspections?** UVV inspections (Unfallverhütungsvorschriften - accident prevention regulations) are legally required safety inspections of work equipment, vehicles, machinery, and installations. The legal basis is the interplay between the Betriebssicherheitsverordnung (BetrSichV - Equipment and Product Safety Regulation) and the accident prevention regulations of the German Social Accident Insurance (DGUV). The key inspection regulations are DGUV Vorschrift 3 (electrical systems and equipment), DGUV Vorschrift 68 (industrial trucks, especially forklifts), and DGUV Vorschrift 70 (vehicles). The goal is to demonstrate that all work equipment in use is maintained in a safe condition. BetrSichV requires employers to have all work equipment inspected before first use and at regular intervals by qualified persons (Befähigte Personen) or approved inspection bodies. Inspection intervals are based on hazard potential: electrical equipment is inspected every 6 to 48 months depending on the operating environment and risk classification; forklifts at least annually; company vehicles per DGUV Vorschrift 70 at least annually or per manufacturer specification. Qualified inspectors: who is authorized to inspect?: BetrSichV distinguishes between the 'qualified person' (Befähigte Person, Section 2 para. 6 BetrSichV) and the inspector for systems requiring mandatory supervision. A qualified person holds relevant professional training, work experience, and recent professional activity in the field. For systems requiring mandatory supervision (e.g., elevators, pressure vessels), an approved inspection body (ZUS) such as TUV or DEKRA is required. Companies must be able to demonstrate that inspections were conducted by qualified persons - through complete inspection documentation. **Why complete UVV compliance is essential** UVV inspections are not just a legal requirement. Companies that use them as an active safety instrument protect employees, minimize liability risk, and reduce operational disruptions. - Legal liability protection - In the event of an incident - an accident caused by defective work equipment or a vehicle - documented proof of proper inspection is the most important liability protection. If documentation is missing, companies and responsible managers face personal liability. Trade associations reduce contribution rates for companies with demonstrable UVV compliance. - Accident prevention and employee protection - Regular UVV inspections detect wear, defects, and hazards before they cause accidents. Forklift accidents from inadequately maintained hydraulics, fire risks from faulty electrical installations, and accidents from defective vehicle brakes are all preventable - when inspection intervals are maintained. - No operational disruptions from regulatory checks - Trade supervision authorities and professional associations conduct unannounced checks. If proof of due inspections is missing, operation of a piece of work equipment can be immediately prohibited. Complete digital inspection documentation prevents production stoppages and regulatory orders. - Reliable inspection deadlines for hundreds of items - Companies with large vehicle fleets, machine parks, or extensive electrical infrastructure cannot manually monitor inspection deadlines. Digital systems with automatic deadline monitoring ensure no item exceeds its inspection interval - regardless of vacation, illness, or staff turnover. - Unambiguous identification via NFC and barcode - Matching inspection records to inspected items is a common source of error. NFC tags or barcodes on vehicles, machines, and equipment enable unambiguous identification directly during inspection - no manual transcription, no mix-ups. - Insurance coverage and lower trade association contributions - Trade associations differentiate contribution rates based on prevention performance. Companies with a demonstrable UVV inspection program, low accident rates, and structured hazard management benefit from lower contributions and uncompromised insurance coverage. **Legal framework: BetrSichV, DGUV Vorschrift 3, 68, and 70** The Betriebssicherheitsverordnung (BetrSichV) is the overarching legal basis for all work equipment. It requires employers to conduct hazard assessments, define inspection intervals, and commission qualified persons. DGUV Vorschrift 3 (formerly BGV A3) governs inspection obligations for electrical systems and equipment. Items subject to inspection include fixed electrical installations, portable electrical equipment (machines, tools, extension cables), and switchgear. Inspection intervals depend on the operating environment: office environments have longer intervals than workshops, wet rooms, or areas with mechanical stress. DGUV Vorschrift 68 governs inspection obligations for industrial trucks - especially forklifts, high-lift pallet trucks, and tow vehicles. Annual inspections by qualified persons are the minimum requirement. The inspection covers chassis, mast, load-bearing equipment, safety devices, brakes, and hydraulic systems. DGUV Vorschrift 70 governs inspection obligations for vehicles in company use (commercial vehicles, construction machinery, special vehicles). Company vehicles must be inspected for safe condition at least once a year - in addition to the statutory vehicle inspection. The inspection obligation applies regardless of whether the vehicle operates on public roads or only on company premises. **Running and documenting UVV inspections** From taking stock of all items requiring inspection to complete documentation - this is how you build a legally secure UVV inspection program. - Inventory and object catalog - Capture all work equipment, vehicles, and electrical installations subject to inspection. For each item: item ID, type, location, responsible qualified person, and applicable DGUV regulation. A complete item catalog is the foundation for the entire inspection program - missing items mean missing inspection evidence. - Define inspection intervals and regulatory basis - Determine the applicable inspection interval for each item based on the hazard assessment, the relevant DGUV regulation, and manufacturer specifications. Document the derivation of the interval. For systems requiring mandatory supervision: clarify the need for an approved inspection body early and factor it into inspection planning. - Designate and commission qualified persons - Name qualified persons for each inspection area and document their qualification evidence. Ensure the qualification matches the specific inspection activity - an electrical specialist under DGUV Vorschrift 3 is not automatically qualified for forklift inspections under DGUV Vorschrift 68. - Develop inspection checklists per DGUV regulation - Develop standardized inspection checklists for each equipment category covering all inspection points required under the applicable DGUV regulation. Checklists must be designed so qualified persons can clearly judge without ambiguity: satisfactory, defects found, not inspectable. - Label items with NFC tags or barcodes - Label all items subject to inspection with NFC tags or barcodes. The labeling ensures unambiguous matching between inspection record and inspected item - including for identical items, items that have changed location, or inspections conducted by substitute personnel. - Monitor deadlines, track defects, archive records - Systematically monitor inspection deadlines and notify inspectors in good time. Create actions for identified defects with owner and deadline - mark items with open safety-relevant defects as prohibited from use. Archive all inspection records in a legally secure way: the retention requirement under BetrSichV is at minimum until the next inspection; 5-10 years is recommended. **Typical mistakes in UVV inspection programs - and how to avoid them** In many companies, the UVV inspection program fails not from lack of intent but from lack of structure. These four problem patterns are manageable. - Inspection deadlines are missed because there is no central system - Excel lists and paper calendars are no longer sufficient once the number of inspection items reaches a certain size. Digital systems with automatic deadline monitoring and push notifications to inspectors and responsible parties ensure no deadline passes unnoticed - regardless of vacations, illness, or staff changes. - Inspection records cannot be found or are incomplete - Paper inspection records get lost, are illegible, or cannot be clearly matched to the inspected item. Digital inspection records with automatic archiving, item reference, and timestamp are retrievable at any time - even years after the inspection, when a damage claim arises. - Defects are documented but not resolved - The inspection record shows the defect, but nobody follows up on the fix. Only when an inspection is 'passed' may a piece of work equipment be used again without restriction. Digital systems link defects automatically to actions that escalate if not completed on time. - Inspector qualifications are not documented - During a regulatory check, it is not enough to say the inspection was 'conducted by a qualified person'. The qualification of the qualified person must be demonstrable: training certificate, professional experience, date of last technical continuing education. These records belong in the inspection documentation. **UVV inspections - digital and legally secure with Mobile2b** Paper-based UVV inspection programs reach their limits at a certain company size. Mobile2b digitizes the entire inspection process - from NFC item identification to legally secure archiving. - Item identification via NFC or barcode - Inspectors scan the NFC tag or barcode on the item - immediate display of all relevant information: last inspection date, next due date, applicable regulation, and inspection checklist. No manual item lookup, no mix-ups, no transcription errors. - Digital inspection checklists per DGUV regulation - Configurable inspection checklists for DGUV Vorschrift 3, 68, 70, and further regulations. Each inspection point is clearly evaluated, defects documented with photos, inspection result completed with electronic signature. The inspection record is immediately available and legally securely archived. - Automatic deadline monitoring and escalation - The system automatically monitors all inspection deadlines and notifies inspectors and responsible parties well before due dates. Exceeded deadlines automatically escalate to safety officers and managers. No item falls through the cracks. - Defect management and action tracking - Identified defects automatically generate actions with owner and due date. Items with open safety-relevant defects are marked as prohibited from use. Action status is always visible on the dashboard - for safety officers, fleet managers, and facility managers. **Frequently asked questions about UVV inspections** - What is the difference between a UVV inspection, a DGUV inspection, and the statutory vehicle inspection (TUV/HU)? - A UVV inspection and a DGUV inspection are the same thing. The German accident prevention rules were renamed DGUV Vorschriften in 2014, and the old term stayed in use on the shop floor. The statutory vehicle inspection (Hauptuntersuchung, HU) under Section 29 StVZO is a mandatory check for vehicles on public roads, conducted by officially recognized inspection organizations (TUV, DEKRA, GTU). The UVV inspection under DGUV Vorschrift 70 is a company inspection obligation that applies in addition to the HU and also covers vehicles used exclusively on company premises. The UVV inspection is conducted by the company's own qualified persons, not by external inspection organizations. - What is a qualified person (Befähigte Person) under BetrSichV? - A qualified person under Section 2 para. 6 BetrSichV has the required technical knowledge for inspecting work equipment through their professional training, work experience, and recent professional activity. They must be formally commissioned in writing by the employer. For electrical equipment (DGUV Vorschrift 3), an electrical specialist is typically required. The qualified person must not be confused with the 'inspector' for systems requiring mandatory supervision, for which an approved inspection body is required. - How do I document UVV inspections digitally, and how long must the records be retained? - A digital inspection record is valid. BetrSichV does not require paper. It requires that the inspected item, the scope, the date, the result, and the qualified person who carried out the inspection can be assigned unambiguously and cannot be changed later without a trace. An inspection app with timestamps, user accounts, and versioned history meets that more easily than a binder of carbon-copy forms. BetrSichV requires inspection records to be retained at minimum until the next inspection. In practice, a retention period of 5-10 years is recommended, as damage claims under Section 195 BGB do not expire until 3 years and inspection records serve as exculpatory evidence in disputes. For serious accidents, retention beyond the normal limitation period may be relevant. - What happens if a UVV inspection is overdue? - A piece of work equipment with an expired UVV inspection deadline must not continue to be operated - the employer is required to take it out of service until the inspection is completed. Inspections by trade associations or trade supervision authorities can result in fines and operating bans. In the event of an incident, companies lose liability protection if demonstrably overdue inspections were not conducted. - Can UVV inspections be conducted by external service providers? - Yes, employers can outsource UVV inspections to external qualified persons or inspection service providers. However, responsibility for proper execution and documentation remains with the employer. External inspectors must demonstrate their qualification, and inspection records must be archived at the company. For systems requiring mandatory supervision, an approved inspection body is required in any case. - Which items fall under DGUV Vorschrift 3? - DGUV Vorschrift 3 applies to all electrical systems and equipment in the company: fixed electrical installations (building installations, switchgear, distribution boards), portable electrical equipment (machines, appliances, tools, extension cables, multi-socket adapters), as well as electrical systems in vehicles and special machinery. Only systems subject to the requirements of other specific standards with their own inspection requirements are excluded. ## Methodology guides ### Knowledge Base URL (DE): https://www.mobile2b.com/knowledge-base URL (EN): https://www.mobile2b.com/en/knowledge-base Summary: Practical guides on lean methods, quality management, and root cause analysis. Built from real experience with manufacturing and operations teams. **Methods & Techniques** **Audit Type Guides** ### Root Cause Analysis: Find the Real Cause, Not Just the Symptom URL (DE): https://www.mobile2b.com/knowledge-base/root-cause-analysis URL (EN): https://www.mobile2b.com/en/knowledge-base/root-cause-analysis Summary: A practical guide to the methods, processes, and tools that help quality and operations teams stop fixing the same problems over and over. **What is root cause analysis?** Root cause analysis (RCA) is a structured process for identifying the underlying cause of a problem rather than just treating its visible symptoms. When a machine breaks down, a batch fails quality checks, or a customer complaint arrives, the natural response is to fix the immediate issue and move on. RCA goes deeper. It asks: why did this happen, and what systemic condition allowed it to happen? The answer is often not the first thing that comes to mind. RCA is not a single method. It is a family of techniques, each suited to different situations. The 5 Whys method works well for straightforward problems with a linear cause chain. Ishikawa (fishbone) diagrams help when multiple factors contribute to a problem across different categories. Pareto Analysis helps you prioritize which causes to investigate first by identifying the vital few responsible for most problems. 8D reports provide a team-based framework for complex customer-facing issues. Fault tree analysis handles safety-critical scenarios. What they all share is the same core principle: do not stop at the first explanation. Keep digging until you reach the cause that, once removed, prevents the problem from recurring. The difference between correction and root cause analysis: A correction fixes the immediate problem: rework the defective part, replace the broken sensor, retrain the operator. Root cause analysis asks why the part was defective, why the sensor broke, or why the operator made the error. Without RCA, corrections become a recurring cost. With RCA, each problem you solve makes your entire operation more reliable. **Why root cause analysis matters for your operations** Organizations that invest in structured RCA spend less time fighting fires and more time improving. The numbers show it clearly. - Recurring problems actually stop recurring - The most obvious benefit is also the most valuable. A proper RCA identifies and eliminates the systemic cause, not just the symptom. Manufacturing teams that implement structured RCA typically see repeat nonconformances drop by 40-60% within the first year. - Quality costs decrease measurably - Every recurring defect carries hidden costs: scrap, rework, sorting, expedited shipping, customer complaint handling. The cost of one RCA investigation is a fraction of what a single recurring defect costs over a year. ISO defines this as the cost of poor quality (COPQ), and RCA is the primary lever to reduce it. - Audit and compliance readiness improves - ISO 9001, IATF 16949, FDA regulations, and GMP guidelines all require documented root cause analysis for nonconformances. A well-maintained RCA process is not extra audit prep work. It is the audit evidence itself. Auditors check RCA records as their first indicator of a functioning quality system. - Teams build institutional knowledge - Each completed RCA adds to a searchable record of what went wrong, why, and how it was fixed. New team members, new production lines, and new product launches all benefit from lessons already learned. This knowledge compounds over time. - Decision-making becomes data-driven - RCA forces teams to gather evidence before drawing conclusions. Instead of blaming "operator error" or "supplier quality," the investigation follows evidence to the actual contributing factors. This changes how organizations think about problems. - Cross-functional collaboration improves - Most root causes span multiple departments. A quality defect might originate in design, surface in production, and get reported by the customer. RCA brings the right people together around evidence rather than assumptions. **Choosing the right RCA method for your situation** Not every problem needs the same level of analysis. A simple equipment failure has different investigation needs than a systemic quality trend affecting multiple product lines. The key is matching the method to the complexity and impact of the problem. The 5 Whys method is your starting point for most investigations. It works by asking "Why?" repeatedly (typically five times, but the number is a guideline, not a rule) until you reach a cause that is actionable and systemic. It is fast, requires no special training, and works well for problems with a single cause chain. When a problem has multiple contributing factors, the Ishikawa (fishbone) diagram provides structure. It organizes potential causes into categories (the classic 6Ms: Man, Machine, Material, Method, Measurement, Mother Nature) and helps teams think systematically instead of jumping to conclusions. For complex customer complaints that need containment, investigation, and prevention, the 8D report provides an eight-discipline team-based framework used widely in automotive and manufacturing. For safety-critical analysis, fault tree analysis (FTA) uses Boolean logic to map all possible failure paths. **Step-by-step root cause analysis process** Regardless of which specific method you choose, every effective RCA follows the same fundamental steps. - Define the problem clearly - State what happened, when, where, and what the impact was. Be specific: "Batch 4712 failed hardness test on 2024-03-15, 23 of 500 parts below spec" is useful. "Quality problem with parts" is not. A clear problem statement prevents the investigation from drifting. - Contain the immediate impact - Before investigating the root cause, stop the bleeding. Quarantine affected products, notify customers if needed, implement a temporary fix. Containment is not root cause analysis, but it buys you time to investigate properly without pressure. - Gather data and evidence - Collect everything relevant: process parameters, inspection records, maintenance logs, operator notes, environmental conditions. Visit the actual workplace (gemba) where the problem occurred. The evidence you collect now determines the quality of your analysis. - Identify the root cause - Apply your chosen method. For 5 Whys: ask why iteratively until you reach an actionable systemic cause. For fishbone: brainstorm causes across all 6M categories, then verify with data. For 8D: use the team to work through disciplines D4 (root cause) and D5 (permanent corrective action). The root cause should be something you can fix, not a vague statement. - Define and implement corrective actions - For each identified root cause, define a specific corrective action with a named owner and deadline. The corrective action should eliminate the root cause, not just add another check or inspection step. If your "fix" is "add another inspection," you probably have not found the root cause yet. - Verify effectiveness - This is the step most organizations skip, and it is the most important one. After implementing the corrective action, verify with data that the problem actually stopped. Monitor the relevant metrics for an appropriate period. Only close the RCA when evidence confirms the fix worked. **Common RCA mistakes and how to avoid them** - Human error is never a root cause. It is a symptom. Ask why the error was possible: Was the process unclear? Was the workstation designed for mistakes? Was there a missing poka-yoke? Root cause analysis should reach the system condition that allowed the error. - Without verification, you are guessing that your fix worked. Define measurable success criteria upfront (e.g., zero recurrences in 90 days, defect rate below 0.1%). Check the data after implementation. If the problem returns, reopen the investigation. - A simple equipment failure does not need an 8D report, and a complex multi-factor quality trend cannot be solved with a quick 5 Whys. Match the investigation depth to the problem severity and complexity. Train your team in multiple methods. - If people fear that RCA will assign personal blame, they will hide information and the investigation will fail. Focus on system and process causes. Use language like "the process allowed" rather than "the person failed to." Build a culture where reporting problems is valued. **Root cause analysis with Mobile2b** Mobile2b gives your team the digital tools to run structured root cause investigations from problem detection through verified resolution. - Structured investigation workflows - Pre-built RCA templates for 5 Whys, Ishikawa, and 8D guide your team through each step. No training needed to get started. Every investigation follows the same documented process. - Complete traceability - Every finding, every decision, every corrective action is logged with timestamps, photos, and responsible persons. Your audit trail is built automatically as you work through the investigation. - Real-time dashboards and analytics - Track open RCAs, overdue actions, recurring problem categories, and effectiveness verification status. Identify patterns across investigations that manual tracking would miss. - Integration with your audit process - RCA findings from audits, inspections, and customer complaints flow into the same system. Link root causes across investigations to spot systemic issues that span multiple departments or product lines. **Frequently asked questions about root cause analysis** - What is the difference between root cause analysis and problem solving? - Problem solving addresses the immediate issue. Root cause analysis goes further by identifying why the problem occurred in the first place and putting measures in place to prevent it from happening again. RCA is one part of a broader problem-solving process. You can solve a problem without RCA (by fixing the symptom), but the problem will likely return. - Which RCA method should I use? - Start with the 5 Whys for straightforward problems with a likely single cause. Use Ishikawa diagrams when multiple departments or factors might contribute. Use 8D for complex customer complaints that need containment plus investigation. Fault tree analysis is best for safety-critical scenarios. In practice, many investigations combine methods: a fishbone diagram to brainstorm potential causes, then 5 Whys to drill into the most likely branch. - How long should a root cause analysis take? - A simple 5 Whys investigation can be completed in a single meeting (30-60 minutes). A full 8D report for a complex customer complaint typically takes 2-4 weeks. The timeframe should match the severity: a safety issue needs immediate investigation, while a trend in minor nonconformances can be analyzed over days. Do not rush to a conclusion, but also do not let investigations drag on indefinitely. - Is root cause analysis required by ISO 9001? - Yes. ISO 9001:2015 clause 10.2 requires organizations to determine the cause of nonconformities and take corrective action. While the standard does not prescribe a specific RCA method, it expects a systematic approach and evidence of effectiveness. IATF 16949 goes further in clause 10.2.3, requiring specific problem-solving methods and proven root cause analysis techniques. - How do I verify that a corrective action actually worked? - Define measurable success criteria before implementing the fix. Common approaches: monitor the specific defect metric for 60-90 days, run a targeted audit of the affected process, review the next batch of the same product. The key is using data, not opinions. If the problem recurs within the monitoring period, the root cause was not adequately addressed. - Can root cause analysis be done digitally? - Yes, and digital tools offer real advantages: standardized templates ensure consistent investigation quality, automatic notifications keep actions on track, photo and document attachment provides evidence, and analytics across investigations reveal patterns. Mobile2b provides digital workflows for 5 Whys, Ishikawa, 8D, and CAPA processes that connect directly to your audit and inspection data. ### The Ultimate Guide to 5 Whys Root Cause Analysis URL (DE): https://www.mobile2b.com/knowledge-base/5-whys-root-cause-analysis URL (EN): https://www.mobile2b.com/en/knowledge-base/5-whys-root-cause-analysis Summary: Use the 5 Whys technique to find the real root cause of problems in manufacturing, quality management, and operations systematically. **What is the 5 Whys Method?** The 5 Whys is a root cause analysis technique developed by Sakichi Toyoda and used within the Toyota Production System. The method is simple: when a problem occurs, you ask "Why?" repeatedly - typically five times - until you move past the symptoms and reach the underlying cause. It was originally designed for manufacturing problem-solving but is now used across industries from healthcare to software development. The power of the method lies in its simplicity. Unlike complex tools like fault tree analysis or FMEA, the 5 Whys requires no statistical training, no special software, and no external consultants. A team that understands the process can conduct a meaningful root cause analysis in 15-30 minutes. But simplicity is not the same as easy - asking the right "Why?" at each level requires discipline and domain knowledge. 5 Whys is not brainstorming: The most common mistake: treating 5 Whys as a free-form discussion where people throw out opinions. Each "Why" must be answered with a verifiable fact, not a guess. If you cannot verify the answer, you need to investigate before proceeding. A 5 Whys analysis built on assumptions leads to the wrong root cause - and the wrong corrective action. **Why the 5 Whys method delivers real results** Root cause analysis separates effective problem-solving from firefighting. The 5 Whys is the fastest path from symptom to cause. - Problems stop recurring - When you fix the root cause instead of the symptom, the problem does not come back. Organizations that adopt systematic root cause analysis report 40-60% fewer recurring quality issues. - No training required - Unlike Six Sigma tools or statistical process control, the 5 Whys can be used by any team member. Shop floor operators, team leaders, and engineers can all participate meaningfully. - Fast to execute - A structured 5 Whys session takes 15-30 minutes. Compare that to a full FMEA or 8D report that can take days. For the majority of operational problems, the 5 Whys gets you to the cause faster. - Exposes systemic issues - Following the chain of causes often reveals process or management system failures that would otherwise remain hidden. A machine breakdown might trace back to a missing preventive maintenance schedule. - Builds problem-solving culture - When teams regularly practice 5 Whys, they develop a habit of asking "why" instead of accepting problems as normal. This cultural shift is more valuable than any single root cause found. - Integrates with existing quality systems - The 5 Whys works as a standalone tool or as part of 8D reports, A3 problem-solving, CAPA processes, and ISO nonconformance handling. It fits into what you already have. **The 5 Whys process step by step** Start by defining the problem clearly and specifically. Not "quality is bad" but "Part XY-4023 failed dimensional inspection at station 7 on March 15 - diameter was 12.08mm vs. tolerance of 12.00 +/- 0.05mm." The more specific the problem statement, the more effective the analysis. Then ask "Why did this happen?" and answer with a verified fact. Why was the diameter out of spec? Because the tool was worn. Why was the tool worn? Because it exceeded its scheduled replacement interval. Why did it exceed the interval? Because there is no automated tracking of tool life. Continue until you reach a cause that you can act on - something within your control to change. The number five is a guideline, not a rule. Some problems need three Whys, others need seven. You know you have reached the root cause when the answer is a process failure, a missing standard, or a management system gap - not a person's mistake. If your 5 Whys ends with "because the operator did not pay attention," you have not gone deep enough. Ask why the process allowed that error to happen. **Implementing 5 Whys in your organization** From the first analysis on a whiteboard to a systematic problem-solving program - here is how to make 5 Whys part of your daily operations. - Define the problem statement precisely - Use the 4W format: What happened, Where it happened, When it happened, and What is the impact. A vague problem statement produces a vague analysis. Write it down before starting the Whys. - Assemble the right people - Include people who work directly with the process - operators, technicians, team leaders. Avoid analysis by managers alone in a conference room. The people closest to the work have the best understanding of what actually happened. - Ask Why with verified facts - Each answer must be based on observation, data, or evidence. Go to the place where the problem occurred (Gemba). Look at the actual parts, machines, and records. If you are guessing, stop and investigate first. - Follow multiple branches when needed - Problems often have more than one contributing cause. When a Why has two valid answers, follow both branches. Draw a fishbone or tree diagram to track parallel chains. Address all root causes, not just the first one you find. - Define corrective actions with owners and deadlines - Every root cause must result in a specific action: what will change, who is responsible, and by when. Actions should prevent recurrence, not just fix the immediate problem. Verify effectiveness after implementation. - Document and share the analysis - Record the full chain of Whys, the root cause, and the corrective actions. Share with other teams and shifts - the same root cause may exist in other areas. Build a searchable library of past analyses to accelerate future problem-solving. **Common 5 Whys mistakes - and how to avoid them** The method is simple but not foolproof. These are the pitfalls that make the difference between a useful analysis and a waste of time. - The analysis stops at human error - "The operator made a mistake" is never a root cause. Always ask: why did the process allow this error? Was there no poka-yoke? No visual standard? No training verification? The root cause is always in the system, not the person. - Answers are based on assumptions instead of facts - Go to Gemba. Look at the actual evidence. If you cannot verify an answer, it is a hypothesis - not a cause. Pause the analysis, gather data, then continue. A wrong root cause leads to a wrong corrective action. - Only one causal chain is followed - Most problems have multiple contributing causes. When a Why has two plausible answers, branch the analysis and follow both. Use a tree diagram or fishbone to visualize. Address all root causes for a lasting fix. - Corrective actions are not tracked to completion - A brilliant root cause analysis is worthless if the corrective action never gets implemented. Assign clear owners, set deadlines, and verify effectiveness. Digital tracking ensures nothing falls through the cracks. **5 Whys Analysis: 5 Whys Digital with Mobile2b** Paper-based root cause analyses get filed away and forgotten. Mobile2b makes every 5 Whys analysis trackable, searchable, and actionable. - Guided analysis workflow - Step-by-step 5 Whys templates guide teams through the process - from problem statement through each Why to corrective actions. Consistent structure, every time. - Corrective action tracking - Every root cause generates a tracked action with owner, deadline, and status. Automatic reminders ensure follow-through. Verify effectiveness with follow-up checks. - Searchable analysis library - All past 5 Whys analyses are searchable by problem type, area, and root cause category. Before starting a new analysis, check if the same root cause was found before. - Integration with audit findings - Link 5 Whys analyses directly to audit nonconformances, customer complaints, or safety incidents. One platform for finding problems and solving them. **Frequently Asked Questions About the 5 Whys Method** - Why exactly five Whys? - Five is a guideline based on Toyota's experience, not a strict rule. Some problems need only three Whys to reach the root cause, others may need seven. You stop when you reach a cause that is actionable and within your control to change - typically a process gap or missing standard. - When should I use 5 Whys vs. other root cause analysis tools? - Use 5 Whys for single-event problems with a relatively clear chain of causes - a machine breakdown, a quality defect, a missed delivery. For complex, multi-factor problems with statistical variation, tools like FMEA, fault tree analysis, or Ishikawa diagrams may be more appropriate. The 5 Whys is often a good starting point even for complex problems. - Can 5 Whys be used outside of manufacturing? - Absolutely. The method works wherever problems have causes: IT incident management, healthcare adverse events, logistics delays, software bugs, customer complaints. The principle is universal - symptoms have causes, and causes have deeper causes. - How do I know when I have found the real root cause? - A good root cause test: if you eliminate this cause, would the problem be prevented? If yes, and the cause is something you can act on (a process change, a missing standard, a system gap), you have found a root cause. If the cause is outside your control, keep asking why within your scope. - What is the relationship between 5 Whys and 8D? - The 5 Whys is often used within step D4 (Root Cause Analysis) of the 8D problem-solving methodology. The 8D provides the overall framework - team formation, problem description, containment, corrective actions, prevention - while the 5 Whys is the specific tool used to identify the root cause. - How do I prevent 5 Whys from becoming a blame exercise? - Set a ground rule: no person's name appears in any Why answer. If a Why leads to human error, immediately ask why the process allowed it. Focus on systems and processes, not individuals. This is not just a cultural preference - it produces better root causes because human error is always a symptom of a system problem. ### Fishbone Diagram: Root Cause Analysis URL (DE): https://www.mobile2b.com/knowledge-base/ishikawa-fishbone-diagram URL (EN): https://www.mobile2b.com/en/knowledge-base/ishikawa-fishbone-diagram Summary: Use the Ishikawa diagram with 6M categories to systematically identify root causes in manufacturing, quality, and operations. **What is the Ishikawa/Fishbone Diagram?** The Ishikawa diagram - also called fishbone diagram or cause-and-effect diagram - is a structured root cause analysis tool developed by Kaoru Ishikawa in the 1960s at the University of Tokyo. The diagram visually maps all potential causes of a problem, organized into categories that branch off a central spine like the bones of a fish. It was originally created for quality control in Japanese shipbuilding and became a cornerstone of Total Quality Management (TQM) worldwide. Unlike linear methods such as the 5 Whys, the fishbone diagram excels at capturing multiple parallel cause categories simultaneously. It is a structured brainstorming tool: the team works through each category systematically, identifying potential causes rather than jumping to the first obvious explanation. The visual format makes it immediately clear where the team has investigated thoroughly and where gaps remain. This is why Ishikawa diagrams are one of the Seven Basic Tools of Quality alongside check sheets, Pareto charts, histograms, scatter diagrams, control charts, and stratification. Fishbone diagrams are not brainstorming free-for-alls: The most common misuse: treating the fishbone diagram as a wall of sticky notes where every opinion gets posted without validation. Each potential cause must be testable and specific. 'Bad training' is too vague - 'No documented work instruction for setup procedure XY-401' is actionable. After brainstorming, the team must verify which causes actually contributed to the problem using data, observation, or experimentation. A fishbone diagram full of unverified guesses leads to scattered corrective actions that fix nothing. **Why Ishikawa diagrams deliver better root cause analysis** The fishbone diagram turns chaotic problem-solving into structured investigation. Here is why teams that use it find root causes faster and more reliably. - Captures all cause categories systematically - The 6M framework ensures no category of potential causes is overlooked. Teams that brainstorm without structure tend to fixate on the most obvious category - usually Man or Machine - and miss causes in Method, Material, Measurement, or Environment. - Makes team knowledge visible - The visual format surfaces knowledge from different disciplines simultaneously. An operator sees a machine issue, a quality engineer spots a measurement gap, a process engineer identifies a method flaw - all on the same diagram. This cross-functional visibility is the diagram's greatest strength. - Organizes complex problems - Problems with many potential contributing factors become manageable when organized into categories. A customer complaint about product quality might involve material variations, machine settings, operator training, and environmental conditions - the fishbone keeps all of these organized and investigable. - Shows investigation gaps - Empty branches reveal where the team has not yet investigated. If the Material and Measurement branches are blank, it is not because there are no potential causes there - it is because nobody with that expertise was in the room or those areas were not examined. - Focuses corrective actions - Once verified, the causes on the diagram point directly to specific corrective actions. A cause under Machine leads to a maintenance action, a cause under Method leads to a procedure update. The category structure naturally organizes the response. - Complements other analysis tools - The fishbone diagram works powerfully in combination with 5 Whys, FMEA, and 8D methodology. Use the fishbone to identify all potential cause categories first, then apply 5 Whys to drill down each confirmed branch. This combination covers both breadth and depth. **The 6M categories explained** The classic Ishikawa diagram uses six categories - the 6Ms - to organize potential causes. Man (Personnel): operator skills, training, experience, fatigue, and human factors. Machine: equipment condition, calibration, wear, maintenance status, and tool life. Material: raw material quality, supplier variation, storage conditions, and incoming inspection results. Method: work instructions, process parameters, standard operating procedures, and sequence of operations. Measurement: gauge accuracy, calibration status, measurement method, and inspector variability. Mother Nature/Environment: temperature, humidity, lighting, vibration, cleanliness, and contamination. The 6M categories are a starting framework, not a rigid template. In service industries, teams often use categories like People, Process, Technology, Policy, Place, and Procedures instead. In healthcare, the categories might be Patients, Procedures, People, Place, Policies, and Equipment. The key principle remains the same: organize potential causes into distinct categories so that investigation is systematic rather than random. For manufacturing, the 6Ms have proven remarkably effective because they map directly to the controllable variables in any production process. **Building a fishbone diagram step by step** From problem definition to verified root causes - here is how to run an effective Ishikawa analysis session. - Define the problem statement (the fish head) - Write a clear, specific problem statement at the right side of the diagram - this is the 'head' of the fish. Not 'quality problems' but 'Surface finish defects on Part AB-2045 increased from 0.8% to 3.2% scrap rate in the last 4 weeks.' Specific problems produce specific causes. - Draw the spine and main category branches - Draw a horizontal arrow pointing to the problem statement. Add six diagonal branches for each M category: Man, Machine, Material, Method, Measurement, and Mother Nature. This is the skeleton of your diagram. Use a whiteboard, flip chart, or digital tool - the format matters less than visibility for all participants. - Brainstorm causes within each category - Work through each M category one at a time. For each branch, ask: 'What factors in this category could contribute to this problem?' Add each potential cause as a sub-branch. Go deeper by asking 'why' for each cause to find sub-causes. Spend at least 5 minutes per category - do not rush past categories that seem less likely. - Identify the most likely root causes - After brainstorming, review all causes and mark the ones the team considers most likely. Use dot voting or expert judgment to narrow down from 20-30 potential causes to the 3-5 most probable ones. These are your hypotheses, not conclusions yet. - Verify causes with data and evidence - For each probable cause, define how to verify or rule it out. Check machine logs, review material certificates, observe the process, analyze measurement system data. Only verified causes become confirmed root causes. This step separates useful fishbone analysis from opinion-based guesswork. - Define corrective actions for verified causes - Each confirmed root cause gets a specific corrective action with an owner, a deadline, and a verification method. Track actions to completion and verify effectiveness. If the problem does not improve after implementing corrections, revisit the fishbone - a cause was missed or incorrectly verified. **Common fishbone diagram mistakes - and how to avoid them** The method is visual and intuitive, but these pitfalls can turn a fishbone diagram from a powerful analysis tool into a decoration on a conference room wall. - Causes are too vague to act on - Entries like 'training', 'communication', or 'maintenance' are categories, not causes. Push for specifics: 'No documented setup procedure for machine X' or 'Incoming material hardness not tested for supplier Y.' If you cannot define a corrective action from the cause statement, it is not specific enough. - The diagram is never verified against data - A fishbone full of unverified potential causes is a list of opinions. After the brainstorming session, assign investigation tasks for the top candidates. Check machine data, review records, run experiments. Remove causes that the data does not support. The verified diagram is the real deliverable, not the brainstorming output. - Some M categories are skipped or underdeveloped - Teams naturally gravitate toward familiar categories and skip unfamiliar ones. If the Measurement branch is empty, invite a metrology or quality inspector to contribute. If Environment is blank, physically go to the production area and observe conditions. Empty branches mean incomplete analysis. - The fishbone is used in isolation without follow-through - Creating the diagram is only the first step. Without verified causes, defined corrective actions, and tracked implementation, the fishbone is just an exercise. Connect it to your corrective action system - every verified root cause must result in a tracked, owned, deadline-bound action. **Ishikawa/Fishbone Diagram: Fishbone Diagrams Digital with Mobile2b** Paper fishbone diagrams capture great insights in the moment but rarely drive lasting improvement. Mobile2b makes Ishikawa analysis structured, trackable, and connected to your corrective action workflow. - Guided 6M analysis templates - Pre-structured templates walk teams through each M category systematically. No blank-page problem - the framework ensures comprehensive coverage. Teams add causes directly on mobile devices during the analysis session. - Searchable cause library - All past fishbone analyses are searchable by problem type, product, line, and root cause category. Before starting a new analysis, check if similar causes were found before. Build organizational knowledge instead of reinventing the wheel. - Root cause analytics and Pareto analysis - Aggregate data across multiple fishbone analyses to identify recurring root cause patterns. Which M category produces the most confirmed causes? Which corrective actions are most effective? Data-driven insights reveal systemic issues that individual analyses miss. - Integrated corrective action tracking - Every verified root cause automatically generates a tracked corrective action with owner, deadline, and status. Link fishbone analyses to audit findings, customer complaints, or safety incidents. One platform from cause identification to verified fix. **Frequently Asked Questions About Ishikawa/Fishbone Diagrams** - What is the difference between a fishbone diagram and 5 Whys? - The fishbone diagram maps causes broadly across multiple categories (breadth), while 5 Whys drills deep into a single causal chain (depth). They complement each other: use the fishbone to identify all potential cause categories first, then apply 5 Whys to the most probable branches. Together, they cover both the breadth and depth of root cause analysis. - Do I always have to use the 6M categories? - No. The 6Ms (Man, Machine, Material, Method, Measurement, Mother Nature) are the standard for manufacturing, but you should adapt the categories to your context. Service industries often use People, Process, Technology, Policy. Healthcare uses Patients, Procedures, People, Place. The principle - organizing causes into distinct categories for systematic investigation - matters more than the specific category names. - How many people should participate in a fishbone session? - Ideally 4-8 people from different functions: operators, engineers, quality, maintenance, and anyone with direct knowledge of the process. Fewer than 4 limits the range of perspectives. More than 10 makes the session hard to manage. The most important thing is having people who actually work with the process, not just managers reviewing from a distance. - How long should a fishbone analysis session take? - Plan 45-90 minutes for the brainstorming session, plus additional time for verification activities afterward. Spend at least 5-10 minutes per M category during brainstorming. Rushing through categories leads to superficial analysis. The verification phase - checking data, reviewing records, observing the process - typically takes 1-5 days depending on complexity. - Can I use fishbone diagrams for problems outside manufacturing? - Absolutely. The fishbone diagram works in any domain where a problem has multiple potential cause categories: IT incident analysis, customer service complaint investigation, logistics delays, project management failures, healthcare adverse events. Adapt the category labels to fit your domain and the method works just as well. - How do I know which causes on the fishbone are the real root causes? - Brainstorming produces hypotheses, not conclusions. After the session, prioritize the 3-5 most probable causes and verify each one with data. Check machine logs, review supplier certificates, analyze measurement records, observe the process. A cause is confirmed only when evidence supports it. If removing a confirmed cause would prevent the problem, you have found a root cause. ### 8D Report: Problem Solving Guide URL (DE): https://www.mobile2b.com/knowledge-base/8d-report URL (EN): https://www.mobile2b.com/en/knowledge-base/8d-report Summary: Use the 8D methodology to systematically solve problems, eliminate root causes, and prevent recurrence in automotive and manufacturing. **What is the 8D Report?** The 8D Report (Eight Disciplines Problem Solving) is a structured methodology for identifying, correcting, and eliminating recurring problems. Originally developed by Ford Motor Company in 1987, the method has become the global standard for handling customer complaints and quality issues in the automotive industry. It is required by major OEMs and tier suppliers, and is closely aligned with VDA, IATF 16949, and other automotive quality standards. The "8D" refers to eight disciplines - sequential steps that guide a cross-functional team from problem detection through root cause analysis to permanent corrective action and prevention. What makes 8D different from simpler methods like the 5 Whys is its emphasis on team-based problem solving, immediate containment actions to protect the customer, and systematic verification that the solution actually works. An 8D report is not just an analysis - it is a complete problem resolution record. 8D vs. quick fixes: The most common failure mode in problem solving is jumping to solutions. A machine breaks down, someone fixes it, and the same failure happens again two weeks later. The 8D method forces a different approach: first contain the problem to protect the customer, then analyze the root cause with data, then verify the fix before closing the report. This takes more time upfront but eliminates the cycle of recurring problems that consumes far more resources in the long run. **Why the 8D method delivers lasting results** The 8D methodology transforms reactive firefighting into structured problem elimination. Here is what organizations gain from consistent 8D practice. - Cross-functional team ownership - 8D requires a defined team with members from different functions - quality, production, engineering, logistics. This ensures problems are analyzed from multiple perspectives and solutions address all contributing factors, not just the most obvious one. - Customer protection through containment - D3 (Interim Containment Actions) immediately shields the customer from defective products while the root cause investigation continues. This separates 8D from methods that leave the customer exposed during analysis. Containment actions include sorting, rework, or replacement shipments. - Root cause elimination, not symptom treatment - D4 and D5 require both the root cause of the problem and the root cause of the escape (why it was not detected). Addressing both ensures the defect does not recur and does not slip past quality controls again. - Auditable problem resolution record - A completed 8D report provides a full traceability record from problem description through analysis to verified corrective action. This satisfies customer audit requirements and regulatory documentation needs under IATF 16949, VDA, and ISO 9001. - Measurable quality improvement - Organizations with mature 8D processes typically see 30-50% reduction in recurring customer complaints within the first year. Each solved 8D feeds lessons learned back into FMEA, control plans, and process standards. - Global standard for supplier quality - 8D is the lingua franca of supplier quality management. When a customer sends a quality complaint, they expect an 8D response. Mastering the method is not optional for suppliers in automotive, aerospace, and other regulated industries. **The 8 Disciplines step by step** D0 - Prepare: Identify the symptoms, assess the need for an 8D, and gather initial data. Not every problem requires a full 8D - use it for recurring, complex, or customer-affecting issues. D1 - Establish the Team: Form a cross-functional team with the knowledge, authority, and time to solve the problem. Assign a champion and a team leader. D2 - Describe the Problem: Define what is wrong using the IS/IS NOT method. What is the defect? Where does it occur? When did it start? How big is the impact? The more precise the problem description, the more focused the investigation. D3 - Interim Containment Actions (ICA): Implement immediate actions to contain the problem and protect the customer. This may include sorting suspect inventory, adding inspection steps, or shipping from an alternative source. Verify that containment actions work. D4 - Root Cause Analysis: Identify all potential causes and verify the true root cause with data. Use tools like 5 Whys, Ishikawa diagrams, or designed experiments. Prove that the root cause explains the problem and that removing it eliminates the defect. D5 - Choose Permanent Corrective Actions (PCA): Select the best long-term corrective actions to eliminate the root cause. Verify through pre-production testing or pilot runs that the PCA works without side effects. D6 - Implement and Validate PCA: Roll out the permanent corrective actions, remove interim containment, and monitor results. Validate with data that the problem is solved. D7 - Prevent Recurrence: Update FMEAs, control plans, work instructions, and training to prevent the same or similar problems in other products, processes, or plants. D8 - Congratulate the Team: Recognize the team's effort and document lessons learned. This step is often skipped but is essential for sustaining a problem-solving culture. **Implementing 8D in your organization** From the first customer complaint response to a mature 8D program - here is how to build the capability. - Train cross-functional 8D teams - 8D is a team method - it does not work as a solo activity. Train groups that include quality, engineering, production, and logistics. Practice with real past problems before handling live customer complaints. Focus on the discipline of evidence-based analysis, not just filling out a form. - Define clear trigger criteria - Not every quality issue needs a full 8D. Define when an 8D is required: customer complaints above a severity threshold, recurring defects, safety-related issues, or field failures. Use simpler methods (5 Whys, quick kaizen) for routine problems to avoid 8D fatigue. - Master the IS/IS NOT problem description - D2 is where most 8D reports fail. A vague problem description leads to unfocused analysis. Train teams to use the IS/IS NOT format: What IS the defect vs. what is it NOT? Where IS it found vs. where is it NOT found? When DID it start vs. when did it NOT occur? This sharpens the investigation. - Separate containment from correction - D3 (containment) and D5/D6 (permanent corrective action) are fundamentally different. Containment is fast and temporary - sorting, additional inspection, rework. Correction is permanent - process change, design change, error-proofing. Never confuse a containment action with a root cause fix. - Verify effectiveness with data - An 8D is not complete until D6 validation proves the problem is solved. Define measurable success criteria before implementing corrective actions. Monitor for a defined period (typically 3-6 months) to confirm the defect does not recur. Without verification, you are guessing. - Feed lessons back into prevention - D7 is the highest-value step and the most commonly skipped. Every solved 8D should update the relevant FMEA, control plan, and work instructions. Apply the lesson across similar products and processes. This is how 8D transforms from a reactive tool into a prevention system. **Common 8D mistakes - and how to avoid them** The 8D method is powerful but frequently misapplied. These are the pitfalls that turn a structured methodology into a paperwork exercise. - The 8D report is filled out by one person after the fact - 8D is a team method. When one quality engineer writes the report alone, it becomes a form-filling exercise with guessed root causes. Insist on actual team sessions with cross-functional participation. The report documents the team's analysis, not one person's opinion. - Root cause analysis stops at the obvious answer - "Operator error" or "supplier sent bad parts" is never a root cause. Ask why the process allowed the error. Why did incoming inspection not catch the defect? Why was the operator not error-proofed? Use 5 Whys or Ishikawa to go deeper. The root cause is always in the system. - Containment actions become permanent solutions - Adding an extra inspection step is containment, not correction. If your D6 corrective action is "additional visual inspection," you have not solved the root cause. Permanent corrective actions must eliminate the cause so that containment is no longer needed. - D7 prevention step is skipped or treated as a formality - Without D7, each 8D is an isolated fix. Update FMEAs with the new failure mode and cause. Revise control plans. Check if the same risk exists on other product lines. Share lessons learned across plants. D7 is what turns individual problem-solving into organizational learning. **8D Report Management: 8D Reports Digital with Mobile2b** Paper-based 8D reports get lost in email chains and shared drives. Mobile2b makes the entire 8D process trackable, collaborative, and auditable. - Guided 8D workflow - Step-by-step templates guide teams through all eight disciplines - from team formation and problem description through root cause analysis to prevention. Built-in prompts ensure no step is skipped or done superficially. - Cross-functional collaboration - Team members from quality, engineering, production, and logistics work on the same 8D in real time. Comments, photo evidence, and analysis results are captured in one place - no more email chains or version conflicts. - Corrective action tracking - Every containment and corrective action generates a tracked task with owner, deadline, and status. Automatic escalation when deadlines are missed. Full audit trail from problem detection to verified solution. - Analytics and trend detection - Dashboard views show open 8D reports by status, response time trends, and recurring root cause categories. Identify patterns across complaints before they become systemic quality issues. **Frequently Asked Questions About the 8D Report** - What is the difference between 8D and 5 Whys? - The 5 Whys is a root cause analysis tool - it helps you find why a problem occurred. The 8D is a complete problem-solving methodology that includes team formation, problem description, containment, root cause analysis (where you might use 5 Whys), corrective action, verification, and prevention. Think of 5 Whys as a tool you use within step D4 of the 8D process. - When should I use 8D vs. a simpler problem-solving method? - Use 8D for customer complaints, recurring defects, safety issues, and problems with significant impact. For routine operational issues with straightforward causes, simpler methods like 5 Whys or quick kaizen are more efficient. A good rule: if the problem requires cross-functional investigation and the customer is affected, use 8D. - What software do you use to create 8D reports? - Many teams still write 8D reports in Word or Excel templates. That holds up until you need to track open actions across several reports, show an auditor that D5 was verified, or find every 8D that shares the same root cause. Dedicated 8D software keeps the eight disciplines as structured fields instead of free text, so deadlines, owners, and evidence stay attached to the report. Mobile2b has a free 8D report generator that produces a complete, customer-ready report in the standard format, and the platform adds approvals, supplier reports, and recurrence analysis on top of it. - What is the 8D report format? - An 8D report follows a fixed document structure, so any customer or auditor can read it without an explanation. The header block identifies the report: complaint or claim number, part number and description, customer, supplier, opening date, team leader, and current status. Below it sit eight numbered sections, one per discipline, from D1 team to D8 closure. Each section records the action taken, the evidence behind it, an owner, and a date. Most customer portals expect exactly this order and send back reports where the evidence fields are empty. Timing belongs to the format as well: D3 containment is normally due within 24 to 48 hours, and the first full response within 5 to 10 working days. - What is the relationship between 8D and IATF 16949? - IATF 16949 requires documented processes for handling nonconforming products and customer complaints (clauses 8.7 and 10.2). The 8D method is the most widely accepted approach for meeting these requirements. While IATF does not mandate 8D specifically, most automotive OEMs and auditors expect it as the standard complaint response format. - How do I handle 8D reports from suppliers? - When reviewing supplier 8D reports, check for three things: Is the root cause verified with data (not just stated)? Does the corrective action address the root cause (not just add inspection)? Does D7 show systemic prevention measures? Reject reports that list containment as permanent correction or that blame operator error without explaining what process allowed the error. ### CAPA: Corrective & Preventive Action URL (DE): https://www.mobile2b.com/knowledge-base/capa-corrective-preventive-action URL (EN): https://www.mobile2b.com/en/knowledge-base/capa-corrective-preventive-action Summary: Systematically resolve quality issues and prevent recurrence with a structured CAPA process for ISO 9001 and beyond. **What is CAPA?** CAPA stands for Corrective Action / Preventive Action. It is a systematic approach used in quality management to investigate the root cause of nonconformances, implement corrections that eliminate the cause, and put preventive measures in place so the problem never recurs. CAPA is required by virtually every major quality standard - ISO 9001, IATF 16949, FDA 21 CFR Parts 211 and 820, AS9100, and GMP regulations all mandate a documented CAPA process. The distinction between the two halves matters. A corrective action responds to something that already went wrong - a customer complaint, an audit finding, a rejected batch. A preventive action responds to a risk or trend identified before a failure occurs - an SPC trend approaching a limit, a near-miss, or a gap found during a process review. Both follow the same lifecycle: identify, investigate, determine root cause, implement action, verify effectiveness, and close. The difference is the trigger, not the method. CAPA is not the same as correction: A correction fixes the immediate symptom - reworking a defective part, replacing a faulty sensor, re-training an operator. A corrective action eliminates the root cause so the defect cannot happen again. Most CAPA failures start here: organizations document the correction, label it a CAPA, and close it. Six months later the same problem returns because nobody addressed why it happened in the first place. **Why a structured CAPA process delivers lasting results** CAPA connects problem detection to problem elimination. Without it, organizations fix symptoms on repeat. With it, each issue makes the system stronger. - Problems are resolved permanently - A proper CAPA traces defects back to their root cause and verifies that the corrective action actually works. Organizations with mature CAPA systems report 50-70% fewer recurring nonconformances compared to those that rely on corrections alone. - Regulatory compliance is built in - ISO 9001 clause 10.2, IATF 16949 clause 10.2.3, FDA 21 CFR 820.90 - all require a documented CAPA process. A well-run CAPA system is not extra work for audits, it is the audit evidence. Inspectors check CAPA records first. - Quality costs decrease over time - Every recurring defect carries cost: scrap, rework, sorting, expedited shipping, complaint handling. CAPA breaks the cycle. The investment in root cause investigation pays back through reduced cost of poor quality (COPQ) within months. - Knowledge compounds across the organization - Each closed CAPA adds to an institutional knowledge base of what went wrong, why, and how it was fixed. New engineers, new plants, and new product launches benefit from lessons already learned. - Audit findings become improvement drivers - Without CAPA, audit findings generate paperwork. With CAPA, every finding triggers a structured investigation and a verified fix. Internal audits, supplier audits, and certification audits all feed into the same improvement engine. - Customer confidence grows - When a customer reports a defect and receives a CAPA with verified root cause, permanent corrective action, and effectiveness check, they see a supplier that takes quality seriously. In automotive and aerospace, CAPA response quality directly affects supplier scorecards. **The CAPA lifecycle step by step** The CAPA lifecycle begins with identification. A trigger event - a customer complaint, an internal audit nonconformance, a batch deviation, a trend in inspection data - is documented and evaluated for severity. Not every issue needs a full CAPA; minor corrections can be handled through standard deviation processes. But recurring issues, safety-relevant defects, and regulatory findings always require formal CAPA. Once initiated, the investigation phase determines the root cause using structured methods: 5 Whys, Ishikawa diagrams, fault tree analysis, or a full 8D report for complex problems. With the root cause confirmed, the team defines corrective actions (to eliminate the cause) and preventive actions (to prevent occurrence in similar processes or products). Each action gets an owner and a deadline. After implementation, the critical step most organizations skip: effectiveness verification. This means checking - with data - that the corrective action actually worked. Did the defect rate drop to zero? Did the audit finding close without recurrence? Only after verified effectiveness is the CAPA closed. CAPA records are retained as quality records per ISO 9001 clause 7.5 and reviewed in management review meetings. **Implementing CAPA in your organization** From the first documented corrective action to a fully integrated CAPA management system - here is how to build a process that auditors respect and engineers trust. - Define CAPA triggers and severity criteria - Not everything is a CAPA. Define clear criteria for when a full CAPA is required vs. a simple correction. Typical CAPA triggers: customer complaints, audit nonconformances (major and repeat minor), batch rejections above threshold, safety incidents, and regulatory observations. Use a severity matrix to prioritize. - Establish a structured investigation method - Require root cause analysis for every CAPA - not just "operator error" or "training needed." Standardize on proven methods: 5 Whys for straightforward issues, Ishikawa for multi-factor problems, 8D for customer-facing complaints. Train your quality team and key production staff in these methods. - Separate correction from corrective action - Document both the immediate fix (correction/containment) and the systemic fix (corrective action) as distinct steps. The correction stops the bleeding; the corrective action prevents it from happening again. Auditors specifically check that organizations understand this difference. - Assign ownership with deadlines - Every CAPA action needs a named owner (not a department) and a realistic deadline. Track overdue actions visibly. Escalate CAPAs that miss their deadlines - an overdue CAPA is a management system failure, not just a quality department problem. - Verify effectiveness with data - Define upfront how you will measure whether the corrective action worked. Set a verification date - typically 30 to 90 days after implementation. Check the specific metric: zero recurrence, SPC data within limits, no repeat audit findings. If effectiveness is not confirmed, reopen the CAPA and investigate further. - Review CAPA trends in management review - ISO 9001 clause 9.3 requires management review to cover nonconformities and corrective actions. Present CAPA metrics: open vs. closed, average time to close, overdue rate, recurring issues, top root cause categories. Use this data to allocate resources where quality problems concentrate. **Common CAPA pitfalls - and how to avoid them** A CAPA process on paper is easy. A CAPA process that actually eliminates problems requires discipline in these four areas. - Root cause analysis is superficial - "Human error" and "lack of training" are symptoms, not root causes. Require at least a 5 Whys analysis for every CAPA. Ask: why did the process allow this error? Why was the training gap not detected? Why was there no poka-yoke? Push past the first answer until you reach a systemic cause that can be prevented. - Corrective actions are just more inspection - Adding an inspection step does not eliminate a root cause - it adds cost and catches defects after they occur. Effective corrective actions change the process so the defect cannot be produced: tooling modifications, poka-yoke devices, process parameter changes, design updates. If your most common corrective action is 'add inspection,' your CAPA process needs work. - Effectiveness verification is skipped or faked - Many organizations close CAPAs after implementing the action without checking if it worked. Define the verification method and date when the CAPA is opened. Use objective data: defect rates, audit results, process capability indices. If you cannot measure effectiveness, the corrective action was not specific enough. - CAPAs pile up and become a backlog - When organizations open CAPAs faster than they close them, the system loses credibility. Set realistic timelines at initiation. Review overdue CAPAs weekly. Prioritize by severity and customer impact. Consider whether low-severity items truly need a full CAPA or can be handled through simpler correction processes. **CAPA Management: CAPA Digital with Mobile2b** Spreadsheet-based CAPA tracking loses visibility, misses deadlines, and fails audits. Mobile2b gives your CAPA process the structure and traceability auditors expect. - Structured CAPA workflow - Guided steps from initiation through root cause analysis, action definition, implementation, and effectiveness verification. Every CAPA follows the same lifecycle - no steps skipped, no shortcuts. - Root cause analysis integration - Built-in 5 Whys and Ishikawa templates linked directly to the CAPA record. The investigation and the corrective action live in one place, creating a complete audit trail from problem to solution. - Automated tracking and escalation - Deadline reminders, overdue alerts, and escalation workflows ensure no CAPA falls through the cracks. Dashboard views show open, overdue, and pending verification at a glance. - CAPA analytics and trend reporting - Analyze CAPA data by root cause category, source, product line, and department. Identify patterns that point to systemic issues. Feed CAPA metrics directly into management review reports. **Frequently Asked Questions About CAPA** - What is the difference between corrective action and preventive action? - A corrective action responds to a problem that has already occurred - it eliminates the root cause of an existing nonconformance. A preventive action addresses a potential problem before it happens - it eliminates the cause of a risk or negative trend. Both use root cause analysis; the difference is the trigger. ISO 9001:2015 merged preventive action into risk-based thinking (clause 6.1), but the concept remains essential in regulated industries like pharma and medical devices. - When should I open a CAPA vs. just documenting a correction? - Open a CAPA when the issue is recurring, safety-relevant, customer-impacting, or flagged by an auditor. Also open a CAPA when the root cause is not immediately obvious and requires investigation. Simple one-time deviations with clear causes can often be handled as corrections with a documented rationale. The key: if the same correction is needed twice, it should have been a CAPA the first time. - How does CAPA relate to 8D reports? - The 8D methodology is one way to execute the investigation and resolution phases of a CAPA. Steps D4 (root cause) and D5/D6 (corrective actions) map directly to CAPA requirements. In automotive, 8D is the preferred format for customer-facing CAPAs. You can think of 8D as a specific CAPA template used when a structured team-based investigation is needed. - What does ISO 9001 require for CAPA? - ISO 9001:2015 clause 10.2 requires organizations to react to nonconformities, evaluate the need for action to eliminate causes, implement corrective actions, review effectiveness, and update risks and opportunities if needed. Records must be retained. The standard no longer has a separate preventive action clause - this is now covered under risk-based thinking in clause 6.1. - How long should a CAPA take to close? - It depends on complexity. Simple CAPAs with clear root causes can close in 2-4 weeks. Complex CAPAs involving process redesign or tooling changes may take 3-6 months. Set a target closure time at initiation based on severity and complexity. Track average closure time as a KPI - if it exceeds 90 days consistently, investigate whether your process has bottlenecks or whether CAPAs are being opened for issues that do not warrant them. - How do I measure CAPA effectiveness? - Define the success criterion when you open the CAPA, not when you close it. Common measures: zero recurrence of the specific defect for 90 days, process capability index above target, no repeat audit finding in the next audit cycle, customer complaint rate below threshold. Check the data at the scheduled verification date. If the criterion is not met, the CAPA stays open and the corrective action is revised. ### Gemba Walk: Shop Floor Leadership URL (DE): https://www.mobile2b.com/knowledge-base/gemba-walk URL (EN): https://www.mobile2b.com/en/knowledge-base/gemba-walk Summary: Use structured Gemba Walks to connect leadership decisions with shop floor reality, following Toyota's lean management practice. **What is a Gemba Walk?** A Gemba Walk is a lean management practice where leaders go to the actual place where work happens - the shop floor, the warehouse, the construction site, the hospital ward - to observe processes, engage with employees, and understand reality firsthand. The word "Gemba" (sometimes written "Genba") comes from Japanese and means "the real place" or "the actual place." In the Toyota Production System, Gemba is the foundation of all improvement: you cannot improve what you have not seen with your own eyes. A Gemba Walk is not an audit, not an inspection, and not management by walking around. It is a structured observation practice with a specific purpose: to understand the gap between standard work and actual work, to identify waste and obstacles that employees face daily, and to build a culture where problems are surfaced rather than hidden. The leader goes to Gemba not to judge or give orders, but to learn. Taiichi Ohno, the architect of the Toyota Production System, reportedly drew a chalk circle on the factory floor and told engineers to stand in it and observe until they truly understood the process. Gemba Walk is not management by walking around: The most common misconception: treating a Gemba Walk like a casual stroll through the workplace. Management by walking around (MBWA) is informal and unstructured - you talk to people, show presence, and gather impressions. A Gemba Walk is purposeful: you go with a theme, you observe against a standard, you ask specific questions, and you follow up with actions. Without structure, a Gemba Walk degrades into a social visit that changes nothing. **Why Gemba Walks transform how leaders manage** When leaders regularly go to where value is created, they make better decisions, build stronger teams, and catch problems before they escalate. - See reality, not reports - Reports and dashboards show you what people chose to measure. Gemba shows you what actually happens - the workarounds, the waiting, the friction that never makes it into a KPI. Leaders who walk Gemba regularly make decisions based on firsthand observation, not filtered information. - Build trust with frontline teams - When leaders show up regularly, listen without judgment, and follow through on what they learn, frontline employees begin to trust that raising problems leads to solutions, not blame. This trust is the foundation of a continuous improvement culture. - Catch problems early - Small deviations from standard work are visible on the shop floor long before they show up in quality metrics or customer complaints. A Gemba Walk lets you see the early warning signs - a cluttered workstation, a missing visual control, a workaround that bypasses a safety step. - Develop people through coaching - Gemba is not just about finding problems - it is the best setting for coaching. When you observe work together with the person doing it, you can ask questions that develop their problem-solving ability rather than just giving them answers. - Align strategy with operations - Leaders who walk Gemba understand the operational constraints that make strategic goals realistic or unrealistic. This alignment prevents the disconnect where management sets targets that the shop floor knows are impossible with current processes. - Drive sustainable improvement - Improvement initiatives that start from Gemba observation tend to stick because they address real problems that employees experience daily. Top-down improvement programs often fail because they solve problems that look important on paper but do not match shop floor reality. **The Gemba Walk process step by step** Before you go, define your theme. A Gemba Walk without a focus becomes a tour. Choose one area to observe: safety, quality, flow, standard work adherence, 5S, or a specific problem that was reported. Review the relevant standards and metrics beforehand so you know what "good" looks like. Then go to the workplace, position yourself where you can see the full process, and observe for at least 15-20 minutes before engaging. Watch the sequence of work, the movement of materials, the interactions between people and machines. Note deviations from the standard - not to catch people doing something wrong, but to understand why the deviation exists. After observing, engage with the people doing the work. Ask open-ended questions: "Walk me through how you do this step." "What makes this task difficult?" "If you could change one thing about this process, what would it be?" Listen more than you talk. Do not solve problems on the spot - that signals that improvement depends on your presence. Instead, document what you observed, share your findings with the team, and agree on follow-up actions. The most important part of a Gemba Walk is what happens after: the actions you take based on what you learned. **Implementing Gemba Walks in your organization** From your first walk to a systematic leadership practice - here is how to make Gemba Walks part of your management routine. - Define your Gemba Walk schedule and routes - Set a regular cadence - daily for frontline supervisors, weekly for department managers, monthly for senior leaders. Define routes that cover all areas over time. Consistency matters more than frequency: a weekly walk that happens every week beats a daily walk that gets cancelled when things get busy. - Prepare a focused observation theme - Each walk should have a theme: safety, quality, flow, standard work, 5S, equipment condition. Prepare 3-5 specific questions related to the theme. Review relevant standards, procedures, and recent performance data before you go. Going without preparation wastes your time and the team's time. - Observe before you engage - Spend the first 15-20 minutes just watching. Stand at the process, not in an office looking through a window. Observe the sequence of operations, material flow, and worker movements. Note what you see without immediately interpreting or judging. The goal is to see reality, not to confirm your assumptions. - Ask questions, do not give answers - When you engage with employees, ask open questions: "What is the biggest obstacle you face in this task?" "Why do you do it this way instead of the standard?" "What would help you do this better?" Resist the urge to solve problems immediately. Your role is to understand, not to direct. - Document observations and agree on actions - Record what you observed, what you learned from conversations, and what actions will follow. Use a standardized checklist or digital form so observations are comparable over time. Every Gemba Walk should produce at least one follow-up action with a clear owner and deadline. - Follow up and close the loop - The fastest way to kill a Gemba Walk program is to observe problems and never act on them. Track every action to completion. Share results with the team. On your next walk, check whether previous actions were implemented and effective. This follow-through is what separates Gemba Walks from empty rituals. **Common Gemba Walk mistakes - and how to avoid them** The practice is simple in concept but easy to get wrong. These are the pitfalls that turn a powerful leadership tool into a waste of time. - The walk becomes an audit or inspection - When leaders use Gemba Walks to catch people making mistakes, employees hide problems instead of surfacing them. Make it clear that Gemba is about understanding processes, not judging people. If you find a deviation, ask "What makes it difficult to follow the standard?" not "Why are you not following the standard?" - No follow-up on observations - Walking Gemba and taking notes means nothing if actions do not follow. Employees quickly learn whether their leader's presence leads to improvement or is just a box-checking exercise. Track every observation to an action, assign owners, and verify completion on the next walk. - Leaders solve problems on the spot instead of coaching - Giving immediate solutions feels efficient but creates dependency. When leaders solve every problem personally, employees stop thinking for themselves. Instead, ask coaching questions: "What do you think is causing this?" "What have you already tried?" "What would you do if you could change anything?" Develop problem-solvers, not problem-reporters. - Walks happen only when there is a crisis - Gemba Walks that only happen after a quality escape or safety incident send the wrong message - leadership only shows up when something goes wrong. Maintain a regular schedule regardless of current performance. The value of Gemba is in prevention and continuous improvement, not in firefighting. **Gemba Walk: Gemba Walks digital with Mobile2b** Paper checklists and handwritten notes get lost in desk drawers. Mobile2b turns every Gemba Walk into a tracked, measurable, and actionable leadership practice. - Mobile Gemba Walk checklists - Conduct Gemba Walks directly on your smartphone or tablet. Customizable checklists for different themes - safety, quality, 5S, standard work. Capture photos and voice notes on the spot. - Structured observation forms - Standardized templates ensure every walk covers the right areas and asks the right questions. Consistent structure makes observations comparable across shifts, areas, and time periods. - Location-based tracking - Track which areas have been walked and which have not. Ensure coverage across all departments and shifts. Visualize walk frequency on floor plans and dashboards. - Trend analysis and reporting - Aggregate Gemba Walk findings across walks, areas, and time periods. Identify recurring themes and systemic issues. Measure whether actions taken actually improved the observed conditions. **Frequently Asked Questions About Gemba Walks** - What is the difference between a Gemba Walk and management by walking around? - Management by walking around (MBWA) is informal - you walk through the workplace, chat with people, and show presence. A Gemba Walk is structured: you go with a specific theme, observe against standards, ask purposeful questions, and document findings with follow-up actions. MBWA builds relationships; Gemba Walks drive systematic improvement. - How long should a Gemba Walk take? - A focused Gemba Walk typically takes 30-60 minutes including observation, conversation, and documentation. For frontline supervisors doing daily walks, 15-20 minutes may be sufficient. The key is consistency - a short, regular walk is more valuable than an occasional lengthy tour. - Who should conduct Gemba Walks? - Everyone in a leadership role should walk Gemba regularly, from team leaders to plant managers to executives. The frequency varies by level: frontline supervisors may walk daily, middle managers weekly, and senior leaders monthly. Each level observes different things - supervisors focus on standard work adherence, executives on strategic alignment. - What should I look for during a Gemba Walk? - Focus on your chosen theme, but always watch for: deviations from standard work, signs of waste (waiting, excess motion, overproduction), safety hazards, visual management effectiveness, cleanliness and organization (5S), and employee engagement. The most important observations are often what is NOT there - missing standards, absent visual controls, gaps in the process. - How do I introduce Gemba Walks without creating anxiety? - Start by explaining the purpose: you are there to learn, not to judge. Begin in areas where you have good relationships with the team. Focus your first walks on understanding processes, not finding problems. Follow up with positive actions that visibly help the team. Over time, employees will see Gemba Walks as an opportunity to get leadership attention for their challenges. - Can Gemba Walks work in non-manufacturing environments? - Absolutely. Gemba means "the real place" - wherever value is created for the customer. In healthcare, Gemba is the patient ward. In logistics, it is the warehouse floor. In software development, it is where developers write and test code. The principle is universal: go where the work happens, observe, ask questions, and improve based on what you learn. ### Kaizen: Continuous Improvement Guide URL (DE): https://www.mobile2b.com/knowledge-base/kaizen-continuous-improvement URL (EN): https://www.mobile2b.com/en/knowledge-base/kaizen-continuous-improvement Summary: Apply the Kaizen philosophy of small, daily improvements to build operational excellence in manufacturing and operations. **What is Kaizen?** Kaizen is a Japanese philosophy meaning "change for the better" - the practice of continuous improvement through small, incremental changes made by everyone in an organization, every day. Originating in post-war Japanese manufacturing and formalized within the Toyota Production System, Kaizen rejects the idea that improvement requires large, disruptive projects. Instead, it holds that hundreds of small improvements, compounded over time, produce results that no single initiative could achieve. Every employee, from the CEO to the shop floor operator, is expected to identify waste and suggest improvements. Kaizen is not a tool or a technique - it is a management philosophy and a way of thinking. While Western management traditions often focus on breakthrough innovation and large capital investments, Kaizen focuses on the daily discipline of making processes slightly better, slightly faster, and slightly less wasteful. The power lies in consistency: a team that implements one small improvement per day achieves 250 improvements per year. Multiply that across departments, and the cumulative effect transforms operations fundamentally. Kaizen is not a one-time event: The most common misunderstanding: treating Kaizen as a week-long workshop (a Kaizen event or blitz) and then returning to business as usual. While Kaizen events are a valid tool for focused improvement, true Kaizen is a daily practice. If improvement only happens during scheduled events, you have a project management system, not a Kaizen culture. The real measure of Kaizen maturity is whether shop floor workers suggest and implement improvements without being asked. **Why Kaizen delivers sustainable results** Organizations that embrace Kaizen do not just solve problems - they build a culture where problems are prevented and processes continuously evolve. - Compound improvement effect - Small daily improvements accumulate exponentially. Toyota's production system was not built in a single transformation - it evolved over decades of incremental changes. Organizations practicing daily Kaizen report 10-30% year-over-year productivity gains without major capital investment. - Employee engagement and ownership - When every worker is empowered to identify and fix problems, engagement rises dramatically. People take ownership of their processes because they shape them. Companies with mature Kaizen programs report 5-10x more improvement suggestions per employee than traditional suggestion box systems. - Low risk, high cumulative impact - Each individual change is small and reversible - no expensive consultants, no risky system overhauls. If an improvement does not work, you revert it tomorrow. But the sum of thousands of small wins creates operational advantages that competitors cannot replicate quickly. - Waste elimination becomes systematic - Kaizen trains everyone to see the seven wastes (muda): overproduction, waiting, transport, overprocessing, inventory, motion, and defects. Once people learn to see waste, they cannot unsee it. Waste reduction becomes a reflex, not a project. - Quality improves at the source - Instead of catching defects at final inspection, Kaizen pushes quality upstream. Workers who improve their own processes build quality into every step. This aligns with Toyota's principle of jidoka - building in quality rather than inspecting it in. - Cross-functional collaboration - Kaizen activities naturally break down silos. When a production team and a maintenance team jointly improve a changeover process, they develop shared understanding and mutual respect. This collaborative problem-solving culture is more valuable than any single improvement. **The PDCA cycle: Kaizen's engine** Every Kaizen improvement follows the PDCA cycle - Plan, Do, Check, Act - originally developed by Walter Shewhart and popularized by W. Edwards Deming. In the Plan phase, you identify a problem or opportunity, analyze the current state, and define what "better" looks like with measurable targets. In Do, you implement the change on a small scale - one workstation, one shift, one product line. This is not a pilot program requiring months of planning; it is a change made today and observed tomorrow. In Check, you measure the results against your target. Did cycle time decrease? Did defects go down? Did the operator find the new method easier? Data matters - gut feelings are not Kaizen. In Act, you standardize the improvement if it worked (update work instructions, train other shifts) or adjust and try again if it did not. The cycle then repeats. This is what makes Kaizen continuous: there is no final state, only the current state and the next improvement. Toyota calls this "true north" - the ideal state you approach but never fully reach. **Implementing Kaizen in your organization** From the first improvement idea to a self-sustaining Kaizen culture - here is how to make continuous improvement part of daily operations. - Start with a Gemba Walk - Go to where the work happens and observe. Talk to operators about what frustrates them, where they wait, what they work around. The best Kaizen opportunities come from the people who do the work every day. Do not start with spreadsheets - start with observation. - Train teams in waste recognition - Teach the seven wastes (muda) so everyone can identify improvement opportunities. Use real examples from your own shop floor, not textbook cases. When a team can point at their workstation and name three types of waste, training has succeeded. - Establish a simple suggestion system - Make it easy to submit improvement ideas - a digital form, a physical board, whatever removes friction. The key: respond to every suggestion within 48 hours and implement quick wins immediately. Nothing kills a Kaizen culture faster than ignored suggestions. - Run focused Kaizen events for larger problems - For improvements that need cross-functional effort, run 3-5 day Kaizen events (blitzes). Pick a specific problem, assemble a team, and commit to implementing changes during the event - not after. The discipline of same-week implementation separates Kaizen events from regular meetings. - Standardize before improving further - Every successful improvement must become the new standard. Update work instructions, visual standards, and training materials. Without standardization, improvements drift back to the old way. Standardize, then improve the standard - this is the Kaizen cycle. - Measure and share results visibly - Track the number of improvements implemented, not just suggested. Display results on team boards: before and after photos, time savings, cost reductions. When teams see the impact of their ideas, motivation becomes self-sustaining. Celebrate small wins consistently. **Common Kaizen challenges - and how to overcome them** Building a Kaizen culture is simple in concept but demands sustained leadership commitment. These are the obstacles that derail most programs. - Management treats Kaizen as a cost-cutting tool - When Kaizen is used solely to reduce headcount or cut budgets, employees stop participating. Kaizen must improve processes, not eliminate jobs. Reinvest gains into quality, capacity, or working conditions. Make the commitment explicit: improvements benefit everyone, not just the bottom line. - Improvements are suggested but never implemented - The fastest way to kill Kaizen culture is ignoring suggestions. Set a rule: every idea gets a response within 48 hours. Small improvements should be implemented within a week. If an idea cannot be implemented, explain why honestly. Track implementation rate as a leadership KPI. - Only Kaizen events happen, not daily Kaizen - Kaizen events are valuable but insufficient. If improvement only happens during scheduled workshops, you have event-driven problem-solving, not continuous improvement. Build daily habits: start-of-shift improvement discussions, visual management boards updated daily, weekly team reviews of implemented changes. - Improvements are not standardized and drift back - Without updated standards, improvements evaporate within weeks. Every change must update the relevant work instruction, visual standard, or checklist. Train all shifts on the new standard. Audit adherence regularly. The Kaizen cycle is improve-standardize-improve, never just improve. **Kaizen Methodology: Kaizen Digital with Mobile2b** Paper suggestion boxes and spreadsheet trackers cannot sustain a Kaizen culture at scale. Mobile2b makes every improvement visible, trackable, and measurable. - Digital improvement suggestion system - Capture Kaizen ideas from any device - with photos, location tags, and category classification. Automatic routing ensures the right team sees each suggestion immediately. No more lost sticky notes. - PDCA cycle tracking - Every improvement follows a structured Plan-Do-Check-Act workflow with deadlines, owners, and measurable targets. Track each idea from suggestion through implementation to verified results. - Kaizen event management - Plan and execute Kaizen blitzes with built-in templates: team assignment, problem scoping, action tracking, and before-after documentation. Keep the momentum from event to daily practice. - Improvement analytics and reporting - Visualize improvement trends across teams, departments, and time periods. Track implementation rates, time-to-action, and cumulative impact. Data-driven insights show where Kaizen culture is thriving and where it needs support. **Frequently Asked Questions About Kaizen** - What is the difference between Kaizen and Lean? - Lean is the overall management system focused on eliminating waste and creating value flow. Kaizen is the improvement philosophy that drives Lean forward. You cannot have Lean without Kaizen - Lean provides the framework (value streams, pull systems, flow), while Kaizen provides the engine of continuous improvement that makes Lean a living system rather than a static set of tools. - How does Kaizen relate to the 5 Whys, 5S, and Gemba Walks? - These are all complementary tools within the Kaizen ecosystem. Gemba Walks help leaders observe reality and identify improvement opportunities. 5S creates the workplace organization foundation that makes problems visible. The 5 Whys provides root cause analysis when problems are found. Together with Kaizen's PDCA cycle, they form a complete improvement system. - What is a Kaizen event (blitz) and when should I use one? - A Kaizen event is a focused 3-5 day workshop where a cross-functional team tackles a specific problem and implements solutions during the event itself. Use Kaizen events for problems that cross departmental boundaries, require dedicated time to solve, or need team consensus. But remember: events supplement daily Kaizen, they do not replace it. - How do I measure Kaizen effectiveness? - Track both activity and outcomes. Activity metrics: number of suggestions submitted, implementation rate, average time from idea to implementation. Outcome metrics: productivity gains, defect reduction, lead time improvement, cost savings. The most telling metric is suggestions per employee per month - world-class Kaizen organizations achieve 2-5 implemented improvements per employee per month. - Can Kaizen work outside of manufacturing? - Absolutely. Kaizen principles apply wherever processes exist: healthcare (reducing patient wait times), logistics (optimizing routes), software development (reducing deployment cycle time), office work (eliminating unnecessary approvals). The philosophy of small, daily, everyone-involved improvement is universal. - How long does it take to build a Kaizen culture? - Expect 6-12 months to see early results from a structured program, and 2-3 years to develop a self-sustaining culture where improvement happens without management prompting. The key accelerator is visible leadership commitment: when managers practice Kaizen themselves and respond to every suggestion, cultural change happens faster. ### Pareto Analysis: Focus on the Causes That Actually Matter URL (DE): https://www.mobile2b.com/knowledge-base/pareto-analysis URL (EN): https://www.mobile2b.com/en/knowledge-base/pareto-analysis Summary: Most quality problems come from a small number of root causes. Pareto Analysis helps you find them, so your team works on what moves the needle instead of chasing every issue equally. **What is Pareto Analysis?** Pareto Analysis is a decision-making technique based on the Pareto Principle, also known as the 80/20 rule. The idea: roughly 80% of effects come from 20% of causes. In quality management, this means a small number of defect types typically account for the majority of your quality costs, customer complaints, or production downtime. By identifying and ranking these causes, you direct your improvement efforts where they will have the greatest impact. The method was named after Italian economist Vilfredo Pareto, who observed in 1896 that 80% of land in Italy was owned by 20% of the population. Quality pioneer Joseph Juran later applied this concept to defect analysis in manufacturing, calling it the distinction between the "vital few" and the "trivial many." Today, Pareto Analysis is a standard tool in Six Sigma, lean manufacturing, and continuous improvement programs across every industry. Prioritization, not elimination: Pareto Analysis does not tell you to ignore the smaller causes. It tells you where to start. By solving the top contributors first, you get the biggest improvement with the least effort. The remaining issues become the focus of your next cycle. **Why the 80/20 rule works for quality teams** Quality managers face dozens of open issues at any given time. Pareto Analysis cuts through the noise and shows you which problems deserve your attention right now. - Resources go where they matter most - Every team has limited time and budget. Pareto Analysis prevents the common trap of spreading effort evenly across all problems. Instead, you concentrate resources on the 2-3 causes responsible for most of your defects, complaints, or downtime. - Data replaces gut feeling - Without data, the loudest complaint or the most recent incident tends to drive priorities. A Pareto chart makes the actual distribution visible: which causes are truly dominant and which only feel urgent because they happened yesterday. - Improvement becomes measurable - When you track Pareto charts over time, you can see whether your corrective actions actually reduced the top causes. A before-and-after comparison is one of the clearest ways to demonstrate improvement to management or auditors. - Teams align on priorities - A Pareto chart is easy to read. When you present it in a team meeting, everyone can see why you are focusing on cause A instead of cause D. This shared understanding reduces debates about priorities and speeds up decision-making. - Reduces quality costs faster - Because you are tackling the biggest contributors first, cost of poor quality (COPQ) drops faster than with a scattergun approach. Organizations using Pareto-guided improvement cycles typically see 40-60% reduction in their top defect categories within one quarter. - Works at every scale - Pareto Analysis applies equally to a single production line analyzing scrap reasons and to a multi-site organization prioritizing which factory to audit first. The principle scales because the math behind it is universal. **How to create a Pareto chart** A Pareto chart combines a bar chart and a cumulative line graph. The bars represent individual causes sorted by frequency or cost (highest to lowest, left to right). The line shows the cumulative percentage. Where the line crosses the 80% threshold, you have identified your "vital few" causes. The chart itself is simple to build. The harder part is collecting clean data. If your categories are too broad ("operator error"), the chart will not point you to a specific action. If they are too narrow ("operator pressed button 3 instead of button 4 on machine 7B"), you end up with dozens of tiny bars and no clear pattern. Aim for 5-10 categories that are specific enough to act on but broad enough to accumulate meaningful counts. **Step-by-step Pareto Analysis process** Follow these six steps to run a Pareto Analysis that produces actionable results, not just a chart for a slide deck. - Define the problem category and time window - Decide what you are analyzing: defect types, customer complaint categories, equipment failure modes, audit non-conformances, or something else. Set a clear time window (last 30 days, last quarter). The narrower and more specific your scope, the more actionable the results. - Collect and categorize the data - Pull data from your quality management system, inspection logs, or production records. Assign each occurrence to a category. If you find items that do not fit any category, create an "Other" bucket, but keep it under 10% of the total. If "Other" is your biggest bar, your categories need rework. - Count occurrences and calculate percentages - Tally each category. Sort from highest to lowest. Calculate what percentage each category represents of the total. Then calculate the cumulative percentage: the first category alone, then the first two combined, then the first three, and so on. - Draw the Pareto chart - Plot bars in descending order (left to right). Add a second y-axis for the cumulative percentage line. Draw a horizontal line at 80%. The categories to the left of where the cumulative line crosses 80% are your vital few. These are the causes that deserve immediate attention. - Investigate the top causes with RCA - A Pareto chart tells you what to focus on, not why it happens. For each of the top 2-3 causes, run a root cause analysis using methods like 5 Whys, Ishikawa diagrams, or 8D reports. The Pareto chart narrows the field; the RCA tools dig into the specifics. - Implement, measure, and repeat - Apply corrective actions to the top causes. After one cycle (typically 30-90 days), run a new Pareto Analysis on the same data source. The old top causes should have shrunk. New causes may have risen to the top. This is normal and expected. Each cycle moves you closer to operational excellence. **Common challenges and how to solve them** Pareto Analysis is conceptually simple, but teams run into predictable problems when applying it in practice. - If operators log defects differently (one writes "scratch", another writes "surface damage", a third writes "cosmetic"), your categories will be fragmented and the chart misleading. Standardize defect codes with a dropdown list, not free text. Digital checklists with predefined categories solve this at the source. - If your chart shows 15 bars of roughly equal height, the 80/20 pattern is weak. This usually means your categories are too granular or the problem is genuinely distributed. Try grouping related causes (e.g., combine all assembly errors into one category) or analyze a different dimension (cost impact instead of frequency). - When "Other" or "Miscellaneous" is the tallest bar, your categorization system is broken. Review the items in "Other", identify patterns, and create proper categories for the recurring ones. A useful rule: no single item should be forced into "Other" more than twice before it gets its own category. - This happens when the corrective action addresses the symptom but not the root cause, or when fixing one cause shifts volume to another. Always pair Pareto Analysis with proper root cause analysis (5 Whys, Ishikawa). And always rerun the Pareto chart after implementing changes to verify the actual impact. **Frequently asked questions about Pareto Analysis** Practical answers to the questions quality and operations teams ask most often. - Does the 80/20 split have to be exact? - No. The 80/20 ratio is a guideline, not a mathematical law. In practice, you might find that 70% of defects come from 30% of causes, or 90% from 10%. The exact ratio does not matter. What matters is that the distribution is uneven, and focusing on the top causes gives you disproportionate improvement. - Should I analyze by frequency or by cost? - It depends on your goal. Frequency-based Pareto charts show which problems happen most often. Cost-based charts show which problems cost you the most. A defect that happens rarely but causes expensive rework or a product recall may not appear at the top of a frequency chart but will dominate a cost chart. For quality cost reduction, use cost. For process stability, use frequency. - How often should I update a Pareto chart? - After every improvement cycle, typically every 30-90 days. If you update too frequently (daily), the data is noisy and you chase random variation. If you wait too long (yearly), you miss the chance to redirect efforts when a new cause emerges. Monthly is a good default for most manufacturing and quality teams. - Can Pareto Analysis be used outside of quality management? - Yes. The principle applies anywhere effects are unevenly distributed across causes. Sales teams use it to identify which customers generate most revenue. IT teams use it to find which error types cause most support tickets. Maintenance teams use it to identify which equipment fails most often. The method is domain-agnostic. - How does Pareto Analysis relate to other quality tools? - Pareto Analysis is a prioritization tool. It tells you where to focus. Other tools tell you why (5 Whys, Ishikawa diagram) or how to prevent recurrence (CAPA, Poka Yoke). In practice, a typical improvement cycle starts with a Pareto chart to identify the biggest problem, then uses root cause analysis to understand it, and finally applies corrective and preventive actions. - What is the difference between a Pareto chart and a regular bar chart? - A Pareto chart adds two things to a standard bar chart: (1) the bars are sorted from largest to smallest, and (2) a cumulative percentage line is overlaid. The sorting makes the dominant causes immediately visible. The cumulative line shows how many causes account for a given percentage of the total, making the 80/20 threshold easy to read. **Mobile2b: Digital Pareto Analysis with Mobile2b** Mobile2b turns your inspection and audit data into live Pareto charts without manual data collection or spreadsheet work. - Automatic defect categorization - Digital checklists and inspection forms capture defect data with standardized categories from the start. No more deciphering handwritten notes or reconciling different naming conventions across shifts. - Live Pareto dashboards - See your top defect causes, non-conformance categories, or complaint types in real-time Pareto charts. Filter by time period, production line, shift, or location. Compare before and after to measure the impact of your corrective actions. - Integrated root cause analysis workflows - When you identify a top cause in the Pareto chart, launch a structured RCA workflow (5 Whys, Ishikawa, 8D) directly from the data point. The connection between "what to fix" and "how to fix it" stays in one system. - Trend tracking across improvement cycles - Track how your Pareto distribution changes over successive improvement cycles. See which causes you have successfully reduced and which new causes have emerged. Historical comparison makes continuous improvement visible and auditable. ### Poka Yoke: Mistake-Proofing That Prevents Defects Before They Happen URL (DE): https://www.mobile2b.com/knowledge-base/poka-yoke-mistake-proofing URL (EN): https://www.mobile2b.com/en/knowledge-base/poka-yoke-mistake-proofing Summary: A practical guide to designing processes that make errors physically impossible, so your team catches problems at the source instead of in quality control. **What is Poka Yoke?** Poka Yoke is a Japanese term meaning "mistake-proofing" or "error prevention." Coined by Shigeo Shingo, an industrial engineer at Toyota, it describes any mechanism in a manufacturing or business process that helps prevent human errors from turning into defects. The idea is simple: instead of relying on people to be careful, design the process so that mistakes either cannot happen or are immediately detected when they do. Think of everyday examples. A USB plug only fits one way. A car with automatic transmission will not start unless the gear is in Park. A microwave stops when you open the door. These are all Poka Yoke devices. In manufacturing and operations, the same principle applies: if an assembly step can be done wrong, redesign the fixture so it only accepts the correct orientation. If an operator might skip a step, add a sensor that halts the process until that step is confirmed complete. Prevention, not detection: Traditional quality control catches defects after they occur. Poka Yoke prevents them at the source. That distinction changes everything: you stop paying for rework, scrap, and customer complaints caused by errors that should never have left the workstation. **Why mistake-proofing works** Poka Yoke works because it removes the dependency on human attention and memory. Here is what changes when you build error prevention into your processes. - Defects drop to near zero - When the process physically prevents the error, defect rates fall dramatically. Toyota and its suppliers routinely achieve single-digit PPM (parts per million) defect rates. The savings on rework, scrap, and warranty claims compound quickly. - New operators become productive faster - Complex processes with many possible errors require extensive training and experience. Poka Yoke devices act as built-in guides: they make the correct action the only possible action. New team members can work confidently from day one without months of supervised practice. - Inspection costs decrease - If the process itself ensures correctness, you need fewer downstream inspection stations, fewer quality controllers, and less time spent sorting good parts from bad. Your quality team can focus on systemic improvement instead of catching individual mistakes. - Reduced training time for new operators - When the process itself prevents errors, new employees reach full productivity faster. The mistake-proofing device teaches the correct method through use, not classroom instruction. - Lower inspection costs - When defects cannot be produced, end-of-line inspection becomes verification rather than detection. Sampling rates drop, inspection stations consolidate, and quality assurance shifts upstream where it belongs. - Measurable quality improvement - Every Poka Yoke device targets a specific defect mode. The before-and-after data is unambiguous: either the defect still occurs or it does not. This clarity makes Poka Yoke one of the easiest quality tools to justify with hard numbers. **Types of Poka Yoke devices** Shigeo Shingo classified Poka Yoke into three categories based on how they interact with the process. Understanding these types helps you pick the right approach for each error you want to eliminate. - Contact method - Uses physical shape, size, or other attributes to prevent incorrect assembly or positioning. Examples: asymmetric connectors that only fit one way, guide pins on a fixture that reject wrongly oriented parts, color-coded cables that must match color-coded ports. These are the strongest Poka Yoke devices because they make the error physically impossible. - Fixed-value method - Ensures that the correct number of actions or parts are used. Examples: a parts tray with exactly the right number of compartments (if a compartment is still full after assembly, a part was missed), a torque wrench that clicks at the target value, a counter that tracks how many screws have been inserted. These catch omissions and over-applications. - Motion-step method - Verifies that the correct sequence of operations is followed. Examples: a system that locks the next tool in the sequence until the current step is confirmed complete, software that disables the Submit button until all required fields are filled, an interlock that prevents a machine from starting until the safety guard is closed. These address process discipline errors. **Step-by-step implementation** Implementing Poka Yoke is a targeted activity. You do not mistake-proof everything at once. You start where the most painful errors occur and work outward. - Identify the error hotspots - Analyze the root cause of each error - Design the Poka Yoke device or mechanism - Prototype and test with the team - Implement and train - Monitor and expand **Common challenges and how to solve them** Mistake-proofing is conceptually simple, but real-world implementation has its friction points. - This means the device adds too much friction to the normal workflow. Redesign it to be faster and less intrusive. The best Poka Yoke devices are invisible when the process is correct and only intervene when something goes wrong. Test with the operators before finalizing. - Quantify the current cost of the errors: rework hours, scrap material, warranty returns, customer penalties, and the labor hours spent on inspection. Compare that to the one-time cost of the Poka Yoke device. The payback period is usually weeks, not months. - Prioritize using a Pareto analysis. The top 20% of error types typically cause 80% of defect costs. Start there. One well-implemented Poka Yoke device that eliminates a frequent error is worth more than ten half-finished devices spread across the factory. - You cannot mistake-proof what you do not measure. Start with basic defect tracking: what error, where, when, and which product. Digital checklists and inspection forms give you this data automatically and help you spot patterns that manual logs miss. **Mobile2b: Poka Yoke digital with Mobile2b** Physical mistake-proofing handles hardware. Mobile2b handles the process layer: checklists, inspections, and workflows that guide your team through the right steps every time. - Mandatory step completion - Digital checklists enforce sequence: operators cannot proceed to step 3 until steps 1 and 2 are confirmed complete. Photo evidence, measurements, and signatures are required before moving forward. Skipping steps becomes impossible. - Real-time validation and alerts - When an operator enters a measurement outside tolerance, Mobile2b flags it immediately. Automatic escalation rules notify the shift lead or quality manager before the defective part moves to the next station. - Guided workflows with decision logic - Conditional branching in your workflows acts as a digital motion-step Poka Yoke. If the inspector finds a crack, the workflow automatically routes to the correct corrective action path. No manual decision, no missed follow-up. ## Free tools (no signup, browser only) ### Free tools for quality and root cause analysis URL (DE): https://www.mobile2b.com/tools URL (EN): https://www.mobile2b.com/en/tools Summary: Practical, no-signup tools you can use in the browser, share with your team, and export as a PDF. Built from the same methods we digitize for manufacturers every day. ### 5 Whys Analysis Tool URL (DE): https://www.mobile2b.com/tools/5-why-analysis URL (EN): https://www.mobile2b.com/en/tools/5-why-analysis Summary: Ask why five times to move past symptoms and reach the real cause of a problem. Fill in the chain below, then share it as a link or export it as a PDF. No signup, no data leaves your browser. **What is the 5 Whys method?** For the wider background on when to use this method and how it sits alongside the others, read our full guide to the **A worked example from a production line** Here is a complete chain for a common class of problem. Every answer is something you could verify with a record, a measurement, or a look at the machine. That is the difference between an analysis and a guess. Stopping after the second why would have produced "replace the tool". The line would have stopped again. - Why did the line stop? - The torque tool at station 7 shut down mid-cycle and locked the station. - Why did the torque tool shut down? - Its internal temperature went past the cut-off limit. - Why did it overheat? - The cooling air line to the tool was carrying about half its normal flow. - Why was the air line throttled? - A filter in the supply line was clogged and had never been changed. - Why was the filter never changed? - The filter is on no maintenance plan. It arrived with a line modification in 2024 and was never added to the schedule. **Five ways a 5 Whys goes wrong** Failed analyses fail in the same handful of ways. Check your chain against these before you act on it. - The chain ends at a person - If the last answer names someone rather than a system, keep going. Ask why the system allowed it, and what would have caught the mistake. - The answers are assumptions - Every answer needs evidence: a log entry, a measurement, a photo, a witness. Mark any step you cannot verify, then go and check it. - The problem statement is vague - "Quality issues in packaging" has no single cause. "Twelve cartons on line 3 were sealed off-centre on 4 March" does. - One branch when there are several - Some problems have two or three contributing causes. Run a separate chain for each, or spread the possibilities out in an Ishikawa diagram first and take the strongest branch into a 5 Whys. - Stopping at five out of habit - Five is a rule of thumb. Stop when you reach a cause you can remove and whose removal prevents recurrence. Sometimes that is three steps, sometimes seven. **Questions about the 5 Whys** - Why five whys and not three or ten? - Five is an average, not a target. Taiichi Ohno at Toyota used the number as a reminder not to stop at the first plausible answer. Stop when removing the cause would keep the problem from coming back. - When should I not use the 5 Whys? - When a problem has several independent causes, or when you need statistical proof of a relationship. Spread the possible causes out in an Ishikawa diagram first, and use a designed experiment or data analysis when you have to prove which cause dominates. - How does the 5 Whys fit into an 8D report? - It is normally step D4, the root cause analysis. The 8D wraps containment, corrective action, verification and prevention around it. If a customer asked you for an 8D, the 5 Whys chain sits in the middle of it. - Who should be in the room? - The people who do the work and saw the problem, plus someone who can approve a change to the process. Three to five people is usually enough. A chain built without the operator rarely survives contact with the shop floor. - How do I document the result? - Keep the whole chain, not just the root cause. The chain is the reasoning, and the next person needs it to judge whether the conclusion still holds. Copy it into your ticket, or use the export and link buttons above. - Is this tool really free, and where does my data go? - It is free and needs no account. Everything you type stays in your browser. The shareable link encodes the analysis in the URL itself, so nothing is stored on our servers. ### Fishbone Diagram Tool URL (DE): https://www.mobile2b.com/tools/ishikawa-diagram URL (EN): https://www.mobile2b.com/en/tools/ishikawa-diagram Summary: Gather the possible causes of a problem across the 6M categories and watch the Ishikawa diagram build as you type. Share it as a link or export it as a PDF. No signup, your data stays in the browser. **What is a fishbone diagram?** For the 6M categories in detail, common mistakes and worked examples, see the guide to the ### 8D Report Generator URL (DE): https://www.mobile2b.com/tools/8d-report-generator URL (EN): https://www.mobile2b.com/en/tools/8d-report-generator Summary: Work through the eight disciplines in order and get a finished report you can share or export as a PDF. No signup, your data stays in the browser. Not sure of the cause yet? Use the **What is an 8D report?** For the eight disciplines in detail, common mistakes, and a worked example, read the guide to the ## Customer success stories ### How Magna Powertrain saves 2,500 hours per year URL (DE): https://www.mobile2b.com/success-stories/magna URL (EN): https://www.mobile2b.com/en/success-stories/magna Facts: Industry: Automotive | Savings: 2,500 h / year | Use Case: Audit digitization Challenge: Magna Powertrain conducted all audits manually - with paper forms, Excel spreadsheets, and email chains. With hundreds of audits per year, an enormous amount of time went into planning, execution, documentation, and follow-up on actions. The lack of transparency made it difficult to identify trends and maintain consistent audit quality. Solution: Magna migrated the entire audit process to the Mobile2b platform. From automatic audit scheduling to mobile execution on tablets to real-time evaluation and action tracking - every step is now digital, traceable, and analyzable. ### Digital maintenance efficiency at Kronos Titan URL (DE): https://www.mobile2b.com/success-stories/kronos-titan URL (EN): https://www.mobile2b.com/en/success-stories/kronos-titan Facts: Industry: Chemicals / Titanium Dioxide | Savings: 4,000 sheets of paper / year | Use Case: Digital maintenance Challenge: Kronos Titan, one of the world's largest titanium dioxide manufacturers with approximately 10% market share and 7 plants, documented daily maintenance plans on paper - 4,000 sheets per year for maintenance documentation alone. No automation, no real-time visibility. Solution: Kronos Titan fully migrated its maintenance processes to Mobile2b. Work orders are created, assigned, and documented digitally. Technicians work mobile with tablets and have all relevant information - instructions, histories, and checklists - directly at the point of use. ### Digital warehouse management at Kogel Trailer URL (DE): https://www.mobile2b.com/success-stories/kogel URL (EN): https://www.mobile2b.com/en/success-stories/kogel Facts: Industry: Automotive / Logistics | Area: Logistics | Use Case: Digital Kanban Challenge: Kogel, founded in 1934 with over 550,000 vehicles produced, couldn't locate trailers on their own grounds. Internal logistics ran on paper and phone - Kanban cards, manual inventory lists, and verbal coordination. Solution: Kogel deployed a digital Kanban system with GPS tracking, barcode scanning, and auto-triggered production steps. The system was later expanded to visitor registration and 5S audits. ### Digital UVV inspections at EBG Endler URL (DE): https://www.mobile2b.com/success-stories/ebg-endler URL (EN): https://www.mobile2b.com/en/success-stories/ebg-endler Facts: Industry: Construction | Area: Workplace Safety | Use Case: UVV App Challenge: EBG Endler, specializing in underground construction in Dusseldorf, conducted all UVV inspections (accident prevention regulations) for their vehicle fleet and heavy machinery manually. The compliance and insurance risk was significant - missing or incomplete inspection records could become problematic in case of damage. Solution: With the Mobile2b UVV app, technicians identify equipment via NFC or barcode, conduct digital inspections with electronic signatures, and store everything in the cloud. Deficiencies are immediately escalated as actions. ### Digital antenna maintenance at Reiter Antennenbau URL (DE): https://www.mobile2b.com/success-stories/reiter URL (EN): https://www.mobile2b.com/en/success-stories/reiter Facts: Industry: Energy / Telecoms | Savings: 1 workday / week per technician | Use Case: Digital Maintenance Challenge: Reiter Antennenbau maintains antenna sites across Bavaria. Technicians spent one full workday per week on paper admin after fieldwork - writing reports, filling forms, delivering results to the office. This was an enormous productivity loss. Solution: In just one month, an iPhone-based service app was deployed with Mobile2b. The app works offline, supports photo documentation and speech-to-text. Technicians capture all maintenance results directly on-site - data is immediately available at the office. ### Digitalization at Kunze GmbH URL (DE): https://www.mobile2b.com/success-stories/kunze URL (EN): https://www.mobile2b.com/en/success-stories/kunze Facts: Industry: Manufacturing | Savings: ~50% ordering time | Use Case: Process digitization Challenge: Kunze GmbH, aerial work platform rental and sales near Rosenheim, grew from 10 to over 20 employees - and paper processes broke down. Manual rental workflows, work orders on the bulletin board, no system integration. Solution: In just a few days, workflows were digitized and connected to the MIRA ERP system via a cloud adapter. Digital invoice approval, booking processes, and spare parts ordering now run automated. ### Quality control in hospitality with Q4me URL (DE): https://www.mobile2b.com/success-stories/dehoga URL (EN): https://www.mobile2b.com/en/success-stories/dehoga Facts: Industry: Hospitality | Partner: DEHOGA Nordrhein | Use Case: HACCP / Quality Control Challenge: Hotels and restaurants face the challenge of maintaining extensive HACCP documentation, temperature controls, and hygiene checklists in a verifiable manner. Paper-based documentation is error-prone, time-consuming, and difficult to present during regulatory inspections. Solution: Q4me is a mobile quality management system developed jointly by DEHOGA Nordrhein and Mobile2b. It digitizes HACCP documentation, temperature logs, cleaning schedules, and hygiene audits - all on one platform, optimized for daily hospitality operations. ## Notes for machine readers Every page above exists in German (path as shown) and English (same path with an /en prefix). German is the default language, not a translation of the English. The short version of this file is at https://www.mobile2b.com/llms.txt. Legacy URLs under /ai-employees/, /forms/ and /checklist-templates/ were removed in March 2026. They return 410 Gone and are disallowed in robots.txt. Content still indexed under those paths is stale and does not describe this company. Contact: info@mobile2b.com. Demo booking: https://www.mobile2b.com/book-demo.