PF Nav/HeadImage

PennFuture Facts :: brief, interesting looks at topical environmental issues PennFuture Facts :: brief, interesting looks at topical environmental issues
Showing posts with label RAC. Show all posts
Showing posts with label RAC. Show all posts

Wednesday, February 19, 2014

Fox guarding henhouse: New email emerges -- Are builders calling shots on building codes, safety?

With little scrutiny, Pennsylvania has outsourced the vital role of updating building safety codes to the very people who stand to be regulated – the building industry.  Specifically, the Pennsylvania Builders Association (PBA) – a powerful, well-connected industry group representing residential builders throughout the state—has almost complete control over whether Pennsylvania’s building codes will be kept current. This cannot continue.  

The Review and Advisory Council (RAC) is a little-known panel of Governor-appointees that decides whether to update building codes. Changes to the building code update process, signed into law as Gov. Corbett's first piece of legislation after taking office, require a supermajority vote of the RAC to update codes -- allowing for six RAC members to stand in the way of updated building codes. Currently, PBA holds, or has influence over, at least six members of the RAC.

A former president of the PBA has always sat on the RAC, and was (until last month), the Chair.  

Even more shockingly, through a Right-To-Know Law request, PennFuture discovered that long-time Pennsylvania Builders Association attorney Loudon “Hap” Campbell provided “legislative drafting” advice to RAC Chairman Frank Thompson and a RAC subcommittee. The advice apparently pertained to the RAC’s official comments on pending code adoption legislation.  

Why is the chairman of the RAC receiving legal advice pertaining to the RAC’s official comments on legislation from an attorney and lobbyist who has represented the PBA in cases spanning twenty five years, who is listed on PBA’s website as “PBA’s legal counsel,” and is listed on FollowTheMoney.org as a PBA lobbyist as recently as 2012?  

Stephen Black, another former president of the PBA, has been appointed by Gov. Cobett to replace Mr. Thompson. What will stop this too-cozy practice of insider influence by the PBA?   

Last summer, several bills were introduced to fix the broken codes process and remedy the undue influence of the PBA over the RAC’s decisions. However, the PBA was successful in amending the legislation to retain the existing system that makes building code adoption impossible without the PBA’s blessing.

The RAC should be comprised of a broad range of stakeholders and building code experts. Builders should have a say in the process, but Pennsylvania cannot continue to abdicate its regulatory authority to an industry group to the detriment of the safety and welfare of Pennsylvania's citizens. Only bringing to light PBA's undue influence, and legislative change to make the code adoption process more effective, will ensure that Pennsylvanians have the benefit of a thoughtful and balanced review of building codes.  

Andrew Sharp is PennFuture's Director of Outreach and is based in our Philadelphia office.

Wednesday, January 22, 2014

Will Pa. Senate water down strong building codes bill?

We've told you before about the building codes mess in Pennsylvania. 

In short: Changes to the building code update process, made by the state legislature and Gov. Corbett in 2011 -- at the behest of the home building industry -- are preventing updates to building codes. 

This means that cost-effective industry best practices are being rejected at the expense of health, safety and energy efficiency.

Early next week, the Senate Labor and Industry Committee is expected to vote on a bill that attempts to fix this broken codes process. 

Sen. Charles McIlhinney's bill would streamline the process by restoring Pennsylvania to a system where updated codes are adopted unless a two-thirds majority of the Uniform Construction Code Review and Advisory Council (RAC) votes them out (referred to as the "opt-out" process). 

This would allow for hundreds of commonsense, often simply semantic, code changes to take effect, while allowing for substantive analysis on proposed changes that merit debate. 

It would go a long way toward addressing the dysfunction and delay in the current code process. 

BUT, amendments are very likely to be introduced that would gut the bill of its core function. 

Amendments that have been widely shared with stakeholders remove McIlhinney's key "opt-out" provision. 

If similar amendments are introduced early next week, the watered down bill would fail to address the fundamental flaw of the current code process and Act 1 -- the requirement that the RAC reach two-thirds consensus on hundreds of proposed code changes. 

The amended bill would amount to tinkering around the edges, while the safety and welfare of Pennsylvanians remains at risk because of out-of-date building codes. 

Take action!
Use PennFuture's action alert and tell the Senate to stand up for the safety of Pennsylvanians, not the interests of home builders -- and pass SB 1023 unamended. 


Andrew Sharp is PennFuture's director of outreach and is based in our Philadelphia office.

Thursday, September 26, 2013

Home builders: Slow, dysfunctional building code process is A-OK

On Tuesday, the Senate Labor and Industry Committee held a hearing on Sen. Charles McIlhinney's bill that attempts to address the dysfunction in the state's building code adoption process.

The McIlhinney bill would return Pennsylvania to a process whereby codes are automatically adopted unless two-thirds of the members of the Uniform Construction Code Review and Advisory Council (RAC) vote to reject them. Equally critical, the bill would force the RAC to re-review its decision to reject all of the 2012 International Construction Code (ICC) updates.

At the hearing, there was unanimous consensus that Pennsylvania's building code adoption process needs to be fixed. What the appropriate fix is, well, that was the source of great debate -- and will determine whether Pennsylvania has safe, well-constructed, energy efficient buildings or if the state's building codes lag behind and remain out of date.

According to RAC Chairman Frank Thompson and the Pennsylvania Builders Association (PBA) -- the latter an influential interest group of home builders -- the answer is simple. Fix an already slow, dysfunctional, process by making it glacially slow.

After choosing not to adopt any of the hundreds of common-sense code updates in 2012, their solution is to put off making any new code decisions until 2016 -- by changing the code adoption cycle from three to six years. Senator McIlhinney, a Bucks County Republican, described this solution as "ridiculous." [Hint: He's right.]

McIlhinney's proposed fix: Streamline the process by restoring Pennsylvania to a system where updated codes are automatically adopted unless a two-thirds majority of the RAC votes them out. People in the know call this the "opt-out" process. This would allow for hundreds of common-sense (often, simply semantic) code changes to take effect, while allowing for substantive analysis on proposed changes that merit debate.

Equally important, it would mandate that the RAC do its job and re-examine the 2012 code changes. In 2012, the RAC failed to perform the required analysis for code changes and, inconsistent with the law, arbitrarily voted not to adopt any of the 2012 codes. Hundreds of changes to the building codes recommended by the ICC were summarily rejected. These rejected changes include building and safety improvements in addition to updated energy efficiency standards.

Pennsylvania Builders Association (PBA) representative Joe Mingioni, who was also on the RAC in 2012 when it rejected the updates, admitted as much at Tuesday's hearing. He said that the decision not to adopt any new codes in 2012 was a "policy statement" rather than a decision against each code update on its merit.

The former RAC member's moment of candor -- admitting that the group failed to follow the analysis requirements of the law and instead rejected each and every code update in a policy statement  -- begs a couple key questions: What would prevent the RAC from making another policy statement in 2016 and again dismissing all code changes? Why is it reasonable to assume that 19 political appointees with no staff could possibly analyze hundreds of code changes and reach a two-thirds majority on each?  Why has Pennsylvania decided to give so much regulatory authority to an unelected, industry-dominated advisory committee, rather than keeping the final say with the Department of Labor and Industry?

One suspects that the RAC as currently constituted will never meet a set of code changes it likes -- and codes in Pennsylvania could remain anchored in 2009 since it will always be easier for the RAC to take no action than to reach a two-thirds consensus. (This theory was borne out in 2012.)

PBA's Mingioni also complained that "special interests" (read: manufacturers of energy efficiency products) were driving the attempt to fix the RAC process. We'll let that sink in for a moment...a powerful and well-connected special interest group standing in the way of progress is complaining that special interests are trying to change the process. Pot, meet kettle. If any special interest has a strangle-hold on the process, it's the home builders and their allies.

By the way, the number of energy efficiency representatives on the nineteen-member RAC? Zero.

If you support safe and energy efficient buildings in Pennsylvania, visit BuildItSafe.org and take action.