Wheel Hub Nonconformance: MRB Disposition and Stock Control
A material review board record decides what happens to a defined nonconforming population. It must not convert an undocumented departure into acceptable stock or allow supplier authority to exceed the buyer’s contract and design control.
How should distributors control a wheel hub MRB disposition?
Identify the exact requirement and nonconforming condition, then bound every affected part, lot, quantity, location, work-in-process, shipment and downstream customer. Segregate and status-control the population before disposition. Document who has authority for return, scrap, rework-to-specification, repair or use-as-is under the actual design ownership and contract; obtain buyer approval where required before shipment or further processing. Link the decision to technical rationale, risk review, reinspection, labeling, traceability, financial handling and notifications. Preserve superseded decisions and never infer that one approved disposition applies to another lot or repeat order.
Describe the nonconformance precisely
Compare the observed condition with one controlled requirement. For wheel hub nonconformance disposition, that boundary matters because labels such as cosmetic or minor can replace measurable evidence and hide scope. The responsible reviewer should decide the question being answered before opening a catalog, measuring a sample or requesting a supplier statement. A narrow decision can be audited; a broad promise assembled from partial clues cannot.
Begin with part, revision, requirement source, actual condition, method, photos and detection event. Keep the original input unchanged beside every normalized value, translation or derived field. Then state the departure without guessing cause or acceptability. Unknown is a controlled status, not permission to copy the most common value from a neighboring SKU. A field remains open until the cited evidence actually resolves it.
Decision rule and evidence owner
The retained record should retain reporter, time, measurement record and requirement revision. This makes a later quotation, receipt, complaint or correction understandable to someone who did not take part in the first conversation. If the team cannot reconstruct the source and decision, the status should return to review rather than remain approved through habit.
Consider this case: surface damage is reported without location, extent or drawing criterion. The stop condition is the condition cannot be evaluated against a controlled requirement. Record the conflict at field level, identify an owner and ask one precise question. Do not hide the open point inside a general note such as “please confirm,” because that wording rarely survives into the next system or order revision.
Bound and segregate affected stock
Prevent unintended use while tracing every location and process state. For wheel hub nonconformance disposition, that boundary matters because physical quarantine at one site can miss work-in-process, in-transit or customer stock. The responsible reviewer should decide the question being answered before opening a catalog, measuring a sample or requesting a supplier statement. A narrow decision can be audited; a broad promise assembled from partial clues cannot.
Begin with lots, serials, date codes, quantities, sites, WIP, warehouse, shipments and customers. Keep the original input unchanged beside every normalized value, translation or derived field. Then reconcile total suspect population and apply visible system and physical status. Unknown is a controlled status, not permission to copy the most common value from a neighboring SKU. A field remains open until the cited evidence actually resolves it.
A workable release condition
The retained record should record hold owner, location, quantity movements and release blocks. This makes a later quotation, receipt, complaint or correction understandable to someone who did not take part in the first conversation. If the team cannot reconstruct the source and decision, the status should return to review rather than remain approved through habit.
Consider this case: a later receipt from the same period bypasses the original hold. The stop condition is the suspect population is not bounded. Record the conflict at field level, identify an owner and ask one precise question. Do not hide the open point inside a general note such as “please confirm,” because that wording rarely survives into the next system or order revision.
Define MRB authority before disposition
Match each decision type to design ownership, contract and authorized roles. For wheel hub nonconformance disposition, that boundary matters because a supplier may assume it can approve use-as-is or repair without buyer authority. The responsible reviewer should decide the question being answered before opening a catalog, measuring a sample or requesting a supplier statement. A narrow decision can be audited; a broad promise assembled from partial clues cannot.
Begin with purchase terms, drawing ownership, delegation, customer requirement and approval matrix. Keep the original input unchanged beside every normalized value, translation or derived field. Then route dispositions through the correct technical and commercial owners. Unknown is a controlled status, not permission to copy the most common value from a neighboring SKU. A field remains open until the cited evidence actually resolves it.
How to document the exception
The retained record should retain signatures, limits, rationale and approval date. This makes a later quotation, receipt, complaint or correction understandable to someone who did not take part in the first conversation. If the team cannot reconstruct the source and decision, the status should return to review rather than remain approved through habit.
Consider this case: a supplier engineer approves a departure controlled by the buyer drawing. The stop condition is the decision authority cannot be demonstrated. Record the conflict at field level, identify an owner and ask one precise question. Do not hide the open point inside a general note such as “please confirm,” because that wording rarely survives into the next system or order revision.
Execute and verify the disposition
Control return, scrap, rework, repair or use-as-is as different workflows. For wheel hub nonconformance disposition, that boundary matters because one status word can hide required instructions, verification or part marking. The responsible reviewer should decide the question being answered before opening a catalog, measuring a sample or requesting a supplier statement. A narrow decision can be audited; a broad promise assembled from partial clues cannot.
Begin with approved instruction, quantity, operator, reinspection, scrap evidence, return record and labeling. Keep the original input unchanged beside every normalized value, translation or derived field. Then issue lot-specific instructions and reconcile completed quantities. Unknown is a controlled status, not permission to copy the most common value from a neighboring SKU. A field remains open until the cited evidence actually resolves it.
A case that exposes the hidden risk
The retained record should retain completion evidence, verifier and residual exceptions. This makes a later quotation, receipt, complaint or correction understandable to someone who did not take part in the first conversation. If the team cannot reconstruct the source and decision, the status should return to review rather than remain approved through habit.
Consider this case: reworked units are mixed with conforming stock before reinspection. The stop condition is the approved disposition was not followed. Record the conflict at field level, identify an owner and ask one precise question. Do not hide the open point inside a general note such as “please confirm,” because that wording rarely survives into the next system or order revision.
Close downstream and repeat-order risk
Notify affected parties and feed the event into corrective and change controls. For wheel hub nonconformance disposition, that boundary matters because closing the MRB at the factory may leave buyer, carrier or customer records unchanged. The responsible reviewer should decide the question being answered before opening a catalog, measuring a sample or requesting a supplier statement. A narrow decision can be audited; a broad promise assembled from partial clues cannot.
Begin with shipments, customers, credit or debit, corrective action, PCN, repeat lots and system holds. Keep the original input unchanged beside every normalized value, translation or derived field. Then confirm each downstream decision and remove holds only with authority. Unknown is a controlled status, not permission to copy the most common value from a neighboring SKU. A field remains open until the cited evidence actually resolves it.
What a second reviewer should see
The retained record should retain recipients, timestamps, acknowledgments and recurrence review. This makes a later quotation, receipt, complaint or correction understandable to someone who did not take part in the first conversation. If the team cannot reconstruct the source and decision, the status should return to review rather than remain approved through habit.
Consider this case: a use-as-is approval is attached to the next PO without review. The stop condition is downstream recipients or repeat risk remain open. Record the conflict at field level, identify an owner and ask one precise question. Do not hide the open point inside a general note such as “please confirm,” because that wording rarely survives into the next system or order revision.
MRB disposition control record
The record keeps nonconformance, population and decision authority inseparable.
| Stage | Required evidence | Release condition |
|---|---|---|
| Condition | Requirement versus actual | Reviewable |
| Population | Lot, quantity, location | Reconciled |
| Hold | Physical and system status | Effective |
| Authority | Design and contract matrix | Authorized |
| Disposition | Instruction and verification | Completed |
| Closure | Notifications and recurrence | Documented |
Keep every disposition lot-specific and reversible in the record
Timken's public supplier manual requires written deviation before shipping nonconforming product in that customer relationship and describes notification fields for product detected after shipment.
ZF QD83 provides a public supplier-quality example of documented nonconforming-product disposition and buyer notification boundaries.
The actual buyer contract and design authority determine whether return, scrap, rework, repair or use-as-is may be approved and by whom.
Claim boundary: This guide does not grant MRB authority, approve any nonconforming wheel hub, define a defect as cosmetic or acceptable, or state JNHJDP's current stock condition.
Additional review scenarios for wheel hub nonconformance disposition
Review scenario 1 for wheel hub nonconformance disposition: Start from part, revision, requirement source, actual condition, method, photos and detection event. The reviewer should state the departure without guessing cause or acceptability. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will retain reporter, time, measurement record and requirement revision. If the condition cannot be evaluated against a controlled requirement, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.
Review scenario 2 for wheel hub nonconformance disposition: Start from lots, serials, date codes, quantities, sites, WIP, warehouse, shipments and customers. The reviewer should reconcile total suspect population and apply visible system and physical status. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will record hold owner, location, quantity movements and release blocks. If the suspect population is not bounded, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.
Review scenario 3 for wheel hub nonconformance disposition: Start from purchase terms, drawing ownership, delegation, customer requirement and approval matrix. The reviewer should route dispositions through the correct technical and commercial owners. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will retain signatures, limits, rationale and approval date. If the decision authority cannot be demonstrated, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.
Review scenario 4 for wheel hub nonconformance disposition: Start from approved instruction, quantity, operator, reinspection, scrap evidence, return record and labeling. The reviewer should issue lot-specific instructions and reconcile completed quantities. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will retain completion evidence, verifier and residual exceptions. If the approved disposition was not followed, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.
Review scenario 5 for wheel hub nonconformance disposition: Start from shipments, customers, credit or debit, corrective action, PCN, repeat lots and system holds. The reviewer should confirm each downstream decision and remove holds only with authority. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will retain recipients, timestamps, acknowledgments and recurrence review. If downstream recipients or repeat risk remain open, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.
Review scenario 6 for wheel hub nonconformance disposition: Start from part, revision, requirement source, actual condition, method, photos and detection event. The reviewer should state the departure without guessing cause or acceptability. An independent checker then tests the conclusion against the stated decision boundary and confirms that the record will retain reporter, time, measurement record and requirement revision. If the condition cannot be evaluated against a controlled requirement, keep the affected line on hold, name the missing evidence and prevent the provisional interpretation from entering a quote, catalog, purchase order or customer promise. The case can move again when the evidence owner closes that exact field; a general assurance, familiar photograph or previous order is not a substitute for the missing source.
Related wheel hub buyer resources
- Wheel Hub Assembly catalog
- Wheel Hub Bearing catalog
- wheel bearing versus wheel hub assembly guide
- ABS encoder identification guide
- wheel hub OE number and RFQ guide
- fitment verification workflow
- sample approval workflow
- kit contents and BOM verification
- supplier evaluation evidence guide
- export packaging checklist
- MOQ and lead-time planning guide
- incoming inspection checklist
- About Jinan Huayuan Auto Bearing
Sources, dates and claim boundaries
- Timken Supplier Requirements Manual — public requirements covering revision control, identification, lot traceability, shipment records and supplier evidence boundaries
- ZF QD83 supplier quality directive — public supplier-quality example distinguishing nonconforming disposition, rework or repair and process-change approval; the actual contract controls
- Timken corporate quality procedure — public defect-material-report fields, response review and corrective-action effectiveness verification
- Schaeffler complaint process — public supplier-complaint process using containment, planned corrective measures and effectiveness evidence
Technical review: Jinan Huayuan Auto Bearing editorial review for source fidelity, procurement-data consistency and unsupported-claim removal. This review does not replace an OE catalog, vehicle service procedure, legal or customs advice, a customer-approved drawing, or mutually agreed commercial and inspection terms.
Corrections: Send the page URL and supporting evidence through the contact page. Material corrections are reviewed, linked records are rechecked and the updated date is changed when warranted.
