Introducing CodeCalls.org: A Free Database

4/9/2020

Today is a very big day for me. I am finally launching the start of an idea I've had and brainstormed and discussed and revisited for a number of years now.

Finally. I could not be more excited about it.

Ever since the COVID-19 pandemic began impacting the world around us I've been pressed to rethink my own operations and what I'm contributing to the world. Articles, design content, PE Prep, and trying to find ways to help the knowledgebase of the fire protection community is good, but I started the website around the idea of impacting the community in a real and tangible way.

Today's new project is the start of what I hope could be a major positive impact for AHJs, designers, and installers.

What is it? A Code Call Database.

What is CodeCalls.org?
CodeCalls.org is a free website that is bringing together local jurisdictions, fire protection designers, engineers, and installers to clarify and collaborate local code requirements.

We're taking the areas of code in fire protection design that need local input, and helping jurisdictions get what they need to help first responders do their work.

When we're done, we plan to have a searchable, filterable database where you can find local requirements based on a project's ZIP code, city or county name.

Where to Start? Indiana!
There tens of thousands of jurisdictions in the United States alone, how is all this data going to come together?

First, we're starting with our test case. If you work in the State of Indiana or have contacts who do, pay close attention today.

Our Goal is to gather jurisdictional requirements for 70% of Indiana's population by May 8th. That's in 30 days.

Why Indiana?
Indiana has a healthy mixture of urban, suburban and rural jurisdictions, so it presents a great test case to validate the concept. If we get enough momentum for Indiana, we feel confident in pursuing the project for larger coverage.

If we find that we can get enough momentum to clarify requirements for Indiana, then we feel that the project could be viable to expand to new areas beyond Indiana and beyond just the United States, too.

Why a 70% Coverage Goal?
In order for the database to work, the user experience has to be great. Both for jurisdictions and for designers & installers. We feel that if we can cover jurisdictions that account for at least 70% of the area's population, that we'll have enough data for a great user experience and a very helpful resource.

Is it Free?
Yes, the database will always be free for anyone to access. We're funding the development efforts as a joint project by MeyerFire.com and BuildingCode.Blog.

Why Should I Help?
If you're an engineer, designer or installer, why should you contribute?

For one - this is a way to clarify local requirements that will help in more fair and consistent bidding.

Second - we'll thank you by crediting your contribution with a link from the local listing directly to your company's website. If someone is looking for a local contractor or design outfit, they can search a ZIP code and immediately have contact information to you, the person who they know is already familiar with the local requirements.

If you're a jurisdiction, why should you contribute?

Simple - get your needs met. Are you tired of providing the same plan-review comments? Tired of answering the same basic questions in phone calls and emails? This platform is an easy way to clarify the gray areas of code and simply make your requirements more clear to those who are seeking them.

I Have Some Information for Some Areas in Indiana. How Can I Help?
You can contribute information for jurisdictions you're familiar with here. We'll thank you with a promotional link to your company's website and help get the information verified by the jurisdiction.

See The New Site!
Click here or the link below to check out the new project. Let us know what you think by commenting or emailing me at joe@meyerfire.com. Would love to hear feedback on how we can make this helpful and accessible.

SEE THE CODE CALL PROJECT (CODECALLS.ORG)

Wayne Ammons

4/9/2020 09:34:30 am

This is GREAT stuff and something I know we could use here in Florida and the many jurisdictions we do work in across the country. Consider it bookmarked!

Perspective

4/9/2020 12:29:46 pm

I love a lot of what Meyerfire does but I feel like local AHJ requirements and interpretations are almost proprietary information to qualified contractors. It takes a lot of time and effort to gather information and to build relationships with AHJs. A large part of being a reputable contractor is having clients count on you to get the work done correctly the first time because they trust you to know and understand the application of codes and standards. If you dont know how to find local codes you probably shouldnt be designing fire sprinkler systems. It takes time because due diligence is important. I feel like this could unintentionally enable unqualified people to access information that they dont know how to apply (which is why many AHJs dont publish their information like this and require NICET or PE approvals on submittals). Local companies could be impacted by this because most local companies have relationships with building owners and care about their future needs and ITM considerations. Larger traveling companies come in and undercut costs because there is no relationship and they dont care about the future needs of the client (we've all seen systems like this). In terms of "area contractor" in the chart, there are areas of the county that have hundreds of licensed contractors. What would the criteria be for the listing on your site? This sounds great for big business and not so great for local relationships. I'm not saying you shouldn't continue with your project and it sounds like you have good intentions but I wanted to offer another perspective from a local contractor point of view. Im also not involved on the A/E level so it could be different, but a lot of contractors in my area tend to hold on to this information for their own use. This might be unique to my area since we have so many unique AHJ requirements so I would love to hear from others on the contractor level.

Joe Meyer

4/9/2020 12:47:53 pm

I agree on a lot of fronts - and I might be able to help clarify the intent a little.

The nuances of plan review, installation and inspection that each local jurisdiction approaches differently isn't really our goal for this site.

The goal is centered more on the coordination side of design and code information. Things like hydraulic safety factors, FDC types, hose connection locations, or links to local amendments would be good examples of basic requirements that would be sought on the database. We're not looking to discuss grievances or expose all the nuances of working in each jurisdiction.

The relationships any one contractor has with the local authorities or the knowledge each contractor has for working in their area really wouldn't (in my opinion) be impacted by this much. It could however help the design team the contractor has when they're working among different jurisdictions.

As far as limitations on defining "area contractor", we'll think on that as a team. The verbiage is flexible, but we're just looking to thank the contributors even if in a small way.

The biggest emphasis I would have is that we're looking to help with this tool. None of the information provided is mandatory by any stretch - and in a best case scenario most if not all of the information is provided by or validated by the jurisdictions themselves, not just contractors or design groups.

Hope this helps, as always feel free to email me at joe@meyerfire.com if you might have ideas on how we could help and not hinder your work. Seriously - the goal is to do good here.

Anon

4/13/2020 10:48:47 am

As an AHJ, who has relationships with small, medium, and large contractors, I'm missing your point here and I want to openly admit that is because I have never been a contractor and do not understand the business side of it. I can also only speak from what I see in my own jurisdiction In California. I understand things could be completely different in another state or even a different part of my own state.

Having said that, as an AHJ in one county and a member of the community in another county, I am all for spreading code knowledge. Telling a contractor they either made it up or they have a stricter ordinance in response to why does the city 5 minutes south of you have different requirements never feels good. Any decent sized jurisdiction or jurisdiction with good enough staffing should have their Fire Ordinance somewhere on their website.

In my experience, most of the stricter requirements found in our ordinance do not affect smaller or even medium sized contractors. They actually affect the developers building large buildings from the ground up. Sure there are some details here and there that every level contractor has missed or will miss because every AHJ is different, but those are not exactly red flags to me because 8 out of 10 contractors/developers did not read the ordinance or skimmed it quickly. The red flag is the contractor missing it on the 3rd resubmittal and then sending me an email asking for a 3rd explanation.

Anyways, I just wanted to say thanks for all the amazing content here and I look forward to this being a success. Another added benefit of this is making it easier for AHJ's to look at what everybody else in the state is doing and talking about why we should or shouldn't be doing that.

Comments are closed.

Introducing CodeCalls.org: A Free Database

ALL-ACCESS

SUBSCRIBE

AUTHOR

FILTERS

ARCHIVES