INTERNATIONAL CODE COUNCIL

1. INTERNATIONAL CODECOUNCIL The ICC Code Development Process

2. To promulgate a comprehensive and compatible regulatory system for the built environment, through consistent performance-based regulations that are effective, efficient and meet government, industry and public needs. ICC Mission

3. Each code is comprehensive All codes are coordinated and compatible with each other All codes are developed according to the same process in the same form All codes reference consensus national standards Characteristics of International Codes

4. 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 interpretation applies to all codes Coordination of I-Codes

5. Utilize a process open to all parties with safeguards to avoid domination by proprietary interests. Development Process Goal

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

7. Code officials Design professionals/consultants Trade associations Builders/contractors Manufacturers/suppliers Government agencies Anyone with a vested interest The Players

8. Open Transparent Balance of Interest Due Process Appeals Process Consensus The Process

9. Some of the slides which follow indicate iccsafe.org. This indicates that the information is available on ICC’s website at www.iccsafe.org. See the Codes & Standards/Code Development web page. Return coupons to receive hard copies of code change documents are also posted Website Information

10. The Procedures (iccsafe.org)

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

12. The following screen is an actual code change, as published in the 2001 Proposed Changes, indicating: Code Committee: IBC Fire Safety “FS” Code change number-cycle: “1-01” Code section affected: “702” Code change in legislative format Proponent’s reason Published Code Change

13. FS1-01 702 Proponent: Add new text as follows: SECTION 702 DEFINITIONS CURTAIN WALL ASSEMBLY. Either a rated or nonrated, nonbearing exterior wall assembly secured and supported by the structural members of the building. Reason: There is currently no definition in Chapter 7 for “curtain wall assembly” while the term is used in Section 712.4.Curtain walls …… Public Hearing: Committee: AS AM D Assembly: ASF DF

14. 16 Code Committees. Identified by code change prefix (“FS” in previous example) One for each code, except: IBC 4 Subcommittees IRC 2 Subcommittees Anyone can attend and testify. No cost to attend the hearings. Code Development Hearing

15. Committee action Approval as Submitted (AS) Approval as Modified (AM) Disapproval (D) Assembly action All members of ICC can vote in response to committee action Approved assembly action results in an automatic public comment Code Development Hearing

16. Committee action Assembly action Published Website: Approx. 30 days after hearing Published: Approx. 60 days after hearing Report of Hearing

17. The following screen is the published Report of the Hearing on Code Change FS1-01, indicating: Committee Action: “Disapproved” Committee Reason Assembly action: “No motion”, indicating no one made a motion for the assembled ICC members to consider Published Report of the Hearing

18. FS1-01 Committee Action: Disapproved Committee Reason: The proposed definition is too broad. Thisdefinition would include basically all exterior walls with the exception ofbearing walls. The definition in ASTM 631 only includes the first sentence of the proposed definition. Assembly Action: No Motion

19. Public Comments on Report of Hearing – due approx. 60 days after ROH published. Allows anyone to submit a comment in response to the results of the hearing: Agree/disagree with the committee action Agree/disagree with the assembly action Further revisions (“modifications”) to changes are permitted Heard at the Final Action Hearing Final Action Agenda

20. Comments published and serve as agenda for the Final Action Hearing Website: Approx. 45 days after deadline Published: Approx. 75 days after deadline Final Action Agenda

21. Hearing: Approx. 45 days after Final Action Agenda published Voting: Consent agenda: Block vote on all code changes which did not receive a public comment or successful assembly action Individual Consideration Agenda: Vote individually on each code change which received a public comment or successful assembly action Final Action Hearing

22. Anyone can testify. No cost to attend. Final vote on whether or not to change the code rests with the “Active” Governmental Members – those who enforce the code and are charged with the public’s safety Open, fair and objective with no proprietary interest Final Action Hearing

23. Edition - every 3 years: Intervening Supplement between Editions. First edition in 2000 2003 Edition 2003/2004 Cycle: 2004 Supplement 2004/2005 Cycle: 2006 Edition Continue Results of Code Development

24. Debut at 2002 Code Development Hearings Followed up in all subsequent hearings Streaming video and audio Internet access on your PC Currently testing remote voting capability See next slide for a PC view Webcasting(iccsafe.org)

25. The ICC remains dedicated to a single family of comprehensive and coordinated model codes. The ICC process allows all interests to participate in the code development process. Conclusions

26. For those proposals for which consensus is not achieved at the Code Development Hearing, the final decision rests with those with no vested interest other than health, safety and welfare…………. THE GOVERNING AUTHORITY WHO ADOPTS AND ENFORCES THE CODE Conclusions

27. If you are interested in code changes submitted in previous code development cycles or the current cycle, be sure to go to the website. All this info is posted. Questions?: Call ICC’s Codes & Standards Development Department 800-323-1103 X 340 Additional Info

28. 3 Tier Inspection Process (1) Inspection by Building Official (Sec 109) (2) Inspection by Qualified Special Inspector (Sec 1704) (3) Structural Observation by Registered Design Professional (Section 1709)

29. Structural Tests and Special Inspections Chapter 17

30. What’s Important in Chapter 17

31. What’s Important in Chapter 17

32. What’s Important in Chapter 17

33. What’s Important in Chapter 17

34. 1. GENERAL REQUIREMENTS Identification Card Ability to read plans/specifications Knowledge of Codes & Standards Ability to Write Inspection Reports REGISTRATION/QUALIFICATIONGUIDELINES

35. 2. EXPERIENCE Verifiable Work Related to Category Sought College/Engineering Technology Degree On - the - Job Training Prior Experience as inspector Certification in Related Work REGISTRATION/QUALIFICATION GUIDELINES

36. Special Inspector Qualifications • Written Examinations • Oral Interviews • Review of Relevant Education • Review of Relevant Experience

37. EDUCATION / REGISTRATION Courses, Seminars, Workshops Apprenticeship Programs Community College/Vocational-Technical University or College Degree Registrations/Certifications Special Inspector Education/Registration/WorkExperience Evaluation

38. Inspector Field Experience Understanding Inspector Duties Understanding Inspector Responsibilities Understanding Inspector Ethics Understanding Codes and Standards Understanding Testing Procedures Special Inspector “Interview” Evaluation

39. Enforcement/Quality Control For Quality People How to Set Up a Special Inspection Program

40. YOU MUST GET INVOLVED Special Inspection Program

41. Agency Qualifications How to Set Up a Special Inspection Program

42. Agency Name Contact Name/Title Address Telephone/Fax Business Type Quality Assurance Inspection and/or Testing Agency Application Process

43. Organization of the Agency Organization History Organization Charts and Functions Technical Services Human Resources of the Agency Material Resources of the Agency Quality Assurance Inspection and Testing Agencies

44. Quality Systems of the Agency Approval Review Audits Quality Assurance Plans Reports Final Reports Quality Assurance Inspection and Testing Agencies

45. CODES INTERNAL STAFF SPECIAL INSPECTIONS TECHNOLOGY CLARK COUNTY

46. PERFORMANCE CODE • Concept Report • Design Report • Operations & Maintenance Manuals

47. New products end up in construction projects, requiring approval by the code official. Adopted codes and standards tend to lag behind new technology development and deployment. It can be difficult for building departments to determine if new building products and materials meet minimum building code requirements. Both the IBC and IRC contain performance provisions for the use of alternative products. New Product Technology

48. Code Basis for Alternative Products Alternative Materials and Products: IBC Section 104.11 provides the code official with a means to accept the use of any material or product not specifically prescribed in the code.

49. Code Provisions for Acceptanceof Products/Technology IBC Section 104.11: Alternative materials, design, and methods of construction and equipment: “The provisions of this code are not intended to prevent the installation of any material or to prohibit any design or method of construction not specifically prescribed by this code, provided that any such alternative has been approved.”

50. Code Provisions for Acceptanceof Products/Technology IBC Section 104.11.1: “Research reports from approved sources may be accepted by the building official as supporting data to assist in the approval of materials or assemblies not specifically prescribed by the code.” It is up to the building official to determine which “research reports” will be used to approve products.