Grant Lobdell is back on the show at a moment when the whole industry is paying attention. The fire at Gabriel House in Fall River, Massachusetts put a hard question in front of every contractor: how do recalled sprinkler heads stay in buildings for decades, and whose job is it to catch them? Grant runs the lab side of Dyne Fire Protection Labs, now an NFPA Global Solutions company, and his answer starts with an honest observation: contractors handle the routine work well. It's the tests that come due 20 or 50 years after install that fall to the wayside. Dyne's whole stance is that the easier the test is to do, the more likely it gets done. From there the conversation goes inside NFPA 25. Grant walks through how testing intervals actually get set and why they keep changing edition to edition: dry sprinklers moving from 10 to 15 to 20 years as failure-rate data came in, quick response intervals stretching as the technology proved itself. The committee isn't trying to make life difficult. The intervals are a data-driven decision, and the data keeps moving. Then the hard part. Recalled O-ring sprinklers are not specifically called out in the standard today. As Grant puts it, if you hand him an O-ring sprinkler and it passes the test, it technically meets the standard, even though the failure rate says otherwise. He expects that to be a hot button in the next revision cycle. The codes, as the saying goes, are written in blood. The back half is a live walkthrough: how Inspect Point structures sprinkler head data down to the individual head, tracks the right test frequency for whatever NFPA 25 edition each building is on, projects what's coming due across every building in a portfolio, and submits heads to Dyne for testing in a couple of clicks. Grant's team sends a kit, you fill the box, and the lab report lands in your inbox.
Drew brings two of Inspect Point's own onto the show this time: John Ryan, a senior solution engineer who came up through the product and engineering side, and Jimmy Snowden, who leads the support team and spent years as a technician and inspection manager before joining the company. If you've caught their monthly customer session, "Coffee with Jimmy and John," this is the same back and forth, now for the industry at large. The heart of the conversation is data. Everybody is talking about AI, but Jimmy and John make the case that the payoff depends on what you capture and how. Plenty of companies record building data. The advantage shows up when you capture clean, standardized data at the system and asset level: manufacturers, model numbers, recalls, test dates, how an asset has performed over time. Lock that in and you can ask real questions, like how many buildings had an extinguisher that wasn't inspected last year, and start making projections instead of digging through PDFs and spreadsheets that were never built to be searched. From there they get into the new features built on that system and asset model: fully custom question sets, components and attributes you can take as granular as you want, barcoding down to an individual cylinder or valve, fire pump curves, and the AI agents on the way. The back half turns to codes and compliance. John talks through healthcare and the Joint Commission's January 2026 change that simplified fire-safety documentation, and why a transition everyone braced for went off quietly. Jimmy walks through the 2026 edition of NFPA 25, including a residential sprinkler head testing gap he spotted and ran past CASI, NFPA LiNK's AI assistant. And he closes with a sharp theory on why NFPA 25 is the most complex standard in the trade: a sprinkler system is full of water, and water can destroy property the same way fire can, so you're protecting against both. Join Drew, John, and Jimmy for a real look at where fire protection data, AI, and the codes are all heading. Topics covered: "Coffee with Jimmy and John" and how it started Why no two fire protection companies do the job the same way How fire protection differs from other trades: each system, its own code Why system and asset data, not just building data, is what makes AI useful Custom question sets, components, attributes, and barcoding everything Putting AI to work: prompts, projections, and agents on the way Healthcare and the Joint Commission's January 2026 change Inside the 2026 edition of NFPA 25 and a residential head testing gap Why NFPA 25 is so complex: protecting against fire and water 0:00 What's in this episode1:44 Getting John and Jimmy on the mic2:16 Meet John Ryan3:33 Meet Jimmy Snowden4:27 Favorite systems: dry systems and valves5:32 "Coffee with Jimmy and John," their monthly customer session10:13 No two fire protection companies are alike11:07 Why fire protection is different: each system, its own code14:13 The real AI unlock is system and asset data15:28 New features: custom question sets, components, and barcoding17:48 Putting AI to work: prompts, projections, and agents23:50 Healthcare and the Joint Commission24:24 The January 2026 change that simplified documentation31:16 Inside the 2026 edition of NFPA 2532:12 The residential head testing gap (and asking CASI)34:22 Why NFPA 25 is so complex: fire and water36:15 Wrap-up
Shawn Mahoney of NFPA's Technical Services team joins Drew for his fourth time on The Fire Protection Podcast, and this one covers a lot of ground before landing on a problem the industry keeps stepping over: construction-site fires. You've seen the headlines. A light wood-frame building goes up mid-construction, and the whole thing is gone, like the Denver complex that took a 238-unit building with it, or the South Park fire in North Carolina that killed two workers. Shawn's point is blunt: we already have the standard to prevent this. It's NFPA 241, the Standard for Safeguarding Construction, Alteration, and Demolition Operations, and it's been around since 1930. It's referenced by NFPA 1, NFPA 101, the IBC, and the IFC. "The biggest issue is people just aren't using it," Shawn says. The code isn't broken. Enforcement is. Drew and Shawn dig into why adoption is so piecemeal, what real enforcement looks like (Boston shuts a site down if the fire prevention program manager isn't there), the legislative push after the North Carolina fire, and what the Fire Prevention Program Manager actually has to do day to day. Before that, they preview the NFPA Conference & Expo in Las Vegas, including Drew's Tuesday session on AI and fire protection, how AI has reshaped the codes world through NFPA LiNK, CASI, and the new Notebooks feature, and why data centers and small nuclear reactors are creating fire-protection problems in towns that have never seen anything like them. Join Drew for Episode 96 for a real conversation about why the standards we already have only matter if someone enforces them. Topics covered: Inside the NFPA Conference & Expo in Las Vegas AI in fire protection: NFPA LiNK, CASI, and NFPA Insights LiNK Notebooks for codes, checklists, and impairment permits Data centers and small nuclear reactors as emerging fire risks Light wood-frame construction fires and why they're catastrophic NFPA 241 and the enforcement gap The Fire Prevention Program Manager role Timestamps 00:00 – Introduction 02:27 – Inside the NFPA Conference & Expo 05:35 – AI in Fire Protection 07:46 – Data Centers & Small Nuclear Reactors 09:13 – NFPA LiNK, CASI & NFPA Insights 12:00 – LiNK Notebooks 15:21 – NFPA 241: A Standard Since 1930 16:50 – Why Wood-Frame Construction Fires Are Catastrophic 19:07 – Referenced Everywhere, Enforced Almost Nowhere 20:36 – How Boston Enforces 241 25:54 – The Fire Prevention Program Manager Role 28:33 – Educational Videos & NFPA's YouTube Channels 30:23 – Conclusion
Levi Rock got laid off for three weeks when COVID hit, and it changed how he thought about job security. In 2020 he started Red Seal Fire Protection in Windsor, Ontario, and grew it to 17 employees in five years by keeping it simple: show up when you say you will, turn reports and deficiency quotes around within 48 hours, and get out of the way so customers never have to think about their fire protection. In this episode, Levi joins Drew Slocum to talk about building a service-first fire protection business. They cover the recurring-revenue membership model behind it, why he says no to most new-installation work, how Red Seal uses social media to educate property managers and recruit fitters, and how Inspect Point replaced their PDF forms with consistent, faster reporting. They also get into the gap between NFPA 25 and the Ontario Fire Code, why contractors and AHJs need to communicate more, and why human expertise still beats generic AI on fire code. Episode #95. The Fire Protection Podcast, powered by Inspect Point. Timestamps: 00:00 Intro 01:31 Welcome and why Levi's on the show 02:56 From sprinkler fitter to founder during COVID 07:50 The edge: speed, communication, 48-hour turnarounds 11:30 Moving off PDF forms to Inspect Point 13:35 Capturing asset data to power AI tools 15:42 The membership model and predictable budgets 20:02 Marketing fire protection and recruiting techs 23:32 The AI content problem and fire code accuracy 25:54 The fire protection education gap and training AHJs 28:34 NFPA 25 vs the Ontario Fire Code (and ULC 536/537) 33:11 Training the next generation 34:13 What's next for Red Seal 37:19 Wrap-up
Ray Fremont Jr., president of General Air Products, joins Drew to talk about the air supply side of dry pipe sprinkler systems. General Air Products has been building air compressors for fire sprinkler systems since the 1960s, and the Fremont family has been in the compressed air business since the 1930s. Ray covers how dry system air supply has changed over the last century: plant air compressors and schedule 40 pipe, the shift to thin-wall steel, nitrogen generators, and a newer vapor corrosion inhibitor technology called Vapor Pipe Shield that creates a molecular barrier on the inside of the pipe. They also dig into some real problems: most dry systems leak well beyond what NFPA 25 allows, jurisdictions are a decade behind on code adoption, and air compressor maintenance still gets skipped. Ray previews a new digital monitoring device that tracks compressor cycling and flags system issues before they turn into failures. It's the kind of predictive data the sprinkler side has never had.