My WebLink
|
Help
|
About
|
Sign Out
PC-98-06
City of Pleasanton
>
BOARDS AND COMMISSIONS
>
PLANNING
>
RESOLUTIONS
>
1990-1999
>
1998
>
PC-98-06
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/15/2006 9:32:58 AM
Creation date
12/10/2003 2:29:40 PM
Metadata
Fields
Template:
CITY CLERK
CITY CLERK - TYPE
RESOLUTIONS
DOCUMENT DATE
1/28/1998
DOCUMENT NO
PC-98-06
DOCUMENT NAME
PUD-81-30-75D
NOTES
SHAKLEE CORP
NOTES 3
CORPORATE CAMPUS
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
14
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
<br />Resolution No. PC-98-06 <br />Page 9 <br /> <br />46. Each applicant is required to submit a Declaration shall post National Fire Protection 704 <br />identification on the building according to the City's "Hazardous Materials Identification <br />Sign" procedures, <br /> <br />47. The developer shall ensure that fire protection facilities including, but not limited to, all <br />surface roads, fire hydrants, and a water supply capable of furnishing the required fire <br />flow is installed and serviceable prior to and during the time of construction framing. <br />When alternative methods of protection proposed, this requirement may be waived or <br />modified, subject to review and approval of the Fire Chief. Proposed alternative methods <br />of fire protection shall be submitted in writing to the Fire Chief. Installation of the <br />alternative fire protection methods shall not start without the approval of the Fire Chief. <br /> <br />48. The Fire Chief and City Engineer shall approve the number, type, and location of all <br />public fire hydrants. The Fire Chief and the Chief Building Inspector shall approve the <br />number, type, and location of private fire hydrants. <br /> <br />49. All public and private streets, driveways, aisles, and alleys designated as fire lanes by the <br />Fire Chief shall be maintained in accordance with Articles 9 and 10 ofthe Uniform Fire <br />Code which includes towing of vehicles illegally parked on the fire lanes. All roads on <br />the site shall be accessible at all times from the start of construction until the project is <br />completed. Fire lane curbs shall be painted red with "No Parking Fire Lane" or posted <br />with "No Parking Fire Lane" signs installed as required by the vehicle code. <br /> <br />50. The pedestrian pathways and all fire access ways on the site shall be designed to meet the <br />structural requirements for the weight of fire apparatus. Calculations demonstrating the <br />structural strength and turning radii of these pathways shall be reviewed and approved by <br />the Fire Marshall prior to the issuance of building permits for the first Phase I building. <br /> <br />51. The Fire Chief shall issues a permit prior to any installation of a fire detection, alarm, and <br />occupant notification system. All sprinkler system water flow and control valves shall be <br />complete and serviceable prior to final inspection. Prior to occupancy of a building <br />equipped with fire alarm systems, the Fire Department shall test and witness the fire <br />alarm systems. <br /> <br />52. All portions of a building shall have installed within a 75 foot radius a fire extinguisher <br />with a minimum rating of2-A:IO-B:C. <br /> <br />53. Each commercial or industrial building entry point shall have a Knox Box as approved by <br />the Fire Chief. Each Knox Box shall have the entry types and number of keys located in <br />the Box. <br /> <br />54. The developer shall post address numerals on the building so as to be plainly visible from <br />all adjoining streets or driveways during both daylight and night time hours. Tenant <br />spaces shall be identified as determined by the City. <br />
The URL can be used to link to this page
Your browser does not support the video tag.