After a Bit Fails: ZZSEGU Failure Analysis, Field Support, and Training System
Nov 19,2026
A bit that fails early is worth more than its weight in steel only if somebody reads it. Our failure analysis turns a returned bit into a documented cause - selection, parameters, formation, or material - with a written report and a correction for the next run. The system behind it: six inputs, four cause categories, fixed response deadlines, and training that prevents the next failure.
What a Failure Analysis Covers
From returned bit to written report
An early failure only becomes information when someone reads the bit. The pressure point in current procurement is exactly this: with supply chains tight and projects bought on total cost, buyers weigh the support system behind a bit as heavily as its price, and a supplier who answers a failed bit with the phrase formation problem - no analysis, no recommendation - will be replaced at the next tender. Our failure analysis runs five steps. The failed bit is returned to the factory; our engineers clean, photograph, and grade it on the IADC eight-scale dull system; the cutting structure, the steel body, and the threaded connections are examined; the findings are matched against the drilling log the customer supplied; and the result is a written report with a cause and a correction for the next run. Every step produces a record, so the conclusion traces back to evidence rather than to an opinion.
The six inputs the analysis needs
The report is only as good as the inputs. Six items make an analysis conclusive, and every one of them is something the drilling crew already produces: a description of the formation with a stratigraphic column; the drilling parameter log covering weight on bit, rotary speed, and torque; a record of the circulating medium with its flow rate - air volume for DTH strings, mud flow for fixed-cutter strings; cuttings samples from the failing interval; the bit accumulated footage and running hours; and a description of anything unusual observed when the bit was pulled. Missing items do not stop the analysis, but each gap turns a conclusion from measured into probable. The most valuable single item is the parameter log: it separates a bit that was run outside its design envelope from a bit that failed inside it, which is the distinction most disputes turn on.
Four Causes and Their Evidence
Selection mismatch and parameter errors
Two of the four cause categories are bought or run, not geology. Selection mismatch shows up as wear far outside the design curve: outer cutters rounded off while the body is intact, or a wear rate several times the design value in a named formation. The correction is re-selection against the formation band, and the report names the band to re-select from. Parameter errors leave signatures on the face instead. Flat-faced wear (IADC code FC) points at rotary speed above the formation band; thermal cracks (HC) at cooling starvation with cutting-zone temperatures near 700 degrees Celsius; chipping (BT, CT) at hard stringers or impact the bit was not graded for. The correction here is not a different bit but different numbers - weight, speed, or hydraulics - and often a short refresher with the crew on the operating table rather than a replacement order.
Formation changes and material defects
Formation change and material defect are the two causes a supplier must prove rather than assert. A formation change announces itself in both places at once: damage concentrated in one interval, and the log showing an interbed or a fault crossing at the same depth. The correction is an assembly or selection adjustment for that boundary, not a replacement bit of the same type. A material defect is the opposite case, and the rarest: braze-line separation on a PDC cutter, a body crack, or a metallographic anomaly, found on one bit out of a batch. Our disposition for a confirmed defect is rework or replacement with a written disposition record - the failed units are reworked or returned and re-inspected, and the batch record carries the action. For large projects where the order contract specifies record delivery, the retained records behind that disposition are available to the buyer as agreed in the contract.
Cause category | Evidence on the bit | Evidence in the logs | Correction |
|---|---|---|---|
Selection mismatch | uniform wear, outer cutters rounded, body intact | ROP far under design curve in named formation | re-select against the formation band |
Parameter errors | FC flat wear, HC thermal cracks, BT/CT chipping | rpm or weight drifted from the operating table | reset parameters, brief the crew |
Formation change | damage concentrated in one interval | interbed or fault crossing at the same depth | adjust assembly for the boundary |
Material defect | braze-line separation, body crack, metallographic anomaly | isolated to one bit of a batch | rework or replacement, written disposition |
Table 1. The four cause categories, the evidence each leaves on the bit and in the logs, and the correction that follows.
Response Deadlines and Deliverables
The clock from receipt to report
Deadlines make a support promise checkable, so ours are fixed. A returned bit or a written claim is confirmed within 24 hours and given a file number. The preliminary cause note goes out within 5 working days of receiving a complete input set - the six items from the previous section. The formal report follows within 10 working days, and re-inspection on a disputed finding completes within 15 working days. Two boundaries keep the clock honest. The 5-day and 10-day clocks start only when the input set is complete, which is why the six inputs are worth assembling before the bit ships back. And the deadlines count in working days, because customs clearance of a returned tool, in either direction, takes days no factory can compress. Contractors who need dates for a project claim file can quote the table below.
Stage | Clock | Output |
|---|---|---|
Receipt confirmation | within 24 hours | acknowledgment with file number |
Preliminary cause | 5 working days from complete inputs | short electronic note |
Formal report | 10 working days | photos, dull grade, detection data, recommendations |
Re-inspection on dispute | 15 working days | re-inspection record and disposition |
Reworked units | with the report | written rework record in the batch file |
Table 2. The response clock: each stage, its deadline, and the document it produces.
What the formal report contains
The formal report is written to be filed, not just answered. It carries the identification of the order, batch, and bit; return-condition photographs; the IADC dull grade of the cutting structure with location codes; the detection results relevant to the bit family - braze-layer ultrasonic readings for PDC cutters, gauge and dimensional checks and hardness for steel bodies, and dimensional or fit checks for press-fitted tricone and DTH parts; a comparison of the run parameters against the design envelope; the cause assignment with its evidence; and the correction for the next run, whether that is selection, parameters, or assembly. A report that ends at cause without a correction is half a report, and ours does not stop there. The report also states what it does not conclude: where inputs were incomplete, the cause is marked probable and the missing item is listed, so a second pass can close the gap if the crew can supply it.
Field Support and Training
Remote sessions and on-site visits
Not every failure needs a shipment. For a bit pulled early with an unclear cause, a remote video session within 48 hours usually separates the four causes well enough to keep drilling: the crew shows the bit face on camera, the parameter log is read together, and the recommendation goes out the same day. Complex cases - repeated failures in one interval, a string of short runs, or a formation with no local history - justify an on-site engineer. Scheduling depends on the country: 2-4 weeks from request to arrival once travel documents are in order, and the visit ends with a written site note that feeds back into the same analysis loop. On-site work on custom tooling connects to the custom delivery process described in the October 21 article: the site observations go into the same engineering file that produced the custom design.
Courses for crews and dealers
Prevention is cheaper than analysis, which is why the training system exists. For drilling crews the core course is one day of 8 hours: IADC codes, weight and speed bands by formation, and the dull-grading scale, so a crew can read its own pulls before shipping them. A half-day workshop of 4 hours practices the grading on real pulled bits. For hard-rock air drilling there is a half-day session on hammer air demand and annular velocity - the numbers from the November 17 article - because dirty holes are routinely misdiagnosed as bad hammers. For distributors the course runs 2 days of 16 hours: the product line, order lead times, and the claim process, so a dealer can answer a customer with documents instead of apologies. Course length and content are fixed, and a project buyer books any of them through the same contact that handles orders.
Course | Audience | Length | Content |
|---|---|---|---|
Bit selection and parameters | drilling crews | 1 day, 8 hours | IADC codes, weight and speed bands, dull scale |
Dull grading workshop | crews, site engineers | half day, 4 hours | grading practice on real pulled bits |
Air drilling session | crews in hard rock | half day, 4 hours | hammer air demand, annular velocity, wet holes |
Product line and claim process | distributors | 2 days, 16 hours | product range, lead times, claim documents |
Custom tooling briefing | project buyers | 2 hours | October custom delivery process interface |
Table 3. The training catalogue: course, audience, fixed length, and content.
Dispute Handling and Documentation
Claim review and disposition
A quality dispute follows a fixed path. The buyer files the claim in writing with the bit and the input set; we confirm within 24 hours; re-inspection completes within 15 working days; and the disposition is written, never verbal. Possible outcomes are rework, replacement, or a written explanation with evidence when no defect is found. Where the buyer prefers an independent verdict, the buyer commissions and pays for the third-party re-inspection - our role is to provide the retained samples and the records the order contract specifies, and to accept the outcome if the third party finds against us. That is the same boundary the November 11 testing article drew on third-party witnessing: the factory does not schedule third-party inspection on its own initiative; it responds when the buyer initiates one.
Re-inspection finding | Disposition | Timeline |
|---|---|---|
Confirmed material defect | rework or replacement with written record | with the 15-working-day re-inspection |
Parameter or selection cause | corrective recommendations, no claim | in the final report |
Mixed cause | partial disposition agreed in writing | negotiated before closing the file |
Third-party re-inspection | retained samples and contract-specified records provided | per contract terms |
No defect found | written explanation with evidence | within 15 working days |
Table 4. Disposition paths by re-inspection finding, with the timeline each path follows.
What contractors can file
Documents outlive bits. The analysis report and its correction are written so a contractor can file them in the project archive: identification, evidence, cause, and correction, without marketing language. For wells tendered under government or NGO rules, the report supports the claim file a contractor assembles for unexpected ground conditions. Delivery shipments continue to carry the certificate of conformity as the standard accompanying document; the fuller record sets behind a dispute - batch records, re-inspection data, disposition records - are provided where the order contract specifies them, which in practice means the large project orders described in the November 11 article. The principle is uniform: everything the factory promises in support is written, dated, and traceable to a file number. The table below collects the channels and their response times so the system can be checked rather than trusted.
Situation | Channel | Response time |
|---|---|---|
Bit pulled early, cause unclear | remote video session | within 48 hours |
Complex or repeated failures | on-site engineer visit | 2-4 weeks from request |
Training request | course at site or dealer office | per agreed schedule |
Quality dispute | written claim with bit and inputs | confirmed 24 h, re-inspection 15 working days |
Order and delivery questions | sales contact | 1 working day |
Table 5. Support channels by situation, with the response time each channel commits to.
A failed bit is either a cost or a lesson, and the difference is whether anyone reads it under fixed rules. The five analysis steps, the six inputs, the four cause categories, and the clocks of 24 hours, 5, 10, and 15 working days are the rules; the reports, the training hours, and the file numbers are the proof. A buyer comparing suppliers on total cost can verify every line of this article against the documents it names - and that checkability, more than any single claim, is what the support system is built to deliver.
ZZSEGU turns failed bits into documented causes: five analysis steps, six inputs, four cause categories, deadlines of 24 hours and 5, 10, 15 working days, field support, fixed training courses, and written dispositions.
Frequently Asked Questions
PREVIOUS:
Contact Us








