My WebLink
|
Help
|
About
|
Sign Out
Browse
Search
AgdaPkt 2002-12-09
RedwoodCity
>
City Clerk
>
Agenda Packets
>
2000-2009 partial
>
2002
>
AgdaPkt 2002-12-09
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/2/2012 12:25:36 PM
Creation date
12/5/2002 3:47:58 PM
Metadata
Fields
Template:
CC Index
CC Index - Document Type
Agenda Packet
Agency Type
City Council
Date
12/9/2002
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
287
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
� O� � � <br /> MAKE YOUR VIEWS KNOWN ON NFPA FIRE SERVICE STANDARD 1710 � <br /> The NFPA Standards Council placed NFPA 1710 into a special 3-year review cycle, as opposed to the normal 5- <br /> year cycle, and the work of the new NFPA 1710 Technical Committee has begun. NLC and other groups representing • <br /> tocal governments have representatives on the 1710 Technical Committee. League of California Cities Executive <br /> Director Chris McKenzie is a member. <br /> NFPA Standard 1710 is the controversial pr.oposal, adopted last year, that recommends minimum staffing levels <br /> (4 per company) and response time standards (4 minutes maximum for initial response) for fire companies staffed by <br /> substantially all career firefighters. <br /> If your community wants to propose a change to Standard 1710, your proposal must be submitted by lanuary <br /> 3, 2003. California cities that submit comments are also requested to send a copy of those comments to League <br /> Executive Director Chris McKenzie at 1400 K Street, Suite 400, Sacramento, CA 95814 or via e-mail to <br /> mckenzie@cacities.org. Outlined below is information about the NFPA 1710 review schedule and details on how to <br /> submit proposed changes to the Standard. <br /> NFPA Review Schedule <br /> The Standard is currently open for public proposals. Anyone can submit the proposals. Proposals must be <br /> received at the NFPA office by 5:00 pm on January 3, 2003. Proposat forms, as well as the current edition of NFPA <br /> 1710, are available on�the NFPA web site (www.nfpa.org/Codes/CodesandStandards.asp ). The NFPA format must be <br /> utilized, and proposals �ar �� submi*ted by mail, fax, or utilizing the web page. <br /> The Technical Committee will review the proposals at a meeting on March 3-5, 2003, in St. Petersburg, Fla. <br /> The Technical Committee votes by a letter ballot, A two-thirds affirmative vote of the Committee is required to <br /> move the draft standard forward to the next step. Committee members can change their vote. <br /> Everyone who sends in a proposal will receive a response back by August 1, 2003 explaining the Committee's <br /> action with respect to their proposal(s). <br /> A revised draft will then be distributed that will include the actions of the 1710 Technical Committee concerning <br /> the proposals submitted. The Standard will then move out of the "Proposal" stage and into the "Comment" stage of <br /> the process. <br /> Comments on the Revised Draft will be due to the NFPA office by October 10, 2003. <br /> The 1710 Technical Committee will meet again between October and December of 2003 to review and vote on <br /> Comments. As done previously, all people who submit Comments will receive a reply from the Committee by March, <br /> 2004, outlining Committee actions on their comments. <br /> The NFPA membership will vote on the revised NFPA 1710 Stan�ard at their annual meeting in Salt Lake City on <br /> May 4, 2004. The NFPA Standards Council will approve, amend, disapprove, or send NFPA Standard 1710 back to <br /> Committee by July 4, 2004. <br /> Visit the League's Official Web Site--www.cacities.org PRIORITY FOCUS/PAGE 7 <br />
The URL can be used to link to this page
Your browser does not support the video tag.