ECSS Brazing — Defect Disposition (space-systems/ecss/q7040-defect-disposition)
Use when the task is what happens after a brazement fails acceptance -- choosing between re-brazing the joint, repairing it locally, carrying it on an approved deviation, or scrapping it, and stating what has to be re-inspected afterwards.
Domain quick reference
- Disposition starts with how far past the limit the defect actually sits. A joint a few percent outside its class is a rework candidate; one several times outside is evidence the process ran wrong, and reworking it only buys a second defective joint with more heat in it.
- Re-brazing is a thermal cycle, and thermal cycles are a finite resource. Each one re-melts the filler, coarsens the joint microstructure, grows the diffusion zone into the parent metal and consumes part of the assembly's declared exposure allowance. The budget is counted, and once it is spent the route is closed whatever the defect looks like.
- A crack that has run into the parent metal is not a braze defect. Re-melting the filler does nothing to a crack in the base material and adds heat to its tip; that case leaves the rework routes entirely.
- Eroded parent metal is made worse by more heat. Erosion happens because molten filler dissolved the base metal, so a second cycle attacks the remaining wall; the route is mechanical, and where the erosion sits in the load path there is no route at all.
- Mechanical defects want mechanical repairs. Entrapped flux and excess filler are removed, not re-melted, and a local repair spends no part of the thermal budget.
- Use-as-is is a paperwork route with an engineering precondition. It needs an approved deviation on file and a defect that is not in the load path; without both it is a reject wearing a signature.
- Rework restarts the inspection, it does not inherit the old result. Whatever method found the defect has to find it gone, visual inspection is repeated, and a hermetic joint owes its leak test again, because the rework cycle can open a path the original test had already passed.
- The bound is a comparison, and a defect sitting exactly on it is within it. The ratio of a measurement to its limit is a quotient of measured quantities, so the comparison absorbs representation error rather than scrapping hardware on the last bit.
Workflow
- Normalise the defect: type, location, joint class, the measured value with its limit and direction, the re-braze count already spent, the thermal cycles used against the allowance, whether a deviation is approved, whether the joint is hermetic, and the method that found it.
- Score the severity ratio in the direction the criterion runs, and dispose the defect as accept-as-is where it is in fact within its limit and is not one of the defects rejected on existence.
- Take the defects that leave the rework routes first: a crack in the parent metal, and eroded parent metal in the load path.
- Send the mechanical defects to local repair, which costs no thermal cycle.
- For the remaining braze defects, test the rework bound, then the re-braze budget, then the cumulative exposure allowance, in that order, and take the first route still open.
- Where no rework route is open, test the deviation route: an approved deviation and a defect out of the load path. Otherwise reject and scrap.
- Attach the re-inspection the chosen route owes and report the re-braze attempts remaining.
Pitfalls
- Re-brazing a joint that is far outside its limit. The severity ratio is telling you the gap, the fixture, the cleaning or the filler placement was wrong; a second run with the same setup reproduces the defect and spends a cycle doing it.
- Counting only the re-braze attempts and not the cumulative thermal exposure. An assembly that has been through a braze cycle, a post-braze heat treatment and a repair cycle can be out of exposure allowance while its re-braze counter still reads one.
- Re-melting a joint to chase a crack that started in the parent metal. The filler was never the problem, and the cycle puts heat into a crack tip in material that has no filler to reflow.
- Adding heat to an eroded joint. The erosion is dissolved parent metal; another molten cycle dissolves more of what is left, and the wall that was marginal becomes a hole.
- Treating an approved deviation as a route for any defect. A deviation covers a defect nobody needs to be sound; a defect in the load path is not that, however senior the signature.
- Releasing reworked hardware on the original inspection record. The rework changed the joint, so the record describes a joint that no longer exists, and a leak path opened during the repair cycle is invisible to it.
Behavior contract (gate 3)
Defect normalisation, the severity ratio in both criterion directions, the parent-metal and erosion exits, the mechanical repair route, the re-braze budget and exposure allowance tests, the deviation precondition and the re-inspection duty are exercised by the gate 3 contract test: scripts/test_q7040_defect_disposition.py against scripts/q7040_defect_disposition_logic.py (stdlib unittest, offline). Run: python3 scripts/test_q7040_defect_disposition.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
