Microfiche records prior to 2006 have not been completely digitized and may not be available yet on PRO. If you can not find what you are looking for please submit a records request.
Permit Review Detail
Review Status: Completed
Review Details: SITE and/or GRADING
Permit Number - DP15-0054
Review Name: SITE and/or GRADING
Review Status: Completed
| Review Date | Reviewer's Name | Type of Review | Description | Status | Comments |
|---|---|---|---|---|---|
| 03/31/2015 | RBROWN1 | ADA | REVIEW | Passed | |
| 04/14/2015 | STEVE SHIELDS | ZONING | REVIEW | Reqs Change | CDRC TRANSMITTAL TO: Development Services Department Plans Coordination Office FROM: Steve Shields Lead Planner PROJECT: Mobile Mini Development Package (1st Review) DP15-0054 TRANSMITTAL DATE: April 14, 2015 DUE DATE: April 23, 2015 COMMENTS: Please resubmit revised drawings along with a detailed response letter, which states how all Zoning Review Section comments were addressed. This plan has been reviewed for compliance with the Unified Development Code (UDC) Administrative Manual (AM) Section 2-06. Also compliance with applicable development criteria for the proposed use as listed in the City of Tucson Uniform Development Code (UDC) and the UDC Technical Standards Manual (TSM). The review comments include the actual standard first with the applicable Administrative Manual section number and the following paragraph is the actual comment related to the specific item that must be addressed. If you need to review the sections listed below click on the link or copy it in the address bar of your internet program. http://www.amlegal.com/nxt/gateway.dll/Arizona/tucson_az_udc/administrativemanual?f=templates$fn=default.htm$3.0$vid=amlegal:tucson_udc_az This link will take you directly to the section used for the standards review. The UDC & TSM requirements are in the Unified Development Code and can be viewed at the same web link as above Section 3.3.3.G.5.c UDC, An applicant has one year from the date of application to obtain approval of a site plan that complies with zoning and other development requirements in effect at the time of application, unless an ordinance adopted by Mayor and Council during this period states otherwise. A site plan application that has been in review for a period of one year and has not yet been approved is considered denied. To continue the review of a site plan for the property, a new site plan must be submitted that complies with regulations in effect at the time of re-submittal. The new submittal initiates a new one-year review period. One year Expiration date is March 25, 2016. SECTION 2-06.0.0: DEVELOPMENT PACKAGE (TENTATIVE PLATS AND SITE PLANS) Section 2-06.1.0 GENERAL 2-06.2.0 APPLICATION SUBMITTAL REQUIREMENTS 2-06.3.0 FORMAT REQUIREMENTS 2-06.4.0 CONTENT REQUIREMENTS 2-06.5.0 FLEXIBLE LOT DEVELOPMENT (FLD) - ADDITIONAL REQUIREMENTS 2-06.1.0 GENERAL 2-06.1.1 PURPOSE This standard has been prepared for the purpose of informing applicants of the submittal and review requirements for development package documents to assure proper and adequate information is presented in a consistent manner, thereby providing the basis for an efficient and timely review. The development package documents are prepared in support of applications for building permits and related reviews. The information that is requested establishes the basis upon which the project will be approved and could affect what is required of the property in the future, should there be a proposal for expansion or for a different use of the property. This standard does not waive any applicable city regulations or codes. 2-06.1.2 APPICABILITY This standard shall be used for all site plans and tentative plats submitted to PDSD for review. 2-06.2.1 APPLICATION SUBMITTAL REQUIREMENTS Development Package applications are available from PDSD. Completed applications and accompanying materials shall be submitted to PDSD. Incomplete or inaccurate applications will not be accepted, nor will any application in which the pre-application conference or neighborhood meeting requirements have not been met. The types of documents and the specific number of copies required of each of the documents are on the PDSD website or may be obtained from PDSD. Resubmittals of development packages require a comment response letter that details how all previous comments have been addressed. Provide the same number of copies of the comment response letter as plans provided. The following documents and information shall be submitted upon application: 2-06.2.1 Application Form A completed application signed by the property owner or authorized designee; 2-06.2.2 Development Package A development package must be prepared to the format and content requirements described herein; 2-06.2.3 Related Reviews In addition to the plan process, a project may require review for other types of plans and documents. The applications for those processes are submitted to the appropriate department for review and approval. These related reviews can be applied for so that review can occur concurrently with the development package application. However, it must be understood that, should the related application be approved subject to conditions or denied, this may affect the; 2-06.2.4 Concurrent Reviews The development package is designed to allow for concurrent review of any site related reviews. Concurrent review means that all plans and documents needed for the review are submitted as one package. Examples of site related reviews include but are not limited to: site plans, landscape plans, NPPO plans, water harvesting plans, grading plans, SWPPP plans, floodplain use permits, and overlay reviews. Separate applications are often required for the different site related reviews even if the plans are submitted concurrently; and, 2-06.2.5 Fees Fees in accordance with Section 4-01.0.0, Development Review Fee Schedule. 2-06.3.0 FORMAT REQUIREMENTS 2-06.3.1 - Each sheet shall measure 24 inches by 36 inches and include a minimum one inch margin on left side and one-half inch margin on all other sides to facilitate efficient record keeping. A larger sheet format may be used with the approval of the Planning and Development Services Department (PDSD). 1) COMMENT: 2-06.3.2 - All mapped data shall be drawn at an engineering scale having no more than 50 feet to the inch. This scale is the minimum accepted to assure the plan will be legible during review and when digitized and/or reduced for record-keeping purposes. The same scale shall be used for all sheets within the set. Smaller scales (60:1 or greater) may be used for some or all of the sheets with the prior approval of PDSD when it is determined legibility and the ability to be digitized and/or reduced for archiving will not be affected. 2) COMMENT: Revise the plans to meet this standard. 2-06.3.12 - An index of sheets in the development package shall be provided on the first sheet. 3) COMMENT: Remove the Individual Parking Plan (IPP) from this development package as it is a separate submittal. CONTENT REQUIREMENTS 2-06.4.2 - The title block shall include the following information and be provided on each sheet: 2-06.4.2.D - The page number and the total number of pages in the package (i.e., sheet xx of xx). 4) COMMENT: The total number sheets will change as the IPP is to be removed. 2-06.4.3 - The administrative street address and relevant case numbers (development package document, subdivision, rezoning, board of adjustment, DDO, MDR, DSMR, overlay, etc.) shall be provided adjacent to the title block on each sheet. 5) COMMENT: Remove the address from the title block and provided it adjacent to the title block on each sheet. 6) COMMENT: Provide the development package case number, DP15-0054, adjacent to the title block on each sheet. 7) COMMENT: Once approved provide the IPP case number adjacent to the title block on each sheet. 2-06.4.4 - The project-location map to be located on the first sheet of the development package in the upper right corner, shall cover approximately one square mile, be drawn at a minimum scale of three inch equals one mile, and provide the following information. 2-06.4.2.B - Identify major streets and regional watercourses within the square mile area and all streets that abut the subject property; and, 8) COMMENT: Identify the Santa Cruz river on the location map. 2-06.4.7 - General Notes The following general notes are required. Additional notes specific to each plan are required where applicable. 2-06.4.7.A.6.a - List additional applications and overlays, by case number (if applicable), in lower right corner of each sheet. As a general note provide the type of application processed or overlays applicable, a statement that the project meets the criteria/conditions of the additional application or overlay, the case number, date of approval, what was approved, and the conditions of approval, if any. 9) COMMENT: If approved provide a general note stating the IPP case number, date of approval, what was approved and if applicable in conditions of approval. 2-06.4.7.A.8 - For development package documents provide: 2-06.4.7.A.8.a - Floor area for each building; 10) COMMENT: As a general note provide the floor are for each building. 2-06.4.8 - Existing Site Conditions The following information shall be provided on the plan/plat drawing to indicate the existing conditions on site and within 50 feet of the site. On sites bounded by a street with a width of 50 feet or greater, the existing conditions across the street will be provided. 2-06.4.8.A - Provide site boundary/subdivision perimeter information, including bearing in degrees, minutes, and seconds, with basis for bearing noted, together with distances in feet, to hundredths of a foot, or other functional reference system. 11) COMMENT: As this site is made up of three parcels a lot combination is required. Provide a copy of the approved Pima Country Combo Request form with the next submittal. 12) COMMENT: Remove the reference to Headlee Roofing and the lot reconfiguration from the plan as this process has been completed. 2-06.4.8.B - All easements shall be drawn on the plan. The recordation information, location, width, and purpose of all easements on site will be stated. Blanket easements should be listed in the notes, together with recordation data and their proposed status. Should an easement not be in use and be proposed for vacation or have been abandoned, so indicate. However, should the easement be in conflict with any proposed building location, vacation of the easement shall occur prior to approval of plan unless written permission from easement holder(s) is provided. 13) COMMENT: Provide the recordation information for all existing easements shown on the plan. 2-06.4.8.C - The following information regarding existing private or public right-of-way adjacent to or within the site shall be provided: the name, right-of-way width, recordation data, type and dimensioned width of paving, curbs, curb cuts, and sidewalks. 14) COMMENT: Provide the dimensioned width of paving, curbs, and curb cuts for the Glenn right-of-way (ROW). 15) COMMENT: Sheet 2 shows Glenn Street as an "MSR STREET". This section of Glenn is not shown on the COT MS&R maps. 2-06.4.9 - Information on Proposed Development The following information on the proposed project shall be shown on the drawing or added as notes. 2-06.4.9.H.2 - Show future and existing sight visibility triangles (SVTs). On a designated MS&R street, the sight visibility triangles are based on the MS&R cross-section. 16) COMMENT: If applicable show the required SVTs on the plan. 2-06.4.9.H.5 - If utilizing parking area access lanes (PAALs), they shall be designed in accordance with Section 7.4.6, Motor Vehicle Use Area Design Criteria, of the UDC. 17) COMMENT: Provide a fully dimensioned vehicle use area. 18) COMMENT: It does not appear that the vehicle use area that accesses the 'EMPLOYEE PARKING SPACES" meets the requirements of UDC Article 7.4.6.I 19) COMMENT: Per UDC Article 7.4.6.H Barriers, such as post barricades or wheel stop curbing, are required in a vehicular use area to prevent vehicles from extending beyond the property lines, to prevent cars from damaging adjacent landscaping, walls, or buildings, overhanging adjacent sidewalk areas, and/or driving onto unimproved portions of the site. That said some type of barrier is required between the PAAL and the landscape area along the north side of the site. 2-06.4.9.H.5.a - Show all motor vehicle off-street parking spaces provided, fully dimensioned. As a note, provide calculations on the number of spaces required (include the ratio used) and the number provided, including the number of spaces required and provided for the physically disabled. The drawing should indicate parking space locations for the physically disabled. A typical parking space detail shall be provided for both standard parking spaces and those for the physically disabled. For information on parking requirements for the physically disabled, refer to adopted building and accessibility codes of the City of Tucson. Design criteria for parking spaces and access are located in Section 7.4.6, Motor Vehicle Use Area Design Criteria, of the UDC. 20) COMMENT: Show all motor vehicle off-street parking spaces provided, fully dimensioned. 21) COMMENT: As a note, provide calculations on the number of spaces required (include the ratio used) and the number provided, including the number of spaces required and provided for the physically disabled. Zoning acknowledges that a vehicle parking calculation was provided on sheet 4 but as this sheet will not be part of the development package provide a calculation on the cover sheet. If does not appear that the building area shown on the vehicle parking calculation on sheet 4 includes the total gross floor area on the site. 22) COMMENT: A typical parking space detail shall be provided for both standard parking spaces and those for the physically disabled. 23) COMMENT: It does not appear that the 'EMPLOYEE PARKING SPACES" meet the requirements of UDC Article 7.4.6.I 2-06.4.9.H.5.d - Show bicycle parking facilities fully dimensioned. For specifics, refer to Section 7.4.9, Bicycle Parking Design Criteria, of the UDC. Provide, as a note, calculations for short and long term bicycle spaces required and provided. 24) COMMENT: Provide a short and long term bicycle parking space calculation that shows the required and provided number. Zoning acknowledges that a vehicle parking calculation was provided on sheet 4 but as this sheet will not be part of the development package provide a calculation on the cover sheet. Also it appears that In-Lieu fees are proposed instead of providing the required number of long term bicycle parking spaces. That said it does not appear that this site qualifies for In-Lieu fees, see UDC Article 7.4.8.B.1.a.(2) The in-lieu fee may not be used if there are vehicular use areas, plazas, exterior courtyards, or other open areas on the site, other than required landscaping, large enough, separately or in combination, to accommodate all or a portion of the required bicycle parking. 25) COMMENT: Provide a long term bicycle parking detail that shows how the requirements of UDC Article 7.4.9.D are met. 2-06.4.9.O - All applicable building setback lines, such as erosion hazard, floodplain detention/retention basins, and zoning, including sight visibility triangles, will be shown. 26) COMMENT: Show the required street perimeter yard setbacks from the proposed structure to the street property line, see UDC Article 6.4.5.C.1. 2-06.4.9.R - Show on-site pedestrian circulation and refuge utilizing location and the design criteria in Section 7-01.0.0, Pedestrian Access, of the Technical Standards Manual. 27) COMMENT: Per TSM 7-01.4.1.A At least one sidewalk is required to a project from each street on which the project has frontage, unless there is no vehicular access from a street because of a physical barrier, such as a drainageway or an unbroken security barrier (e.g., a wall or fence). The sidewalk should be located to minimize any conflict with vehicular access to the project. That said provide a sidewalk/pedestrian path from the structures on site to the ROW. 28) COMMENT: Per TSM 7-01.4.1.B A sidewalk is required adjacent and parallel to any access lane or PAAL on the side where buildings are located. That said provide a sidewalk along the north side of the covered work area, restrooms, office, east side of the offices, west side of the restrooms. 29) COMMENT: Per TSM 7-01.4.1.C A sidewalk is required adjacent to any parking space accessed by a PAAL where the space is located on the same side of the PAAL as any building and no other parking spaces or PAALs intervene. That said provide a sidewalk along the south side of the office. See red line for sidewalk requirements. 2-06.4.9.T - Show refuse collection areas, including locations of dumpsters, screening location and materials, and vehicle maneuverability, fully dimensioned, and access route. If dumpster service is not proposed, indicate type of service. For specific information on refuse collection, refer to Section 8-01.0.0, Solid Waste and Recycle Disposal, Collection, and Storage, of the Technical Standards Manual. Refuse collection on all projects shall be designed based on that section, even if collection is to be contracted to a private firm. 30) COMMENT: Show the refuse collection area on the plan. 2-06.4.9.W - Indicate the locations and types of proposed signs (wall, free-standing, pedestal) to assure there are no conflicts with other requirements and that minimal locational requirements can be met. Indicate if there are any existing billboards on site. Compliance to the Sign Code, Chapter 3 of the Tucson Code, is required. 31) COMMENT: If applicable show the location of any existing or proposed signs on the plan. 32) COMMENT: Provide a general note on the plan "ALL SIGNAGE TO BE UNDER SEPARATE PERMIT". If you have any questions about this transmittal, please Steve Shields, (520) 837-4956 or Steve.Shields@tucsonaz.gov RESUBMITTAL OF THE FOLLOWING IS REQUIRED: Revised development package, Approved Pima Country Combo Request form. |
| 04/15/2015 | MARTIN BROWN | FIRE | REVIEW | Reqs Change | Unable to determine how a fire truck can access property beyond the entrance. Please clarify. |
| 04/21/2015 | ANDREW CONNOR | LANDSCAPE | REVIEW | Reqs Change | ADMINISTRATIVE MANUAL SECTION 2-10.0.0: LANDSCAPE PLAN REQUIREMENTS Identification and Descriptive Data All improvements and site information, such as adjacent rights-of-way and property lines, shown on the landscape plan will be identical in size and location to those shown on the base plan (site plan or tentative plat). Should amendments be required to the base plan through the review process, the same amendments will be made to the landscape plan which will then be resubmitted along with the base plan. The landscape plan will contain the following identification in the lower right corner of each sheet: Any relevant case number(s) for reviews or modifications that affect the site Maintenance Schedule Pruning schedules to show that plant material will maintain pedestrian and vehicular clearances or that the material will establish opaque hedge screens, if required; Replacement criteria, should plant material not survive; Replacement or upkeep maintenance schedules for inert ground cover materials; Upkeep maintenance schedules for exterior hardscape materials; and, Maintenance and replacement schedules for irrigation systems. Grading Information The methods by which water harvesting or storm water runoff is used to benefit the planting areas on the site. Irrigation Plan Type of water conserving irrigation systems proposed and differentiation between systems for the different water use zones on the site; Source of irrigation water; Indicate potable or reclaimed water use. Reclaimed water system specifications, if used; System specifications and system design and layout (Section 4-01.4.2, Irrigation Standards, of the Technical Standards Manual); Extent of supplementary irrigation in each planting area, provided by water harvesting methods; Point of drainage off roof areas, amount of flow, and disposition of flow; Temporary systems proposed to establish native seeded areas; The length of irrigation duration (e.g., for native plat material, automatic drip for two years or until established); and, The extent to which systems are proposed within the public right-of-way. UNIFIED DEVELOPMENT CODE ARTICLE 7: DEVELOPMENT STANDARDS The standards in this Section 7.6.4. apply to all developments that provide more than four motor vehicle parking spaces. Landscape must be submitted for review. LANDSCAPING AND SCREENING To enhance the visual appearance of the streetscape, a street landscape border is required in accordance with Table 7.6.4-1 along the street frontage of a site as follows: Fifty percent or more of the area of the street landscape border must be covered with shrubs or vegetative ground cover. The required ground coverage must be achieved within two years from the date of planting. The 50% coverage is in addition to the screening and canopy tree requirements. Provide coverage and calculation on landscape plan. Ensure that all Zoning and Engineering comments and concerns are addressed. Additional comments may apply. |
| 04/22/2015 | ANDREW CONNOR | NPPO | REVIEW | Approved | |
| 04/23/2015 | LOREN MAKUS | ENGINEERING | REVIEW | Reqs Change | 1. The drainage report is accepted for development package review. 2. Provide dimensions for vehicle use areas, parking spaces, radii, buildings and other features. 3. Fully dimension the right of way features including curb locations. |
| 04/23/2015 | ROBERT SHERRY | PLUMBING-COMMERCIAL | REVIEW | Reqs Change | Revise the site drawing to include the following information: a. The location and size of water lines, and fire hydrants. b. The invert and rim elevations of the manholes upstream and downstream of the proposed point of connection to the 8" public sewer; along with the Pima County Wastewater Management Department (PCWMD) reference number. c. The proposed point of connection to the existing 8" public sewer. d. The locations of gas lines, electric and telephone lines, poles, and communications cables, and street lights. e. The first floor elevation of any building that will contain plumbing fixtures. Reference: City of Tucson Administrative Manual No. 2-06.0.0, Section 4.8 and Section 107.2.13, IBC 2012. |
| 04/23/2015 | RONALD BROWN | H/C SITE | REVIEW | Reqs Change | 1. Provide an accessible route from the public right of way to the accessible parking spaces and to all building entrances on the site. a. Insure accessible route slopes comply with the 2009 ICC A117.1, Section 403.3. 2. Provide a large scale detail of the accessible parking space including all accessible requirements such as dimensioning, van accessible space, grades, markings, signage, access to and the accessible route. 3. Provide a large scale sign detail including a van accessible sign. END OF REVIEW |