• E-Mail: [email protected] AGENDA · Agenda – NEII Central Code Committee January 28-29, 2009 3 9. Use of Elevator in Fires and Other Emergencies. (a) NEII Position. Click on the

National Elevator Industry, Inc. ASSOCIATION HEADQUARTERS 1677 County Route 64 • P.O. Box 838 • Salem, New York 12865-0838 • 518.854.3100 Fax: 518-854-3257

CODE & SAFETY OFFICE 47 Leicester Street • Perry, New York 14530 • 585.302.0813 Fax: 585.302.0841

WWW.NEII.ORG • E-Mail: [email protected]

AGENDA

NEII CENTRAL CODE COMMITTEE

January 28-29, 2009

The NEII Central Code Committee meeting will take place January 28-29, 2009 at:

Schlindler Elevator Corporation 20 Whippany Road

Morristown, New Jersey 07962-1935

See Attachment #1 for hotel information.

The meeting agenda is as follows: 1. Call to Order – 2:30 p.m. [CodeFinder Editors’ Meeting in the morning] 2. Record of Attendance. 3. Announcements.

Vincent Robibero has indicated he will not be in attendance at the meeting (Attachment #2). 4. Election of Chairman. 5. Adoption of Agenda. 6. Approval of October 29-30, 2008 Minutes. 7. Personnel.

Please see Attachment #3 for a copy of the NEII Central Code Committee roster. Members are requested to advise Brian Black of any corrections that should be made.

Agenda – NEII Central Code Committee January 28-29, 2009

2

8. NEII CodeFinder.

(a) Status Report from Members on Company Assignments (Attachment #4).

Members are reminded the NEII Local Code Regulation Database Policy (Attachment #5) states: “CodeFinder is to be maintained up to date with current Codes and regulations. At a minimum on the 15th of January, April, July and October, the responsible company shall review and update CodeFinder local Code information.”

(b) NEII CodeFinder Open Feedback (Attachment #6). (c) NEII CodeFinder Help Update (Attachment #7).

(d) CodeFinder Editor Training PowerPoint.

The committee agreed to split the training between members, each of whom will develop a PowerPoint segment on his assigned topic. The topics follow the “Help” feature in CodeFinder: 1. Adding jurisdictions – Vincent Robibero [Amzad Malique] 2. Adding agencies – Vincent Robibero [Amzad Malique] 3. Adding contacts – Phil Hampton 4. Adding codes – David McColl 5. Code modifications – David McColl 6. Update existing code modifications – Joe Busse 7. Code modifications – Hold code modifications – Andy Juhasz 8. Rollovers – Andy Juhasz 9. Feedback –Phil Hampton Committee members will report on the training provided at the CodeFinder Editors’

January meeting. (e) CodeFinder Auditing (Attachment #8).

The committee will establish a CodeFinder Auditing Team comprised of CodeFinder Editors and two or more committee members. (f) CodeFinder Management Report Outline (Attachment #9).

(g) Other Issues.

The committee will discuss contracting maintenance of CodeFinder with an outside entity (e.g., Stateside). A proposal to the NEII Board of Directors should be developed with the assistance of Brian Black and Edward Donoghue.


3

9. Use of Elevator in Fires and Other Emergencies.

(a) NEII Position.

Click on the following link to access NEII Position on the use of Elevators in Fires and Other Emergencies, http://www.neii.org/members/committees/20/.

(b) ASME A17 Emergency Operations Committee Task Groups on Use of Elevators in Fires and Other Emergencies – David McColl. (c) February 2009 Workshop on Emergency Preparedness for Persons with Disabilities and Special Needs (Attachment # 10) – Brian Black.

10. NEII Long Range Plan for Codes and Standards.

For a copy of the current Long Range Plan for Codes and Standards, click on the following link, http://www.neii.org/members/committees/20/.

11. Alternative Technology – Louis Bialy.

(a) ASME A17.7/CSA B44.7Adoption.

(b) AECOs.

12. Accessibility Issues. (a) ADA/ABA AG (ADAAG) – Brian Black.

(b) ICC/ANSI A117.1 – Brian Black.

(c) CSA B44, Appendix E - David McColl.

13. Local Elevator Code Issues.

(a) Model Elevator Law.

For a copy of the latest Elevator Law Activity File click on the following link http://www.neii.org/members/committees/20/index.cfm.

(b) California - Steve Grainer and Joseph Busse. The committee will discuss the response from Paul Puno to its letter regarding Static Control Testing (Attachment #11).


4

(c) Chicago - Andy Juhasz. (d) Illinois - Andy Juhasz.

(e) Other Jurisdictions.

14. ASME QEI – Louis Bialy and Brian Black. 15. Seismic Activities – Louis Bialy.

(a) Seismic Task Group Report.

(b) ASME A17, BSSC and ASCE 7.

16. Electrical Codes.

(a) National Electrical Code® - Andy Juhasz.

(b) Canadian Electrical Code - David McColl.

17. Building Code Activities.

(a) ICC - Brian Black. (b) NFPA 101/5000 (Attachment #12) – Brian Black.

(c) National Building Code of Canada - David McColl.

18. ISO Activities – Louis Bialy. 19. Codes and Standards Document Library – Brian Black.

20. NEII Area Code Committees – Brian Black. (a) Vacancies: NEII Area Code Committee Personnel (Attachment #13).

(b) Area Code Committee Chairs.

21. ASME A18 Committee – Brian Black. 22. NEII NOW Articles.

The committee will identify authors for articles in the next two editions of NEII Now.

23. A17 Outside Emergency Elevators Committee – Brian Black and Louis Bialy.


5

This committee has proposed that the ASME A17 TG continue its work and consider changing the language to merely define and scope Outdoor Evacuation Elevator in the ASME A17.1/CSA B44 code, then specify compliance with ASME A17.7/CSA B44.7 for the specific technical requirements for these devices. From the TG draft Scope: This section applies to elevators operating on the outside of the building that are used for emergency evacuation of building occupants and for building access by emergency personnel. Louis Bialy and Brian Black will report on the results of the January 21, 2009 meeting of the A17 committee.

24. ASME A17 Maintenance Code Issues – David McColl. 25. International Mutual Recognition Agreements and Meeting with European Lift

Association – Louis Bialy. The Global Elevator Industry Commitment to Global Technical Barrier-Free Trade is located on

the committee website at http://www.neii.org/members/committees/20/. 26. NEII/PALEA/JEA Meeting - Louis Bialy. 27. ASME/NEII Liaison - Louis Bialy.

28. Local Code Interpretations Policy (Attachment #14) –Steve Grainer.

29. CSA Technical Information Letters (TIL) – Brian Black (Attachment #15 and Attachment #16).

30. NEII Code Record Archive –Brian Black.

The following historical and current records are still being sought for the NEII Code Record Archives (NEII CRA):

• ASME A17 Mechanical Design Committee – assigned to Lou Bialy; • ASME A17 Escalator and Moving Walk Committee – previously assigned to Kyle

Apperson; and • ASME A17 Hydraulic Committee – previously assigned to John Koshak.

31. Inspection Committee and ASME A17.2 Inspection Guide – Louis Bialy. 32. Liaison Committee Reports.


6

(a) NEII Performance Standards Committee.

(b) NEII Architectural Standards Committee.

(c) NEII Safety Committee.

33. Other Business.

34. Time and Place for Future Meetings.

A joint meeting of the NEII Central Code and NEII Government Affairs Committees is scheduled for April 23, 2009 at 8:30 a.m. in Mississauga, Ontario.

35. Adjournment.

The meeting is scheduled to adjourn January 29 at 3:00 p.m. Travel arrangements should be scheduled accordingly. Please advise Brian Black if you are not planning to attend.

Attachments: 1. Hotel Information 2. Alternate(s) for Vincent Robibero 3. Committee Roster 4. CodeFinder Editor Activity Report 5. CodeFinder Database Procedure 6. CodeFinder Open Feedback 7. CodeFinder Help Update 8. CodeFinder Editor Audit Report Outline 9. CodeFinder Management Report Outline 10. Workshop: Emergency Preparedness for Persons with Disabilities and Special Needs 11. Letter to Al Tafazoli 12. NFPA 101/5000 Schedule 13. Area Code Committee Vacancies 14. Local Code Interpretations Proposal 15. CSA Letter 16. Response to CSA

1. The Westin Governor Morris 2 Whippany Road Morristown, NJ 07960 973-539-7300

www.westin.com/morristown Next to Schindler office / free shuttle available upon request Rate: 229.00 2. Best Western Morristown Inn 270 South Street Morristown, NJ 07960 973-540-1700 www.bestwesternnewjersey.com/hotels/best-western-morristown-inn/ Approximate 10-minute drive to Schindler office / high speed internet incl. in rate Rate: 139.00 3. The Madison Hotel 1 Convent Road Morristown, NJ 07960 973-285-1800 www.themadisonhotel.com Approximate 5-minute drive to Schindler office / free shuttle available upon request /

high speed internet incl. in rate Rate 175.00 4. Summerfield Suites 194 Park Avenue Morristown, NJ 07960 973-944-5902 www.morristown.summerfieldsuites.hyatt.com Approximate 5-minute drive to Schindler office / free shuttle available upon request /

high speed internet incl. in rate Rate: 189.00 5. Courtyard by Marriott - Hanover 157 Route 10 Whippany, NJ 07981 973-887-8700 www.marriott.com/hotels/travel/ewrnj-courtyard-hanover-whippany Approximate 10-minute drive to Schindler office Rate: 159.00 6. The Hotel Westminster 550 West Mount Pleasant Avenue Livingston, NJ 973-533-0600 www.westminsterhotel.net Approximate 15-minute drive to Schindler office / free shuttle available upon request Rate: 162.00

ATTACHMENT 1 Page 1 of 1

1

BDBlack Codes

From: [email protected]: Wednesday, December 10, 2008 9:17 AMTo: BDBlack CodesCc: [email protected]; [email protected];

[email protected]; [email protected]: Aziz Rehman as Alt - NEII Elevator Law Activity Status ReportAttachments: pic08909.jpg

Importance: High

Dear Brian, I will be away for an extended period and Aziz Rehman will act my alternate at NEII CCC, CCC/GAC and Performance committees. Please add aziz to all correspondence and meeting information that comes to me. Aziz will support the meetings in MOR in January along with Amzad. Kind regards, Vince Robibero ____________________________________ Schindler Elevator Corporation Product Codes and Standards Vincent Robibero Corporate Code Consultant, NA 20 Whippany Road Morristown, NJ 07960 Tel. +1 973 397 6018 Fax +1 973‐397‐6141 [email protected] www.us.schindler.com ____________________________________ "BDBlack Codes" <brian@bdblackcod es.com> To <[email protected]>, 11/18/2008 11:12 <[email protected]>, AM <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]> , <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]>,

ATTACHMENT #2 Page 1 of 3

2

<[email protected]>, <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]> cc Subject NEII Elevator Law Activity Status Report NEII Government Affairs and Central Code Committee Members: Please be advised that the Elevator Law Activity Status Report has been updated on your respective websites. Government Affairs Committee: http://www.neii.org/members/committees/25/ Central Code Committee: http://www.neii.org/members/committees/20/ Thank you, Brian Black (Embedded image moved to file: pic08909.jpg) Code and Safety Consultant to NEII 47 Leicester Street Perry, New York 14530 585.302.0813 office 585.354.6772 cell


3

585.302.0841 fax [email protected] www.bdblackcodes.com ************************************* Notice: The information contained in this message is intended only for use of the individual(s) named above and may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient of this message you are hereby notified that you must not use,disseminate, copy it in any form or take any action in reliance of it. If you have received this message in error please delete it and any copies of it and notify the sender immediately. *************************************


Central Code Committee

Name KYLE APPERSON

Title R & D MANAGER

Company FUJITEC AMERICA, INC.

Address 401 FUJITEC DRIVE

City LEBANON State OH Zip Code 45036

E-Mail [email protected]

666

Notes

MemberCategory

Phone 1 932-8000 Extension

Phone 2

Fax 1 933-5582Mobile 276-5680

513Area Number Area Number

513513

Name LOUIS BIALY

Title DIRECTOR WORLDWIDE CODES & STANDARDS

Company OTIS ELEVATOR COMPANY

Address 5 FARM SPRINGS ROAD

City FARMINGTON State CT Zip Code 06032-


56

Notes Alternate member NEII Standards Committee for ISO activities.

ChairCategory


Phone 2 651-8335

Fax 1 676-6865Mobile 839-0961


860860860

Name BRIAN BLACK

Title NEII CODE AND SAFETY CONSULTANT

Company BDBLACK CODES

Address 47 LEICESTER STREET

City PERRY State NY Zip Code 14530


725

Notes

SecretaryCategory


Phone 2 237-5965

Fax 1

Mobile 354-6772585Area Number Area Number

585 585

Wednesday, January 07, 2009 Page 1 of 4ATTACHMENT 3 Page 1 of 4


Name JOSEPH BUSSE

Title DIR. OF TECH. SERVICES CHIEF ENGINEER R & D

Company FUJITEC AMERICA, INC.

Address 401 FUJITEC DRIVE

City LEBANON State OH Zip Code 45036-9698


300

Notes

AlternateCategory


Phone 2

Fax 1 933-5582Mobile 739-0802


513513

203

Name STEVE GRAINER

Title SPECIAL PROJECTS MANAGER

Company MITSUBISHI ELECTRIC & ELECTRONICS USA, INC.

Address 5665 PLAZA DRIVE, PO BOX 6077

City CYPRESS State CA Zip Code 90630-0007


461

Notes

MemberCategory


Phone 2 220-4800

Fax 1 220-4812Mobile 448-5796


714714714

Name PHILLIP HAMPTON

Title CHIEF ENGINEER

Company THYSSENKRUPP ELEVATOR CORPORATION

Address 9280 CRESTWYN HILLS DRIVE

City MEMPHIS State TN Zip Code 38125


623

Notes

MemberCategory


Phone 2

Fax 1 860-2598Mobile 210-9275


901901



Name DOUG HENDERSON

Title ENGINEER

Company THYSSENKRUPP ELEVATOR CORPORATION

Address P. O. BOX 370

City MIDDLETON State TN Zip Code 38052


624

Notes

AlternateCategory


Phone 2

Fax 1 376-1913Mobile 652-3649


731901

Name ANDREW JUHASZ

Title MANAGER, CODES & STANDARDS

Company KONE INC.

Address ONE KONE COURT

City MOLINE State IL Zip Code 61265-


111

Notes

MemberCategory


Phone 2 743-5525

Fax 1 743-5530Mobile


3093095525

Name DAVID MCCOLL

Title MANAGER, CODES & STANDARDS

Company OTIS CANADA INC.

Address 1655 THE QUEENSWAY EAST

City MISSISSAUGA State ON Zip Code L4X 2Z5


272

Notes

AlternateCategory


Phone 2 276-5577

Fax 1 660-9874Mobile 500-3919


905860416



Name VINCENT P. ROBIBERO

Title NORTH AMERICAN CODE CONSULTANT

Company SCHINDLER ELEVATOR CORPORATION

Address P. O. BOX 1935

City MORRISTOWN State NJ Zip Code 07962-1935


53

Notes

MemberCategory


Phone 2

Fax 1 397-6141Mobile 216-8030


973973


CodeFinder Editor Activity Report

Code Type: Return to the CodeFinder Editor Activity ReportGenerator page

This CodeFinder database report was was generated for Brian Black on 01/09/2009. Brian Black is granted a single user non-transferablelicense for the use of CodeFinder database generated reports which are not to be copied in whole or in part for distribution outside BDBlackCodes Inc..

Date Range: 10/09/2008 to 01/09/2009

Editor: Amzad Malique State: West Virginia Jurisdiction: State of West Virginia Code Type: Elevator NewCode Eff/As Of Added Added by Req # Req Eff Added

ASME A17.1/CSA B44Edition: 2007

04/01/2008 Building Permit Date

11/11/2008 Amzad MaliqueSchindler Elevator [email protected]

Comments:

Editor: W. J. (Bill) Morrison State: Colorado Jurisdiction: City of Denver Code Type: BuildingCode Eff/As Of Added Added by Req # Req Eff Added

ICC International Building CodeEdition: 2006


10/28/2008 W. J. (Bill) MorrisonThyssenKrupp [email protected]

Comments:http://www.denvergov.org/Portals/114/documents/DBC%208%208%2008.pdf statutes http://www.denvergov.org/2008Amendments/tabid/427532/Default.aspxmain page

Editor: W. J. (Bill) Morrison State: Colorado Jurisdiction: City of Denver Code Type: ElectricalCode Eff/As Of Added Added by Req # Req Eff Added

NEC - NEC / NFPAEdition: 2008



Comments:http://www.denvergov.org/Portals/114/documents/DBC%208%208%2008.pdf statutes http://www.denvergov.org/2008Amendments/tabid/427532/Default.aspxmain page

Editor: W. J. (Bill) Morrison State: Colorado Jurisdiction: City of Denver Code Type: Elevator NewCode Eff/As Of Added Added by Req # Req Eff Added

ASME A17.1Edition: 2004 & 1a-05 & 1S-05



Colorado -Denver Elevator

08/08/2008 10/23/2008

Comments:2008 Denver Building Code & Amendments The following are the Denver Amendments to the 2006 International Building Code: The Building Code for the Cityand County of Denver is based on the 2006 Series of I - Codes, and 2008 National Electrical CodeCHAPTER 30 ELEVATORS AND CONVEYING SYSTEMSSECTION 3001 GENERAL Section 3001.2 Referenced standards is amended by adding the following: ASME A 17.1 A-2004 addenda and A17.1SSupplement Safety Code for Elevators and escalators.

NEII CodeFinder Editor Admin Area http://www.neii.org/members/CodeEditor/EditorAdmLookup.cfm

1 of 8 1/9/2009 3:44 PM


Editor: W. J. (Bill) Morrison State: Colorado Jurisdiction: State of Colorado Code Type: BuildingCode Eff/As Of Added Added by Req # Req Eff Added




Comments:Exhibit A Rev. 7/2008 APPROVED STATE BUILDING CODES The following approved building codes and standards have been adopted by State BuildingsPrograms (SBP) as the minimum requirements to be applied to all state-owned buildings and physical facilities including capital construction and controlledmaintenance construction projects. The 2006 edition of the International Building Code (IBC) (as adopted by the Colorado State Buildings Program as follows:Chapters 2-35 and Appendices C and I) The 2006 edition of the International Mechanical Code (IMC) (as adopted by the Colorado State Buildings Programas follows: Chapters 2-15 and Appendix A) The 2006 edition of the International Energy Conservation Code (IECC) (as adopted by the Colorado StateBuildings Program) The 2008 edition of the National Electrical Code (NEC) (National Fire Protection Association Standard 70) (as adopted by the ColoradoState Electrical Board) The 2006 edition of the International Plumbing Code (IPC) (as adopted by the Colorado Examining Board of Plumbers as follows:Chapter 1 Section 101.2,102, Chapters 2-13 and Appendices B, D, E, F and G) The 2006 edition of the International Fuel Gas Code (IFGC) (as adopted bythe Colorado Examining Board of Plumbers as follows: Chapter 1 Section 101,102, Chapters 2-8 and Appendices A, B, C and D) The National Fire ProtectionAssociation Standards (NFPA) (as adopted by the Department of Public Safety/Division of Fire Safety as follows with editions shown in parentheses: NFPA-1(2006), 11 (2005), 12 (2005), 12A (2004), 13 (2002), 13D (2002), 13R (2002), 14 (2003), 15 (2001), 16 (2003), 17 (2002), 17A (2002), 20 (2003), 22(2003), 24 (2002), 25 (2002), 72 (2002), 409 (2004), 423 (2004), 750 (2003) and 2001 (2004)) The 2004 edition of the ASME Boiler and Pressure VesselCode (as adopted by the Department of Labor and Employment/Boiler Inspection Section as follows: sections I, IV, VIII-Divisions 1 and 2 and 3, X and B31.1)The 2004 edition of the National Boiler Inspection Code (NBIC) (as adopted by the Department of Labor and Employment/Boiler Inspection Section) The 2004edition of the Controls and Safety Devices for Automatically Fired Boilers CSD-1 (as adopted by the Department of Labor and Employment/Boiler InspectionSection) The 2004 edition of the Boiler and Combustion Systems Hazards Code, NFPA 85 (as adopted by the Department of Labor and Employment/BoilerInspection Section) The 2007 edition of ASME A17.1 Safety Code for Elevators and Escalators (as adopted by the Department of Labor andEmployment/Conveyance Section and as amended by ASME International) The 2005 edition of ASME A17.3 Safety Code for Existing Elevators andEscalators (as adopted by the Department of Labor and Employment/Conveyance Section and as amended by ASME International) The 2005 edition ofASME A18.1 Safety Standard for Platform Lifts and Stairway Chairlifts

Editor: W. J. (Bill) Morrison State: Colorado Jurisdiction: State of Colorado Code Type: Elevator ExistingCode Eff/As Of Added Added by Req # Req Eff Added

ASME A17.3Edition: 2005



Chapter 333,Title 9, article5.5-101thru120

01/02/2008 10/28/2008

Comments:

Editor: W. J. (Bill) Morrison State: Colorado Jurisdiction: State of Colorado Code Type: MechanicalCode Eff/As Of Added Added by Req # Req Eff Added

IMCEdition: 2006



Comments:

Editor: David Nicholas State: Wisconsin Jurisdiction: State of Wisconsin Code Type: ElectricalCode Eff/As Of Added Added by Req # Req Eff Added

NFPA 70 National Electrical CodeEdition: 2008

02/01/2009 Plan Approval Date

01/06/2009 David NicholasKONE [email protected]

620.25 02/01/2009 01/06/2009

620.21(A)(1) 02/01/2009 01/06/2009

Comments:

Editor: David Nicholas State: Wisconsin Jurisdiction: State of Wisconsin Code Type: Elevator NewCode Eff/As Of Added Added by Req # Req Eff Added


01/01/2009 Contract Award Date

01/06/2009 David NicholasKONE [email protected]

1.1.1 01/01/2009 01/07/2009

1.1.2 01/01/2009 01/06/2009

1.1.3 01/01/2009 01/06/2009

1.1.4 01/01/2009 01/06/2009


2 of 8 1/9/2009 3:44 PM


1.2 01/01/2009 01/06/2009

1.3 01/01/2009 01/06/2009

2.7.2.1 01/01/2009 01/06/2009

2.7.2.17.1 01/01/2009 01/09/2009

2.7.3.1 01/01/2009 01/06/2009

2.7.3.4.1 01/01/2009 01/06/2009

2.7.3.4.3 01/01/2009 01/06/2009

2.7.5.2 01/01/2009 01/06/2009

2.7.9.2 01/01/2009 01/08/2009

2.8.2.3 01/01/2009 01/06/2009

2.10.1 01/01/2009 01/06/2009

2.10.1 01/01/2009 01/08/2009

2.12.6.2 01/01/2009 01/06/2009

2.16.1.1 01/01/2009 01/06/2009

2.17.14 01/01/2009 01/06/2009

2.18.9 01/01/2009 01/06/2009

2.26.4.1 01/01/2009 01/06/2009

2.27.2 01/01/2009 01/06/2009

2.27.3.2.1 01/01/2009 01/08/2009

2.27.3.2.3 01/01/2009 01/09/2009

2.27.3.2.4 01/01/2009 01/09/2009

2.27.4.2 01/01/2009 01/09/2009

2.27.8 01/01/2009 01/06/2009

3.4.7 01/01/2009 01/06/2009

3.18.3.8.3 01/01/2009 01/06/2009

3.26.3.1.2 01/01/2009 01/06/2009

8.1 01/01/2009 01/09/2009

8.6 01/01/2009 01/09/2009

8.6.1.4.2 01/01/2009 01/09/2009

8.6.10 01/01/2009 01/06/2009

8.6.11.3 01/01/2009 01/09/2009

8.6.11.4 01/01/2009 01/09/2009

8.6.11.5 01/01/2009 01/09/2009

8.6.11.6 01/01/2009 01/09/2009

8.6.11.7 01/01/2009 01/09/2009

8.6.11.8 01/01/2009 01/09/2009


3 of 8 1/9/2009 3:44 PM


8.6.5.7 01/01/2009 01/06/2009

8.6.5.8 01/01/2009 01/06/2009

8.7.2.13 01/01/2009 01/06/2009

8.7.2.17.1 01/01/2009 01/06/2009

8.7.2.22.1 01/01/2009 01/09/2009

8.7.2.28 01/01/2009 01/06/2009

8.7.2.8 01/01/2009 01/09/2009

8.7.3 01/01/2009 01/09/2009

8.7.3.22.1 01/01/2009 01/06/2009

8.7.3.31.8 01/01/2009 01/06/2009

8.7.3.8 01/01/2009 01/09/2009

8.9 01/01/2009 01/06/2009

8.10.1.1.1 01/01/2009 01/06/2009

8.10.1.1.2 01/01/2009 01/06/2009

8.10.1.1.3 01/01/2009 01/06/2009

8.11.1.1 01/01/2009 01/06/2009

8.11.1.1.1 01/01/2009 01/06/2009

8.11.1.1.2 01/01/2009 01/06/2009

8.11.1.3 01/01/2009 01/06/2009

8.11.1.4 01/01/2009 01/06/2009

8.11.2.2.1 01/01/2009 01/06/2009

8.11.2.2.2(b) 01/01/2009 01/06/2009

8.11.2.2.7 01/01/2009 01/06/2009

8.11.2.3.1 01/01/2009 01/06/2009

8.11.2.3.3 01/01/2009 01/06/2009

8.11.2.3.4 01/01/2009 01/06/2009

8.11.2.3.5 01/01/2009 01/06/2009

8.11.3.2.1 01/01/2009 01/06/2009

8.11.3.2.2 01/01/2009 01/06/2009

8.11.3.2.3 01/01/2009 01/06/2009

8.11.3.3.1 01/01/2009 01/06/2009

9.1 01/01/2009 01/06/2009

Comments:

Editor: JoAnne Stokes State: Virginia Jurisdiction: State of Virginia Code Type: AccessibilityCode Eff/As Of Added Added by Req # Req Eff Added

ANSI A117.1 Accessible/UsableBuildings


11/07/2008 JoAnne StokesFujitec America Inc.


4 of 8 1/9/2009 3:44 PM


Edition: 2003 [email protected]

Comments:Virginia Uniform Statewide Building Code (USBC) adopts ANSI A117.1 2003 as referenced by 2006 IBC.

Editor: JoAnne Stokes State: Virginia Jurisdiction: State of Virginia Code Type: BuildingCode Eff/As Of Added Added by Req # Req Eff Added



11/07/2008 JoAnne StokesFujitec America [email protected]

103.2 05/01/2008 11/25/2008

1007.4 05/01/2008 11/07/2008

3002.4 05/01/2008 11/07/2008

3006.7 05/01/2008 11/07/2008

Comments:Virginia Uniform Statewide Building Code (USBC) references the 2006 ICC codes and their referenced standards. The Virginia Construction Code (USBSPart 1) adopts Chapters 2-35 of the 2006 International Building Code. Chapter 1 and other Virginia amendments contained in USBC Part I supercede anyconflicting provisions of IBC Chapters 2-35. See grace period described in Req. 103.2.

Editor: JoAnne Stokes State: Virginia Jurisdiction: State of Virginia Code Type: ElectricalCode Eff/As Of Added Added by Req # Req Eff Added




Comments:Virginia Uniform Statewide Building Code (USBC) adopts NFPA 70 National Electrical Code 2005.

Editor: JoAnne Stokes State: Virginia Jurisdiction: State of Virginia Code Type: Elevator NewCode Eff/As Of Added Added by Req # Req Eff Added

ASME A17.1Edition: 2004 & 1a-05 & 1S-05



Comments:Virginia Uniform Statewide Building Code (USBC) adopts ASME A17.1-04, A17.1a-2005 addenda, A17.1S Supplement 2005 as referenced by 2006 IBC. VAConstruction Code (USBC Part 1) Req. 103.2 describes grace period: 103.2 When applicable to new construction. Construction for which a permitapplication is submitted to the local building department after May 1, 2008, shall comply with the provisions of this code, except for permit applicationssubmitted during a one-year period after May 1, 2008. The applicant for a permit during such one-year period shall be permitted to choose whether to complywith the provisions of this code or the provisions of the code in effect immediately prior to May 1, 2008. This provision shall also apply to subsequentamendments to this code based on the effective date of such amendments. In addition, when a permit has been properly issued under a previous edition ofthis code, this code shall not require changes to the approved construction documents, design or construction of such a building or structure, provided thepermit has not been suspended or revoked.

Editor: Sandra Anderson State: Oregon Jurisdiction: State of Oregon Code Type: BuildingCode Eff/As Of Added Added by Req # Req Eff Added



12/02/2008 Sandra AndersonOtis Elevator [email protected]

3001.2 04/01/2007 12/02/2008

Comments:The 2007 Oregon Structural Specialty Code is the 2006 Edition of the International Building Code and amended by the Building Codes Division.

Editor: Sandra Anderson State: Oregon Jurisdiction: State of Oregon Code Type: ElectricalCode Eff/As Of Added Added by Req # Req Eff Added




Comments:Oregon Electrical Specialty Code is based on NEC 2008.

Editor: Sandra Anderson State: Rhode Island Jurisdiction: State of Rhode Island Code Type: BuildingCode Eff/As Of Added Added by Req # Req Eff Added


08/01/2007 Unknown

11/11/2008 Sandra AndersonOtis Elevator Company

3001.1 08/01/2007 11/11/2008


5 of 8 1/9/2009 3:44 PM


[email protected]

3001.1.1 08/01/2007 11/11/2008

3001.2 08/01/2007 11/11/2008

Comments:No state building inspector, local municipality inspectors only. 39 minicipalities. Rhode Island State Building Code is Regulation SBC-1-2007, withamendments effective January 1, 2006

Editor: Sandra Anderson State: Rhode Island Jurisdiction: State of Rhode Island Code Type: ElectricalCode Eff/As Of Added Added by Req # Req Eff Added




Comments:Known as Rhode Island State Electrical Code - SBC-5, 2008.

Editor: Sandra Anderson State: Rhode Island Jurisdiction: State of Rhode Island Code Type: Elevator ExistingCode Eff/As Of Added Added by Req # Req Eff Added

ASME A17.3Edition: 2005

03/31/2006 Final Acceptance Date


2.2 01/14/2008 11/25/2008

2.3 01/14/2008 11/17/2008

2.4 01/14/2008 11/17/2008

2.5 01/14/2008 11/17/2008

2.6 01/14/2008 11/17/2008

2.7 01/14/2008 11/17/2008

2.8 01/14/2008 11/17/2008

2.9 01/14/2008 11/17/2008

2.1 01/14/2008 11/17/2008

2.10 01/14/2008 11/25/2008

2.11 01/14/2008 11/25/2008

2.12 01/14/2008 11/17/2008

2.13 01/14/2008 11/17/2008

2.14 01/14/2008 11/17/2008

2.15 01/14/2008 11/17/2008

2.16 01/14/2008 11/25/2008

2.17 01/14/2008 11/17/2008

2.18 01/14/2008 11/17/2008

2.19 01/14/2008 11/17/2008

2.20 01/14/2008 11/25/2008

2.21 01/14/2008 11/17/2008

2.22 01/14/2008 11/17/2008

2.23 01/14/2008 11/17/2008

2.24 01/14/2008 11/17/2008


6 of 8 1/9/2009 3:44 PM


2.25 01/14/2008 11/17/2008

2.26 01/14/2008 11/17/2008

2.27 01/14/2008 11/17/2008

2.28 01/14/2008 11/17/2008

2.29 01/14/2008 11/17/2008

2.30 01/14/2008 11/17/2008

2.31 01/14/2008 11/17/2008

2.32 01/14/2008 11/17/2008

2.33 01/14/2008 11/17/2008

2.34 01/14/2008 11/17/2008

2.35 01/14/2008 11/17/2008

2.36 01/14/2008 11/17/2008

2.37 01/14/2008 11/17/2008

2.38 01/14/2008 11/17/2008

2.39 01/14/2008 11/17/2008

2.40 01/14/2008 11/17/2008

2.41 01/14/2008 11/17/2008

2.42 03/31/2006 11/17/2008

2.43 01/14/2008 11/17/2008

2.44 01/14/2008 11/17/2008

2.45 01/14/2008 11/17/2008

2.46 01/14/2008 11/17/2008

2.47 01/14/2008 11/17/2008

2.49 01/14/2008 11/17/2008

2.50 01/14/2008 11/17/2008

Comments:Rhode Island autoadopts per Title 23, Health and Safety, Chapter 23-33, Section 23-33-2.

Editor: Sandra Anderson State: Rhode Island Jurisdiction: State of Rhode Island Code Type: Elevator NewCode Eff/As Of Added Added by Req # Req Eff Added


10/06/2007 Final Acceptance Date


2101.10a 01/14/2008 11/13/2008

303.4(a) 01/14/2008 11/13/2008

2100.10a 01/14/2008 11/13/2008

2102.10a 01/14/2008 11/13/2008

Rule 1.0Revision (g)

01/14/2008 12/01/2008

Rule 1.0 01/14/2008 11/13/2008

Rule 2.1Definitions

01/14/2008 12/01/2008


7 of 8 1/9/2009 3:44 PM


Rule 2000.10a 01/14/2008 11/14/2008

Rule 2001.10a 01/14/2008 11/14/2008

Rule 2002.10a 01/14/2008 11/14/2008

Note Rule 1.0 01/14/2008 11/13/2008

Note: Rule 1.0Addition

01/14/2008 11/13/2008

Note: Title 23Health & Safety

01/14/2008 11/13/2008

Comments:Rhode Island autoadopts per Title 23, Chapter 23-33, Section 23-33-2

Agencies/Contacts with no Codes/Modifications

Committed: UnCommitted: Pending:

Return to the CodeFinder Editor Activity Report Generator page

Copyright © 2003-2009 National Elevator Industry, Inc., Salem, NY


8 of 8 1/9/2009 3:44 PM


1.0 Purpose and Objective:

1.1 This document establishes procedures as required by the National Elevator Industry Inc. Local Code Regulations Database Policy (hereinafter called “NEII CodeFinder Policy”) to ensure an accurate and up-to-date NEII Local Code Regulations Database (hereinafter called “CodeFinder”) of all pertinent Codes.

1.2 At this time Rack and Pinion Elevators, Screw-Column Elevators, Hand Elevators, Inclined Elevators, Limited-Use/Limited-Application Elevators, Private Residence Elevators, Private Residence Inclined Elevators, Power Sidewalk Elevators, Rooftop Elevators, Special Purpose Personnel Elevators, Shipboard Elevators, Mine Elevators, Elevators Used for Construction, Dumbwaiters, Material Lifts, Platform Lifts and Stairway Chair Lifts shall not be included in CodeFinder.

2.0 Responsibilities:

2.1 Allocations of Responsibilities:

The Central Code Committee established the following allocations of responsibilities for establishing and maintaining CodeFinder by representative companies.

COMPANY ASSIGNMENTS

State / Province Company UNITED STATES

Alabama ThyssenKrupp Elevator Corp. Alaska ThyssenKrupp Elevator Corp. Arizona Schindler Elevator Corp. Arkansas ThyssenKrupp Elevator Corp. California Mitsubishi Electric & Electronics USA, Inc. Colorado ThyssenKrupp Elevator Corp. Connecticut Otis Elevator Company Delaware Fujitec America, Inc. District of Columbia Fujitec America, Inc. Florida Mitsubishi Electric & Electronics USA, Inc. Georgia Fujitec America, Inc. Hawaii Mitsubishi Electric & Electronics USA, Inc. Idaho Schindler Elevator Corp. Illinois KONE Inc. Indiana Otis Elevator Company Iowa KONE Inc. Kansas ThyssenKrupp Elevator Corp. Kentucky Fujitec America, Inc. Louisiana ThyssenKrupp Elevator Corp. Maine Otis Elevator Company Maryland Fujitec America, Inc. Massachusetts Otis Elevator Company


COMPANY ASSIGNMENTS State / Province Company

Michigan ThyssenKrupp Elevator Corp. Minnesota ThyssenKrupp Elevator Corp. Mississippi Schindler Elevator Corp. Missouri ThyssenKrupp Elevator Corp. Montana KONE Inc. Nebraska KONE Inc. Nevada Mitsubishi Electric & Electronics USA, Inc. New Hampshire ThyssenKrupp Elevator Corp. New Jersey Schindler Elevator Corp. New Mexico Schindler Elevator Corp. New York Schindler Elevator Corp. North Carolina Schindler Elevator Corp. North Dakota KONE Inc. Ohio Fujitec America, Inc. Oklahoma KONE Inc. Oregon Otis Elevator Company Pennsylvania Schindler Elevator Corp. Rhode Island Otis Elevator Company Puerto Rico Schindler Elevator Corp. South Carolina Otis Elevator Company South Dakota KONE Inc. Tennessee ThyssenKrupp Elevator Corp. Texas KONE Inc. Utah ThyssenKrupp Elevator Corp. Vermont Fujitec America, Inc. Virginia Fujitec America, Inc. Washington Fujitec America, Inc. West Virginia Schindler Elevator Corp. Wisconsin KONE Inc. Wyoming KONE Inc.

CANADA Alberta Fujitec America, Inc. British Columbia Otis Elevator Company Manitoba KONE Inc. New Brunswick Schindler Elevator Corp. Newfoundland Otis Elevator Company Northwest Territories Nunavut and Yukon

Otis Elevator Company

Nova Scotia Otis Elevator Company Ontario Otis Elevator Company Prince Edward Island Otis Elevator Company Quebec Schindler Elevator Corp. Saskatchewan KONE Inc.


2.2 Company Responsibility:

2.2.1 It is the responsibility of the assigned company to obtain and document in accordance with this procedure information for assigned jurisdictions including their local Code variations and interpretations. This information is to be recorded in CodeFinder in a timely manner. Only substantive deviations from the requirements in the Model Code shall be entered into CodeFinder. Editorial deviations from the Model Code should not be included in CodeFinder, e.g. wording revised but requirement the same.

2.2.2 Requirements in local codes that impact the industry shall also be included. 2.2.3 Local code information shall be included only when it differs from the state code or

effective date is different. Add following to comment field when state has modifications “See state (insert code title) Code for modifications”

2.2.4 Each company to assign one CodeFinder Editor to follow-up on feedback forms. Once

the issue is resolved, NEII Code and Safety Consultant to be advised.

3.0 CodeFinder Revisions:

CodeFinder is to be maintained up to date with current Codes and regulations. At a minimum on the 15th of January, April, July and October, the responsible company shall review and update CodeFinder from local Code information. The update will include the data specified in Appendix A of the NEII CodeFinder Policy.

3.1 Revision Methodology:

3.1.1 The latest edition and addenda and/or supplement shall be indicated as the referenced Model Code in CodeFinder. The effective date is the date the AHJ begins to enforce the applicable Code. 3.1.2 The following method of revision shall be used for CodeFinder: 3.1.2.1 All text shall be Arial 10 (CodeFinder editor “Arial small”). Red Underline text shall be used for all additions and Blue Strikeout text for all deletions to the Model Code text. Text for “Other Codes” and a non-model code shall be black and not underlined. 3.2.2.1 The number recorded in the REQUIREMENT field shall be the actual requirement number for the affected text. In Example 1 the requirement numbers for the two entries are 2.27.1.1 and 2.27.1.2. In Example 2 the requirement number for the single entry is 2.27.1.1(g).

EXAMPLE 1: Where a Section, Rule or a Requirement is modified, each Requirement shall be entered into CodeFinder; e.g. Section 2.27


Requirement 2.27.1 Requirement 2.27.1.1 –Local modifications are made to this requirement. Only the text of this requirement shall be shown with the modifications. Requirement 2.27.1.2 – Where this local requirement does not appear in the Model Code, it is a new requirement. Only the text of this added requirement shall be shown

EXAMPLE 2: Where a new subparagraph is added to an existing Section, Rule or Requirement, the text of the affected Requirement subparagraph shall be entered into CodeFinder, e.g. Section 2.27

Requirement 2.27.1 Requirement 2.27.1.1(g) –A new local subparagraph (g) is added. The entire text of 2.27.1.1(g) shall be shown. The following text shall be inserted in the COMMENT field “This requirement has been added”.

3.1.3 Where a local Code requirement number exists that number shall precede the text of the modification.

3.1.4 Do not add text in requirement number field. The requirement number field should

contain only the model code section/requirement/rule number. The number must be entered exactly as shown in the referenced model code. When their is no requirement number insert the term “NOTE”

3.2 Agency Field: 3.2.1 Where there is no responsible agency for enforcement of an adopted model code, enter

“NO AGENCY IDENTIFIED” in the agency name field and “NA” in all other fields.

3.3 Comment Field: 3.3.1 If a modification was added by error or is revised due to an intermediate revision by the AHJ it shall be deleted from the modification field and shown in the COMMENT field as struck out text to advise the user of CodeFinder that a revision has been made to the entry. 3.3.2 Published local Code interpretations, director rulings, etc. shall be included in the COMMENT field.

3.3.3 The comment field should include the term(s), “Added”, “Modified”, “Deleted”, and/or

“Reference” at a minimum.

3.3.4 Where an existing Section, Rule or Requirement is deleted the following text shall be inserted in the COMMENT field for each deleted Requirement “This requirement has been deleted”. In this instance the CodeFinder Editor shall not show the struck out text for the requirement.


EXAMPLE 3: Where an entire Section is deleted each Requirement number shall be entered in CodeFinder. In this instance the CodeFinder Editor shall not show the struck out text for the requirement, e.g. Section 2.27

Requirement 2.27.1 - Where the Section has been deleted add the following to the COMMENT field “This requirement has been deleted”. Requirement 2.27.2 - Where the Section has been deleted add the following to the COMMENT field “This requirement has been deleted”.

3.3.5 Where ASME A17.7/CSA B44.7 is adopted either directly or by reference from ASME A17.1/CSA B44 or other model code, one of the following statements shall be inserted in the COMMENT field:

• “Adopted by legislation/regulation”; or • “Adopted by reference from model code.” Substitute ASME A17.1/CSA B44, etc. for

the term “model code”.

3.3.5.1 Where the code is adopted by reference, the CodeFinder Editor is to verify with the AHJ that they will accept equipment conforming to ASME A17.7/CSA B44.7. If the AHJ indicates equipment conforming to ASME A17.7/CSA B44.7 will not be accepted this information is to be recorded in the COMMENTs field along with the statement required by 3.3.5.

4.0 General:

4.1 Every effort shall be made to attach, or hyper-link to, a copy of the law or regulation (source document) adopted by the AHJ or attach some form of official verification that the regulation has been adopted. Where written documentation is not available the CodeFinder Editor shall document the form of verification in the COMMENT field.

4.2 Local letters of interpretation, directors ruling, etc. shall be appended to the modification to which they apply. 4.3 General documents pertaining to local regulations (e.g. permitting, licensing, enforcement, etc.) shall be appended to the “Edit Code Modification Record”. 4.4 When an effective date is not available, insert record added date, select “Other” for “As Of” insert “Date Record Entered - Effective Date Unknown”.

5.0 NEII Local Code Database Metrics:

5.1 The following shall be tracked by the Central Code Committee:

(a) days between CodeFinder commit date and Code effective date; and (b) revisions to modification records in CodeFinder after commit date.


6.0 Auditing:

6.1 Immediately after adding or revising data the CodeFinder Editor shall generate a user report to verify the added or revised data is included in the report. If the report is not correct the CodeFinder Editor is to advise the developer, NEII Administrator and NEII Code and Safety Consultant of any discrepancies.

APPROVED: NEII Central Code Committee, 30-Aug-08 c:\my documents\wpdocs\neii\neii codefinder\neii codefinder procedures.doc


Created State Jurisdiction Code Type Code Agency Contact Req #AgenciesContacts

Codes2008-11-12

Kentucky State of Kentucky Elevator New ASME A17.1200407/06/2007

Department of Housing,Buildings andConstruction

Feedback Issue: Open: 58 days From: Amzad MaliqueEmail: [email protected]: Schindler Elevator CorporationPhone: 973-397-6289 extension:There is an issue with the following Code: ASME A17.1 in State: Kentucky Jurisdiction: State of Kentucky Code Type:Elevator New Edition: 2004

This is an email we recieved from KY acting cheif inspector George Tackorchick. I hope you dont mind that I left thefeedback here, but thought it would be simpler then opening up a feedback for each amendment. Can you please let meknow if you get any official documentation showing these changes. Thanks. Amzad Upon subsequent testing andinvestigation of the following rules which were initially not adopted, I have concluded that from a safety standpoint they areacceptable as long as they are in compliance with A17.1 2004 edition. 2.19.3..29(a)(3)--rope gripper 2.27.3.3.7--firefighter's service behind a locked cover 3.26.10--battery lowering--Variance letter required and letter will beposted in machine room after testing In addition the governor (hoistway)access opening shall not be required if thegovernor can be inspected and serviced from the car top or an adjacent car, means are furnished to prevent movement ofthe car when servicing the governor, and the governor can be reset automatically when the car is moved in the updirection. If you have any questions or concerns, please call 502-330-3889. Respectfully, George Tokarchick ActingChief Elevator Inspector

2008-11-24 Washington Seattle Building

ICC InternationalBuilding Code200308/15/2004

Department of Planningand Development

Feedback Issue: Open: 46 days From: Amzad MaliqueEmail: [email protected]: Schindler Elevator CorporationPhone: 973-397-6289 extension:There is an issue with the following Code: ICC International Building Code in State: Washington Jurisdiction: Seattle CodeType: Building Edition: 2003

Seattle has adopted IBC 2006 and also A17.1 2005a according to the attachment.

2008-11-25 Washington Seattle Elevator New

ASME A17.12000 thru 1b-0308/15/2004

Department of Planningand Development,Elevator Section

Feedback Issue: Open: 45 days

CodeFinder Open Feedback

Click on these Icons to view or close the entire Feedback Issue. Indicates Feedback Issue has been open for more than twoweeks.

NEII CodeFinder Editor Admin Area http://www.neii.org/members/CodeEditor/IndexFB.cfm

1 of 2 1/9/2009 10:14 AM


From: Amzad MaliqueEmail: [email protected]: Schindler Elevator CorporationPhone: 973-397-6289 extension:There is an issue with the following Code: ASME A17.1 in State: Washington Jurisdiction: Seattle Code Type: ElevatorNew Edition: 2000 thru 1b-03

I Tried sending this yesterday, my computer kicked me off so wasn't sure if it went through. Sorry if this is a duplicate.Seattle apperently has adopted IBC 2006 and A17.1-2005a. Can you please confirm, looks like alot of amendments.thanks http://www2.iccsafe.org/states/Seattle2006/seattle_building/building_frameset.htm

Code Modifications

Created State Jurisdiction Code Type Code Agency BrokenURL Req ##

Agencies2008-10-28

Colorado State of Colorado Building Department ofRegulatory Agencies

Regulation WebSite Link broken

Open: 73 days Broken Regulation Web Site Link:http://colorado.gov/dpa/dfp/sbrep/forms/sb/building codes

Code Modifications

CodeFinder Broken Link Report

CodeFinder Feedback ReportState/Province

Company

Jurisdiction Code Type

Begin Date

End Date

Note: Report shows items CREATED between Begin and End dates selected.

Copyright © 2003-2009 National Elevator Industry, Inc., Salem, NY

NEII CodeFinder Editor Admin Area http://www.neii.org/members/CodeEditor/IndexFB.cfm

2 of 2 1/9/2009 10:14 AM


CodeFinder Online Help

Note: CodeFinder users should be aware that the Internet browser supported by CodeFinder is the Microsoft Internet Explorer versions 6 and later. Other browsers are not supported and may not, in all instances, work satisfactorily. Also CodeFinder produces reports in the PDF format. Reports may be read and saved to your computer using any of the Adobe Acrobat products versions 5 and later.

CONTENTS

• INTRODUCTION o Introductory Presentation

• CODEFINDER REPORTS o Enforcement Authority for a Jurisdiction o Code Information for a Jurisdiction o Model Code Adoption by Edition o Model Code Modifications by Edition and Requirement # o Model Code Modifications by Requirement # o Word Search o Pending Code Information for a Jurisdiction

• WEEKLY REPORT ARCHIVE • CODEFINDER FEEDBACK • SEARCHING FOR WORDS IN A PDF DOCUMENT • MODEL CODE PROCUREMENT INFORMATION • ACROBAT READER BROWSER CONFIGURATION

INTRODUCTION The NEII CodeFinder Report Catalog provides a convenient method of querying the CodeFinder database. Field personnel will find the Enforcement Authority for a Jurisdiction, and Code Information for a Jurisdiction reports most useful. Engineers will find Model Code Modifications by Edition and Requirement #, Model Code Modifications by Requirement #, and Word Search reports most useful. Factory personnel will find Code Information for a Jurisdiction, and Model Code Adoption by Edition reports most useful. Attorneys will appreciate the Enforcement Authority for a Jurisdiction, and Code Information for a Jurisdiction reports, especially the historical information. All the queries return their reports in an Acrobat file that can be saved to your computer.

Note: At this time Rack and Pinion Elevators, Screw-Column Elevators, Hand Elevators, Inclined Elevators, Limited-Use/Limited-Application Elevators, Private Residence Elevators, Private Residence Inclined Elevators, Power Sidewalk Elevators, Rooftop Elevators, Special Purpose Personnel Elevators, Shipboard Elevators, Mine Elevators, Elevators Used for Construction, Dumbwaiters, Material Lifts, Platform Lifts and Stairway Chair Lifts are not included in CodeFinder.

NEII CodeFinder Introduction

To view CodeFinder introduction presentation


CODEFINDER REPORTS

Enforcement Authority for a Jurisdiction Inputs for this report are:

• State/Province; • Local Jurisdiction; and • Code Type (all or selected).

The report includes the following information:


• State/Province; • Jurisdiction; • Code Type; • Agency Name; • Contact, Title, Email, Phone, and Fax; • Agency Street and Mailing Address; • Agency Phone, and Fax; • Agency Web Site; and • Regulation Web Site.


Code Information for a Jurisdiction

Inputs for this report are: • State/Province; • Local Jurisdiction; • Code Type (all or selected); and • Current or Historical.

Clicking on the Historical radio button will bring up the In Effect Date input. If Historical is selected, only information within the CodeFinder database for the selected date (In Effect Date) will be included in the report. The report includes the following information:

• State/Province; • Jurisdiction; • Code Type; • Agency Name; • Contact Title, Email, Phone, and Fax; • Agency Street and Mailing Address; • Agency Phone and Fax; • Agency Web Site; • Regulation Web Site; • Code; • Edition; • Effective Date; • As of Date; • Code Comments; and • Modifications (Requirement #, Requirement, Comment, Effective Date &

Document Link).


Model Code Adoption by Edition Inputs for this report are:

• Code Type; • Code Title; and • Edition.


• State/Province; • Jurisdiction;


• Code Type; • Agency Name; • Code; • Edition; • Code Comments; and • Code Attachments.


Model Code Modifications by Edition and Requirement # Inputs for this report are:

• Code Type; • Code Title; • Edition; and • Requirement #.

The Requirement # can be a full requirement number or a partial with an asterisk to retrieve a series of Requirement Numbers. Example 11.* would retrieve 11.1, 11.2, 11.a, etc. Another valid example,*-11-*, which would retrieve 18-11-1101.1, 119-11-1101.2, etc. The report includes the following information:

• State/Province; • Jurisdiction; • Code Type; • Agency Name; • Code; • Edition; • Effective Date; • As of Date; • Code Comments; and • Modifications (Requirement #, Requirement, Comment, Effective Date &

Document Link).


Model Code Modifications by Requirement # Inputs for this report are:

• Code Type; • Code Title; • Requirement #; and • Historical.


Clicking on the Historical radio button will bring up the In Effect Date input. If Historical is selected, only information within the CodeFinder database for the selected date (In Effect Date) will be included in the report.



Document Link).


Word Search Inputs for this report are:

• State/Province; • Jurisdiction; • Code Type; • First Word/Phrase; • Second (optional) Word/Phrase; • Historical.


Inputs for First Word/Phrase and Second (optional) Word/Phrase can contain asterisks as a wildcard. For Example: “Elevat*” will match all Modifications with Comments or Requirement text containing words that begin with “Elevat”; including “elevator” and “elevators”. Two search terms are available, the first is required. If you enter a term into the second field, only Modification with Comments or Requirement text containing both terms will be retrieve (either of the terms could appear in either the Modification with Comments or Requirement text to satisfy a "match" condition. Clicking on the Historical radio button will bring up the In Effect Date input. If Historical is selected, only information within the CodeFinder database for the selected date (In Effect Date) will be included in the report. The report includes the following information:


Document Link).


Pending Code Information for a Jurisdiction Inputs for this report are:

• State/Province; and • Jurisdiction/Code/Edition.

The input screen only displays code information for jurisdictions with future Effective Dates for the criteria selected. The report includes the following information:


• State/Province; • Jurisdiction; • Code Type; • Agency Name; • Contact, Title, Email, Phone, and Fax; • Agency Street and Mailing Address; • Agency Phone and Fax; • Agency Web Site; • Regulation Web Site; • Code; • Edition; • Effective Date; • As of Date; • Code Comments; and • Modifications (Requirement #, Requirement, Comment, Effective Date &

Document Link).


Weekly Report Archives Weekly reports include links to CodeFinder database changes or addition made in the prior week. Weekly reports for the past year are available in this area.


To receive weekly CodeFinder e-mail reports you must check CodeFinder E-Mail Opt In at Edit My Account. If you have not subscribed to weekly reports you may also see an option to subscribe at the bottom of the CodeFinder Report Catalog page. If you previously subscribed to weekly CodeFinder e-mail reports and no longer wish to receive the weekly CodeFinder e-mail uncheck CodeFinder E-Mail Opt In at Edit My Account. To access Edit My Account


CODEFINDER FEEDBACK This FEEDBACK icon will appear at selected locations within a CodeFinder report. If an issue arises you are encouraged to click on the FEEDBACK icon at the point of the issue and a feedback form will be generated. Please fill in the appropriate information and click on the submit feedback button. You may also attach up to 5 documents to provide additional information to the CodeFinder Editors. Allowed document types, that can be attached, are: PDF, Word files (.doc), text files(.txt), .gif files, .jpg files, and Excel files (.xls). Once the feedback report issue has been addressed by the CodeFinder Editor you will receive an e-mail advising of the action taken on your feedback. Feedback can also be sent from the button on the CodeFinder drop down menu. However, it is strongly recommended that this only be used for general comments or soliciting help as this feedback is sent to the NEII Administrator not the CodeFinder Editor.


If you see this CAUTION icon someone else has already found an issue with the associated information and has submitted a feedback report on it. When you see the CAUTION icon there will be no feedback icon. Once the feedback item has been address the FEEDBACK icon will appear on subsequent reports. If you have saved an old report and click on a feedback icon, and someone else has already submitted a feedback report on the item, an alert email will be sent to the editor but no Feedback Report item will be created. It will be up to the Editor to incorporate your issue into the open Feedback Report. A sample feedback form is shown below:

SEARCHING FOR WORDS IN A PDF DOCUMENT Since all CodeFinder database reports are Acrobat PDF’s you can use the tools available in the Acrobat reader to take further advantage of the information in CodeFinder reports.


You can use either the Acrobat Find toolbar, if available on your version of Acrobat, or the Acrobat Search PDF window to locate a word, series of words, or partial word in CodeFinder reports. The Acrobat Find toolbar provides a basic set of options for searching for text in only the open CodeFinder report. The Acrobat Search PDF window provides more advanced options, and lets you search for text in one or more PDF documents, an index of PDF files, or PDF files on the Internet. The Acrobat Find toolbar provides the following search options in the toolbar's Find Options menu. The Acrobat Search PDF window provides these options in either the basic or advanced search mode:

• Whole Words Only - finds only occurrences of the complete word you enter in the text box. For example, if you search for the word “stick”; the words “tick” and “sticky” aren't found.

• Case-Sensitive - finds only occurrences of the words that are in the case that you typed. For example, if you search for the word “Elevator”; the words “elevator” or “ELEVATOR” aren't found.

• Include Bookmarks - searches the text in the Bookmarks tab as well as in the document.

• Include Comments - searches the text in comments and in the document. The Advanced Search Options in the Search PDF window can either broaden or restrict your search results. You can view Advanced Search Options by clicking Use Advanced Search Options at the bottom of the Acrobat Search PDF window when the window displays Basic Search options.

Note: The options Whole Words Only, Case-Sensitive, Include Bookmarks, and Include Comments are also available when the window is in basic search mode.

The Return Results Containing menu lets you restrict your search results according to the option you choose.

• Match Exact Word or Phrase - searches for the entire string of characters, including spaces, in the order in which they appear in the text box. For example, if you type “elevator car”, the results list only instances of “elevator car” (both words, next to each other, and in that order).

• Match Any Of The Words - searches for any instances of at least one of the words typed. For example, if you type each of, the results include any instances in which one or both of the two words appear: each, of, each of, or of each.

• Match All Of The Words - searches for instances that contain all your search words, but not necessarily in the order you type them. For example, if you type “elevator car”, the results include instances “elevator car” and “car elevator”. This option is available only for a search of multiple documents or index definition files.

• Boolean Query - searches for terms or phrases you indicate using Boolean operators. This option is available only for searching in a designated location, not for single-document searches


The Look In menu lets you restrict the search to the current document, an index, or a location on your computer. If you choose to search an index or a location on your computer, additional options appear under Use These Additional Criteria: The options under Use These Additional Criteria let you restrict the search parameters according to the criteria you specify. The results include instances that match all of the selected criteria only.

• For example, if you select Whole Words Only and Case Sensitive for a search of the word “Elevator”, the results don't include “elevator” or “Elevators”.

• The Proximity option returns documents that contain two or more words that you specify and in which the range of words between the specified words is lower than the number specified in the search preferences. For example, if you search for the words “elevator car” and set the Proximity preference to 900, the search finds all instances that contain the words “elevator” and “car”, but the number of words between them is not more than 900. This option is available only for a search of multiple documents or index definition files, and if Match All of The Words is selected.

• The Stemming option finds words that contain part (the stem) of the specified search word. This option applies to single words, and phrases when conducting a search in the current PDF, Find In Folder, or Acrobat indexes. For example, in English, Stemming finds instances of the search word that end in ing, ed, x, ion, and so on, but not er. This option is not available in searches for phrases in indexes created with Acrobat 5.0 or earlier. You cannot use wildcard characters (*, ?) in stemming searches.

MODEL CODE PROCUREMENT INFORMATION

Code Title Publisher ACCESSIBILITY ADA/ABA AG Americans with Disabilities Act US ATBCB ADAAG Americans with Disabilities Act US ATBCB ANSI A117.1 Accessible/Usable Buildings ICC BUILDING BOCA National Building Code ICC ICBO Uniform Building Code ICC ICC International Building Code ICC NBCC of Canada NRCC NFPA 5000 Building NFPA SBCCI Standard Building Code ICC ELECTRICAL CSA Canadian Electrical Code CSA NFPA 70 National Electrical Code NFPA ELEVATOR EXISTING ASME A17.3 ASME


ELEVATOR NEW ASME A17.1 ASME ASME A17.1/CSA B44 ASME or CSA CSA B44 CSA LIFE SAFETY NFPA 101 Life Safety Code NFPA Acrobat Reader Browser Configuration When CodeFinder Reports are generated the browser will attempt to pop up a new browser window which should display the report in PDF format. If instead it attempts to download the report file you should follow the instructions below:

• Configuring the browser to open PDF files within the browser window. • When you install an Acrobat product on a system that includes a browser, you

automatically configure the browser to open PDF files within the browser window. Acrobat installs ActiveX plug-in files that allow you to use IE or AOL to open PDF files. If Acrobat is installed, but PDF files don't open in the browser window, work through the following steps to configure the browser: 1. Make sure that the system meets the requirements for the Acrobat product you use. For a list of system requirements, refer to the following resources:

o Acrobat 6.0 Professional: See the Adobe website at www.adobe.com/products/acrobatpro/systemreqs.html

o Acrobat 6.0 Standard: See the Adobe website at www.adobe.com/products/acrobatstd/systemreqs.html .

o Adobe Reader 6.0: See the Adobe website at www.adobe.com/products/acrobat/acrrsystemreqs.html .

o Acrobat 5.x or Acrobat Reader 5.x: See the ReadMe file included with the application.

2. Make sure that the ActiveX plug-in is in the correct location: o Acrobat 6.0: Program Files/Adobe/Acrobat 6.0/Acrobat/ActiveX folder. o Adobe Reader 6.0: Program Files/Adobe/Acrobat 6.0/Reader/ActiveX

folder. o Acrobat 5.x: Program Files/Adobe/Acrobat 5.0/Acrobat/ActiveX folder. o Adobe Reader 5.x: Program Files/Adobe/Acrobat 5.0 /Reader/ActiveX

folder. 3. Use a supported version of the browser:

o Acrobat 6.0 and Adobe Reader 6.0 support IE 5.1-6.1 and AOL 6.0-8.0. o Acrobat 5.0 and Acrobat Reader 5.0 support IE 4.0-5.0 and AOL 6.x

(Windows 2000, Me, 98, or 95) or AOL 5.x (Windows NT). 4. Restart Windows to make sure that IE or AOL is accessing the most current Windows registry information. 5. Reinstall Acrobat or Acrobat Reader to make sure that the correct plug-in information is added to the Windows registry. 6. If you have an older version of Acrobat or Adobe Reader installed on the system, remove it.


Return to CodeFinder Report Catalog h:\wpdocs\neii\neii codefinder\codefinder user help.docx


CODEFINDER EDITOR AUDIT REPORT OUTLINE

Page 1 of 3

Report to be generated as Excel spread sheet table. Selection Criteria: Report to include committed current and pending code information. The State/Province will be identified with an asterisk “*” for pending code information.

• Company (Editor their company assignment only – Administrator chose company or all) • State/Province (select one or all) (Editor their company State’s/Province’s only –

Administrator chose State/Province or all) • Jurisdiction (select one or all) • Code Type (select one or all)

Default selection Company, State/Province “all”, Jurisdiction “all”, Code Type “all” Report Fields:

• State/Province • Jurisdiction • Agency

o Agency website (Yes or No) o Regulation website (Yes or No) o Last updated (date)

• Contact o Name o Phone (Yes or No) o E-mail (Yes or No) o Address (Yes or No) o Last updated (date)

• Code Type o Code title o Edition o Effective date o Modifications (Yes or No) o Last updated (date)

• Open Feedback (Yes or No) o Date opened

Report will include current data (pending and past data not included). All data field will be hyperlinked. Report Sorting:

• Editor default: o State/Province o Jurisdiction o Code type

• Administrator default: o Company o State/Province o Jurisdiction



Page 2 of 3

o Code type • Secondary sort by user on any column in report (ascending/descending)

Print/Save:

• Print button – print using print utility in browser or if report for single state/province, or jurisdiction offer option to print as a pdf

• Save button – save to file on user computer that can be opened using Excel Rev: 06-Jan-09 c:\my documents\wpdocs\neii\neii codefinder\codefinder editor audit report outline.doc



Page 3 of 3

SAMPLE REPORT

CodeFinder Editor: first name, last name Report Date: mm/dd/yyyy

Sta

te/P

rovi

nce

Juris

dict

ion

Age

ncy

Age

ncy

Web

site

R

egul

atio

n W

ebsi

te

Age

ncy

Last

Upd

ated

Con

tact

Nam

e

Con

tact

Pho

ne

Con

tact

E-M

ail

Con

tact

Add

ress

C

onta

ct L

ast U

pdat

ed

Cod

e Ty

pe

Cod

e Ti

tle

Cod

e E

ditio

n

Cod

e E

ffect

ive

Dat

e

Cod

e M

odifi

catio

ns

Cod

e La

st U

pdat

ed

Ope

n Fe

edba

ck

Feed

back

Ope

ned

AL State of Alabama Building Department

Y N 6/26/2007 John Updike Bill Williams

YY

YN

YY

6/26/20076/26/2007

Building IBC International Building Code

2006 1/1/2007 Y 6/26/2007 Y 9/5/2008

AL State of Alabama Building Department


YY

YN

YY

6/26/20076/26/2007

Electrical NFPA 70 National Electrical Code

2005 3/1/2005 Y 2/24/2005 N

AL * State of Alabama Building Department


YY

YN

YY

6/26/20076/26/2007

Electrical NFPA 70 National Electrical Code

2009 3/1/2009 Y 1/62009 N

AL State of Alabama Elevator Division Y Y 6/27/2007 Joe Inspector Y N Y 9/30/2008 Elevator New

ASME A17.1 2004 10/1/2006 N 9/30/2008 N

AL Birmingham Birmingham Building Department

Y Y 6/27/2007 James Ludlow Y Y Y 9/28/2007 Elevator New

ASME A17.1 2004 & 1a-05

1/1/2006 Y 9/28/2007 N

* PENDING CODE

Note: All fields will be hyperlinked to the data source within CodeFinder.


NE

II C

odeF

inde

r M

AN

AG

EM

EN

T R

EPO

RT

OU

TL

INE

Page

| 1

Cod

eFin

der

Edi

tor:

___

____

____

____

____

___

Rep

ort D

ate:

___

____

____

____

____

____

____

_ R

epor

ting

Peri

od:

____

____

__ to

___

____

____

ME

TR

IC 1

: CO

DE

AC

TIV

ITY

D

etai

led

Rep

ort C

odes

Add

ed a

nd R

olle

d O

ver

in R

epor

ting

Peri

od

Stat

e Pr

oven

ce

Juri

sdic

tion

Add

ed/R

olle

d O

ver

Cod

e T

ype

Res

pons

ible

C

ompa

ny

Eff

ectiv

eD

ate

Dat

e A

dded

/Rol

led

Ove

r D

ays

Lat

e

Su

mm

ary

Rep

ort C

odes

Add

ed a

nd R

olle

d O

ver

in R

epor

ting

Peri

od

C

odes

Add

ed/R

olle

d O

ver

Res

pons

ible

C

ompa

ny

Tot

al

≤ E

ffec

tive

Dat

e ≤

14 d

ays a

fter

E

ffec

tive

Dat

e >

14 d

ays a

fter

E

ffec

tive

Dat

e

N

umbe

r Pe

rcen

tage

Num

ber

Perc

enta

geN

umbe

r Pe

rcen

tage


NE

II C

odeF

inde

r M

AN

AG

EM

EN

T R

EPO

RT

OU

TL

INE

Page

| 2

M

ET

RIC

2:

FEE

DB

AC

K A

CT

IVIT

Y

Det

aile

d R

epor

t on

Feed

back

Cre

ated

in R

epor

ting

Peri

od

Stat

e/Pr

oven

ce

Juri

sdic

tion

Res

pons

ible

Com

pany

D

ate

Cre

ated

D

ate

Clo

sed

Sum

mar

y R

epor

t Fee

dbac

k A

ctiv

ity in

Rep

ortin

g Pe

riod

Feed

back

Cre

ated

R

espo

nsib

le

Com

pany

T

otal

C

lose

d ≤

5 D

ays

Clo

sed

>5 D

ays a

nd

≤ 14

Day

s C

lose

d >1

4 D

ays

Num

ber

Perc

enta

geN

umbe

r Pe

rcen

tage

Num

ber

Perc

enta

ge

N

OTE

:

1.

Rep

ort t

o be

in C

odeF

inde

r Edi

tor R

epor

t Cat

alog

. 2.

C

odeF

inde

r Edi

tors

, acc

ess t

o th

eir c

ompa

ny in

form

atio

n on

ly.

3.

NEI

I Cen

tral C

ode

Com

mitt

ee (c

hair,

mem

ber a

nd a

ltern

ate)

, NEI

I Cod

e an

d Sa

fety

Con

sulta

nt a

nd N

EII A

dmin

istra

tor,

acce

ss to

info

rmat

ion

on a

ll co

mpa

nies

. h:

\wpd

ocs\

neii\

neii

code

finde

r\cod

efin

der e

dito

r man

agem

ent r

epor

t.doc


1

ANSI Homeland Security Standards Panel (ANSI-HSSP)

February 3- 4, 2009 Washington, DC Workshop Co-Chairs: Hilary Styron, NOD Allan B. Fraser, NFPA

A Workshop on:

“Emergency Preparedness for

Persons with Disabilities and Special Needs”

Draft Agenda

February 3-4, 2009

Kellogg Conference Hotel at Gallaudet University

800 Florida Avenue N.E. Washington, DC 20002-3695

Tuesday – February 3, 2008

12:00 noon Registration

1:00 – 1:20 pm

Welcome

• S. Joe Bhatia, President and CEO, ANSI

• David Cappozzi, Executive Director, US Access Board

1:20 – 2:50 pm “Evacuation of People with Disabilities from recent events ” Moderator: Co-Chair, Hilary Styron, NOD

• Overview of concepts of mass evacuation from a geographic area:

o Erica Kuligowski, NIST

• Examples of specific lessons learned: o Claudia Gordon (DHS)- ( To Be Confirmed) o Cindy Daniel (DHS) (To Be Confirmed)

2:50 – 3:10 pm Break (Light refreshments served)

3:10 – 3:50 pm Overview and Perspective on the Population of People with Disabilities

• Timothy Muzzo - NIDRR National Institute on Disability and Rehabilitation Research (To Be Confirmed)

3:50 – 4:15 pm Public Input, Questions & Answers (Open forum)

4:15 – 4:30 pm Summary and Expectations for Tomorrow Co-Chair: Hilary Styron, NOD

Wednesday – February 4, 2008

8:00 – 9:00 am Registration (Light refreshments served)

9:00 – 10:15 am Panel Discussion: “What does the community of people with disabilities want and need, in terms of standards, to feel safe, protected and included”


• Moderator: Marsha Mazz, US Access Board

• Panelists:

o Hilary Styron - NOD

o Bill Scott-DARAC

o Peg Blechman-US Access Board- (To Be Confirmed) o State Emergency Planner or NGO representative from Texas ( To Be

Confirmed)

o Mary Troupe-Coalition for Citizens with Disabilities, Mississippi

10:15 – 10:30 am Break (Light refreshments served)

10:30 am – 12:00 pm

Breakout Groups: Group One: “What standards are there for the built environment for the community of

people with disabilities and what standards are still needed?”

-Moderator: Co-Chair, Allan Fraser, NFPA

Group Two: “What standards are there for evacuation operations and equipment for

the community of people with disabilities and what standards are still needed?”

- Moderator: Co-Chair, Hilary Styron, NOD

12:00 – 1:00 pm Lunch (provided)

1:00 – 1:30 pm Report of Discussions of the Breakout Groups Co-Chairs: Hilary Styron, NOD Allan Fraser, NFPA

1:30 – 2:00 pm Report: Environmental scan results of what is in place right now

Co-Chair, Allan Fraser, NFPA

2:00 – 3:00 pm Roundtable Discussion: Based on what standards we know exist, can we identify the gaps that need to be filled and what are the priorities?

-Moderator: Dominic Marinelli, United Spinal Association

• What works?

• What doesn’t work?

• What needs more research, development or refinement?

• Roles of public/private sectors and NGOs like community or faith based organizations.

3:00 – 3:15 pm Break (Light refreshments served)

3:15 – 3:30 pm Public Input Opportunity for other attendees/audience to weigh in on ideas, experiences.

3:30 – 4:00 pm Action Items , Follow-up Report, Next Steps & Closing Remarks Co-Chair: Hilary Styron, NOD


National Elevator Industry, Inc. CODE & SAFETY OFFICE 47 Leicester Street • Perry, New York 14530 • 585.302.0813 Fax: 585.302.0841


NEII ASSOCIATION HEADQUARTERS

1677 County Route 64 • P.O. Box 838 • Salem, New York 12865-0838 • 518.854.3100 Fax: 518-854-3257

November 7, 2008 Mr. Al Tafazoli Principal ERT Engineer State of California Division of Occupational Safety & Health 2100 E. Katella Avenue, Suite 280 Anaheim, CA 92806 Dear Mr. Tafazoli, The purpose of this letter is to draw your attention to direction by the ERT Division specifying EMI test procedures that are outside the letter of Title 8, Group IV, and is not in compliance with the referenced ASME A17.1-2004 Elevator Safety Code. Specifically, ERT has stated in the attached correspondence of August 4, 2008 an EMI test procedure as defined by an EN standard that is not referenced within the ASME A17.1-2004 Code. ASME A17.1-2004, Part 9 specifically references EN 12016-1998 for compliance with section 2.26.4.4. ERT is requiring EMI tests specified by EN 12016-2004 which is a substantially different document in technical content compared to EN 12016-1998. Furthermore, ERT is additionally requiring tests beyond the scope of EN-12016-2004, specifically beyond equipment limitations for voltage dips and interruptions specified in normative standard EN 61000-4-11. The limited capability of test apparatus is an important issue for a valid test. Please be cautioned that it is entirely feasible that in order to self-declare compliance to spec 4-11, EMI testing companies and elevator manufacturers may need to interpret test procedure to a degree that may compromise validation of the operational safety intent resulting in a false or incomplete statement of compliance. The ERT direction goes significantly beyond the rules established in Title 8, Section 3141.3 which requires compliance with ASME A17.1-2004 and creates difficulties for EMC testing companies and elevator equipment manufacturers, and consequently for the ERT Division as well. Furthermore, the rationale stated in the ERT correspondence of August 4, 2008 to me, which unilaterally mandates EN-12106-2004 test procedures and goes beyond the requirements of EN 61000- 4-11, is not valid for elevator control systems that have remained stable in terms of design concept since the introduction of EMI testing requirements by California in the year 2000.


Mr. Al Tafazoli November 7, 2008 Page 2

NEII requests that ERT amend the direction in its August 4, 2008 correspondence from Mr. Paul Puno so as to comply with the ASME A17.1-2004 Code as adopted by Title 8 Elevator Safety Orders Group IV. Respectfully,

Brian Black Code and Safety Consultant attachment cc: NEII Central Code Committee NEII Government Affairs Committee Mr. Paul Puno


NFPA 101/NFPA 5000 TECHNICAL COMMITTEE ROP MEETINGS

Core Committees - September 21-25, 2009

Monday, September 21 – Friday, September 25, 2009 Building Systems (BSY) Monday, September 21 Fundamentals (FUN) Monday and Tuesday, September 21-22 Furnishings and Contents (FUR) Tuesday, September 22 Structures, Construction Tuesday, September 22 And Materials (SCM) Building Construction (BLC) Wednesday, September 23 Means of Egress (MEA) Wednesday, Thursday and Friday, September 23-25 Fire Protection Features (FIR) Thursday and Friday, September 24-25 Building Service and Fire Thursday, September 24 Protection Equipment (BSF)


NFPA 101/NFPA 5000 TECHNICAL COMMITTEE ROP MEETINGS

Occupancy Committees - December 7-11, 2009

Monday, December 7 – Friday, December 11, 2009 Educational and Day-Care Monday, December 7 Occupancies (END) Board and Care Facilities (BCF) Tuesday, December 8 Detention and Correctional Tuesday, December 8 Occupancies (DET) Mercantile and Business Tuesday, December 8 Occupancies (MER) Assembly Occupancies and Wednesday, December 9 Membrane Structures (AXM) Residential Occupancies (RES) Wednesday, December 9 Industrial, Storage and Wednesday and Thursday, December 9-10 Miscellaneous Occupancies (IND) Health Care Occupancies (HEA) Thursday and Friday, December 10-11 1/09


NEII AREA CODE COMMITTEE VACANCIES

Page 1 of 2

NEII AREA CODE COMMITTEEArea Code Committee Company Alabama & Georgia KONE, Otis Alaska Arizona & New Mexico

Arkansas & Oklahoma California Otis Colorado Connecticut & Rhode Island

Otis

Florida Otis Hawaii ThyssenKrupp Idaho ThyssenKrupp, Otis Illinois Indiana Iowa ThyssenKrupp Kansas Kentucky Louisiana & Mississippi

ThyssenKrupp

Maine ThyssenKrupp Maryland & DC Massachusetts ThyssenKrupp Michigan Minnesota Otis Missouri ThyssenKrupp Montana & Wyoming ThyssenKrupp, Otis Nebraska ThyssenKrupp Nevada Schindler New Hampshire ThyssenKrupp New Jersey & Delaware

New York North & South Carolina

Otis

North & South Dakota Ohio ThyssenKrupp Oregon Otis, ThyssenKrupp Pennsylvania ThyssenKrupp Tennessee Otis Texas Fujitec America Inc. Utah Otis Vermont ThyssenKrupp Virginia


NEII AREA CODE COMMITTEE VACANCIES

Page 2 of 2

NEII AREA CODE COMMITTEEArea Code Committee Company Washington ThyssenKrupp, Otis West Virginia Otis, Wisconsin ThyssenKrupp

NEII AREA CODE COMMITTEE CHAIRSArea Code Committee Company of Past Chair

REV: 17-Dec-08 h:\wpdocs\neii\neii area code committee vacancies.doc


NEII Handling of Local (AHJ) Interpretations of Model Codes Vincent Robibero (updated 12/12/08 with Ed’s comments) CCC Item 27

Page 1 of 4

Issue: With the increase of the adoption of the model codes there appears to be an increase in: 1) Local interpretations by Authorities Having Jurisdiction (AHJ) of requirements in model codes that are either gray or are not explicitly addressed in the model code, both of which may have already been addressed by the code writing body responsible for the model code but rejected by the AHJ, 2) AHJ requests to the code writing body for interpretations. Sources of Issue: Often a local interpretation / position is precipitated by:

a) opinions or bias of an inspectors; b) opinions presented at NAESAi educational programs or other programs such as EIWPF/QEI training; c) areas where the model code is silent or gray; or d) new inexperienced inspection personnel.

local interpretation/position may or may not be documented by the AHJ but is none-the-less enforced. Some jurisdictions publish directives or news-letters that communicate their interpretation/position. For example: Pennsylvania has a web-link on interpretations. It also has an advisory web-link that includes positions and interpretations that are important: for example, permanent platforms in the overheads where machine ropes penetrate the top of a hoistway that has 11ft or more clearance above the crosshead of the elevator car. Impact: Typically once an AHJ has rendered an interpretation, it is unlikely they will change their position for two reasons:

1) Chiefs tend to support the position of their enforcement inspectors 2) Once the one manufacturer or service company complies with the local interpretation/position, the AHJ is very reluctant to reverse their position even in view of existing official model code interpretations that they may not have been aware of initially.

Local interpretations can have the same effect as an official model code interpretation in that they can be applied retroactive for all existing installations. It may even apply to installations approved by the AHJ prior to the interpretation.



Page 2 of 4

Proposal to address the issue: Overview: To address this issue, it is recommended that the NEII Central Code Committee add to its scope the coordination of AHJ local code issues among NEII members. To achieve this objective, the NEII Codes and Standards policy will be revised to reflect this initative. Proposed Elements to Policy revisions to address root sources of the issue: A) Establish NEII local code interpretation reporting process. B) NEII process of coordination to address issues and remediation with AHJ. C) Engage NAESAi in advocating use of model code interpretations by AHJ's The following will be incorporated into the NEII Code and Safety Policy upon NEII Board of Directors approval. Instructions and member communication regarding the scope addition would also be addressed. Plan will require NEII, NAESAi and ASME agreements. A) NEII local code interpretation reporting process: NEII will establish a method for member company personnel to report an AHJ’s change in enforcement as a result of a local interpretation. Signs of a local interpretation include:

1) Rejection/citation of a practice in new installations that were previously approved by the AHJ in the past, even though the code being enforced has not changed.

2) Rejection of an official model code interpretation. 3) Direct comment from an AHJ inspector or Chief. 4) AHJ posting of interpretation or advisory on their website or via other method. Suggested solution: Add to the NEII Talk a new "Member Forum" folder for Local Code Advisories with auto notification to NEII CCC members concerning the advisory. B) NEII coordination to address issues and remediation with AHJ The AHJ interpretations may be time critical for a NEII member because the AHJ is holding up approval of the member's installation. It is important that NEII coordination on the issue be as rapid as possible. Several steps to coordinate NEII on the issue are proposed: 1) Affected NEII member:

a) Obtain from the AHJ (preferred in writing) the source of their position/interpretation and confirm. b) Consult NEII code finder for local deviations to the model code. c) Consult the model code body regarding published interpretations in the model code (example ASME interpretations). d) Inform the AHJ, if necessary, that they would like a temporary extension to provide the AHJ with information regarding the issue. e) Identify commercial time constraint surrounding issue.



Page 3 of 4

f) If no official model code interpretation exists, see if AHJ will accept official interpretation from model code organization. Draft a proposed inquiry that is acceptable to AHJ. g) Post all information regarding issue in NEII Local Code Advisory, NEII Talk forum.

2) NEII Central Code Committee and NEII Code and Safety Consultant: a) NEII Central Code Committee members advise via the new NEII Talk forum if they have already addressed the issue or had similar experience with the AHJ. b) If an official model code interpretation exists:

a) NEII Code and Safet Consultant sends the AHJ the model code interpretation or, 2) NEII Code and Safety Consultant requests NAESAio contact the AHJ encouraging them to accept the model code interpretation

c) Where the local interpretation emanates for information given at a NAESAi / or EIWPF/QEI educational program and it conflicts with a clear model code requirements or official interpretations exist; the NEII Code and Safety Consultant will requests NASEAi or EIWPF to issue a memo to AHJ and if necessary modify the educational module. If appropriate the organization will be requested to clarify the issuewith its members such as in the NAESAi Progress news letter. d) If there are no clear model code requirements or official model code interpretations, the draft of a proposed interpretation by the affected NEII member is:

1) commented on by CCC members for NEII CCC approval on NEII Talk. 2) Upon NEII approval, NEII Code and Safety Consultant will send memo to AHJ requesting temporary delay in enforcement pending model code interpretation with proviso that: Depending on AHJ preference, NEII Code and Safety Consultant

can either: a) Sends inquiry to model code body on behalf of NEII with copy to AHJ and Central Code Committee. b) Sends inquiry to AHJ as a proposal for AHJ to submit to model code organization.

e) NEII Code and Safety Consultant searches Handbooks for references that may be of help and forwards to AHJ f) Upon model code approval of interpretation, NEII Code and Safety Consultant requests from model mode organization permission to forward in writing official minuted decision on interpretation to AHJ g) Conclusion of issue is incorporated into NEII CodeFinder where necessary h) Very serious issues that cannot be resolved with the above are discussed at Central Code Committee meeting for further actions including

Comment [ EAD1]: Do you mean what you said. This will take time. In the past the NEII Code and Safety Consultant submitted the request on behalf of a NEII member company. A compromise may be to circulate proposed interpratation for a period of time for comments, then submitt on behalf of a member company?



Page 4 of 4

escalation of the issue to the Government Affairs Committee and Legal Advisory Group where appropriate.

C) Engage NAESAi in addressing model code interpretations with AHJ's 1) Work with NAESAi to secure agreement with ASME to list interpretations in Progress based on minuted ASME A17 Standards Committee approval with short abstract and reference to ASME web-link 2) Where there were AHJ issues between issues and interpretations resolved them, B2(b) and B2(f) above. NAESAi makes special note of the issue and obtains approval from ASME to publish entire interpretation in Progress 3) NAESAi Cracker Barrels:

a) Interpretation questions addresses at Cracker Barrel at NAESAi meetings are to be clearly identified as unofficial. If official interpretation is requested a strawman opinion is to be prepared at the crackerbarell. b) Strawman opinion to forwarded to NEII for evaluation / comment c) agreement of strawman opinion between NEII and NAESAi is published in NAESAi Progress. Disagreement prompts a request for interpretation from either NEII or NAESAi from model mode body d) When model code organization issues official interpretation NAESAi will publish in NAESAi Progress .

h:\wpdocs\2007\jun\neii local code interpretation policy [ead 25-jun-07)].doc

Comment [ EAD2]: I am not clear whit this is intending to address?


C!II

CSA INTERNATIONAL -July 25, 2008

Mr. Edward A. Donoghue, CPCA Code and Safety Consultant to NEIl c/o National Elevator Industry, Inc. 1677 County Route 64 P.O. Box 838 Salem, NY 12865-0838

By-

Re: CSA International Technical Infonnation Letters

Dear Mr. Donoghue:

Thank you for allowing me the time to investigate your concerns regarding the incorporation of relevant requirements of the CSA Technical Infonnation Letters (TILs) into the CSA B44.1/ASME 17.5 standard.

As an accredited certification organization, CSA International's mandate is to certify products to published Standards and/or to Other Recognized Documents (such as the CSA TILs) as stipulated in the Standards Council of Canada (SCC) document CAN-P-1500L, Additional Requirements for Accreditation of Certification Bodies. TILs are typically used to advise industry of additional requirements that need to be addressed between editions of standards, or when concerns are raised by regulatory authorities and industry regarding safety issues encountered in the field, or when new technologies evolve which current standards do not fully address. The publication of a TIL allows CSA International to take into account the relevant issues during its normal certification process. Please note that CSA International's preference is to let the relevant Technical Committees deal with such concerns through the accredited standards development process. CSA International's procedure to issue TILs is designed specifically not to circumvent this standards development process.

CSA International initially prepared the TILs after consultation with industry and th Advisory Council on Elevating Devices (ACED) with the intent 0 address product certification requirements in Canada. Although these requirements were in the Elevator Safety Codes B44, B355 and B613 and CSA Standard B44.I, they could not be used by the regulatory authorities to verify elevator devices. The TILs received acceptance from the Elevator Technical Committees, ACED, and the Canadian Advisory Council on Electrical Safety (CACES). By the year 2000, the Hannonized Elevator Safety Code CSA B44.1 / ASME A17.1 and updated versions ofCSA Elevator Safety Codes B355 and B613 were published. Following the guidelines ofCAN-P1500, CSA International updated the TILs and made proposals to incorporate the TILs into the appropriate standards. We undedtand that these proposals are under review by the A17.11B44 Committees.

Randall W. Luecke

PreSident

---- 8501 East Pleasant Volley Rood. Cleveland. OH. U.S.A. 44131-5516 ---

Telephone: 2165244990, Ext. 8203 Fox: 216.328.8118 Email [email protected]


Edward A. Donoghue Page 2 0[2

CSA International agrees that the relevant requirements of the CSA TILs should be incorporated into the applicable CSA standard. It is suggested that the B44.1/ASME 17.5 Standard may still be the appropriate document to cover many of these requirements.

I have assigned Mr. Richard MacKenzie, Technical Advisor to coordinate with the Secretary of the ASME A17 Standards Committee to modify B44.1/ASME 17.5. Richard will identify the origin of the requirements of the CSA TILs for review by the Secretary of the ASME A17 Standards Committee. Upon request, Richard will provide his support to the Secretary to finalize the incorporation of the requirements of the TILs into the standard. We will only be in a position to withdraw our TILs when this task has been completed.

If you have any further comments or suggestions, please feel free to contact Richard MacKenzie or Davey Li, Technical Manager.

Yours truly,

~"--",,, Randall W. Luecke President, CSA International


National Elevator Industry, Inc. CODE & SAFETY OFFICE 47 Leicester Street • Perry, New York 14530 • 585.302.0813 Fax: 585.302.0841


NEII ASSOCIATION HEADQUARTERS

1677 County Route 64 • P.O. Box 838 • Salem, New York 12865-0838 • 518.854.3100 Fax: 518-854-3257

January 2, 2009 Randall W. Luecke, President CSA International 8501 East Pleasant Valley Road Cleveland, OH. 44131 RE: CSA International Technical Information Letters Dear Mr. Luecke: Thank you for your comprehensive letter of July 25, 2008 explaining the CSA International position on the above subject matter. We appreciate the diligence of CSA International and the commitment to promote enhancements to CSA B44.1/ASME A17.5. We request that TIL proposals be sent to the ASME A17 Secretary for dispersion to the various A17 committees, as some cover issues that are beyond the scope of CSA B44.1/ASME A17.5. Moreover, please confirm that should a proposal submitted by CSA International not be accepted by an ASME A17/CSA B44 committee, the corresponding TIL will be withdrawn by CSA International. As always we thank you for your continued commitment to safety. Best wishes,

Brian Black NEII Code and Safety Consultant Cc: NEII Central Code Committee John Walter, VP Standards, Canadian Standards Association International Suzanne Kiraly, President, Canadian Standards Association International

ATTACHMENT #16 Page 1

ATTACHMENT #16 Page 2