The Explainer Untracked Reality Cumulative Damage

NO SINGLE CYCLE BREAKS THE PIPE THE SUM CAN Yesterday: Crescent Dunes, and why scale-up is a change Today: One of the slowest hazards in a thermal plan damage accumulating while every operating day looks normal1. THE IDEA Metal can fail under repeated stress ranges well below its static strength that is fatigue. Every heat-up and cool-down expands and contracts the steel2. One cycle may leave no visible trace, but thousands of cycles can initiate and grow a crack especially at welds, notches, and local stress concentrations. MINER’S RULE Miner’s rule turns fatigue into an accounting model: D=∑▒n_i/N_i n_i ∶Number of cycles experienced in a given stress range2. N_i: Estimated number of cycles to failure at that rang . Each cycle consumes an estimated fraction of fatigue life. In the linear damage model, D approaching signal that calculated usage has reached its design limit not a guaranteed failure timestamp. Code-based pressure-equipment assessments use related cumulative fatigue-usage methods with code-specific rules and design margins. WHY IT MATTERS FOR CSP Molten-salt thermal storage tanks experience daily pressure and temperature cycles. A simple assumption of one cycle per day gives about 10,950 cycles over 30 years. One published industry design basis for nitrate-salt tanks specifies at least 10,000 low-cycle fatigue cycles and operating procedures consistent with a 30-year fatigue life. That is a useful warning not a universal rule for every tank. Actual fatigue usage depends on design, local stresses, thermal gradients, and real operational cycles. Cycles are not equal: A rapid cloud transient, uneven salt distribution, or emergency trip can impose a vastly different stress range than a controlled daily ramp6. KNOWING ITS LIMITS Miner’s rule does not fully capture load sequence the order of loads matters. Actual failure does not occur at one universally reliable value of D Calculations depend on local stress or strain at critical locations not average tank temperature. It only counts cycles and transients captured by monitoring. A usage factor built on assumed cycles is a model-based estimate, not a direct measurement of remaining life. THE CASE: DAMAGE NOBODY COUNTED On 9 August 2004, a condensate pipe ruptured at Mihama Unit 3 in Japan, resulting in 5 fatalities and 6 serious injuries. The mechanism was not fatigue, but erosion-corrosion (flow-accelerated corrosion) downstream of an orifice that thinned the pipe wall until it ruptured under pressure. The rupture location was omitted from the relevant inspection-management system. The overarching lesson: Cumulative damage whatever its mechanism can progress unnoticed when critical locations are not identified, inspected, and tracked. THE LINK TO THE SERIES Vaughan: Every cycle without failure can become false reassurance that the next one is safe. Reason: Fatigue is a latent condition that can grow silently inside the material. Monte Carlo: Fatigue life is uncertain and variable, not a single guaranteed number. Barrier Matrix: An integrity barrier is only as strong as the last verified inspection and the quality of the assumptions behind it THE REAL SAFEGUARD Count actual cycles and meaningful transients—not only design assumptions12. Classify severe ramps, trips, and abnormal thermal events separately13. Track fatigue usage at critical locations as an operating and integrity parameter13. Verify that every critical location is included in the inspection plan13. Review inspection scope and frequency as damage usage and uncertainty increase13. What in your plant is quietly accumulating damage and who is keeping score?13 Next stop: Arc flash, IEEE 1584, and why the label on the panel may not match the incident energy behind it Follow the series on YouTube:    / @safetybymenga3c