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: DP15-0032
Parcel: 12415014A

Address:
744 S EUCLID AV

Review Status: Completed

Review Details: SITE and/or GRADING

Permit Number - DP15-0032
Review Name: SITE and/or GRADING
Review Status: Completed
Review Date Reviewer's Name Type of Review Description Status Comments
03/03/2015 RBROWN1 ADA REVIEW Passed
03/16/2015 JASON GREEN ENGINEERING REVIEW Reqs Change DATE: March 19, 2015
DUE DATE: March 30, 2015
SUBJECT: Latitude Engineering Development Plan Package- Engineering Review
TO: Metro TED; Attn: Lisa Bowers
LOCATION: 744 S Euclid Ave; T14S R14E Sec18
REVIEWERS: Jason Green, CFM
ACTIVITY: DP15-0032

SUMMARY: Engineering Division of Planning & Development Services Department has received and reviewed the proposed Development Plan Package and Drainage Statement (Cypress Civil Development, 20FEB15). Engineering Division does not recommend approval of the Development Plan Package at this time. This review falls under the Unified Development Code (UDC), Administration Manual (AM) and Technical Standards Manual (TSM). Refer to the following link for further clarification:
http://www.amlegal.com/nxt/gateway.dll/Arizona/tucson_az_udc/administrativemanual?f=templates$fn=default.htm$3.0$vid=amlegal:tucson_udc_az

The following items need to be addressed:

SITE PLAN:

1) AM Sec.2-06.4.1: Revise the development plan package to provide the email address and phone number for both the Architect and Landscape Architect under the Sections.

2) AM Sec.2-06.4.3: The relevant Development Plan Package case number (DP15-0032) may be added to the lower right hand corner of the plan on all sheets.

3) AM Sec.2-06.4.8.F: Revise the development plan package to label all existing storm drainage facilities on and adjacent to the site with the Improvement Plan Number in plan view.

4) AM Sec.2-06.4.9.H.1: Revise the development plan package to label and dimension the curb return taper (Detail C) for the 25-foot curb returns at the intersection of the proposed vertical curbing and existing concrete header.

5) AM Sec.2-06.4.9.H.2: Revise the development plan package to provide the correct SVT dimensions for the driveway and the MS&R Collector Street. The dimensions shown are for a driveway to an Arterial Street which is larger than required.

6) AM Sec.2-06.4.9.H.5.a: Revise the development plan package and Typical Parking Space Detail to correctly label the 2.5-foot overhang form the wheel stop to the front of the parking space.

7) AM Sec.2-06.4.9.H.5.a: Revise the development plan package to provide a vehicular separation along all areas of the site between the vehicular use area and the landscape area/retention basin. Refer to UDC Sec.7.4.6.H.1; A barrier, such as post barricades or wheel stop curbing, are required in a vehicular use area to prevent vehicles from extending beyond project area, damaging adjacent landscaping, fencing, or unpaved areas, and/or driving onto unimproved portions of the site.

8) AM Sec.2-06.4.9.R: Refer to comments from Ron Brown, RA Structural Plans Examiner for all handicap accessibility comments that may be associated with this project.

9) AM Sec.2-06.4.9.R: Revise the development plan package to provide a scupper at all roof drain pipes at sidewalk locations, specifically at the northwest corner of the building. Per TSM Sec.7-01.4.1.Esidewalks shall be flood free for all storm discharges of up to and including a 10-year frequency flood event.

10) AM Sec.2-06.4.9.R: Revise the development plan package to clarify the location of Keynote #14 located at the sidewalk adjacent to the eastside of the existing building and along the north side of the new building addition. It appears that the Keynote is either in the wrong location or misplaced, revise.

GENERAL COMMENTS:

Please provide a revised Development Plan Package that addresses the comments provided above. Include a comprehensive response letter addressing in detail responses to all of the above comments.

For any questions or to schedule meetings call me at 837-4929.



Jason Green, CFM
Senior Engineer Associate
Engineering Division
Planning & Development Services Department
03/20/2015 MARTIN BROWN FIRE REVIEW Approved
03/25/2015 RONALD BROWN H/C SITE REVIEW Reqs Change Where the marked crossing is shown crossing the main drive entrance, relocate the crossing out of the asphaltic paving (PAAL) area and into the curb pensula just east of the present location.
a. Provide all curb ramps as required
END OF REVIEW
03/25/2015 ANDREW CONNOR LANDSCAPE REVIEW Reqs Change 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 for reviews or modifications that affect the site

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

Additional comments may apply
03/26/2015 ANDREW CONNOR NPPO REVIEW Approved
03/31/2015 MICHAEL ST. PAUL ZONING REVIEW Reqs Change CDRC TRANSMITTAL

TO: Development Services Department
Plans Coordination Office

FROM: Michael St Paul
Planning Technician

PROJECT: D15-0032
744 South Euclid Avenue
Parking and building expansion for precision manufacturing:

TRANSMITTAL DATE: March 31, 2015

DUE DATE: March 31, 2015

1) COMMENTS: Please resubmit revised drawings along a response letter, which states how all Zoning Review Section comments regarding the Unified Development Code, The Administrative and Technical Manuals were addressed.

This plan has been reviewed for compliance with the Development Package Standards listed in section 2-06 of the City of Tucson Administrative Manual. Also compliance with applicable development criteria for the proposed use as listed in the City of Tucson Uniform Development Code (UDC).

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 requirements are in the Unified Development Code and can be viewed at the same web link as above

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

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

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.
2-06.3.3 - All lettering and text (upper or lower case), and numbering, shall be a minimum of three-thirty-seconds inches in height to assure the plan will be legible during review and when digitized and/or reduced for archiving.


2-06.4.0 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: Provide the email address for all consultants with the rest of their contact information.

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.1 - List as a general note: "Existing zoning is ____."

3) COMMENT: I-1, not I1. You have this in two places.

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.

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

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.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/are provided.

5) COMMENT: Provide all the easement information described above (2-06.4.8.B) on the plans.

2-06.4.8.D - The following information regarding existing utilities shall be provided: the location and size of water wells, water pumping plants, water reservoirs, water lines, fire hydrants, sanitary and storm sewers, including the pipe diameter and the invert and rim elevations of all manholes and cleanouts; the Pima County Wastewater Management Department (PCWMD) reference number; locations of gas lines, electric and telephone lines, poles, and communications cables, on-ground junction boxes, and street lights. If water mains and sewers are not located on or adjacent to the tract, indicate the direction, distance to, and sizes of those nearest the property.
Identifying the locations of all utilities and service equipment immediately adjacent to the project is especially important in situations where pedestrian and vehicular access and circulation or landscaping can be in conflict. By knowing the location of the existing utilities, design of the project can take those elements into consideration and can help avoid expensive and time-consuming relocation of utilities, major redesign, or requests to vary regulations after commencement of construction.

6) COMMENT: Provide all the utility information, as described above (2-06.4.8.D) relevant to this site on the plans.

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 - Proposed Traffic Circulation

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.

7) COMMENT: Provide specific dimensions for the PAAL. Do not use approximate dimensions.

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.

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.

8) COMMENT: Provide details for the provided long-term bicycle parking.

2-06.4.9.L - All proposed easements (utility, sewer, drainage, access, etc.) are to be dimensioned and labeled as to their purposes and whether they will be public or private. The easements may have to be recorded and the recordation information added to the development package prior to approval.

9) COMMENT: Be certain to provide all proposed easements on the plans.

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

COMMENT:

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.

10) COMMENT: Continuous pedestrian circulation paths are required with all development (TS 7.01.3.3).

A) The pedestrian path must be connected to all public access areas of the development and to any adjacent streets (TS 7-01.3.3.A).

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" (TS 7-01.3.3.B).

C) "Within this pedestrian circulation path, an accessible route is also required in compliance with the city's adopted building codes" (TS 7-01.3.2). "Pedestrian circulation paths designed for barrier-free accessibility for the physically disabled and located within any development are regulated by the adopted building codes" (TS 7-01.3.3.C).

7-01.4.0 LOCATION AND DESIGN STANDARDS
4.1 Location Standards
Sidewalks must meet the following locational requirements:
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;
B. A sidewalk is required adjacent and parallel to any access lane or PAAL on the side where buildings are located (See Figure 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 (See Figure 2);
D. Sidewalks must connect all areas of the development and must also connect to the pedestrian circulation path located along any adjacent street;
E. Sidewalks shall be flood free for all storm discharges of up to and including a ten-year frequency flood event. Drainage flowing across all pedestrian circulation paths shall be conveyed under the path for up and including the ten-year frequency flood events, except at street intersections, pedestrian crossings, and PAAL pedestrian crossings;
F. Sidewalks or pedestrian refuge areas cannot be located between any motor vehicle parking space and the PAAL providing access to that space;
G. Sidewalks or crosswalks cannot cross any type of stacking areas for drive-through lanes; and,
H. In Land Use Classes where the public does not have access to certain portions of the site, a four- foot wide pedestrian refuge area must be maintained between any enclosed structure and a PAAL (See Figure 6).


2-06.4.9.S - Show existing or proposed pedestrian circulation along abutting rights-of-way. Such sidewalks must comply with accessibility requirements for the physically disabled and the design criteria in Section 10-01.0.0, Street Technical Standards, of the Technical Standards Manual.

11) COMMENT: Provide the pedestrian circulation as described above (2-06.4.9.S) on the site plan for this development package.

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.

12) COMMENT: Sign are a separate permit.

2-06.4.9.X - Show compliance with landscaping and screening requirements by locations, material descriptions, and dimensions. Specific plant or hardscape material shall be detailed on a landscape plan. A detailed landscape plan is required. In accordance with Section 2-11.0.0, Landscape Plan Requirements.

13) COMMENT: See comments by the landscaping review section.

If you have any questions about this transmittal, please call Michael St. Paul, (520) 837-4959.

RESUBMITTAL OF THE FOLLOWING IS REQUIRED: Revised development package site plan and any requested documents.

Provide a copy of the last approved site plan. The expansion calculations are based upon the last approved site plan. The calculations are also based upon the last full code site plan. The expansion calculations are cumulative.

Provide copies of this submittal with the revised plans and response letter.
04/01/2015 ROBERT SHERRY PLUMBING-COMMERCIAL REVIEW Completed

Final Status

Task End Date Reviewer's Name Type of Review Description
05/13/2015 KROBLES1 OUT TO CUSTOMER Completed