SCHEDULE FOR
DEVELOPMENT OF 2010 FBC
7/9/09
NOTE CHANGES TO CODE
DEVLOPMENT APPROACH:
This approach defers printing of codebooks until after the completion of the glitch amendment fixes to the FBC Update which is presented to the public as a Supplement to the 2009 I Codes. The FBC Update will be published online for public review. The codebooks publishing will begin when the FBC Update/Supplement is published to the web.
At least one contractor will be hired to evaluate the FBC Update for errors and unintended consequences, conflicts with laws and rules, etc. The review should start at point when TAC recommendations are developed and proceed through the time up till glitch amendments due date. This may be the publishing contractor who will identify these glitches during the publishing process similar to what the ICC does when publishing the new I codes.
The true glitches and Update of the NEC edition will be addressed through a limited glitch amendment process. The output of this glitch amendment process will be published on the web.
The printed 2010 FBC will be published using the FBC Update Supplement and the Glitch Amendment results. Given the glitches will be limited and ideally identified by the publisher (and perhaps an additional contractor) the time to completion of the final printed codes will be short.
This plan’s timeline for implementation by 12/31/11 depends on the
assumption that the 2010 FBC is established by adopting the 2009 I codes by
reference and the 2010 Supplement of
This plan also adheres to the principle of the 3 year updates of the
FFPC and FBC taking effect at the same time to avoid conflicts as directed by
law. It uses the last date identified by the SFM legal counsel’s opinion that
the FFPC can be implemented , 12/31 of the year before the year date of the
next edition of the NFPA standards that form its basis, as the target for
implementation of the FBC update.
2010
Update to the
Printed 2009 International Codes
published and available to the public 4/2/09
2009 I Codes must be
available to public for 6 months prior to selection
Commission selects 2009 I Codes as foundation for 2010 FBC (Oct Cmsn meeting) 10/13/09
Initiation draft of 2010 FBC Supplement with all 2007 FBC Florida specific 3/1/10
amendments referenced to the 2009 I Codes posted to the web.
Proposed amendments must use this Supplement’s
section numbering.
(Note:
The 2007 FBC Supplement and Glitch 1 and Glitch 2 Amendment Supplements,
all
existing
and
the 2009 I Codes are available to the public as of April 2009. The law provides
6 months
from
I Codes availability before the Commission can begin the 2010 FBC development.
Local amendments posted to 2010 Code development section of the website. 3/1/10
FFPC to FBC correlations/overlaps identified and recommendations developed (see subtasks below)
Proposed amendments to the 2009 I
Codes and
Proposed amendments posted to the Commission website by 5/1/10
45 day comment period ends (By law- 45 day min before TAC review) 6/15/10
TACs review proposed
at Rule Development Workshop(August Commission meeting)
TAC recommendations (tracking charts) posted to web 9/3/10
45 day comment period ends (By law- 45 day min before Commission review) 10/18/10
TACs review comments and prepare public comment for Rule Hearing 11/15/10
Commission considers TAC recommendations on proposed amendments 12/7-8/10 at Rule Adoption Hearing (December Commission meeting)
File Rule adopting the 2010 FBC and post Supplement to web 2/1/11
Code
amended to resolve glitches (see Glitch schedule below) 4/11-6/11
Code implemented (By law- no sooner than 6 months from
available to public) 12/31/11
Note: By law this is the latest date the
The goal is to implement the FFPC and FBC
concurrently.
Subtasks:
Review
of
identified by staff in the originating draft 2010 FBC Supplement 3/1/10
(Note: Law requires review of
amendment issue All other
or
removed by an approved amendment proposal. Staff will identify overlaps for the
TACs’ and Commission’s
consideration
and decision.)
Joint Fire TAC/Fire Code Advisory Council review of I Codes/NFPA 1/NFPA 101 10/09-8/10
changes for overlaps/conflicts
Contractor reviews Building and Fire codes and reports 10/09
Joint Fire TAC/FCAC meetings to develop recommended fixes 10/09-12/09
Fire TAC reviews proposed building code amendments for fixes 8/9-10/10
(Note: Law requires the Commission and
SFM to maintain the FBC and FFPC for consistency
to
avoid conflicting requirements. A contractor will identify new overlaps
resulting from changes
in
the new editions of the I codes and NFPA codes for consideration by the joint
Fire TAC and
Fire
Code Advisory Council and decision on
FBC amendments by the Commission)
(Note: Subtasks identify proposed code
modifications that are integrated into the code development process.)
Schedule:
2010 FBC Supplement published online 2/1/11
Glitch amendment submittal DEADLINE 3/1/11
(Note:
The Code publisher will identify correlation glitches and unintended
consequences of
specific
amendments in the final 2010 FBC Supplement for correction by glitch amendment.
See subtask
for
adoption of the 2011 NEC via the glitch proceeding)
Rule development workshop (April Commission meeting) 4/5/11
Rule adoption hearing (June Commission meeting) 6/7/11
Glitch Rule adopted (filed) 7/1/11
Code printed with glitch fixes and available to the public 10/1/11
2010
FBC effective 12/31/11
Note: By law this is the latest date the
The goal is to implement the FFPC and FBC
concurrently.
Subtask:
Review 2011 NEC (Note: not subject to glitch proposal submittal deadline) 1/11-4/11
Recommend whether to adopt as glitch (August Commission meeting) 4/5/11
Adoption per schedule above
Intervals Between Milestones:
Option 1:
Time From To
6 months 2009 I Codes available to public Commission selects 2009 I Codes
11 months 2009 I Codes available for review 2007 FBC Supplement* ready for amendments
11 months 2009 I
Codes available for review
local amendments; FFPC Correlations: identified
for review in the update proceeding.
12 months 2009 I Codes available for review Amendment proposals due date (4/2/10)
1 month Supplement* ready for amendmnts Amendment proposals due date (4/2/10)
1 month Amendment proposals due date Amendment proposals posted to web (5/1/10)
45 days Proposed amendmnts posted to web Comment on proposals period ends (6/15/10)
7 weeks Comment period ends TACs review proposed amendments at Rule Workshop
3 weeks TACs review amendments/RDW TAC recommendations posted to web
45 days TAC recmnds posted to web Comment on TAC recommendations period ends
1 month Comment period ends TACs review comments and report to Commission
2 months Comment period ends Commission considers TAC rcmnds at Rule Hearing
7 weeks Rule AdoptionHearing Rule filed and 2010 FBC Supplement** posted to web
1 month 2010 Supplement**on web Glitch amendment submittal deadline
1 month Amendment deadline Rule Development Workshop
2 months Rule Development Workshop Rule Adoption Hearing
1 month Rule Hearing Rule filed/adopted
3 months Rule filed/adopted Codebooks available to the public
3 months Codebooks available Code implementation date
* The 2007 FBC
Supplement is all the
** The 2010 FBC Supplement is all
Option 2: