Microfiche records prior to 2006 have not been completely digitized and may not be available yet on PRO. If you cannot find what you are looking for please submit a records request.

Permit Review Detail

Permit Number: DP14-0210
Parcel: 141185910

Review Status: Completed

Review Details: DEV PKG - RESUBMITTAL

Permit Number - DP14-0210
Review Name: DEV PKG - RESUBMITTAL
Review Status: Completed
Review Date Reviewer's Name Type of Review Description Status Comments
01/08/2015 CPIERCE1 START PLANS SUBMITTED Completed
01/13/2015 KEN BROUILLETTE FIRE REVIEW Reqs Change COULD NOT FIND HYDRANT AS PREVIOUSLY ASKED
01/15/2015 STEVE SHIELDS ZONING REVIEW Reqs Change 2101 CDRC TRANSMITTAL

TO: Development Services Department
Plans Coordination Office

FROM: Steve Shields
Lead Planner

PROJECT: Old Vail Plaza
Development Package (2nd Review)
DP14-0210

TRANSMITTAL DATE: January 16, 2015

DUE DATE: January 23, 2015

COMMENTS: Please resubmit revised drawings along 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 November 17, 2015.

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.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.

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.

1. COMMENT: As it appears that the majority of these plans were not produced by Dowl provide the name, mailing and email addresses, and phone number of organization(s) that prepared the development package documents, i.e. AGS & Jocobs on the cover sheet.

2-06.4.2 - The title block shall include the following information and be provided on each sheet:

COMMENT: Provided a title block on the first 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;

2. Addressed COMMENT: Provide the project name within the title block on all sheets including sheets 1 &2 .

2-06.4.2.B - A brief legal description and a statement as to whether the project is a resubdivision are to be provided. On resubdivisions, provide the recording information of the existing subdivision plat;

3. Addressed COMMENT: Provide a brief legal description with in the title block on all sheets including sheets 2 -24.

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. This comment was not addressed, remove the address from the title block and provide the address adjacent to the title block on each sheet. COMMENT: Provide the street address adjacent to the title block on all sheets.

5. Addressed COMMENT: Provide the development package case number, DP14-0210, adjacent to the title block on all sheets.

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

6. COMMENT:

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.

7. This comment was not addressed. COMMENT: Provide a general note stating "EXISTING USE VACANT, PROPOSED USE FOOD SERVICE: EXCLUDING SOUP KITCHENS, SUBJECT TO USE SPECIFIC STANDARDS 4.9.4.M.1 & 5 and 4.9.13.O.

2-06.4.7.A.7 - If the property is part of a subdivision plat that is being reviewed or has been recorded, provide the case number in the lower right corner of each sheet. As a general note, indicate whether the project is part of a Flexible Lot Development (FLD), condominium, or another similar type project.

8. Addressed COMMENT: Provide the subdivision case number, S07-156, adjacent to the title block on all sheets

2-06.4.7.A.8 - For development package documents provide:

2-06.4.7.A.8.a - Floor area for each building;

9. Addressed COMMENT: Provide the floor area for the building only

2-06.4.7.A.8.b - Percentage and area in square feet of building and accessory building coverage;

10. This comment was not addressed. COMMENT: Provide a floor area ratio (FAR) calculation for this building only on the plan, see UDC Section 6.4.6.

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. This comment was not addressed. No final plat or survey provided. COMMENT: Clarify what the center line with perimeter information, bearings and distance, shown on the plan is for. This boundary does not match the final plat in size shape or location. Show the correct property boundary per final plan S07-157 or if the property boundary shown is proposed a revised tentative and final plat will be required.

12. This comment was not addressed. COMMENT: Clearly show the over-all site street property line along Houghton Road.

Additional Comment - Based on Development Package (Tentative Plat) DP14-0248 show the parcel boundaries along with the bearings & distance for lot 8 on this plan.

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. This comment was not addressed. Show all easements on the site plan. Coordinate your response with Development Package (Tentative Plat) DP14-0248. Based on DP14-0248.COMMENT: Show all easements within 50 feet of this site on the plan along with the recordation information.

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. This comment was not addressed. COMMENT: Provide the above information for Houghton Road on the plan.

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.F - All existing zoning classifications on and adjacent to the project (including across any adjacent right-of-way) shall be indicated on the drawing with zoning boundaries clearly defined. If the property is being rezoned, use those boundaries and classifications. The basis for this requirement is that some zoning requirements on a project are based on the zoning classification of adjacent property. Also, in some instances, each zone has to be taken into consideration on property that is split by two or more zoning classifications, as each may have different requirements.

15. This comment was not addressed. COMMENT: Show all zoning classifications on and adjacent to the project (including across any adjacent right-of-way) on the drawing with zoning boundaries clearly defined.

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.

16. COMMENT: Until the proposed phasing plan has been submitted and approved this development package cannot be approved.

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.

17. This comment was not addressed. COMMENT: Provide the above information for Houghton Road 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.

18. This comment was not addressed correctly. Coordinate your response with Development Package (Tentative Plat) DP14-0248. COMMENT: Per UDC Section 7.4.6.H.1 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 demonstrate on the plan how vehicles will be prevented from access unimproved portions of this 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.

19. This comment was not addressed correctly. Coordinate your response with Development Package (Tentative Plat) DP14-0248. Based on DP14-0248. The vehicle parking space calculation does not provide the ratio used. Based on a proposed building square footage of 1,949/100 the required number of vehicle parking spaces should be 19. COMMENT: Until the square footage for this building is provided, see comment 9, the required number of vehicle parking spaces cannot be verified. Zoning acknowledges that it appears that the provided number should more than exceed the required number. Provide the ratio used for this vehicle parking calculation. It appears that UDC requirements are proposed of the number of loading spaces, see comment 22. If this is the case than the vehicle parking space calculation will need to be revised also.

20. Detail 2 Sheet C-09 does not match DP14-0248. Coordinate your response with Development Package (Tentative Plat) DP14-0248. COMMENT: Provide a typical parking space detail for both standard parking spaces and those for the physically disabled on the plan.

21. Addressed COMMENT: Northwest of the northwest corner of the building there are two (2) vehicle parking spaces that are allowed to overhang the proposed sidewalk, show the 2'-6" overhang on the plan. It appears that a parking vehicle with encroach into the 4'-0" sidewalk in this area.

2-06.4.9.H.5.c - Show all loading zones, vehicle maneuverability fully dimensioned, and access route. Provide as a note the number of loading spaces required, the number provided, whether the loading space is a Type A or B as provided in UDC Section 7.5.4.

22. Addressed COMMENT: Based on the "GENERAL NOTES" table on sheet 2, Lot 8 requires one (1) 12 x 35 loading space. It appears that you are proposing to use the current UDC loading space requirements. If this is the case "GENERAL NOTES" table on sheet 2 will need to revised to reflect all UDC requirements or you will need to provide the required 12 x 35 loading space.

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.

23. COMMENT: The short and long term bicycle parking space calculation does not provide the number provided. Revise the calculation to include the number of short and long term bicycle parking. Coordinate your response with Development Package (Tentative Plat) DP14-0248.

24. This comment was not addressed correctly. The proposed short term bicycle parking detail does not meet the requirements of UDC Sections 7.4.9.B & C. Coordinate your response with Development Package (Tentative Plat) DP14-0248. COMMENT: Provide a short-term bicycle parking space detail that meets the requirements of UDC Sections 7.4.9.B & .C.

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.

25. This comment was not addressed. COMMENT: Until the street property line is clearly shown, see comment 12, and the height of the proposed building, see comment 27, the required street perimeter yard cannot be verified.

26. This comment was not addressed. COMMENT: Provide a street perimeter yard setback dimension from the east end of the building to the street property line along Houghton Road.

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).

27. This comment was not addressed. COMMENT: Provide the square footage and height of the proposed building within the footprint on the plan.

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.

28. This comment was not addressed COMMENT: Provide a sidewalk width dimension from the northwest corner of the proposed building to the top of the ramp shown on the plan. It appears that the building pop-out may encroach into the minimum 4'-0" sidewalk width, see TSM Section 7-01.4.3.A.

29. Addressed. COMMENT: There is a 5'-0" sidewalk shown northwest of the northwest corner of the proposed building that vehicles are allowed to overhang. Demonstrate on the plan how the minimum 4'-0" sidewalk width will be maintained, see TSM Section 7-01.4.3.A.

30. This comment was not addressed correctly. The sidewalks shown along the east side of the building do match what is shown on DP14-0248. Coordinate your response with Development Package (Tentative Plat) DP14-0248. COMMENT: Per TSM Section 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 drainage way 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 show the required sidewalk to Houghton Road and Old Vail Road.

31. This comment was not addressed correctly. The sidewalks shown along the east side of the building do match what is shown on DP14-0248. Coordinate your response with Development Package (Tentative Plat) DP14-0248. COMMENT: The striped area shown at the west end of the vehicle parking area located along the north side of the building is required to be a sidewalk physically separate from the vehicle use area, see TSM Section 7-01.4.2

Additional Comment - The vehicle parking area, drive through lane, trash enclosure and loading space layout does not match DP14-0248. Coordinate your design and all responses with Development Package (Tentative Plat) DP14-0248.

Additional Comment - Numerous response to comments state "Please refer to the survey and final plat attached. Neither of the documents were provided and all information requested above shall be provided on the development package.

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
01/21/2015 RONALD BROWN HC SITE REVIEW Reqs Change Non Responsive to Accessible Comments. No written response provided.
01/21/2015 PGEHLEN1 COT NON-DSD TRAFFIC Approved I don't have any additional comments.
>>> Patricia Gehlen 1/21/2015 2:19 PM >>>

The revised plans are on PRO and the response letter is there too. They should have addressed the comments you provided on the first review. Once you look at the plans on PRO please let me know if you need additional revisions or if the plans have addressed your concerns.

Thanks
01/23/2015 JOE LINVILLE LANDSCAPE REVIEW Reqs Change 1) Submit new landscape plans for the project that coordinate with DP14-0248 . AM 2-10.2.0

2) Revise the plans as necessary to comply UDC 5.3 SCENIC CORRIDOR ZONE
01/23/2015 JOE LINVILLE NPPO REVIEW Passed
01/23/2015 LOREN MAKUS ENGINEERING REVIEW Reqs Change Please take note of the correct spelling of the City of Tucson.
1. The grading and development of this site depends on the design and completion of sufficient center improvements and access routes. Approval of this plan will require enough information about the center improvement designs to confirm the improvements will function together. Additional comments may be forthcoming once the overall site development package is approved. Ensure this plan is consistent with the overall center development plan, especially as it applies to the drainage facilities.
01/26/2015 PATRICIA GEHLEN ZONING-DECISION LETTER REVIEW Reqs Change This review has been completed and resubmittal is required.

Please resubmit the following items:

1) Two rolled sets of the plans
2) All items requested by review staff
3) All items needed to approve this plan
01/26/2015 ROBERT SHERRY PLUMBING-COMMERCIAL REVIEW Reqs Change Comment not addressed. An area drain connected to the sanitary drain system is shown within the trash enclosure.
a. Show how rainwater will be prevented from entering the sanitary waste system. Reference: Section 1101.3, IPC 2012.
b. Show how the introduction of deleterious materials will be prevented from entering the sanitary waste system. Reference: Section 302.1, IPC 2012.

Final Status

Task End Date Reviewer's Name Type of Review Description
02/13/2015 FERNE RODRIGUEZ OUT TO CUSTOMER Completed