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-0159
Parcel: 14027043J

Address:
6221 S TUCSON BL

Review Status: Completed

Review Details: SITE and/or GRADING

Permit Number - DP14-0159
Review Name: SITE and/or GRADING
Review Status: Completed
Review Date Reviewer's Name Type of Review Description Status Comments
09/12/2014 RBROWN1 ADA REVIEW Passed
09/16/2014 KEN BROUILLETTE FIRE REVIEW Reqs Change Please indicate on plans the location of all proposed fire hydrants. The one existing fire hydrant shown does not meet requirements.
Please indicate the location of the fire line for the automatic fire sprinkler system.
09/25/2014 STEVE SHIELDS ZONING REVIEW Reqs Change CDRC TRANSMITTAL

TO: Development Services Department
Plans Coordination Office

FROM: Steve Shields
Lead Planner

PROJECT: Certex
Development Package (1st Review)
DP14-0159

TRANSMITTAL DATE: September 26, 2014

DUE DATE: October 09, 2014

COMMENTS: Please resubmit revised drawings along a 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 September 10, 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.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).

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.

1. COMMENT: As Sheet A1.0 is the only sheet provided with dimensions and will be considered part of the development package it should be drawn at an engineering scale.

2-06.3.4 - A title block shall be provided in the lower right quadrant of each sheet.

2. COMMENT: A title block shall be provided in the lower right quadrant of each sheet. The title block should be the small on all sheets.

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.

3. COMMENT: Provide the PDSD Development Package approval stamp in the lower right quadrant of all sheets. The required stamp can be found at http://pdsd.tucsonaz.gov/pdsd/development-permits under Development Package.

2-06.3.7 - A small, project-location map shall be provided in the upper right corner of the cover sheet.

4. COMMENT: Provide a project/location map on the cover sheet.

2-06.3.12 - An index of sheets in the development package shall be provided on the first sheet.

5. COMMENT: Provide a drawing index on the cover sheet that includes all sheets, site plan, grading, SWWP, landscape, submitted with the development package

6. COMMENT: The sheets do not appear to be in order. Sheet SWP2 is in front SWP1.

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.

7. COMMENT: Provide the above information on the cover sheet.

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

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;

8. COMMENT: Provide a brief legal description within the title block.

2-06.4.2.D - The page number and the total number of pages in the package (i.e., sheet xx of xx).

9. COMMENT: Provide the page number and total number of pages on all sheets, i.e., sheet xx of xx.

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.

10. COMMENT: Remove the street address and provide it 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.

11. COMMENT: Provide a project location map on the first sheet.

2-06.4.2.A - Show the subject property approximately centered within the one square mile area;

12. COMMENT: Provide the above information on the location map.

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,

13. COMMENT: Provide the above information on the location map.

2-06.4.2.C - Section, township, and range; section corners; north arrow; and the scale will be labeled.

14. COMMENT: Provide the above information 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 - 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.

15. COMMENT: Provide a general note stating "EXISTING USE VACANT, PROPOSED USE COMMERIAL STORAGE, SUBJECT TO USE SPECIFIC STANDARDS 4.9.10.A, 4.9.5.C.8, and 4.9.13.Q.

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.

16. COMMENT: Provide a general note on the cover sheet stating "THIS PROJECT IS DESIGNED TO MEET THE OVERLAY ZONE(S) CRITERIA, UDC ARTICLE 5.4 MAJOR STREETS AND ROUTES SETBACK ZONE (MS&R), UDC ARTICLE 5.5 GATEWAY CORRIDOR ZONE (GCZ) AND UDC ARTICLE 5.6 AIRPORT ENVIRONS ZONE (AEZ)."

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

17. COMMENT: Remove "ZONING AND LAND USE NOTE" 5. B from the plan as lot coverage is not applicable in the PI zone.

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

18. COMMENT: Provide the above information on the site 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.

19. COMMENT: Provide the 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 on the site plan.

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.

20. COMMENT: Provide the future SVTs for Tucson Blvd on the site plan.

21. COMMENT: It does not appear that the SVTs for Ganley Road are correct, see Engineering 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.

22. COMMENT: Show the future right-of-way (ROW) for Tucson Blvd and dimension the future curb and sidewalk, see COT Major Streets and Route plan.

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.

23. COMMENT: Provide a vehicle parking space calculation on the cover sheet, see UDC Table 7.4.4-1: MINIMUM NUMBER OF MOTOR VEHICLE SPACES REQUIRED. This calculation should include the number required, include the ratio used, and the number provided, including the number of spaces required and provided for the physically disabled. Clarify if outdoor storage is proposed as this will effect the parking calculation.

24. COMMENT: Provide a typical parking space detail for both a standard and accessible vehicle parking space.

25. COMMENT: It appear that parking vehicles will be allowed to overhang the proposed sidewalk along the west side of the proposed building. Show the 2'-6" vehicle overhang on the plan. It does not appear that there will be sufficient sidewalk width once the overhang is shown.

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.

26. COMMENT: Provide a loading space calculation on the plan that provides the number required and provided on the plan. Per UDC Table 7.5.5-A: REQUIRED LOADING AREAS one (1) type "A" loading space is required.

27. COMMENT: Show the required loading space and vehicle maneuverability on the plan.

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.

28. COMMENT: Provide a short and long term bicycle parking space calculation on the plan that provides the number required and provided on the plan. Per UDC Table 7.4.8-1: Minimum Required Bicycle Parking Spaces, STORAGE USE GROUP, Commercial Storage & Hazardous Material Storage, Short term required 0, Long term required 1 space per 40,000 sq. ft. GFA. Minimum requirement is 2 spaces.

29. COMMENT: Show the required long term bicycle parking on the plan and provide a detail that shows how the requirements of UDC Sections 7.4.9.B & .d are met.

30. COMMENT: It does not appear that the bicycle parking called out under Keynote 22, Sheet A1.0 meets the long term bicycle parking requirements.

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.

31. COMMENT: The street perimeter yard setback dimension shown on the plan is not correct. Until the future ROW & curb are shown on the plan the correct street perimeter yard setback cannot be verified, see UDC TABLE 6.4.5.C-I, ADT of 1,000 or greater, 2 The setback is measured from the back of existing curb or future curb location.

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

32. COMMENT: Provide the height of the proposed building within the footprint.

33. COMMENT: This project is located within the Airport hazard district for the Tucson International Airport (TIA). Per UDC Section 5.6.11.A.1 Provide a building height based on mean sea level (MSL) elevation established for the NE end of runway 21.

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.

34. COMMENT: Keynote7 calls out "4' CONCRETE SIDEWALK" the plan shows a 5'-0" dimension, which is correct.

35. COMMENT: Per TSM 7-01.4.3.A Width All sidewalks must be a minimum of four feet wide and installed to avoid any obstruction which decreases the minimum width to less than four feet. That said it appear that parking vehicles will be allowed to overhang the proposed sidewalk along the west side of the proposed building. If vehicle over-hang is proposed the minimum width of the sidewalk is 6'-6". Provide a 6'-6" sidewalk or provide wheel stops for the vehicle parking spaces.

36. 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 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 the ROW along Ganley Road.

37. 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 four (4) foot sidewalk between the north side of the proposed building, and the proposed access lane.

All the above comments have been based on sheet A1.0.

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
.
10/01/2014 ROBERT SHERRY PLUMBING-COMMERCIAL REVIEW Reqs Change 1. An approved development plan is not to be used for construction of on-site utilities (e.g. water service to the building, building sewer, site lighting, electrical service to the building, etc.). The construction of the on-site utilities may be included with the permit for constructing the building or as a separate permit.
2. A separate permit is required for the installation of a septic system and will require a review of the septic system design by the Pima County Department of Environmental Quality. Reference Title 18, R18-9-E302, 4.02 General Permit, Arizona Administrative Code.
10/03/2014 RONALD BROWN H/C SITE REVIEW Reqs Change SHEET A1.0
1. Provide a large scale detail of the accessible parking layout. Where is sheet 9/A1.4?
SHEET GD02
2. At details 3 and 7
a. Detectable warnings are not a code requirement however if chosen to be implemented in the design they must meet the requirements of ICC A1171.1, Section 406.12, 13 and 14 and section 705.
SHEET GDO3
3. At Note 6:
a. Delete all references to "...PC and COT SSPI Section 708 and as per ADA accessibility guidelines latest edition."
b. All accessible requirements are to be as per the 2012 IBC, Chapter 11 and the 2009 ICC A117.1.
c. Provide a large scale detail of the accessible parking layout showing all accessible requirements such as dimensions, Van Acccessible parking, markings, signage, grade slopes, aisles, ramp and accessible to accessible routes.
d. Provide a large scale detail of the accessible parking sign including a van accessible sign.
END OF REVIEW
10/07/2014 ANDREW CONNOR LANDSCAPE REVIEW Reqs Change TECHNICAL STANDARDS MANUAL

SECTION 4-01.0.0:
COMMERCIAL RAINWATER HARVESTING

RAINWATER HARVESTING PLAN

Rainwater Harvesting Plan shall be submitted with all applications for commercial developments at which landscaping is required. The Rainwater Harvesting Plan shall consist of two elements: a Site Water Budget and a Water Harvesting Implementation Plan. Preparation of the Rainwater Harvesting Plan elements requires coordination between project managers, site engineers and landscape architects from the inception of the project. The two elements of the Rainwater Harvesting Plan shall illustrate how water harvesting will meet 50% of annual landscape water demand, as required by the ordinance.

Provide additional data indicated in within: TS 4-01.2.0 DESIGN CONSIDERATIONS AND TECHNICAL REQUIREMENTS along with the background data and assumptions used to develop it. This water budget format is available to applicants as an Excel spreadsheet @ cms3.tucsonaz.gov/files/dsd/water_budget_spreadsheet.xls

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:

Rezoning case;

Subdivision case;

Board of Adjustment case;

Design Development Option case;

Development Review Board (DRB) case; and/or,
Any other relevant case number for reviews or modifications that affect the site.

Ensure that all Zoning and Engineering comments and concerns are addressed.

Additional comments may apply.
10/09/2014 ANDREW CONNOR NPPO REVIEW Approved
10/09/2014 LOREN MAKUS ENGINEERING REVIEW Denied The Development Package must meet the format and content requirements of the City of Tucson Administrative Manual Section 2-06. The standards include but are not limited to the following:
1. All mapped data must be presented at an engineering scale of not more than 50 feet per inch.
2. Include a small project location map in the upper right corner of the cover sheet.
3. Provide a legend that shows and describes all symbols used.
4. Provide a sheet index on the cover sheet.

Provide dimensions for the existing sidewalk along Tucson Boulevard. If the existing sidewalk is less than 4 feet wide, it must be widened to 6 feet. (TSM 40-01.4.1.A)
Provide solid waste enclosures for both garbage and recycling containers. (TSM 8-01.5.1.)
On sheet 1, drainage notes 2 and 3 indicate the project is subject to the floodplain regulations. Delineate the floodprone areas on the plan. (AM 2-06.4.8.I) If the site is free from floodprone areas, omit the notes.
Grading note on Sheet GD01 should be changed to indicate that grading will conform to Technical Standard 2-01.
Tucson Boulevard has a future right of way width of 120 feet. Show the location of the future right of way on the plans.

Final Status

Task End Date Reviewer's Name Type of Review Description
11/05/2014 AROMERO4 OUT TO CUSTOMER Completed