INTERNATIONAL CODE COUNCIL

1. INTERNATIONAL CODE COUNCIL Building Energy Codes and Public Power Companies

2. Presentation Outline: • ICC Codes and Development Cycle • Code Adoption • I-Codes as the means to reduce energy use/ meet renewable /efficiency goals • New IGCC Green Code • Involvement

3. ICC Codes and Standards 14 Model Codes: I-Codes • Building: IBC, IRC • Fire: IFC, IWUIC • Fuel Gas, Mechanical, Plumbing: IFGC, IMC, IPC, IPSDC • Existing Buildings: IEBC, IPMC • Specialty: IECC, ICC Perf, IZC • Green: IGCC ANSI Standards include: • ICC/ANSI A-117, Accessibility • ICC/ANSI 700, Green Building • ICC Model Codes used • All 50 States • Federal Agencies- DOD, GSA, DOS, etc. • ICC is successor to ICBO, SBCCI, BOCA & CABO

4. Coordination of I-Codes • Defined scope of each code • Interdependence and reliance on the entire family of codes - cross referencing and duplication of provisions within code scopes • Issues resolved in a single and central public forum • Single interpretationapplies to all codes • Fully supported codes- not just code books

5. Development Process Goal Utilize a process open to all parties with safeguards to avoid domination by proprietary interests. ICC Governmental Consensus Process assures inclusive process, with the final vote reserved for those who enforce the codes. Meet policy and process needs of governmental customers

6. Code Committees • Materially affected interests represented • Not less than 33% of each committee is to be regulators • All meetings in public forum • All actions and reasons for action published

7. The Players • Code officials • Design professionals/consultants • Trade associations • Builders/contractors • Building owners/developers • Manufacturers/suppliers • Government agencies • Anyone with an interest

8. The Process • Open • Transparent • Balance of Interests • Due Process • Appeals Process • Consensus

9. The Procedures • All aspects of the ICC Code Development Process regulated by published procedures • Council Policy (CP) 28 – Code Development • Website link: • http://www.iccsafe.org/AboutICC/Documents/CP28-05.pdf

10. Code Changes Submitted Code Changes Printed & Distributed New Edition Published Code Development Hearing I-CODE DEVELOPMENT CYCLE Final Action Hearing Public Hearing Results Printed & Distributed Public Comments Printed & Distributed Public Comments Sought on Public Hearing Results

11. Steps 1,2&3 in a typical code change cycle • Next code changes due. 1-1-2012 Anyone can submit a code change • Staff review / Publish on website: • Approx. 90 days prior to Code Development Hearing • Code Development Hearing: • Anyone can attend, and testify. • No cost to attend the hearings. • All ICC members can vote in assembly action. • Report published 30 days following hearing

12. Steps 3&4:Public Comment & Final Action Hearing • Public Comments on Report of Hearing (ROH) – due approximately 45 days after ROH published. • Anyone may submit a comment. • Original code change with the committee action and assembly action (if any) (CHANGE HERE) • Public commentors requested action • Agenda published approx 60 days before Final Action Hearing • FAH- Anyone can attend and testify • No cost to attend • Only ICC Governmental Member Representatives can vote: those with responsibility to adopt or enforce codes- no proprietary interests.

13. Note on New Code Cycle Schedule -Previously, two cycles of approximately 18 months, between publication dates. -New schedule, one cycle, beginning in first year of publication date, with new editions published about a year ahead (2012 editions published in 2011)

14. By federal, state or local legislative or regulatory action and applicable in all areas covered by the action • Mandatory max/min • Mandatory with amendment allowed • Mandatory only if agency elects to adopt a code • By insurance, builder, utility, etc. action • As part of professional practice ethics Model Code Adoption

15. Implementation and Enforcement • By Federal, state or local agency charged with enforcement • Review and approval of plans, test data, calculations, etc. • Inspection of product manufacturing and testing • Inspection of building construction • By other entity such as utility or insurance carrier • Building owner, design professional, builder, contractor, manufacturer etc. is responsible to comply and provide verification of compliance

16. Compliance • Verification directly from the plans or through field inspection

17. Compliance • Verification based on testing, calculations and other evidence directly linked to specific criteria in the adopted codes and standards • Verification based on equivalent performance, as determined by approved specific computer software, compliance manuals, or worksheets that meet the intent of the code and standards

18. Code Content Drivers • Safety concerns of code officials and advocates • Simplified acceptance of technology / systems • Recent federal efforts to use codes to achieve policy goals • States set land use and construction regs • Local enforcement system largely in place

19. Energy Code- currently 2009 IECC • MEC renamed IECC in 2000 • 2003, 2006, 2009. • Referenced in EPACT, EISA, ARRA. • Referenced in HR 2454, S1462 • Kerry- Lieberman, Lugar also use

20. Why use the code to increase Energy Efficiency? • Existing infrastructure, acceptance & support mechanisms • Simpler adoption • Avoids Federal / State enforcement issues • Avoids complexity of drafting specific technical provisions • Allows for comparison w/ existing EE levels

21. Pending Federal Legislation & the energy code • All reference IECC for residential, ASHRA 90.1 commercial buildings • All set goals for higher EE, by percentage • “hammer” provisions if goals not met. • provisions to encourage / force adoption • “Renewables” legislation allows EE to meet goals

22. IECC Climatic Zones • IECC requirements vary by region. The regions are determined based on the climate • Each county in the country is sorted into one of the climate zones

23. New International Green Construction Code(IGCC) • Energy use efficiency • Water use efficiency • Materials and resource use • Indoor environment quality • Impact on environment (Greenhouse Gas/Carbon) • Site design • Sustainable building owner/facility management education • Existing buildings

24. IGCC Development Timeline • 2009: SBTC met five times in person, with several conference calls, and additional subcommittee mtgs, through January 2010 • Draft complete March 2010, agreement reached with ASHRAE • Public Comment period commenced March 15, comments were due May 14, 2010 • Hearings to review comments in Fall 2010, in Chicago. • Revised draft submitted for code development and final action hearings in 2011. Regular code cycle type hearings in 2011. • Published as 2012 IGCC

25. Opportunities for action…. • Now is the time to focus on technology: • Smart grid requirements • Peak /off-peak issues • Vehicle charging facilities • You know about these issues- propose changes to the codes • Code efficiency is predictable&permanent

26. Getting started • Work with your association • Get a committee going to review and draft • Make some proposals NOW, to affect 2012 IGCC, 2015 IECC • Simple way to make a BIG difference

27. Code Council information and updates ICC website at www.iccsafe.org David Karmol, VP, Federal & External Affairs at dkarmol@iccsafe.org