Permit Review Detail
Review Status: Completed
Review Details: SITE and/or GRADING
Permit Number - DP18-0037
Review Name: SITE and/or GRADING
Review Status: Completed
| Review Date | Reviewer's Name | Type of Review | Description | Status | Comments |
|---|---|---|---|---|---|
| 02/09/2018 | SSHIELD1 | FIRE | REVIEW | Needs Review | |
| 02/09/2018 | ANDREW CONNOR | NPPO | REVIEW | Approved | |
| 02/09/2018 | ANDREW CONNOR | LANDSCAPE | REVIEW | Reqs Change | A detailed landscape plan is required with submittal of a development package. In accordance with Section 2-10.0.0, Landscape Plan Requirements. No landscape plans were submitted. A Board of Adjustment variance will be necessary for the elimination of any landscape requirements. |
| 02/09/2018 | SSHIELD1 | H/C SITE | REVIEW | Reqs Change | See Zoning comments |
| 02/09/2018 | STEVE SHIELDS | ZONING | REVIEW | Reqs Change | CDRC TRANSMITTAL TO: Development Services Department Plans Coordination Office FROM: David Rivera PDSD Zoning Review Section PROJECT: DP18-0037 Development Package (1st Review) 5602 E 22nd Street TRANSMITTAL DATE: January 10, 2018 DUE DATE: January 9, 2018 COMMENTS: Please resubmit revised drawings and any redlined plans along with a detailed response letter, which states how all Zoning Review Section comments were addressed. 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 , 2018. (This plan was submitted incorrectly as a T.I. rather than as a Development Package) The expiration date will be provided once the plan has been re-submitted as a DP for review. ***Zoning has done a DP review of the plans submitted even though the plans were submitted by the applicant as a tenant improvement. All comments are related to standards applicable to a development package review only. A full review will have to be completed by all applicable reviewers once the DP is resubmitted correctly which include a landscape and NPPO plan or exception and any additional documentation that may be requested. SECTION 2-06.0.0: DEVELOPMENT PACKAGE (TENTATIVE PLATS AND SITE PLANS) Section 2-06.3.0 FORMAT REQUIREMENTS 2-06.3.5 - A three-inch by five-inch space shall be reserved in the lower right quadrant of each sheet for an approval stamp. 1. COMMENT: Remove from the plan sheets the Approvals block. The reviewers will add their signatures in the PDSD approval stamp. CONTENT REQUIREMENTS 2-06.4.1 - The name, mailing and email addresses, and phone number of the primary property owner of the site, the developer of the project, registrant(s), and other person(s), firm(s), or organization(s) that prepared the development package documents shall be provided on the right half of the cover sheet. The applicable registration or license number shall be provided if prepared by or with the assistance of a registered professional, such as a surveyor, architect, landscape architect, or engineer. All sealing shall be consistent with Arizona Board of Technical Registration guidelines. 2. COMMENT: On the cover sheet, list the phone number and email address for the owner/developer. 2-06.4.2 - The title block shall include the following information and be provided on each sheet: 2-06.4.2.A - The proposed name of the project or subdivision, or if there is no name, the proposed tenant's name; 3. COMMENT: List in the title block of all sheets, the name of the project or as noted by the standard above. 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. 4. COMMENT: This project has not been assigned a DP case number because it was not submitted as a DP. When the plan is resubmitted as a DP the project will be assigned a DP case number. List the number in the lower right corner of all plan sheets. 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.4.C - Section, township, and range; section corners; north arrow; and the scale will be labeled. 5. COMMENT: Add the following under the location map: "In the NW ΒΌ of Section 24. T.14, R.14, E., G.&S.R.M. City Of Tucson, Pima County, Arizona" 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 - Zoning and Land Use Notes 2-06.4.7.A.4 - Identify the existing and proposed use of the property as classified per the UDC. List all UDC sections applicable to the proposed uses. 6. COMMENT: Revise Site Note 3 as follows; Exist/Proposed Uses - Food Service use Subject to UDC 4.9.4.M.1 and.2, Administrative Office Subject to UDC 4.9.13.0. 2-06.4.7.A.6 - If a plan or plat is prepared in conjunction with other applications or overlays or the parcel being developed is subject to conditions of an application processed previously, additional information must be added to the plan. Such applications and overlays include, but are not limited to: annexations; rezonings; special exceptions; Board of Adjustment variances; Design Development Options; Technical Standard Modification Request; overlays (Airport Environs Zone, Environmental Resource Zone, Gateway Corridor Zone, Hillside Development Zone, Historic Preservation Zone, Major Streets and Routes, Rio Nuevo District, Scenic Corridor Zone, WASH); Modification of Development Regulations through the Downtown Area Infill Incentive District or Rio Nuevo District; Downtown Heritage Incentive Zone; or, Design Review Board. Provide the following information on the plan. 7. COMMENT: This project will be subject to Board of Adjustment variance approval. If variances are required for approval of the site as proposed list the case number in the lower right corner of all plan sheets and list as a general note the case number, date of approval and variances requested and approved. 2-06.4.7.A.6.b - If there is more than one lot within the site, the note should specify which lots are affected by the additional applications or overlay zones. 8. COMMENT: This project is over two parcels. Prior to approval of the development package a Pima County Tax Parcel combo will be required. Contact the Pima County Assessor's office for information on the parcel combo process. 2-06.4.7.A.8 - For development package documents provide: 2-06.4.7.A.8.c - Percentage of building, lot area, or vehicular use area expansion. If the building(s) or lot area have been previously expanded, those calculations shall be included; and, 9. COMMENT: Provide the expansion calculations as noted by the standard above. 2-06.4.7.A.8.d - When the proposed site is part of a larger site, the calculations encompass the entire site, whether existing or proposed. If the project is being phased, calculations must show that, at each phase, requirements are being met. 10. COMMENT: If this project is to be phased provide the information as noted by the standard above. 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. 11. COMMENT: Provide the information as noted by the standard above. 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. 12. COMMENT: Distance labeled for the combined north property lines is incorrect. Review and label the correct distance. 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: If applicable provide the easement information as noted by the standard above. 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: Label the face of curb to property line along the along the Jefferson Avenue street frontage. 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.G - If the project is to be phased, provide calculations, setbacks, etc., to indicate that each phase complies with all requirements as a separate entity. Show phase lines on the drawing. Show and label any temporary improvements that may be needed to make the site function for each phase as one entity. If such temporary improvements are off the site of the phase under consideration, a temporary easement or other legal documentation to assure legal use of the property is required. Note recording information. 15. COMMENT: If applicable, provide the information as noted by the standard above if this will be a phased development. 2-06.4.9.H.2 - Show future and existing sight visibility triangles. On a designated MS&R street, the sight visibility triangles are based on the MS&R cross-section. 16. COMMENT: draw and label Site visibility triangles. Contact Loren Makus for information on the requirements for SVT's on this site. Because of existing conditions and a greater than 25% expansion TSMR or variances may be required. 17. COMMENT: See the attached reference documents related to a few of the zoning comments. 2-06.4.9.H.4 - Indicate if existing streets are public or private; provide street names, widths, curbs, sidewalks, and utility locations, all fully dimensioned. 18. COMMENT: Label the frontage road as Public Street. 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. 19. COMMENT: An extruded curb will be required at the back up spur. The bollards will have to be placed to prevent vehicles from The proposed bollards at the east end of the PAAL will have to be placed 3 back from the current location. See UDC Section 7.4.6.F.4 for more information on back up spur design criteria. 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: Due to full code compliance for this project all parking spaces must be provided on site and must comply with the UDC Section 7.4.6 Motor Vehicle Use Area Design Criteria. It is clear that site is non-conforming for several requirements such as, parking lot design, pedestrian circulation, landscaping, bicycle parking, refuse enclosures etc. As part of the full code compliance these items and other may have to be brought into current UDC or Technical standards or approved through, PDMR, TSMR, or Board of adjustment variances. The following is related strictly to parking lot design; Backing out onto the right of way is not allowed a variance will be required, Back up spur must be revised, A minimum 4 four wide sidewalk is required between the building and the parking spaces (front), A minimum four wide sidewalk is required between the rear PAAL and the building, The number of parking spaces required for this development is 31 spaces which includes 2 Accessible parking spaces of which one must be a van space, Per the vehicle parking calculations indicate that reductions are being used to reduce the number of required vehicle parking spaces. Two accessible spaces are required based on a total of 31 spaces required per code. One additional accessible spaces has been provided which allows a reduction of two vehicle parking spaces. Also six additional long term bicycle parking spaces have been provided that allows a reduction of one vehicle parking space. Between the two reductions the overall vehicle parking spaces required is 28. 27 spaces have been provided, a board of adjust variance for one vehicle parking space is required or add an additional Accessible parking spaces that meets the design requirements and includes an acceptable accessible aisle, ramp and connection to the accessible pedestrian path. The two parking spaces at the north end of "Building C" must have a minimum four foot wide sidewalk between the spaces and the building. 2-06.4.9.J - If street dedication is not required or proposed and the project site is adjacent to a Major Street or Route, draw the Major Street right-of-way lines for those streets. (Add the MS&R future sidewalk, right-of-way lines, sight visibility triangles, etc.) 21. COMMENT: Add the information for 22nd Street as noted by the standard above. 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. 22. COMMENT: Label the existing and future building setbacks. The setbacks can be determined by utilizing the developing area setbacks of 21 or the height from existing and future back of curb along the 2nd Street frontage and 21 feet or the height from the nearest edge of travel lane along the Jefferson Avenue frontage. It was noticed (in doing a comparison of the drawing with the current aerial photograph) that a structure approximately 12' x 18' was not shown on the plan. Clarify if this structure is to be demolished otherwise the structure must be drawn and labeled on the plan. 2-06.4.9.Q - Provide the square footage and the height of each commercial, industrial, or business structure and the specific use proposed within the footprint of the building(s). 23. COMMENT: In order to verify the square footage of the buildings, dimension the length and width of the buildings and the clearly define the patio area and dimension. Label within the building footprint the heights of Building A, B and C. 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. 24. COMMENT: All onsite sidewalks must be a minimum of four feet clear in width and installed to avoid any obstruction which decreases the minimum width to less than four feet. The sidewalk along the south side of the buildings must be clearly dimensioned, be physically separated from the vehicular use area and constructed of concrete or a similar material as noted in Technical Standards 7.4.3.C. Label the cross and running slopes for all sidewalks and ramps. Accessible ramps may not be constructed within the vehicular use area as depicted for the ramp adjacent to Building "B". See redlines on sheet two for requested dimensions, additional sidewalk and clarifications. Clarify how pedestrian access to the buildings from the south parking area is provided? Per T.S. Section 7-01.3.3.B, The areas within the development which must be connected include, but are not limited to, all buildings, all bicycle and vehicle parking areas, all recreation areas, all dumpster areas, and all other common use areas. Demonstrate compliance for this requirement out to the dumpster. 2-06.4.9.V - For gang mailboxes indicate location to assure there are no conflicts with other requirements, such as pedestrian accessibility, utilities, and landscaping. 25. COMMENT: Clarify by general note or drawing, how mail is to be provided, gang mailboxes, to each building etc. 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. 26. COMMENT: If applicable draw and label any proposed ground mounted signage. It does not appear that the existing sign depicted on the site plan is located in the correct location. Verify location and adjust the plan for correctness. If you have any questions about this transmittal, Contact David Rivera on Tuesday or Wednesday at (520) 837-4957 or by email David.Rivera@tucsonaz.gov or contact Steve Shields any time during the week at (520) 837-4956 or email Steve.Shields@tucsonaz.gov RESUBMITTAL OF THE FOLLOWING IS REQUIRED: Revised development package |
| 02/09/2018 | SSHIELD1 | PLUMBING-COMMERCIAL | REVIEW | Needs Review | |
| 02/09/2018 | SSHIELD1 | ENGINEERING | REVIEW | Needs Review |
Final Status
| Task End Date | Reviewer's Name | Type of Review | Description |
|---|---|---|---|
| 02/09/2018 | QJONES1 | OUT TO CUSTOMER | Completed |
| 02/09/2018 | QJONES1 | REJECT SHELF | Completed |
| 02/09/2018 | QJONES1 | APPROVAL SHELF | Completed |