Ready to revolutionize your data journey with Infoveave?

Recent Blogs

    ·3 min read

    First Time Through (FTT) in Manufacturing: Formula, PPM, and Action Playbook

    If your output looks healthy but rework keeps rising, your line is not actually in control. First Time Through (FTT) is the quality signal that tells you how much production is right the first time.
    Many teams track FTT monthly. High-performing plants run FTT as a shift-level operating metric with clear thresholds, reason-code governance, and action ownership.

    FTT definition and formulas

    Use one definition across plant, line, and management dashboards.
    • FTT % = (First-time good quantity / Produced quantity) x 100
    • FTT PPM = (First-time defect quantity / Produced quantity) x 1,000,000
    Supporting quantity definitions:
    • Produced quantity = Good + Rework + Rejection
    • First-time good quantity = Units passing all required checks without rework
    • First-time defect quantity = Units failing first-pass checks before any recovery
    Formula hygiene rules:
    • Keep denominator logic identical across lines and models.
    • Do not merge first-time defects into rework-recovered totals for FTT.
    • If produced quantity is zero, return null and flag a data quality exception.
    For KPI consistency with OEE and plan tracking, reference Top 10 KPIs for manufacturers to track.

    Defect taxonomy that makes FTT actionable

    FTT improves only when defects are structured, not free-text chaos.
    Minimum taxonomy:
    • Defect family (for example: dimensional, cosmetic, assembly, electrical)
    • Defect reason code under each family
    • Defect remark template (station, symptom, suspected cause)
    • Optional severity tag (critical, major, minor)
    Governance standards:
    • Add new reason codes through controlled master updates.
    • Keep names stable to protect trend integrity.
    • Require remarks for repeat or high-impact defect reasons.
    If your capture layer is inconsistent, strengthen it with last-mile data collection patterns.

    Data model required for shift-level FTT control

    Your dashboard is only as reliable as your data model.
    Core fact layers:
    • Production fact: date, shift, line, model, good qty, rework qty, reject qty
    • Defect fact: date, shift, line, model, family, reason code, defect qty, remark
    • Plan fact: shift target and cumulative target
    Core master layers:
    • Line master
    • Shift master
    • Model master
    • Defect family and reason-code masters
    Join discipline:
    • Use date + shift + line + model as the minimum operational key.
    • Enforce the same key usage in all quality and output widgets.
    This is also the foundation needed for scalable OEE tracking software implementations.

    How to read FTT in a line dashboard

    FTT should never be viewed alone. Pair it with output and defect concentration.
    Recommended widget stack:
    • KPI cards: FTT %, FTT PPM, reject qty, rework qty
    • Pivot: line vs shift vs model for defect concentration
    • Query widget: top reason codes by quantity and recurrence
    • Plan panel: output variance with quality variance
    Directional operating bands (tune by product family):
    • FTT < 92%: immediate containment
    • FTT 92% to 97%: moderate instability, focused corrective action
    • FTT > 97%: controlled first-pass quality in many discrete settings
    • FTT PPM > 20,000: root-cause escalation within shift cycle
    • FTT PPM 5,000 to 20,000: recurring-defect action plan required
    • FTT PPM < 5,000: healthy operating range for many lines
    For board architecture patterns, read OEE visualization blueprint.

    Shift-level escalation loop for quality teams

    FTT improves when ownership is explicit and time-bound.
    Use this five-step loop:
    1. Shift handoff reviews prior FTT %, FTT PPM, and unresolved reasons.
    2. Supervisor triggers containment when thresholds are breached.
    3. Top defect family is assigned to quality, process, or maintenance owner.
    4. Corrective action and due time are logged.
    5. Next shift validates recurrence reduction before closure.
    Routing model:
    • Maintenance route: machine wear, calibration drift, equipment instability
    • Process route: setup sequence, instruction variance, method gaps
    • Quality route: incoming material variation, inspection escape patterns
    This keeps FTT from becoming a passive report metric.

    FTT and OEE should be reviewed together

    OEE can look stable while first-pass quality quietly deteriorates. Use a weekly combined review:
    1. Track OEE trend by line.
    2. Overlay FTT and FTT PPM trend.
    3. Identify lines with stable OEE but declining FTT.
    4. Prioritize defect-family action before speed optimization.
    For root-cause prioritization structure, use the OEE loss tree framework.

    Quick implementation roadmap

    First 30 days
    • Standardize FTT formula and denominator logic
    • Freeze defect taxonomy and reason-code masters
    • Baseline shift-level FTT dashboard
    Days 31 to 60
    • Enable threshold alerts for FTT and FTT PPM
    • Run daily recurring-defect review cadence
    • Start closure tracking by owner
    Days 61 to 90
    • Add predictive checks for recurring defect patterns
    • Connect FTT trend to plan-attainment and labor reviews
    • Recalibrate thresholds by product family

    Frequently Asked Questions

    Q: What is First Time Through (FTT) in manufacturing?
    First Time Through (FTT) is the percentage of produced units that pass quality checks on the first attempt without rework. It is a direct indicator of first-pass process capability and quality stability.
    Q: How do you calculate FTT percentage?
    FTT % is calculated as first-time good quantity divided by produced quantity, multiplied by 100. Teams should keep denominator rules consistent across lines and shifts.
    Q: How do you calculate FTT PPM?
    FTT PPM is calculated as first-time defect quantity divided by produced quantity, multiplied by 1,000,000. It is useful for detecting quality drift in high-volume production.
    Q: What data is needed to make FTT actionable?
    You need production facts (good, rework, reject), defect events (family, reason, remark), and governed master tables for line, shift, model, and reason code values.
    Q: How often should FTT be reviewed?
    Review FTT every shift for tactical correction, daily for trend and ownership tracking, and weekly for recurring defect-family intervention planning.

    Operationalize First-Pass Quality with Infoveave

    Connect production and defect data, govern reason codes, and act on quality drift before it impacts output and delivery.
    Book a Demo

    About the Authors

    This article was produced by the Infoveave Product and Solutions Team — specialists in Unified data platforms, agentic BI, and enterprise analytics. Infoveave (by Noesys Software) helps organizations unify data, automate business process, and act faster with AI-powered insights.

    Ready to see Infoveave in action?

    Book a Demo
    ISO 27001ISO 27017ISO 27701GDPRHIPAACCPAAICPACSR LogoCapterra Reviews — Infoveave

    © 2026 Noesys Software Pvt Ltd

    Infoveave® is a product of Noesys

    All Rights Reserved