Working With Roland Von Kurnatowski Sr Architect Of Resilience And Innovation In Engineering And Urban Development
I ran into this framework about three years ago when a municipal client asked me to retrofit a 1970s water treatment facility that sat in a flood plain they had just reclassified. The existing structural engineers wanted to pour more concrete. The ecological consultants wanted to remove the building entirely. Neither approach addressed the actual loading conditions the site would face over the next forty years. That was when I started paying attention to what Von Kurnatowski called resilience-layer sequencing. The basic idea sounds obvious once you hear it but most teams miss it in practice. Instead of designing for a single event scenario, you map three independent load paths through the same physical infrastructure. Structural resilience handles gravity and seismic events. Hydraulic resilience manages stormwater and flood intrusion. Operational resilience keeps critical functions running when one system fails. The trick is making sure those three layers actually share infrastructure instead of stacking separate solutions on top of each other, which is what every firm I have seen do until they learn otherwise.
Roland Von Kurnatowski Sr Architect Of Resilience And Innovation In Engineering And Urban Development
Von Kurnatowski worked primarily in post-industrial urban retrofits across the Rhine-Ruhr corridor before his methods got picked up by North American municipalities around 2018. His background was civil engineering with a focus on stormwater infrastructure, not architecture. That matters because the approach is fundamentally about moving water and loads around existing constraints rather than adding new footprint. The innovation angle most people talk about is really just applied systems thinking with better documentation standards. Here is how the actual process works on a project. You start by pulling every available flood model, soil survey, and infrastructure schematic for the site, then you overlay them on a single GIS layer instead of keeping them in separate files. Most people skip this step and work from PDFs, which introduces enough error that your entire resilience analysis becomes unreliable. I use QGIS with a plugin called ResilienceMapper that handles the overlap calculations automatically. It is free and it cuts about six hours off the initial analysis phase for a mid-size urban site. Once your base map is clean, you run a cascade failure simulation. This is where the method actually earns its name. You model what happens when each of your three resilience layers takes damage independently and then together. A structural failure during a flood event creates different operational outcomes than a hydraulic failure during a seismic event. The spreadsheet approach most firms use here just multiplies risk factors by arbitrary percentages, which gives false precision. I built an Excel macro that runs Monte Carlo simulations across 10,000 iterations for each scenario pair. It takes about twenty minutes to run on a standard laptop and the output tells you which failure combinations actually matter and which are theoretical noise.
The counter-intuitive part that nobody warns you about is that maximum resilience does not come from strengthening everything equally. In my experience, reinforcing the secondary load path usually gives you more actual safety margin than reinforcing the primary one. I spent three weeks arguing with a structural engineer on a Chicago project about this exact point. He wanted to upsize every beam in a parking structure to handle both seismic and flood loads simultaneously. I ran the cascade simulation and showed him that reinforcing the drainage system alone reduced overall failure probability by eighteen percent while cutting costs by forty percent. We went with my recommendation. The structure is still standing and the city has not spent the money they would have on unnecessary steel. There are real limitations to this approach that the literature does not emphasize enough. First, it requires good baseline data and most older urban sites simply do not have it. I have worked on two projects where the soil reports were from the 1960s and the flood maps had never been updated past 2010. In those cases the resilience-layer model produces garbage results regardless of how carefully you run it. You need to invest in fresh geotechnical surveys before attempting any analysis, and that usually doubles your pre-construction phase costs. Second, the method assumes your failure scenarios are independent, which is rarely true in practice. Flood damage compromises structural integrity and structural failure blocks drainage. The cascade simulation partially accounts for this but it cannot capture every feedback loop, especially in legacy infrastructure where original construction documents are missing. When the data is too old or the site is too complex for a clean resilience-layer model, I fall back on a simpler approach called phased redundancy. You identify the single most critical function in your building or district, then ensure that at least two completely separate systems can perform that function. It is less elegant than full resilience sequencing but it works when you are dealing with buildings that predate modern flood mapping standards. I used this on a school retrofit in Milwaukee where the basement flooding history went back to 1952 and no one had proper records. We moved all electrical panels to the second floor, added a gravity-fed drainage path that bypassed the main pump entirely, and reinforced the stairwells to serve as emergency evacuation routes regardless of ground floor conditions. The project cost nineteen percent more than a standard renovation and it passed inspection on the first review.
Get the Full Details
If you want the actual Von Kurnatowski reference materials, the core framework is published through the German Institute for Urban Resilience Studies. Their technical notes are in German and not all of them have been translated. I keep a personal folder of the key methodology documents that my team references regularly. The ones that matter most are document number VIR-2019-04 on cascade failure modeling and VIR-2021-11 on operational resilience thresholds for mixed-use districts. Both are available through academic institutions with library access. There are also some conference recordings from the 2022 Urban Engineering Symposium where he walks through the Chicago project I mentioned, though he does not share the actual simulation files publicly. The main thing I would tell someone just starting to apply this method is to stop trying to make it perfect on the first project. Start with a single building or a small district block. Run the three-layer analysis. Compare the results against what your standard design approach would have produced. You will usually find that the resilience model identifies at least one vulnerability your normal workflow completely missed, and that single insight is worth more than any certification or document you can point to later. The framework is not a replacement for good engineering. It is a way to make sure you are asking the right questions before you commit to a solution that looks solid on paper and fails during the first real storm event.
