❌

Reading view

How heat and cooling methods alter basalt fiber concrete’s mechanical behavior

When a tunnel catches fire, temperatures inside the concrete lining can soar to 800 or 900 degrees Celsius, and the emergency response almost always involves dousing the structure with water. A new study suggests that this familiar firefighting image—flames followed by a torrent of cooling water—may be doing far more damage to the concrete than engineers have typically accounted for. Researchers investigating basalt fiber-reinforced concrete have found that how a fire-damaged structure is cooled can be as important as how hot it got in the first place, with water quenching consistently inflicting greater strength loss than slow, natural cooling across every temperature they tested.

The research, published in Case Studies in Construction Materials, systematically examined how heating temperature, cooling regime, fiber content, and impact loading combine to determine whether concrete survives a fire with its load-bearing capacity intact. The team, led by Yang Liu and colleagues including Delin Li, Jinyue Dong, Yingda Zhang, Xianliang Zhou, and Qiong Zhou, chose basalt fiber-reinforced concrete, or BFRC, as their test material because of the fiber’s unusual combination of properties. Basalt fibers, drawn from volcanic rock, offer high tensile strength, thermal stability up to melting points between 1350 and 1450 degrees Celsius, and a cost profile far more attractive than premium alternatives such as carbon fiber. This makes them an appealing candidate for tunnel linings, where fire resistance and economy must be balanced.

The experimental design was exhaustive. The researchers prepared a C35-grade concrete mix—the grade commonly recommended for tunnel design—using ordinary Portland cement, medium sand, and continuously graded gravel between 5 and 10 millimeters. Into this base mix they incorporated chopped basalt fibers, 12 millimeters long with a monofilament diameter of 17 micrometers, at volume fractions of 0, 0.1, and 0.2 percent. The fibers were added in small batches during dry mixing to prevent agglomeration, and the fresh concrete was cast into cylindrical specimens measuring 50 millimeters in diameter and 25 millimeters in height, then cured under standard conditions at 20 degrees Celsius and 95 percent relative humidity.

The thermal assault began in a high-temperature electric oven capable of reaching 1200 degrees Celsius. Specimens were heated at a controlled rate of 5 degrees Celsius per minute to target temperatures of 200, 400, 600, and 800 degrees Celsius, then held at temperature for a full hour to ensure the heat penetrated the interior. Half the specimens were then removed and allowed to cool naturally in ambient air, mimicking a structure left to cool on its own after a fire. The other half were plunged immediately into a tank of tap water, replicating the thermal shock of firefighting operations. After cooling, the water-immersed specimens were conditioned in air for seven days to return them to a natural moisture state before testing.

The dynamic mechanical properties were then probed using a split Hopkinson pressure bar, the workhorse instrument for measuring how materials behave under the extreme strain rates produced by impacts and blasts. The apparatus used bars 75 millimeters in diameter, made of high-strength steel with an elastic modulus of 210 gigapascals, with a striker bar propelled by compressed gas striking an incident bar that transmitted stress waves through the specimen. Three impact velocities—3.5, 4.4, and 5.2 meters per second—were tested, achieved by varying the operating gas pressure, with three specimens per condition. A thin pulse shaper was pasted at the impact end of the incident bar to smooth out high-frequency oscillations, and stress equilibrium between the two faces of each specimen was verified from strain-gauge signals, confirming the reliability of the data. Fragments from each impact were sieved through meshes ranging from 4.75 millimeters down to 75 micrometers so that a fractal dimension could be calculated, providing a quantitative measure of how thoroughly each specimen shattered.

The visual evidence of thermal damage followed a familiar but telling progression. At 200 degrees Celsius, the concrete surfaces turned bluish-gray, with no cracking. By 400 degrees, the color shifted to yellowish-gray, still structurally sound. At 600 degrees, fine cracks appeared along with slight surface peeling, and by 800 degrees the specimens showed severe cracking, spalling, and edge breakage. Water-cooled specimens generally exhibited more pronounced surface damage than their naturally cooled counterparts, and at 800 degrees the concave shape at the start of the stress-strain curve—evidence of pre-existing microcracks being closed under compression—was especially marked in the water-quenched samples.

The strength data told a stark quantitative story. For naturally cooled specimens containing 0.2 percent basalt fiber, the dynamic peak stress at an impact velocity of 3.5 meters per second fell from 51.1 megapascals at room temperature to 18.6 megapascals at 800 degrees—a reduction of 63.6 percent. Water cooling made matters worse across the board: at the same impact velocity, the reductions reached 23.9 percent at just 200 degrees and climbed to 64.9 percent at 800 degrees. Averaged across the temperature range, each 100-degree increment cost naturally cooled specimens roughly 6.7 to 8.0 percent of their strength, while water-cooled specimens lost about 7.5 to 8.1 percent per 100 degrees. The gap between the two cooling regimes widened at higher impact velocities: at 5.2 meters per second and 800 degrees, the water-cooled specimens suffered 6.4 percent greater strength loss than the naturally cooled ones, whereas at the lowest velocity the difference was a mere 1.3 percent. The explanation lies in competing timescales—at slow loading rates, cracks have time to propagate and dissipate energy, blunting the effect of water-induced damage, but at high rates the loading outpaces the material’s energy dissipation, and the microcracks created by thermal shock propagate catastrophically.

Against this backdrop of degradation, the basalt fibers demonstrated genuine protective power. At every temperature from 200 to 800 degrees, specimens with 0.2 percent fiber content outperformed both plain concrete and the 0.1 percent mix. At 400 degrees and an impact velocity of 3.5 meters per second, the naturally cooled fiber-reinforced specimens reached peak stresses of 40.1 megapascals, some 16.9 percent above plain concrete, while at 200 degrees under water cooling the 0.2 percent mix achieved 38.8 megapascals—a remarkable 32.4 percent improvement over unreinforced concrete. The mechanism, the authors explain, is architectural: randomly distributed fibers form a three-dimensional network that binds tightly with the cementitious matrix, reduces internal pores and cracks, and bridges microcracks before they can coalesce into fracture surfaces. But this protection has a ceiling. Above roughly 600 degrees, the fibers begin to degrade and lose their reinforcing capability, and the fiber-matrix interface—already weakened by thermal mismatch between fiber and paste—becomes a liability during water quenching.

Fractal analysis of the impact debris added another layer of insight. The fractal dimension of the fragments rose steadily with temperature, from around 1.82 at 200 degrees to above 2.3 at 800 degrees under the highest loading rate, indicating progressively finer and more complex fragmentation. Water-cooled specimens consistently shattered into finer pieces than naturally cooled ones, particularly at 600 and 800 degrees, confirming that the steep thermal gradients during quenching seed dense populations of microcracks that later explode into fracture networks under impact.

Microstructural investigation grounded these observations in chemistry and physics. X-ray diffraction of specimens heated to 800 degrees showed the disappearance of calcium hydroxide peaks and weakened calcium carbonate signals, evidence that these phases had thermally decomposed—reactions that release vapor, increase porosity, and weaken the matrix. Scanning electron microscopy revealed the deterioration in vivid detail: an unheated specimen showed a dense microstructure with abundant calcium-silicate-hydrate gel and a compact interfacial transition zone around each aggregate, while specimens heated to 800 degrees contained no detectable C-S-H gel at all, their structure riddled with pores and cracks and hosting instead a dicalcium silicate-like phase. Comparing cooling regimes at 400 degrees, the naturally cooled sample remained relatively dense and rich in hydration products, whereas its water-quenched twin displayed obvious cracks at the interfacial transition zone and a loosened surrounding matrix—the fingerprint of thermal shock stress racing through the cooling material.

The practical implications reach well beyond the laboratory. Tunnel linings that survive a fire are routinely assessed and, if necessary, repaired, but this study shows that the assessment itself must account for the cooling history. A lining quenched by firefighting water may be significantly weaker than its peak temperature alone would suggest, particularly if it subsequently faces dynamic loads from traffic vibration, rockfall impacts, or secondary events. Conversely, the results give engineers a positive tool: specifying basalt fiber reinforcement at around 0.2 percent by volume can meaningfully bolster the impact resistance of fire-exposed concrete below 600 degrees, at a modest material cost. The authors frame their work as a theoretical foundation for post-fire safety assessment of tunnel linings and for the wider engineering adoption of basalt fiber-reinforced concrete—a reminder that in structural fire engineering, what happens in the minutes after the flames matter almost as much as the fire itself.

Subject of Research: Dynamic mechanical properties and deterioration mechanisms of basalt fiber-reinforced concrete after exposure to high temperatures under natural cooling and water cooling, investigated using split Hopkinson pressure bar testing, XRD, and SEM analysis.

Article Title: Dynamic mechanical properties of basalt fiber-reinforced concrete after exposure to high temperature and different cooling methods

Article References: Liu, Y., Li, D., Dong, J., Zhang, Y., Zhou, X., & Zhou, Q. (2026). Dynamic mechanical properties of basalt fiber-reinforced concrete after exposure to high temperature and different cooling methods. Case Studies in Construction Materials, 25, Article e06505. https://doi.org/10.1016/j.cscm.2026.e06505

Image Credits: AI Generated

DOI: 10.1016/j.cscm.2026.e06505

Keywords: basalt fiber-reinforced concrete, tunnel fire, high temperature exposure, water cooling, thermal shock, split Hopkinson pressure bar, dynamic compressive strength, fractal dimension, interfacial transition zone, XRD, SEM, microstructural deterioration

  •  

Cloud has a new bulk capacity market

For 15 years, public cloud providers have defined the industry for most enterprises: on-demand, automatically metered services delivered over the open internet that give developers immediate access to storage, databases, compute, application development platforms, and AI capabilities. That model remains dominant because it is simple, well-instrumented, and universally supported. Yet an adjacent reality has always existed. Large-scale, off-market capacity deals where technology companies with surplus GPUs, storage, and compute sold blocks of capacity in bulk to other firms under nondisclosure agreements were once common. Those were cloud transactions in substance, since you were using somebody else’s servers. However, they lacked the automation, metering, and governance that define public cloud services, and they operated entirely outside the frameworks enterprises rely on for budgeting, compliance, and accountability.

A shadow market becomes visible

These arrangements are now becoming more visible and more formalized. Some are even openly auctioned. Meta’s entrance into the cloud capacity space, essentially offering its excess compute infrastructure to outside buyers, represents the maturation of a market that has existed in back rooms for years. Large, multiyear capacity commitments are no longer whispered about during boardroom lunches. They are being announced, financed, and tracked by analysts. This shift is creating a distinct layer in the cloud landscape, one that sits between traditional hyperscalers and true private clouds, and one that enterprises can no longer afford to ignore.

The practical implication is that the cloud market you thought you understood now has a parallel track. When a large enterprise needs maximum GPU capacity for model training or inference, it has more options than a year ago, and those options come with genuinely different trade-offs. You can go to a hyperscaler and pay the published rate for metered GPU as a service, receiving a fully managed platform with all the tools, governance, and integration you need. Or you can reach out to a technology provider that happens to have idle or excess GPU capacity and negotiate a bulk deal at a fraction of the published rate. The first option provides predictability and depth of service. The second offers raw cost savings if you have the operational capability to handle less-managed infrastructure.

This bifurcation is muddying procurement decisions. The gap in pricing between bulk off-market capacity and public cloud offerings can be substantial. Some analysts cite differentials ranging from 10 to 100 times. But headline GPU rates are only part of the evaluation. Bulk deals tend to come with minimal metering, limited monitoring, and a do-it-yourself culture around incident response and optimization. You are, in effect, purchasing wholesale energy. It is robust and capable, but it requires your own wiring and maintenance. Organizations accustomed to the instrumentation and service-level agreements of hyperscalers may find such a different operational reality a bit jarring. Those with mature cloudops teams may find the economics compelling.

Who benefits and who adjusts

The hyperscale incumbents will not be displaced overnight. They offer the complete ecosystem, not just GPU frameworks but development tools, hundreds of managed services, identity, compliance, and integration layers that are genuinely difficult to replicate. However, they are now facing a market where customers with intensive computational needs can source raw GPU capacity from alternative suppliers, particularly for bursty or cost-sensitive workloads. This is not necessarily a threat to hyperscaler dominance, but it is a complication. The hyperscalers will likely respond through partnerships, capacity-coverage agreements, and possibly acquisitions of promising capacity players. Effectively, they will become customers of the same off-market ecosystem they once ignored.

The cloud market is adding a new axis of choice: managed breadth versus specialized efficiency. Enterprises will increasingly construct hybrid operating models, keeping steady-state, security-sensitive, and toolchain-dependent workloads on hyperscaler platforms while offloading cost-intensive training runs and elastic inference to bulk-capacity providers. This is not a binary choice. It is an expanding continuum of sourcing options that demands more sophisticated procurement and architecture planning.

How to take advantage

Know your actual workload cost before you negotiate. If your AI workloads are compute-intensive, model training-heavy, or require burst capacity at unpredictable intervals, the economics of bulk capacity deals can be compelling. Run a pilot that captures total cost of ownership, including data movement, integration effort, operational overhead, and potential downtime during self-managed troubleshooting before you assume bulk is simply cheaper. Compare fully loaded costs, not GPU-hour sticker prices.

Build portability into your AI stack from the start. Bulk-capacity providers often lack the governance, compliance tools, and model life-cycle management enterprises need. Mitigate this risk by standardizing on containerized inference runtimes, open model formats, and CI/CD pipelines capable of deploying across multiple targets. This type of discipline turns vendor diversity into negotiating leverage rather than operational liability. It also ensures you can shift workloads as capacity markets fluctuate.

Treat capacity sourcing as a strategic procurement function. Bulk cloud capacity is not a niche quirk. It is becoming a recognized market that rewards supply-chain thinking. Diversify your supplier base, negotiate multi-vendor commitments where possible, and develop a reserve strategy for critical workloads. Keep your hyperscaler relationship for reliability and breadth, but maintain at least one secondary capacity arrangement for cost-sensitive or elastic workloads. The enterprises that treat capacity as a variable asset, rather than a fixed infrastructure decision will be better positioned as this market continues to expand and formalize.

The cloud market is no longer a simple fork between public and private. A defined middle ground of negotiated bulk capacity is now attracting billions in investment and reshaping how AI infrastructure costs are allocated. Enterprises that understand this landscape and build flexible, portable architectures that can span it will capture more value from AI investments than those who default to the familiar hyperscaler menu alone.

  •  
❌