| Date |
Text |
| 2022-12-20 10:40:25 | THIS PLAN WAS REVIEWED AND FAILED BY PETER LEDUC, FIRE |
| | MARSHAL, WITH THE FOLLOWING COMMENTS: |
| | |
| | 1) THERE IS AN INDICATION OF AN EXIT DISCHARGE AT THE |
| | REAR OF THE BUILDING QITH A SHORT CONCRETE TYPE PAD. |
| | |
| | IT IS UNCLEAR THAT THIS EXIT LEADS TO A PUBLIC WAY AS |
| | THIS AREA HAS LIMITED ACCESS DUE TO THE RR AND POSSIBLE |
| | FENCED IN AREA. |
| | |
| | PER NFPA 101, CH 7, MEANS OF EGRESS. |
| | |
| | 7.7 DISCHARGE FROM EXITS |
| | 7.7.1* EXIT TERMINATION. EXITS SHALL TERMINATE |
| | DIRECTLY, AT A PUBLIC |
| | WAY OR AT AN EXTERIOR EXIT DISCHARGE, UNLESS OTHERWISE |
| | PROVIDED IN 7.7.1.2 |
| | THROUGH 7.7.1.4 |
| | |
| | 7.7.1.1 YARDS, COURTS, OPEN SPACES, OR OTHER PORTIONS |
| | OF THE EXIT DISCHARGE |
| | SHALL BE OF THE REQUIRED WIDTH AND SIZE TO PROVIDE ALL |
| | OCCUPANTS WITH A |
| | SAFE ACCESS TO A PUBLIC WAY |
| | |
| | 7.5.3.4 EXTERIOR EXIT ACCESS SHALL BE ARRANGED SO THAT |
| | THERE ARE NO DEAD |
| | ENDS IN EXCESS OF THOSE PERMITTED FOR DEAD-END |
| | CORRIDORS IN CHAPTERS 11 |
| | THROUGH 43. |
| | |
| | |
| | FOR THE OFFICIAL RECORD, PLEASE PROVIDE DETAILS THT |
| | THIS EXIT LEADS TO A PUBLIC WAY AND IS PROTECTED ALONG |
| | THE EXIT TRAVEL PATH SHOULD THERE BE WINDOWS THAT CAUSE |
| | EXPOSURE CONCERNS. |
| | |
| | |
| | |
| | 2) THERE ARE INDICATIONS OF FIRE ALARM DEVICES ON THE |
| | ELECTRICAL PLANS WITH NO DESIGN DETAILS AS REQUIRED OF |
| | A MASTER PERMIT. |
| | |
| | PER FLORIDA ADMINSTRATIVE CODE: |
| | |
| | 61G15-30.003 MINIMUM REQUIREMENTS FOR ENGINEERING |
| | DOCUMENTS. |
| | (1) ENGINEERING DOCUMENTS ARE PREPARED IN THE COURSE OF |
| | PERFORMING ENGINEERING SERVICES. WHEN PREPARED FOR |
| | INCLUSION WITH AN APPLICATION FOR A GENERAL BUILDING |
| | PERMIT, THE DOCUMENTS SHALL MEET ALL ENGINEER???S |
| | RESPONSIBILITY RULES, SET FORTH IN CHAPTERS 61G15-31, |
| | 61G15-32, 61G15-33, AND 61G15-34, F.A.C., AND BE OF |
| | SUFFICIENT CLARITY TO INDICATE THE LOCATION, NATURE AND |
| | EXTENT OF THE WORK PROPOSED AND SHOW IN DETAIL THAT IT |
| | WILL CONFORM TO THE PROVISIONS OF THE FLORIDA BUILDING |
| | CODE, ADOPTED IN SECTION 553.73, F.S., AND APPLICABLE |
| | LAWS, ORDINANCES, RULES AND REGULATIONS, AS DETERMINED |
| | BY THE AHJ. THE DOCUMENTS SHALL INCLUDE: |
| | (A) INFORMATION THAT PROVIDES MATERIAL SPECIFICATIONS |
| | REQUIRED FOR THE SAFE OPERATION OF THE SYSTEM THAT IS A |
| | RESULT OF ENGINEERING CALCULATIONS, KNOWLEDGE AND |
| | EXPERIENCE. |
| | (B) LIST FEDERAL, STATE, MUNICIPAL, AND COUNTY |
| | STANDARDS, CODES, ORDINANCES, LAWS, AND RULES, WITH |
| | THEIR EFFECTIVE DATES, THAT THE ENGINEERING DOCUMENTS |
| | ARE INTENDED TO CONFORM TO. |
| | (C) INFORMATION, AS DETERMINED BY THE ENGINEER OF |
| | RECORD, NEEDED FOR THE SAFE AND EFFICIENT OPERATION OF |
| | THE SYSTEM. |
| | (D) LIST ENGINEERING DESIGN CRITERIA; REFERENCE PROJECT |
| | SPECIFIC STUDIES, REPORTS, AND DELEGATED ENGINEERING |
| | DOCUMENTS. |
| | (E) IDENTIFY CLEARLY ELEMENTS OF THE DESIGN THAT VARY |
| | FROM THE GOVERNING STANDARDS AND DEPICT/IDENTIFY THE |
| | ALTERNATE METHOD USED TO ENSURE COMPLIANCE WITH THE |
| | STATED PURPOSE OF THESE RESPONSIBILITY RULES. |
| | (2) ENGINEERS SHALL LEGIBLY INDICATE THEIR NAME AND |
| | BUSINESS ADDRESS, ON ENGINEERING DOCUMENTS. ENGINEERING |
| | DOCUMENTS WHICH ARE ISSUED FOR PRELIMINARY OR |
| | CONCEPTUAL USE, SHALL CLEARLY NOTE THE INTENDED PURPOSE |
| | OF SUCH DOCUMENTS. |
| | (3) WHEN ELEMENTS OF THE PROJECT ARE SHOWN ON AN |
| | ENGINEERING DOCUMENT ONLY FOR INFORMATION OR |
| | CLARIFICATION AND THE ENGINEER DOES NOT INTEND TO |
| | ACCEPT RESPONSIBILITY FOR THE ELEMENTS, THE ENGINEER |
| | SHALL CLEARLY NOTE ON THE DOCUMENTS THE EXTENT OF HIS |
| | RESPONSIBILITY. |
| | (4) ENGINEERING DRAWINGS SHALL BE LEGIBLE AND CLEARLY |
| | DEFINE AND DELINEATE THE WORK IN THE PROJECT. THEY MUST |
| | ALSO COMPLY WITH CHAPTER 61G15-23, F.A.C., SEALS. |
| | (5) ENGINEERS SHALL CLEARLY NOTE ON ANY PRELIMINARY |
| | ENGINEERING DOCUMENTS THAT SUCH DOCUMENTS ARE NOT IN |
| | FINAL FORM, BUT ARE BEING TRANSMITTED TO THE PUBLIC |
| | AGENCY TO RECEIVE AGENCY REVIEWS, COMMENTS AND |
| | INTERPRETATIONS. THE DOCUMENTS MAY SUBSEQUENTLY BE |
| | REVISED BY THE ENGINEER TO REFLECT RESOLUTION OF ISSUES |
| | WITH THE PUBLIC AGENCY PRIOR TO FINAL ACTION BY THE |
| | AGENCY. CHANGES, REVISIONS AND MODIFICATIONS TO A |
| | PROJECT MAY PROMPT ADDITIONAL DOCUMENT SUBMITTAL FOR |
| | AGENCY APPROVAL ACTION ON THE SAME PROJECT. |
| | SPECIFIC AUTHORITY 471.033(2), 471.008 FS. LAW |
| | IMPLEMENTED 471.033(1)(G), 471.025(3) FS. HISTORY???NEW |
| | 1-26-93, FORMERLY 21H-30.003, AMENDED 11-13-08. |
| | |
| | |
| | 61G15-32.008 DESIGN OF FIRE ALARMS, SIGNALING SYSTEMS |
| | AND CONTROL SYSTEMS. |
| | (1) FIRE ALARMS, SIGNALING, AND CONTROL SYSTEMS |
| | INCLUDE, BUT ARE NOT LIMITED TO, FIRE PROTECTION |
| | SUPERVISION AND ALARM CIRCUITS, ACTIVATION CONTROLS, |
| | AND REMOTE SIGNALING. |
| | (2) THE FIRE PROTECTION SYSTEM DESIGN SPECIFICATIONS |
| | SHALL BE BASED ON APPLICABLE NFPA STANDARDS, WHEN |
| | AVAILABLE, OR ALTERNATIVE ENGINEERING SOURCES AND GOOD |
| | ENGINEERING PRACTICE WHEN REQUIRED, AND SHALL COMPLY |
| | WITH THE PROVISIONS OF RULE 61G15-33.006, F.A.C. |
| | SPECIFIC AUTHORITY 471.008, 471.033(2) FS. |
| | LAW IMPLEMENTED 471.033 FS. |
| | HISTORY--NEW 5-19-93, FORMERLY 21H-32.008. |
| | |
| | PLEASE PROVIDE GREATER DETAIL AS REQUIRED BY THE F.A.C. |
| | |
| | |
| | 2A) THE FIRE ALARM SHALL BE INSTALLED UNDER SEPARATE |
| | PERMIT & SHOP DRAWINGS. |
| | |
| | PLEASE PROVIDE AN APPLICABLE NOTE OF ACKNOWELDGMENT ON |
| | THE F.A.C. DOCUMENTS NOTED IN # 2. |
| | |
| | |
| | |
| | 3) WHEN RESUBMITTING, PLEASE PROVIDE PLAN SHEET |
| | REVISION CLOUDS OR NUMBERED NARRATIVE RESPONSES TO THE |
| | ABOVE. |
| | |
| | |
| | 4) ADDITIONAL COMMENTS MAY BE PROVIDED ON THE |
| | RE-SUBMITTAL OF THE ABOVE. |
| | |
| | |
| | PETER LEDUC |
| | FIRE MARSHAL |
| | 561-804-4709 |
| | [email protected] |
| | |
