The URL can be used to link to this page

2018, 02-06 Study SessionAGENDA SPOKANE VALLEY CITY COUNCIL STUDY SESSION FORMAT (with some action items) Tuesday, February 6, 2018 CITY HALL COUNCIL CHAMBERS 10210 E Sprague Avenue (Please Silence Your Cell Phones During the Meeting) 6:00 p.m. CALL TO ORDER ROLL CALL ACTION ITEMS: 1. First Reading Ordinance 18-003 Amending Street Standards — Henry Allen, Micki Harnois [public comment] 2. First Reading Ordinance 18-004 Updating Subdivision Regulations — Marty Palaniuk [public comment] 3. Motion Consideration: Street Maintenance Option to Renew — Bill Helbig [public comment] 4. Motion Consideration: Street Sweeping Option to Renew — Bill Helbig [public comment] DISCUSSION LEADER SUBJECT/ACTIVITY GOAL NON -ACTION ITEMS: 5. Erik Lamb; and SHA Director Pam Tietz 6. Mark Werner, Morgan Koudelka and Tony Anderman 7. Mark Werner, Morgan Koudelka 8. Mayor Higgins 9. Mayor Higgins 10. Mark Calhoun Adjourn Spokane Housing Authority (SHA) Re -authorization Pre -Law Enforcement Academy Training Spokane Valley Police Department Vehicle Color and Graphics Advance Agenda Council Check-in City Manager Comments Discussion/Information Discussion/Information Discussion/Information Discussion/Information Discussion/Information Discussion/Information Study Session Agenda, February 6, 2018 Page 1 of 1 Meeting Date: CITY OF SPOKANE VALLEY Request for Council Action February 6, 2018 Department Director Approval: Check all that apply: ['consent ❑ old business ® new business ['public hearing ['information ❑admin. report ['pending legislation ['executive session AGENDA ITEM TITLE: First reading of Ordinance 18-003 (CTA -2017-0004) - revisions to the Street Standards and related amendments to the Spokane Valley Municipal Code (SVMC) GOVERNING LEGISLATION: Chapter 35.78 RCW PREVIOUS COUNCIL ACTION TAKEN: • March 2003 - Ordinance 53 adopting Spokane County Road Standards • December 2009 - Ordinance 09-033 adopting City's Street Standards • December 2016 - Ordinance 16-018 revising Surety Requirements in Chapter 9 • December 5, 2017 — Administrative Report, Street Standards Update BACKGROUND: Chapter 35.78 RCW requires cities and counties to adopt uniform definitions and design standards for municipal streets and roads. The City adopted the City of Spokane Valley Street Standards in December 2009. The following revisions have been incorporated since adoption: • Updated Standard Plans in January 2016 • Updated requirements for sureties in December 2016 During the December 5, 2017 Council meeting, Council heard a report explaining the basics of the Street Standards, including what is required, our last updates, and that the purpose of the proposed revision is mostly due to the FHWA's request to update the Maintenance Responsibility Section to ensure infrastructure funded with federal funds is adequately cared for, as well as to address changes to implementation of the Standards, and to the City's organizational structure which was changed in early 2017. At that December 5, 2017 meeting, Council agreed to move this forward. At their December 14, 2017 meeting, the Planning Commission heard a report on the proposed amendments to the Street Standards, and subsequently held a public hearing on the matter January 11, 2018. During the Commission's January 25, 2018 meeting, they passed a motion to recommend that Council adopt the draft with certain modifications as noted below, and moved to approve the Findings and Recommendations and to forward those to Council. The Federal Highway Administration (FHWA) has requested updates to the Maintenance chapter (Chapter 10) of the Street Standards to ensure that infrastructure funded with federal funds is adequately cared for. While FHWA comments were being addressed, revisions to the SVMC and other Street Standard chapters were also proposed to address changes to implementation of the Standards and to the City's organizational structure established in early 2017. This ordinance is a City initiated text amendment to: • Amend Spokane Valley Municipal Code (SVMC) to modify SVMC 20.80 and 22.130 to remove references to Future Acquisition Areas, • Update Chapter 3 (Traffic Analysis) to provide guidance on traffic requirements for SEPA infill areas, • Update Chapter 10 (Maintenance) to address FHWA comments on the maintenance of sidewalks, and, • Perform changes to most chapters in the Street Standards to reflect reorganization and revisions to implementation. And also to incorporate the Planning Commission's recommended revisions to the Municipal Code and Street Standards: • Modify SVMC 22.130 to replace references to "development services senior engineer" with "City Manager or designee." • Modify Section 1.3.2 bullet 3 to read as follows: To ensure public facilities and services meet level of service standards as adopted in the Comprehensive Plan. • Modify Section 10.2.1 paragraph two sentence two to read as follows: Property owners are responsible for the maintenance of these features as described below. OPTIONS: Advance to second reading with or without modifications RECOMMENDED ACTION OR MOTION: Move to advance Ordinance 18-003, Amending Street Standards, to a second reading. BUDGET/FINANCIAL IMPACTS: N/A STAFF CONTACT: Henry Allen, Senior Engineer Ray Wright, Senior Engineer, Traffic Gloria Mantz, Engineering Manager ATTACHMENTS: 1. Ordinance text which includes: Attachment A Draft SVMC chapters 20.80 Attachment B 22.130 with Planning Commission changes Attachment C Draft revised Street Standard chapters with Planning Commission changes 2. Planning Commission Findings and Recommendations 3. Staff Report and Recommendation 4. Presentation DRAFT CITY OF SPOKANE VALLEY SPOKANE COUNTY, WASHINGTON ORDINANCE NO. 18-003 AN ORDINANCE OF THE CITY OF SPOKANE VALLEY, SPOKANE COUNTY, WASHINGTON AMENDING THE STREET STANDARDS; AMENDING SPOKANE VALLEY MUNICIPAL CODE AND CHAPTER 22.130 SPOKANE VALLEY MUNICIPAL CODE RELATED TO FUTURE ACQUISITION AREAS, AND OTHER MATTERS RELATING THERETO. WHEREAS, pursuant to Spokane Valley Municipal Code (SVMC) 22.130.040, the City of Spokane Valley (City) previously adopted its City of Spokane Valley Street Standards (Street Standards), and has made subsequent amendments from time to time as appropriate; and WHEREAS, the City previously adopted chapters 20.80 and 22.130 SVMC, which contain provisions relating to future acquisition areas, and has made subsequent amendments from time to time as appropriate; and WHEREAS, such regulations are authorized by RCW 36.70A; and WHEREAS, on December 11, 2017, the Washington State Department of Commerce was notified pursuant to RCW 36.70A.106, providing a 60 -day notice of intent to adopt amendments to Spokane Valley development regulations; and WHEREAS, on December 14, 2017, the Planning Commission held a study session; and WHEREAS, on December 15, 2017 and December 22, 2017, notice of the Planning Commission public hearing was published in the Valley News Herald; and WHEREAS, on January 11, 2018, the Planning Commission held a public hearing, received evidence, information, public testimony, and a staff report with a recommendation followed by deliberations; and WHEREAS, on January 25, 2018, the Planning Commission approved the findings and recommended that City Council adopt the amendments; and WHEREAS, on February 6, 2018, City Council considered a first ordinance reading to adopt the proposed amendment; and WHEREAS, the amendment set forth below is consistent with the goals and policies of the City's Comprehensive Plan; and WHEREAS, the Street Standards and chapters 20.80 and 22.130 SVMC, as amended, bear a substantial relation to the public health, safety, welfare and protection of the environment. NOW, THEREFORE, the City Council of the City of Spokane Valley ordains as follows: Section 1. Purpose. The purpose of this Ordinance is to make minor revisions to the Street Standards and related amendments to chapter 20.80 SVMC Boundary Line Adjustments/Eliminations and chapter 22.130 SVMC Development Transportation Improvements. Section 2. Findings and Conclusions. The City Council acknowledges that the Planning Commission conducted appropriate investigation and study, held a public hearing on the proposed Ordinance 18-003 Street Standards Page 1 of 3 DRAFT amendments and recommends approval of the amendments. The City Council has read and considered the Planning Commission's findings. The City Council hereby makes the following findings: A. Growth Management Act Policies - Washington State Growth Management Act (GMA) provides that each city shall adopt a comprehensive land use plan and development regulations that are consistent with and implement the comprehensive plan. B. City of Spokane Valley Goals and Policies - The City of Spokane Valley has adopted goals and policies consistent with the GMA and adopted County -Wide Planning Policies, set forth below. Land Use Policy — 8: Ensure that neighborhoods are served by safe and convenient motorized and non -motorized transportation routes. Transportation Policy - 9: Provide and maintain quality street, sidewalk, and shared -use path surfaces that provide a safe environment for all users. Capital Facilities Policy - 3: Coordinate the construction of public infrastructure with private development to minimize costs. C. Conclusions The proposed amendment bears a substantial relation to public health, safety, welfare, and protection of the environment. The proposed City -initiated Code text amendments are consistent with the City's adopted Comprehensive Plan and the approval criteria pursuant to SVMC 17.80.150(F). The GMA stipulates that the comprehensive land use plan and development regulations shall be subject to continuing review and evaluation by the City. The proposal is consistent with RCW 36.70A, Washington State GMA, which stipulates that the comprehensive land use plan and development regulations be subject to continuing review and evaluation by the City. Section 3. Amendment. Chapter 20.80 SVMC is hereby amended as set forth in Attachment Section 4. Amendment. Chapter 22.130 SVMC is hereby amended as set forth in Attachment Section 5. Amendment. The Spokane Valley Street Standards are hereby amended as set forth in Attachment "C." Section 6. Other sections unchanged. All other provisions of Titles 20 and 22 SVMC, and the Spokane Valley Street Standards not specifically referenced hereto shall remain unchanged and in full force and effect. Section 7. Severability. If any section, sentence, clause or phrase of this Ordinance shall be held to be invalid or unconstitutional by a court of competent jurisdiction, such invalidity or unconstitutionality shall not affect the validity or constitutionality of any other section, sentence, clause, or phrase of this Ordinance. Ordinance 18-003 Street Standards Page 2 of 3 DRAFT Section 8. Effective Date. This Ordinance shall be in full force and effect five days after publication of this Ordinance or a summary thereof in the official newspaper of the City of Spokane Valley as provided by law Passed by the City Council this day of , 2018. ATTEST: Christine Bainbridge, City Clerk Approved as to Form: Office of the City Attorney Date of Publication: Effective Date: L.R. Higgins, Mayor Ordinance 18-003 Street Standards Page 3 of 3 Spokane Valley Municipal Code Chapter 20.80 BOUNDARY LINE ADJUSTMENTS/ELIMINATIONS ATTACHMENT A Chapter 20.80 BOUNDARY LINE ADJUSTMENTS/ELIMINATIONS Sections: 20.80.010 Scope. 20.80.020 Review process. 20.80.030 Application and drawing requirements. 20.80.040 Recordation. Page 1/2 20.80.010 Scope. Boundary line adjustments shall be a minor alteration in the location of lot or parcel boundaries on existing lots or parcels. In this section "lot" shall mean a parcel of land having fixed boundaries described by reference to a recorded plat, a recorded binding site plan, by metes and bounds, or by section, township, and range, and be of sufficient area to meet minimum zoning requirements. The purpose of the boundary line elimination process is to remove interior lot lines of a parcel comprised of two or more separate lots with contiguous ownership. Boundary line adjustments must be consistent with the following: A. Such alteration shall not increase the number of lots nor diminish in size open space or other protected environments; B. Such alteration shall not diminish the size of any lot so as to result in a lot of less square footage than prescribed in the zoning regulations; C. Such alteration shall not result in a building setback violation or site coverage to less than prescribed by the zoning regulations or areas as required in SVMC 22.130.080, Future acquisition area;,; and D. All lots resulting from the boundary line alteration shall be in conformance with the design standards of this chapter. (Ord. 12-008 § 3, 2012; Ord. 09-002 § 6, 2009; Ord. 07-015 § 4, 2007). 20.80.020 Review process. Boundary line adjustments and eliminations are classified as Type I applications and shall be reviewed pursuant to Chapter 17.80 SVMC. (Ord. 09-002 § 6, 2009; Ord. 07-015 § 4, 2007). 20.80.030 Application and drawing requirements. Application for a boundary line adjustment or elimination shall be made on forms provided by the department and shall provide the following information: A. Existing Conditions Site Plan. Produce a to -scale site plan on an eight -and -one -half-inch by 11 -inch sheet with one -inch margins on all sides showing the following information: 1. The existing dimensions and square footage of the existing property(ies) involved; 2. The location and setbacks of any permanent improvements (i.e., structures, septic systems, etc.) from all property lines; 3. The identification, location and dimension of all access and utility easements; and 4. The location, dimensions and names of public and/or private streets abutting the property(ies); and 5. North arrow and scale shall be noted. B. Proposed Adjustment/Elimination Site Plan. Produce a to -scale plan on an eight -and -one -half-inch by 11 -inch sheet with one -inch margins on all sides showing the following information: 1. The location and setbacks of any permanent improvements (i.e., structures, septic systems, etc.) after the proposed boundary line adjustment or elimination from the new property lines; The Spokane Valley Municipal Code is current through Ordinance No. 17-014, passed November 14, 2017. Spokane Valley Municipal Code Chapter 20.80 BOUNDARY LINE ADJUSTMENTS/ELIMINATIONS ATTACHMENT A Page 2/2 2. The identification, location and dimension of any access or utility easements after the proposed boundary line adjustment or elimination; 3. The location, dimensions and names of public and/or private streets abutting the property(ies) after the proposed boundary line adjustment or elimination; 4. Indicate the existing property lines to be revised with a dashed line and the proposed property lines with a solid line if applicable; and 5. North arrow and scale shall be noted. C. On a separate sheet of paper (eight and one-half by 11 inches) a written legal description for the existing parcel(s) and the proposed adjusted or eliminated parcel(s) with one -inch margins on all sides. D. One copy each of all involved property owners' recorded deeds, verifying current ownership of the subject property(ies). E. If available, submit a copy of an original plat for the subject property. A copy of the general land office plat is not required. F. A record of survey of the property may be required by the city manager or designee. The need for a survey will be determined based on an evaluation of the number of parcels, legal descriptions, appurtenances, disputed or apparent lines of ownership, and setbacks. If required, the survey must be completed by a professional land surveyor licensed in the state of Washington. (Ord. 17-004 § 3, 2017; Ord. 12-001 § 1, 2012; Ord. 09-002 § 6, 2009; Ord. 07-015 § 4, 2007). 20.80.040 Recordation. The department shall record approved boundary line adjustments and eliminations with the Spokane County auditor's office and submit copies of the recorded documents to the Spokane County assessor's office. All fees for such recording shall be paid by the applicant prior to recording. (Ord. 09-002 § 6, 2009; Ord. 07-015 § 4, 2007). The Spokane Valley Municipal Code is current through Ordinance No. 17-014, passed November 14, 2017. Spokane Valley Municipal Code Chapter 22.130 DEVELOPMENT TRANSPORTATION IMPROVEMENTS ATTACHMENT B Chapter 22.130 DEVELOPMENT TRANSPORTATION IMPROVEMENTS Sections: 22.130.010 Purpose. 22.130.020 Regulated activities. 22.130.030 Authority to develop and administer standards. 22.130.040 Street standards. 22.130.050 Manual on Uniform Traffic Control Devices. 22.130.060 Development project and permit review process. 22.130.070 Required improvements. 22.130.080 Future acquisition areas. 22.130.090 Conditional use permit. 22.130.100 Right-of-way permit and use requirements. 22.130.110 Liability. 22.130.010 Purpose. The purpose of this chapter is to: A Maintain the proper function of street infrastructure; B. Maintain and improve the street safety; C. Provide for future street expansion; Page 1/6 D. Identify requirements that may be imposed upon development projects and permits defined in SVMC 22.130.020. (Ord. 09-033 § 3, 2009; Ord. 07-015 § 4, 2007). 22.130.020 Regulated activities. All new development approvals and permits as set in Chapter 17.80 SVMC, unless exempt pursuant to SVMC 17.80.040, shall comply with this chapter. (Ord. 09-033 § 3, 2009; Ord. 07-015 § 4, 2007). 22.130.030 Authority to develop and administer standards. The development services senior engineer, under the authority of the city manager or designee, shall develop and administer the Spokane Valley street standards (SVMC 22.130.040) and require development projects to provide transportation improvements, dedicate right-of-way and border easements, and future acquisition areas. These improvements will be required to achieve the purpose of this chapter and goals of the currently adopted Comprehensive Plan. (Ord. 17-004 § 3, 2017; Ord. 09-033 § 3, 2009). 22.130.040 Street standards. Pursuant to RCW 35A.11.020 and 35A.12.140, the City adopts, by reference, the City street standards, and as it may be amended from time to time. The city clerk shall maintain a copy on file. (Ord. 16-018 § 7 (Att. B), 2016; Ord. 09-033 § 3, 2009). 22.130.050 Manual on Uniform Traffic Control Devices. The Washington Manual on Uniform Traffic Control Devices (MUTCD), and as it may be amended from time to time, is hereby adopted by reference. (Ord. 09-033 § 3, 2009; Ord. 07-015 § 4, 2007. Formerly 22.130.070). 22.130.060 Development project and permit review process. Following submittal of a completed application pursuant to Chapter 17.80 SVMC, the project shall be reviewed to determine compliance with all applicable regulations and standards. Additional material and/or analysis may be required to demonstrate compliance. (Ord. 09-033 § 3, 2009). The Spokane Valley Municipal Code is current through Ordinance No. 17-014, passed November 14, 2017. Spokane Valley Municipal Code Chapter 22.130 DEVELOPMENT TRANSPORTATION IMPROVEMENTS ATTACHMENT B Page 2/6 22.130.070 Required improvements. A. Prior to the issuance of any approvals for development projects or permits subject to the provisions of this chapter, the - - • : - • :. - - ity Manager or designee shall determine the extent and type of street improvements and; right-of-way/border easements dedications or designation of future acquisition areas required, to the extent allowed by the law, and pursuant to the following: 1. The Comprehensive Plan; 2. The arterial street map; 3. The street standards (SVMC 22.130.040); 4. The Manual on Uniform Traffic Control Devices identified in SVMC 22.130.050; 5. The local street plan; 6. Information submitted by the applicant including any preliminary site plans, engineering reports, or other relevant data; 7. A determination of the function, safety, efficiency and coordinated future expansion needs of the roadway system to serve the traveling public and emergency vehicles; and 8. Portions of the uniform development code, SVMC Titles 17 through 25, that specifically identify required future roadways, streets, or other rights-of-way. B. Requirements may include but are not limited to: 1. The extent and type of required street improvements pursuant to SVMC 22.130.040; 2. The extent of additional and/or new right-of-way and/or border easement needed to support the required improvements pursuant to SVMC 22.130.040; 3. Designation of future acquisition areas pursuant to SVMC 22.130.080; 43. Participation in capital improvement projects as included on the adopted six-year street improvement plan. (Ord. 09-033 § 3, 2009; Ord. 08-006 § 1, 2008; Ord. 07-015 § 4, 2007. Formerly 22.130.030). A. When a future acquisition area is designated, a title notice shall be completed and recorded with the county auditor. The notice shall run with the land and shall not be removed or amended prior to approval. The notice shall be recorded as soon as possible and, in all cases, prior to the issuance of a building -permit. The notice shall: 1. Include the tax parcel number and the full legal description; 2. Make reference to any related approval file number or permit numbers; 3. Include an exhibit showing street names, future acquisition areas, rights of way, and their dimensions; 1. Identify any limitations for improvements or features within the acquisition boundary(ies); 5. Indicate that the future acquisition area is private property; 6. Identify the responsibility for relocation or loss of interim features or improvements within the future acquisition areas; and 7. Be mailed to the property owner's and taxpayer's address as shown in the current Spokane County assessor's/treasurer's records, if a complete mailing address is indicated. The Spokane Valley Municipal Code is current through Ordinance No. 17-014, passed November 14, 2017. Spokane Valley Municipal Code Chapter 22.130 DEVELOPMENT TRANSPORTATION IMPROVEMENTS ATTACHMENT B Page 3/6 The establishing agency may approve the amendment and removal of the title notice if the arterial street plan, the local street map or other conditions change and the recorded title notice is no longer necessary. If the City initiates the amendment or removal of the title notice, the property owners will be notified of the change B. Building Setback. The required setback of buildings as specified in the underlying zone classification shall be measured from the future acquisition area boundary. Exceptions to the full setback may be administratively granted 1. An existing -parcel or lot equals or is up to five percent larger than the minimum lot area required in the underlying zone; 2. An existing parcel or lot has an existing -building -proposed for expansion; or 3. The applicant adequately demonstrates a site design or use limitation for the existing -property. Such exceptions niay be granted; provided, that: a. The property is not part of a zone reclassification and/or subdivision application; and b. The property has no reasonable alternative site design solution feasible; and c. A title notice is recorded pursuant to this section that further identifies likely impacts (such as noise, d. The building is located at the greatest setback possible, but in any case shall be no closer than one quarter of the required setback from the future acquisition area boundary and shall not be located within the future acquisition area. C. Landscaping. Significant landscape features, such as trees, shall be located in such a manner that when the street is widened in the future a significant portion of such landscaping features, such as matured trees, will not need to be destroyed or relocated. A majority of the trees required in the current landscaping areas shall be planted eight feet from the future acquisition area boundary within the future planting strip and shall be spaced no less than 60 feet from one another. acquisition area. If no reasonable site design solution complying with parking location requirements is feasible, exceptions to these requirements may be administratively granted if: 1. An existing -parcel or lot equals or is up to five percent larger than the minimum lot area of the underlying zone; 2. An existing -parcel or lot has an existing -building -proposed for expansion; or 3. The applicant adequately demonstrates a site design or use limitation for the existing -property. Such exceptions may be granted; provided, that: a. The property is not part of a zone reclassification and/or subdivision application; and b. The property has no reasonable alternative site design solution feasible; and c. A title notice is recorded pursuant to this section that further identifies likely impacts to the site when the street is widened in the future; and d. The fewest number of parking stalls is located in the future acquisition area as possible and, in any case, shall contain no more than one quarter of the required parking stalls for the site. The Spokane Valley Municipal Code is current through Ordinance No. 17-014, passed November 14, 2017. Spokane Valley Municipal Code Chapter 22.130 DEVELOPMENT TRANSPORTATION IMPROVEMENTS ATTACHMENT B Page 4/6 E. Drainage Improvements. All required drainage facilities and structures for the site shall be located outside the future acquisition area. A portion of the drainage facility improvement may be temporarily allowed within the future acquisition area if a conditional use permit is issued pursuant to the provisions of SVMC 22.130.090. The permit shall provide for the relocation of the drainage facility to an alternative site by the property owner when the street is widened. The permit shall identify the alternate location and the means of relocating the facility. located within the future acquisition area unless a conditional use permit has been issued pursuant to SVMC 22.130.090. If permitted, they shall be considered "interim" and shall be relocated or removed if the right of way is widened in the future, subject to the conditions of the conditional use permit. All developers, agencies and purveyors installing -utilities in, adjacent to or across rights of way shall show the future acquisition area and boundary(ies) on construction plans or drawings. Impacts from the future street widening- and ideningand other relocation cost shall be considered when designing and siting utilities and improvements. (Ord. 09 033 § 3, 2009; Ord. 08 006 § 1, 2008. Formerly 22.130.035). 22.130.090 Conditional use permit. A. The City may temporarily allow, as an interim conditional use, site features or improvements located within or adjacent to the future acquisition area that are in conflict with the provisions of this chapter; provided, that a hardship can be demonstrated and the use can be reasonably conditioned and restricted to ultimately accomplish the intent of this chapter. Examples of site features or improvements include driveways, drainage facilities and structures, parking stalls, utilities and signs. RA. Permit Required. Conditional use permits shall be issued administratively at or before the time development approvals and permits are granted. Conditional use permits shall, at a minimum, specify the temporary or interim use allowed, the conditions of the permit, the provisions for and timing of removal, relocation or installation and the responsibility for the cost of relocation, removal or installation. GB. Appeals. Any appeal of the administrative decision shall be heard pursuant to Chapter 17.90 SVMC, Appeals. All conditional use permits shall be referenced by a title notice pursuant to SVMC 22.130.080. (Ord. 09-033 § 3, 2009; Ord. 08-006 § 1, 2008. Formerly 22.130.037). 22.130.100 Right-of-way permit and use requirements. A. Right -of -Way Permit Applicability. Unless exempt from permit requirements, a right-of-way permit is required of any person or company who performs construction work or otherwise engages in activity within existing City rights-of-way, or on City -owned infrastructure. A right-of-way permit authorizes a permittee to perform work or conduct activity in a right-of-way or easement. Permits shall not be required for the following: 1. Work done by or for the City within its rights-of-way. 2. Work that is two hours or less in duration, as long as that work does not require the closure of more than 50 percent of a non -arterial street, does not close any lanes on an arterial street, does not involve excavation within the rights-of-way, or does not involve cutting or placement of pavement, sidewalks, curbs or gutters. Exemption from the permit requirements of the SVMC shall not be deemed to grant authorization for any work to be done in any manner in violation of the provisions of the SVMC or any other laws, ordinances or standards of this jurisdiction. B. Expiration. Right-of-way permits issued between April 1st and September 30th are valid for 30 days after the date of issuance, with a one-time 30 -day extension available. Right-of-way permits issued between October 1st and March 31st shall be valid until the following April 30th. The Spokane Valley Municipal Code is current through Ordinance No. 17-014, passed November 14, 2017. Spokane Valley Municipal Code Chapter 22.130 DEVELOPMENT TRANSPORTATION IMPROVEMENTS ATTACHMENT B Page 5/6 C. Emergency Repairs. In the case of an emergency repair, a private or public utility may commence work prior to obtaining a permit, provided the person responsible for the work obtains a construction permit within 48 hours after work is commenced or on the first City business day following said elapsed 48-hour period. D. Right -of -Way Permit — Application. No right-of-way permit shall be issued unless a written application is submitted and approved by the City. The application shall, at a minimum, contain the following: 1. Construction plans or drawings approved by the City, if required; 2. A traffic control plan, if the work closes more than 50 percent of the non -arterial street, or closes any lanes on an arterial street; 3. The period of time during which the right-of-way will be obstructed; and 4. Proof of the contractor's and all subcontractors' state licensing, insurance and requirements. Depending upon the nature and extent of the construction activity or work, the City may require engineering, restoration and drainage plans prepared by a Washington -licensed engineer at the applicant's sole cost and expense. At the discretion of the City, a multiple -use permit may be available for licensed and bonded businesses and public utilities. The multiple -use permit fee will be established by resolution in the master fee schedule. The multiple -use permit shall expire at the end of the City fiscal year. The administrative regulations governing the multiple -use permit shall be written and approved by the City. Failure to comply with the administrative regulations shall be a violation of this code. E. Right -of -Way Permit Fees. Permit fees shall be assessed in accordance with the currently adopted Spokane Valley master fee schedule. F. Notice Required. The applicant shall give te-the City notice not less than 48 hours before any work or activity is commenced and shall notify the City upon completion of the same. If a traffic control plan is required to be submitted with the application, the applicant shall give the City not less than 72 hours' notice. In the event of an unexpected repair or emergency, work may be commenced as required under the circumstances. Unexpected repairs and emergency work shall comply with all other requirements of this section. G. Construction Standards. All work within the City rights-of-way shall be in accordance with adopted City standards in effect at the time of the application for the permit. These include but are not limited to current versions of the Spokane Valley street standards; the Spokane Regional Stormwater Manual; the Manual on Uniform Traffic Control Devices (MUTCD); Washington State Department of Transportation (WSDOT) Standard Specifications for Road, Bridge and Municipal Construction; and applicable standards of the American Public Works Association (APWA). H. Maintaining Access. In the event it is necessary for the permittee to excavate the entire width of the street, no more than half of the street shall be opened for construction and closed to traffic at one time. Such portion of the work shall be backfilled and completed before the remaining portion of the street may be excavated. If it is impossible, infeasible or unsafe to permit the work while maintaining an open lane for traffic, the City may, with the concurrence of the chief of police and fire chief, permit the street to be blocked for a short period of time where suitable detours can be provided and the public will not be unnecessarily inconvenienced. The permittee shall furnish facilities, such as bridges or other suitable means, or clearly identify appropriate detours, to allow the flow of traffic without unnecessary congestion. I. Traffic Control. Any person or company that performs construction work or otherwise engages in activity within the existing City rights-of-way, or on City -owned infrastructure, is responsible for all traffic control and assumes the responsibility to maintain appropriate signage, signals and barricades that protect the public safety, in accordance with the MUTCD. The person or company shall provide for the safe operation of all equipment, vehicles and persons within the right-of-way. J. Damage to Existing Infrastructure. All damage to existing public or private infrastructure and/or property during the progress of the construction work or activity shall be repaired by the permittee. Methods and materials for such The Spokane Valley Municipal Code is current through Ordinance No. 17-014, passed November 14, 2017. Spokane Valley Municipal Code Chapter 22.130 DEVELOPMENT TRANSPORTATION IMPROVEMENTS ATTACHMENT B Page 6/6 repair shall conform to adopted City standards. If the permittee fails to furnish the necessary labor and materials for such repairs, the City shall have the authority to cause said necessary labor and materials to be furnished by the City and the cost shall be charged against the permittee. Such charge shall be immediately paid by the permittee and shall, if not paid on demand, be deemed a valid claim on the bond filed with the City. K. City's Right to Restore Right -of -Way and Easements. If the permittee fails to restore any City right-of-way or easement to its original and proper condition upon the expiration of the time fixed by such permit or shall otherwise fail to complete the right-of-way construction work covered by such permit or if the work of the permittee is defective and the defect is discovered within one year from the completion of the right-of-way construction work, the City or designee shall have the right to do all work and things necessary to restore the right-of-way and/or easement and to complete the right-of-way construction work. The permittee shall be liable for all costs and expenses of restoration or completion. The City shall have a cause of action for all fees, expenses and amounts paid for such work. Following demand, the City may enforce its rights pursuant to this section. No additional permits shall be granted until the invoice for City -performed work has been paid. L. Insurance — Evidence. The permittee, prior to the commencement of construction hereunder, shall furnish the City satisfactory evidence in writing that the permittee has in force, during the performance of the construction work or activity, commercial general liability insurance of not less than $1,000,000 per occurrence and $2,000,000 general aggregate duly issued by an insurance company authorized to do business in this state. In addition, the policy shall name the City as an additional named insured. The City may reduce the insurance limits if good cause exists. M. Indemnification and Hold Harmless. The permittee shall defend, indemnify and hold harmless the City, its officers, officials, employees and volunteers from any and all claims, injuries, damages, losses or suits, including attorney fees, arising out of the permit issued under this section except as may be caused by the negligence or willful conduct on the part of the City. N. Rules and Policy. To implement the right-of-way permit and provide for the public health and safety, the City, under the supervision of the city manager, may develop and adopt rules, policies and forms consistent with this section. All adopted rules, policies and forms shall be filed with the city clerk. O. Violations — Penalties. Any person violating the provisions of this section shall be subject to all enforcement actions and penalties pursuant toas found in Chapter 17.100 SVMC. (Ord. 09-033 § 3, 2009; Ord. 07-015 § 4, 2007. Formerly 22.130.060). 22.130.110 Liability. The express intent of the City of Spokane Valley is that the responsibility for compliance with the provisions of this chapter shall rest with the permit applicant and their agents. This chapter and its provisions are adopted with the express intent to protect the health, safety, and welfare of the general public and are not intended to protect any particular class of individuals or organizations. (Ord. 09-033 § 3, 2009; Ord. 07-015 § 4, 2007. Formerly 22.130.090). The Spokane Valley Municipal Code is current through Ordinance No. 17-014, passed November 14, 2017. Street Standards Spokane jUalley Adopted December 2009 Revised February 2018 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 1- INTRODUCTION Chapter Organization 1.1 Title 1 1.2 Intent and Provisions 1 1.3 Objectives of Street Standards 1 1.3.1 Minimum Standards 1 1.3.2 Objectives 2 1.4 Authority 2 1.4.1 Development Services Senior Engineer 3 1.4.2 Senior Traffic Engineer 3 1.4.3 Senior Capital Projects Engineer 3 1.5 Document Organization 4 1.6 Amendments and Revisions to Standards 4 1.6.1 Policy Revisions 4 1.6.2 Technical Revisions 4 1.7 Interpretation of Standards 5 1.7.1 Governing Standards 5 1.7.2 Prior Acceptance of Construction Plans 5 1.7.3 Severability 5 1.8 Contact Information 6 1.9 Reference Material 6 1.10 Variance 7 1.11 Design Deviations 7 1.12 Abbreviations 8 1.13 Definitions 10 Adopted December 2009 Chapter 1 — Introduction 1-i CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIONALLY LEFT BLANK Adopted December 2009 Chapter 1 — Introduction CITY OF SPOKANE VALLEY STREET STANDARDS 1.1 TITLE These regulations, along with all future amendments, shall be known as the City of Spokane Valley Street Standards (hereinafter called "Standards" or "Street Standards"). 1.2 INTENT AND PROVISIONS These Standards apply to all capital and development projects within the City's limits and, to the extent allowed by law, to those projects outside of City limits that impact City infrastructure or transportation systems. When full compliance with these Standards makes a capital project impracticable or unfeasible, exceptions may be granted for reconstruction, resurfacing, restoration and rehabilitation of existing public streets. The City's review and approval of any plans, reports, or drawings, or the City's inspection and approval of any improvements designed and constructed by the Applicant in accordance with these Standards, does not constitute a representation, warranty, or guarantee by the City that such improvements are free from defects or will operate adequately for the purpose intended. • - - - . - .: hese Standards pertain to planning, design, approval, construction, inspection, testing, maintenance and documentation of street improvements. The intent of this manual is to establish the minimum acceptable standards. 1.3 OBJECTIVES OF STREET STANDARDS 1.3.1 MINIMUM STANDARDS These Standards shall be the minimum standards necessary for design and construction of all street_ related and some onsite private improvements in the City. Special situations, as determined by the City, may require different facilities and/or standards. For items not covered by these Standards, the City may require the use of other standards as referenced in Section 1.9. It is incumbent upon the Applicant's engineer to use good engineering practice and to be aware of, and implement, new design practices and procedures that reflect current techniques in civil engineering. Good engineering practice is defined in these Standards as professional and ethical conduct that meets the current codes and regulations adopted for engineers. The proposed design shall consider functionality, constructability, operation, and maintenance, including the health, safety and welfare of the public. Ad pted December 2009 Chapter 1 - Introduction 1-1 CITY OF SPOKANE VALLEY STREET STANDARDS 1.3.2 OBJECTIVES It is the objective of these Standards to address the following: • To provide for an efficient transportation system and improve local circulation and emergency access by providing connectivity between residential streets and arterials; • To extend the functional life of the existing transportation systems and increase its safe and efficient operation; • To ensure public facilities and services meet level of service standardss- as adoptedcstablished in the adopted Comprehensive Plan; • To encourage the use of public streets in new development; • To protect the public health, safety, environment, and welfare to the greatest extent possible resulting from construction, operation and maintenance activities within the public rights-of-way; • To ensure the primary uses of the public rights-of-way are for bicycle, pedestrian and vehicular travel; • To ensure the public rights-of-way arei-& properly maintained during construction and repair work in these areas; • To protect the City's infrastructure investment by establishing standardized design, materials, construction, and repair criteria for all public improvements; • To optimize the use of the limited physical capacity of public rights-of-way held by the City; • To provide an efficient permit system that regulates and coordinates activities in an effective and safe manner; • To protect private and public property from damages that could occur because of faulty design and construction; and, • To provide criteria for inspection of public and private improvements, in order to ensureassuro conformance with the approved plans, proper construction techniques, and to ensure that acceptable materials are used for the construction process of such public and/or private improvements. 1.4 Authority The following sections describe City engineering positions having authority over these Standards. Adopted December 2009 Chapter 1 - Introduction 1-2 CITY OF SPOKANE VALLEY STREET STANDARDS 1.4.1 Development Services Senior Engineer The Development Services Senior Engineer is part of the Development Services Division of the Community Development Department and has the authority to: a. Require development projects to provide and improve future acquisition areas, dedicate right of way and border casements, construct new streets, and/or improve existing infrastructure to the applicable standard pursuant to the City of Spokane Valley Municipal Code (SVMC) Title 22.130, the Revised Codc of Washington (RCW) , , , , , and , b. Make slight modifications to the standard sections for public streets when site conditions warrant; c. Ensure that all design and construction for development projects is completed to a level that is equal to or exceeds the requirements set forth in these Street Standards; d. Make revisions to the Street Standards in accordance with Section 1.6; and, e. Review and approve design deviations for development projects in accordance with Section . 1.4.2 S-enior Traffic Enginccr The Senior Traffic Engineer is part of the Traffic Division of the Public Works Department and has the authority to: a. Determine traffic concurrency for development projects pursuant to the SVMC 22.20; b. Review and approve driveway locations within intersections; c. Review and approve signal, signing and striping plans to ensure that they meet or exceed the applicable Manual on Uniform Traffic Control Devices (MUTCD) standards; d. Ensure that capital projects and development projects meet or exceed the traffic requirements set forth in Chapter 3; and, e. Impose other traffic requirements to the extent allowed by the law. 1.4.3 Senior Capital Projects Enginccr The Senior Capital Projects Engineer is part of the Capital Improvement Program Division of the Public Works Department and has the authority to: a. Ensure that all design and construction for capital projects is completed to a level that is equal to or exceeds the requirements set forth in these Street Standards; b. Review and approve design deviations for capital projects in accordance with Section 1.11; and, tea. 1 I when site conditions warrant in accordance with Section 1.11. Adopted December 2009 Chapter 1 - Introduction 1-3 CITY OF SPOKANE VALLEY STREET STANDARDS 4,51.4DOCUMENT ORGANIZATION These Standards are generally organized as described below: • Chapter 2 describes typical project requirements; • Chapter 3 describes traffic analysis requirements; • Chapter 4 describes requirements for plan submittal; • Chapter 5 describes requirements for clearing and grading; • Chapter 6 describes requirements for utility work; • Chapter 7 describes requirements for street design; • Chapter 8 describes requirements for pavement design; • Chapter 9 describes requirements for inspection and certification; • Chapter 10 describes maintenance requirements; and, • Chapter 11 provides the City's Standard Plans. 4 61.5AMENDMENTS AND REVISIONS TO STANDARDS The Street Standards may be periodically amended as necessary to provide additional clarity or to reflect changes in policy or in construction or engineering practice. Such revisions to these Standards may consist of either "policy" revisions or "technical" revisions. The City will maintain an electronic file of these Standards. All updates and revisions will be available on the City web page or at the City Clerk's office. 4T6A1.5.1 POLICY REVISIONS Policy revisions shall be considered major changes, changes in law and changes that will cause significant increased cost or controversy. Policy revisions also include those changes that relate to the public use and convenience, such as changes in standard street width. Policy revisions require a public hearing process for their adoption and City Council approval. 1.6.21.5.2 TECHNICAL REVISIONS Technical revisions shall consist of minor additions, clarifications, revisions, and corrections to the Street Standards and City standard plans as may be necessary to better conform to good engineering and/or construction standards and practice. Technical revisions shall be: a. Consistent with all existing policies relevant to the revision; b. Necessary for the public's health, safety and welfare; c. Needed to clarify these Standards; or, Ad pted December 2009 Chapter 1 - Introduction 1-4 CITY OF SPOKANE VALLEY STREET STANDARDS d. Consistent with existing law. Technical revisions shall become effective when approved in writing. If technical revisions are deemed necessary, the revisions may occur through either: e. Planned periodic revisions; or f. An accelerated process. If a technical revision is determined to be immediately necessary, then the change shall be made and notification given on the web page. Document holders on record with the City, will be notified of the changes. 4,71.6INTERPRETATION OF STANDARDS In the interpretation and application of the provisions of the Street Standards, the following principles shall apply: 4T7-711.6.1 GOVERNING STANDARDS Whenever a provision of the Street Standards or any provision in any law, ordinance, resolution, rule, or regulation of any kind contains restrictions covering any of the same subject matter, the standards that are more restrictive or impose higher standards or requirements shall govern. 1.7.21.6.2 PRIOR ACCEPTANCE OF CONSTRUCTION PLANS The Street Standards shall not modify or alter any street construction plans that have been filed with and accepted by the City prior to the effective date of the ordinance or resolution adopting the Street Standards. This exception shall be subject to the conditions and limitations under which said plans were accepted by the City. 1.7.3 SEVERABILITY If any section, sentence, clause or phrase of these Standards should be held invalid or unconstitutional, the validity or constitutionality thereof shall not affect the Standards. Ad pted December 2009 1-5 Chapter 1 - Introduction CITY OF SPOKANE VALLEY STREET STANDARDS 1.8 CONTACT INFORMATION City of Spokane Valley 11707 E. Sprague, Suite 106 Spokane Valley, WA 99206 Phone (509) 921 1000 Fax (509) 688 0037 City of Spokane Valley 11707 E. Sprague, Suite 106 Spokane Valley, WA 99206 Phone (509) 921 1000 Fax (509) 688 0261 Prcycntion Officc 13319 E Sprague Spokane Valley, WA 99206 Phone (509) 928 1700 ... City of Spokane Valley 11707 E. Sprague, Suite 106 Spokane Valley, WA 99206 Phone (509) 921 1000 Fax (509) 921 1005 City of Spokane Valley 11707 E. Sprague, Suite B 3 Spokane Valley, WA 99206 Phone (509) 720 5210 Fax (509) 688 0037 L irc Protcction District 8 12100 E Palouse Highway Valleyford, WA 99036 Phone (509) 926 6699 Fax (509) 92'1 835g 491.7REFERENCE MATERIAL The Street Standards are supplemented by the current version of the "Washington State Department of Transportation/American Public Works Association (WSDOT/APWA) Standard Specifications for Road, Bridge and Municipal Construction," latest edition. The Street Standard Details are comprised of the City's construction and design detail drawings for grading, storm drainage, and street work within the City that are supplemented by the current version of theWashington State Department of Transportation (WSDOTT "Standard Plans for Road, Bridge and Municipal Construction." The current versionedition of the following publications should shall be used as additional reference material for design applications, when situations are not addressed by these Street Standards or WSDOT Standards. Every subsequent reference to one of these publications in the Street Standards shall be to the currently adopted version unless specifically stated to the contrary, whether stated or not. Other standard technical references may be used if approved by the City Engineer: a. American Association of State Highway and Transportation Officials' (AASHTO) "A Policy on Geometric Design of Highways and Streets" (Green Book) b. AASHTO Guide for the Development of Bicycle Facilities c. AASHTO Standard Specifications for Highway Bridges d. Americans with Disabilities Act (ADA)Accessibility Guidelines e. American Society for Testing and Materials (ASTM) f. Associated Rockery Contractors, Standard Rock Wall Construction Guidelines Adopted December 2009 Chapter 1 - Introduction 1-6 CITY OF SPOKANE VALLEY STREET STANDARDS g. City of Spokane Valley Municipal Code h. Federal Highway Administration (FHWA) Engineering Circulars i. Highway Capacity Manual j. Institute of Transportation Engineers (ITE) Trip Generation Manual k. International Fire Code adopted by the City of Spokane Valley 1. Washington Model Traffic Ordinance (Chapter 308-330 WAC) m. Spokane County Standards for Road and Sewer Construction n. Spokane Regional Stormwater Manual o. U. S. Department of Transportation Manual on Uniform Traffic Control Devices, (MUTCD) p. Washington Department of Ecology Stormwater Management Manual for Eastern Washington q. Washington State Department of Transportation (WSDOT) Design Standards r. WSDOT Guidelines for Urban Arterial Program s. WSDOT Local Agency Guidelines t. WSDOT Standard Specifications for Road, Bridge and Municipal Construction u. WSDOT "Design Standards" v. Design criteria of federal agencies including the Federal Housing Administration, Department of Housing and Urban Development; and the Federal Highway Administration, Department of Transportation 1.10 Variance The requirements established in Chapter 2 can only be waived or reduced through a variance. Refer to SVMC Title 19.170 for variance process and requirements. 4,141.8 DESIGN DEVIATIONS In special cases, strict application of Street Standards may not best address a particular engineering situation. In these cases, a design deviation may be requested. Design deviation requests shall be on the City's form and include applicable engineering justification for the deviation_.. The Development Services Senior Engineer is the final authority to deny or approve a design deviation request for development projects. For capital projects, the authority lies with the Senior Capital Projects Engineer. a. The Applicant shall request a design deviation when either of the following situations applies: i. The project proposes non-standard methods, analysis, design elements or materials; or, ii. The project proposes design elements above maximum criteria or below the minimum criteria found in these Standards. b. A design deviation will only be considered for review if: i. The design elements proposed do not conflict with or modify a condition of approval; and, Adopted December 2009 Chapter 1 - Introduction 1-7 CITY OF SPOKANE VALLEY STREET STANDARDS ii. The design elements proposed are based on sound engineering principles, and are not inconsistent with the public interest, and the City's goals and policies. c. To requestFor consideration of a design deviation, the Applicant shall submit a design deviation request and supporting documentation. The supporting documentation shall include sufficient information for the City to make a decision as to the adequacy of the proposal. The design deviation package shall demonstrate that: i. There are special physical circumstances or conditions affecting the property that may prohibit the application of some of the requirements of these standards; ii. Every effort has been made to find alternative ways to meet the objectives of the Street Standards; iii. Approving the design deviation will not cause adverse impact on down gradient or adjacent properties, public health or welfare; and, iv. Approving the design deviation will not adversely affect the goals and policies of: the City's Comprehensive Plan, Spokane Valley Municipal Code, Sprague and Applcway Corridors Subarea Plan, Street Master Plan, and Transportation Improvement Plan. 4411.9 ABBREVIATIONS When the following abbreviations appear in these Standards, they shall mean the following: AASHTO American Association of State Highway and Transportation Officials ADA Americans with Disabilities Act ADT Average Daily Trips APWA American Public Works Association ASA American Standards Association ASTM American Society for Testing Materials BMPs Best Management Practices CBR California Bearing Ration CC&Rs Covenants, Codes and Restrictions CESCL Certified Erosion and Sediment Control Lead CSBC Crush surfacing base course CSTC Crush surfacing top course Dbh Diameter Breast Height ESALs Equivalent Single -Axle Loads ESC Erosion and Sediment Control FAA Federal Aviation Administration/Future Acquisition Area Ad pted December 2009 Chapter 1 - Introduction 1-8 CITY OF SPOKANE VALLEY STREET STANDARDS FEMA Federal Emergency Management Agency FHWA Federal Highway Administration FOP Field Operating Procedure GMA Growth Management Area HCM Highway Capacity Manual HMA Hot Mix Asphalt HOA Homeowner's Association IBC International Building Code IFC International Fire Code IRC International Residential Code ITE Institute of Transportation Engineers LOS Level of Service Mr Resilient Modulus MUTCD Manual on Uniform Traffic Control Devices O&M Operations and Maintenance PI Point of Intersection PC Point of Curvature PCR Point of Curve Return PE Professional Engineer PGIS Pollution Generating Impervious Surfaces PLS Professional Land Surveyor POA Property Owner's Association PT Point of Tangency RCW Revised Code of Washington SEPA State Environmental Policy Act SI Street intersection SR State Route SRSM Spokane Regional Stormwater Manual SRTC Spokane Regional Transportation Council SVMC Spokane Valley Municipal Code TESC Temporary Erosion and Sedimentation Control TIA Traffic Impact Analysis Ad pted December 2009 Chapter 1 - Introduction 1-9 CITY OF SPOKANE VALLEY STREET STANDARDS TIP Transportation Improvement Program USGS United States Geological Survey WAC Washington Administrative Code WAQTC Western Alliance for Quality Transportation Construction WSDOT Washington State Department of Transportation 1.131.10 DEFINITIONS For the purpose of these Street Standards, certain words and terms are herein defined. The word "shall" is always mandatory. The word "may" is permissive, subject to the judgment of the person administering the code. The word "should" indicates an advisory condition, recommended but not required. These definitions take precedence over those found elsewhere in the SVMC. In the event a technical term is not listed below, definitions shall be taken from the WSDOT Design Manual. Access Management: The concept of a public agency controlling the location of access points in order to achieve the dual purposes of providing access to individual land uses and limiting access on higher order streets in order to facilitate the smooth flow of traffic with a limited amount of impedance. Applicant: The party or parties desiring to construct a public or private improvement or project within City rights-of-way, easements or private property, securing all required approvals and permits from the City, and assuming full and complete responsibility for the project. The Applicant may be the Developer Owner or the individual designated by the DeveloperOwncr to act on his behalf. Binding Site Plan: A division of land approved administratively by the Department of Community Development, which legally obligates a person making a proposal to conditions, standards or requirements specified by these Standards and the SVMC. Border Easement: A dedicated easement on private property adjacent to public street right-of-way established for the purpose of utility, drainage facilities, pedestrian access or other public purpose. Building Division: The Division at the City of Spokane Valley responsible for reviewing, issuing and certifying construction permits. Builder: The party or parties desiring to construct a public or private project, which may include improvements, within the boundaries of the Applicant's project. Builder's project may include but not be limited to landscaping, paving, stormwater facilities, structures and installation of facilities or utilities to support the Builder's project. Certificate of Occupancy: An official certificate issued by the City building official that indicates conformance with all applicable provisions of the SVMCbuilding requirements and zoning regulations and authorizes legal use of the premises for which it is issued. Ad pted December 2009 Chapter 1 - Introduction 1-10 CITY OF SPOKANE VALLEY STREET STANDARDS Certification Package: A packet prepared by the Onsite Inspector including, but not limited to, Mylar record drawings, weekly reports, certification checklist and related construction documents, for review by the City to determine project acceptability. City: City of Spokane Valley, Washington. City Engineer -- The City Engineer or his duly authorized representative. Clear Zone: A relatively flat area void of fixed objects or obstructions beyond the edge of the traveled way that allows drivers to stop safely or regain control of a vehicle that leaves the traveled way. Clearing and grubbing: Includes, but is not limited to, removing trees, stumps, roots, brush, structures, abandoned utilities, trash, debris and all other materials found on or near the surface of the ground in the construction area. Concurrency: A requirement that those public facilities and services necessary to support development shall be adequate to serve the development at the time the development is available for occupancy and use, without decreasing the current level of service below locally established minimum standards adopted by the City. Contractor: The individual, partnership, firm or organization to whom a construction contract has been awarded by the Applicant, or who has been issued a right-of-way work permit by the City, for work covered by the contract. Agents, employees, workers, subcontractors, or designers employed by the Contractor shallae also be bound by the terms of the contract or permit. Corner Clearance: At an intersecting street, the distance measured along the curb line from the projection of the intersecting street flowline to the nearest edge of the curb opening. County: Spokane County. Design Deviation: An administrative approval of design elements that do not conform to or are not explicitly addressed by these Standards. Design E ginecrer: The person or persons responsible for the creation and submission of contract documents or construction plans for the purpose of one time construction of a facility. This person shall be a Washington licensed professional engineer. Developer: Owner of the Project and/or Development. Owner may be an individual, corporation, government or governmental agency, business trust, estate, trust, partnership, association, or some combination of the foregoing., Development: Any man-made change to improved or unimproved real estate including the division of land with potential for construction. Development Agreement: The contract between the City and the Applicant that defines public improvement requirements, costs, and other related public improvement issues. Adopted December 2009 Chapter 1 - Introduction CITY OF SPOKANE VALLEY STREET STANDARDS Development Inspector: A City employee, responsible for coordinating with the Onsite Inspector(s), reviewing and accepting certification packages and warranty sureties, and recommending public streets for establishment. Driveway: Any area, improvement or facility between a public or private street and private property, which provides ingress/egress for vehicles from a public or private street to a lot or parcel or to a structure constructed on the lot or parcel, whichever is longer. Driveway Approach: The transition at the end of a private street or driveway where it connects to a public or private street. For details, see standard plans. Easement: A right to use the land of others. The right may be from the common law or may be acquired, usually by purchase or condemnation and occasionally by prescription or inverse condemnation. The right is not exclusive, but subject to rights of others in the same land, the lesser right being subservient to a prior right which is dominant. Easements for drainage may give rights to impound, divert, discharge or concentrate surface flow, extend pipelines, deposit silt, erode, scour, or any other necessary consequence of a development. Enginccr: Shall mean a professional engineer. Scc Pr fcssi nal Enginccr dcfiniti n. Engineered Driveways: Driveways, which due to their length, surface area or other situational factors, are required to be designed by a professional engineer licensed in the State of Washington. Engineering — City Engineering Department Fill: A deposit of earthen material placed by artificial means. Fire Department: Fire district having jurisdiction. Fire Lane: An access designated to accommodate emergency access to a parcel of land or its improvements. Final Acceptance: The written notification from Development Engineering, after the Development Services SeniorCity Engineer finds the Warranty Period to be satisfactorily completed, that all public improvements are free of defects and the City releases the Applicant from future maintenance obligations. Frontage Improvements: Required improvements on public streets fronting the property which typically include pavement widening, curb, gutter, grassy swale, and sidewalk. Futurc Acquisition Arca: Arca identified on property as potential right of way for the easement area. Grading: The physical manipulation of the earth's surface and/or surface drainage pattern which includes surcharging, preloading, contouring, cutting, and filling to establish final site grades. Half -Street Improvements: Shall mcan, tThe construction of frontage improvement on the street fronting the property or development, including paving from the street Ad pted December 2009 1-12 Chapter 1 - Introduction CITY OF SPOKANE VALLEY STREET STANDARDS centerline, curb, gutter, swale or grassy strip, and sidewalk, plus a minimum of a 12 - foot lane on the opposite side of centerline with a one -1 --foot gravel shoulder and grassy ditch for stormwater treatment. The final pavement width shall be at least 28 feet. Improvements: All public or private improvements within City rights-of-way, 6f easements or private property. Development of a public or private street, typically including some or all of the following: pavements, curb, gutter, landscaped swale, sidewalk, drainage improvements. Intersection Sight Distance: The distance necessary for the driver of a motor vehicle stopped at an intersection or driveway to see approaching vehicles, pedestrians, and bicyclists along the intersecting major street and have sufficient space to make any allowed move to cross the intersection or merge with traffic without causing vehicles, pedestrians, or bicyclists traveling at or near the design speed on the major street to slow down. The controlling distance for design is the longest distance, generally the distance necessary to merge with traffic. Land Disturbing Activity: The result in a change in existing soil cover (vegetative or non -vegetative) or site topography. Land disturbing activities include, but are not limited to, demolition, construction, clearing and grubbing, grading and logging. Level of Service (LOS): A measure of a public facility or service's operational characteristics used to gauge its performance. Offsite Improvements: Construction of facilities located away from and up to a project site, necessary to serve the proposed development or to mitigate effects of the development. Onsite Inspector: A qualified person or firm, hired by the Applicant or Owner, responsible for project inspection and certification. Pollution Generating Impervious Surface (PGIS): Impervious surfaces that are significant sources of pollutants in stormwater runoff. Such surfaces include those that are subject to vehicular use, industrial activities, or storage of erodible or leachable materials that receive direct rainfall, or run-on or blow-in of rainfall. Metal roofs are considered to be PGIS unless coated with an inert, non -leachable material. Roofs that are subject to venting of manufacturing, commercial, or other indoor pollutants are also considered PGIS. A surface, whether paved or not, shall be considered PGIS if it is regularly used by motor vehicles. The following are considered regularly -used surfaces: streets, non -vegetated street shoulders, bike lanes within the traveled lane of a street, driveways, parking lots, unfenced fire lanes, vehicular equipment storage yards, and airport runways. Pre -Construction Meeting: A meeting between the Designer and assigned agents, the Onsite Inspector, and the Development Inspector to review proposed work necessary to construct the project, prior to proceeding with the work. A meeting may be required for each project, at the Development Inspector's discretion. Private Street: A local access street that is privately owned and maintained by capable and legally responsible owner(s). Ad pted December 2009 Chapter 1 - Introduction 1-13 CITY OF SPOKANE VALLEY STREET STANDARDS Professional Engineer (P.E.) (or Engineer): A civil engineer licensed in Washington under Chapter 18.43 RCW who is qualified by examination and/or experience to practice in the fields of civil, geotechnical and/or soils engineering. Professional Land Surveyor (P.L.S.) (or Surveyor): A Washington licensed land surveyor. Project: The public or private improvement(s) designated in the approved plans, which are to be constructed in conformance with these Standards. The term "Project" includes any and all public or private improvement projects for or within the City, whether development projects, private utility projects, or capital improvement projects. Public Improvements: Public facilities to be located within the rights-of-way or border easement which include pavement, curb and gutter, sidewalk, pedestrian/bike/equestrian paths, storm drain facilities, bridges, water distribution or transmission facilities with related appurtenances, pavement markings, signage and striping, traffic signals and related appurtenances, erosion control and right-of-way grading, or earth excavation processes integral to construction of other public improvements listed herein. Punch list, Initial or Final: A written list of work items, compiled by the Onsite Inspector, which do not conform to these Standards, the plans or SVMCether associated City Codes that govern the project and require correction prior to project approval. Record Drawings: Original approved design drawings, updated by an professional engineer which depicts all modifications from the design that occurred during construction. Redevelopment: Removal or modification of existing improvements and construction of new improvements or substantial remodeling. Regional Pavement Cut Policy: A regional policy adopted by the City of Spokane Valley, City of Spokane, and Spokane County. This policy, amongst other things, the construction of a newly paved street. Rights-of-way (Also "public right-of-way"): The land area (owned by the City) which was acquiredprovided by by acquisition or dedication for public use of streets, utilities, walks, and other uses, including -al -se providing access to adjoining properties. Right-of-way Permit: A permit, with or without conditions specified by the City, which allows an Applicant to construct public or private improvements within the public rights-of-way or border easement. Subdivision: Short -Long Subdivision: A division of land resulting in the creation of 10 or more 9 or fewer lots. Short Subdivision: A division of land resulting in the creation of nine or fewer lots. Ad pted December 2009 Chapter 1 - Introduction 1-14 CITY OF SPOKANE VALLEY STREET STANDARDS Slope, Recoverable: A slope on which a motorist may retain or regain control of a vehicle by slowing or stopping. Slopes flatter than 4:1 are generally considered recoverable. Slope, Non-recoverable: A slope considered being traversable but on which an errant vehicle continues to bottom. Embankment slopes between 3:1 and 4:1 may be considered traversable but non-recoverable if they are smooth and free of fixed objects. Specifications: Construction and standards adopted by the City. Speed — 85th Percentile: The speed at or below which 85% percent of the motorists drive on a given street unaffected by slower traffic or poor weather. This speed indicates the speed that most motorists on the street consider safe and reasonable under ideal conditions. Street: A public or private way for vehicular travel, exclusive of the sidewalk or shoulder even though such sidewalk or shoulder is used by persons riding bicycles. Street Classifications: The identification of a street according to different levels of emphasis on traffic movement versus direct access to property. Surety: A financial instrument securing the Applicant's responsibility to complete construction of public or private improvements within an approved project. Surety shall also mean a financial instrument securing the Applicant's obligations throughout the Warranty Period. Sureties approved by the City include cash, letters of credit and savings assignment. Surety, Performance: A surety securing the Applicant's responsibility to complete construction of public or private improvements within an approved project. Surety, Warranty: A surety securing the Applicant's obligations throughout the warranty period; required of projects in the public rights-of-way and border easements, guaranteeing against defects in street construction, utility work and/or drainage facilities. Survcyor: Shall mean a professional land survey r, sec definition. Swale: A grassland percolation area designed to accept and treat storm runoff from impervious areas such as streets, driveways, sidewalks, parking lots, roofs, etc. Traffic Calming Devices: Physical measures included in the design of streetstravel ways that improve neighborhood livability by reducing the speed and impact of vehicular traffic on residential streets. Travel Lane: The portion of the street intended for the movement of vehicles, exclusive of shoulders and lanes for parking. Trip Generation and Distribution Letter (TGDL): A document, prepared by a professional civil engineer with experience in traffic, design and analysis; that identifies the amount of traffic anticipated to and from a development. The letter is reviewed to determine if a traffic impact analysis is required. Traffic Impact Analysis (TIA): A study of the potential traffic impacts of a development on the transportation system. Ad pted December 2009 Chapter 1 - Introduction 1-15 CITY OF SPOKANE VALLEY STREET STANDARDS Variance: The process used to change or reduce improvements required of a project. Warranty Period: The period of time that the Applicant remainsi-s responsible for material and workmanship defects in the public improvements, which remains in effect until written notification is issued by the City. Warranty period is a minimum of two years. Wheel Path: The three3-foot wide portion of a travel lane, located on both sides of the travel lane and the two2-foot wide portion from the center of the travel lane. Ad pted December 2009 Chapter 1 - Introduction 1-16 CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIONALLY LEFT BLANK Ad pted December 2009 Chapter 1 - Introduction 1-17 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 2 -DEVELOPMENT ENGINEERING REQUIREMENTS Chapter Organization 2.1 Introduction 1 2.2 Applicability 1 2.3 Required Dedications and Improvements 1 2.3.1 Typical Requirements 2 2.3.2 Specific Requirements for Short Subdivisions, Long Subdivisions and Binding Site Plans 3 2.3.3 Specific Requirements for Commercial Building Permits 3 2.3.4 Specific Requirements for Miscellaneous Projects 5 2.3.5 Other Requirements 5 2.4 Modifications to Requirements 6 2.4.1 Variance 6 2.4.2 Capital Projects 6 2.4.3 Limiting Site Conditions 6 2.5 Applicant's Responsibilities 7 List of Tables Table 2.1 Required Street Improvements for Commercial Building Permits 4 Adopted December 2009 Chapter 2 — Development Entineerint Requirements 2-i CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIALLY LEFT BLANK Ad pted December 2009 Chapter 2 — Development Entineerint Requirements 2 -ii CITY OF SPOKANE VALLEY STREET STANDARDS Ad pted December 2009 Chapter 2 — Development Entineerint Requirements 2 -iii CITY OF SPOKANE VALLEY STREET STANDARDS 2.1 INTRODUCTION This chapter sets forth the specific requirements of the Development Engineering Division (Division) of the Community Development Department for development projects. These requirements are intended to supplement the general requirements of the Spokane Valley Municipal Code (SVMC) Cchapter 22.130 SVMC, and are adopted pursuant to SVMC 22.130.040. Required improvements and dedications shall be in compliance with all Chapters in these Street Standards. An overview of the review process for this Division can be found in the "Development Engineering Guidelines" which are adopted herein by reference. 2.2 APPLICABILITY Projects reviewed and conditioned by Development Engineeringthe City fall within three general categories: • Land divisions (short subdivisions, subdivisions and binding site plans); • Commercial building permits; and, • Miscellaneous projects which include access permits, boundary line adjustments, rezones, changes of use, changes of occupancy, temporary use permits, and conditional use permits and residential projects with engineering concerns. In some instances, this last category of projects may not need a building permit. They may, however, result in an increase in traffic and other impacts that maycan require street improvements and other mitigation. 2.3 REQUIRED DEDICATIONS AND IMPROVEMENTS This section describes the dedications and types of improvements that may be required pursuant to the SVMC Cchapter 22.130 SVMC, the Revised Code of Washington (RCW) chapters 35.63.080, RCW 35.63.090, RCW 35A.63.100, RCWchapter 43.21C RCW; RCWchapter 58.17 SVMC, and RCW 82.02.020. Land divisions and development permits trigger requirements for dedications of public right-of-way, border easements, future acquisition areas, and other construction of improvements. Other project types may also trigger these requirements. Specific requirements shall be determined during project review. To determine the requirements for a project, the City considers the following: a. Existing improvements, both onsite and offsite, such as curb, gutter, swale and sidewalk; b. Any anticipated increase in traffic that would lead or contribute to an unacceptable level of service; Ad pted December 2009 Chapter 2 — Development Entineerint Requirements 2-1 CITY OF SPOKANE VALLEY STREET STANDARDS c. Connectivity of existing or future streets to better serve public and emergency vehicle mobility; d. Street classification, as shown in the City's Comprehensive Plan; e. The City's of Spokane Valley Sixe-year Transportation Improvement Program and any anticipated improvements in the project vicinity; f. Public safety as affected by the project (i.e. pedestrian and vehicle safety, traffic flow, etc); g. Bike routes, pursuant toas shown in the City's Comprehensive Plan; and, h. Environmental impacts as identified through applicable State Environmental Protection Act (SEPA) reviews as related to street, sidewalk, drainage improvements, or traffic impacts. 2.3.1 TYPICAL REQUIREMENTS Typical requirements for all projects, except for single-family dwellings, set forth more specifically herein, may include the following: a. Design and construction of all new streets to provide adequate transportation service within a development; b. Design and construction of fronting improvements on existing streets necessary to provide adequate transportation service to, or within, a development, as applicable (see Sections 2.3.2 and 2.3.3); c. Adequate access for all parcels. Offsite streets used to access the project shall be improved to the applicable standard. Improvement shall extend from the nearest public street meeting the pavement width requirements, up to the project boundaries. Curb, and gutter, and sidewalk may not be required for the offsite improvements unless they are made necessary by the proposed development. However, provisions for stormwater management pursuant toper the Spokane Regional Stormwater Manual shall be required; d. Dedications of right-of-way and border easements for full build -out of the project's side of all adjacent and interior public streets (Chapter 7); c. Creation of future acquisition areas as required by the SVMC Chapter 22.130; Emergency access to all parcels of land, pursuant toin c of nuance with City standards and the latest International Fire Code; gf. Driveway approaches pursuant toin accordance with Chapter 7; h,g_Relocation of rigid objects out of the clear zone more specifically set forth in Chapter 7; Repair and replacement of damaged curb, gutter, swales/planters, sidewalk, survey monuments, etc, (Chapter W7); Removal of of abandoned or substandard approaches and replacement with frontage improvements (Chapter 7); and Ad pted December 2009 Chapter 2 — Development Eng-ineering Requirements 2-2 CITY OF SPOKANE VALLEY STREET STANDARDS k.Mitigations as determined bvi a traffic impact analysis, more specifically described in Chapter 3. Mitigations may include construction of or contributions to traffic calming devices, traffic signals, street lights, signing and/or pavement markings, etc. 2.3.2 SPECIFIC REQUIREMENTS FOR SHORT SUBDIVISIONS, LONG SUBDIVISIONS AND BINDING SITE PLANS a. Short subdivisions, long subdivisions, and binding site plans shall provide fronting improvements along all public streets adjacent to the project where access from the project is provided to the street. The extent of required improvements shall be based on existing conditions, the identified impact of the project or transportation improvement, and the applicable standard. Required improvements typically include pavement widening, curb, gutter, grassy swale and sidewalk. b. All land division projects shall fully improve new internal streets. c. If the existing fronting street is unimproved or will have less than 28 feet of pavement with fronting improvements, the Applicant shall provide half - street improvements as defined in Section 1.13. No sparking -Fire Lane On Pavement" signs shall be installed : • : • - : • - - - ser the latest adopted International Fire Code. Curb, gutter, and sidewalk are only required on the side of the street adjacent to the project's parcel(s). Provisions for stormwater management are required for the sides of the street being improved (Chapter 7). 2.3.3 SPECIFIC REQUIREMENTS FOR COMMERCIAL BUILDING PERMITS a. Fronting improvements for building permits are determined based on the type of project, square footage of the project, and peak hour vehicle trips. These projects shall provide improvements for the street fronting their projects pursuant toin accordance with Table 2.1. b. In the event that the street used to access the project is unimproved or has less than 28 feet of pavement, the Applicant shall provide fronting improvements and/or half -street improvements to meet the applicable standards regardless of the proposal type or size. In these instances, curb, gutter, and sidewalk requirements, for the side of the street adjacent to the project, shall be pursuant todetermined based on Table 2.1. Provisions for stormwater management are required for the sides of the street being improved. Ad pted December 2009 Chapter 2 — Development Entineerint Requirements 2-3 CITY OF SPOKANE VALLEY STREET STANDARDS TABLE 2.1 REQUIRED STREET IMPROVEMENTS FOR COMMERCIAL BUILDING PERMITS PROJECT PROPOSAL COMMERCIAL BUILDING PERMITS FOR PARCELS WITH EXISTING OR NEW BUILDING Gross Area of Building (for proposed additions or new structures) in sq. ft; or, Up to 999 1,000 to 5,999 6,000 to 11,999 12,000+ Number of New Peak Hour Trips Generated by Project Up to 4 5 to 9 10 to 15 16+ COMMERCIAL BUILDING PERMIT FOR PARKING LOT ONLY (NO NEW OR EXISTING BUILDING) Up to 9 spaces 10 to 19 spaces 20 to 40 spaces 41+ spaces REQUIRED IMPROVEMENTS Widen Pavement .((1) ./ .( Curb & Gutter (2) ./ ./ Grass Strip or Swale ./ ./ ./ Sidewalk (2) (2) ./ Right-of-way, Future ,((3) ./ ./ ./ Acquisition Area;, Border and Easements The final pavement width on the project's side of the street is the half -street width, plus six6 inches to allow for future curb installation. If the amount of pavement width needing to be added is less than 2two feet, then widening can be omitted unless the full width is less than 28 feet. Grassed ditches or swales are required along pavement edges required to be improved for stormwater treatment, regardless of amount of widening. 2. If a project is located in an area already improved to the requirements above, the project may be required to provide curb and gutter and/or sidewalk. 3. Not required if project is determined to have insignificant impact. d. When using Table 2.1 for commercial building permits with existing or new buildings, the Applicant shall identify the size of building and number of peak hour vehicular trips. The one triggering the most improvement requirements shall be used. For example, an Applicant is proposing an addition to an existing building; the proposed addition is 3,000 square feet. The proposal also generates 10 peak hour vehicular trips. This project shallwill be required to provide frontages -g improvements which include pavement widening, curb and gutter installation, grass strip/swale construction, and right-of-way and border easement dedication. If the required improvements currently exist, then the project shall be required to provide sidewalk. Ad pted December 2009 Chapter 2 — Development Entineerint Requirements 2-4 CITY OF SPOKANE VALLEY STREET STANDARDS 2.3.4 SPECIFIC REQUIREMENTS FOR MISCELLANEOUS PROJECTS Miscellaneous projects include access permits, boundary line adjustments, rezones, changes of use, changes of occupancy, temporary use permits and conditional use permits. In some instances, this last category of projects may not need a building permit. They may, however, result in an increase in traffic and other impacts that maycan require street improvements and/or other mitigation. Required improvements for change of use and conditional use permits are determined based on traffic impacts pursuant to the SVMC Cchapter 22.20 SVMC. Required improvements for boundary line adjustments, rezones, changes of occupancy, and temporary use permits are determined on a case-by-case basis during project review pursuant tousing the criteria specified in Section 2.3. 2.3.5 OTHER REQUIREMENTS Additional improvements may be required on a case-by-case basis, depending on site-specific conditions. These requirements may include, but are not limited to, the following: • Improvements previously required by the Spokane Valley City Council by ordinance, past land use action, or resolution, to be provided in the vicinity of the project; • New streets (and accompanying dedications) as required by the Street Master Plan, Local Street Plan, Sprague and Appletivay Corridors Subarea Plan _and according to the City's Comprehensive Plan; • Participation in the City's Transportation Improvement Program; • Other public improvements when physical characteristics of the property (including but not limited to topography, slope, soil type, drainage pattern or vegetation) create potential hazards; and, • Other public improvements necessitated by the public's health, safety, or welfare. Ad pted December 2009 Chapter 2 — Development Entineerint Requirements 2-5 CITY OF SPOKANE VALLEY STREET STANDARDS 2.4 MODIFICATIONS TO REQUIREMENTS 2.4.1 VARIANCE The requirements established in this chapter can only be waived or reduced through a variance. Refer to SVMC Title 19.170 for variance process and requirements. 2.4.22.4.1 CAPITAL PRO ECTSDEFERRING CONSTRUCTION Generally, all improvements shall be constructed prior to issuing a certificate of occupancy or final platting. In certain circumstances, installation of some or all of the frontage improvements may not be appropriate at the time development occurs. These may include instances where: a. Required improvements are part of a larger project scheduled for construction in the City's Transportation Improvement Program; or, b. Sanitary sewer is not available but is scheduled to come through in less than three years. In these situations, the installation of such improvements may be deferred to a later date or waived. A developmentcr's agreement may be required and a surety, as deemed sufficient by the City pursuant toconsistent with Section 9.14. 2.4.32.4.2 LIMITING SITE CONDITIONS Generally, all projects shall build public orand private streets and related improvements to the applicable standard. However, the City can may approve a slightly smaller sectionminor alterations to the requirements when full construction of the piiI344improyements renders the project unfeasibleis e not possible. Reduction of the requirements for public improvement may be considered if the parent short subdivision or subdivision parcel meets the following criteria: a. Is in an R1, R2, or R3 zone, and, b. Is smaller than 2.5 acres, and, c. Will have block lengths that do not exceed 300 feet for a through street; and, d. Has less than 216 feet of street frontage. The Applicant shall demonstrate that full improvement construction is not possible and propose an alternative(s) section. The Applicant is not guaranteed to have double frontage on the public street and/or the maximum number of lots at the minimum square footage allowed by the SVMC. All such proposals shall be approved -before the submittal of the preliminary plat application. Request after the preliminary plat application pproval will be required to go through the variance Adopted December 2009 Chapter 2 — Development Entineerint Requirements 2-6 CITY OF SPOKANE VALLEY STREET STANDARDS 2.5 APPLICANT'S RESPONSIBILITIES The Applicant is the party or parties desiring to construct a public or private improvement within City right-of-way, easements or private property, securing all required approvals and permits from the City, and assuming full and complete responsibility for the project. The Applicant may be the Owner or the individual designated by the Owner to act on his behalf. The Applicant is responsible for the following: a. General project management; b. Communicating requirements and project status with the Owner, if Applicant and Owner are not the same; c. Coordinating project consultants; d. Providing complete submittals; e. Ensuring all required applications have been submitted to the City; f. Ensuring adherence to: i. The standards and criteria presented in these Standards, as amended; ii. Hearing Examiner's decision and staff report with administrative decisions, if applicable; and, iii. Any conditions established by City staff. Ad pted December 2009 Chapter 2 — Development Entineerint Requirements 2-7 CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIONALLY LEFT BLANK Ad pted December 2009 Chapter 2 — Development Entineerint Requirements 2-8 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 3 -TRAFFIC ANALYSIS CHAPTER ORGANIZATION 3.1 INTRODUCTION 1 3.2 TRIP GENERATION & DISTRIBUTION LETTER GUIDELINES 2 3.2.1 Applicability 3 3.2.2 Minimum Elements 3 3.3 LEVIITED TRAFFIC IMPACT ANALYSIS 5 3.3.1 Applicability 5 3.3.2 Scope 5 3.3.3 Methodology 6 3.3.4 Limited TIA Report Minimum Elements 6 3.3.4.1 Title Page 6 3.3.4.2 Project Description and Summary 7 3.3.4.3 Proposed Development and Trip Generation 7 3.3.4.4 Summary of Existing Conditions 7 3.3.4.5 Background Projects 8 3.3.4.6 Other Analyses 8 3.3.4.7 Findings 9 3.3.4.8 Appendices 9 3.4 9 3.5 TRAFFIC IMPACT ANALYSIS 10 3.5.1 Applicability 10 3.5.2 Scope 10 3.5.3 Methodology 11 3.5.4 TIA Report Minimum Elements 13 3.5.4.1 Title Page 13 3.5.4.2 Introduction and Summary 13 3.5.4.3 Proposed Development 13 Adopted December 2009XXXX, 2018 Chapter 3 —Traffic Analysis 3-i CITY OF SPOKANE VALLEY STREET STANDARDS 3.5.4.4 Summary of Existing Conditions 14 3.5.4.5 Background Projects 15 3.5.4.6 Analysis Scenarios 15 3.5.4.7 Other Analyses 15 3.5.4.8 Findings 16 3.5.4.9 Appendices 16 3.6 MEETINGS 16 3.1 Introduction 1 3.2 ATRIP CENERATION & DISTRIBUTION LETTER GUIDELINES 1 3.2.1 Applicability 1 2 3 3 / 4,-34-1446414.6464egy 3 1.3.1 /IA Rep rt Minimum Elements 1 4.3.9.1 f itic Pag, 1 4.311.2 ntr ducti n and Summary 1 opo.,ed Deve1 pment 5 S ummary fExisting C nditi nc 5 4.3.9.5 Backgr and Pr jects 6 6 4.3.1.8 Fines 7 A3.4 MEETINGS 7 Adopted December 2009XXXX, 2018 Chapter 3 —Traffic Analysis 3 -ii Formatted: Default Paragraph Font, Font: Bold, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Font: Bold, Check spelling and grammar Formatted: Default Paragraph Font, Font: Bold, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted: Default Paragraph Font, Check spelling and grammar Formatted Formatted Formatted Formatted Formatted Formatted Formatted Formatted Formatted Formatted Formatted Formatted Formatted CITY OF SPOKANE VALLEY STREET STANDARDS THIS PACE IS INTENTIALLY LEFT BLANK Adopted December 2009XXXX, 2018 Chapter 3 —Traffic Analysis 3 -iii CITY OF SPOKANE VALLEY STREET STANDARDS 3.1 INTRODUCTION This chapter describes the contents of the trip generation and distribution letter and traffic impact analysis (TIA) submittals. The TIA is a comprehensive report containing all of the technical information and analysis necessary to evaluate a proposed new development or redevelopment project for compliance with level of service (LOS) standards. The City will a t sign ff n r ject until tr ns rt ti n c ncurrency h s cen etcnninc . All projects except those exempt pursuant toas set forth in the City of Spokane Valley Municipal Code (SVMC) e 22.20.020 shall beafe subject to transportation concurrency review. This review is conducted to ensure that adequate transportation facilities are provided in conjunction with new growth. Transportation concurrency shall be measured using the concept of level of service (LOS). Acceptable LOS thresholds are defined in the Spokane Valley Comprehensive Plan. This flowchart may be used to determine what type of transportation concurrency document is required. The City shall not sign off on a project until transportation concurrency has been determined. concurrency review. Trip Generation & Distribution Letter Required for all projects that generate more than f0 peak hour trip$ {see 5ettion 3.Z} Limited TIA Required for qualified projects within a SERA Infill Area that generate more than 20 peak hour trips at an arterial intersection 1 TIA req for all qualified projects that do not ;qualify for a Limited TIA and that generate more an 20 peak hour trips at an arterial intersection isec snceKm /A Adopted December 2009XXXX, 2018 Chapter 3 —Traffic Analysis 3-1 CITY OF SPOKANE VALLEY STREET STANDARDS The table below summarizes the mandatory scope elements for each type of analysis required by Spokane Valley: Table 1— Summary of Traffic Analysis Scope Elements Scope Elements Trip Generation Limited TIA TIA Letter Engineering Seal X X Title Page X Project Description and Summary Proposed Development and Trip Generation u; X Summary of Existing Conditions X Background projects and growth rate X Study Area Intersections of Collectors or higher within % mile X Intersections of Collectors or higher within 1 mile LOS Analyses Safety Analyses X Other Analyses (Operations, Sight Distance, Turn Lane ; Warrants, etc.) Analysis Scenarios (Peak Hours defined in scope) Existing Conditions Build -out year without project Build -out year with project Build -out + 5 years without project Build -out + 5 years with project Regional modeling — regional impacting development Findings X Appendices X Public Meetings 3.2 TRIP GENERATION & DISTRIBUTION LETTER GUIDELINES All projects which generate 10 or more new peak -hour vehicular trips shall submit a trip generation and distribution letter. The letter shall be based on the current version of thelatest edition of the Institute of Transportation Engineers (ITE) Trip Generation Manual and developed by an Engineer. If a project is subject to State Environmental Policy Act (SEPA) review, the trip generation and distribution letter shall be submitted for review at the time of the SEPA application. The letter is required to be approved by the City prior to submittal of a traffic impact analysis report. Adopted December 2009XXXX, 2018 Chapter 3 —Traffic Analysis 3-2 CITY OF SPOKANE VALLEY STREET STANDARDS 3.2.1 APPLICABILITY a. A trip generation and distribution letter is required for most projects. However, the following projects are typically under the peak -hour threshold and may not be required to prepare a trip generation and distribution letter: i. Residential short plats; (the number of trips from a duplex shall be equivalent to two single family homes); ii. Drive-through coffee stands with no indoor seating; iii. Multi -family projects with nine (9) units or less; iv. Changes of use from residential to commercial with no new buildings or building additions; v. Office projects of less than 2,500 square feet€ (ITE land uses 700-799); and, vi. Industrial projects of less than 9,000 square feet (ITE land uses 100- 199). b. For projects expected to generate less than 10 peak -hour vehicular trips the project applicant is required to submit a letter with the following information for all proposed development phases for the property: i. Brief project description; ii. Number of expected employees; iii. Hours of business; and, iv. The expected number of vehicular trips (customers and employees) to the business during the AM and PM peak hours. 3.2.2 MINIMUM ELEMENTS The trip generation and distribution letter for projects generating 10 or more peak - hour trips shall include the following elements: a. Project description, including proposed use; b. Site plan with vicinity map; c. Building size noted in square feet; d. Zoning of the property; e. Determination of whether the project is in a SEPA Infill Area (see following section); �f. Proposed and existing access points, site circulation, queuing lengths for driveways (and drive-throughs, if applicable) and parking locations; €g_Project phasing and expected build out year; gh.An estimate of trip generation for the typical weekday, AM peak -hour, and PM peak -hour conditions. Supporting calculations and data sources shall Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-3 CITY OF SPOKANE VALLEY STREET STANDARDS be shown. Any adjustments for transit use, mixed use internalization, pass - by trips, and/or diverted trips shall be clearly stated; tri A comparison of the trip generation between the previous and the proposed site use for projects involving a change of use. If the comparison shows a net increase in trip generation, the project shallwill be subject to the TIA requirements of a new development; preliminary distribution pattern for traffic on the adjacent street network, shown in a graphical format; and, j -k. The engineering seal signed and dated by the l engineer who prepared the letter. Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-4 CITY OF SPOKANE VALLEY STREET STANDARDS 3.3 LIMITED TRAFFIC IMPACT ANALYSIS Pursuant to SVMC 21.20.040, portions of Spokane Valley had additional environmental review performed as part of the Comprehensive Plan EIS. Because of the additional environmental review within the SEPA Infill Areas, the majority of development projects within these areas do not require a full TIA report if the Applicant adopts the subarea environmental analysis and mitigation requirements identified in the SEPA documents. However, to assess potential traffic safety or site access issues, a limited TIA is required as set forth below. 3.3.1 APPLICABILITY A limited TIA is required for the following situations: a. Projects adding 20 or more peak -hour trips through an arterial intersection and which are located within a SEPA Infill Area; b. Projects within a SEPA Infill Area that impact local access intersections, alleys, or driveways located within an area with a current traffic problem as identified by the City or previous traffic study, such as a high -accident location, poor roadway alignment, or area with a capacity deficiency; or c. At the discretion of the City in lieu of a full TIA. A full TIA (see Section 3.4) is required for land uses that exceed the total trip bank established in SVMC 21.20.040. Applicants are encouraged to consult with City staff if they are unsure if they apply for both SEPA relief and a limited TIA. 3.3.2 SCOPE The scope of the limited TIA shall be developed by an engineer. A draft scope shall be reviewed and approved by the City prior to submission of the limited TIA. The scope of the limited TIA shall conform to the following: a. The study area may include any intersections or streets within a 1/2 mile radius of the site. b. A safety analysis may be required as identified by City staff in the scope review phase. If the analysis is required, the City shall assist by providing crash data if available. Safety analysis at a minimum requires three years of crash history showing the date and time, type, number of vehicles involved in the crash, including weather and road conditions. Crash analysis shall include bicycle and pedestrian crashes. Crash information shall be assessed by the developer's engineer to identify possible impacts the proposed new trips would add to the problem. Examples may include queuing that exceeds storage pocket lengths or that extends to upstream intersections, recurring left tum crashes, limited sight distance, or proposed project access intersections that may be poorly placed. c. If a safety and operational analysis reveals deficiencies, then mitigation measures shall be developed with recommendations to fix the deficiencies. Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-5 CITY OF SPOKANE VALLEY STREET STANDARDS d. Unless otherwise identified by the City, the analysis shall be performed for the build -out year of the proposed development. 3.3.3 METHODOLOGY The analysis shall be done using the following methodology: a. Background growth rate — The background growth rate may be based on historical growth data or the growth rate as calculated from Figures 30 and 32 of the Comprehensive Plan (the 2016 and 2040 average daily traffic volumes). A minimal annual growth rate of 1% is required unless otherwise approved by the City; b. The LOS shall be determined in accordance with the methods reported in the current version of the Highway Capacity Manual (HCM); c. Use of the two-stage gap acceptance methodology for unsignalized intersections is subject to City approval; d. "Synchro" is the primary traffic software used by the City to model intersection and tum pocket queuing analysis. Depending on the analysis, the City may request other traffic analysis using other modeling software. In addition to Synchro, the engineer may use the most current version of Highway Capacity Software (HCS). Other analysis tools may be utilized with City approval if HCM methodology cannot accurately model an intersection; e. Trip generation data shall be based on the latest version of the ITE Trip Generation Manual. Trip generation data from studies of similar facilities may be substituted with prior City approval; and, f. Turning movement counts and crash diagrams may need to be developed to document a safety or operations problem. If traffic counts are required, they shall be taken on a Tuesday Wednesday or Thursday representing a typical travel day. Counts shall not be taken during a week which contains a holiday or during a week of a significant weather event. Projects near schools may be required to collect turning movement counts during a typical school day. 3.3.4 LIMITED TIA REPORT MINIMUM ELEMENTS The limited TIA report shall include at least the following: 3.3.4.1 Title Page The limited TIA shall include a title page with the following elements: a. Name of project; b. City project number/permit number; c. Applicant's name and address; d. Engineer's name, address and phone number; Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-6 CITY OF SPOKANE VALLEY STREET STANDARDS e. Date of study preparation; and, f. The engineering seal, signed and dated by the professional engineer licensed in the State of Washington who prepared the report. 3.3.4.2 Project Description and Summary The limited TIA shall include a brief description of project, location, study intersections, findings, and mitigation. 3.3.4.3 Proposed Development and Trip Generation The limited TIA shall include the following information for the proposed development: a. Project description, including proposed use; b. Site plan with vicinity map; c. Building size noted in square feet. d. Zoning of the property; e. Determination of whether the project is within a SEPA Infill Area (see following section); f. Proposed and existing access points, site circulation, queuing lengths for driveways (and drive-throughs, if applicable) and parking locations; g. Project phasing and expected opening year h. An estimate of trip generation for the typical weekday, AM peak - hour, and PM peak -hour conditions. Supporting calculations and data sources shall be shown. Any adjustments for transit use, mixed use internalization, pass -by trips, and/or diverted trips shall be clearly stated; i. A comparison of the trip generation between the previous and the proposed site use for projects involving a change of use. If the comparison shows a net increase in trip generation, the project shall be subject to the limited TIA requirements of a new development j. A preliminary distribution pattern for traffic on the adjacent street network, shown in a graphical format and, k. Project phasing and timing. 3.3.4.4 Summary of Existing Conditions The limited TIA shall provide a brief summary of existing conditions for the study area that includes at least the following: a. Brief summary of the transportation network adjacent to the site including a qualitative description of the facilities, speed limits, presence of bike lanes/trails, bus stops, and on -street parking; Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-7 CITY OF SPOKANE VALLEY STREET STANDARDS b. Figure or table of the peak hour turning movement volumes at the study intersections; c. Collision history — three years minimum; d. Length of existing turn pockets at study intersections; and, e. Other information as identified during the scoping process. 3.3.4.5 Background Projects If background project traffic is necessary to assess build -out conditions it shall include the following: a. Traffic from newly constructed projects; b. Projects for which traffic impacts have been tentatively reserved; c. Projects for which a Concurrency Certificate has been awarded; d. Non -project, general background traffic increases; and, e. Vested traffic for vacant buildings that are undergoing redevelopment. The limited TIA shall provide the following information for background projects, as identified by the City: a. Project descriptions; b. Vicinity map; c. Trips generated by projects and assigned to study intersections, d. Figure or table of the build -out peak hour turning movement volumes at the study intersections; e. Planned transportation improvements (private development and City); and, f. Where required, safety and operations analysis results. 3.3.4.6 Other Analyses Other analyses may be required as requested by the City, including but not limited to: a. Queue lengths at driveways and drive-through windows; b. Noise; c. Air quality (typically required when physical improvements are proposed and requires electronic submittal of Synchro files); d. Intersection control warrant analysis (signal, roundabouts, four-way stop yield)- e. ield)e. Auxiliary lane warrant analysis; f. Parking study (including vehicles and/or bicycles); Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-8 CITY OF SPOKANE VALLEY STREET STANDARDS g. Site access; and, h. Pedestrian access study. 3.3.4.7 Findings The following shall be addressed in the findings section: a. Traffic and safety impacts; b. Proposed project modifications; and, c. Off-site mitigation. 3.3.4.8 Appendices The following information shall be included in appendices: a. Definitions; b. Trip generation sources; c. Passer-by and origin -destination studies (if applicable); d. Volume and turning movement count sheets; e. Analysis software (Synchro, HCS, SimTraffic, etc.) report printouts (electronic submittal may be required); f. Warrant analysis calculations; and, g. References. Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-9 CITY OF SPOKANE VALLEY STREET STANDARDS 3.4 TRAFFIC IMPACT ANALYSIS -RIA) For developments that are not within a SEPA Infill Area, this section outlines the requirements for a TIA. The intent of the TIA is to allow the City to properly plan and improve the transportation system to meet the mobility needs of future growth and to comply with SEPA requirements. 3.2.33.4.1 APPLICABILITY A TIA is required for the following situations: a. Projects adding 20 or more peak -hour trips to an intersection of arterial streets, as defined in Chapter 1 of the City's Comprehensive Plan, within a one -mile radius of the project site as shown by the trip generation and distribution letter; or, b. Projects impacting local access intersections, alleys, or driveways located within an area with a current traffic problem as identified by the City or previous traffic study, such as a high -accident location, poor roadway alignment or capacity deficiency. 3.2.43.4.2 SCOPE The scope of the TIA shall be developed by an professional engineer licensed in the State of Washington. Prior to submittal of the TIA, the City and other impacted jurisdictions/agencies shall approve the scope of the TIA. The scope of the TIA shall conform to the following: a. The study area shall include any intersections of arterial streets within a one - mile radius of the site that would experience an increase of at least 20 vehicle trips during a peak hour. Some intersections may be excluded if analyzed within the past year and are shown to operate at LOS C or better. All site access points shall be analyzed. Additional arterial intersections outside of the one mile radius and intersections of local streets may also be required at the discretion of the City; b. If any of the study intersections are on a Major Arterial Corridor, a corridor LOS analysis shall be conducted for all relevant corridors. For example. If a project increases traffic by 20 vehicles at the intersection of Pines Road/Mission Avenue then a corridor LOS analysis shall be required for Pines Road. If a corridor has been analyzed within the last two years and is shown to operate at LOS C or better, the City may exempt the corridor LOS analysis, although traffic counts on the corridor may still be required in order to maintain an up-to-date database of counts along the Major Arterial Corridors. Below is a list of the Major Arterial Corridors from the Comprehensive Plan: • Argonne/Mullan Road between Trent Avenue and Appleway Blvd Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-10 Formatted: Bulleted + Level: 1 + Aligned at: 1.75" + Tab after: 2" + Indent at: 2" CITY OF SPOKANE VALLEY STREET STANDARDS • Pines Road between Trent Avenue and 8th Avenue • Evergreen Road between Indiana Avenue and 8th Avenue • Sullivan Road between Wellesley Avenue and 8th Avenue • Sprague Avenue/Appleway Blvd between Fancher Road and Park Road b-c.A PM peak hour LOS analysis shall be conducted for all study area intersections- (and corridors if applicable). An LOS analysis of the AM peak hour, Saturday afternoon, or other time period may be required at the discretion of the City; and, d. As identified by City staff in the scope review phase, a safety analysis may be required, which may include intersection queuing, tum lane warrants and LOS, sight distance, and pedestrian/bicycle conflicts to identify potential safety issues; and, e:e. Additional analysis may be required by other reviewing agencies. The Intersection and corridor (if applicable) LOS shall meet or exceed the thresholds pursuant tocet forth in the City's of Spokane Valley Comprehensive Plan — Chapter 4: Capital Facilities, Table 4.3 Spokane Valley Level of Service Standards. In the event that the LOS standard is not met, the project applicant shall work with the City to identify appropriate mitigation measures, which could include modification of the intersection designs, constructing/funding improvements to City -owned intersections, or changing the scale of the development. A safety analysis may be required, as identified by City staff in the scope review phase. If the analysis is required, the City shall assist by providing crash data if available. Safety analysis at a minimum requires three years of crash history showing the date and time type number of vehicles involved in the crash weather and road conditions. Crash analysis shall include bicycle and pedestrian crashes. Crash information shall be assessed by the developer's engineer to identify possible impacts proposed new trips would add to the problem. Examples may include queuing that exceeds storage pocket lengths or that extends to upstream intersections recurring left tum crashes limited sight distance or proposed project access intersections that may be poorly placed. Safety issues shall be mitigated to the satisfaction of City staff. 3.4.3 METHODOLOGY The analysis shall be done using the following methodology: a_ Background growth rate — The background growth rate may be based on historical growth data and/or the Spokane Regional Transportation Council (SRTC) Regional Travel Demand Model, or the growth rate as approved by the City. This rate is to be applied to existing turning movement volume prior to the addition of background project calculated from Figures 30 and 33 of the Comprehensive Plan (the 2016 and 2040 average daily traffic of Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-11 CITY OF SPOKANE VALLEY STREET STANDARDS cite generated traffic volumes. The). A minimal annual growth rate of 1%. 10 percent is required. Under no circumstances shall the Frowth rate be less than 1.1 percent; unless otherwise approved by the City; b. The LOS shall be determined in accordance with the methods reported in the current version latest edition of the Highway Capacity Manual (HCM) or as further defined by City staff; c. Corridor LOS shall be determined by calculating the volume -weighted average intersection LOS of all signalized arterial/arterial intersections along the defined length of the Major Arterial Corridor.1 With all intersection LOS calculated along the corridor, the control delays of all intersections shall be averaged to calculate total corridor LOS. The same control delay thresholds defined for individual intersections shall be used to assign corridor LOS (e.g., corridor average control delay of 38 seconds would correspond to LOS D). Based on City input, WSDOT ramp terminal intersections may or may not be included as part of the corridor LOS calculation, and may be evaluated separately as individual intersections. d. Use of the two-stage gap acceptance methodology for unsignalized intersections is subject torequires prior City approval; a -e." Synchro" is the primary traffic software used by the City to model intersection and tum pocket queuing analysis. Depending on the analysis, the City may request other traffic analysis using other modeling software. In addition to Synchro, the Engineer may use the most current version of HCS. Other analysis tools may be utilized with prior City approval if HCM methodology cannot accurately model an intersection; f. Trip generation data shall be based on the currenthatest versionedition of the ITE Trip Generation Manual. Trip generation data from studies of similar facilities may be substituted as approved by the City; and, ,Turning movement counts shall be recorded less than one year prior to submitting a traffic study. Counts less than two years old may be used if no significant development projects or changes to the transportation network have occurred. -Counts shouldshall be taken on a Tuesday, Wednesday, or Thursday representing a typical travel day. -Counts shouldshall not be taken during a week which contains a holiday- or during a week of a significant weather event. Projects near schools may be required to collect turning movement counts during idea typical school day. Given the potentially large-scale of corridor LOS evaluation, counts older than one year- may be used for intersections along a corridor that are more than one mile away, so long as they are factored using the growth rate identified above. However, the City may request, at its discretion, that the project collect new traffic To clarify, unsignalized project driveway intersections with the Major Arterial Corridor are not part of the corridor LOS calculation since they are not arterial streets. Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-12 CITY OF SPOKANE VALLEY STREET STANDARDS counts at any intersection along a relevant Major Arterial Corridor in an effort to maintain a relatively current database for TIA review. 3.2.53.4.4 TIA REPORT MINIMUM ELEMENTS The TIA report shall include at least the following, at a minimum: 3.2.5.13.4.4.1 Title Page The TIA shall include a title page with the following elements: a. Name of project; b. City project number/permit number; c. Applicant's name and address; d. Engineer's name, address and phone number; e. Date of study preparation; and, f. The engineering seal, signed and dated by the professional engineer licensed in the State of Washington who prepared the report. 3.2.5.23.4.4.2 Introduction and Summary a. Purpose of report and study objectives; b. Executive summary; c. Proposed development description; d. Location and study area; e. Findings; and, f. Recommendations and mitigation. 3.2.5.33.4.4.3 Proposed Development The TIA shall include the following information for the proposed development: (this is the same information that is required for the trip letter): a. Project description; b. Location and vicinity map; c. Site plan with building size (square feet); d. Proposed zoning; e. Land use; f. Access points, site circulation, queuing lengths, and parking locations; Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-13 CITY OF SPOKANE VALLEY STREET STANDARDS g. An estimate of trip generation for the typical weekday, AM peak - hour, and PM peak -hour conditions. Any adjustments for transit use, pass -by trips, and/or diverted trips shall be clearly stated; h. A distribution pattern for traffic on the adjacent street network, shown in a graphical format; and, i. Project phasing and timing 3.2.5.43.4.4.4 Summary of Existing Conditions The TIA shall provide a summary of existing conditions for the study area that includes the following: a. Transportation network description, including functional classification, bike/pedestrian facilities and transit routes; b. Existing zoning; c. Existing traffic volumes including percent heavy vehicles; d. AccidentCollision history past three4 years minimum; e. Posted speed limits (and if known the 85 percentile speed determined from a speed study); f. Length of existing turn pockets at signalized intersections; and, g. Location of -the following: i. On -street parking, ii. Bus stops, and iii. Private and public schools in the area, and, ah.Hospitals, policcLOS and fire stations in the arcasafety analysis results. Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-14 Formatted: Numbered + Level: 1 + Numbering Style: a, b, c, ... + Start at: 1 + Alignment: Left + Aligned at: 1.75" + Tab after: 2" + Indent at: 2" CITY OF SPOKANE VALLEY STREET STANDARDS 3.2.5.53.4.4.5 Background Projects Background project traffic shall includes the following: a. Traffic from newly constructed projects; b. Projects for which traffic impacts have been tentatively reserved; c. Projects for which a Concurrency Certificate has been awarded; d. Non -project, general background traffic increases; and, e. Vested traffic for vacant buildings that are undergoing redevelopment. The TIA shall provide the following information for background projects, as identified by the City: f. Project descriptions; a. Vicinity map; b. Trip generation; c. Trip distribution; and, d. Planned transportation improvements (private development and City*); and, e. LOS and safety analysis results. 32.5.63.4.4.6 Analysis Scenarios The TIA shall include the following analysis scenarios: a. Existing conditions; b. Build -out year without project; c. Build -out year with project; d. Build -out + five4 year analysis if project is expected to proceed in phases, take more than six6 years to complete, or if the study intersection is included on the City's Six& -Year TIP; and, e. Build out Yc r + 20 analysis if the project mitigation involves installation or modification to an intersection controlledMajor developments with a traffic sitnal or roundabout. Forecast volumes slregional impacts may be estimated usingrequired to use the current version of the SRTC Regional Travel Demand Model- and the associated horizon years for analyses, as determined by City staff. 3.2.5.73.4.4.7 Other Analyses Other analyses may be required as requested by the City, including but not limited to: a. Sitht distance; Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-15 CITY OF SPOKANE VALLEY STREET STANDARDS b. Queue lengths at signalized intersections; 4a.Queue lengths at driveways and drive-pthrough windows; e,b.Noise; Air quality (typically required when physical improvements are proposed and requires electronic submittal of Synchro files); gd.Intersection control warrant analysis (signal, roundabout, four4-way stop, yield); e.Auxiliary lane warrant analysis; f. Parking study (including vehicles and/or bicycles); i g_Site access; and, }h. Pedestrian access study. 3.2.5.83.4.4.8 Findings The following shall be addressed in the findings section: a. Traffic impacts; b. Compliance with level of service standards; c. Proposed project improvementsmodifications; and, d. Recommendations and Offsite mitigation. 3.2.5.93.4.4.9 Appendices The following information shall be included in appendices: a. Definitions; b. Trip generation sources; c. Passer-by and origin -destination studies; d. Volume and turning movement count sheets; c. Level of service calculations Synchro report printouts (electronic submittal may be required); gf. Warrant analysis calculations; and, a. References. 3.33.5 MEETINGS A public meeting(s) may be required for any residential project generating over 100 PM peak -hour trips, commercial projects generating over 100 PM peak -hour trips impacting a residential area, or for other projects at the discretion of the City. The intent of the public meeting is to let the public know about the proposed project and to allow for public input Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-16 Formatted: Numbered + Level: 1 + Numbering Style: a, b, c, ... + Start at: 1 + Alignment: Left + Aligned at: 1.75" + Tab after: 2" + Indent at: 2" CITY OF SPOKANE VALLEY STREET STANDARDS to determine the scope of the TIA. Notice of date, time, place and purpose of the public meeting(s) shall be provided by the following means: a. One publication in the City'sSpokanc Valley' official newspaper at least 15 days prior to the meeting; b. A mailing to adjacent residents, property owners, neighborhood groups, jurisdictions, and—/or organizations within a 400 -foot radius of the project boundaries, not less than 15 days prior to the public meeting. Other persons or entities outside of the 400 -foot radius may be required to be notified if the City determines they may affected by the proposed project or have requested such notice in writing; and, c. A sign shall be erected, on the subject property fronting and adjacent to the most heavily traveled public street, at least 15 days prior to the meetings. The sign shall be at least four4 feet in width and four4 feet in height and shall have letters three3 inches in size. The sign shall be easily read by the traveling public from the right- of-way. This sign shall announce the date, time and place of the traffic meetings and provide a brief description of the project. Proper notification and all associated costs shall be the responsibility of the Applicant. Notification shall be considered satisfied upon receipt of an affidavit provided by the Applicant to the City stating the above requirements have been completed. Adopted December 2009XXXX, 2018 Chapter 3 — Traffic Analysis 3-17 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 4 - REQUIREMENTS FOR PLAN SUBMITTAL Chapter Organization Introduction 4.1 1 4.2 General Requirements 1 4.2.1 Plan Completeness 1 4.2.2 Fonts 1 4.2.3 Lines and Symbols Error! Bookmark not defined. 4.2.4 Sheet Size / Plan Medium 1 4.2.5 Engineer Signature and Stamp 1 4.2.6 Scale 1 4.2.7 North Arrow 2 4.2.8 Vertical and Horizontal Datum 2 4.2.9 Utility Locate Note 2 4.2.10 Title Block 2 4.2.11 Required Civil Plan Sheets 2 4.2.12 Required Traffic Plan Sheets 3 4.2.13 Other Required Plan Sheets 3 4.3 Specific Requirements for Plan Sheets 3 4.4 Cover Sheet 4 4.4.1 Applicability 4 4.4.2 Minimum Elements 4 4.5 Clearing and Grading Plan 5 Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-i CITY OF SPOKANE VALLEY STREET STANDARDS 4.5.1 Applicability 5 4.5.2 Minimum Plan Elements 5 4.6 Street Improvements Plan 6 4.6.1 Applicability 6 4.6.2 Minimum Plan View Elements 6 4.6.3 Minimum Profile View Elements 8 4.6.4 Minimum Typical Cross Section Elements 8 4.7 Onsite Improvement Plan 9 4.7.1 Applicability 9 4.7.2 Minimum Elements for Onsite Improvement Plan 10 4.8 Drainage Plan 10 4.9 Temporary Erosion and Sediment Control Plan 10 4.10 Temporary Traffic Control Plan 10 4.11 Permanent Traffic Control Plan 11 4.11.1 Area Map 11 4.11.2 Road Segment Pages 11 4.11.3 Signing Plan 11 4.11.4 Striping Plan 11 4.11.5 Traffic Signal Plan 12 4.12 Site Plan of Record 12 List of Appendices Appendix 4-A - General Construction Notes 13 Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4 -ii Formatted: Normal, Tab stops: Not at 0.5" + 1.25" CITY OF SPOKANE VALLEY STREET STANDARDS 4.1 INTRODUCTION The Applicant is required to submit a complete plan set for all proposed public and private improvements. This chapter provides the minimum plan elements for a complete submittal. To be accepted for review, plans shall be clear, concise and easy to read with all lettering and lines legible. Hand drawn plans are not acceptable. Incomplete plan sets shallwill not be reviewed and will be returned to the Applicant. State law requires that engineering work be performed by or under the direction of a professional engineer currently licensed in the State of Washington. 4.2 GENERAL REQUIREMENTS 4.2.1 PLAN COMPLETENESS All plan submittals are assumed to be the final plan set and so all plan sheets for every submittal shall be signed by the Applicant's Engineer pursuant toas per Section 1.2.5 4.2.4. It is the responsibility of tThe Applicant's Engineer shallte verify that all minimum requirements specified in the Street Standards and the Spokane Regional Stormwater Manual are met and are incorporated in the plan set. Each submittal of revised plans and supporting documents shall be accompanied by a letter that indicates how each review comment was addressed and provides a brief description of any changes made that were not in direct response to a review comment. 4.2.2 FONTS Lettering shall be legible to be easily read and understood by the reviewer. Lettering shall be of sufficient size and scale to produce clear, readable images when scanned digitally by an optical scanner. 4.2.3 SHEET SIZE / PLAN MEDIUM All plan sets shall be plotted or copied on standard drafting paper with dark ink. When the plans or plats are accepted, the City will specify the media type required in the acceptance letter. All plan sheets shall be 24 inches by 36 inches (D size). 4.2.4 ENGINEER SIGNATURE AND STAMP All sheets shall include the engineer's signature, stamp, and date of signature pursuant toin accordance with the regulations established by the State of Washington Board of Registration of Professional Engineers. 4.2.5 SCALE The scale for all plan and profile sheets shall be: a. Horizontal: 1 inch = 20, 30, 40, or 50 feet (scales greater than 1 inch = 50 feet shall not be accepted) b. Vertical: 1 inch = 5 or 10 feet Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-1 CITY OF SPOKANE VALLEY STREET STANDARDS c. Overall plan: 1 inch = 100 feet, maximum d. Cross sections: vertical exaggeration ratio shall be 5:1 4.2.6 NORTH ARROW All design sheets shall have a north arrow oriented toward the top or right side of applicable sheets. 4.2.7 VERTICAL AND HORIZONTAL DATUM The City of Spokane Valley vertical datum shall be based on the National North American Vertical datum (NAVD 1988). The horizontal datum is a coordinate system based on 1983(91) State Plane Coordinates. 4.2.8 UTILITY LOCATE NOTE All utilities shall be located prior to construction. All sheets shall have the following message: CALL TWOS BUSINESS DAYS BEFORE YOU DIG 811 OR 1 800 424 5555 4.2.9 TITLE BLOCK A title block is required on every sheet. The title block shall be located in the extreme lower right hand corner, the right side margin, or along the bottom edge of the sheet. The following information shall appear in the title block: a. Project name and number (including permit number, Short subdivision, Subdivision or Binding Site Plan numbers) provided by the City; b. The type and location of improvement. (For profile sheets, the title block shall have the name of the street and beginning/end stations); c. Engineer's name, address, including zip code, telephone number, and fax number; d. Date and brief description of all revisions; e. Sheet number and total number of sheets; and, 4.2.10 REQUIRED CIVIL PLAN SHEETS Civil plan sets are reviewed by Development Engineering. The civil plan set shall include the following, as applicable: a. Cover sheet (see Section 4.4); b. Clearing and grading plan (see Section 4.5 ); c. Street improvement plan (see Section 4.6); d. Onsite improvement plan (see Section 4.7); e. Drainage plan (see Section 4.8); f. Temporary erosion and sediment control plan (see Section 4.9); and, Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-2 CITY OF SPOKANE VALLEY STREET STANDARDS g. Detail sheets, as needed. 4.2.11 REQUIRED TRAFFIC PLAN SHEETS Traffic plan sets are reviewed by the Traffic Division of the Public Works Department. The traffic plan set shall include the following, as applicable: a. Permanent traffic control plan (see Section 4.11); b. Detail sheets, as needed. 4.2.12 OTHER REQUIRED PLAN SHEETS The site plan of record is reviewed by Development Engineering and the Planning Division. See Section 4.12 for the requirements from Development Engineering. 4.3 SPECIFIC REQUIREMENTS FOR PLAN SHEETS This section incorporates sections 4.4 to 4.12, which outline the minimum required information to be included on specific sheets of the plan set. The sheets are listed in the order they should appear in the plan set. Some sections of the plan set may have more than one sheet, but should be labeled alike. 4.4 Cover Sheet 4.5 Clearing and Grading Plan 4.6 Street Improvements Plan 4.7 On-site improvement Plan 4.8 Drainage Plan 4.9 Temporary Erosion and Sediment Control Plan 4.10 Temporary Traffic Control Plan 4.11 Permanent Traffic Control Plan 4.12 Site Plan of Record Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-3 CITY OF SPOKANE VALLEY STREET STANDARDS 4.4 COVER SHEET 4.4.1 APPLICABILITY All plan sets shall include a cover sheet. 4.4.2 MINIMUM ELEMENTS The following shall be included on the cover sheet: a. The project name and the number (including permit number, Short Subdivision, Subdivision or Binding Site Plan numbers) shown in the top center of the page; b. A legible vicinity map, approximately 8-'/2 inches by 11 inches, showing the location and name of all arterial roadways within one mile of the proposed construction, and all other roadways within 1/2 mile of the proposed construction. The project area shall be indicated by shading; c. An index of all sheets within the plan set; d. Impervious area quantities for all commercial projects. Quantities shall include the existing, proposed and total rooftop area, pavement area and gravel area, and the overall, total impervious area; e. Type of roofing material for all commercial projects; f. Section, Township, and Range; g. Legend of line types and symbols for all appurtenances related to each type of facility; h. General construction notes as provided in Appendix 4A; i. Applicant's signature; j. The datum used and all benchmarks, which must refer to the established control when available; k. Private Improvements Statement. The note below shall appear on the cover sheet of the construction plans that include private streets and : The City of Spokane Valley will not be responsible for the maintenance ofstreet and appurtenant improvements, including storm drainage structures and pipes, for the following private streets: (list street names). 1. Name of owner and Applicant. Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-4 CITY OF SPOKANE VALLEY STREET STANDARDS 4.5 CLEARING AND GRADING PLAN 4.5.1 APPLICABILITY Clearing and grading sheets are required for projects applying for: a. A clearing and grubbing permit; b. A grading only permit; c. A building permit for all new non-residential development and for residential construction of four or more units per lot; d. Short subdivisions; e. Long subdivisions; or f. Binding Site Plans. 4.5.2 MINIMUM PLAN ELEMENTS Clearing and grading sheets shall clearly convey design and construction intent and shall depict only the work to be done with the requested permit. Clearing and grading sheets shall include, as applicable: a. Property limits and accurate contours of existing ground elevations. For existing topography, one -foot contour intervals are preferred unless the City determines that available fives -foot contour mapping is adequate and detailed enough to describe current landforms; b. The extent of clearing and/or grading areas, delineated and labeled "excavation" or "fill"; c. Finish contours to be achieved by the grading and related construction. The contour interval for proposed topography shallmust be no more than 1- foot, unless the slope is greater than 10% percent, in which case, the City may accept five4-foot contour intervals. Periodically call out the proposed slope. One -foot contours may still be necessary to show certain features such as swales; d. Existing and proposed surface and subsurface drainage facilities; e. Footprint of onsite buildings or structures and the location of adjacent buildings or structures located within 15 feet of the property or which may be affected by the proposed grading operations; f. Cross-section along the proposed and/or existing street, spaced every 50 feet, when required by the City. The cross-sections shall show proposed and existing topography along the street, at tie in points and property boundaries; Information covering construction and material requirements including, but not limited to, specification of the soil compaction to be achieved in any areas of fill placement; h. Estimated amount and vertical dimensions of cut and fill; g. Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-5 CITY OF SPOKANE VALLEY STREET STANDARDS i. Delineation of sensitive areas, floodplains, and critical areas pursuant to pe the SVMC Title 21; j. The approximate location of all trees Seight-inches diameter breast height (dbh) and larger, and a description of the tree protection standards to be implemented during construction; k. Delineation of any areas to be preserved. 4.6 STREET IMPROVEMENTS PLAN 4.6.1 APPLICABILITY Street improvements sheets are required for projects: a. Proposing new or revisions to public or private street or street extensions; b. Proposing private engineered driveways; or, c. Required to provide frontage improvements. 4.6.2 MINIMUM PLAN VIEW ELEMENTS The plan view shall include, at a minimum, the following: a. Survey lines and stationing lines. Lines shall normally be based on centerline of street. Other profiles may be included but shall be referenced to centerline stationing. Stationing in cul-de-sacs shall be on the centerline to the center of the bulb, with dimensioned slopes along the flowlines within the bulb; b. Property limits and accurate contours of existing ground elevations. For existing topography, one -foot contour intervals are preferred unless the City determines that available 5 -five-foot contour mapping is adequate and detailed enough to describe current landforms; c. Finish contours to be achieved by the grading and related construction. The contour interval for proposed topography must be no more than one- foot, unless the slope is greater than 10% percent, in which case, the City may accept 5 -five-foot contour intervals. Periodically call out the proposed slope. One -foot contours may still be necessary to show certain features such as swales; d. Lot lines, lot numbers and block numbers; e. Proposed and adjoining subdivision names; f. Existing and proposed street names; g. Section, Township, and Range; h. Existing and proposed property and/or right-of-way lines, easements, and/or tracts. All of them shall be labeled and dimensioned; i. Road alignments with 100 -foot stationing, reading from left to right, and stationing at points of curve, tangent, and intersections, with appropriate ties Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-6 CITY OF SPOKANE VALLEY STREET STANDARDS to existing road surveys and stationing, section corners, quarter comers, and the County GPS control net. Stations shall increase from west to east and from south to north; } Match lines and stations; k. Bearings on the road centerline, keyed to an associated plat map; 1. Station and elevation of all horizontal curves including PI, PC's, PT's, etc.; existing and proposed, centerline bearings, distances, and complete curve data; m. Curve data including radius, delta, arc length and semi -tangent length on all street centerlines and curb returns; n. Stations and elevations of all curb returns; including beginning, mid -point, and ending elevations of curb retums; o. Location of all proposed and existing approaches; p. All existing utilities; q. All proposed utilities that will be designed and constructed. The plan sheet shall show the extent of the pavement cut for connections; r. Proposed drainage features including station and type of all structures, direction of flow, size and kind of each drainage channel, ditch or pipe and any other requirements as specified in the Spokane Regional Stormwater Manual, as adopted or amended; s. A thorough search for all survey monuments shall be conducted. Any survey monuments shall be shown; t. Fire hydrant locations; u. No Parking signs and locations; v. Turnaround locations; w. Fire emergency access easements; x. Traffic elements such as conduit, junction boxes, signal cabinets, electrical service, signal poles, push-button poles, and loops; Storm drainage flow direction arrows, particularly at intersections and all high and low points; and, z. Station and critical elevation (flowline, invert of pipe, etc.) of all existing and proposed utility or drainage structures. Location of utilities shall be identified with horizontal and vertical dimensions as measured from roadway centerline profile grade. y. Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-7 CITY OF SPOKANE VALLEY STREET STANDARDS 4.6.3 MINIMUM PROFILE VIEW ELEMENTS The profile view shall include, at a minimum, the following: a. Stationing, shown the same as in the horizontal plan, reading from left to right. It shall include stationing of points of curve, tangent, length, and point of intersection of vertical curves, with elevations to 0.01 feet; b. Original ground line at 100 -foot stations and at significant ground breaks and topographic features, based on field measurement and accurate within 0.1 feet on unpaved surface and 0.01 feet on paved surface; c. Profiles for curbed streets shall show and label the tops of both curbs and the centerline. Profiles for shouldered streets may show the centerline only. The centerline, top of curb, and existing ground lines of all streets (except cul-de-sacs) shall be continued for 100 feet beyond the proposed construction; d. High and low point and PI of all vertical curves; e. Ditch and swale flowlines and drainage structures; f. A continuous profile for both existing and proposed improvements, shown on a grid of numbered lines; g. Elevation of vertical grade breaks, K values, grade and length of vertical curves; h. Storm drainage flow direction arrows, particularly at intersections and all high and low points; and, i. Station and critical elevation (flowline, invert of pipe, etc.) of all existing and proposed utility or drainage structures. Location of utilities shall be identified with horizontal and vertical dimensions as measured from roadway centerline profile grade. 4.6.4 MINIMUM TYPICAL CROSS SECTION ELEMENTS A typical street section shall include, at a minimum, the following: a. A separate full -width, typical section required for each street or portion of the street that differs significantly. The typical section shall be drawn looking in the direction of increasing stations; b. Station limits; c. The dimensions of traffic lanes, shoulders, gutters, sidewalks, swales, depths, planting strips, easements, rights-of-way, etc.; d. The cross slope of elements such as pavement, ditches, sidewalks, etc.; e. Type of curb; f. Dimensions and type of structural section material layers; and, g. Retaining walls, as applicable. Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-8 CITY OF SPOKANE VALLEY STREET STANDARDS 4.7 ONSITE IMPROVEMENT PLAN 4.7.1 APPLICABILITY Onsite improvement plans are required for projects proposing: a. New commercial developments; b. Residential construction of three or more units per lot; c. Drywells; d. A project site that will have both of the following: i. Any addition or replacement of impervious surface and ii. 5000 or more total square feet of impervious surface. If both of these criteria are met then the runoff from the new and/or replaced PGIS surfaces and areas hydraulically connected to them will need to be treated prior to disposal. The site includes all of the parcels involved in the project whether or not they are contiguous. Impervious surface includes roofs, paved areas, gravel travel ways, etc. Full build -out includes all the project's phases even if - 1. The different phases will be constructed under separate contract and/or by separate owners, and/or, 2. The project is phased over multiple years, but the phases are still under a consistent plan for long term development; and, e. Increases impervious areas to 5,000 square feet or more; i. Alters site access requirements, including adding or removing driveways; or, ii. Connects to and impacts City streets and utilities. 4.7.2 MINIMUM ELEMENTS FOR ONSITE IMPROVEMENT PLAN The onsite improvement plan shall include, at a minimum, the following: a. Property limits and accurate contours of existing ground elevations. For existing topography, one -foot contour intervals are preferred unless the City determines that available five4-foot contour mapping is adequate and detailed enough to describe current landforms; b. Finish contours or spot elevations to be achieved by the grading and related construction. The contour interval for proposed topography must be no more than 1 -foot, unless the slope is greater than 10% percent, in which case, the City may accept 4five-foot contour intervals. Periodically call out the proposed slope. One -foot contours may still be necessary to show certain features such as swales; c. Lot lines, lot numbers and block numbers; d. Existing street names; Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-9 CITY OF SPOKANE VALLEY STREET STANDARDS e. Section, Township, and Range; f. Existing and proposed property and/or right-of-way lines, easements, and/or tracts. Type and dimension of easement or tract shall be clearly labeled. Dimensions of property and right-of-way lines shall be marked. g. Location of all proposed and existing driveways; h. All existing utilities; i. All proposed utilities that will be designed and constructed. The plan shall show the extent of pavement cut(s) for connections; j. Proposed drainage features including, structure type, locating information, direction of flow, size and kind of each drainage channel, ditch or pipe and any other requirements as specified in the Spokane Regional Stormwater Manual, as adopted or amended; k. Fire hydrant locations; 1. No Parking signs and locations; m. Turnaround locations; n. Storm drainage flow direction arrows, particularly at intersections and all high and low points; and, o. Station and critical elevation (flowline, invert of pipe, etc.) of all existing and proposed utility or drainage structures. Location of utilities shall be identified with horizontal and vertical dimensions as measured from roadway centerline profile grade. 4.8 DRAINAGE PLAN A drainage plan, showing the location of drainage facilities intended to provide flow control, treatment, and conveyance shall be submitted with the construction plans and shall conform to Section 3.5.2 of the Spokane Regional Stormwater Manual (SRSM), as adopted or amended. For small projects, the drainage plan may be included in the Onsite Improvement Plan. 4.9 TEMPORARY EROSION AND SEDIMENT CONTROL PLAN A Temporary erosion and sediment control (TESC) plan shall be submitted for all projects pursuant toas specified in Section 5.3.1, and shall conform to Section 5.3, and the SRSM, as amended. For small projects, the temporary erosion and sediment control plan may be included in the clearing and grading plan. 4.10 TEMPORARY TRAFFIC CONTROL PLAN A temporary traffic control plan shall be included with the right-of-way permit. The plan shall be in detail appropriate to the complexity of the project pursuant toMUTCD Chapter 6 B. Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-10 CITY OF SPOKANE VALLEY STREET STANDARDS 4.11 PERMANENT TRAFFIC CONTROL PLAN When required, permanent traffic control plan sheets shall include the components outlined below. Permanent signage and striping shall be complete and in place prior to the acceptance of the certification package. 4.11.1 AREA MAP Separate signage and striping plans shall consist of an overall area map noting all specific use areas, such as schools, parks, recreation centers, library, commercial, industrial, etc. 4.11.2 ROAD SEGMENT PAGES The pages following the area map shall be broken down into street segments, for notation of signage and striping details. 4.11.3 SIGNING PLAN The permanent signing plan shall: a. Show the longitudinal location of each sign (horizontal offset and station); b. Specify the sign legend and sign type (from MUTCD and International Fire Code); c. Specify the sign size and applicable standard plan; d. Refer to Standard Plan R-140 for post and base dimensions and installation plan; e. Specify the blank gauge of the sign; and, f. Note the reflectorization provided. 4.11.4 STRIPING PLAN The striping plan shall show: a. Color and type; b. Lane widths, taper lengths, storage lengths, etc.; c. Striping/skip interval; d. Any construction or application notes, (e.g., application temperatures, surface cleaning methods to be used prior to application, etc.); e. Typical treatments for acceleration/deceleration lanes, turning lanes, and crosswalks; f. Type of material (epoxy, latex, thermoplastic, etc.); and, g. Station and offset or dimensions to all angle points, symbol locations, and line terminations. Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-11 CITY OF SPOKANE VALLEY STREET STANDARDS 4.11.5 TRAFFIC SIGNAL PLAN Traffic signal installation and equipment shall be coordinated with and approved by the Community and Public Works Department. The applicable MUTCD signal warrants shall be met. 4.12 SITE PLAN OF RECORD DevelopmentThe Engineering requires that the following items shall be included: a. The footprint of drainage facilities including swales, ponds, channels, detention/retention basins, inlets, drywells, etc. b. A table providing the following areas in square feet: i. total rooftop areas, ii. total pavement area, iii. total gravel area, and iv. total impervious area. Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-12 CITY OF SPOKANE VALLEY STREET STANDARDS APPENDIX 4 -A -GENERAL CONSTRUCTION NOTES a. All work and materials shall be pursuant toin conformance with the latest edition of the City of Spokane Valley Street Standards, Spokane Regional Stormwater Manual and all other governing agency's standards. b. Prior to site construction, the Contractor shall bei responsible for locating underground utilities. Call the underground utility location service at 8111 800 121 5555 before you dig. c. Locations of existing utilities shown in the plans are approximate. The Contractor shall be responsible for locating all underground utilities. Any conflicting utilities shall be relocated prior to construction of road and drainage facilities. d. The Contractor shallis required to have a complete set of the accepted street and drainage plans on the job site whenever construction is in progress. e. If the Contractor discovers any discrepancies between the plans and existing conditions encountered, the &Contractor shall immediately notify the Applicant's engineer and Onsite Inspector. f. The Contractor shall take appropriate precautions to protect the infiltration capacity of stormwater facilities (e.g., line the facility with filter fabric, over -excavate upon completion of the infrastructure, etc.) g. Where directed by the Ci control devices, the placement and type of which shall be pursuant conform to the . • . - • • TCD). h. It shall be the Contractor's responsibility to coordinate with and contact all appropriate utilities involved prior to construction. i. All pavement cuts to connect utilities shall be repaired pursuant toin conformance with the Regional Pavement Cut Policy. All survey monuments shall be protected during construction by or under the direction of a Licensed Surveyor pursuant toas required by 4state blaw. disturbed or damaged monuments shall be replaced by or under the direction of a licensed Surveyor prior to certification /final plat and/or release of surety. The Contractor is responsible for the filint of permits for monument removal and replacement with the Washington State Department of Natural Resources, a required by WAC 120 070. k. Contractor shall be responsible for scheduling and acquiring electrical inspections required by the State. 1. Contractor shall beis responsible forte verifying that all required permits have been obtained prior to initiating construction. m. The Contractor and all subcontractors shall have a current City business registration of Spokane Valley Business License. n. The Contractor and all subcontractors shall be licensed by the State of Washington and bonded to do work in the public right-of-way. , the Contractor shall place traffic J. Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-13 CITY OF SPOKANE VALLEY STREET STANDARDS o. No work on this project shall commence until a City of Spokane Valley right-of- way permit has been issued. p. The Contractor shall protect adjacent properties, public or private, at all times during construction. q. Contractors shall control dust pursuant to applicable lawin accordance with retulations of local air pollution control authority. r. Contractor shall remove all construction—_related debris to an approved waste disposal site. s. Fire hydrants shall be installed and functioning prior to the construction of any structures. t. Contractor shall maintain fire apparatus access to streets during construction. u. The Contractor shall notify the On-site Inspector one business day before any construction or product placement takes place that requires testing or observation (Refer to Appendix 9A- Minimum Material Testing Frequencies). The On-site Inspector shallwill determine the time required to satisfactorily achieve the necessary testing, observation and documentation. The On-site Inspector shallwill be required to be on site 100% of the time during HMA placement, drywell placement, and trench work. v. Supplemental notes used when applicable: i. For any curb grades less than 1.0% (0.01 ft/ft), a Professional Land Surveyor currently licensed in the State of Washintton shall verify that the curb forms are at the grades noted on the accepted plans, prior to placement of concrete. The Contractor shallis responsible for arrangeing and coordinateig work with the Surveyor. ii. The Contractor shall employ a Professional Land Surveyor currently licensed in the State of Washintton to verify that the cross -gutter forms are at the correct plane grade prior to concrete placement.. iii. Concrete aprons are required at the inlet into any swale or pond. The finish grade of the swale/pond side slope, where the concrete inlet apron ends, shall be a minimum of 2two inches below the finished elevation of the concrete curb apron extension. Thise intention is to allow stormwater runoff to enter the swale/pond unobstructed, without backing up into the street and gutter due to sod overgrowth at the inlet. iv. Unlined pond and bio -infiltration swale bottoms are expected to infiltrate via the pond floor, and therefore, shall not be heavily compacted; equipment traffic shall be minimized on the pond bottoms. The facility sub -grade shall be a medium- to well- draining material, with a minimum thickness of 48 inches and a minimum infiltration rate of 0.15 in/hr. The facility shall drain within 72 hours of a storm event. If the pond also serves as a water quality treatment facility, the treatment zone (sod and 6six inches of treatment soil) shall be a medium- to well -draining material, with a minimum infiltration Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-14 CITY OF SPOKANE VALLEY STREET STANDARDS rate of 0.25-0.50 in/hr. Scarify the finish grade of the pond bottom prior to hydroseeding/sodding. Testing that verifies subgrade minimum infiltration rate may be required by the Citylocal jurisdiction prior to construction certification to ensure adequate drainage. Infiltrative testing of the treatment zone is only required if soils other than silty loam or loamy soils are proposed. v. If, during final inspection, it is found that the constructed pond or swale does not conform to the accepted design, the system shall be reconstructed so that it does comply. Refer to Appendix 9A of the Spokane Regional Stormwater Manual for Erosion and Sediment Control Standard Notes. vi. Pursuant tom Spokane Regional Stormwater Manual methods, a qualified licensed engineer shall evaluate, classify and document the soils in the excavated drywell infiltration zone prior to installation of the filter fabric, drainage rock or drywell barrel and shall determine if the soil's conditions arewill be suitable and capable of infiltrating storm water at the design flow rate. Applicant's Engineer shall submit a copy of the documentation detailing the observations, the conclusions and the basis for the conclusions to the City _of Spokane Valley Development Engineering Department. If the eApplicant's engineer determines that the soils do not meet the design's requirements or that a condition exists preventing the drywell from functioning as designed, the design engineer shall be notified and the design revised to meet existing conditions. Any revisions to the design shall be submitted to the City of Spokane Valley for review and acceptance. vii. Construction of every drywell, including fabric and drainrock, shall be observed by the eOn-site ilnspector to confirm that it meets the design details and specifications. Drywells that have not been observed shall have their performance verified by a full-scale drywell test. Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-15 CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIONALLY LEFT BLANK Ad pted December 2009 Chapter 4 —Requirements for Plan Submittal 4-16 1 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 6 - UTILITIES Chapter Organization 6.1 Introduction 1 6.2 Design Criteria 1 6.2.1 Utilities Located within Right -Of -Way 1 6.2.2 Underground Utilities 1 6.2.3 Aboveground Utilities 2 6.2.4 Regional Pavement Cut Policy 2 Appendix 6A - Regional Pavement Cut Policy 4 Adopted December 2009 Chapter 6 — Utilities 6-i CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIONALLY LEFT BLANK Adopted December 2009 Chapter 6 — Utilities 6 -ii CITY OF SPOKANE VALLEY STREET STANDARDS 6.1 INTRODUCTION The design and construction of public and private utilities located within City rights-of- way shall be in conformance with these standards. 6.2 DESIGN CRITERIA The City has established the following minimum requirements to ensure the efficient construction of utilities with the least impact to City transportation and utility infrastructure. 6.2.1 UTILITIES LOCATED WITHIN RIGHT-OF-WAY Pursuant toln accordance with the SVMC Title 20.20.0901—M1 the short subdivision, subdivision, or binding site plan shall provide underground utilities within all new public rights-of-way, alleys, or utility easements including, but not limited to, those for electricity, communication, and street lighting. 6.2.2 UNDERGROUND UTILITIES New underground utilities shall meet the following requirements: a. Private utility lines shall be located within the rights-of-way only when approved by the City. Utility companies shall have a current franchise 6f public way agreement consistent with the City of Spokane Valley Municipal Code, b. Private utilities shall be located a minimum horizontal distance of five feet from buildings and public utilities; c. When crossing public utilities, private utilities shall be located a minimum vertical distance of 12 inches from the public utility; d. Manhole covers, utility box lids, and all other underground utility and irrigation access covers shall not be located within the sidewalk or driveway approaches; e. Sewer utility installation shall meetsSpokane CountyIs Standards for Road and Sewer Construction, as adopted or amended, and the Department of Health's Orange Book, as adopted or amended; f. Water line installations or modifications shall satisfy American Water Works Association (AWWA) Standard Specifications; End markers shall be installed at the end of all utility stubs or crossings, and locator tape shall be installed at a maximum of gsix inches above all conduits, pipe and cables; and, h. The Applicant shall timely notify the applicable utility companies of upcoming street construction; so they have the opportunity to upgrade their utilities in conjunction with the development project, if desired. g. Adopted December 2009 Chapter 6 — Utilities 6-1 CITY OF SPOKANE VALLEY STREET STANDARDS 6.2.3 ABOVEGROUND UTILITIES On projects where underground requirements do not apply, the following requirementsparameters shall be metaddressed in locating aboveground utilities: a. Utilities shall be located pursuant toper Standard Plan U-100; b. Utility poles and other aboveground utility structures located on curbed streets with separated sidewalks shall be installed a minimum of two2 feet behind the back of curb. When the sidewalk is adjacent to the curb, they shall be located a minimum of two2 feet behind the sidewalk. For shouldered streets, utility poles and other aboveground utility structures shall be located outside the clear zone pursuant toin accordance with _the AASHTO manual "A Policy on Geometric Design of Highways and Streets "as adopted or amended, and Chapter 7 of the Street Standards; c. Utility poles and other aboveground utility structures shall not be located within the sidewalk. Sidewalks shall have a continuous unobstructed path of at least -five feet wide; d. Utility poles and other aboveground utility structures shall not interfere with driveways, intersections, clear zone, and all other road features. They shall not obstruct with sight distance, road signing, traffic signals, culverts, etc. This may require that existing poles be relocated at the Applicant's expense; e. No utility pole or other aboveground utility structures shall be located in such a way as to pose a hazard to the general public. Utility companies shall locate and replace poles and other structures with primary consideration given to public safety and roadway functionality; and, f. When an Applicant -driven project requires the relocation of private utilities due to public utility extensions or other City required improvements, the cost of relocation of the private utility shall be borne by the Applicant. 6.2.4 REGIONAL PAVEMENT CUT POLICY Modification or removal of pavement within the City's rights -=of -=way is governed by the most current Inland Northwest Regional Pavement Cut Policy, or as adopted or amendedit may be amended in the future. Copies may be obtained from the City Permit Center or City website. -General requirements are as follows: a. Pursuant to SVMC 22.130.060, aA right-of-way permit is required foref any person or entitycompany cutting pavement within existing City rights- of-way or on City -owned infrastructure (SVMC Title 22.130.060); b. Permit fees are established in the Spokane Valley Master Fee Schedule as adopted or amended; c. A pavement cut moratorium is in effect for three years from the date of pavement or reconstruction of pavement for public streets. For streets beyond the moratorium period, cuts are allowed if the requirements of this policy are meth, and, Adopted December 2009 Chapter 6 — Utilities 6-2 CITY OF SPOKANE VALLEY STREET STANDARDS d. For pavement cuts and other infrastructure affected by the work, tThe Applicant shall provide a warranty in accordance with this policy for pavement cuts and other infrastructure affected by the work. Adopted December 2009 Chapter 6 — Utilities 6-3 CITY OF SPOKANE VALLEY STREET STANDARDS Appendix 6A Inland Northwest Regional Pavement Cut Policy Adopted December 2009 Chapter 6 — Utilities 6-4 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 7 - STREET ELEMENTS Chapter Organization 7.1 Introduction 1 7.2 Terrain Types 1 7.3 Street Types 1 7.3.1 Public Streets 1 7.3.2 Private Streets 2 7.3.3 Alleys 2 7.3.4 Private Driveways 3 7.4 Half -Street Improvements 3 7.5 Street Geometry 4 7.5.1 Design Criteria 4 7.5.2 Right -of -Way 8 7.5.3 Border Easement 8 7.5.4 Grade 8 7.5.5 Cross Slope 8 7.5.6 Horizontal Curves 9 7.5.7 Vertical Curves 9 7.5.8 Street Surfacing Requirements 10 7.5.9 Curb and Gutter 10 7.5.10 Landscape Strip and Swales 10 7.5.11 Turnarounds 10 Ad pted December 2009 Chapter 7 — Street Elements 7-i CITY OF SPOKANE VALLEY STREET STANDARDS 7.5.12 Bikeways 11 7.5.13 Intersections 12 7.5.14 Street Layout 13 7.5.15 Survey Monuments 14 7.5.16 Traffic Control Devices 16 7.6 Roadside Elements 16 7.6.1 Sidewalks 16 7.6.2 Pedestrian Ramps 17 7.6.3 Side Slopes 17 7.6.4 Clear Zone 17 7.6.5 Sight Distance 18 7.7 Miscellaneous Features 22 7.7.1 Street Names 22 7.7.2 Mailboxes 22 7.7.3 Guardrail 22 7.7.4 Bollards 22 7.7.5 Roadway Barricades 23 7.7.6 Entrance Gates 23 7.8 Approach Design Criteria 23 7.8.1 Applicability 23 7.8.2 Access Limitations 24 7.8.3 General Design 25 7.8.4 Driveway Approach Horizontal and Vertical Grade 25 7.8.5 Approach Widths 26 7.8.6 Driveway Approach On -Site Layout 26 7.8.7 Corner Clearance from Intersections 27 7.8.8 Driveway Approach Spacing - Same Side of Street 28 7.8.9 Driveway Approach Methods of Measurements 28 7.8.10 Restricted Access Driveways 28 7.8.11 Alignment of Cross -Street Driveway Approaches 29 7.8.12 Signalized Driveway Approaches 29 7.8.13 Approaches on State Highways 29 7.9 Traffic Calming 30 7.9.1 New Development 30 7.9.2 Existing Development 30 7.9.3 Traffic Calming Devices 30 List of Figures Figure 7-1 Sight Distance Triangle for Case A 21 Figure 7-2 Sight Distance Triangle for Case B 21 List of Tables Table 7.1 Arterial Street Design Criteria 5 Table 7.2 Arterial Street Design Criteria Minimum Widths 6 Table 7.3 Access Street Design Criteria 7 Table 7.4 Minimum Street Approach Length 12 Table 7.5 Minimum Intersection Spacing for Local Access Streets 13 Ad pted December 2009 Chapter 7 — Street Elements 7 - ii CITY OF SPOKANE VALLEY STREET STANDARDS Table 7.6 Minimum Stopping Sight Distance 19 Table 7.7 Minimum Intersection and Approach Sight Distances 20 Table 7.8 Driveway Approach Spacing 28 Table 7.9 State Routes Classifications 30 Ad pted December 2009 Chapter 7 — Street Elements 7 - iii CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIALLY LEFT BLANK Ad pted December 2009 Chapter 7 — Street Elements 7 - iv CITY OF SPOKANE VALLEY STREET STANDARDS 7.1 INTRODUCTION The design of streets within the City of Spokane Valley shall generally conform to American Association of State Highway and Transportation Officials (AASHTO)and the State of Washington Department of Transportation (WSDOT) standards unless modified herein. Some street designs require technical criteria that are above the scope of these Standardsthis manual and therefore are not covered. In these cases, design manuals from the above referenced agencies and references listed in Section 1.944 should shall be used for a basis of design. The standard plans referenced in this chapter are locatedcan be found in Chapter 11. 7.2 TERRAIN TYPES Terrain type can be classified as flat, rolling or mountainous. Flat terrain is the condition where roadway sight distances, as governed by both horizontal and vertical restrictions, are generally long or could be made to be so without construction difficulty or major expense. The slope of the existing terrain is from 0% percent to and including 5% percent. Rolling terrain is that condition where the natural slope rises above and falls below street grade line consistently. Normal street alignment is restricted some by occasional steep slopes. The slope of the existing terrain is from 5% percent to and including 15% percent. Mountainous terrain is that condition where longitudinal and transverse changes in the elevation of the ground with respect to a street are abrupt and where the roadbed is obtained by frequent benching or side hill excavation. The slope of the existing terrain exceeds 15% percent. 7.3 STREET TYPES Streets within the City include public and private streets. Since community needs are usually best served by streets owned and maintained by the City, most projects are required to be accessed via public streets. Private streets may be appropriate for some local accesses in very limited usage. For the purposes of these Street Standards, the following sections provide additional descriptions of streets. 7.3.1 PUBLIC STREETS Public streets are owned and maintained by the City. All public streets in the City arehave been classified using the Federal Functional Classification system, which provides a hierarchy, from principal arterials to local access streets, to accommodate existing and anticipated traffic. Street classifications can be found in the City of Spokane Valley Comprehensive Plan. Adopted December 2009 Chapter 7 — Street Elements 7-1 CITY OF SPOKANE VALLEY STREET STANDARDS New pPublic streets may be requiredcan be triggered by land actions or development permits pursuant toas described in Chapter 2. Public streets, not private streets, shall be used to connect two public streets and shall be designed per Tables 7.1 through 7.3 and the Standard Plans R 120 through R 122. Sections 7.3 through 7.7, including Tables 7.1 through 7.3,Chapter 7 provides additional design criteria and requirements for public streets. 7.3.2 PRIVATE STREETS Private streets are local access streets, privately owned and maintained. All new private streets shall be approved by the City. Private streets shall bene permitted when all of the following apply: a. Where connectivity to the public street system is not compromised;-, b. Where future through connection to public streets is not possible;, c. The private street does not land -lock present or planned parcels; d. The private street serves from two to nine single family dwelling lots; e. The private street provides direct access to a public street. Access to and from private streets shall be limited to properties immediately adjacent to the private street„ and f. The private street is not used to connect two public streets. Private streets shall be designed pursuant toper Table 7.3. The design of a private street shall discourage any through traffic of non-residents. Traffic calming measures may be utilized in the design of private streets. Private streets shall connect to City streets using a standard driveway approach per Standard Plan R 1 l5but not a high volume approach. A capable, legally responsible owner or homeowners association shall be established and identified to maintain private streets and associated drainage facilities in perpetuity. A plat or short plat with private streets shall be required to provide an executed, recorded Private Street Maintenance Agreement and a Stormwater Easement and Maintenance Agreement that obligate future property owners to maintain the infrastructure in perpetuity (see Chapter 10 for requirements). 7.3.3 ALLEYS Alleys are not typically required. However, certain projects may have the option or may be required to provide alley access by the City's Comprehensive Plan or by an adopted subarea plan. Design of alleys typically follows the criteria for local streets {Standard Plan R 125). The following is a list of design standards that differ from local street elements: Ad pted December 2009 Chapter 7 — Street Elements 7-2 CITY OF SPOKANE VALLEY STREET STANDARDS a. Alleys shall have a minimum width of 20 feet of asphalt pavement. If the alley is the only access point to the site, the alley width shall meet the width requirements for local access streets (See Table 7.3); b. Curb, gutters and sidewalks are not required, unless conditioned otherwise; and, c. The pavement area may have an inverted crown at centerline to convey stormwater into catch basins located at low points in the invert. Alleys shall connect to a private or public street at each end. In cases where this is not feasible, adequate turnarounds shall be provided. Alleys maycan be located in the public rights-of-way or a private easement. 7.3.4 PRIVATE DRIVEWAYS Private driveways provide vehicular access to one lot. Private driveways shall comply with the following: a. Private driveways longer than 75 feet but less than 150 feet in length shall meet the requirements for width and, grade and signing as private streets (See Table 7.3); b. Private driveways longer than 150 feet shall be engineered and meet the requirements for width, grade, and signing as private streets (See Table 7.3); c. Private driveways longer than 750 feet shall only be allowed when approved by the Fire Department. Structures accessed by a private driveway and which are not visible from the public street shall post an address at the street. Addresses shall be permanent inhy nature and the numbers shall be a minimum of 4four inches tall, 1/2 inch stroke, and contrasting color to the background. Driveways shall not extend off the end of an arm of the hammerhead turn -around. 7.4 HALF -STREET IMPROVEMENTS A half -street is required as an interim facility. Half -street improvements are required for a property fronting a public street that is not currently built to City standards. Half -street construction may also be required for property that abuts future streets proposed in the City's Arterial or Local Street Plan. When half -street improvements are required, the design of the half -street shall be consistent with the existing street classification or as dictated by the City's 6Six-year Transportation Improvement Plan (TIP) or City Street Plans. This requires construction of more than half the street for safety and drainage reasons. Construction in these circumstances requires a minimum of one travel lane on the opposite side of the roadway and frontage improvements on the project side of the street. Dedication of additional right-of-way and border easements are required, unless the existing right-of-way and easement widths are sufficient to fit the improvements. Ad pted December 2009 Chapter 7 — Street Elements 7-3 CITY OF SPOKANE VALLEY STREET STANDARDS When half -street improvements are required, a minimum of 28 feet of pavement is required. Street improvements shall be designed to provide drainage for the constructed portion of the street. Provisions shall be made to allow for extension of the storm drainage system to the undeveloped portion of the street for future construction. Transition tapers are required when the new edges of pavement do not match the existing edge of pavement. Tapers shallare required to conform to Chapter 6 of the MUTCD, latest edition. All proposed utilities located within the half -street shall be installed during construction. The unfinished side of the half -street shall be finished with a gravel shoulder, grassed ditch and/or side slope to ensure^ proper drainage, bank stability, and pedestrian and traffic safety (see Standard Plans R 113). When half -streets connect to an intersection, the intersection shall be designed and constructed for the full build -out of the street. The intersection design and construction shall extend for at least 75 feet from the street intersection -(S4). 7.5 STREET GEOMETRY Factors contributing to the geometric conditions of a street are discussed in the following sections. All public streets in a subdivision, including half -streets, shall be fully constructed to the plat boundaries. Pavement, gutter, curb and sidewalk shall be extended to allow future connections to occur. 7.5.1 DESIGN CRITERIA Minimum and maximum geometric design elements are set forthprovided in Tables 7.1 through 7.3. Any revision to a geometric element or traffic control on a State Highway requires WSDOT approval. For in-depth design information on the following criteria, refer to AASHTO Green Book, latest adopted edition. Ad pted December 2009 Chapter 7 — Street Elements 7-4 CITY OF SPOKANE VALLEY STREET STANDARDS TABLE 7.1 ARTERIAL STREET DESIGN CRITERIA MINIMUM DESIGN ELEMENTS TERRAIN TYPE URBAN ARTERIAL SYSTEM URBAN COLLECTOR SYSTEM Classification Principal Minor Collector Design Flat 40 40 35 Speed (mph) Rolling 40 35 35 Mountainous 35 30 35 Minimum Section Type Crown Crown Crown Horizontal 2% 3% 2% 3% 2% 3% Curve Radius'' Flat 765 820 765 820 510 545 2 (ft) Rolling 765 820 510 545 510 545 Mountainous 510 545 330 350 510 545 Minimum All 150 150 100 Tangent Length2 (ft) Maximum All 4 4 Not allowed Superelevation (%)3 Maximum All 6 8 8 Grade (%) 4 Acceptable All 2-3 2-3 2-3 Range Cross -slope (%) Minimum Flat 45 45 30 Crest Vertical Rolling 45 30 30 Curves' (K) Mountainous 30 20 30 Minimum Flat 65 65 50 Sag Vertical Rolling 65 50 50 Curves' (K) Mountainous 50 40 50 1. Minimum horizontal curves reflect a crown section. For superelevated sections, the horizontal curve radius shall be re -calculated using AASHTO — Geometric Design of Highway and Speeds. Radius measured to centerline. 2. Minimum tangent required at intersections and between curves. 3. Horizontal curves may be adjusted if a super -elevated section is proposed - use AASHTO — Geometric Design of Highway and Speed:,Streets. 4. Maximum grades may be exceeded for short distances subject to approval by the City "(+ 2%)". 5. Length in feet per percent of algebraic grade difference (K value). L = K x Algebraic difference in grade. K Shall not exceed 167. Ad pted December 2009 7-5 Chapter 7 — Street Elements CITY OF SPOKANE VALLEY STREET STANDARDS TABLE 7.2 ARTERIAL STREET DESIGN CRITERIA MINIMUM WIDTHS TYPE URBAN ARTERIAL SYSTEM URBAN COLLECTOR SYSTEM Classification Principal Minor Collector Curb & Gutter Required Yes Yes Yes Edge Type Curb Shoulder' Curb Curb Painted Center/Left-turn lanes 12 12 12 12 Inside lanes (feet) 12 12 12 12 Intermediate lanes (feet) 12 12 12 12 Outside lanes' (feet) 12 12 12 12 Minimum Sidewalk (feet) 6 6 6 (5 to 6)4 Minimum Intersection return radii (ft)5 50 50 40 30 Minimum Asphalt Width (feet) 6 2 lanes 44' 40' 3 lanes 44 or 46 -- 44 or 46 -- 4 lanes 56 64 56 -- 5 lanes 68 or 70 78 68 or 70 -- 6 lanes 80 102 -- -- 7 lanes 92 or 94 -- -- -- 1. Shoulder section only when approved by the City. 2. Where raised median islands are required, the center lane or left -turn lane shall be fourteen feet in width. 3 Traveled lanes of a two-lane road are shown as outside lanes. If the street is a shared roadway as designated in the Comprehensive Plan, the outside lane shall beis 14 feet minimum For streets with a bike lane as designated in the Comprehensive Plan, increase the lane width by 5 feet 8 inches to allow for a 5 -feet bike lane and 8 -inch stripe. 4. Minimum sidewalk width is six6 feet if it is adjacent to the curb and/or if located in a commercial zone. 5. Return radii at face of curb. 6. When asphalt width varies, the larger width is for a raised median. 7. Parking lanes included. Ad pted December 2009 Chapter 7 — Street Elements 7-6 CITY OF SPOKANE VALLEY STREET STANDARDS TABLE 7.3 ACCESS STREET DESIGN CRITERIA DESIGN ELEMENTS TERRAIN TYPE INDUSTRIAL/ COMMERCIAL LOCAL ACCESS PRIVATE STREET ALLEY ADT All 200+ < 200 All All Curb & Gutter Required All Yes Yes Yes No No Design Speed (mph) Flat Rolling Mountainous 35 30 25 30 30 25 25 25 20 20 20 20 20 20 20 Minimum Horizontal Curve Radius (ft)' Flat Rolling Mountainous 545 350 210 350 350 210 210 210 110 110 110 110 110 110 110 Minimum Tangent Length (ft) at intersections All 100 25 25 25 25 Maximum Superelevation Rate (%) All Not allowed Not allowed Not allowed 2 2 Maximum Grade (%)2 All 8 8 8 10 8 Acceptable Range Cross slope (%) All 2 to 3 2 to 3 2 to 3 2 to 3 2 to 3 Minimum Crest Vertical Curves (K)3 Flat Rolling Mountainous 40 30 20 20 20 15 15 15 10 10 10 10 10 10 10 Minimum Sag Vertical Curves (K) 3 Flat Rolling Mountainous 50 40 30 40 40 30 30 30 20 20 20 20 20 20 20 Minimum Sidewalk Width (ft)4 All 6 5 5 Not required Not required Min. Asphalt Width (ft)5 All 40 30 286 (20-26)7'8'9 (20-30)10 Minimum Intersection return radii at face of curb (ft) All 30 30 30 30 30 1. Minimum horizontal curves reflect a crown section with a cross -slope of 3 percent. Other section types should be calculated using AASHTO — Geometric Design of Highway and Speeds. Radius measured to centerline. 2. Maximum grades may be exceeded for short distances subject to approval by the City (+2%). 3 Length in feet per percent of algebraic grade difference (K value). L = K x Algebraic difference in grade. K shall not exceed 167. 4. Minimum sidewalk width is 6six feet if it is adjacent to the curb and/or if located in a commercial zone. 5. Asphalt width does not include curb and/or gutter section. 6. "No Parking" signs shall be posted on one side of the street. 7. A minimum 10 -foot maintenance and utility easement shall be provided on each at least one side of the private street. 8. Asphalt width based on the length of the street: up to 500 feet = 20 feet; up to 600over 500 feet = 26 feet. The minimum width is 26 feet around a fire hydrant when if there i;, a fire hydrant is located on the private street, regardless of the street length, per Appendix ED of the IFC. Ad pted December 2009 7-7 Chapter 7 — Street Elements CITY OF SPOKANE VALLEY STREET STANDARDS 9. Streets 20 to 26 feet wide shall be posted on both sides as a fire lane and with No Parking signs. Pavement widths greater than 26 shall be posted on side of the street as a fire lane and with No Parking signs. If curb is provided, the curb to curb width can be used to determine if a "No Parking" sign is required. 10. If the alley is the only access point to the site, the alley width is 30 feet unless the ADT is less than 200, then the width is 28 ft. 7.5.2 RIGHT-OF-WAY The public street right-of-way shall extend at a minimum to two- feet behind the curb for projects with separated sidewalk. When the sidewalk is adjacent to the curb, the right-of-way shall extend 2two feet behind the sidewalk. Right-of-way requirements may vary within a street corridor. The required right-of-way width depends on the required street elements, including number of lanes, on -street parking, bike lanes, medians, turn lanes, roadside swales, pedestrian buffer strips and above and below ground utilities. Right-of-way shall be conveyed to the City on a recorded plat or by a right-of-way dedication. 7.5.3 BORDER EASEMENT Border easements shall be granted to the City on a recorded plat or by a recorded easement. Border easements shall extend from the right-of-way line to the back of sidewalk or the back of public facilities when located behind the sidewalk, whichever is greater±'= _ate t. The border easement shall run the total length of the street on both sides. Fences shall not be constructed inside the border easement. The border easement area shall be kept clear of other objects that may would obstruct a driver's view. The sidewalk shall be open for use of pedestrian traffic at all times. The border easements may be used by the utility companies. Utility and other easements can cross the border easement but cannot be entirely located within the border easement. 7.5.4 GRADE Minimum longitudinal grade shall be 0.5% percent for streets with concrete gutters and shouldered roads. The minimum longitudinal grade shall be 0.8% percent for streets with asphalt gutters. Maximum allowable grade shall be pursuant toper Tables 7.1 and 7.3. 7.5.5 CROSS SLOPE All new streets shall be constructed with a center crown, with the cross slope per Tables 7.1 and 7.3. When widening an existing street, the cross slope may range between 2 and 4.5% percent. The cross slope of the higher priority street shall be extended through the intersection. The grade of the cross street shall be adjusted to meet the cross slope of the higher priority street. When two streets with the same classification meet, the street with the higher average daily trip (ADT4 shall be selected to act as the higher priority street. The slope of the other street shall be adjusted as required above. Ad pted December 2009 Chapter 7 — Street Elements 7-8 CITY OF SPOKANE VALLEY STREET STANDARDS 7.5.6 HORIZONTAL CURVES Curve radii shall be as large as possible; the minimum radii shall be used only where necessary. The minimum allowable centerline radii for horizontal curves shall be pursuant toper Tables 7.1 and 7.3. Angle points are not allowed. All changes in direction shall be made using horizontal curves. Reverse and compound curves should only be used when a single radius curve will not work. For driver safety, compound curves shall have a ratio no greater than 1.5 where the value of the larger radius is divided by the smaller radius. Whenever two streets intersect, a tangent length (measured from the nearest gutter flowline of the intersected street to the point of curvature in the intersecting street) shall be provided for a safe sight distance and traffic operation. The angle of departure from perpendicular shall not exceed 15 degrees for the length of the tangent. The minimum required tangent length shall be pursuant toper Tables 7.1 and 7.3. For driver safety, horizontal curves shall not begin near the top of a crest vertical curve or the bottom of a sag vertical curve. Connection with existing streets shall be made to match the existing alignment grade of the existing improvements. The centerline, flowline, and existing ground lines of all streets (except cul-de-sacs) shall be continued for 100 feet beyond the proposed construction. 7.5.7 VERTICAL CURVES The minimum vertical curve length for public and private local access streets is 50 feet and 100 feet for arterials. A vertical curve is required when the grade break is 1% percent or greater. The following guidelines shall be followed when designing a profile: a. The grade line shall be smooth flowing; b. The roller coaster type profile should be avoided; c. A broken -back grade line (successive vertical curves in the same direction) generally shall be avoided; d. The grade through intersections on streets shall not exceed 6% percent; e. A sag vertical or flat grade is desirable in advance of such features as channelization and ramp takeoffs in order to provide good visibility; f. The approach at street intersections shall be pursuant toper Table 7.4; g. When superelevation is allowed, transitions shall be designed pursuant toef the latest version of the WSDOT Design Manual or AASHTO Policy on Geometric Design of Highways and Streets. The pivot point should be located at the centerline. The gutter profile along the grade break shall be evaluated for stormwater conveyance. Vertical curves and grades created by and along the transition shall conform to these standards; and, Ad pted December 2009 Chapter 7 — Street Elements 7-9 CITY OF SPOKANE VALLEY STREET STANDARDS h. Vertical curves should be avoided at the intersection with streets or approaches. 7.5.8 STREET SURFACING REQUIREMENTS All travelways shall be paved, including public and private streets, alleys, and private driveways. Paving requirements are specified in Chapter 8. 7.5.9 CURB AND GUTTER Type B curb and gutter shall be used for all public streets per Standard Plan R 102. When the existing curb is not continuous along the street frontage, the Applicant shall construct curb and/or gutter to provide continuity. 7.5.10 LANDSCAPE STRIP AND SWALES A grass strip shall be provided between the curb and the sidewalk for all public streets, providing a buffer for pedestrians. The width of the grass strip shall be as follows: a. Seven feet wide if the grass strip is not used for drainage. In this case, drainage facilities shall be located in a separate tract. Commercial and industrial projects may place drainage facilities within a drainage easement granted to the City; or, b. Ten feet wide if a continuous roadside swale is provided within the strip. Planting shall conform to Section 7.8.9 of the Spokane Regional Stormwater Manual and SVMC Title 22 of the SVMC. Drainage facilities receiving stormwater from public streets shall be located within the rights-of-way, within a border easement parallel to the street, or within a drainage tract. Drainage facilities receiving stormwater from private streets or engineered driveways shall be located within a drainage easement parallel to the street or a drainage tract. 7.5.11 TURNAROUNDS Streets shall be planned, designed and constructed to connect to future developments. Dead end public and private streets shall not be more than 600 feet in length. All dead-end streets shall have a turnaround that meets the City and Fire Department requirements. A turnaround is required when: a. The length is 150 feet or more for all types of travelways. The length is measured from the street intersection (SI) to the terminus of the travelway; or, b. A public street is longer than the depth of one lot. Proposed dExisting stubdead end streets, p ' lly those greater than 600 feet in length shall be linked connected to other existing streets that terminate at the project boundary where possible, unless it can be demonstrated that such connections would lead to a substantial rerouting of through -=traffic onto the street. Ad pted December 2009 Chapter 7 — Street Elements 7-10 CITY OF SPOKANE VALLEY STREET STANDARDS Non -motorized paths to adjacent arterials or public facilities, such as schools and parks, shall be provided at the dead-end of the street to shorten walking distances. This shall requires. right-of-way dedication and/or easements. 7.5.11.1 Temporary Turnarounds Temporary turnarounds shall be approved by the City and are allowed only when there is the possibility for extending the street to connect adjacent parcels or other streets. Standard Plans R 131 and R 132 provide acceptable temporary turnarounds for public streets. For public streets, the temporary turnaround shall be placed within an easement. Curb, gutter, and sidewalk shall be provided to the locations specified in standard plans. The plan shall include language indicating that the easement is to be vacated when the street is extended across the adjacent parcel. For private streets, the turnaround shall be part of the access easement and not part of the driveway approach. It is the responsibility of the Applicant to verify that setback requirements are satisfied for the lots with the turnaround. A sign shall be posted at the back of the temporary turnaround stating that the street is planned to be extended in the future (Standard Plan R- 142). 7.5.11.2 Permanent Turnarounds Permanent cul-de-sacs shall be provided for approved dead-end public streets (see Standard Plan R-130). For private streets and driveways, cul-de-sacs are the preferred turnaround; hammerheads or other turnaround types (Standard Plan R-133) shallffe only be allowed for private streets when approved by the City and the Fire Department. A permanent dead-end street is only allowed when connection to adjacent properties and/or other streets is not needed or possible. Permanent cul-de-sacs shall be constructed with curb, gutter, sidewalk and swales. The grade of the cul-de-sac bulb shall be a minimum 1% percent at all places along the gutter lines. As topography permits, drainage shall be directed away from the bulb. 7.5.12 BIKEWAYS The minimum design standards for bikeways shall be per AAHSTO Guide for the Development of Bicycle Facilities, latest edition. Typically, bikeways are shared with other transportation modes, although they may be provided exclusively for bicycle use. Types of bicycle facilities and planned bicycle facilities within the City can be found in Chapter 3 of the City of Spokane Valley Comprehensive Plan. Ad pted December 2009 Chapter 7 — Street Elements 7-11 CITY OF SPOKANE VALLEY STREET STANDARDS 7.5.13 INTERSECTIONS 7.5.13.1 General Design Street intersections shall be laid out so the streets intersect as nearly as possible at right angles. If a right angle is not possible, the skew shall not vary more than 15 degrees from a right angle. Opposite street legs shall lie on a straight line, whenever possible. For safe design, the following shall be avoided: a. Intersections with more than four intersecting streets; b. "Y" type intersections where streets meet at acute angles; and, c. Intersections adjacent to bridges, horizontal curves, and vertical curves and other sight obstructions. When a private street intersects a public street, the private street shalli-s required to be stop -controlled. A private street is prohibitednot allowed as the fourth leg of the intersection at existing tee intersections. The minimum return radii shall be pursuant toef Tables 7.2 and 7.3. 7.5.13.2 Approach Length The street approach area is where vehicles store while waiting to enter an intersection, and shall be designed with a nearly flat grade. For public or private streets, the street approach area at an intersection shall have a downgrade approaching the intersection of no greater than 2% percent. An upgrade approaching the intersection shall be no steeper than 4% percent. The minimum length of the street approach area, measured from the intersected street's edge of curb face, or traveled way where curbs are not present, pursuant tois to be in accordance with Table 7.4. TABLE 7.4 MINIMUM STREET APPROACH LENGTH Average Daily Traffic (ADT) of Higher Priority Road Minimum Road Approach Length (feet) (2% Maximum Downgrade and 4% Maximum Upgrade) Local Access Streets & Private Roads Collector Arterials ADT< 1000 25 50 1000 < ADT < 5,000 50 75 5,000 < ADT < 7,000 75 100 7,000 < ADT < 9,000 75 analysis required Ad pted December 2009 7-12 Chapter 7 — Street Elements CITY OF SPOKANE VALLEY STREET STANDARDS 7.5.13.3 Intersection spacing Arterial spacing shall be per the adopted Arterial Plan. Local access streets and private streets shall be located at the minimum spacing specified in Table 7.5. TABLE 7.5 - MINIMUM INTERSECTION SPACING FOR LOCAL ACCESS STREETS MINOR STREET MAJOR STREET PRINCIPAL ARTERIAL SEPARATION MINOR ARTERIAL SEPARATION COLLECTOR SEPARATION LOCAL ACCESS SEPARATION LOCAL ACCESS & PRIVATE STREETS 660 feet 330 f t 330 f t 150 feet 1. Minimum intersection spacing is measured from centerline to centerline. 7.5.14 STREET LAYOUT The internal local residential street network for a subdivision should be designed to discourage regional through _traffic. Subdivisions shall be planned in a manner that minimizes the number of local street accesses to arterials and collectors. Street configuration shall conform to the following: a. Blocks lengths shall not exceed 600 feet except as provided in the zoning regulations for estate lots, unless unique characteristics associated with the land such as creeks, woods, or parks justify a longer length; b. Public streets, private streets, and driveways shall not be located closer than two2 feet from any point from an interior property line. The only exceptions to this rule are for public streets which shall extend to the plat boundaries to allow for future connection and for half -streets; c. Horizontal alignment within intersection area. The horizontal approach to an intersection shall be tangent for a minimum length pursuant toas specified in Tables 7.1 and 7.3. Longer tangents are highly desirable. The tangent distance is measured from the curb line of one street to the first point of curvature on the intersecting street; d. Residential developments with greater than 30 single family dwelling units shall have a minimum of two2 street accesses that Ad pted December 2009 Chapter 7 — Street Elements 7-13 CITY OF SPOKANE VALLEY STREET STANDARDS meet the Fire Department separation requirement to ensure adequate emergency access; and, e. Multi -family developments with greater than 100 dwelling units shall have a minimum of two street accesses. 7.5.15 SURVEY MONUMENTS 7.5.15.1 General Requirements Surveys shall conform to all applicable state and SVMC requirementslocal regulations (SVMC Title 20). Prior to any construction or maintenance activities within City rights- of-way, a professional land sSurveyor licensed in the State of Washington (Surveyor) shall conduct a thorough search for all survey monuments. Any found monuments shall be referenced pursuant to state law and SVMCin accordance with current applicable state and local regulations. A copy of the references shall be filed in the office of the County Engineer. The Surveyor shall comply with WAC chapter 332-120. If monuments are found to be at risk by construction or maintenance activities, an approved copy of the Application Permit filed with the Washington State Department of Natural Resources (DNR) shall be provided to the City. 7.5.15.2 Monumentation a. The responsible Surveyor shall set permanent monuments pursuant toas shown per the Standard Plans R 115 with his/her registration number as follows: For placing new or replacement of section corners, quarter corners, closing corners, witness corners, and meander corners that have been disturbed or destroyed, the minimum acceptable monument is a 3/4 -inch inside diameter iron pipe or a #5 (5/8 -inch) steel reinforcing rod, 24 inches in length. The monument and cap shall be marked in conformance with state laws and regulations. Any of these corners in paved roads shall be covered by a cast iron monument case and lid per Standard Plan R 1'15. ii. For placing new or replacement of disturbed road intersection points on arterials, the minimum acceptable monument is a 1/2 -inch inside diameter iron pipe or a #5 (5/8 inch) steel reinforcing rod, 24 inches in length. These monuments shall be covered by a standard cast iron monument case and lid per Standard Plan R 115. iii. For placing new or replacement of disturbed road centerline angle points, curve points and road intersection points (not identified above), the minimum acceptable monument is a 1/2 -inch inside diameter iron pipe or a #5 (5/8 -inch) steel Ad pted December 2009 Chapter 7 — Street Elements 7-14 CITY OF SPOKANE VALLEY STREET STANDARDS reinforcing rod, 24 inches in length. Monuments set in the residential street shall be as shown on Standard Plan R 1'15. iv. For placing new or replacement of all permanent monuments not covered above, the minimum acceptable monument is a 1/2 -inch inside diameter iron pipe or a #4 (1/2 -inch) steel reinforcing rod, 18 inches in length. v. If it is impossible to set the above monuments, the City may approve an alternative monumentation method. b. For each monument being set or established, the responsible Surveyor shall: i. Identify at least three reference points. The reference points may consist of, in order of preference, cross on curbs, bearing trees or accessories, nearby property corners or an alternate as approved by the City. A completed DNR permit shall be filed with the DNR with a copy supplied to the City. ii. Show on a Record of Survey, Subdivision, Short subdivision or Binding Site Plan sufficient information to comply with RCW 58.09.120. A filed copy of said Record of Survey, Subdivision, Short Subdivision or Binding Site Plan shall be supplied to the City as needed. 7.5.15.3 Horizontal Control Network 7.5.15.4 A horizontal control network previously established by the Spokane County Engineer shall be the mapping base for all surveys performed under these Street Standards. Intersections shall also be located and referenced to the current control network as established by the Spokane County GPS control project and that coordinate system. Refer to the SVMC Title 20.40 for additional information. All survey work done within the City boundaries shall conform to the degree of accuracy required under applicable state laws and professional standards. Adequate supplemental information may be required by the City to ensure accuracy. Temporary Bench Mark The Surveyor shall provide a temporary bench mark along the roadway every 1,000 feet. These temporary bench marks shall be based on the datum plane approved by the City. Refer to the SVMC Title 20.20 for additional information. If requested by the City, the Surveyor shall submit field notes or a sealed statement, einsuring work according to third order accuracy. Refer to Washington State Department of Transportation Standards (Highway Surveying Manual M22-97) for additional information. Ad pted December 2009 Chapter 7 — Street Elements 7-15 CITY OF SPOKANE VALLEY STREET STANDARDS 7.5.16 TRAFFIC CONTROL DEVICES The City has adopteduses the Washington State MUTCD as a guideline for traffic control devices including pavement marking and signing. The Applicant shall bei -s responsible for providing and installing all required traffic control devices, including but not limited to street name signs, regulatory signs (including stop and no parking), warning signs, barricades, crosswalk markings, and bicycle/pedestrian signs. "No Parking" signs shall be posted on both sides of the street for curb--to--curb widths up to 26 feet, and on one side of the street for curb to curb widths greater than 26 feet and up to 32 feet. If the street has no curb, the pavement width shall be used to determine if "No Parking" signs are required. For private streets and private driveways, a minimum of one "No Parking — Fire Lane" sign shall be installed every 100 feet of frontage or as required by the Fire Department. "No Parking" signs on public streets shall be installed when required by these Street Standards at a separation as required by the City and the Fire Department. 7.6 ROADSIDE ELEMENTS 7.6.1 SIDEWALKS Sidewalks arei-s required on public streets along both sides for all street classifications. When approved by the City, the sidewalk may be eliminated on one side of the street if topography or safety prohibits construction. The Applicant shall demonstrate that pedestrian needs are still satisfied. Additionally, sidewalk may not be required on a local access street fronting the project if all of the following are true: a. The project is in a low -pedestrian zone (zones R-1, R-2, R-3, I-2); b. There are no other sidewalks within its block; and, c. Any part of the project is more than one mile radially away from an activity center (which includes but is not limited to parks, schools, large employment centers, religious institutions). The width of sidewalks shall be pursuant toas required in Tables 7.2 and 7.3. Wider sidewalk may be required to provide corridor continuity. At no location shall a sidewalk provide an unobstructed path of less than the required width. Wider sidewalk may be required at bus stops to allow bus riders a place to stand without hindering pedestrian movements or handicap access. When the existing sidewalk is not continuous along the street frontage, the Applicant shall construct sidewalk along the frontage of the project to provide continuity. The thickness of the sidewalk shall be pursuant toper Standard Plan R-103. Ad pted December 2009 Chapter 7 — Street Elements 7-16 CITY OF SPOKANE VALLEY STREET STANDARDS Meandering sidewalks may be approved by the City. The design of meandering sidewalks shall address obstructions, including mailbox mountings, street trees, fire hydrants, power poles, driveways, swales and street signs, without deviation from the required design width. Additional right-of-way (or easement) may be required to accommodate the obstructions or the meander of the sidewalk. 7.6.2 PEDESTRIAN RAMPS Pedestrian ramps shall be provided at all pedestrian crossings having vertical curb sections and shall be pursuant toper the Standard Plans R 105 and R 106. Every pedestrian ramp shall have at least one receiving ramp. This may require construction of "island" landing ramps. In special conditions, pedestrian ramps shall also be provided to enable passage across curbed radius return access points. Pedestrian ramps shall have detectable warning patterns formed with manufactured truncated domes in yellow. Pedestrian ramps shallare required to meet all ADA guidelines. 7.6.3 SIDE SLOPES Typical slopes for embankments should be 3:1 or flatter. The steepest slope for embankment or excavation shall be 2:1. Refer to Chapter 5 for additional requirements. On shouldered streets, a minimum space of five- feet shall be provided between the catch point of the side slope and the right-of-way line for the installation of utility poles, fences, sloped rounding, etc. Depending on site conditions, this may require additional right-of-way, retaining walls, or other requirements. The maximum slope of this space shall be 3:1. Slope easements shall be granted to the City when required by terrain or design features. 7.6.4 CLEAR ZONE Clear zone is defined as a relatively flat area void of fixed objects or obstructions beyond the edge of the traveled way that allows drivers to stop safely or regain control of a vehicle that leaves the traveled way. This area may consist of a shoulder, a recoverable slope, a non-recoverable slope, and/or a clean run -out area. The desired minimum width is dependent upon traffic volumes, traffic speeds, side slopes, and the street geometry. A recoverable slope is a slope on which a motorist may retain or regain control of a vehicle by slowing or stopping. Slopes flatter than 4:1 are generally considered recoverable. A non-recoverable slope is considered to be traversable but on which an errant vehicle continues to bottom. Embankment slopes between 3:1 and 4:1 may be considered traversable but non-recoverable if they are smooth and free of fixed objects. Ad pted December 2009 Chapter 7 — Street Elements 7-17 CITY OF SPOKANE VALLEY STREET STANDARDS A clear run -out area is the area at the top of a non-recoverable slope available for safe use by an errant vehicle. Slopes steeper than 3:1 are not considered traversable and are not considered part of the clear zone. For streets with Type B or Type A curb, the following is required: a. Sidewalk adjacent to the curb - Rigid objects shall be placed 2two feet behind the sidewalk; b. Separated sidewalk - Rigid objects shall be no closer than two- feet from the back of the curb; c. No sidewalk - Rigid objects shall be no closer than 2two feet from the back of the curb; d. Speed limit 40 mph or less - The clear zone distance is 2two feet behind the back of the curb. For all other pavement edges and design speeds, clear zone requirements per AASHTO's "A Policy on Geometric Design of Highways and Streets" shall be used. 7.6.5 SIGHT DISTANCE Sight distance is defined as the length of roadway that is entirely visible to the driver. All roads, intersections, and access points shall be designed to provide adequate sight distance for all normal driving situations and are required to conform to AASHTO's "A Policy on Geometric Design of Highways and Streets," latest edition. Stopping sight distance shall be calculated for vehicle crest curves and horizontal curves. The stopping sight distance shall not be less than the distances specified in Table 7.6. These values should be adjusted for grades 3% percent or greater, more than two lanes, skewed intersections, intersections near vertical or horizontal curves, or for design vehicles other than passenger cars. Ad pted December 2009 Chapter 7 — Street Elements 7-18 CITY OF SPOKANE VALLEY STREET STANDARDS TABLE 7.6 MINIMUM STOPPING SIGHT DISTANCE Design Speed (mph) Stopping Sight Distance (feet) 20 115 25 155 30 200 35 250 40 305 50 425 55 495 Table 7.7 statesspecifies the required sight distance for different types of intersections and approaches. These values shall be adjusted for grades with slopes of 3% percent or greater, number of lanes greater than two, for design vehicles other than passenger cars, using the procedures in the AASHTO design guidelines. For intersections or approaches located near horizontal or vertical curves, the City may require the 85th -percentile speed be used in the sight distance analysis. The 85th a given street unaffected by slower traffic or poor weather. This speed indicates the speed that most motorists on the street consider safe and reasonable under ideal conditions. Sight distance triangles shall be shown in the civil plans for all new intersections and all projects with new driveway approaches. Sight distance shall be continuous. Non -engineered driveways on local access streets are exempt from this requirement. Sight distance triangles shall be developed by an Engineer with traffic engineering experience developing intersection sight distance triangles. Fire hydrants shall be visible for at least 50 feet in either direction. A sight distance triangle shall be shown at the location of each fire hydrant in the civil plans and lot plans. The area within the sight distance triangle shall be free from any sight -obscuring objects pursuant toin accordance with AASHTO design guidelines. Sight - obscuring objects include but are not limited to buildings, parked vehicles, signs, fences, and landscaping. For sight triangles in the right of way, only grass may be planted. The City may remove, at the expense of the property owner, any vegetation or objects which obstruct sight distance because such obstructions are hazardous to the life, health, and safety of the public. Adopted December 2009 Chapter 7 — Street Elements 7-19 CITY OF SPOKANE VALLEY STREET STANDARDS The sight distance triangle shall be located completely within an easement or right- of-way, if required by the City. The property owner shall beis responsible for removing any objects that become a sight hazard. If an easement is not practical, the City may require additional right-of-way as a condition of development approval to ensure proper maintenance. TABLE 7.7 MINIMUM INTERSECTION & APPROACH SIGHT DISTANCES CASE TYPE THROUGH STREET TYPE THROUGH STREET SPEED LIMIT (MPH) DISTANCE FROM TRAVELWAY (FT) SIGHT DISTANCE' (FT) Case A — Uncontrolled Local access or lower 20 902 90 classification 25 1152 115 Case B — Signal, Any 25 153 280 Stop Control, Commercial 30 335 Approach & engineered driveways 35 390 1. These values should be adjusted for grades 3%o percent or greater, more than two lanes, skewed intersections, or for design vehicles other than passenger cars. 2. Distance back from center of intersection. 3. Use Figure 7-2. The following types of intersection and accesses are covered in Table 7.7. Other intersection types shall be analyzed pursuant to -using Chapter 9 of AASHTO Green Book. a. Case A can be used to analyze uncontrolled intersections which are intersections not controlled by a stop sign, traffic signal or yield sign. They are usually located on streets that carry low volumes and have a 25 mph speed limit. Figure 7-1 shows the sight distance triangle for this type of intersection. b. Case B can be used to analyze street approaches controlled by stop signs or a signal, commercial approaches and alleys. Figure 7-2 shows the sight distance triangle for Case B. Ad pted December 2009 Chapter 7 — Street Elements 7-20 CITY OF SPOKANE VALLEY STREET STANDARDS (B) Intersection Center 115 ft 115 ft FIGURE 7-1 SIGHT DISTANCE TRIANGLE FOR CASE A Major Street Required Sight Distance (C) • (C) • Point A is located at the center of the minor street approach lane 185 ft from the edge of traveled waypavement for driveway approaches and 15 ft for stop controlled and sitnalized intersections. Stop (A) (B) Points B & C are located at the center of major street approach through lane or in the center of the major street approach if more than one lane exists. FIGURE 7-2 SIGHT DISTANCE TRIANGLE FOR CASE B Ad pted December 2009 Chapter 7 — Street Elements 7-21 CITY OF SPOKANE VALLEY STREET STANDARDS 7.7 MISCELLANEOUS FEATURES 7.7.1 STREET NAMES The City and the Fire Department review proposed street names to conform to established names within the County grid to expedite property identification by emergency services. Street names shall also comply with the US Postal Services addressing standards. Street name designations shall be as follows: a. All north -south streets shall be called Streets; b. All east -west streets shall be called Avenues; c. Streets in large subdivisions that do not have a definite directional course shall be called Drives; d. A permanent dead-end or cul-de-sac street shall be called a Court; e. A street that lies diagonally to the east -west, north -south grid system and is an arterial or collector street shall be called a Boulevard; f. A street that has its ingress and egress on the same street shall be called a Circle; and, A private street shall be called a Lane. g. 7.7.2 MAILBOXES Mailbox installation and placement shall comply with€ollew AASHTO and US Postal Services guidelines. Mailboxes should not be placed in sight triangles or in clear zones. 7.7.3 GUARDRAIL Evaluation of embankments for guardrail installations shall be pursuant tom accordance with Chapter 710 of the WSDOT Design Manual. Guardrail installations shall conform to WSDOT/APWA Plan C-1, Beam Guardrail Type 1. End anchors shall conform to WSDOT/APWA Plan C-6, Beam Guardrail Anchor Type 1. 7.7.4 BOLLARDS Points of access shall be closed by a line of bollards when necessary to deny vehicle access to an easement, tract, or trail (except for maintenance or emergency vehicles). Bollards shall be wrapped with reflective tape. Closure shall include one or more fixed bollards on each side of the traveled way and removable, locking bollards across the traveled way. Spacing shall provide one bollard on centerline of the trail and other bollards at a maximum spacing of three; feet to preclude vehicular access. Fire access roads shall not be blocked in this manner without the approval of the Fire Department. Reflective tape and safety striping shall be placed on bollards. Bollards shall be placed 10 feet from the paved edge of roadway. Ad pted December 2009 Chapter 7 — Street Elements 7-22 CITY OF SPOKANE VALLEY STREET STANDARDS 7.7.5 ROADWAY BARRICADES Temporary and permanent barricades shall conform to the Manual on Uniform Traffic Control Devices (MUTCD). Type III barricades (see Standard Plan R-142) shall be used at the end of a local access street terminating abruptly without cul-de- sac bulb or on temporarily stubbed off streets. Each such barricade shall be used together with an end -of -road marker and signed future street extension. 7.7.6 ENTRANCE GATES Entrance gates are prohibitednot allowed on public streets. Use of entrance gates on private streets requires prior approvalshall be approved by the City and the Fire Department. Minimum gate opening width shall bei 20 feet. Proposed gates shall be clearly shown on the street plans. If a center island is used as part of an entrance gate feature, a minimum 14 -foot wide lane between face of curb and center island shall be provided. The center island shall not extend past the end of the gate when it is fully opened. Gated streets require a queuing area to allow vehicles to exit the connecting street prior to the gate. The queuing length shall be a minimum of 35 feet plus the gate width. Parking shall be prohibitedis not allowed within the queuing area, on either side of the street, for a distance equal to the queuing length. Signage for the "No Parking Zone" shall be placed on both sides of the gate. Gates shall be required to have a Fire Department emergency access device installed and maintained: a. A Knox key switch shall be installed on gates that provide access to 20 lots or less; or, b. An Opticom gate activation device shall be provided for subdivisions with more than 20 lots. 7.8 APPROACH DESIGN CRITERIA The following section contains design criteria for intersections and driveway approaches. These are minimum requirements and may be modified if traffic volumes (existing and/or projected), topography, design speed, design vehicle requirements, drainage, and other conditions, both existing and projected indicate a more stringent criterion is necessary. The City may require additional provisions to ensure public safety. All access points to and from City streets, including intersections and driveways shall be approved by the City prior to construction and require an approach permit. 7.8.1 APPLICABILITY These requirements apply to all new or altered intersection and driveway approaches to City streets. Ad pted December 2009 Chapter 7 — Street Elements 7-23 CITY OF SPOKANE VALLEY STREET STANDARDS 7.8.2 ACCESS LIMITATIONS a. While no property is denied access to City streets, direct street access is not guaranteed. When direct access is denied, properties may be required to: i. Access the street throughvia an alley; ii. Share a single driveway approach with two or more contiguous properties; or, iii. Restrict access with a right-in/right-out approach for properties located on arterials and with no available alternate access. Additionally, these properties may be required to construct street improvements to preclude left turning traffic. b. Properties shall beafe restricted to one access point on arterials and two access points on local access streets. The Development Services Senior Engineer after consultation with the Senior Traffic Engineethg may grant one additional arterial access point provided that: i. Minimum spacing requirements between access points are met with any driveway approaches; ii. The applicant demonstrates that additional access points will result in an improvement to safety or traffic flow both on-site and off-site; and, iii. One of the following situations exists: 1. The PM peak hour volume exceeds 100 PM peak hour vehicles -on both directions; or, 2. Traffic volumes using one driveway would exceed the capacity of a stop sign controlled intersection during the PM peak hour; or, 3. The ADT using one driveway would exceed 1,000 vehicles both directions. c. When a property has frontage on two or more streets, and spacing requirements on the major street cannot be met, the driveway approach shall be located on the street with the lowest classification unless safety considerations dictate otherwise. d. For a development that combines more than one underlying lot, these requirements, including the number and spacing of access points, shall apply to the development as a whole, not to each underlying lot. e. For all Binding Site Plans, excluding industrial zones, shared access shall beis required between the lots. The shared access shall include parking lot travel lane connections or shared driveway approach. If the Applicant adequately demonstrates a site design or building use limitation for installation of the travel lanes or shared approach on the existing property, exceptions to this requirement may be administratively granted. Exceptions may be approved if: Ad pted December 2009 Chapter 7 — Street Elements 7-24 CITY OF SPOKANE VALLEY STREET STANDARDS i. The City finds that the lack of shared access does not negatively impact the present or future function and safety of the parking lot circulation, ingress/egress, or roadway network; and, ii. The City finds that the lots required to share access have allowable incompatible uses; and, iii. The property does not have a feasible alternative site design solution. f. Driveways shallwill not be allowed where horizontal or vertical curves prevent the roadway from having continuous stopping sight distance or adequate intersection sight distance to safely accommodate the movements in and out of the driveway. 7.8.3 GENERAL DESIGN Approaches shall be constructed to avoid interference with existing drainage inlets, culverts, lighting, utility poles, traffic regulating devices, fire hydrants, or other facilities. The Applicant shall be responsible for the cost of relocating any of the above. The agency holding authority for the particular structure shall decide how the facility will be relocated, which may require approval of the City. If at the time of construction the fronting street does not have full width pavement or curb and gutter, a rural driveway approach may be used with the approach starting at the edge of the existing pavement (see the Standard Plans R 111). Approaches shall not restrict or impound drainage flow in the street. For shouldered streets with ditches, stormwater shall be conveyed under the driveway with a culvert. The minimum culvert size shall be 12 inches. For curbed roads, stormwater shall be conveyed using a culvert and Standard Plan R 110 or an inverted approach pursuant toef the Standard Plans R 111. If an existing approach is to be altered or abandoned, the unused portion of the original approach shalli-s-te be removed and replaced with curb, gutter and sidewalk matching that which is adjacent. Redevelopment projects shall be required to modify or eliminate any existing driveway approach that does not conform to these standards. 7.8.4 DRIVEWAY APPROACH HORIZONTAL AND VERTICAL GRADE Approaches shall align perpendicular to the street. The angle of intersection to the street shall not be less than 75 degrees. The angle may be reduced to 45 degrees for right-in/right-out driveways where the entering and exiting lanes are separated by a raised "pork chop" island (scc Standard Plan R 115). The vertical grade of approaches shall not exceed 8 percent within the right-of-way and shall be designed to preclude vehicles dragging when entering or exiting the site. Vertical grades shall not exceed 10% percent within ten10 feet of the right- of-way. Ad pted December 2009 Chapter 7 — Street Elements 7-25 CITY OF SPOKANE VALLEY STREET STANDARDS 7.8.5 APPROACH WIDTHS The total approach width shall not be greater than 50% percent of total lot frontage width. When approaches are constructed different than that shown on the construction plans, the design engineer shall verify that any impactedaffected street and stormwater facilities Estill meet the design requirementsgea1-5. If the facilities are inadequate, measures shall be taken to bring the facilities into compliance prior to their acceptance. Driveway approaches shall be designed pursuant tom the Standard Plans. Single family driveway approach shall be per Standard Plans R 110 through R 112. 7.8.5.2 Residential Private Strccts Approach for private streets shall match the required pavement width and shall be per Standard Plans R 110 and R 112. 7.8.5.37.8.5.1 Commercial/Industrial Commercial/industrial driveway approaches shall be per Standard Plans R 110 through R 112. High volume driveway approaches (Standard Plan R 113) may be required or permitted when all of the following conditions are present: a. The access is located along an arterial; b. Access volumes indicate a need for a radii curb return where the ADT exceeds 500 or where speed change lanes would be required; c. The access is designed to restrict turning movements, requiring the installation of an access island or center median; d. The roadway has no curb and gutter; e. The access serves an industrial property, or provides for commercial deliveries, where large truck movements are required; and, f. A traffic engineering analysis submitted by the applicant determines that a radii access is necessary to ensure adequate traffic safety and operation. 7.8.6 DRIVEWAY APPROACH ON-SITE LAYOUT Approaches shall provide access to an off-street parking area located on private property. The driveway shall be of sufficient length so a vehicle in the driveway does not project into the right-of-way, sidewalk, or pathway. Approaches and on- site parking shall be designed such that vehicle -backing maneuvers will not occur into the street/public right-of-way, impede pedestrian access to sidewalk or vehicles in the public street. Driveway approaches shall be designed to allow the largest typical vehicle using the approach (i.e. tractor trailers at large warehouses, delivery Adopted December 2009 Chapter 7 — Street Elements 7-26 CITY OF SPOKANE VALLEY STREET STANDARDS trucks at mini marts, etc.) to enter and exit the site without encroaching into opposing traffic. Whenever possible, the site should be designed for counterclockwise circulation of large trucks as left turns and left-hand backing maneuvers are easier and safer since the driver's position is on the left hand of the vehicle. All parking, loading and maneuvering of trucks shall be conducted on private property. 7.8.6.1 Driveway Stacking Length for Multi -use Properties Driveway stacking length for multi -use properties is the distance between the right-of-way and the near side of the first intersecting interior aisle or parking space. The driveway stacking length for multi -use properties shall be as follows: a. 20 feet for parking lots with less than 50 spaces; b. 50 feet for parking lots with up to 200 spaces; and, c. 80 feet for parking lots with over 200 spaces. 7.8.6.2 Driveway Stacking Length for Single -use Properties Driveway stacking length for single -use properties is the distance between the right-of-way and the proposed uses. The minimum length for driveway stacking for drive-thru windows shall be as follows: a. 150 feet for drive-in banks and drive-thru restaurants; b. 50 feet for automated tellers (ATM) and drive-in cleaners and repair services; c. 75 feet for automated car wash and espresso stands; and, d. 100 feet for controlled access parking. The City may require a traffic study to determine the stacking and queuing requirements for such uses that include, but are not limited to, service stations, drive-thru restaurants, drive-in banking, etc. The City may require sites with internal traffic congestion to design approaches with long throat lengths to provide extra storage to avoid impacting City streets. 7.8.7 CORNER CLEARANCE FROM INTERSECTIONS The following sections provide minimum corner clearances. Greater corner clearances may be required at the discretion of the City based on existing or proposed conditions at the intersection. In general, full access driveways are not allowed within the functional intersection boundary, which can be minimally defined by the length of the turn pockets, but may extend further from the intersection. Where the driveway location does not meet minimum City criteria, or where a safe driveway location cannot be found, the City may requires reasonablgapprepriatc mitigation measures to provide for as safe a driveway as feasible. Ad pted December 2009 Chapter 7 — Street Elements 7-27 CITY OF SPOKANE VALLEY STREET STANDARDS 7.8.7.1 Single Family Residential Residential driveway approaches may not be located closer than 15 feet from the point of curvature of a curb return. 7.8.7.2 Commercial/Industrial Commercial driveway approaches may not be located closer than 75 feet from the point of curvature of a curb return. 7.8.8 DRIVEWAY APPROACH SPACING - SAME SIDE OF STREET Table 7.8 provides the minimum distance allowed between the centerlines of adjacent driveway approaches. The distance is measured from centerline to centerline of each approach. TABLE 7.8 - DRIVEWAY APPROACH SPACING STREET CLASSIFICATION DESIRABLE CONDITIONS SEPARATION (FT) LIMITING CONDITIONS SEPARATION (FT) Collector 70 50 Minor Arterial 90 60 Principal Arterial 120 80 Desirable conditions shall be applied when sufficient space or street frontage is available. If sufficient space or street frontage for desirable conditions is not available, then lesser distances, down to, but not less than the requirement for limiting conditions, may be applied. 7.8.9 DRIVEWAY APPROACH METHODS OF MEASUREMENTS Driveway throat width is measured perpendicular to the centerline of the driveway between lines defined by the radii, whether or not that occurs inside the property lines and is physically marked with curbing. Driveway throat length is measured along the centerline of the driveway from the back edge of the driveway apron and the nearest vehicle aisle or circulation road. Dimensions in this section refer to distances from (or along) face of curb. In the absence of a curb, the measurement is considered to be from (or along) the edge of pavement. Driveway angles are measured between the driveway centerline and centerline of the roadway. 7.8.10 RESTRICTED ACCESS DRIVEWAYS Restricted access approaches do not allow left-hand turns out of or into the driveway approach. Development or redevelopment of properties, where the Ad pted December 2009 Chapter 7 — Street Elements 7-28 CITY OF SPOKANE VALLEY STREET STANDARDS required setback from an intersection cannot be achieved in any direction and without other ways to access the site, may be required to use a restricted access driveway. In some cases a raised median may be required down the street centerline. Restricted access approaches shall only be allowed when approved by the City. The existence of other approaches in the vicinity that do not meet standards is not grounds for allowing further substandard approaches. 7.8.11 ALIGNMENT OF CROSS -STREET DRIVEWAY APPROACHES Driveways should be placed directly opposite from each other whenever possible. If this is not possible and adequate left -turn storage capacity is not available in advance of each driveway, combining of driveways on the same side of the street may be required. The requirement above shall not apply if the street to be accessed has a permanent median and/or traffic control device that prevents any cross -street movement of traffic or if the City determines that adhering to said requirement would be unsafe. 7.8.12 SIGNALIZED DRIVEWAY APPROACHES If the Traffic Impact Analysis determines that there is or will be a need to signalize proposed access points, then proposed access points shall be aligned directly opposite any existing or proposed access points or T -intersection across the street. Where driveways are to be signalized, a minimum spacing of 1,320 feet to any other signalized intersection should be maintained or shall be spaced as approved by the City. Roundabouts may be considered as an alternative option by the City. 7.8.13 APPROACHES ON STATE HIGHWAYS This section contains specific access standards for state highways within the City limits, which are classified as managed access facilities. Managed access is based on the premise that access rights of a property owner are subordinate to the public's right and interest in a safe and efficient highway system. Pursuant toln accordance with RCW Gchapter 47.50 RCW, the City adopts by reference, the provisions of WAC Cchapter 468-52 WAC, as adopted or amendedtogcthcr with all future amendments, in order to regulate and control vehicular access and connection points of ingress to and egress from, the State Highway System within the incorporated areas of the City of Spokane Valley. State Routes (SR) within the City include SR -27 (Pines Road) and SR -290 (Trent Avenue). The current access classifications for SR -27 and SR -290 are shown in Table 7.9. Ad pted December 2009 Chapter 7 — Street Elements 7-29 CITY OF SPOKANE VALLEY STREET STANDARDS TABLE 7.9 STATE ROUTES CLASSIFICATIONS STATE ROUTE BEGINNING MILEPOST ENDING MILEPOST APPROXIMATE LOCATION CURRENT ACCESS CLASSIFICATION 27 83.14 84.61 14TH TO CITY LIMITS M2 27 84.61 86.49 14111 TO —NORA M5 27 86.72 87.70 MONTGOMERY TO 290 M5 290 4.31 6.35 FANCHER TO ARGONNE M5 290 6.35 10.29 ARGONNE TO PROGRESS M4 290 10.29 12.84 PROGRESS TO CITY LIMITS M2 7.9 TRAFFIC CALMING Traffic calming devices improve neighborhood livability by reducing the speed and impact of vehicular traffic on residential streets. 7.9.1 NEW DEVELOPMENT The internal local access street layout shall be designed oto discourage through, high-speed traffic or shall incorporate traffic calming devices in the design. The Applicant may utilize one or more of the traffic calming devices. Proposed devices shall be reviewed and approved by the City at the time of preliminary design review. Traffic calming devices shall be installed at the expense of the Applicant. 7.9.2 EXISTING DEVELOPMENT Traffic calming devices are prohibitednot allowed on arterials. On collectors and local access streets, traffic calming devices are only allowed when warranted by an engineering study and approved by the City. The installation of devices shall be neighborhood -_funded. 7.9.3 TRAFFIC CALMING DEVICES Currently, the only traffic calming device allowed by the City is the Traffic Circle (see Standard Plan T-101). Alternative devices recommended by the Applicant's Engineer may be permitted with City approval. Ad pted December 2009 Chapter 7 — Street Elements 7-30 CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIONALLY LEFT BLANK Ad pted December 2009 Chapter 7 — Street Elements 7-31 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 8 - PAVEMENT DESIGN Chapter Organization 8.1 Introduction 1 8.2 Street Classification 1 8.3 Street Pavement and Subgrade 1 8.3.1 Travelways In Residential Zones 1 8.3.2 Travelways In Non -Residential Zones 2 8.3.3 Subgrade Preparation 2 8.4 Engineered Pavement Parameters 3 8.4.1 Traffic Parameters 3 8.4.2 Reliability Level 4 8.4.3 Overall Standard Deviation 4 8.4.4 Initial and Terminal Serviceability Indexes 4 8.4.5 Structural Layer Coefficients 4 8.4.6 Drainage Layer Coefficients 4 8.4.7 Subgrade Evaluation 5 8.5 Report Submittal 5 8.6 Materials Specifications 5 8.6.1 Gravel Base 5 8.6.2 Crushed Rock 6 8.6.3 Asphalt or Concrete Treated Base 6 8.6.4 Hot Mix Asphalt 6 Adopted December 2009 Chapter 8 Pavement Design 8-i CITY OF SPOKANE VALLEY STREET STANDARDS 8.6.5 In-place Mainline Asphalt Compaction Test Requirements 6 8.6.6 Cold Joint Requirements 7 8.6.7 Longitudinal and Transverse Joint Requirements 7 8.6.8 Tack Coats — Preparation of Existing Surfaces 7 8.6.9 Cover Asphalt Loads During Transport 8 8.6.10 Breakdown Rolling Maximum Temperature Loss 8 8.6.11 Asphalt Temperature Placement Requirements 8 8.6.12 Paving Dates & Weather Limitations 9 List of Tables Table 8.1 — Equivalent Single Axle Loads 3 Table 8.2 — Initial and Terminal Serviceability Indexes 4 Table 8.3 — Structural Layer Coefficients 4 Table 8.4 — Recommended Drainage Coefficients 5 Table 8.5 — Moduli Ratio 5 Table 8.6 — Performance Grade 6 Table 8.7 — Recommended Minimum Laydown Temperature 9 Adopted December 2009 Chapter 8 Pavement Design 8 -ii CITY OF SPOKANE VALLEY STREET STANDARDS 8.1 INTRODUCTION This chapter provides the minimum requirement for the design of pavement sections for travelways streets within the City. The use of these design criteria will ensure that paved transportation corridors are improved in a uniform and consistent manner. The requirements presented in this chapter have been established to minimize structural failures in streets, due to traffic loadings and/or existing soils conditions. 8.2 STREET CLASSIFICATION All public streets in the City have been classified using the Federal Functional Classification system, which provides a hierarchy from principal arterials to local access streets, to accommodate existing and anticipated traffic. Street classifications can be found in the City of Spokane Valley's currently -adopted Comprehensive Plan. A street's classification is used to determine the volume and mix of vehicles for which it is designed. In cases where a street has yet to be designated a specific classification, the anticipated traffic volume should be used. If available, the City may provide the anticipated daily traffic for a street. However, the Applicant may be required to obtain additional traffic information. 8.3 STREET PAVEMENT AND SUBGRADE 8.3.1 TRAVELWAYS IN RESIDENTIAL ZONES The requirements of this section apply to local access streets, private streets, alleys, and private driveways located in residential zones. For the purpose of pavement design, the engineering characteristics of the subgrade soil shall be determined through laboratory testing. Laboratory testing consisting of California Bearing Ratio (CBR) testing, Resilient Modulus (Mr) testing or Resistance Value (R -value) testing may be used to characterize the subgrade soil supporting capability. A minimum street section of three3 inches of hot mix asphalt (HMA) over size inches of properly placed and compacted crushed rock is required for local access streets, private streets, and alleys regardless of native soils. A minimum pavement section of 2two inches of HMA over esix inches of crushed rock is required for private driveways. A soils investigation is required for all projects. The minimum pavement section cannot be used for sites with poor subgrade soils, which are soils that meet any of the criteria below: a. Have CBR less than 4three; b. Have R -values less than 20; c. Have Mr values less than 3,000 psi; or, Adopted December 2009 Chapter 8 Pavement Design 8-1 CITY OF SPOKANE VALLEY STREET STANDARDS d. Are classified as MH, CL, CH, OL or peat in accordance with the Unified Soil Classification System. When results of laboratory testing indicate that poor subgrade soils are present, an engineered pavement design is required. Subsurface explorations (borings/test pits) are required for each streeta+rwetway to demonstrate the subgrade soils meet the criteria above. Exploration should extend to a depth of at least 5five feet below proposed pavement subgrade. 8.3.2 TRAVELWAYS IN NON-RESIDENTIAL ZONES Engineered pavement design is required for commercial local access streets, commercial alleys, collector arterials, and arterials. The resilient modulus value can be acquired using the following methods: a. Mr testing: Soil samples shall be obtained and sent to a private lab for testing. The proposed street shall have a minimum of one laboratory test for every 1,000 feet of street and/or for every obvious change in subgrade material (minimum of 4three tests per street). b. CBR testing or R -value testing: Soil samples shall be obtained and sent to a private lab for testing. The proposed street shall have a minimum of 4 -one laboratory test for every 1,000 feet of street and/or for every obvious change in subgrade material (minimum of three; tests per street). A geotechnical engineer shall be retained to provide recommendations for correlations between CBR or R -value results and Mr values. c. In-situ testing using a non-destructive deflection test method: The Applicant shall obtain approval from the City for the type of non-destructive deflection test method proposed, before conducting the testing. For non- destructive deflection testing, a statistical analysis is needed. The results shall be reported by street stationing. Test results shall include a graph of the resilient modulus values vs. street stationing. The graph shall be included in the pavement design report. A minimum street section of 4four inches of HMA over esix inches of properly placed and compacted crushed rock is required regardless of the pavement design results in accordance with Section 8.4. 8.3.3 SUBGRADE PREPARATION Prior to placing any street base material, the subgrade shall be rolled and compacted to a minimum of 95% percent of the maximum dry density as determined by ASTM D-1557 (Modified Proctor). This degree of compaction shall extend to a depth of at least one -1- foot below pavement subgrade elevation in cut areas. The fill areas shall be compacted to at least 95% percent of the maximum dry density based on ASTM D1557 and WSDOT Standard Specification 2-03.3(14)C Compacting Earth Embankments, Method C. Fill placed more than two2 feet below pavement subgrade elevation shall be compacted to at least 95% percent of the maximum dry density based on ASTM D1557. Adopted December 2009 Chapter 8 Pavement Design 8-2 CITY OF SPOKANE VALLEY STREET STANDARDS Any street section which cannot be compacted to the degree specified above shall be removed to a depth of 2 -two feet or to a depth where the pumping ceases, or as directed by the Onsite Inspector, and replaced with granular imported material that can be compacted to at least 95% percent of the maximum density as determined by ASTM D-1557, or as directed by the Oonsite Inspector. Prior to placing any sub -base or base materials, geo-textile fabric on the subgrade may be required if the existing subgrade is a fine-grained soil (ML, CL, MH, or CH). The geotextile fabric shall meet the criteria in Section 9.33 for "Separation" of the most current version of the WSDOT Standard Specifications. If the material is unsuitable, the soil shall be excavated below grade and compacted per WSDOT Standard Specification 2-03.3(3) and 2-03.3(14) Method C. 8.4 ENGINEERED PAVEMENT PARAMETERS Engineered pavement designs shall be pursuant toin accordance with the most current version of the 1993 AASHTO Guide for Design of Pavement Structures for flexible pavements and the following criteria: 8.4.1 TRAFFIC PARAMETERS The existing traffic levels shall be increased to match the projected traffic at the end of the street design life. The minimum design life shall be 20 -_years. The growth rate is 1.5% percent for residential streets and 3.5% percent for commercial/industrial streets and arterial streets. The 1.5% percent growth rate may be waived in closed subdivisions with City approval. This growth rate shall only be used for pavement design purposes and shall not be used for traffic analyses. The engineer shall submit Equivalent Single -Axle Loads (ESALs) calculations. The truck factors found in Table 8.1 may be used in the absence of other information. TABLE 8.1 — EQUIVALENT SINGLE AXLE LOADS VEHICLE TYPE TRUCK FACTOR (ESALs/VEHICLE) School Bus 2.87 STA Bus 2.57 Refuse Truck 1.03 All other trucks (averaged) 0.42 Adopted December 2009 Chapter 8 Pavement Design 8-3 CITY OF SPOKANE VALLEY STREET STANDARDS 8.4.2 RELIABILITY LEVEL The reliability level (R) for residential streets and local non-residential streets is 75% percent. For all other street classifications, the reliability level is 90% percent. 8.4.3 OVERALL STANDARD DEVIATION The overall standard deviation (S) is 0.45 for new construction and 0.49 for overlay projects. 8.4.4 INITIAL AND TERMINAL SERVICEABILITY INDEXES The initial and terminal serviceability indexes shall be per Table 8.2. TABLE 8.2 - INITIAL AND TERMINAL SERVICEABILITY INDEXES STREET CLASSIFICATION PSI(INITIAL) PSI(TERMINAL) Private streets, alleys, access street, residential streets & local non-residential 4.2 2.00 Collector and minor arterials 4.2 2.25 Principal arterials 4.2 2.50 8.4.5 STRUCTURAL LAYER COEFFICIENTS Structural Layer Coefficients (aj) for new material shall be in accordance with Table 8.3. TABLE 8.3 - STRUCTURAL LAYER COEFFICIENTS MATERIAL STRUCTURAL COEFFICIENT HMA 0.42 Crushed rock 0.14 Gravel base 0.10 8.4.6 DRAINAGE LAYER COEFFICIENTS Drainage coefficients (mi) for crushed rock and gravel base shall be in accordance with Table 8.4. This coefficient is used to modify the structural layer coefficients of untreated base and sub=basin materials in flexible pavements. If limited information is available regarding drainage conditions, a value of 0.95 may be used. TABLE 8.4 - RECOMMENDED DRAINAGE COEFFICIENTS PERCENT OF TIME PAVEMENT STRUCTURE IS EXPOSED TO MOISTURE LEVELS APPROACHING SATURATION Quality of Less Than Greater Than Drainage 1% 1-5% 5-25% 25% Excellent 1.40-1.35 1.35-1.30 1.30-1.20 1.20 Good 1.35-1.25 1.25-1.15 1.15-1.00 1.00 Fair 1.25-1.15 1.15-1.05 1.00-0.80 0.80 Adopted December 2009 8-4 Chapter 8 Pavement Design CITY OF SPOKANE VALLEY STREET STANDARDS Poor 1.15-1.05 1.05-0.80 0.80-0.60 Very Poor 1.05-0.95 0.95-0.75 0.75-0.40 0.60 0.40 8.4.7 SUBGRADE EVALUATION Prior to designing the pavement thickness, the subgrade soil shall be evaluated in accordance with Section 8.3.2 to establish a design Mr value. The following moduli ratios (ratio of seasonal moduli to "summer" module) found in Table 8.5 can be used to determine the effective roadbed (subgrade) resilient modulus value (MReff): TABLE 8.5 — MODULI RATIO SAMPLE COLLECTION PERIOD MODULI RATIO Winter (January) 1.00 Winter & Spring (February through May) 0.85 Summer (June through September) 1.00 Fall (October through December) 0.90 8.5 REPORT SUBMITTAL The Applicant shall submit a geotechnical report for all sites. The report shall be prepared and stamped by an eEngineer with experience in geotechnical engineering. The report shall include, as applicable: a. Narrative of the site conditions and soils; b. Recommended pavement section; c. Site plan showing soil sample locations; d. Field data; including boring or test pit logs; e. Laboratory testing results, including discussion of CBR/modulus subgrade correlation or R value/modulus subgrade correction; and, f. Pavement design calculations. 8.6 MATERIALS SPECIFICATIONS The following material requirements refer to or amend the most current version of the WSDOT Standard Specifications. 8.6.1 GRAVEL BASE Gravel base shall be bank run gravel, defined as naturally occurring material having characteristics such that when compacted in place on the street, it provides a course having greater supporting value than the subgrade on which it is placed. It shall be pursuant to in accordance with Section 9-03.10 of the most current version of the WSDOT Standard Specifications. Adopted December 2009 Chapter 8 Pavement Design 8-5 CITY OF SPOKANE VALLEY STREET STANDARDS 8.6.2 CRUSHED ROCK Crushed rock used shall fall under the following two classifications: a. Crushed Surfacing Top Course (CSTC) b. Crushed Surfacing Base Course (CSBC) CSTC and CSBC shall be in accordance with Section 9-03.9(3) of the most current version of the WSDOT Standard Specifications, including the following modification: The crushed aggregate portion which is retained on the No. 4 sieve shall contain not more than 15% percent, by weight, of flat or elongated pieces as defined in ASTM D 693. The crushed aggregate shall have at least 90% percent by weight of particles with at least one fractured face. The area of each face shall be equal to at least 75% percent of the smallest mid-section area of the piece. 8.6.3 ASPHALT OR CONCRETE TREATED BASE When compaction soils type or moisture content precludes proper compaction, asphalt treated base (ATB) or concrete treated base (CTB) should be utilized. 8.6.4 HOT MIX ASPHALT Hot mix asphalt shall pursuant tobe in accordance with the most current versionedition of the WSDOT Standard Specifications. Pavement design calculations shall be performed by an Engineer experienced with performance grade oils and pavement design calculations. Asphalt used in City street construction shall use performance grade asphalt binders, pursuant toin accordance 3,1,4414 AASHTO Designation MP -1. The minimum base binder used shall be PG - 64 -28. Required base binders based on street type and condition are provided in Table 8.6. TABLE 8.6 — PERFORMANCE GRADE STREET CLASSIFICATION PERFORMANCE GRADE Local access, private streets, and alleys 64-28 Collectors and arterials 70-28 Aggregate for use in hot mix asphalt shall be Class 1/2—inch in accordance with Section 9-03.8(1) of the current version of the WSDOT Standard Specifications. 8.6.5 IN-PLACE MAINLINE ASPHALT COMPACTION TEST REQUIREMENTS A lot consists of Mive random individual tests. Minimum density testing requirements are 4 -one lot per 400 tons of HMA or -tone lot per day, whichever results in the greater number of lots. A lot shall be rejected if any of the following occurs: Adopted December 2009 8-6 Chapter 8 Pavement Design CITY OF SPOKANE VALLEY STREET STANDARDS a. The average compaction of the lot is less than 92% percent of maximum density, as determined by WSDOT FOP for AASHTO T166 and T209; or; b. Any individual compaction test in the lot is less than 91% percent or higher than 96% percent of the maximum density, as determined by WSDOT FOP for AASHTO T166 and T209. Additional testing requirements shall be pursuant toper Appendix 9-A. 8.6.6 COLD JOINT REQUIREMENTS Section 5-04.3(10)B of the current version of the WSDOT Standard Specifications for Road, Bridge, and Municipal Construction, 2008 edition is supplemented as followswith the following: a. Extreme care shall be exercised in the construction of cold joints to }ensure that the joint is properly tacked with a uniform and heavy coating of an approved tacking agent, that the placement of HMA adjacent to the cold joint is properly raked and that the adjacent hot mix is rolled and compacted in such a manner so as to completely seal the joint. The formation of all joints shall be made in such a manner as to ensure a continuous bond between the courses and obtain the required density. All joints shall be the same texture as other sections of the course and meet the requirements for smoothness and grade. b. If in the opinion of the City, the cold joint has not been properly constructed, the joint shall be sealed with a joint compound sealant pursuant toas per AASHTO M 324, at the Contractor's own expense. 8.6.7 LONGITUDINAL AND TRANSVERSE JOINT REQUIREMENTS Section 5-04.3(12) Joints of the current version of the WSDOT Standard Specifications for Road, Bridge, and Municipal Construction, 2008 edition is supplemented as follows with the following: a. The formation of all joints shall be made in such a manner as to ensure a continuous bond between the courses and obtain the required density. All joints shall be the same texture as other sections of the course and meet the requirements for smoothness and grade. b. When paving occurs on an arterial street within the City of Spokane Valley, cold joints will be limited to the centerline of the roadway and shall be constructed pursuant toper Standard Plan R -127 -Step Wedge Longitudinal Cold Joint. A paving plan shall be submitted, to the CityPublic Works, detailing how the work is to be accomplished. Where possible, the Contractor shallis required to use multiple pavers in order to reduce or eliminate longitudinal joints. 8.6.8 TACK COATS — PREPARATION OF EXISTING SURFACES Section 5-04.3(5)A, paragraph two2 of the current version of the WSDOT Standard Specifications for Road, Bridge, and Municipal Construction is hereby amended as follows: Adopted December 2009 Chapter 8 Pavement Design 8-7 CITY OF SPOKANE VALLEY STREET STANDARDS a. A tack coat of asphalt shall be applied to all paved surfaces on which any course of HMA is to be placed or abutted. Tack coat shall be uniformly applied to cover the existing pavement with a thin film of residual asphalt, free of streaks and bare spots. The application rate shall be 0.02 to 0.08 gallons of retained asphalt per square yard. If the tack coat has been diluted with water, as allowed in this section, then the application rate must be adjusted in order to achieve the retained amount of asphalt required. A heavy application of tack coat will be applied to all joints. Thin lifts of pavement require heavier applications of tack coat to prevent raveling, spalling and delamination. As a guide, existing surfaces that are coarse, dry or milled require a higher application rate of tack coat than surfaces that appear rich or bleeding. For streets open to traffic, the application of tack coat shall be limited to surfaces that will be paved during the same working shift. The spreading equipment shall be equipped with a thermometer to indicate the temperature of the tack coat material. 8.6.9 COVER ASPHALT LOADS DURING TRANSPORT Tarpaulin material shall be used to cover asphalt loads during transport from plant to project for all projects when the ambient air temperature is 50°F 50 degrees Fahrenheit or less. 8.6.10 BREAKDOWN ROLLING MAXIMUM TEMPERATURE LOSS Breakdown rolling shall occur before 20°-F or greater temperature loss of the mix from the point of laydown. Temperature for basis shall be that observed and recorded in the transport vehicle at time of discharge to the paver. 8.6.11 ASPHALT TEMPERATURE PLACEMENT REQUIREMENTS Table 8.7 shows the minimum laydown temperatures and rolling times. Vibratory compaction shall not be used after the asphalt mat cools below 175°F. The rolling pattern shall be established in conjunction with asphalt density testing. TABLE 8.7 RECOMMENDED MINIMUM LAYDOWN TEMPERATURE 1. Reference is Table 6-4 from the National Center for Asphalt Technologies, Hot Mix Asphalt, Mixture Design and Construction. Adopted December 2009 8-8 Chapter 8 Pavement Design MAT THICKNESS (INCHES) Base Temp, F % 3A 1 1 1/2 2 >3 40-50 310 300 285 275 50-60 310 300 295 280 270 60-70 310 300 290 285 275 265 70-80 300 290 285 280 270 265 80-90 290 285 275 270 265 260 < 90 280 275 270 265 260 255 Rolling Time (min) 4 6 8 12 15 15 1. Reference is Table 6-4 from the National Center for Asphalt Technologies, Hot Mix Asphalt, Mixture Design and Construction. Adopted December 2009 8-8 Chapter 8 Pavement Design CITY OF SPOKANE VALLEY STREET STANDARDS 2. Time available between recommended laydown temperature and cessation temperature (175-°F) when attempts to compact the mat should cease. 3. These compaction temperatures are estimates and will vary with different asphalt cements and aggregates. For thin mats, the time available for rolling is short. For example, a 3/4 -inch mat placed at the recommended minimum laydown temperature has only 6six minutes to be compacted to achieve the target density. The roller speeds cannot be increased significantly without adversely affecting density; hence, additional rollers may be required when paving at low temperatures. Subgrade cannot be frozen for laydown. Subgrade may be required to be protected depending on the outside temperatures. Compaction requirements shallmust be met. 8.6.12 PAVING DATES & WEATHER LIMITATIONS WSDOT Section 5-04.3(16) Weather Limitations is amended as follows: a. HMA shall not be placed on any traveled way between October 1st and April 1st without written approval from the City. Adopted December 2009 Chapter 8 Pavement Design 8-9 CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIALLY LEFT BLANK Adopted December 2009 Chapter 8 Pavement Design 8-10 CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 9 - INSPECTION & CERTIFICATION Chapter Organization 9.1 Introduction 1 9.2 Applicability 1 9.3 Authority to Stop Work 1 9.4 Responsibilities 1 9.4.1 Development Inspector 1 9.4.2 On-site Inspector 2 9.4.3 Applicant's Engineer 2 9.4.4 Contractor 3 9.5 Right -of -Way Permits 3 9.6 Pre -construction Meeting 3 9.7 Construction Notification 4 9.7.1 Notices of Upcoming Construction 4 9.7.2 Notices of Utility Shutdown and Access Limitations 5 9.7.3 Notices for Inspection 5 9.8 Field and Lab Testing 6 9.8.1 Reporting 6 9.8.2 Minimum Material Testing Frequencies 6 9.8.3 Field Testing and Lab Requirements 6 9.9 Required Inspections 6 9.9.1 Erosion and Sediment Inspections 7 Updated January 2017 9-i Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS 9.9.2 Utility Inspections 7 9.9.3 HMA Inspections 7 9.9.4 Drainage Structure Inspections 7 9.9.5 Drainage Swale and Drainage Facilities Inspections 7 9.9.6 Swale Inspection During Warranty Period 8 9.10 Miscellaneous 8 9.10.1 Changes During Construction 8 9.10.2 Construction Complaints 9 9.10.3 Conflict Resolution 9 9.11 Final Walk -Through 9 9.12 Record Drawings 9 9.13 Project Certification 10 9.13.1 Certification of Drainage Facilities 11 9.14 Performance Surety 11 9.14.1 Performance Surety Authorized 11 9.14.2 Performance Surety Criteria 11 9.14.3 Performance Surety Release 12 9.15 Warranty Surety 12 9.15.1 Warranty Surety Amount 12 9.15.2 Acceptable Sureties 12 9.15.3 Warranty Duration 13 9.15.4 Time Frames to Complete Repair 13 9.15.5 Failure to Complete Repair 13 9.15.6 Responsibility for Maintenance 13 9.16 Street Establishment 13 List of Figures Figure 9-1 Typical Sign 5 List of Tables Table 9.1 Required Sign Information 5 List of Appendices Appendix 9-A - Minimum Material Testing Frequencies 16 Appendix 9-B - Final Certification Checklist - Sample 17 Appendix 9-C - Removed Appendix 9-D - Erosion and Sediment Control Log 18 Updated January 2017 9 -ii Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS 9.1 INTRODUCTION Inspection oversight is required for the construction of all public and private streets, alleys, driveways, and utility improvements. Water and sewer construction shall also be monitored by the system purveyor and/or agency of system ownership. The City of Spokane Valley's construction certification process is based on the project construction certification procedures found in the Project Construction Certification Procedures for Spokane County Road, Drainage, and Sewer Projects, dated April 2002. Spokane County Department of Public Works and the American Council of Engineering Companies of Washington (a subcommittee named the Spokane County Construction Certification Committee) developed that document. 9.2 APPLICABILITY The following projects require construction certification: a. New construction of public streets; b. New construction of private streets; c. New construction of engineered driveways; d. Frontage improvements on public streets, including pavement widening, curb and gutter, sidewalk, and drainage improvements; and, e. Swales and drywells. 9.3 AUTHORITY TO STOP WORK The Development Inspector has the authority to stop work when any of the following situations exists: a. The Contractor is working without a valid permit; b. The Contractor is executing work not included in the approved plans; c. Required inspections and tests are not being performed; d. Test results do not meet required specifications; and, e. Construction activities have the potential to adversely impact public or private property or human life. 9.4 RESPONSIBILITIES 9.4.1 DEVELOPMENT INSPECTOR The Development Inspector is a City employee and is responsible for: a. Coordinating with and reviewing submittals from the On-site Inspector(s); Updated January 2017 9-1 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS b. Performing development walk-through on private and public streets for acceptance and surety reductions; c. Reviewing and accepting certification packages. A project certification will not be accepted if required frequencies for testing are not met or test results do not meet specifications; d. Reviewing quantity estimates for performance and warranty sureties; e. Performing final inspections of public streets for surety release and street establishment; and, f. Inspecting swales located in border easements and/or right-of-way for single family dwellings and duplexes prior to issuing a certificate of occupancy. 9.4.2 ON-SITE INSPECTOR The Applicant is required to secure the services of an On-site Inspector for all projects requiring certification. The On-site Inspector is responsible for: a. Preparing weekly reports; b. Ensuring that plans and specifications are followed; c. Inspecting paved areas, curb and gutter, sidewalks, approaches, drainage improvements, and utilities within the right-of-way and border easements. The On-site Inspector shall be present at all times for HMA placement, any trench work within the street prism, and for drywell installation; d. Coordinating required testing and frequencies (see Appendix 9-A); e. Monitoring traffic control; f. Verifying fire hydrants, gates, and No Parking signs were installed at the location shown in the plans; g. Preparing as -built drawings, and, h. Preparing the certification package. 9.4.3 APPLICANT'S ENGINEER The Applicant's Engineer is an Engineer, as defined in the Definitions, hired by the Applicant. The Applicant's Engineer provides required project modifications that occur during the construction process, coordinating with the Contractor and obtaining City approval when significant modifications are required. Conflicts arising due to concerns regarding project design or constructability, whether surfaced by the Contractor, On-site Inspector, or Development Inspector, shall be addressed by the Applicant's Engineer. The method of addressing the Updated January 2017 9-2 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS concern shall be confirmed by the Development Inspector with specific follow-up oversight by the On-site Inspector. 9.4.4 CONTRACTOR The Contractor is responsible for: a. Attending the pre -construction meeting; b. Providing all licenses, bonds and insurance information at the pre - construction meeting; c. Construction notification in accordance with Section 9.7; d. Having knowledge of the testing frequencies and construction items requiring inspection (see Appendix 9-A); e. Notifying the On-site Inspector and Development Inspector, as applicable, prior to the placement of construction items requiring inspection; f. Completing all improvements in accordance with the approved plans; and, g. Correcting deficiencies as identified by the On-site Inspector, the Development Inspector, or the applicant. 9.5 RIGHT-OF-WAY PERMITS Right-of-way permits are required for all work in the public right-of-way. No person, firm or corporation shall commence work or permit any other person, firm or corporation to commence work on the construction, alteration, repair or removal, cutting and/or paving of any street, alley or other public place in the City without first obtaining a written right- of-way construction permit and approved plans from the City. The Applicant shall secure the services of an On-site Inspector before securing a right-of- way construction permit for any given project requiring certification. 9.6 PRE -CONSTRUCTION MEETING A pre -construction meeting is required for the following projects: a. Subdivisions; b. Short subdivisions; c. Binding site plans; d. Commercial projects with frontage and/or full street improvements; and, e. Other projects which the City deems a pre -construction meeting is required. The pre -construction meeting shall be held prior to commencing work. The purpose of the pre -construction meeting is to discuss project concerns or issues, construction notification requirements and certification procedures. The Applicant, Applicant's Engineer, Contractor, HMA and concrete subcontractors, Development Inspector and On-site Inspector are required to attend this meeting. A pre -construction meeting will not be held Updated January 2017 9-3 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS if the Contractor, paving and concrete subcontractors, and/or the On-site Inspector are not present. The Contractor shall bring a properly planned and coordinated project schedule to the pre - construction meeting. 9.7 CONSTRUCTION NOTIFICATION 9.7.1 NOTICES OF UPCOMING CONSTRUCTION Construction warning signs shall be securely posted 48 days prior to construction of short subdivisions, subdivisions or any other project with street construction. Signs shall be placed at all ingresses to the project area and shall be clearly visible from the right-of-way. A typical sign is included in Figure 9-1. The Contractor shall notify the Development Inspector within 24 hours of installing the sign(s). The signs shall be posted for the duration of the project and shall conform to the following: a. The signs shall be made of materials that are able to withstand weather for the duration. The signs shall be maintained to remain readable from the public right-of-way; b. The sign supports shall meet current safety standards; c. The bottom of the sign shall be 7 feet above ground; d. Lettering shall be easily readable and shall be per Table 9.1; and, e. The signs shall include the information required in Table 9.1. On large or high profile projects, the Applicant shall provide the proposed project schedule and weekly updates to the City's Public Information Officer to notify the public of the project progress. Updated January 2017 9-4 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS FIGURE 9-1 TYPICAL SIGN Road Work Next 600 Feet Begin: May 25, 2008 — End: Oct. 12, 2008 Work Includes: Sewer and Water Installation, Roadway Widening and Repaving Contractor: Dee Caterpillar, (999) 636-3333, Pave la Tierra, Inc. Engineer: Mike Mylar, (999) 111-2233, Pan Global Engineering Developer: Ima Platter, (999) 555-1212, Progression Homes, LLC Thank you for your patience. TABLE 9.1 REQUIRED SIGN INFORMATION INFORMATION ON SIGN MINIMUM TEXT HEIGHT Road Work Next # Miles/Feet 2 1/2 inch Begin: Month, Day Year — End: Month, Day Year 2 inch Work includes: New Street, Utility Installation, Paving ... 1 inch Contractor: Contact Name, Phone Number, Company Name 1 inch Engineer: Contact Name, Phone Number, Company Name 1 inch Developer: Contact Name, Phone Number, Company Name 1 inch Thank you for your patience. 2 inch 9.7.2 NOTICES OF UTILITY SHUTDOWN AND ACCESS LIMITATIONS Affected residents and businesses are to be notified at least 24 hours in advance of when their utilities (water, electricity, etc.) will be interrupted and/or when access will be limited. The notification shall include the duration of the interruption. The Contractor shall provide written notification and hand deliver the notification to the affected residents and businesses. The Contractor shall provide a copy of the notification and a list of the citizens/businesses notified to the Development Inspector. This information shall be included in the weekly reports. 9.7.3 NOTICES FOR INSPECTION The Contractor shall inform the Development Inspector at least 24 hours in advance of paving operations or installation of drywells. At least 72Seventy two hours notice is required for work performed during the weekend or on Monday. It is the Updated January 2017 9-5 Chapter 9- Inspection & Certification 1 CITY OF SPOKANE VALLEY STREET STANDARDS responsibility of the Contractor to coordinate with the On-site Inspector for all required inspections and required testing. Development Engineering will not accept any improvements failing to meet the minimum number of required tests or failing to meet the required test results. 9.8 FIELD AND LAB TESTING 9.8.1 REPORTING The On-site Inspector shall prepare weekly project summary reports. All lab and field-testing reports shall be included in these weekly reports and in final certification packages. Test reports that show failing tests shall have follow-up test reports that show passing tests for the area of failure. On-site samples shall be used for testing. Any nonconforming issues shall be fully recorded with subsequent documents detailing how the issue was corrected. 9.8.2 MINIMUM MATERIAL TESTING FREQUENCIES Material testing is required as specified in Appendix 9-A. The frequency of testing may be increased at the discretion of the On-site Inspector or the Development Inspector. Any known site soil special areas of concern shall be addressed with increased testing frequencies based on sound engineering judgment. Wet weather conditions may also require additional testing frequencies. The On-site Inspector shall coordinate the number of tests, locations, etc. with an approved materials lab. The Applicant shall be responsible for the testing and laboratory costs. Development Engineering will not accept any improvements failing to meet the minimum number of required tests or failing to meet the required test results. 9.8.3 FIELD TESTING AND LAB REQUIREMENTS A material supplier, the Applicant, or the Contractor may not perform testing for certification purposes. Field testing shall be conducted by personnel that is adequately trained, qualified, and certified in accordance with the applicable test specifications. Field testing and laboratories shall have a national recognized accreditation, for the field and lab tests performed by the firm, such as AASHTO, Washington Association of Building Officials (WABO), American Association of Laboratory Accreditation (A2LA), etc. The entity in charge of field testing and the laboratory shall submit copies of their accreditation to the On-site Inspector so this information can be included in the certification package. 9.9 REQUIRED INSPECTIONS The On-site Inspector is required to certify the inspection of the following (See Appendix 9-B for required testing frequency): Updated January 2017 9-6 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS a. Placement and maintenance of erosion control. A site log shall be completed for the project; b. Embankment placement and density control; c. Trenching backfill and density control; d. Inspection and testing during pipe installation and pipe zone material placement (see Section 9.8.1 for additional information); e. Subgrade line and grade/density control; f. HMA surfacing line and grade/density control (see Section 9.8.3 for additional information); g. Installation of drainage improvements and any required testing; h. Installation of curb and gutter and material quality; and, i. Installation of sidewalks and material quality. 9.9.1 EROSION AND SEDIMENT INSPECTIONS A site log shall be completed for the project. The site log shall include the results of all site inspections, sampling as applicable and other records. For sites one acre or larger, inspections must be conducted by a Certified Erosion and Sediment Control Lead (CESCL) (See Appendix 9-D). 9.9.2 UTILITY INSPECTIONS Utility work shall be in accordance with Spokane County Interim Policy Regarding Sewer Construction Inspections, Record Drawings & Engineer's Statement and Spokane County Division of Utilities Protocol for Television Inspection of Sewers. Whenever pipe installation or pipe zone material placement and compaction are underway, the On-site Inspector shall observe the work on a continual basis. 9.9.3 HMA INSPECTIONS The On-site Inspector shall be present at all times during paving operations. 9.9.4 DRAINAGE STRUCTURE INSPECTIONS The On-site Inspector shall be present at all times during the installation of pipe, pipe zone material, drywells (including the geotextile and drainrock surrounding the drywell barrel), catch basins, and other drainage structures or facilities. 9.9.5 DRAINAGE SWALE AND DRAINAGE FACILITIES INSPECTIONS The On-site Inspector shall verify that the volume of each finished drainage swale equals or exceeds the design volume of the swale at a 6 -inch and 1 -foot depth. Additionally, the On-site Inspector shall verify that there is adequate and continuous grade from the street to the swale for the effective conveyance of runoff. If these items are deficient, the On-site Inspector shall notify the Contractor and/or Applicant's Engineer to determine a solution. Elevation sensitive aspects of Updated January 2017 9-7 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS installed materials, such as drywell rims, etc., shall be verified as being within normal industry tolerances (i.e., drywell rim elevations +/- 5/100'). At the discretion of the City, a test of the facility may be conducted to demonstrate adequate performance. The test shall be performed in the presence of the On-site Inspector and Development Inspector. All aspects of the drainage facility, including landscaping, irrigation, and establishment of specified vegetation, shall be completed in accordance with the accepted plans. An exception may be granted for single-family or two-family residential subdivisions where the completion of the swales is not practical until such time as the dwellings are constructed. In these cases, the Applicant shall rough -grade the swales to the required volume, install all drywells, inlets, and curb drops and other structures in accordance with the accepted plans. If the driveway approach width is greater than the width shown in the lot plans, engineering calculations shall be submitted that demonstrate that treatment and storage requirements are met. Erosion control measures shall be implemented to protect the installed drainage structures and to prevent erosion and/or failure of the swale side slopes. This includes, but is not limited to, lining the swale with geo-fabric that can be removed along with accumulated silt, until the swale is final -graded and vegetated. Completion of the landscaping, irrigation, and establishment of specified vegetation shall be required prior to issuance of the final Certificate of Occupancy or final inspection for any associated dwelling. For single and two-family dwellings, it shall be the responsibility of the Builder to satisfy these requirements. Acceptance of performance sureties, in lieu of establishing the vegetation, shall be permitted only when completion of improvements prior to final land action or permanent Certificate of Occupancy is impractical because of cold weather not suitable for the establishment of vegetation. 9.9.6 SWALE INSPECTION DURING WARRANTY PERIOD The Applicant's Engineer and the Development Inspector shall monitor performance of swales during the construction and warranty periods for proper percolation. Swales that do not percolate properly shall require corrective work or measures and are the financial responsibility of the Applicant. 9.10 MISCELLANEOUS 9.10.1 CHANGES DURING CONSTRUCTION Changes during construction that affect the scope of the project and/or the accepted individual lot plans shall be submitted for review by the City. The Development Inspector will determine if the change is significant. Minor changes do not require City review, but shall be discussed with the Development Inspector and documented in the daily and weekly inspection reports. Updated January 2017 9-8 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS The Development Inspector shall review and approve any significant field changes to the design plans and permits that have prior approval. Review and acceptance of any changes to approved plans for utility, site improvements and street right-of- way work shall require the oversight of both the utility operator as well as the Development Inspector. 9.10.2 CONSTRUCTION COMPLAINTS Complaints from citizens regarding the project shall be documented and shared with the Development Inspector and resolved by the Applicant. On more significant or high profile projects, the City may assign a City staff memberPublic Information Officer to notify the public of the project schedule and provide weekly up -dates (See Section 9.6). 9.10.3 CONFLICT RESOLUTION During the construction process, occasional differences may arise between the Applicant's Engineer and/or Contractor and City staff regarding interpretation of policies, standards or guidance documents. When the Applicant's Engineer or Contractor does not agree with an interpretation made by City staff, the Applicant's Engineer may appeal to the ` - - :: -• - • _ - _• ity Engineer as appropriate. The determination by the Development Services SeniorCity Engineer shall bels final. 9.11 FINAL WALK-THROUGH When requested by the Applicant, the On-site Inspector and Contractor shall prepare a punch list. When the punch list items have been addressed, the Applicant shall schedule a final walk-through with the Development Inspector. If no deficiencies are found, the On-site Inspector shall then prepare a certification package in accordance with Section 9.13. If deficiencies are found, another final walk-through with the Development Inspector is required. The Applicant shall continues to be responsible for correction of all deficiencies until the City accepts the project unless as noted in Section 9.14. It is suggested that the Applicant should consider taking verification photographs immediately following the final walk-through. Verification photographs maycan be helpful in resolving cases of damage by third parties (utility companies, builders, landscapers). 9.12 RECORD DRAWINGS All construction changes shall be recorded on a set of approved plans with the original approval stamp from the City. After the final walk-through, the Applicant's Engineer or On-site Inspector shall prepare record drawings for the project. Record drawings shall be stamped and have a signed certification statement saying: "I have reviewed the construction and to my knowledge I find it to be in conformance with the approved plans except as noted". Updated January 2017 9-9 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS Changes from the originally accepted documents shall be clearly noted with "clouds" on the approved plans and changes shall be noted in the revision block. Revised notes, elevations, grades or other text shall be lined through. Clean new sheets are not desired. Any changes to easements shall be clearly shown on the record drawings. Record drawings shall be marked "Record Drawings." If a change represents a deviation from the design intent or system performance in the judgment of the Applicant's Engineer, then it shall be clearly shown. It is recommended that Sspot elevations (on swales, curb, gutter, etc.) to depict final grades should be taken and compared with the final design. Differences shall be noted on the record drawings. Significant changes shall be coordinated with the Applicant's Engineer. Elements of the plans that were not built shall have a design change acceptance from the City prior to final inspection and submittal of record drawings. 9.13 PROJECT CERTIFICATION The On-site Inspector shall prepare a certification package for the project. The package shall include- a. Certification letter from Engineer with stamp; b. Weekly reports; c. Material test reports; d. A summary of the test results, including a discussion of how they compare to required specification; e. The certification checklist (Appendix 9-B); f. Erosion and Sediment Control Logs (Appendix 9-D); g. Truck tickets; h. All related construction documents including correspondence and communication records; i. Copies of the required accreditation for the field testing staff and testing laboratory in accordance with Section 9.8.3; j. Copies of drywell registrations; and, k. One set of r record drawings_; and, One paper copy of the stamped Mylar. The City of Spokane Valley will review the certification package within a two -_weeks period and shall notify the Applicant if the project is accepted to go to warranty. This Notice of Substantial Completion is conditioned upon no further deficiencies being discoveredbecoming evident before the City accepts the project. Upon notification that the project is provisionally accepted and upon receipt of the warranty surety, the warranty period shall begin. Updated January 2017 9-10 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS 9.13.1 CERTIFICATION OF DRAINAGE FACILITIES Stormwater facilities located in tracts shall be certified prior to final plat approval for plats, short plats and binding site plans. The certification of stormwater facilities located within border easements and rights-of-way for single-family and two-family dwellings may be delayed until the issuance of the final Certificate of Occupancy (Refer to Section 9.9.5). Drainage facilities associated with a commercial building permit shall be certified, as specified in Section 9.13, prior to issuing a final Certificate of Occupancy. 9.14 PERFORMANCE SURETY 9.14.1 PERFORMANCE SURETY AUTHORIZED Except as otherwise provided in section 9.14, Applicants shall complete all plan improvements prior to approval of the final plat, short plat, binding site plan or any phase thereof, the issuance of any Certificate of Occupancy (commercial, residential, or otherwise), or performance of a final inspection. The City may authorize the use of performance surety solely in conformance with and pursuant to the provisions of section 9.14. 9.14.2 PERFORMANCE SURETY CRITERIA (A) A performance surety in lieu of construction of one or more required plan improvements may only be accepted by the City if: (1) The required construction cannot be completed due to situations out of human control such as adverse weather, inability to acquire construction materials or other unforeseen complications; (2) The Applicant submits a completion schedule and the schedule is approved by the City. Non -landscaping items shall be completed no later than nine months after the effective date of the performance surety or July 31st of the following year, whichever is earlier. Completion of landscaping items shall be completed no later than 18 months after the effective date of the performance surety; (3) Required plan improvements have been made that are sufficiently complete as to allow the needed proper function and operation of the transportation, sewer, water, and stormwater systems, as determined by the City; (4) All-weather driving surfaces approved by the Fire Department are constructed to all locations of flammables before flammables brought on site; and (5) The Applicant has no other outstanding project improvements within the City that have been deemed by the City to be untimely, in bad faith, unsatisfactory, or incomplete and the Applicant has provided an acceptable performance surety covering all such outstanding improvements. Updated January 2017 9-11 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS (B) All performance sureties shall be in an amount of 125% percent of the estimated construction cost for all outstanding required plan improvements for the project that are covered by the performance surety. Performance sureties shall be a letter of credit or cash savings assignment substantially in the form of the City's draft performance surety. The City shall maintain a current acceptable draft form of performance surety. Performance bonds are not allowed as acceptable performance sureties. The Applicant's Engineer or designer of record shall submit quantities for the complete nature of the work to be performed. The Development Inspector shall enter that information into an updated calculation spreadsheet to determine the performance surety amount. Performance surety amounts shall include all construction costs, including erosion and sediment control, critical area mitigations and inspection costs. Note, items such as granting of easements and dedications of right-of-way shall not be covered by a performance surety. 9.14.3 PERFORMANCE SURETY RELEASE The performance surety shall be released when all of the following conditions have been met: (A) A certification package is accepted by the City; (B) The Applicant has paid in full all costs incurred by the City; (C) All monuments have been reset and referenced by a surveyor; and, (D) The Applicant has submitted a warranty surety for improvements in the public right-of-way and border easements as specified in Section 9.15. 9.15 WARRANTY SURETY All projects with improvements in the public rights-of-way or border easements shall submit to the City a warranty surety. The warranty surety shall guarantee against material and/or workmanship defects in street construction, in utility work within the rights-of-way and border easements, and/or in drainage facilities as required by the City. As required by the -The warranty surety shall guarantee against damages to street infrastructure and drainage facilities. 9.15.1 WARRANTY SURETY AMOUNT The Applicant's Engineer shall submit quantities for the complete nature of the work to be performed within or on the rights-of-way, border easements, or on the frontage of the City rights-of-way. The Development Inspector shall enter that information into an updated calculation spreadsheet reflecting a total valuation of the work to be performed. The Development Inspector shall then calculate 20% percent of that total work to be performed and request a warranty surety for that amount from the Applicant. 9.15.2 ACCEPTABLE SURETIES The warranty surety shall be based on the total warranty amount required for the project as set forth in section 9.15.1. Warranty sureties shall be in the form of a Updated January 2017 9-12 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS letter of credit, cash savings assignment, or bond substantially in the form of the City's draft warranty surety. The City shall maintain current acceptable draft forms of warranty sureties. 9.15.3 WARRANTY DURATION A warranty surety shall remain in effect for two years from the date the City provisionally accepts the streets. At least 30Thirty days prior to the expiration of the warranty, the Applicant shall retain an Engineer to inspect the improvements. Any deficiencies noted shall be repaired prior to the release of the surety. If the inspection is not conducted and the deficiencies are not repaired, the warranty surety shall be renewed by the Applicant until this requirement is satisfied. The Development Inspector shallwill conduct a walk-through prior to releasing the warranty surety. 9.15.4 TIME FRAMES TO COMPLETE REPAIR The warranty surety shall be used to correct deficiencies due to materials and/or workmanship. At any time before the end of the warranty period, the City may notify the Applicant of needed repairs. If repairs are considered to be an imminent danger to the public's health, safety, and welfare, the Applicant shall act within 24 hours to complete the repair. If the work is not considered a safety issue, the Applicant shall havehas 10 business days to schedule the work, and 60 calendar days to complete the work. Extensions of time may be considered when necessary due to weather constraints. When the Applicant's project is accepted and in warranty, or after releasing the warranty surety, the Builder shall bei -s responsible for any damage to the improvements along the lot frontagcresulting from their project including the construction, operation or maintenance of their project. Any deficiencies shall be corrected by the Builder prior to the final inspection of their project or the issuance of the final Certificate of Occupancy for the structure. 9.15.5 FAILURE TO COMPLETE REPAIR If the warranty repairs are not completed in the time frame specified, the City may choose to conduct the necessary repairs. The City mays either invoice the Applicant or collect from the surety for all costs for the related work, plus a $50040 administrative fee. 9.15.6 RESPONSIBILITY FOR MAINTENANCE The Applicant shall bei -s responsible for maintaining all public improvements, excluding snow plowing, throughout the warranty period. 9.16 STREET ESTABLISHMENT When the project has been certified and accepted, the Applicant maycan request to receive provisional acceptance after posting a warranty surety pursuant toin accordance with Section 9.14. The Applicant shall bei -s responsible to repair failures during the warranty Updated January 2017 9-13 Chapter 9- Inspection & Certification 1 CITY OF SPOKANE VALLEY STREET STANDARDS period pursuant toin accordance with Section 9.15.4. Final acceptance shall be granted after the warranty period assuming all deficiencies have been corrected. The City Manager is responsible for approving the establishment of new streets. When the project receives final acceptance, the Development Services SeniorCity Engineer shall recommend to the City Manager that the streets be established. Updated January 2017 9-14 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS Appendix 9-A Appendix 9-B Appendix 9-C Appendix 9-D APPENDIX INDEX - Minimum Material Testing Frequencies - Final Certification Checklist — Sample - Removed - Erosion and Sediment Control Log Updated January 2017 9-15 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS APPENDIX 9-A — Minimum Material Testing Frequencies The following testing frequencies represent the minimum requirements during construction. If individual tests fail to meet specifications, additional testing shall be conducted to assure conformance. Earth Embankment Road Subgrade Crushed Rock 1 density test per lift per 500 CY placed 1 density test per 100 LF of lane or equivalent 1 density test per 100 LF of lane or equivalent per lift Trench Embankment 1 density test per 150 CY with varying test depths Crushed Rock under Curb and Sidewalks Concrete for Curbs and Sidewalks Aggregate Quality Asphalt Pavement 1 density test per 100 LF of curb of walk length per lift(Unless tested as part of the roadway crushed rock) 1 set (4 cylinders) per 100 CY (Minimum 1 set per day) 1 set of air, slump, temperature, etc. on first truck and with cylinders thereafter 1 gradation test 1 sand equivalent test 1 fractured face test 1 Lot = 400 tons 5 random density tests per lot (Minimum 5 tests per day) 1 test to verify gradation per 1,000 tons (Minimum 1 test per day) 1 test to verify asphalt content per 1,000 tons (Minimum 1 test per day) 1 test to verify maximum density per 1,000 tons (Minimum 1 test per day) Updated January 2017 9-16 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS APPENDIX 9-B — Final Certification Checklist (Sample) Project: Certification Letter: Statement of intent to certify the project. PE Stamp and Signature. Record Drawings Mylar Drawings: PE Stamp and Signature Lettered certification statement (Section 9.12) Project Documents: Daily Inspection Reports: Field Reports: Inspection of Asphalt Paving: 100% On site inspection during paving Compaction Reports: Sewer trench lifts. Water trench lifts. Utility trench lifts. Crushed Rock lifts. Material Documents: Field and Laboratory Tests: Field Concrete Subgrade: Crushed Rock Asphalt Test (Slump, Air Content, Temp). (Compaction) (Compaction, Depth) (Compaction, Thickness) Lab Test On Site Inspections of Drainage Items: Drywells: Gutter Inlets: Culverts: Sidewalk Vaults: Drainage Ditches: (Break Test) (Gradation, Proctor) (Gradation, Proctor) (Rice, Gradation, Oil Content) Other: Incoming/Outgoing Correspondence Updated January 2017 9-17 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS APPENDIX 9-C — Removed APPENDIX 9-D — EROSION AND SEDIMENT CONTROL LOG The following items are to be included in the daily logs and inspection reports to assure conformance: a. Date of Inspection. b. When, where and how the BMPs were installed, removed or modified. c. Repairs needed or made. d. Observations of BMP effectiveness and proper placement. e. Recommendations for improving performance of BMPs. f. Identify the points where stormwater runoff potentially leaves the site, is collected in a surface water conveyance system, (i.e., road ditch, storm sewer), and enters receiving waters of the state. g. If water sheet flows from the site, identify the point at which it becomes concentrated in a collection system. h. Inspect for SWPPP requirements including BMPs as required to ensure adequacy. Updated January 2017 9-18 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE LEFT INTENTIONALLY BLANK Updated January 2017 9-19 Chapter 9- Inspection & Certification CITY OF SPOKANE VALLEY STREET STANDARDS CHAPTER 10 - MAINTENANCE Chapter Organization 10.1 Introduction 1 10.2 Maintenance Responsibility 1 10.2.1 Public Streets 1 10.2.2 Private Streets and Driveways 1 10.3 Required Documents 2 10.3.1 Homeowners' and Property Owners' Associations 2 10.3.2 Operation and Maintenance Manual 2 10.3.3 Financial Plan 3 10.3.4 Conversion from Private to Public Street 3 Adopted December 2009 Chapter 10 — Maintenance 10-i CITY OF SPOKANE VALLEY STREET STANDARDS THIS PAGE IS INTENTIONALLY LEFT BLANK Ad pted December 2009 Chapter 10 — Maintenance 10 -ii CITY OF SPOKANE VALLEY STREET STANDARDS 10.1 INTRODUCTION This chapter establishes the parties responsible to maintain the public and private infrastructure created with development. In addition, it provides a list of documents required to be submitted during project review. 10.2 MAINTENANCE RESPONSIBILITY 10.2.1 PUBLIC STREETS Upon releasing the warranty surety and acceptance of the public infrastructure, the City maintains all public streets (curb, gutter, and pavement) and public stormwater drainage structures (drywells, inlets and pipes) located within the public rights-of- way and within border easements that serve public street runoff. The City does is not responsible for maintainmaintenance of sidewalks or landscaping of swales and grass strips, even if located within the public right-of- way or border easements. Property owners are responsible for the maintenance of these features as described below. Swale maintenance means includes preservation of the original area, volume, configuration and function of the stormwater facility as described in the approved plans. Swale maintenance also includes mowing, irrigating, and replacing when necessary the lawn turf within the swales. The pProperty owners are also responsible for maintaining sidewalks free of obstructions and debris, including snow and ice. If the property owners fail to maintain said facilities, the City shall give a notice of such failure to the property owners. If not corrected within the period indicated on said notice, the City has the right to correct the maintenance failure, or have it corrected, at the expense of the property owners. 10.2.2 PRIVATE STREETS AND DRIVEWAYS The City docs is not responsible for maintainmaintenance of any of the infrastructures located on private streets or private driveways infrastructure. Private streets and driveways and related facilities shall be contained within a permanently established tract or easement providing legal access to each lot served. The Applicant shall provide arrangements for the perpetual maintenance of the private streets, private driveways and all elements of the stormwater system (including swales within the right-of-way and border easements), and any other related facilities. The City docs shall not furnish, install, or maintain signs for private streets including stop signs or street name signs for private streets intersecting public streets or "No Parking" signs. The owner may install their own sSigns shall be in accordance with MUTCD. Installation of signs at intersections with public streets require , but must have approval from the Seniorathe City Traffic Engineer_ when Access shall be granted to the City to provide emergency maintenance of private facilities. The cost of emergency maintenance shall be the responsibility of the property owners or the Homeowners' Association in charge of maintenance. December 2009 Chapter 10 - Maintenance 10-1 CITY OF SPOKANE VALLEY STREET STANDARDS 10.3 REQUIRED DOCUMENTS The following maintenance -related items shall be submitted for all projects with private streets and/or common areas: a. A copy of the conditions, covenants and restrictions (CC&Rs) for the homeowners' association (HOA) or property owners' association (POA) in charge of operating and maintaining all elements of the private street system (see Section 10.3.1); b. An operations and maintenance (O&M) manual (see Section 10.3.2); c. A financial plan outlining the funding mechanism for the operation, maintenance, repair, and replacement of the private street system, related facilities and/or common areas (see Section 10.3.3); d. Street maintenance agreements, as applicable; e. Reciprocal use agreements, as applicable; and, f. Drainage easements, as applicable. Refer to the Spokane Regional Stormwater Manual for maintenance requirements for stormwater facilities. 10.3.1 HOMEOWNERS' AND PROPERTY OWNERS' ASSOCIATIONS An HOA shall be formed to maintain the private streets, signs, entrance gates, other related facilities and/or common areas. For commercial/industrial and multi -family residential developments with shared access and multiple owners, a POA or similar entity shall be formed, or a reciprocal -use agreement executed. If the HOA or POA has CC&Rs, a draft copy of the CC&Rs for the HOA or POA shall be submitted with the civil and drainage plans. The CC&Rs shall summarize the maintenance and fiscal responsibilities of the HOA or POA, refer to the O&M Manual, and include a copy of the sinking fund calculations and Financial Plan. Annual HOA or POA dues shall provide funding for the annual operation and maintenance of private streets, private driveways, related facilities, and common areas. The sinking fund calculations shall also include costs for the maintenance of the stormwater system and all facilities associated with the stormwater system (Refer to Chapter 11 of the Spokane Regional Stormwater Manual). Homeowners' associations and property owners' associations arc to shall be non- profit organizations accepted by the Washington Secretary of State. A standard business license is not acceptable for this purpose. 10.3.2 OPERATION AND MAINTENANCE MANUAL All projects with private streets and/or common areas used for stormwater management shall have an O&M Manual. Projects with engineered driveways may also be required to submit an O&M Manual. The O&M Manual must shall include, at a minimum: a. Description of the entity responsible for the perpetual maintenance, including legal means of successorship; December 2009 Chapter 10 - Maintenance 10-2 CITY OF SPOKANE VALLEY STREET STANDARDS b. Description of street maintenance tasks to be performed and their frequency. Street maintenance tasks shall include at a minimum street sweeping, snow plowing, signage repair, crack sealing, pot hole repair, overlay, pavement replacement, etc.; c. Description of the stormwater maintenance tasks to be performed and their frequency. Tasks shall include, at a minimum, swale maintenance and removing sediment from drywells, catchbasins, and pipe system. Swale maintenance means preservation of the original area, volume, configuration and function of the stormwater facility as described in the plans. Swale maintenance also includes mowing, irrigating, and replacing when necessary the lawn turf within the swales; d. Description of emergency maintenance tasks to be performed and their frequency, such as gate operation, "No Parking" signs, access to fire hydrants, fire lanes; e. Description of the source control best management practices (BMPs) such as street sweeping (refer to Chapter 10 of the Spokane Regional Stormwater Manual); f. A list of the expected design life and replacement schedule of each component of the private street and/or stormwater management system; A general site plan (drawn to scale) showing the overall layout of the site; and; h. Contact information for the Edesign engineer. 10.3.3 FINANCIAL PLAN g. To provide guidance regarding financial planning for maintenance and replacement costs, a Financial Plan is required. The Financial Plan shall include the following items: a. A list of all private streets and related facilities, common areas, and/or stormwater management facilities, expected maintenance activities and associated costs; b. Sinking fund calculations that take into consideration probable inflation over the life of the infrastructure and estimates for the funds needed to be set aside annually; and, c. A mechanism for initiating and sustaining the sinking fund account demonstrating that perpetual maintenance will be sustained. 10.3.4 CONVERSION FROM PRIVATE TO PUBLIC STREET The Applicant shall submit written authorization from all property owners, any and all available construction drawings of the subject street, along with an engineer - stamped analysis of the pavement and subgrade as determined from test sites separated no greater than 100 feet apart, or as required by the City. Digital photos at every 50 feet, or as the City requires, shall be submitted with the application. December 2009 Chapter 10 - Maintenance 10-3 CITY OF SPOKANE VALLEY STREET STANDARDS The City shall review the information, visually check the street and determine requirements to bring the street up to current City standards. A letter of requirements shall be issued by the City. The Applicant(s) shall meet the requirements before the street is accepted as a public right-of-way. The Applicant shall prepare a legal description of the street and execute a deed of trust, transferring the property to the City once the physical deficiencies have been corrected and accepted. December 2009 Chapter 10 - Maintenance 10-4 FINDINGS AND RECOMMENDATIONS OF THE SPOKANE VALLEY PLANNING COMMISSION FOR CTA -2017-0004 January 25, 2018 The following findings are consistent with the Planning Commission's decision to recommend approval. Background: 1. The City of Spokane Valley interim development regulations were adopted on March 25, 2003 (Ordinance No. 53). These included the Spokane County Road Standards. In December, 2009 the City adopted Ordinance 09-033- City of Spokane Valley Street Standards. Chapter 11 Standard Plans were updated in January, 2016 and Chapter 9 Surety Requirements were updated as part of the Comprehensive Plan in December, 2016 by the adoption of Ordinance 16-018. 2. CTA -2017-0004 is a City initiated text amendment to amend Spokane Valley Municipal Code (SVMC) to modify SVMC 20.80 and 22.130 to remove references to Future Acquisition Areas, update Chapter 3 — Traffic Analysis to provide guidance on traffic requirements for SEPA infill areas, update Chapter 10 — Maintenance to address Federal Highway Administration (FHWA) comments on the maintenance of sidewalks, and perform minor changes to most chapters in the Street Standards to reflect reorganization and revisions to implementation. 3. The Planning Commission held a public hearing and conducted deliberations on January 11, 2018. The Planning Commission voted 6-0 to recommend approval as modified to City Council. Planning Commission Findings: 1. Recommended Modifications The Planning Commission recommended the following modifications and/or additional requirements to CTA -2017-0004: a. Modify SVMC 22.130 to replace references to "development services senior engineer" with "City Manager or designee". b. Modify Section 1.3.2 bullet 3 as follows: To ensure public facilities and services meet level of service standards as adopted established in the adopted Comprehensive Plan. c. Modify Section 10.2.1 paragraph two sentence two as follows: Property owners are responsible for the maintenance of these features as described below. 2. Compliance with SVMC 17.80.150(F) Approval Criteria a. The proposed text amendment is consistent with the applicable provisions of the Comprehensive Plan. Findings(s): i. Land Use Policy - 8: Ensure that neighborhoods are served by safe and convenient motorized and non -motorized transportation routes. ii. Transportation Policy - 9: Provide and maintain quality street, sidewalk, and shared -use path surfaces that provide a safe environment for all users. iii. Capital Facilities Policy - 3: Coordinate the construction of public infrastructure with private development to minimize costs. Findings and Recommendations of the Spokane Valley Planning Commission CTA -2017-0004 Page 1 of 2 Finding(s): The proposed amendment bears a substantial relation to public health, safety, welfare and protection of the environment 3. Conclusion(s): a. The proposed text amendment is consistent with the City's adopted Comprehensive Plan and the approval criteria contained in SVMC 17.80.150(F). b. The Growth Management Act requires that the comprehensive land use plan and development regulations shall be subject to continuing review and evaluation by the City. Recommendations: The Spokane Valley Planning Commission therefore recommends the City Council approve CTA -2017- 0004 with modifications specified above. Approved this 25th day of January, 2018 Michelle Rasmussen, Chair ATTEST Deanna Horton, Administrative Assistant Findings and Recommendations of the Spokane Valley Planning Commission CTA -2017-0004 Page 2 of 2 Spok ii u'► .001Talley CITY OF SPOKANE VALLEY COMMUNITY & PUBLIC WORKS DEPARTMENT PLANNING DIVISION STAFF REPORT AND RECOMMENDATION TO THE PLANNING COMMISSION CTA -2017-0004 STAFF REPORT DATE: January 2, 2018 HEARING DATE AND LOCATION: January 11, 2018, beginning at 6:00 p.m., Spokane Valley City Hall Council Chambers, 10210 East Sprague Avenue, Spokane Valley, Washington 99206. PROPOSAL DESCRIPTION: A City initiated code text amendment to the Spokane Valley Municipal Code (SVMC) to make minor revisions to the Street Standards to address changes in responsibilities due to the City re -organization and in implementation of the standards, Federal Highway Administration (FHWA) comments on maintenance of sidewalks; traffic requirements for SEPA infill areas and to revise Chapter 20.80 Boundary Line Adjustments/Eliminations and Chapter 22.130 Development Transportation Improvements to remove references to Future Acquisition Areas. APPROVAL CRITERIA: Spokane Valley Comprehensive Plan, Spokane Valley Municipal Code (SVMC) Title 17 General Provisions, and SVMC 19.30.040 Development regulation text amendments. SUMMARY OF RECOMMENDATION: Staff recommends approval of the code text amendment. STAFF PLANNER: Micki Harnois, Planner; Henry Allen, Senior Engineer ATTACHMENTS: Exhibit 1: Proposed code text amendments to SVMC Chapter 3 Exhibit 2: Proposed code text amendments to SVMC 20.80 Exhibit 3: Proposed code text amendments to SVMC 22.130 BACKGROUND INFORMATION 1. APPLICATION PROCESSING: SVMC Chapter 17.80, Permit Processing Procedures. The following summarizes application procedures for the proposal. Process Date SEPA Review The proposal consists of changes that are procedural in nature and are considered exempt under WAC 197-11- 800(19)(a) and (b) N/A Staff Report and Recommendation CTA -2017-0004 Process Date Published Notice of Public Hearing December 15, 2017 and December 22, 2017 Sent Notice of Public Hearing to staff/agencies: December 22, 2017 2. PROPOSAL BACKGROUND: On March 25, 2003 the City of Spokane Valley City Council approved Ordinance No. 53 adopting the City's first interim development regulations which were portions of the Spokane County Zoning Code. This included the Spokane County Road Standards. In December, 2009 the City adopted Ordinance 09-033 City of Spokane Valley Street Standards. Chapter 11 Standard Plans were updated in January, 2016 and Chapter 9 Surety Requirements were updated as part of the Comprehensive Plan in December, 2016 by the adoption of Ordinance 16-018. Since then the City has undergone a reorganization and changes to its implementation of the street standards. Recently the FHWA requested revisions to the street standards providing the City with authority to maintain sidewalks. Staff was also sent draft regulations for review and their comments are incorporated in the draft. While addressing the additional FHWA comments, the City decided to update the SVMC and street standard documents to reflect changes from the reorganization and implementation. Specific revisions include: • Addition of Limited Traffic Impact Analysis (TIA) to provide guidance on traffic requirements for SEPA Infill areas. • SVMC Title 20 Subdivision Regulations -Chapter 20.80 Boundary Line Adjustments/Eliminations— remove references to Future Acquisition Areas. • SVMC Title 22 Design and Development Standards Chapter 22.130 Development Transportation Improvements— remove references to Future Acquisition Areas. • Minor changes to most chapters to reflect reorganization (e.g. now authority is City Engineer) • Revisions to implementation (e.g. eliminating variance process, FAA and mylar record drawings; proposed streets not required to connect to future development) FINDINGS AND CONCLUSIONS SPECIFIC TO THE MUNICIPAL CODE TEXT AMENDMENT 1. Compliance with Title 17 (General Provisions) of the Spokane Valley Municipal Code a. Findings: SVMC 17.80.150(F) Municipal Code Text Amendment Approval Criteria i. The City may approve Municipal Code Text amendment, if it finds that (1) The proposed text amendment is consistent with the applicable provisions of the Comprehensive Plan; Staff Analysis: The proposed amendment is consistent with the applicable goals and policies of the Comprehensive Plan. The amendment will allow reasonable opportunity for infrastructure development activities while protecting the character of the neighborhood and ensures that the development is compatible by allowing flexible decisions. Page 2 of 3 Staff Report and Recommendation CTA -2017-0004 Relevant Comprehensive Plan goals and policies are shown below: Land Use Policy — 8 Ensure that neighborhoods are served by safe and convenient motorized and non -motorized transportation routes. Transportation Policy -9 Provide and maintain quality street, sidewalk, and shared - use path surfaces that provide a safe environment for all users. Capital Facilities Policy — 3 Coordinate the construction of public infrastructure with private development to minimize costs. (2) The proposed amendment bears a substantial relation to public health, safety, welfare, and protection of the environment; Staff Analysis: The proposed amendment establishes standards that will reasonably protect neighborhoods from adverse impacts of transportation uses as well as ensure the property owner is responsible for maintaining sidewalks for safety purposes. The City will also have the ability to charge a fine for those who do not maintain the sidewalks. b. Conclusion(s): The proposed text amendment is consistent with the approval criteria contained in the SVMC. 2. Finding and Conclusions Specific to Public Comments a. Findings: No public comments have been received to date. b. Conclusion(s): Adequate public noticing was completed for CTA -2017-0004 consistent with adopted public noticing procedures. 3. Finding and Conclusions Specific to Agency Comments a. Findings: The draft regulations were sent to staff for their review. b. Conclusion(s): The suggested revisions are incorporated in the draft regulations. A. OVERALL CONCLUSION The proposed amendment is consistent with the applicable goals and policies of the Comprehensive Plan. The amendment will allow reasonable opportunity for infrastructure development activities while protecting the character of the neighborhood. The proposed amendment sets standards that will protect neighborhoods from the impacts of traffic and the maintenance of sidewalks. Page 3 of 3 Street Standards Minor Update - Ordinancel8-oo3 Henry Allen, Senior Engineer Ray Wright, Senior Engineer/Traffic Street Standards Spokane Valley �nr�lz�ne Valley Adopted December 2009 Revised February 2018 Timeline ❖ City Council ■ Dec 5th - Admin Report + Planning Commission ■ Dec 14th 2017 — Study Session ■ Jan 11th 2018 — Public Hearing ■ Jan 25th 2018 — Findings of Fact ❖ City Council ■ Today: Feb 6th 2018 —1st Reading ■ Feb 27th 2018 — 2nd Reading About the Street Standards ❖ Chapter 35.78 RCW requires the adoption of uniform definitions and design standards for municipal streets and roads. ❖Street Standards provide requirements on the design, construction, operation and maintenance of streets. The Street Standards apply to new development, redevelopment and capital projects. ❖ Chapters include required improvements, traffic analysis, street elements, pavement design, inspection and certification and maintenance. 3 Street Standards History ❖ The Spokane County Road Standards were adopted when the City incorporated in 2003 ❖ The City of Spokane Valley Street Standards were adopted in December 2009 ❖ Minor revisions since initial adoption • The Standard Plans were updated in January 2016 • Surety Requirements in Ch. 9 were updated (to include bonds) as part of the Comprehensive Plan update in December 2016 4 This Revisi - Purpose ❖ Purpose ■ Address Federal Highway Administration (FHWA) comments on the Street Standards (specifically sidewalk maintenance in chapter 10.2.1) ■ Update Standards and Municipal Code to reflect reorganization and revisions to implementation •'•Compile a list of revisions for a future review of standards 5 This Revision - Details ❖ Street Standards ■ Minor changes to most chapters to reflect: ■ Reorganization ■ Revisions to implementation (e.g. eliminated Variance process, Future Acquisition Areas and mylar record drawings; proposed streets not required to connect to future development, frontage improvements only where project accesses street) ■ Chapter 3 Traffic Analysis implements traffic requirements for SEPA infill areas utilizing a Limited Traffic Impact Analysis (TIA) ■ Revisions to Chapter 10 (Maintenance) section to address FHWA comments ❖ Municipal Code ■ Revise SVMC chapters 20.80.010 and 22.130 to remove references to Future Acquisition Areas ■ Modification - revise SVMC chapter 22.130 to replace reference to development services senior engineer with City Manager or designee 6 Questions? CITY OF SPOKANE VALLEY Request for Council Action Meeting Date: February 6, 2018 Department Director Approval: Check all that apply: ❑ consent ❑ old business ® new business ❑ public hearing ❑ information ❑ admin. report ❑ pending legislation ❑ executive session AGENDA ITEM TITLE: First Reading Proposed Ordinance 18-004, amending SVMC 20.20 and SVMC Appendix A. GOVERNING LEGISLATION: SVMC 17.80.150; 19.30.040; and RCW 36.70A.106; RCW 58.17 PREVIOUS ACTION TAKEN: Administrative Report, January 30, 2018 BACKGROUND: CTA 2017-0003 is a text amendment to SVMC Chapter 20.20, General Provisions to address non -legal lots and innocent purchasers, eliminate inconsistencies with Title 19 resulting from the Development Regulations update in 2016, provide clarifications and minor grammatical changes, and modify the definition of flag lot in Appendix A. The draft regulations generally include: 1. Clarify and define what constitutes a "legal lot" in the City of Spokane Valley; add language to allow development on a non -legal lot by an "innocent purchaser"; 2. Set forth criteria for development on a non -legal lot; 3. Eliminate the additional width requirement for corner lots; 4. Eliminate the ratio of lot width to lot depth requirement; 5. Eliminate language that requires the arrangement of lots and streets in conformance with approved plans; 6. Modify the requirement for a minimum 15 foot border easement to allow the City to determine the required border easement or right-of-way width up to 15 feet maximum; and 7. Amend Appendix A by modifying the definition of a "flag" lot. The Planning Commission conducted a public hearing on December 14, 2017 to consider the amendments. Following the public hearing and deliberations, the Planning Commission voted 6-1 to recommend that the proposed code text amendment be approved with changes. On January 11, 2018, the Planning Commission approved the Findings of Fact and Recommendation to City Council. On January 30, 2018 staff provided an administrative report to City Council with Council consensus to move the amendment to a First Ordinance Reading. OPTIONS: Move to advance the ordinance to a second reading with or without further amendments; or take other action deemed appropriate. RECOMMENDED ACTION OR MOTION: Move to advance Ordinance 18-004 updating subdivision regulations, to a second reading. BUDGET/FINANCIAL IMPACTS: N/A STAFF CONTACT: Marty Palaniuk, Planner CTA -2017-0003 RCA for 1" Ordinance Reading page 1 ATTACHMENTS: A. Draft Ordinance 18-004 B. Planning Commission Findings and Recommendations C. Planning Commission Meeting Minutes 11/09/2017 D. Planning Commission Meeting Minutes 12/14/2017 E. Draft Planning Commission Meeting Minutes 1/11/2018 F. Staff Report CTA 2017-0003 G. PowerPoint Presentation H PowerPoint Presentation CTA -2017-0003 RCA for 1' Ordinance Reading page 2 DRAFT CITY OF SPOKANE VALLEY SPOKANE COUNTY, WASHINGTON ORDINANCE NO. 18-004 AN ORDINANCE OF THE CITY OF SPOKANE VALLEY, SPOKANE COUNTY, WASHINGTON AMENDING SPOKANE VALLEY MUNICIPAL CODE APPENDIX A RELATING TO FLAG LOTS; AMENDING SPOKANE VALLEY MUNICIPAL CODE CHAPTER 20.20 RELATED TO LEGAL LOTS, INNOCENT PURCHASERS, AND DOUBLE FRONTAGE LOTS; AND OTHER MATTERS RELATING THERETO. WHEREAS, the City of Spokane Valley (City) previously adopted Spokane Valley Municipal Code (SVMC) Title 20, relating to subdivision regulations, and has made subsequent amendments from time to time as appropriate; and WHEREAS, such regulations are authorized by RCW 36.70A; and WHEREAS, on November 9, 2017, the Planning Commission held a study session; and WHEREAS, on November 14, 2017, the Washington State Department of Commerce was notified pursuant to RCW 36.70A.106, providing a 60 -day notice of intent to adopt amendments to Spokane Valley development regulations; and WHEREAS, on November 24, 2017 and December 1, 2017, notice of the Planning Commission public hearing was published in the Valley News Herald; and WHEREAS, on December 14, 2017, the Planning Commission held a public hearing, received evidence, information, public testimony, and a staff report with a recommendation followed by deliberations; and WHEREAS, on January 11, 2018, the Planning Commission approved the findings and recommended that City Council adopt the amendments; and WHEREAS, on January 30, 2018, City Council reviewed the proposed amendments, Planning Commission findings, and Planning Commission recommendation. City Council determined it desired to consider adopting the amendments; and WHEREAS, the amendment set forth below is consistent with the goals and policies of the City's Comprehensive Plan; and WHEREAS, SVMC Appendix A and SVMC 20.20, as amended, bears a substantial relation to the public health, safety, welfare and protection of the environment. NOW, THEREFORE, the City Council of the City of Spokane Valley ordains as follows: Section 1. Purpose. The purpose of this Ordinance is to amend chapter 20.20 SVMC General Provisions to address illegal lots and innocent purchasers, eliminate inconsistencies with Title 19 resulting from the development regulations update in 2016, make clarifications and minor grammatical changes; and modify the definition of flag lot in Appendix A. Section 2. Findings and Conclusions. The City Council acknowledges that the Planning Commission conducted appropriate investigation and study, held a public hearing on the proposed amendments and recommends approval of the amendments. The City Council has read and considered the Planning Commission's findings. The City Council hereby makes the following findings: Ordinance 18-004 Page 1 of 9 DRAFT A. Growth Management Act Policies - Washington State Growth Management Act (GMA) provides that each city shall adopt a comprehensive land use plan and development regulations that are consistent with and implement the comprehensive plan. B. City of Spokane Valley Goals and Policies - The City of Spokane Valley has adopted goals and policies consistent with the GMA and adopted County -Wide Planning Policies, set forth below. Land Use Goal LUG -G1: Maintain and enhance the character and quality of life in Spokane Valley Land Use Goal LUG -G2: Provide for land uses that are essential to Spokane Valley residents, employees, and visitors. Land Use Goal LUG -G4: Ensure that land use plans, regulations, review processes, and infrastructure improvements support economic growth and vitality. C. Conclusions The proposed amendment bears a substantial relation to public health, safety, welfare, and protection of the environment. The proposed text amendment is consistent with the City's Comprehensive Plan and the approval criteria pursuant to SVMC 17.80.150(F). Section 3. Amendment. SVMC Appendix A is hereby amended as follows: Lot, double frontage: An interior lot with frontage on more than one street. Lot, flag: A lot of irregular shape with reduced frontage on a public or private street with dimensions which are otherwise adequate at the building line. Flag Lot: A lot with two distinct parts: a. A large portion of the lot which is the only building site; and is located behind another lot; and b. A strip of land which connects the flag to the street and provides the only street frontage for the lot. Ordinance 18-004 Page 2 of 9 DRAFT Lot, interior: A lot within a subdivision that is not located at the intersection of any adjacent public or private street. Section 4. Amendment. SVMC 20.20 hereby amended as follows: Chapter 20.20 GENERAL PROVISIONS Sections: 20.20.010 Purpose. 20.20.020 Exemptions. 20.20.030 Legal lot. 20.20.040 Approval required prior to recordation. 20.20.050 Prohibition against sale, lease or transfer of property. 20.20.060 Vertical datum. 20.20.070 Monumentation. 20.20.080 Professional land surveyor. 20.20.090 General design. 20.20.100 Findings. 20.20.110 Attached single-family subdivisions. 20.20.010 Purpose. Pursuant to the purposes set forth in RCW 58.17.010, these regulations in this title are necessary to: A. Promote the health, safety, and general welfare in accordance with standards established by the state and the City; B. Promote effective use of land by preventing the overcrowding or scattered development which would be detrimental to health, safety, or the general welfare due to the lack of water supplies, sanitary sewer, drainage, transportation, or other public services, or excessive expenditure of public funds for such services; C. Avoid congestion and promote safe and convenient travel by the public on streets and highways through the proper planning and coordination of new streets within subdivisions with existing and planned streets in the surrounding community; D. Provide for adequate light and air; E. Provide for adequate water, sewage, drainage, parks and recreational areas, sites for schools and school grounds, and other public requirements; F. Provide for proper ingress and egress; G. Provide for housing and commercial needs of the community; H. Require uniform monumentation of land divisions and conveyance of accurate legal descriptions; I. Protect environmentally sensitive areas; J. Provide for flexibility in site design to accommodate view enhancement and protection, protection of streams and wetlands, protection of steep slopes, and other environmentally significant or sensitive areas; K. To eEnsure consistency with and le further the goals and policies of the Comprehensive Plan; and L. Provide a process for the division of land for the following: 1. Short Subdivision. The division of land into nine or fewer lots, tracts, parcels, sites or divisions with a level of review that is proportional to the effect those lots may have on the surrounding area; 2. Subdivision. The division of land into 10 or more lots, tracts, parcels, sites or divisions with a level of review that is proportional to the effect those lots may have on the surrounding area; 3. Binding Site Plan. An alternative method of dividing property interests for nonresidential development and applying to the phased division of any land for sale or lease which is zoned for Ordinance 18-004 Page 3 of 9 DRAFT commercial, business, office, mixed-use, or industrial development, or which is to be developed as condominiums or a manufactured home park. (Ord. 09-002 § 1, 2009; Ord. 07-015 § 4, 2007). 20.20.020 Exemptions. A. The provisions of this titleTitle 20 SVMC shall not apply to: 1. Cemeteries and other burial plots while used for that purpose (RCW 58.17.040(1)); 2. _Divisions made by testamentary provisions or laws of descent (RCW 58.17.040(3)); 3. _A division of land for purpose of leasing land for facilities providing personal wireless services while used for that purpose (RCW 58.17.040(8)). B. The provisions of Titlethis chapter 20 SVMC shall not apply to the following; provided, that an exemption application for exemption and drawing consistent with subsection SVMC 20.20.020(C) of this section is provided submitted and approved teby the City: 1. Division of land into lots or tracts if such division is a result of subjecting a portion of the parcel or tract of land to either Cchapter 64.32 RCW (Horizontal Regimes Act) or Cchapter 64.34 RCW (Condominium Act) subsequent to the recording of a binding site plan for all such land (RCW 58.17.040(7)); 2. Division of land due to condemnation or sale under threat thereof, by an agency or division of government vested with the power of eminent domain; 3. Division or acquisition of land for public right-of-way; 4. A division of land into lots or tracts of less than three acres that is recorded in accordance with Cchapter 58.09 RCW, used or to be used for construction and operation of consumer- or investor-owned electric utilities to meet the electrical needs of a utility's existing and new customers as set forth in RCW 58.17.040(9). C. An application for exemption for any of the purposes set forth in SVMC 20.20.020(B) shall pursuant to subsection B of this section shall be processed to determine that whether the division is exempt with a minimum review for conformance compliance withte applicable adopted City regulations and ordinances. The application willshall be determined to be complete upon the submittal of the following materials: 1. An application; and 2. Maps, plans, and/or exhibits containing all applicable information as required by SVMC 20.30.020(B). (Ord. 09-002 § 1, 2009; Ord. 07-015 § 4, 2007). 20.20.030 Legal lot. Development shall be permitted only on legally created lots. A lot is created in compliance with applicable state and local land segregation statutes or codes in effect at the time the lot was created or binding site plan was approved including, but not limited to, demonstrating the lot was created through one of the following: A. Lots created through subdivision; on a plat approved by the City or Spokane County separately describing the lot in question; or B. Lots created through short subdivision on; a short plat approved by the City or Spokane County separately describing the lot in question; or C. Lots created pursuant to a binding site plan process in effect at the time the binding site plan was approved by the City or Spokane County; or D. A deed, contract of sale, mortgage, property tax segregation, plat, or recorded survey describing the lot in question if the instrument wasA division of land prior to March 13, 1978, provided that: 4. A tax segregation request was received by the Spokane County assessor's office prior to said date -Executed prior to March 21, 1980, for subdivisions (effective date of county's first subdivision ordinance) while the lot in question was under Spokane County jurisdiction; or 2. A legal instrument(s) pertaining to said division were filed of record prior to said date; and Executed prior to March 13, 1978 (effective date of county's first short subdivision ordinance), for short subdivisions while the lot in question was under Spokane County jurisdiction; or 3. All state and local land development regulations were met at the time the lot was created or can be met prior to the issuance of a building permit .Executed prior to July 1, 1969 (effective date of Chapter 58.17 RCW). (Ord. 09-002 § 1, 2009; Ord. 07-015 § 4, 2007). Ordinance 18-004 Page 4 of 9 DRAFT E. Development shall be allowed on a lot owned by an innocent purchaser. For purposes of SVMC 20.20.030(E), an "innocent purchaser" is an owner of the property, other than the original owner that created the lot, and who did not have actual notice that the lot was created by a means other than specified in SVMC 20.20.030(A -D). F. In the event a lot was created by a means other than as specified in SVMC 20.20.030(A -D). development shall be allowed on such lot if the development does not adversely affect the public interest. When determining the impact on the public interest, the City shall consider the following criteria-: 1. Whether the proposed development is consistent with the public health, safety, and general welfare; 2. Whether the use meets the underlying zoning requirements and is consistent with the use of at least one adjoining property; and 3. Whether the lot was created on, or before December 31, 2016. G. In the event an illegally created lot does not meet the criteria of SVMC 20.20.030(A -F), a development permit shall not be issued until such time that a legal lot is created. 20.20.040 Approval required prior to recordation. Any map, plat or plan, unless previously exempt, hereafter made of a proposed short subdivision, subdivision or binding site plan, or any part thereof, shall be presented for approval and be recorded as set forth in SVMC 20.40.030. _No such map, plat or plan shall be recorded or have any validity unless or until it has the approval of City departments and agencies with jurisdiction as required by this title. (Ord. 09-002 § 1, 2009; Ord. 07-015 § 4, 2007). 20.20.050 Prohibition against sale, lease or transfer of property. No person shall sell, lease or offer to sell or transfer any lot, tract or parcel subject to the requirements of this -aide 20 SVMC without first receiving approval hereunder by the City and recording the approved division with Spokane County; provided, that if performance of an offer or agreement to sell, lease or otherwise transfer a lot, tract or parcel of land is expressly conditioned on the recording of the subdivision, short subdivision or binding site plan containing the lot, tract, or parcel, the offer or agreement does not violate any provision ofTitle 20 SVMC. (Ord. 09-002 § 1, 2009; Ord. 07-015 § 4, 2007). 20.20.060 Vertical datum. Where topography is required to be shown, the land survey data must shall be based on the North American Vertical Datum (NAVD-88). (Ord. 09-002 § 1, 2009; Ord. 07-015 § 4, 2007). 20.20.070 Monumentation. Right-of-way, street centerline and street intersection monumentation shall be established as described by City -adopted street standards. In addition, for short subdivision, subdivision or binding site plans, every lot corner shall be marked or referenced in a permanent manner with the registration number of the professional land surveyor in charge of the survey in accordance with state law. (Ord. 09-002 § 1, 2009; Ord. 07-015 § 4, 2007). 20.20.080 Professional land surveyor. The preparation of all preliminary and final short subdivisions, subdivisions and binding site plans shall be made by or under the supervision of a professional land surveyor licensed in the state of Washington. The professional land surveyor shall certify on the final plat that it is a true and correct representation of the lands actually surveyed. A survey is required on all final plats. All surveys shall comply with Gchapter 58.09 RCW and Gchapter 332-130 WAC. (Ord. 09-002 § 1, 2009; Ord. 07-015 § 4, 2007). 20.20.090 General design. The design of short subdivisions, subdivisions and binding site plans shall conformcomply with -4e the requirements of all applicable City plans, regulations, and design and development standards. _In addition: Ordinance 18-004 Page 5 of 9 DRAFT A. The design, shape, size, and orientation of the lots shallee14 be appropriate for the use for which the divisions are intended, and the zoning and land use classification identified in the Comprehensive Plan of the area in which they are located. B. Lot Arrangement. 1. Side lot lines shall generally be perpendicular to public street rights-of-way, but may be within twenty degrees of perpendicular, or radial to the right-of-way in the case of curvilinear streets or cul-de- sacs. 2. Corner Lots. a. The lot lines at the intersection of two public streets shall be located a minimum of two feet behind the back of curb. b. At the intersection of two arterial streets (collector, minor or principal), the applicant may be required tosliall provide a widened border easement or right-of-way area behind the pedestrian ramp landing for the placement of traffic control devices and street lights, traffic signals, et cetera and their related appurtenances (see Figure 20.20.01). The limits of the border easement and right-of-way area shall be determined by the City at the time of application. This area shall not extend more than a minimum of 15 feet behind the landing. The boundary of this area may shall -be defined by an arc that is tangent at each end to the standard border easement, typically located behind the back of sidewalk, or right-of-way if there is no border easement in the vicinity. If this area is already fully contained within right-of-way then no additional border easement width wi-llshall be required. The only utilities allowed within this area are those necessary for the function of the proposed lights, signals et cetera._ Corner lots in single family or two family residential development shall have an average width at least 15 percent greater than the width of interior lots along both adjacent streets to permit building setback and orientation to both streets. Figure 20.20.01 8DRf1ER EASEIENT z La i p .rte 95` TANGENT L.ANDING— SIDEWALK RGGMT [9E Wear ARTERIAL ARTEP] AL CURE ` KIN. Ordinance 18-004 Page 6 of 9 DRAFT , ! a W ..0 B62OCR EASEMENT 4. "° rGENr -L7wG SHIEVALk Hp:kr OF VA` AQTERl._ 3. Lot Dimensions. a. Lot dimensions shall comply with the minimum standards established in Chapter 19.7040SVMC; b. Flag lots are prohibited. Reverse flag lots providing access to alleys or amenities located to the rear of the property are permitted; c. No lot shall have an average depth greater than three times its average width. 4. Double Frontage Residential Lots. a. Double frontage and reverse frontage lots shall be avoided except permitted only where necessary to separate residential development from arterial roadway or to overcome specific disadvantages of topography and orientation; b. When lots back to arterials, e screening device shall be installed on the lot(s) limiting visibility between the arterial and the adjoining lots in accordance with Chapter 22.70.070 SVMC; c. No building, except buildings designed and constructed as two-family dwellings or one -family attached dwellings, shall be constructed on or across existing lot lines. Where buildings are designed and constructed on or across lot lines, the building shall be located so that the common wall separating the individual living units is located on and along the common lot lines of the adjoining lots. C. Block dimensions should shall reflect due regard to the needs of convenient access, public safety, connectivity, emergency vehicle access, topography, road maintenance, and the provision of suitable sites for the land use planned. 1. Block Length. Block length shall bercomply with the adopted street standards. 2. Block and Lot Labeling. Blocks and lots shall be identified in sequential numerical order. 3. Street alignments shall be designed and constructed with appropriate consideration for existing and planned streets, anticipated traffic patterns, topographic and drainage conditions, public safety, adopted street standards, Comprehensive Plan and the proposed use of the land so divided. D. When a tractland is subdivided into lots of one acre or more in size, the CM may require an arrangement of the lots and streets, in conformance pliance with the adopted arterial and local access ! : ! subsequent redivision. E. Lots shouldshall not be divided by the eCity boundary or public right-of-way, and shall not be divided by -f any city, county, zoning designation, or public right of way unless exceptional circumstances exist-. F. Every lot shall have direct access to a paved public street, private street, or an easement for a private driveway. G. Prior to filing the final short subdivision, subdivision or binding site plan application, the applicant shall improve or make appropriate provisions for the construction of the public or private streets, alleys or private driveways that provide access to lots being created through the short subdivision, subdivision, or binding site plan consistent with applicable City -adopted standards. H. Wastewater design shall be in compliancecomply with all applicable City regulations and other jurisdictional agency regulations. I. Adequate public domestic water supply and/or fire protection shall be provided in compliance with all applicable City regulations and other jurisdictional agency regulations. Ordinance 18-004 Page 7 of 9 DRAFT J. All road designs shall be in confonnancecomply with Cchapter 22.130 SVMC and adopted street standards. K. Provisions for stormwater runoff shall be in complyianco with City regulations for stormwater management as set forth in Gchapter 22.150 SVMC. �. Existing and proposed easements for electric, water, sewer, gas, and similar utilities shall be illustrated on the short plat, plat, or binding site plan. The utility purveyors shall indicate to the community and public works development ddepartment (hereafter referred to as the "department") in writing that the easements are adequate for their service needs. M. The short subdivision, subdivision, or binding site plan shall provide for the location of underground utilities within public rights-of-way, border easements, alleys or utility easements including, but not limited to, those for electricity, communications and street lighting. When conditions make underground installation impractical, the dircctorCity Manager may waive the requirement for underground utilities. (Ord. 12-008 § 1, 2012; Ord. 09-002 § 1, 2009; Ord. 07-015 § 4, 2007). 20.20.100 Findings. Prior to approving any preliminary short subdivision, subdivision or binding site plan, the department in the case of short subdivisions and binding site plans or the hearing examiner in the case of subdivisions, shall determine and make written findings of fact that appropriate provisions are made for the following: A. The public health, safety, and general welfare; B. Open spaces; C. Drainage ways; D. Streets or roads, alleys, sidewalks, and other public ways; E. Transit stops; F. Public potable water supplies; G. Sanitary sewer; H. Parks and recreation; I. Playgrounds, schools and school grounds; J. Sidewalks and other planning features that assure safe walking conditions for students who only walk to and from school; K. Whether the public interest will be is served by the short subdivision, subdivision, and binding site plan; L. The proposed short subdivision, subdivision or binding site plan is in conformity with all applicable development code provisions; and M. Other requirements found to be necessary and appropriate and for which written standards and policies have been adopted. (Ord. 09-002 § 1, 2009; Ord. 07-015 § 4, 2007). 20.20.110 Attached single-family subdivisions. Applications for an attached single-family subdivision consisting of nine or fewer lots shall be submitted and processed according to the requirements for content and form for preliminary and final short subdivisions and process as stated in Gchapters 20.30 through 20.40 SVMC. Application for an attached single-family subdivision consisting of 10 or more lots shall be submitted and processed according to the requirements for content and form for preliminary and final subdivisions as stated in Cchapters 20.30 through 20.40 SVMC. Application for alterations of any preliminary short subdivision or subdivision shall be submitted and processed according to the requirements of €chapter 20.50 SVMC. Applications for alterations of any final short subdivision or subdivision shall be submitted and processed according to the requirements of Cchapter 20.60 SVMC. Applications for vacation of any plat shall be submitted and reviewed according to the requirements of €chapter 20.70 SVMC. (Ord. 12-008 § 2, 2012; Ord. 09-002 § 1, 2009). Section 5. Other sections unchanged. All other provisions of SVMC Appendix A and Title 2- SVMC not specifically referenced hereto shall remain in full force and effect. Ordinance 18-004 Page 8 of 9 DRAFT Section 6. Severability. If any section, sentence, clause or phrase of this Ordinance shall be held to be invalid or unconstitutional by a court of competent jurisdiction, such invalidity or unconstitutionality shall not affect the validity or constitutionality of any other section, clause or phrase of this Ordinance. Section 7. Effective Date. This Ordinance shall be in full force and effect five days after publication of this Ordinance or a summary there in the official newspaper of the City of Spokane Valley as provided by law. Passed by the City Council this day of , 2018. ATTEST: L.R. Higgins, Mayor Christine Bainbridge, City Clerk Approved as to Form: Office of the City Attorney Date of Publication: Effective Date: Ordinance 18-004 Page 9 of 9 FINDINGS ANI) RECOMMENDATIONS OF THE SPOKANE VALLEY PLAN INC C'OMMTSSIDN CAA. -2017-0003 • Proposed Amendment to Spokane Virilr<y Municipal Code (SVMC) Pursuant to SVMC 17,80,150 (E) the Planning Commission shall consider the proposal and shalI prepare and forward a recamniencation to the City Council following the public hearing. The following findings are consistent .t.ith the Thinning Commission recommendation that City Council adopt the amendment. 1. Background: Pursuant to RCW 36,70,A 1.30, Spokane Valley adopted its 2016 Comprehensive Plan Update aild aapdaleri development regulations on December 13, 2016, with December 2Ii, 2016 as the effective date. CP'A-2017-0003 is a City initiated code text amendment to SVMC Chapter 2010; Central Provisions to address naso -legal lots and iruFiccrll purchasers; eliminate inconsistencies with Title 19 resulting from the Development Regulations update. in 2.016; and piovide. clarifications and minor grammatical cEiariges; and modify the definition of flag lot in Appendix A. 'l'he Planning Con.lniissica held a public Bearing and conducted deliberations on December 14, 2017. TlUri 11 the public hearing deliberation the Planning Commission discussed whether the language allowing an innocent purchaser to develop on a non-fegal lot would imply other development rights. Specifically, the Commissioners licit the criteria added in SSC 20,2.0.030(F)() lulplictl that any proposed development could be allowed on a non -legal lot if it was consistent with the use of of least one adjoining property, The Planning Commission's concern was that al use: inconsistmt with tilt: am&rlyi.ng :tone: may be expanded under this provision. A c aange was proposed that would modify the criteria i n SCMC 20.20.010(F)(2) to include a requitement emit the use must comply with underlying zoning requirements for the site and be consistent with otic use ofat least one adjoining property. The Planning C')inIni ion also, discussed i'yo additional proposal changes. to the drat), amexidaucnt language. itie 1'rrst change would reword the language in SVMC 20.20.090(B)(4)(a), changing the proposed amendment language From "prohibited t xcepl." to "permitted only", The second change would modify SVMC 20.20.09Q:13x2)(h) and Figure 20.20.01 to allow city staff more flexibility in determining right-of-way and border c ricin~ nt requirements. The Commissioners voo J 6-1 le recommend that the City Connell adopt the elmendiraelil and iucludc Ilia~ proposed changes to the amendment language. 2. Planning CORIrrllssirira F1 ii 1iugs The City may approve amendments to the SVMC if it finds that the amendment is consistent with the applicable provisions of the Comprehensive Plan and bears s #1 substantial relation to public health, safely, welfare, and protection of the environment The proposed amendment is consistent with thetbElov.'ing Comprehensive Plan Goals and Palacio: Economic Policy .l U -I'6 — Promote the development or redevelopment of vacant and aindeeiu1ilizvd properties, particularly those with potential to serve as a catalyst for ccon0113i0 development. b. Land IJsas Goal LU -G1 Maintain and enhance the character and quality of li.Ce in Spokane Valley, e. Land Use Genal LTJ -(]4 13riswrc: that land use plans, regulations, review processes, and [ran irnJ:.rovenacaits salpport. cvmimic growth and vitality. d. Land Use Polity .0-P5 Insane compatibility between ndjaoent residential and commercial or industrial al SOS. bIniiiika iChLIR4NA51111ktarLlh ,14111i1ofth Sn}ulu5ti, VrdlryPtuniiIrr ctulitttiIysleillirrA•2017O0d3 Page 11.111 e. Lund Use Policy 7.0-P7— Protect neighborhoods from incompatible bund use rind arlvonse itnpacts associated with trunspt rtcttirin currid ors. f. Transportation Goal T-02 — Etrsrri'+M that transportation planning efforts reflci.t autiaipnlcxd land tir c l altcrns and support identified growth xipporturritics. g. Transportation Policy `l`-1'2 Consider neighborhood traffic and Livability conditions anti acldre:ss potential adverse impacts Eat pub! is and private projects during Ilio planning, designing, permitting, and construction! phases. "I' iiiispor[trtk n Policy T P9 — Provide and maintain quality street, sidewalk, and share l -use bath slit -Canes that provide a safe environment for all users. The Planning Commission recommended that the City Council approve the proposed omendrnent, Conclusion: The proposed text kmiendrneut is tonsistuiit with Comprehensive Plan and bears a substantial relation tea put lie. bca101, safety, welfare, and protection of the: envirouniclll. 3, Recommendation: I'Iya Spokane. Volley Planning Conun issioiitherefore recommends the Courtcil adoptCTA-20 I. 7-0003 as Iiiuctitiod, a proposed amendment to the SV C, Approved this 11'° day of January, 2018 Planning Commission Chairni:sn ATTEST Deanna Horton, Admini tantive Assistant i:lud[ng$ eifid [#ecarnnIAndat1l3A. flirLiht Spusauc v-.dlcyPlannlug fion7mis5"s1:111cJ -fL 17-0gm3 Page 2 oft T. Chair Graham called the the pledge of rrtleglifirce. Frosoi 'Heather G raha tri James Johnson Tim Kelley Mike Phillips Michelle Hasmussen SUZaniW Slalltos Matt Walton i innteq Spalm no \'ialloy P1 inrrirrg (2omruIa:iiriu Cu i ncil Climatal; mmink — City Hull Novntmrlanr.1i9, 24117 tuee;tit to Oder at ta0.) p.m. Conimi ioaea;s, staff and awdierico stood Car Steretaiy Deanna Horton look roil ami Shy following members and staff were Cary Driskell, City Attorney Lori Btulesw, Senior fi;inlier Marty Palaniuk, Planer Mary Swank, (office Assistant 1}4:ynna Horton, Secretary for the Corninias;inru 11. AGENDA: Coin niiision er Johnson moved to accept the November 9, 2017 agenda as Iprercnted. The vote cm the motion iMY euera Fre frrr 1, for er atom and iiie motion rO,-. erT TIT, MINUTES; Cotnmisione:r Johnson moved to approve the June 22, 2017 orotates as presented. The vale le to approve fire* motion to approve the minutes wag seven infrrvro, a:e n ENafarsa', rine 'w rm flosses. .1V. ar'[ IMMlSSTON RFPDT4TS1 C iiuri issiauers Johnson and Gatlin ru repot to d they Ii s,d attended sovcra I City C'uun' it meetings daring the last Blur months bill hsc1 DOL participated on anything which related to planning commission business. V_ AI)MINISTRATi[VE REPORT: ScniorPhinnur Lori Barlow said the City had received four privately initialed Comprehensive. Plana amendments. Siafi'will be taking tliu_n forward to Council for review of [ha (Mels ,ort titers be bringing Them to the Planning Conivaission in order to process tliciu though the review and rte caiaainendntioan ptc ocss, City Alkorney Cairy Driskei] ;also commented his office land been tivutk[ng un updates on small cell technology which allows cel I. phone companies to ]uc ata 5G technology in the public rights-or•way. His office will be biingn,g forward changes to the municipal cridu ELIong with training and changes to current franchise agreements, VT, PUBLIC COI' h1LN'fl 'Iliere was no public comment. VII. COMMISSION BUST 9iSS Fr) Strictly Session: CCA -24I7-0003, A proposed amendment. la the Spokane Valley Meutiieipal Code regarding subdivision general provvsiom9. Planner Iviarly Pnlar;in1c pru6uai1I Ll to fire Commissioners the proposod amendments to Spolame Valley Munioirrrl ('ode (SVMC) chapter 20,20, He stated when the development regulations Mkt lochitud in 2016; it created Raiile utcenosistencles iaa SVMC chapter 20,20, which need to be corrected. The amendment will eltarify !Iowa lesg;il Jol is wanted, eliminate the rcgttii meat that n cornea lot needs be 15 percent larger than other lots in the sulidivisinr;, remove tho Int duptlr unci width requirement, and redefines a flag lent. The proposed amendment al -' o rnrnnvcar the iegwirenieot far artr€rLs end lots to be laid out for the possibility of future slrwerts. 'Hu also amid there is clE:tin up of grammar and changes in wording to make things more enncise. Mr. PoiatIiuk explained thai the City haa dciyieled to uge the date of March 13, 1978 as a benchmark to determine n legal lot. Spokane County uses the same dale in their regulations. Any lot created prior to this dare by a deed, is considered [regally created_ After this date, the lot moist ii ve gone: through a proper subdivision process to be ucatasidered at luggal lot. An. npplicaant will need to Iorov i de ti legal document showing Flow th4 bt was mated. Cununisylerntit1'h1tli}as expressed concent over easing the ward prohibited rather tliun ttvuis[ed in ce njuiiotion with double frontage lots. He fell that prohibited meant it wouldn't he allowed, and asked Bow an exception could he given in the next slitenient. Ms. Barlow stated in certain situations double frontage lots ;lire the only de_cign Folutirni. The ekeeption allows lhosc Co9ulitian 7017-11-09 IF[FuiEihig 4`uonnitidun Pnxe 7S of7. to be reeognited. Double frontage lets fire prohibited, iuyiesn thEt is die only way to develrrp n lrieec ul prtrpurty, Chu iu Ciitrsu rases, it ivctiuld be allowed. Mx. Phillips said he didn't like the uhEingiiig ol'the word from avoid to prohibited ss he was coiwcrncti they y would not bo allowed ander any 4bircuinsnnwes. Mi'. Driskeil said there is no way to enforce avoid, but the City call Unforec piuhibllutl. Dated on the cliscosdo I sr<tffwIil look Irl this lopie more. VIII. GOOD OF 'Fl -IE ORDER: Commissioner GraihGim staled h a -U i -a WLI iip art iiw end orthis year, and she would not be s king reappointment. IX. ADJOURNMENT: Commissioner Jnlinnon moved to adjourn the 'sleeting at tS:45 p.m. Tire yore 1}11 the motion irtm: nrmumr.1ars firm; io motion passel ActfityiJ 4 ) thine( Oialieitl; Chair J:iaile signed ID C3 tna Horton, Scerein ry Minutes Sp 'thane Valley Planning Commission Council Chaambers — City I±uit l)eceitt ber 14, 2017 Chair Graham ca]itxl the meeting to order at 6:02 p.m. Commissioners, staff and audience stood for [tic plcdgc of allegiance. Secretary Deanna Horton look roll tirrd the following tncarabcrs and stair were present: Heath cr Grnhaiati Cary 1)rislcell, City Attorney Ja111Q3 Johnson mill Plc Ibig, City Engineer lam 14LHky Marty l'alaaniuk, Plainer Mike Phillips limy Allen, Engineer iv9icheIle Rasniu cn Ray Wright, Senior Tratlic Engineer Suzanne Stathos (Adria M:iril:r., Swint Engineering Manager Niall W:rllon Deanna Ilotion, Secretary for the Commission 11. AGENDA; DA: Connor sioncr Johnson ancav'ad to accept the December 14, 2017 agenda as presented. 7 err ti,ote. On 'he uaoatr)rr wcL4 Srr'latt rrlJbV01l a erre against and the umtlan passed, III, MINUTES; Commissicrfcr Johnson moved to approve the November 9, 2017 minutes as presetitud. 77w ate a,toar1 n fo aJ L ' the ar;laaufes aura's seven nfavor, zero c airs, a, crracl the moriatt pissed. i CommiSSJ1 }1 BEFOR'1'S; The Commissioners had no reports, V. ADMINISTRATIVE REPORT There wain Mier tuirrMiaaiSaa7oliVe reprl. VI. PLI RI iC C [)M F I N'l`; "['here was no public comment. ViI. COMMISSION BUSINESS; i) l'lihtic nearing: C.TA-2017-0003, A proposed amendment fu the aSptilraine Valley Municipal Code regarding subdivision general provisions. Chair Graham read the rules for is publit: hearing and opcaacsl ttae tnihIic hearing at 6!05 p.nl, Planner Marty Palaniuk presen0utl llrs pinpnscd amendments to Spokane Valley M,rnit•.ipait Coda: (SVNIC) chapter 20.24. ile explained when the development rt tiplatitnz� woic ripdated In 2016 It created some inconsistencies in SVMC chatter 20.20 which need to be coaiected. The amendment will clarify how a legal lot is created, eliminate the requirement lha: a corner Int needs tti lac. 15 percent larger than othe=r lots in a subdivision, reinove the lot depth and width requirement, fan+_t redefines a [lad tut, ' 'tic proposed amendment also removes the requ irame:at for iivi sii m tri ctlrafnrm with future planning documents and provide for possible future strcrvts. The update includes a clettin-up (of grammar coal Elgill ges in wording for consistency. In 1969 Washington state developed the slihdivision process to divide praperty and create lots. Prior to that a lot could be created by a boundary line adlusircc<nl sn' by a. aleucl. Spok,Firac. County adopted subdivision regulations in 1978. Mr. Prrlataiuk explained that the City has decided to use the date ofMaareli 11, 1978 as a benchmaaikto determine a legal lot, Spa kcute (._'.curly uses Ifac smile date In their regulations. Any lot created prior to this date by a decd, is considered legally created. Alter this dale, [lie lea[ must have gonethrough a proper subdivision proce :s to hc.ccsaasid+rescl ¢a Jc t ial lot_ An applicant will need to provide i feraI document showing how the lot was created,, The Cvrrnsaissanraers ilist`iGpccd the provis[ons for SVMC 20.20.30 (E) 1rltauecan purchaser. This section provides pr.lmtiuti for seinctrne who unknowingly ingly purchases a lot which was not erented legally. This allows the innocent purchaser to put a haaildn on lhral. property_ Commissioner -Phillips was concerned sti it oiio would try in use this I]I,1cc`ss to commit fraud. Mr. Driskell stated this would not apply to any ]ut created after 1978, however staff will research this to ineke sure this could not occur. It was p[Jiro ctsi Oil! tfsi 4 watsul{l only *ply to lois created prior to 2016. ( o1T aniesioner Johnson had ai question regaarding 1VMC. 207.211.30 (2)(2), rrhelher the Ilse is arisisient-with the use c+ 'a lea.it one. ue4r ihhng properly. t li= concern., in the case o1`aan inno'mo 2017-12-14 Nanning Cnmmi sic+ hrtinurca: 1' :c 21}ri purchaser, was someone could comic in and request to place a use on Muir property, because it is allowed on an axijuinaing property which was not consistent with the smTt otimlirtg rruiglalrcrrlrnod. Mr, t'ailrairiuk replied the use WOL1kI ll Live to he consistent with :he underlying knifing. This could not be used uhangu lift ,earning. Commissioners Johnson and Walton felt the wording + olid not rneet. iie inlr:ait The flag lot d4:f nition relies on the front lot dimension. The pike posed definition does mot rely on any width requirerents, and retrieves any lot dimensions fOr a Lag lot. Rather than allowing at flag lot for access, the City will require an easement tir:wss piopei1y" Mr. PnlaniL1k said u developer v+i 11 i ut corners developing a fluff; tut. The amendment rernovas the requirement for land to be Met aide for the development yrfrtlnare streets the City might nut boll&, 'i'lris set aside is based on the arterial street plan. 1t also removes the tutufie arxlu`siliem area requirements aunt the municipal code. A change to ihu amount of egise..rmoni fora corner lot where two aiturial streets meet is proposed to allow stafftri determine the appropriate amount, whiLli es cRrin less tart rhe current regtiircfnent" l'[iu r+;st of the changes update referenet and consistency in language. Commissioner Oraltuto, seeing no one who wished to testii'y, closed the public hearing al 6:32 p.m. ('c+rn,Trissrnricr,ToI+ttl,soii asked to discaisi 20,20,020 (E) and (F)(2) regarding the innocent purchases and extending } land use into incompatible zones. He said Ile felt that the language will allow a rise from adjoining property on pile pr fi rtv" Fie requested language be arlcled that the use must be allowed within the rn1dtrlying 7.0110. Commissioner 'Walton hiatal it. would resolve his issue: with dime duns as .vuell, Mr. Pattmitik stated dcvcthisir1L'nt, as It is tefeu'td 10 Iii this case, meant a building. 1f someone, wiinted to suhdivlde it, they would have to comply with the subdivision regtnremcnis. Staff would cheek /Diking, find enforce those zoning requirements. The Commission lei! the Crtrr+°nk lfirrgvage was oat 5p n1.1 e: cricrrx 1. rt i' the public to understand. Mr- Driskell c lc[1 the following language to Reit] tr, (1)(2) ,vheffrer the proposed use ax consislefrl ivUli ffir m f crit actiobling prrverfy, and edso consistent with the underlying zoning. The Commission fell this satisfied their issue Wilk [his piucc lar tlic amendment. Commissioner lissioner SuatI os asked about the removal of'the future ire u+.sitinil areas. 1v r. Driskell2,.iated it is not fir to require land to be set ; 1dc, 'without any possibility cif ck:vt,lnpn}erit, fill' the dovelnpruent of future toads which the City did not have the funds Lci build or in ti-te near future. Corniraisssnner Johnson asked ahouL the proposed change to SV C 20.20,090 General Design. These are proposal changes being suggested by tate Engineering. . Division. lnuniT5.1[Hier Waltat3 caked why the language re a di ng the easement for as r;.urzaer tot at two m ite:tints wsrLs changing from shall to may be required.. Gloria Mantz, Engineering Marragei-, stated it currently yu1Les [here varill ba; ra 15 -foot casement for traffic. equipment. She said there are limes when they don't need 15 foul, sometimes they only need (lye fist, sometirues none al all, 'Phis allows engineering the flexibility to look trLoh aituatiarti and snake a deterrninatiiN1 at that time. The Corrarnissioar er crr,ief fhc.t' liked the .oposed enact , as well la changing the rrrrilchingfigivv" ComTr1 ssionerlohnson asked iithe t;:cma ni sion agreed to the pr'oposcrt amigo to 20"20.070 (13)(4) language from "shall" to " per-mittnd oj' "" The Commission discussed double iion[rat c i nix, arid ogr•r:ed to "permitted only" language. Comm isskiller Qrrthum moved to forward to [he City Counc[I CTA -2017-0003, with the firllotvirig changes adding to SVMC 20.20.030 (F)(2) "whether tth propr's'eri use is corrsisfenl with the use of «n 6uir pining property, arid riINvr iiddh the rr:;r r'r-f}'rnzonh ," and all others us- presc:rttccl" Tho' ucmirr iiia orae m tion W six infer+r; 0116 u, rairrsf, with Commissioner LV i fr,n dissenting. Li) $Ludy ge. lois CTA211?-014104,. A proposed ameualrnerrlls le the Spokane Valley Sit'ixl Stnndtit�als. Engineer Henry A11i.n explained to the Comrni sioti the Street Standards need to he changed regarding some time sensitive 4hiing cs which need to be made Leath i. of some federal projects. 2017-12-14 !'tanning Commission Mireitex Trite 3 of 3 'I'hc Street Standards, which derme Prow public and private infrastructure is built, was adopted in 2009 and has only had minor changes to it since that time, S orti c i] f t I re changes are for consistency,. and language. Mr. Allen also explained stiff is reviewing the Street Standards and would be returning at a figure date with a comprehensive update. 'I`hc pilinriay reason for they update was comments received from the J'cdcral Highway Admnais]niki i (FHWA) concerning the ability of the City to maintain aidcwalks. The FHWA wanted the City to nr;ike sums when a property owner does not innintain their sicicwollk the City has the proper anti milt' Ici gT in and fix it. This change is neeessurry in order Ibr the City to continuer to r+:ccive grants for road projects. Generally, the update will make the language in the standards consistent with changes to stall jo,itie1ns that occurred with the reorganivation and Implementation of the standards. Other substantive cliingcs prcipngcd include removing relerenoes tai variances and future acrlcIisiticrn aims, hinny sIampru itions were changed in tiro rcttrga,til+sitiOn, ltut ,MSC [tic references stiII rcrnaiur in the municipal code. 'film rure.renees have bceii ch_1nged ler [Ire criLy manager. her. Driskell commented ihe, rutixon for this i.s the city manager has the ulli mate authority, but delegates it In other elarirloyees to p riin3T] the work, There will IN ii public hearing on the proposed changes January 25, 2018. VIJ1. GOOD OF THE ORDER: 'till's vies. Ct i I kitIlitiq ioner Grahanfg Iasi. Stair and the Commissioners thanked C:oiT Trtisrsinner Graham for her tittiteserVing IIsi City WS #r Cotrunisstoner, Conrmia iotaer Walton stated he agreed to all or tim proposed changes for CTA-20l74CO3 however he wanted to be a dissenting voice should there be a ireecl for a reconsidera+l+im, Ix, ADJOURNMENT; Commissioner Jsrhnwon moved to adjourn the meeting gat 7;48 part. Tire vote ora dee tarcadk n was tills raftrrrne in fiwwu', and flee' motionpassrrr! Heather Ur hata, Clair Date signed Demure Horton, Secretary 11Ji11(1(es Spokane Valley Planning Commission Council Chumberws — Cit} Hall January 11, 20m Viet! Clwait Johnson called the meeting to order al 6:02 p.m. Commissioners, staff and audience sto d for the p[edge of allegiance. Sceretary Deanna 1 foitnn took roll r.nd the fallowing members and stuff wc,re present. James Johnson Danielle Ktlschmitter, absent, excused J'itn T elley, abseni, exeused Mike Phillips IvIk.hollc Rasmussen Suzanne Staattina Matt Walton Erik Lamb, Deputy City Attorney Lori Barlow, senior Planner Marty Pc,hetiut:, Planner Henry 1111ur7, F.nglncer Ray Wri gal, Senior' Traffic Engineer Gloria Ment, Senior Engineering Manager Rod 1 liggins, Mayor Deanna Horton, Secretary y for the Coxninis.1ion 1T AGENDA: Commissioner Rasmussen moved Lo accept the January I I, 2018 agenda as presented. The rota erre to rtlr.rfio,t 7arrs f use ter f asps+', zerrr igate t i and the motion pas sed: 111. MIN Li TES: Commissioner Rasmussen moved to approve the December 14, 2017 minutes as presented, The vote on the ?nation avers five in frnvor, aero crgrn ns', the n coliOn. j a '-+r t . 1V: comivrissroN REPORTS: "rite Commissioners had no reports. V. ADMiINISTRATIVC REI1ORR'1': Senior Planner i.oax Barlow noted Danielle Kaschinitter had been appointed to the: Platirning Commission to replace l feather Cullum al tins January 9, 2018 City Council meeting. She also shared the advanced agenda with tho Commissioners and discussed upcoming sal. jecis which will appear bifbr^c them: Comprehensive Plan amendments and fa text calttendment to change the one acre requirement for animal keeping back to 40,000 square feet which was changed in the update to the development regulations, 4'7. F[Tlil IC C(}tVI.NMLN'P: Rod Higgins. Spokane Valley Mayor — Mr. i IigRins thanked the Commissioners for a job well done last year. He said he bad heard the Commissioners felt they in: lit have been undelworked, but he assured them their mission was very itraportnnil. TTc Ra id the job of the Coratlaaission is to screed things the City Council And it makes their -jobs casicr. I -le commented tlaaat laately the Council has tollnwed the recommendations of the Planning t:c,tr1rnils*iucr, ich inrlicatws they kava done a thorough job. Vll. COMMJSSJON BUSINESS: i, Flection of Officers Secretary Deanna Horton reminded the Commission that only Commissioners who had servcxl more than otic year would he eligible to serve as the Chair or the Vice Chair orf the Commission. Ms. Horton then called for nornivationc for the office of Chair. Mr. Phillips nominated Ms. .Rasmussen, w'hc- accepted the nomination. Ms. Rasmussen nominated Ivfr. Johnson, he declined the nomination. L laving no other nominations 'voting, by a show of hands, four in favor and one against, Ms. Rasmussen dissenting, Ms. Rasmussen was voted to the; office of Planning Commission Chair for 2018. Ms, 1 fs rton ten accepted nominations for the position ofVk.c.Chair. Mr- Phillips nominated Mr. Johnson, who amopted the nomination_ I laving no other nominations, voting by a show of hands, [vc in favor and rianrr against, Mr. Johnson was olceik:d to the position ot" Vice Chair for 20/8. Ms. Rasmussen Chen continued to lead the ntcctir g. Planning Commission Findings of Fact for CT, -2017.01103, A pr'r►pns .d amendment (u the Spokane Volley I'Junic•iiiat Code regarding suliriivisiou gttmerfrl provisions. 201YI-0I-11 Planning commissEonMinutes Page 2of4 Planner Marty Pal ahruuk explained the; Findings of Fact had been drafted based on the recommended changes the Harming Commission hod voted on at the public hearing and then incorporated into the aamendtnnctit to *hove forward to the City Council. C'ermards,s(oner Johnson proved lo approve flw Planning CnrrirnL ..Lion AilldhigS of Fart Po. C1.4- 2617-(1(103, 1 hie role on the morir.rix was fore in fervor, zero tiii mprxssecI_ iii. Public Hearing, Street Sliinrliii'ds Update Chair Rasmussen opcneld the public hearing at 6:17 p.m. Ellgii eer Henry y Allen explained the City's Stroet Standards, which are the stnndaards that guide the cleveloptnent of politic and private, Infrastructure, Mr. Allen explained the changes to the Stat standards were initialed to address tura Federal Highway Aelrr]inrstrattion'as concern regarding Chapter 1(1.2.1 and the City's ability to maintain ra'sidewalk if the property owner should fail to do so. The Street Staanelayrils are also being updnted to alimin;,te City positions-vhiclh no longer exist and change them Lo refer to the City tvlanagr, r, wlio lr;as ultimate authority but delegates it to oilier staff members in the City to perforile. Some of the other claatnntls include cliirrinsaiing the variance process, FAA and Mylar record drro,vings, no longer requiting streets to connect to future; development, frontage improvements only where a project accesses a street. Chapter 3 as being updated to allow limited trtafl'lc impact analysis for SEPA 1111111 There ore also proposed ehangus to the Spokane Valley Municipal Code (SYNC) 20.0,010 and 22.130 to remove references rences to fibrae acquisition irCrc4 #][ld revise SVMC 22.130 to rep nated positions. Commissioner Rasmussen questioned why on page 3-14 which references ccsllisir n history; the word `peril' was being struck. Senior Traffic Engineer Ray Wright explained the City provides llie collision bistoe-ytothe outside engirl[xrs when they creed to do a traffic analysis and the City always provides the most cumin information. She also named that on page 6-3 the word `ousts` needs to be changed to cuts, on page 1-2 adopted is in the sentence twice. Chair Rasmussen then open the hearing up for die 1 uhlic to comment. Vicki Donsahaie, 323 S Bvwciialii Ms. Donahue stated she lives at the interscelion orf 4" Ave and 13owdish Rd. This is a buoy intersection and there are many accidents which occur there. She is ills° Cnneerned about the school children walking along these roads. She feels there should be a traffic control tic:vice al. this intersection, slowing }7eoplc on TIcrwdish, improving 4'1' Ave, She also stated shelled received a letter repo-ding snow removal. She said they 5hC.IVO. but then the plow cornea along and puts Ilio, it riglht back on the sidewalk.. Paul Taylor, 323 S ] ,dish; Mir_ Taylor said the leaves and the gullets did not get cleaned out along the road, so when the snow raells there is no place for the water to ga. He commented there is toe much traffic on that (flowdish) road, it needs a safety control device_ I le said it is not can we have it, it is do something about il. Seeing no one elle Alin Wished to testify, Chau" Rnsm. aisscn closed the public hearing at 6;37 p.m, Commissioner S1adios stated she could see the iommernter's voiat ot'view because 4111 Avcnnic is busier all the time. She would like to see more stop lights along it. She said 44' Avenue is how everyone avoids Sprague but with all the apartments along it now„ it is dangerous. Commissioner Johnsen said he agreed regarding 4'1' Avenue. Control ionet Philips commented 10.1 sys The City is rot responsible for rrrriiiitenanCe of the sidmv iks. He ootniiauuuled he has a problem with a citizen having to replace the sidev miik if it becomes damaged. He feels il should be part of"the City's maintenance iiru rain a{r repair the s[dowel ks, espeeirilly if they ar'c inside the right-Hyl-way or a bonier ulsem Lrat._ I Ie felt maintenance should be e xplained better_ Ile also commented bo tilos li p]inbk111 with shoveling the iielewalks and then the. plow conies along and puts the snow hack and the City turning arui1Itd slid fining Koti.neone because there is soca* on the sidewalk. Ms. Barlow reminded tiro Crinylnissinnrrs the reason for 1Iic change in the language: in this section is due to the comments received rilarii the Federal Highways Administration and without it, it could affect the City's ability to receive grants in t1ir. future. 201WW11-11 Planning Cummibsion NI inors Page 3 or'4 Mr. Allen stated that when the Street Standards were adopted, they spoke to nuerty jurisdictions regairtiing the can; of sidewalks, and the idea of citizens main'_raining Ike sidewalk iir Boort ref their homes or businesses is not unique to our Cily. The City inherited this language from Spekatno County but many other juris.iictinns in and around the state have the seine =quit -moot, 11. would } a huge expense and under taking for the City to have in maintain hundreds of milers of sidewalk.. Commissioner Walton confirmed the snow shoveling vas not in the Street Standards but was to separate ordinance from what was currently being considered. lie wondered how the expense year repairing or ',enlacing a sidewalk was determined. Mr. Lamb explained the City is required to get NA; for itt public' works projects and required to accept the lowest bid. Based on lhis, lin: citizen would only Ile billed tar the actual work and we would have an invoice for the vrrprlc which was performed. Commissioner Phillips fell thai maintenance 'WM Hot .berry defined in section 10.2.1. Commissioner Johnson stated t1ut he also felt it did not cle- u'ly define rrrairttenanec however felt changing it rttiglt: he better handled in a figure update. Mr. I.. utrb ot°icred adding to the end of the sentence `properly owners arc responsible for the maintenance of these features as described below.' The Commissioners agreed this change would satisfy their concerns. 'oonontssiora+ttr .1'nhninn moved to approve the staff recommended changes to the tiara aic!pal code and the, Spokane YaTTey Street cat Stundarc as proposed -with the follnt ring changes, ree'I.5'lratrrlru do sur.rivri 10.2.1 e_ ' mgi1ig the .second Sentence of tette second p[ra'rrgrupla by «drirrrg► enc described hvloir'tothe end eftinesmience. Street S'dandeo sxr}dtlnrr 1.3.2,'bird bullet ensure public; fay [lilies great level of servke sta nd;mik adopted in the Comprehensive Plan, SF ,C 22.1.30 eh 7ngv nevelopmen1.5'rrrvicer Senior Engineer to City Itianarger. The rife on the motion ,getslvr ii fen}or, zero against, the ntofionflossed. iv. Study Session Wireless Small Cell Technology Deployment: Mr. Lamb gave ti prescntation to explain to the Commission wireless small cell techrtning , Most lvir'els cell phone traffic is currently Handled by the large monopoles, 1 tistorically the City has only dealt with the monopoles which have been located c.n private property. The City was contaetcd by a Tvlobilite, company connected will' Sprint, regarding small cell sites in late 2015leiiit 2016. The City joined fl oxen. ctrtirrnt of numerous cities in 2016 to become wore educated in haat the sniall cell technology is and how it will.i'fuct us. Lt its u tiurn developed `model franchise' agreements area `model development regult'itinns' for the deployment of small cell sites. The City has been working with Verizon. MCI "fele com, and Msbilite mgarding the use a f' Spokaiic \' 1 l ey rights-of-way for small cell d pin'yi nen!, Tho City has developed draft franchise agreements and regulations Mated to small cell deployments. Current 3 air 40 (gruel lion) icchnG10 y k when a hared held 'device coumuiiii ales with the large monopole. The farther you get from the monopole the less .r.liablc the signal is. Monopoles ctin only accept so Batch data at one time, Sentell cell technology would be adding antennas in the. righ of -ways and belle to tering data from farther out to the larger monopoles. }°ederal law changed to set specific timelines for processing these. small cell porotits_ There are also laws in place which stop eitics from prohibiting small cell deployment. State taw atiotiws t}he City to require a riuester use hermit, the City is using figuichisn lucent -cots as these master pertt7its. Cities are allowed site specific pwmil,s for the Remelt call installations in addition to the mita permits. The lelocpanrn iiidtisiry cannot interfere with the no_znal use of the riglds-of-way. Cities cannot regulate 4ervices based on eon lord or kind or sigreaits, c iiia not prohibit placement of wireless facilities within thu [ .iy. Since the City dam not ower any of tate lighting fixtures imp the right-of- way, the ca; I1 pray i d e rs linve ben signing agreements with catch of the; power providers to use their facilities. The City is expecting a small cell to be art antenna arm mare than three cubic feet in volume and the equipment box would be no larger than seventeen cubic fail. Mr. Iamb shared pietui es of what it was possible for the srnali cell deployment to look like. 'Ito City errn restrict the height, based 21111i-01-11 Manning Curnrui: :ori Miriule3 I'ags 4 if4 on 5.itnirlg location, impose sonic design standards which might incltidc stealth shrouding requirements and landscaping for some facilities. Mr. Lamb explc+itted Ills proposed amendments: • Appendix A, add definitions related specifically to saint cell deplclyrii n[s clad the Hew timeline provisions. w SVMC 17.11(1.030 add that sn14111 cull permits are a Type 1 permit and shall hes processed as such, except kis otherwise required by federal and state: law, • SVMC 19,6{}.050 emend the permitted use. matrix to allow small cell deployments in all macs subject to the supplemental mglilationA proposed in new chapters SVMC 2.2.12 t and 22.122 • SV MC 22.12(1 remove any references to small cell services sVMC 22,121 new Chapter pi widing fir master use pm -faits, deployment of small cell fiic:ilitic:s rind lays nut the permit application requirements and small cell tIcsigri and cnncealirent standards. • SVMC 22.122 new chapter providing for mandated permit review times. iiS suited in state or federal regulations.. Commissioner Jehtts4n n ked who would be responsible if ouc or the sites was danifaged. Mr. Lamb stated it would be Iulrndled jut as if it was a power pole eta. a mail box in I]sc right-of=wa . Commissioners asked if pruvidci, would be required to a lce:ato on the sumo prole- Mr. Lamb said providers would have to prove that the only plaice Clye:y can provide services is where they want 10 locate their. egnipnrertt. Commissioners raised concerns regarding: • the aesthetie:s of having more equipment in the rights -or -ways, * how close together acilities would need to be ionated, if they could not co -locate, • if they were wide band or narrow Mand facilities. • what would the frexlnc.troy do to honeybees, animtils and p4c}plr. thieves would dans€rgc: the sites for wiring. ▪ yid iatioo Full the signals being givers off these lowered antennas, • the ability to determine what they depluyriient will look like. Mr. Lamb slated the public hearing for the small cell deployment was scheduled for Janerary 25, 2018, Ho would do his hest to try and bring answers lly tile public. hearing. VBEL Goon of TIIE ORDER: Commissioners congratulated C umrnisyiuric:r Rasmussen on her appointor ent to the o:fice of Chair and wished her luck. TX. ADJOURNMENT Commissioner Johnson moved to adjourn 1.1ic meeting at 8:12 para. The vole on lbw migion was 1rraafintaus in favor, the trruliurJFar}.s.sed( Michelle Rasmussen, Chair Date signed Deanna Horton, Secretary COMMUNITY AND PUBLIC WORKS B1111.1]IN( & 11L,ANNING STAFF REPORT AND RECOMMENDATION '1'Cl'1' ;. PLANNING COMMISSION ('TA -4.017 003 STAFF REPORT DATE: I'ecember 7, 2017 HEAR1NG DATE AND LOCATION: December 14, 2017, beginning at 6:00 p.m., Spokane Valley City Rill Council Chambers, 10210 East Sprague Avenue, Spokane Valley, Washington 99206. T'ttoPoSALl)ESCRIPTION: A text amendment to Spuluatne Valley Municipal Code (SVMC) Chapter 20.20, General Provisions to address non -legal. 1o1s and innocent purchasers, ulimivaile inconsistencies with Title 19 resulting from the development regulations update in 2016, modify Ilio rlofnition of flag lot in Appendix A, eliminate requirements for lot and street arrangements and fame acquisition areas, clarifications and minor gra11matical changes. APPROvAIr Cur•a'LdlRIA: Spokane; Valley Comprehensive. Plan. SVMC Title 17 (general Provisions, and SVMC 1930.040 .30,040 I}eveloprrment regulation text amendments. SUMMARY OFBECOMNIEi*tI?A'1'IONa StaaITri oiritnc ds approval of CIA -2017-0003 to City Council STAFF PLANNER: Martin, Palaniuk, l'ltunncr, Coatununity and Public forks Dcpa'+ttment A'LTAC:HME> TS: Exhibit 1! Ptnposed text aarnendmcnt to SVMC 20.20 (general Provisiotia Exhibit 2: Proposed I4xt alaa7cnduuent to SVI MC Appendix A - Definitions A. TtAf:1CC RC3lJ N I) I N FOR11'L&TION 1. APPLICATION PROCESSING: S'VNIC Chapter 47.811, Permit 1'rv0ttssing Frncoduics_ fr Mowing. table summarizes the procedural steps for the proposal, Process Published NIA ice of Public Hearing: Sent Notice o Pub1k Hearing to staff/agencies; SF, PA - Pursuant to WAC 19711-R00(I 9)(a) this action is excentpt from SEPA review_ Department of Commerce 60 -day Notice of intent to Ado t Amens neat 1)n k '1 he November 21, 2017 Ducembur 1, 2017 November 29, 2017 WA Novo rT ba 14, 2017 PROPOSAL 13ACKGROUNTr: The Genera,' Provisions chaoplcr oi. the Subdivision Regulation corolains regulatory provisielm that ripply to tiny subdivision ot`property in the City of Spokane Valley. The regulations in this chapter are general in iaatuat, apply to all aspsc:(s 01' subdividing land, and arc not specific to uriy particular subdivision process or laud action_ Staff Report unci Rec[amirtcmdation CTA -2017-0003 entire SVIvie Ciiap1c-r 20,20 (General Provisions was revieweei. Many il'the proposed changes have been made to improve the readability o1 the chapter, standardize the wviy the municipal cede is referenced, mid to irctikc it consistent throughout the municipal code, The rctn€svxal of lot width unci depth requirements hi the Zoning regulations created inconsistencies with the sttladivisioir regulations. The issue of determining u legal lot has been problematic for staff when reviewing building peramtiit, _ The state legislation adopted ri putting act in 1937 that grave local jurisdictions the authority to review the division nt'land and to in9are compliance with local rcquireniints. Prisu'to I937 plats wens not reviewed by local jurisdictions, In 1969 the shite to ;isIature repealed the 1937 act acid adopted the plattingaotthnt is in cffcct today, The 1969 Platting Act is implemented at the s181c 1c' cI through the [Revised etnIC of Washington (1 W) 58.17 and at the local level through SVMC'litle 20. hr order far development lo oec:tit can land, it inust he divided in cnnrpiiarnc;e with stale platting i'teluhuii lits. 1.ocai subdivision regulations ikuV designed and itriptcrtrnotci1 to ensure compliance with slate requirements and cc. -m nunity staindards. The subdivi lion regulations provides the process for local jurisdictions to maike sure the iiew development of lots will comply with the standards for access, roadways, water and sewer service, lot arca, density, sate paths t* school, and other health, safety, and welfare concerns. A lot that is created outride ofthe legal subdivision process may not meet these standards, S1althas encountered seVerrYI occasions in which ai citizen has applied for a building permit to develop on a lot that was not legally cleated City staff reviews the site plan for a new building (o ‘16111'k2, aYittong other things, (he 1+ui1dtii wi t1 Dave adequate aicress, will be properly set hack t'rorn property lines, will riot he built within an established casement, aind is being built on a legal lot. In cases Where i IOC lois not Xoom legally established the In ildirr permit must be denied pursuant to the current regulations. in 50111B cases the properly rrw Tier. has purchased the lot without knowing the lot was not legally established. The proposed amendment clarifies whait is It legal rlivriNioir nf lane_ C'irrently, lots may be created through a deed if the were recorded prior to one of three key dates. 'ilii± dates correspond to the implcuzeniatintt times of various stale and vouuty platt[ing 1 islation- As currently written, it is nut deur what date should be applied when determining if a lot was legally created. The proposed language will establish the key date as the date Spokane County adopted their first sitbclivisioli ordinance. The proposed amendment will also allow protecrtion fur an innocent purchaser of a non -legal lot. If the ipurchaser did not have kaowlcdgc that a lot was not legally created them they will be permitted to develop un the lot. The amendment wil] also allow development on a non-logr►1 lot if the public interest is not adversely affected. The City of Spokane Valley compreltensive Flan was updated through a legislative update in 2016, A variety of chinl„cs tocettr d wittrin SV MC 'title 1 J. Zoning Regulations, as hurt of the update, Amon; the changes was the elimination of wlJHrd Ir lot width and lot depth. '['hese changes resulted to inconsistencies with SVi 4C Chapter 211-20 Cleneral Provisions. The eIimiiuition of he corner lot width a !ulrctrlcnts and the lotwidth to lot depth requirement will eliminate thie inconsistency with thii chapter. SVMC 20.26,090(il) provides a mechanism for Ilse City lir require lore and street arrangements and to establish future acquisition aro aiy.. Future acquisition areas encumber the property in that parking., draivaigc, improvements, and physical structures cannel. be tai:Gucci within 111e area Setbacks for building are established from the future tiC[1iiisi ion arca. These aroaN wtre meant 10 aneconirncxlaie future road irnprovernents that were anticipated as part of the airteriar[ mrd la,util access street plans. The City ieterinined that it was not legal to regtrire developnierrt to }"sot aside' areas for future developmme:nt based on pians that may or may not be implemented. 'Clues proposed a mendirient will eliminate language that is not consistent with this determination. The Plano Gnat Commission n conducted u study session on this arnendnient on November 9, 2017.. A public hearueg is schtml ilod fur Due 1 r[, 2017. Pige2 of Staff R.epaii mut Reel.)mnot:dation CIA -2017-0003 1;. jiINDINGS AND CONCLUSIOI S SP>S CIlr1C�. Ti) 'i'liL MUNICTPA[, CODE 'i'EX' APel N13ME11I' 1. Coiuplirrnce with Title 17 (Central Provisions) oFilre Spokane Volley Municipal C.odc E6. 'hiding', SV MC 17, M.150(F)1'vfi iii ipal Code "Text Amendment Approved Criteria f. The City may approve MuiiiciCode "Fox( rirnendm.ent, if it finds that (1) 'Ilse proposed text amendment is consistent wills the applicable. provisions of the Comprehensive Plan; Stair Analysis: Thu pro/rased amendment is supported by the Coinpre. nsiv4 Plt{rr and is consist Cid with the foI]owing goals and pc.heicw Land Use. Coal—1,1i-(i 1: Maintain and onhha tee the character and ci ialiivr of 1 ite in SpeiI attic Valley Land (Ise Cioal — LU -02: Provide for land uses that are essential to Spokane Valley residents, employees, and visitors. Land Ust: (]otil —1 .t1 -( Ensure that land ILISU plans, regulations, review processes, and irrtl^ristratcture improvements support economic grOW111 rind vital ity_ The change will simplify the process used to determine if development can occcir cm a lat. If a purchaser cliff riot have knowledge 'hall a lot was not legally cnrc:alccl they wit. still he able to develop tlru lot. Tlse changes. will eliminate inconsistencies with other monk:401 stile titles_ (2) The proposed amendment hears a substantial relation to public heaI1h. safely, wellnrv, and protection of the environment; Staff Analysis: The amendment bears substant: al relation to public health, safety, welfare and protectiem of the environment. The changes will correct inc rrtsiislarscres, protect innocentpureliascr. of ron-legal lets, and simplify and clarify the Mingling.. Cunclirsfnn(s): Tim proposed text amendment is consistent with the apprwal criteria contained in lite SVlvtC', 2. Finding and Cniaclusions Specific to Public Comments a. Findings: No public. cennnenls have been received to dale. b. C:unclusioi1 R): In thn absenue o!' publ is cnrnnients, staff makes no c ne1-tsions. 3. Finding and Conclusions Specific to Agcy Comments Findings: No agency coninments have been received to date. b, Cr nelirsioa(s): In the absence of agency comments, stafFniakes no Couclrisicirns, Palle: 3 taro Staff Report j |Re __kms m CTA -2017-{1003 C. OVERALL CONCLUSION. ']cproposed codetext amendment irii■e�nt with theCompreiwnic Plan policies and goals, e, m!'J± RECOMMEND AT1ON %SEmrcii s thnt rimming Commission recommend Eipproval or (t code text amendment to Cil Couni2i1 with Q]." c & - mg4oro S"pokane City Council Meeting First Reading Ordinance 18-004 CTA -2017-0003 Subdivision — General Provisions February 6, 2018 WU• 11 Cit N a4 a4 A � : A CI © 11. CJ N •P o o 4 4 (Categorically Exempt) PROCESS 0 •- 1 5 Study Session November 9, 2017 © Public Hearing tio December 14, 2017 1 Findings of Fact January 11, 2017 A* Ir m#' A A A Admin Report January 30, 2018 Ordinance 2nd Reading TBD Today Proposed SVMC Amendment Overview ❑ SVMC Chapter 20.20 General Provisions D Clarify legal lot definition ✓ Establish innocent purchaser and right to develop D Change border easement and ROW width requirement D Eliminate need for additional width on corner lots Eliminate lot depth to lot width restriction Change Flag Lot definition Eliminate development requirements based on "future" plans Minor grammatical, word & phrasing changes A Closer Look at the Substantive Changes Legal Lot Definition Establish a date, March 13, 1978, prior to 0 which lots could be created by means other N d than a subdivision process. (\I Identify criteria for establishing a lot was a) legally created prior to 1978 1-6 Innocent Purchaser Development Permit development on a non -legal lot by an O "innocent purchaser" p Define an "innocent purchaser" (\I Establish criteria for allowing development on } non -legal lots Border Easement / ROW Allow width at the intersection of two arterial �streets to be determined when development 0 occurs (\I Allow up to 15 feet of width versus requiring a a) minimum of 15 feet of width i— Update the corner detail illustration Corner Lot Width/Lot Width -Depth Ratio Eliminate requirement for additional width for 0 corner lots N p Eliminate maximum lot depth based on the lot (\I width 4) 1-6 Lot Arrangement and Future Acquisition Areas Eliminate City requirement to arrange lots 0 based on future plans d Future acquisition areas are being eliminated in (\I the Street Standards update N H Flag Lot Definition Q lot width Current definition is predicated on a minimum X 73 New definition does not have any dimensional c N requirements Q Q Q Other Change Minor grammatical, word & phrasing Changes to create consistency in referencing the SVMC Next Steps • Proceed to Ordinance 2nd Reading; or • Council Discretion CITY OF SPOKANE VALLEY Request for Council Action Meeting Date: February 6, 2018 Department Director Approval: Check all that apply: ['consent ❑ old business ® new business ['public hearing ['information ❑admin. report ['pending legislation ['executive session AGENDA ITEM TITLE: Motion Consideration: Street and Stormwater Maintenance Contract Renewal — 2018 Option Year GOVERNING LEGISLATION: PREVIOUS COUNCIL ACTION TAKEN: Motion to execute the Street and Stormwater Maintenance Contract on 10/14/2014. Approval of 2016 and 2017 option year. Admin Report January 30, 2018 concerning 2018 option year. BACKGROUND: This contract consists of asphalt repair, roadway shoulder repair and grading, gravel road grading, crack sealing, sidewalk and path repair, guardrail repair, fencing repair, drainage structure repair and installation, curb, gutter and inlet repair and installation, and other related work. City staff prepared a Request for Bids in 2014. The City received four bids and Poe Asphalt was the low bidder. The 2017 option year will be the third of four option years that may be exercised by the City. Per the contract specifications, the hourly labor rates will change based on the prevailing wage changes. Prevailing wages are required on this contract as the work is considered a "Public Work." The increases in prevailing wage range from 0.00%-3.62% ($0.00-$1.53 per hour) based on the specific classification. We estimate the increases in hourly labor rates will be about $10,000. We are not requesting an increase in the total contract amount as work items will be adjusted accordingly. Equipment and material rates stay constant for each option year exercised. Poe has provided a good level of service throughout the 2017 contract year and staff recommends exercising the 2018 option year contract. OPTIONS: Move to authorize the City Manager to finalize and execute the 2018 option year contract renewal with Poe Asphalt Paving; or take other action deemed appropriate. RECOMMENDED ACTION OR MOTION: Move to authorize the City Manager to finalize and execute the 2018 option year contract renewal with Poe Asphalt Paving, in the amount of $1,366,663. BUDGET/FINANCIAL IMPACTS: This contract will be funded by the approved 2018 Budget STAFF CONTACT: Bill Helbig, City Engineer ATTACHMENTS: Poe Option Renew Letter, 2018 Prevailing Wage Rates, 2014 Contract Spokane��' j�ney December 15, 2017 Poe Asphalt Paving, Inc. 2732 North Beck Road Post Falls, ID 83854 OFFICE OF THE CITY ATTORNEY CARY P. DRISKELL - CITY ATTORNEY ERIK J. LAMB - DEPUTY CITY ATTORNEY 11707 East Sprague Ave., Suite 103 • Spokane Valley, WA 99206 509.720.5105 • Fax: 509.688.0299 • cityattorney@spokanevalley.org Re: Implementation of 2018 option year - Agreement for Street and Stormwater Maintenance and Repair Services, contract number 14-223.03. Dear Mr. Poe: The City executed a contract for provision of Street and Stormwater Maintenance and Repair Services on November 21st, 2014 by and between the City of Spokane Valley, hereinafter "City" and Poe Asphalt Paving, Inc., hereinafter "Contractor" and jointly referred to as "Parties." The Contract Provisions states that it was for one year, with four optional one-year terms possible if the parties mutually agree to exercise the options each year. This is the third of four possible option years that can be exercised and runs through December 31, 2018. The City would like to exercise the 2018 option year of the Agreement. The Compensation as outlined in Exhibit A, 2018 Cost Proposal, includes the labor and material cost negotiated and shall not exceed $1,366,663.00. The history of the annual renewals is set forth as follows: Original contract amount .$ 1,366,663.00 2016 Renewal $ 1,366,663.00 2017 Renewal $ 1,366,663.00 2018 Renewal $ 1,366,663.00 All of the other contract provisions contained in the original agreement are in place and will remain unchanged in exercising this option year. If you are in agreement with exercising the 2018 option year, please sign below to acknowledge the receipt and concurrence to perform the 2018 option year. Please return two copies to the City for execution, along with current insurance information. A fully executed original copy will be mailed to you for your files. CITY OF SPOKANE VALLEY POE ASPHALT PAVING, INC. Mark Calhoun, City Manager Name Title ATTEST: Christine Bainbridge, City Clerk APPROVED AS TO FORM: Office of the City Attorney CONS RUC1'Tt1NT ACTRE M.ENT Poe Asphalt: Paving Inc, 2015 Street and Stnrmwater Maintenance and Repair SVP' 14-048 TEItS CONSTRUCTION ,ACIREEMENT (the "Agreement") is made by and between the City of Spokane Valley, a code City oftho State of Washington ("City") and Poe AThaftPaving Inc.., ("Contractor") jointly rcfLni d to as the "Parties". IN CONSIDERATION of tho terms and conditions contained herein die Parries agrees as follows; 1.. Work to Re Performed. Contractor shroll do all work and ftarxaish all labor, supervision, tools, materials, supplies and equipment and other items neeesaary for the con,strtictiou and completion ❑fthe 2015 Street. and Starmwatcr Maintenance and Repair Project (the `Work'") in accordance with documents dcstaibed in Exh ib it 1 and in acc;ordauar.e with:his Agreement (which are by this reference meoxrpootut humin and made Bait hereof (the "Contract Documenrs")), and shall perform any changes in the work in accordance with the Contract Documents. The terms oar d provisions in this Agreement shall control over any inconsistent err incompatible atible tonus in any other Contract Document. Contractor shall, for the Eonount set Perth in paragraph 4, below, asst me and be responsible for the cost and expense of all work ra;quirax[ for constructing and completing the Work and related activities provided for in the Contract Documents to City's satisfaction, withi o the time limits prescribed in the Contract Documents. The City Manager, Or designee, shall administer and be the pri many contact fur Contractor. Upon notice from City, Contractor shall promptly comma: nuaa WO rk, coin pl etc tic sane in a tin: ly manner, and cure any failure in performance under this Agreewent. Unless other -wise tlire.:ttd by City, all work shall be performed in ❑onfonnaataoe with the ContractDocumcnta, and all City, State and ficdcral a[andards, codes, ❑rdinanurs, regulations and laws as now existing oras maybe adopted or aainendcad. 2. Performance Period. This contract shall be in effect fiem January I. 2015 to T7eeeanb el 31, 2015. The City may extend the contract for up to four additional one year terms, which will commence on or about January 1 of each year and end nn Duccmber 31 of that year. The City wilt ive the contractor written notice of its intent to extend the contract at least sixty days hctbrc the contract term expire.. The. total duration of the Contract shall not escort 5 years, 3. Liquidated Damages. Tues not apply to this contract. 4, Compensatln%, in consideration of Contractor performing the Work, City agrees to pay Contractor in accordance with the. Coniraet Documents a total not to exceed $1,366,663 $aased on the bid submitted by thc contractor. 5. Payment. Contractor may elect to be paid in monthly installments, upon : iir❑soratafion of an application for payment in a foam sati&factoiy to City- Applications for payment shall be seat to the City Finance Department at the below stated address, Pursuant to Chapter 60.28 RCA', frve percent of the compensation due Con tractor shall be retained by City, Caastnaction Agreemena 13agn ] offi z3.1 t_1 -22_3 City reserves the right to withhold payment under this Agreement which is determined in the reasonable; judgment of the City Manager or designee to be noncompliant with the Contract Documents, City standards, City Code, and federal or state standards. 6.Di9tice. Notice other than applications for payment shall be given in writing as follows: TO THE CITY TO THE CONTRACTOR: Name: Christine Bainbridge, City Clerk Name: Joe Asphalt Paving Inc. Phone: (509) 921-1000 Phone: 208-777-0498 Address: 11707 East Sprague Ave, Suite 106 Address: 2732 N. Beck Road Spokane Valley, WA 99206 Pot Falls, ID 133854 7. Aoraicable Laws and S(undards. 'Elie Parties, in the performanceofthisAgreement, agree toeeri glywith a[1 applicable federal, slate, and local laws, codes and regulations. R. Certification Re rirdin' Debarment SIB ensign and Other I esnnnsibiIity Matters — Pa'imary Co vexed 'Transactions. A. I3y execrating tbis Agreement, the Consultant coli Lips to the best of its knowledge. and belief, that it and its principals: 1. Are not presently debarred, suspended, proposed for debairueat, declared ineligible, or voluntarily excluded from covered transactions by any federal department or agency; 2. Have riot within a threo-year period preceding this proposal been convicted of or had a civil judgment rendered against there for commission or fraud ora criminal offense in connection with obtaining, attempting to obtain, or performing a public (federal, state, or local)lrarsaction or contract under a public transaction; violation of federal or state antitrust statues or commission of embezzlement, theft, forgery, brit-ery, falsification or destruction of records, making fa]sc statements, or receiving stolen property; 3. Are nc t presently indicted for or otherwise criminally orcivilly charged by a governmental entity (federal, state, or local) with commission of any of the offenses enumerated in paragraph (A)(2) of this certification; and 4. Have uot within a three-year period preceding Ihie application/proposal had one or more public transactions (federal, state, or local) terminated for cause or default. B. Where the prospective primary participant h unable to certify to any of the statements in this certification, such prospective participant shall attach an, explanation to this Agreement. 9. )prevailing Wages on, Public Works. Contractor, any subcontractor, orother person doing work under this Agreement, shall comply with the requirements of RCI ' 39.12, and shall pay each employee an amount not less than the Prevailing Rate of Wage, as specified by the Industria[ Statistician of the Washington State Department of Labor and industries ("I,&T"). Ifomploying labor in a c]ass not shown, Contractor shall request a determination of the correct wage rate for the class and focality from the Industrial Statistician, Contractor shall provide a copy of any such determinations to City. Before commencing, during, and upon completion of the work, Contractor shall file all forms and pay all fees required by l:.&I and shall indemnify and hold City harmless from any c[airns related to its failure to comply with RCW 39.12. Construction Agreement Pale2of6 The following inforrnatic n is provided pursuant to ROW 39-12.03O: A. State of WaslUngton prevailing v a e rates applicable to this public works project, published by L&i arc located at the L8a website address: haps:llfcrtress.wa.gov/lnilwagelnnkupl ry a c]ookiip.as B. This Project is located in Spokane County. C, The effective prevailing wage date is the sane date as the bid due date as referenced in the nriginat request for bids and as may be revised by addenda. A copy of the applicable prevailing wage rates is also available for viewing at the offices of City located at 11707 East Sprague, Suite 106, Spokane Valley, WA 99206, Upon request, City will mail a hard copy of the applicable prevailing wages for this project. I0. Relationship) of the Partics. It is understood, agreed and declared that Contractor shall be an independent contractor, and not the agent or employee of City, that City is interested in only the results to be achieved, and that the right to control the particular manner, method and means in which the services are performed is solely within the discretion of Contractor. Any and all employees who provide services to City under this Agreement shall be deemed empIoyees solely of Contractor, Contractor shall be solely responsible for the conduct and actions of all its employees under this Agreement and any liability that may attach thereto, 11, Ownership of Documents. Al] drawings, plans, specifications, and other related documents prepared by Contractor tinder this Ag-'eenuent are and shall be the property of City, and may he subject to disc/o=re pursuant to RCW 42.56 or other appiicah[e public record taws. 12, Records. The City or State Auditor or any of their representatives shall have full access to and the right to examine during normal business hours ali of Contractor's records with res?ect k, ail !natters covered in this Agreement. Such representatives shall be permitted to audit, examine and crake excerpts or transcripts from such records and to make all dits of aaMI contracts, invoices, matcdals,payrolls and record of matters covered by this contract for a period of three years from tlae date final payment is made hereunder. 13. Warranty. Un less prc vi Jed of her vise in the Contract Documents, Contractor warrants that all Work and materials perforated or ins_ailed und+:r this Agreement are free from defector failure for a period of tine year following final acceptance by City, unless a supplier or Manufacturer has a warranty for a greater period, which warranty shall be assigned or transferred to City. in the event a defect or f'a_lurc oc:eurs in work or materials, Contractor shall, within the warranty period, remedy the same at no cost or expense to City. This warranty provision shall not be cons need to establish a period of limitation with respectto Contractor's other obligations under this Agreement. 14- Contractor to Be Licensed And Bonded. Contractor shalt be duly licensed, registered and bonded by the State of Washington at. ail. limes this Agreement is in effect, 15, insurance. Contractor shall procure and maintain for the duration of the Agreement, insurance against claims for injuries to persons or damage to property which may arise from or in connection with the performance of the wort{ hereunder by Contractor, its agents, represeotathg s, or employees. A, Minimum 5 cone of Pnsurance, Contractor shall obtain insurance of the types described below: Canslauction Agree so Page 3 of 6 1. Automobile liability insurance covering all owned, non -owned, hired, and ]eased vehicles. Coverage shall be written on Insurance Services Office (lSO) form CA 00 01 ora substitute form providing equivalent Iiability coverage. If necessary, the policy shall be endorsed to provide contractual liability coverage. 2. Commercial general liability insurance shalt b c written on ISO occurrence form CG 00 01 and shaL cover liability arising from premises, operations, independent contractors, pi oduats- completed operations, stop gap liability, personal injury aid advertising injury, and liability assumed under an insured contract. The commercial general liability insuriance shall be endorsee: to provide the Aggregate Per Project Endorsement ISO form CG 25 03 11 85. There shall ben° endorsement or modification of the couonerclal general liability insurance for liability arising from explosion, collapse or underground property damage. City shall be named as an insured -under Contractor's continaercial general liability insurance policy with respect to the work p erfotined for City using ISO Additional Insured endorsement CO20 10 10 01 and Additional Insured -Completed Operations endorsement CG 20 37 10 01 or substitute endorsements providing equivalent coverage. 3. Workers' compensation coverage as required by the industrial insurance laws of the Stain of Washington. B. Minimum Amounts of Insurance. Contractor shall maintain the following insurance limits: 1. Automobile liability insurance with a minimum combint=dsingle limit for badilyinjuryand property damage of $ 1,000,000 per accident, 2. Commercial general liability insurance shall be written with limits no less than 5 f ,000,000 each occurrence, $2,000,000 general aggregate, and a 52,000,000 products-cornpleicri operations aggregate limit. C. Other Insurance P3Qvis torts. The insurance policies are to contain, or be endorsed to contain, the following provisions for automobile liability, professional liability and commercial general liability ins'nrance: 1. Co rar or's insurance coverage shall be primary insurance with respect to City. Any inswanre, self-insurance, or insurance pool coverage maintained by City shall be excess cf Contractor's in urence and shall not contribute with it 2, Contractor shall fax or send electronically in .pdf format a copy of insurer's cancellation notice within two business days of receipt by C.,nntractor. D. Acceptability of insurers. Insurance is to be placed with insurers with a current A.NT, Best rating of not less than A:VI7. E. Evidence of Coverage, As evidence of tho insurance coverages required by this Agreement, Contractor shall furnish acceptable insurance ceriificares to City at the time Contractor returns the signed Agreement, The certificate shall specify all of rho parties who are additional insureds, and will include applicable policy endorsements, and the deduction or retention level. insuring commies or entities arc subject to City acceptance. If requested, complete copies of insurance policies shall be COnsir c ion Agreement Page 4 of provided to City. Contractor s]ta]l be financiallyresponsible for all pertinent deductibles, self-insured retentions, and/or self-insurance, 16. Indemnification and Hot 1—tararless. Contractor shall, at its sole ex0en213, defend, indemnify and bold harmless City and its officers, agents, and employees, from any and all claims, actions, suits, liability, lass, costs, attorney's fees and costs of litigation, expenses, injuries, and damagea of any n aturc whatsoever relating to or arising out of the wrongful or negligent acts, errors or omissions in filo services provided by Contractor, Contractor's agents, subcontractors, subconsultants and employees to the fullest extent permitted by law, subject only to the limitations provided below. Contractor's duty to defend, indemnify and bold harrn[ess City shall not apply to liability for damages arising out of such servicos caused by or resulting from the sole negligence of City or City's agents or employees. Contractor's duty to defend, ill damnify and hold harmless City against ]iahi!ityfor damages arising out of such services caused by the concurrent neg]igenea of (a) City or City's agents or employees, and (b) Contractor, Contractor's agents, subcontractors, suboonxuftants and employees, shall apply only to the extent of the negligence of Contractor, Contractor's agents, subcontractors, aubconsultnnks and employees. Contracto?s duty to defend, indemnify and bald City harmless shall include, as to all claims, demands, losses and liability to which it of plies, City's personnel -related costs, reasonable attorneys' fees, and the reasonable value of any services rendered by the office of the City Attorney, outs idu consultant costs, court costs, fees for collection, and aI] other claire-rr latcd expenses, Contractor specifically and expressly waives any immunity that maybe granted it under the Washington State Industrial Insurance Auk, Tido 5111.CW. These indemnification nifrcation obligations shall not be limited in any way by any limitation ou the amount or type of damages, compensation or benefits payable to or for any third party under workers' compensation acts, disability benefit acts, or other employee benefits acts. Provided, that Con tractor's waiver of immunity by the provisions of this paragraph extend only to clsirms against Contractor by City, and does not include, or extend to, any claims by Contactor's employees directly against Contractor. Contractor hereby certifies that this indemnification provision was mutually negotiated, 17. Waiver. No officer, employee, agent or other individual acting on behalf of either party has the power, right or authority to waive any of the conditions or provisions of this Agreement. No waiver in one instance shall be herd to be waiver of any other subsequent breach or nonperformance. Ali remedies afforded in this Agreement or by lav, she:1 be taken and construed as cumulative, and in addition to every other remedy provided herein or by law. Faihtre of either party to enforce at any time any of the provisions of this Agreement or to require at any timo performance by the other party of any prrvisiun hereof shall in no wily be construed to be a waiver of such provisions nor shatl it affect the validity of this Agreement or any part thereof, 18. Assitrnment and Dele Hatton. Neither patty shall assign, transfer, or delegate any or all of the responsibi[it[es of this Agreement or the benefits received hereunder without first obtainingthe written consent of the other party. 19. Con ideiit Bt. Contactor may, from time to time, receive information which is deemed by City to be confidential. Contractor shall not disclose such information without the prior express written consent of City or upon order of a Court of competent jurisdiction. 20, Disn u,fe ;. All disputes s rising under or related to this Agreement that cannot be. resolved through informal Coias(ruction Agreement Page 5 of6 discussion and negotiations shall be resolved by litigation filed in the Superior Court for Spokane County, unless otherwise required by applicable federal or state law. 21, Subcontractor Responsibility. As required by RCW 39.06.02i}, Co-itractor shall verify responsibility criteria for each first tier subcontractor and its subcontractors of any tier that hires other subcontractors shall verify respon,s ihi lity criteria for each of its subcontractors. Verification shall. include that each subcontractor, at the boon of subcontract execution, meets the responsibility criteria listed in RCW 39.04.350(1) and possesses anielectrical contractor license, if requiredbychapter 19.28 RCW, or an elevator contractor licenseifrequired by chapter 70.87 RCW. This verification requirement roust be included in every subcontract of every tier. 22. Jurisdiction and Venue. This Agreement is entered into in Spokane County, Washington. Venue shall be in Spokane County, State of 'Washington. 23, Entire Agreement. 'itis Agreement constitutes the entire and complete agreement between the patties and superccdcs any prior oral or written agreements. This Agreement may riot be changed, modified or altered except in writing signed by the Parties. 24, A nti-lcickback No officer or employee of City, having firepower or duty to perforin an official act or action related to this Agreement shall have or ai quire any interest in this Agreement, or have solicited, accepted of granted a present or fhturc gift, favor, service or other thing c -f value from any person with an interest In this Agreement. 25.Business Rer<isfratinn, Prior tocornmencernento€Work under this Ag enlent,Contractbrshallrefgister with the City as a business. 26. Sever ability, If any section, sentence, clause or phrase of thus Agreement should be held to be invalid for any real on by a court of competent jurisdiction, such invalidity shall riot affect ttie validity of any other section, semeneu, clause or phrase Df this Agreement. 27. Exhibits, Exhibits attached and incorporated into this Agreement are: 1, Contract Provisions — Slrcct and Stonnwatcr Maintenance and Repair Services 1 Contract Rates 3. Tiisurrarlce Endorsements 1 The Parties have executed this Agreement this day of ifittelettei , 20/7 CITY OF 81'0/ONE VALLEY: ATTEST: ristinn Bainbridge, City Ierk Cons Lruclion ,Agroc[a2nt APPROVE r AS TO FORM: Office the Ci r orney Page 6of6 SPokane .ssago*Valley 2(175 Street end Stormwater Maintenance and Repair Contract Bid Proposal Form The wrtfersrgned Indiv!dual represents and warrants that he or she 1s truly au rized to ersecoto the brd on behalf of any partnershIp, pint venture or corporation. **The hours below represent an average year and are subject to change Company Name: Signature' Printed Name: SCHEDULE A - REGULAR HOURS Estimated Item # trade Occupetron Reg*IHours**+ Mate Total 1 Foreman 5001 sit, 32. 27 160 , P.tnementMasons Journey Lever 240, &4o b 3 Fence Erectors Fence Erector 211 11. loci 4 naggers Journey Level 1900 G.,,1,5 b 5 Laborers General' Laborer 2300 120 Lit,Tfp ,,, .115,2- 1O 0 22.1g. en 54 5c14 . q b 6 Lab ore rs Asphalt Raiser 7 Laborers Concrete Crewman 220 -- 19rib urr, ..r. /1{l 71i Erb ii,fl....' - — 9 10 11 12 Lab °Nis Laborers Power Equipment Operate -s !Power r.qurprnent Operatct'S 12 flower Cqurpriu rd. Ctperatcars 14 15 16 Power Equipment Operators Power Equipment Operato-s Power Equipment Operato-s aro nor Pipeiayer Traffic Control. 5upervlsor Blade (finis h & bruetap) H.D. Mechanic Paving 1v12chlrre Rorrerman Screed Operator Power Broom 17 Power EquTpmerrt Gperato-s lg F'ower Equipment Operators 19 Power Equipment Operators 6ackhoes & Hae Cram Vactor G'1z7Eer, Super Sucker Roto hill 20 Power Equipment operators 11 Power EgtalprnentOperators Post hole Auger or Punch Datkhae (45,00 GW & under) 130 f40 3 `7,511 14 ,74 if Vib.trb �►.ta9.11,0 200 5z.g7 1450 . I 90 .37 :11J;1 30 624;1 ?f5-R.Jq teD. b :7 22 Truck Drivers Dump Truck (E, WA -G90) 800 LiCi. 91Z. 1b 23 Truck Drivers Dump Truck & Trailer E. A -690J 504 q 12 24 V. CZ 24 Truck 0revers Other Trucks (E. WA -59D) 20 "7 .7 W 1 t Liqtc, .22 25 Truck Drivers T'rans(t Mixer 11 441 . Schedule A - Regular lfiours 2Z . 421.47D SCHEDULE 5 - OVERTIME HOURS 26 2.8 30 31 32 33 85 36 37 35 39 L10 41 43 44 Trade Occupativn Es"Imaterf 07 Hours Rate Cement Masons Fence Erectors Naggers Laborers Laborers Laborers Laborers Laborers Foreman 40 70. Total Journey Level Fence Erector IDUIT1211 L@veI General Laborer As•ha[t Raker Concrete Crewman Guard Rai[ Laborers Power oer Equipment Operators Power Equipment 0peratcrs Power E q u l me 11t Operators Power Equipment Operators Ply elayer Traffic Control Supervisor Biade(finish&biueto ) 20 H.D. Mechanic Paving Machine Rollerrnan 5 50 75 20 5 $,5 5 20 bb, 208 qii"7.,trD 476 .q1 2 c1-10. Sof. 1 D.1 1 91 1 b .qb 20 40 ip(..b -711422-, 16,2/, (ower Ego Ipment erat:vs lower Equipment Operators Power Eq ul pmcnt Operators tower Equipment; [lower E tri meat Operators 45 Power Equipment Operators Screed Operator Power Hro;:m Backiioes & Hae Ram Vactor Guzzler, Scup°r Sucker 20 10 477.4 _1ipi1.12. i.4L1I -y. ip Rota Mi[I Porthole Auger or Punch 5 AG ('ower Equipment Operators Borkhae (45,000 CW & under) 47 Truck Drivers 48 Truck Drivers 49 Truck grievers 50 Truck Drivers Dump Truck (E. WA•590) 'Dump Truck & Trailer (E, WA -690) other Trucks (E. WA -9D) Transit Mixer 30 5 40 1.0 5 Zg1.1-22-- ET, CD 440. • . b 4 .CD 75.20 et D /02 :7L 2.1 j 26- Schede a [3- Overtime Hours 1. b7 SCHEDULE C- EQUJPMENTTOURS Item 0 Equipment Type Unit Ty. a quantify Hourly Rate Total 51 1 Ton Truck Hour X00 1 ` .SV 1 TED. . 52 1Ton/Trailer Hour - 25 150 - 250 if..edgy 1. ,1 b 1'L76 0.2.5' J# D b 1 7.Sb 53 1/2 Toll Truck Hour Hour 54 160 Blade 55 3 ,i I E TrJt Tra&l or Flour 16 if 0 , i 2$ 715 56 5th lapel/Lowboy Hour 125 ' .I 11 r+; .` 67 Arrowbaard Day 50 l03#. z 1 L .5b + . t _ . _ 59 Backhoe our Hour 60 61 Broca Broom 64 65 66 67 58 Chop Saw Crac*JJolot Sealer IDD -110 Roller or E.uivalexrt DD•S4 Roller or Equivalent 70 71 72 73 74 75 Fred Dump Truck End bump/rup Grade Roller Hoe Pack Jumping Jack Wacker Nuclear De sorfleter Hour Hour Hour Hour Hour Hour Hour Hour Hour Hour 25 75 77 Paver Plate Wacker 5RlpbY Super Dump Traffic Coque' Vehicle Variable Message Sign, Water Truck - LG 78 Water Truck -5M Hour Hour Hour Hour Hour Hour Day Hour Hour 150 250 50 300 1o0 200 35 20 30 150 150 10 200 450 400 .d$1) 11.Gb iso 104 f. ° 1 ip 11.51 1-12,14 STJ Tri313g,d 2 'Ego b. 54 6 .26 Z. trb 9 iaGs 40 .24i 200 +� „To ?00 4 Schedule C - Eguipmerbt Hours 217 1 3r7 2 . L5'd) 1r) . - -761. 0 [ ID SD 11 g b.0 le 10 15D SCHEDULE D - MATERIALS Unit Prices !nein d❑ materials only. Labor and Equipment will be paid separately. Item it Materiel Typo Unit Type Chiantity UnitPrlce Total 79 80 WMA "J/8" P G 64-28 5O Gyro HMA 1J2" PG GI.28 50 Gyro 81 HMA 1/2" PG 70-28 75 Gyro Tail 500 Ton 3500 Ton 2200 1,#ibb. 53•is 203 3 82 IUUMA 1/2k PG 70,28 100 Gyro 83 CRUSHED SURFACING TOP COURSE Ton 500 Teri 0 LRIISHEV SURFACING E5 ASH 84 COURSE gr, GRAVEL BACKFILL FOR QRYNEt,l S Ton 22 1 1q6. `- 1500 G. Ton 200 05,25 700 f 4 86 TACK OIL PRECAST CONCRETE DRYWELL 87 TYPE A Gal krr CA moo 2 ,1v$ PRECAST CONCRETE 0RYI\FELL 5Jx TYPJ:l3 89 90 91 CATCFI VAS EN TYPE 1 CATCH BASIN TYPE? TYPE 1 Ir4LE1. 92 GRATE 'INLET TYPE 2,}SOOT EA EA EA k+� EA 7 4;1.24 310 11111. 4-11b12, 7 1S-5/LIB 5 125'1.25 3 Poo. o 3IUV* q Stheduie D -Materials SCHEDULE A SCHEDULE 9 SCHEDULE C SCHEDULE D TOTAL 5CI-fE'DtJLE A-0 F,51 -1S,111 inzt t. bo S31 qgt.ol ''7l 241. 2 t i.tisi,'t fib J. o .Zi • CERTIFICATE OF LIABILITY INSURANCE POEASPH-01 CASHBY DATE IMM,DD,' CC ) 1111412014 THIS CERTIFICATE IS ISSUED AS A MATTER OF INFORMATION ONLY AND CONFERS NO RIGHTS UPON THE CERTIFICATE HOLDER. THIS CE=RTIFICATE DOES NOT AFFIRMATIVELY OR NEGATIVELY AMEND, EXTEND OR ALTER THE COVERAGE AFFORDED BY THE POLICIES DELOIN, THIS CERTIFICATE OF INSURANCE DOES NOT CONSTITUTE A CONTRACT BETWEEN THE ISSUING INSURERS), AUTHORIZEC REPRESENTATIVE OR PRODUCER, AND —HE CERTIFICATE HOLDER. IMPORTANT: ft the certificate holder Is an ADDITIONAL INSURED, the purlcy(Ies) must be endorsed. it SUBROGATION IS WAIVED, subject tc the terms and conditions of the pulley, certain policies may require an endorsement. A statunent on oris certificate does riot confer rights to the certificate holder in lieu of such endol'sament{s), PROPUcaR Stonebraker 1ilcQ1.4aryl 616 6th S!, PO BOX 9' Clarkston, WA 911403 INSURED. Pao Asphalt Paving, loo. PO B» 449 Lewiston, ID 83541 COVERAGES .r,1TACT N0.MIk� II ..- PrrONEFJ'a -rJ� 6 f t, No$ 7O:1'}758-5311 }Arc, Na Earp E-MPIU- ADDRE9S1 INSutER{SI Mr 4I JJHGCOVERAOL INSURER A:Pllaenix ensuranCe Company IN suRER B ; The Charter Oak Fire Ins Co JN uRERC; Tr voters Properly Casualty Insurance Company INSURER a ; Idaho State Insurance Fund INSURES E:Ohl o Casualty Ins Ca INSURER F LAIC 1i 25823 _1 26815 36161 37126 24074 CERTIFFCATE NUMBER: REVISION NUMBER: THIS IS TO CERTIFY THAT 1HE POLICIES CIF INSURANCE LISTED BELOW HAVE BEEN ISSUED —C THE INSURED NAMED ABOW FOR THE POLICY PERIOD INDICATED. NOTWITHSTANDING ANY REM IREMENT. TERM OR CONDITION OF ANY CONTRACT OROTHER DOC UMEHTWITH RESPECT TOkM-IICWTHIS CERTIFICATE MAY BE ISSUED OR MAY PERTAIN, THE INSURANCE AFFORDED BY THE POLIO ES DESCRIBED HEREIN IS SUBJECT TOALL THE TERMS, EXCLUSIONS AND CONDITIONS OF SUCH POL CIES- LIMITS SFIGV N MAY HAVE BEEN REDUCED BY PHD CLAIMS. CYR IFR �.�.- INSURANCE ADDL SUER, cv W �C,tiFi F !r{iLICY EXP LIMITS A X carom ERClALGENERAL LIAEILITY EACH5GCUnRENCE $ 1,000,000 PREMISES [Ea 4> mance} 6 300,0041 MED EXP hurl' me ilemsn1 S 10,0001 EI CLAIM .MADE 1 X 1 aeOLPR GENT AGOREUA1F 1 Iy.,T APPLIES PER: POLICY! X PRO- JECT 11 L LOC 0111. A1Ix(7MOr9LE LIABILITY X X c X ANY AUTO ALL OWNED AUTOS H IREO AIJTns X UM DRELL!, LIOk 3 O CESsLI,a SCHEDULED AUT4s Nem:MED AUTOS X X OCCUR CLAIMS-MAAOE UaU 1 X RETENTIONS 10,000 WORKERS COM. PENSAT1Ord AND EMP LGYERS' LIABILITY D FAY PROPRI c foRJPARrNERfrXEGUTI4E Cr FICERAIEd'.0ER EKCLUDE0? �r+l ar•dalury In Nil re 0.8, d6snrhe under DESCRIPTION OF OPERATIONS trelaw E E YIN rlulpment Floater N7A DTCO1537P996PHX14 f]T9101637P996C0F14 DTSMCUP9537P99STIL14 678561 11151/2014 11/0112014 1119112014 10101,12414 11!0112015 1110112415 1110112015 1 J1011201B W4101555611380 1110112014 11i0102015 PERSQFL4L. $ AfiV INJURY g 1,0 0,1100 GENERALAGGREGATE • 2,000,1100 PRODUCT6-0CfsINQPAGG 2,000,000 COMBINED SC♦ Ewr{ [fa. ocassrlk1 BODILY INJURY (Per peso) • 1,000,000 BOaILi' INJURY tPeracarrEt Il $ PROPERTY DAMAGE 1Par aacdderiI $ 1 ERCN (1CGURRENCE AGGREGATE 5 4,000,000 4,000,4401 ISTAME E,L. EACH ACCIDENT OTH- ER 600,000 E.L. PI$FA.S F. • FA EMPLOYEE 800,000 E.L DISEASE • POLICYLIMIT 500,000 Leased Hirod Rented DESGRIPTl0NOF0P1RAT1ONSlLOCATI BfVEHICLES{,CORP1a1,AddItIonerReworksSchedule,mayheetLaandMTarnsmeceIsrequIrodp This Certificate of Insurance neither affirmatively nDr negatively amen de, extend, nor alters the coverage, afforded by the policy or policies nurnhered itt 1411$ cortiileete, Tho City of Sp kahe Valley Is additional! Insured an general (lability as respects the 2015 Street & StDrmwater MaIntenance project. insurance Is Primary end NonOnuhrlbutoryr. CERTIFICATE HOLDER City {xf Spakano Valley 11707 E Sprague Ave Ste 1 13 ,5pokane Valley, WA 99208 CANCELLATION SHOULD ANY OF 1 HE ABOVE DESCRIBED POLICIES eE CANCELLED BEFORE THE EXPIRATION DATE THEREOF, NOTICE WELI. RE DELIVERED IN ACCORDANCE WITH THE POLICY PROVISIONS. AUTI- 5WMEC REP RSENTA1WF 1688-2014 ADORE) CORPORATION, AI/ rfyhts reserved. ACORD 25 {2014101) The ACORD name and logo are registered marks cf ACORD .00"a . OND tri; 10614 2027 C0.,hAICTOR1s PAYMENT BON» NON -FT FUNDED FROSEC ij to Lily of Spokafle Valley, Watikingtan T`sc City of Spcl ante Valley, Wasktirtg on, in Spokane Cou aty, has awn d€d tc Poe WW1. F3ui J Inc. (COMME1410, r), as Pritt:icelr r< contract ibr the crnmstrurtioa of the.piJe.er designated as 2(115 fir nd Storrirn' er h to ee And Rep air, I'tgj No. )#- irR Spokane Valley; W,litsleinvom, and sxdd 7imttip8l is required under the (ems of lit Contract in &rt,ishapayni ritbondtoacrordancetuiOrclha rer34.0$1RevisedCott ofWashirtgt1U(RC1'). The PlineiPal, sualtyandof-kneri1R, (Steel}'), a cot;. oaaoru organized ter the 18wA.of Connecticut and lieeusedto dobik.idess in. tine Slate of Wnsliiwina as surety and ramtd intim matfett 1i51 of "Surety Onmpanies Acceptable in Paull Bonds" as published ,n the Federal Register by die Audit Sin f' 1)atxeat► of Accu iril$, U.S_ Treasury Dep:,, tde failtty and severally, held and far C} bound to the Ciao t r Spukarte Yh1ky, as Obt 4ei, in time tum nfS1,365,663 total Contract =dam {.ittclutding State sales vis). subjct to t1t� la i ia,c thein_ ' 3his payment bond dad, become. null and void, if and when the Principal, its 3aess, exec utr)rs, adminiaammitors, 3u g5s tpta, or 'anion shalt pay all persons in atccoadeu�'toc with chapters 39,01# and 39. ' 12 RL , indndittg ail wnrkets, lakmr€rr, mechanics, subenntraotoo, and nratetistlmen, atzd all persons wito shall supply stat contactor or subconu'atlor with prOv15ionS find supplies for the eaffying viz of 9ud11 wart; And shall indemehfy' and hold harmicr a the Obligee !mai all loss, cost cd damage 3vhith Oblisec May CiAlet by root► erf Ike failure` of Principal to rake 904 requited payments; raid if ittcit Parmit ebligations have not haat fu1Gllasd, this Ewald shall remain in 0il1 lora and efffsCL The Sunray for vrtlivo remivcd ap x6 Ilkat dines, r tensiem of *Ps, alttxation or addition to the terms cifthe Contract, the specifications aortawring the Contract, of to the w.Oric be perforated tuner the CAMEIRCI 5lmll lit Baily way sea It obligation ne rk s trona except as p ovic{ed herein, dv.aiv sii tiee oi•any itta iga, extension of tktx]e. elterotion of addl4oai m the mins of the Contact or the vrork crfrorr ed The Surety agrees that modifications and changes to the ternms and c rditins of +ore CnsiUac: that incrv13aa the total 2mowxt t m be' paid the Pni3el 101121.1 aucnirtielatC aPly iOgrease the 013 /10211511 OF, sway on trim bn7d. and artier to Suretyai nntrequired for ouch incfea5ed obligation. This bur% t +ay b mowed in mo original enurxeiparis, and slialL be signed by die peutics' duly trttlhorixed officers_ This hand will tale he accepted if it is accompanied b'[ a fel lyr cxoculcd and anginas!. pnw¢r of attorney fur t113 officer exacvting. au behalf of surety, i 121j4 P inc;pot r aeu Uate Printed Nan _ P WN i4 NAti;l R Title SRFTY rs C-jsualty o ety Camnpa ny or America : 5 Lay Surety Sigrature Cheryl Ay Pillaged Name Date ❑ tprrsoi In Fact Title Name, add os, and ulephorie eflat2t PAi4gthRetU ofS,arery COni .PY is' star.draker McCtnarY+49 Y 5819-756557 PG Bog 9 Clarkston WA 994P3 TRAVELER ALIO 11 rh'-ro fMet \o. WARNOX THIS POWER OF ATTORNEY IS INVALID WRHOUTTNB RED BOFCIDFR POWER OF ATTORNEY I+arnttngltua Caisnttlty Conipa ray Fidelity and Guaranty Insurance Company Fidelity and Guaranty insurance Underwriters, Inc. St. Paul Fire and Marini Insurance Company St- raid t rardian Insurance Company 227798 SI. PEIul ilicruiry 11ISilrii#ICe Crnnparay Travelers Cauuulty rind Surety Company Travelers Casualty and Surely Company or America United States Fidelity and Guaranty Company l.ieule No, 005960119 KNOW ALL MEN RY Ti F.Si: 1'RESFaN'I-S: That Farmington Casualty Cwiglasiy, Si. Paul Fire and hfarinc insurance Cunipuuy, Si. Paul a ardi i Insurance Company. St- Paul Mercury Insurance COnp>caly, Travelers Casualty Trod Surely Company, Travelers Casualty anti Surly Company or Arrnurii:u, Mid Untied Startes Fitkllly and OnMranly Company arc corporaurnr_s duly organized wider the Taws n( Ilio State of Canmcd cul, that Fidelity and CJUuranty Insurance Company is a corporaticnn &Idly organized under the laws. of 0I.0 Siaie of Iowa. and that Fidcliiy and limn -drily Insurance --I nderwriters, Inc-, is a corporation duly organized under the laws of the Slue of \rfiscasriin hen Ln oulkxir.chy called diie "Comp,nlires" ). arid &hal the C'ampunies do hereby snake, cOlOilinlo and appoint Cheryl Ashhy, Della 1, Allen, James M. Hewitt, Kurtal J. McBride, Liti+ismith, Vonda Hail, 1?obcrl E. Krtiler, Shuman Siaybaugh, Ikoland'tyiornasor, Durr McQuary, and Lesha Lehmiti cif flit (.I(1 �r Clarkston , State ar WashingtonMu it Iruc ,nue Ii rte] At6nn.cp?sJ-in-Fact, cacti in !heir Nupar,lte capacity if nWrc Engin one is narncd arbauc, to sign, cxa [rte, .peal alit) iurkli erigc ILISF :aiYiI MLI brands, rC{'ngr izinlw s. conditional t dart old rig:- aria nncC: wriLi1 i uhligatory in the nature thereof an behalf or the Companies in iheir business of giumi teeing Ilia tiJelity of persons, guurnnicciug the perlamt rare a, cu r iralel'. and csecurinJ; nr Gnnrunrccing bonds and undertakings required or permitted in any netkinS or proceedings arlIou+edl by I;drv, IN WI'INI SS 4V11EREOF, the Compyiii h:rvc Caused this instrirraent to he signed and their corp.:mac w urs to bw< henna affixed. this Juno tiff 11; 'of Slots: of Connecticut Ciiy or Flaiifard h%.. Farminglun Casuulky Company meaty and Gil 'wanly Insurance Company Fidelity grind Gu urniilp insurance Underwrlkrs, Inc, St. I'auI fire and Marine Insurance Company St. Poul GI la Mian 1nsilrance Company 25th Si,. Paul Mercury Insurance Company Ti meters Casualty and. Surety Canipuny 'I7avclem Cstsu illy anti Surety Company or Alperin llnitcal Staten Fidelity and G uairnnly Company 25th Jule 2014 On Ihis the day or .. __— . before rate persuually appeared. Robert L, Raney, who acknowledged himself to be the Senior Vico President of Forminglon Cn uulty C mpnrly, Fidelity and Guaranty Insurance Company. Fidelity and Guaranty Insurance Underwriters . tree„ 5t. Paul Fire and Marine Insurance Conipciny, St, Parra Guardian ]nsuruncc Curnpsiny, Si. Paul M rn tiry Insurance Company, TraVelcrs Casualty IYIHJ SUCLy Cbr]ipwuly, Travelers Casually and Surely Company of Anferica,;Mull Uniled States Fidelity and Guaranty Campinry, arid that he, as such. being authorized SD to do. executed the foregoing instrument for ibe purposes therein contained by signing urs behalf of !he.. cni pora do ns by himself as a duly authorized aIfie& ', la Witness Whereat, i Iturealuto NCL my hand x.11{1 official seal. My Commission cxpiICS the 30t1] day or Ju110-2016. 58440-8-12 Printed In U-S.A- WARN ING:TH.IS POWER OF ATTORNEY IS INVAL ir1 e . .. Manic C. Teirriryrt. tv'7rinU Public I U. +. I E `ED BORDER F3OND NO! 1O6142O27 CONTRACT0R'5 PERFORM NCE POND to City iirSpDkaneValtRyiWafhtngtcat The 4r Elpok'ane Valfay, vhishblon, in Spokane !Dainty, Las aWa fed iv koc F L0italt Yawing 1*. (OfdttraelOT), $fi Principal, tw conarect fpr the eensb'ucllion of the: projccr desipated as2nd Sire t tendSs emWakr M intenaa� atLd F,op r _Pr+ije;:t. f`1o. j -4)I$ In Spelt/sae Valley Washington, and said Principal it required under the tarots ate Ca !race to fthrrush a perfoln w.Gebond in accordance with diaster 39.08 Reused Code of Wa1un, act (RCW). The aauip.,Q, and Travelers Casually and Sure Ct nn.any aiAmericra (Suety), a carpatetiOD. oigattil ed Linda the laws ofConner.lir.^I and llcettsad. Lo do bosihress in the Stale of Washington ass xbr and turned in Lha current Sist of "Stacey (ox ranks neep4E131e in 'Federal Bvtx(s'- 2s published idrt the Federal P,cgistex ! y thc Audit S t1T'15urcau of Accounts. ILS. 'FL-CR/157y P ., a iadntly and scvcrallybeld mrd 61m1:11yboundt2 IEw City of'SpoEni Valley, as Obligee, ir. the sal of S1,364,6 . taia.l Cppaact aasowit [iru lading Magtcn Skew 5a1ca tax), subject t4 he provisions herein_ his perfvrmarto botxt shall become null and v if and +alien the Principal, its ]wits, executors, administrator r successors. ox R.56.4 45 shill uretl Ltd faithfully perform all of the Frincipara o141106i014 is der tlit Cpittilt and hlrll atl the 1211COS mud conditions of all duly authorize -4 ❑di caQ1 , }dditzona, wururAel e.i as Said Coiitracr that may hereafter be made, at the time and in the Alatlt]er i6, reint sped frail, fhalt1 sxtitronty ib . wok as prrn dad it the Contract and abs1i inckanify and hold harnatcas the Obligee FrtY.tt any (ideas in the w4rtmamhip and materials incotpaxated into the wank liar the period ids iIi`cd in the oto. t; and if sia:h pei-feertiatiov abligetioha has not bm fal61]ed, this bend alhall remain in full trail lelefi efFact The Suitt' for Value yeccjvcd racts tart no O.0.*, c tnitskin eftime, altcratiox ar additions ro dee tam oftlte Cot>xnaci, xlie specifI marc s accompanying the Coutin.c1„ ar torte h3Cr}- to be perfasrmd unlet the Contxacc Shall in any way nff❑ct itS oblirRaliara an this bore, and varves notice of An Fringe, Clc.0.8n6tou ottima, alternlior or addition to the terms of Eha Ccalimet or the work prformal. T15e Safety agrees thin r ioalif`,catiot 844 changes to t1' a terms and Conditiotis. ❑ r the COrltract that iitcreasa the ivL nnwuht to be paid the E'rincipal shell seloronlic lly Lamaze the ollligetion of rho SuroT' ort this bond ar+d ssotiGI to SkAterY is not Tequila" for 4,14 vrcreaScri`obligatiou. Thin bawd may tra €.went d in tern neutral and dealt be sighed ter the parties' duly awlboriud olticers- This bond will an1y be accepted if n eniod d fully encoded suet origionk 1' ower ofateoritey ;or the officer eXecutking on brhaif of the surety. i ,. CTO Foe A ;,ilk*' ,� PAW era BRAD er IFF .TH SURETY Travelers Ce and ;surety Company of America 11/12174S i '\ LS Thule /_� I1� Primed Name Tide chenastagy punted Ntrsit: Aticr> eye In aaCt Thlc 1V tldd$cas, endtnlaphcrlw 9d beat ott.eth.i ant of Surety CompaKrY eicinicludiCr.mei— they. QPnr'y S07fiti-5i9n YtBia�4 ..J..1' TRAVELERS Attorney -la Pact N. WARNING: TINS POWBFI OF ATTORNEY IS INVALID WITHOUT THE RED BORDER POWER OF ATTORNEY Farmington Casualty Cumpuaiy' Fidelity an -d Guaranty Insurance Company Fidelity ar.d Guaranty Insnraanee Un deiirriters, 1>ac- SL Paul Fire and Ithurir & Insurance Compaaiy St. Pant Guardian Insurance Company 227798 St, Paul Mercury Insurance Cuuiluiny Trawekrs Casually and Surely Company rruvetcrs Casually mid Surely Conti/may of America United SOWS Fidelily and Guaranty Cuiupany Certificrte No, 0 0 5 9 6 0118 KNOW ALL MHN BY THF$E PRE EN'i'S: That Farmington Lbsunlly Company, St, Paul Fire and Marble Insurance Cnmpnny, St- Paul Guardian Insuranor Company, St, Paul MI®rcury Insurance Cuanpiiiy, Travelers Casualty ;and Sutrety Company, Travelers Cnsuulty and Surety CwiipanYy of Aand T.ritiled Slates Fidellly and Guaranty Company am corporations lily ruganizCd under the laws of the Slate ufC& ii-1lcul, that Fidelity sinal Guaranty !manual!. 'urnpwny is r corporation daily Ofganlzed hider the laws "Jibe Slate of Iowa, and that Fidelity and Guaranty rosuruorc Underwriters. Inc.. is h eorpOfal Ion duly orcin i red under du laws citric Suite of Wisconsin (herein anllecti Iy called alta -Companies"), iII tI L11att the Companies do hereby mrnlx- constitute and appsabit Cheryl Ashby. Dullu J. Alyn, James M. Hewill, !Carol J. McBride, Lisa Smith, Vonda Hall, Robert E. Feller, Shairol Siaybnngh, Roland Thnilan-,on, Dun McQuary, and Lesha Lehmilz - the Cite of _ Clarkston , $a1IC of Wsl ihlrtgiLrn , their true and lawful Attune sHin-Cali each in iltcii separate capacity if more than one is uutncd 411501.,e, Ica sign, execute, seal and acknutiwletipo uiw i1I1i1 all huiuls, feissgn]xaiee+cs- conditional undertakings and other writings ubliguutury in the nature tbereuf on Pe I it If or the Companies in their business of guarantee'. ng the fidelity of persons, guaranteeing the perfor mike of contracts and executing or guaranteeing bonds urd undertakings required or permitted in any auctions. or proceedings aillowed by law - ITV 'WITNESS VI/IiIsRE„Olf, , the Companies Mile carotid ibis instrument to be signed and their corporate seals las be hereto affixed, this 25th W day of June 2014 St,1Ie o(Connecllciit City of 1-Iartford ss. FarminRto:t Casualty Company Fidelity and Guaranty insurance Company fidelity and Cuarianly It -mut -an -cc Underwriters, LILA`. St, Pard F i:'e and h larine Insurance Company St. Paul Giardini Insuratice Company Sl. Paul Mercury insurance Company Tli vcIcrs Casually and Surely Company Travelers Casualty and Surely' Company of America Uuilud Slates Fidelity aanat Guaranty Company By: Clma Luis the day day or June 2014 r before nue personally appeared Robert L. Raney, who aeknuwleJgixl himself tc Ire aIle Senior Vice President of Farmington Casualty Company. Fidelity and Guaranty Insurance Company, Ficletiiy aac1 Guauunty 111SliriLTIrLM UuidcrwriLers, Inc-, St- L'aul Fire and Marine Insurance Company. St. Paul GLiardi7rn Insurnncc Company, ,ti it. Paul Mtercury Insurance Company, 'nave Iors Casualty and Surety Company, Travelers Casualty and Surety Company of An]enuu, and United Slates Fidelity and Guaranty Company, and that hr , us such. b: ing authorized so to do, executed the fungal e» instrument far the purposes therein cirmincd by signing on behalf of she corporations by himself as ,t duly muffin rind officer - In liVitnexs Whereof, L hereunto set nay hind trail official seal, My Commission expires the 3i)Lli day of Jume.20L6. 50440-8-12 Pliltleel In U,S-A, liEarie C.'Iihreauhl. 'oiary L'ilrIi VMI ININC:1711E POWER OF ATTORNEY IS le'1VALI.0 y,'IT1 4tr-TI IE RED 3QHI]F!! 2018 Prevailing Wage Rates Estimated 2016 Rates 2017 Rates 2018 Rates Occupation Hours Rate Rate Rate Foreman 500 $55.02 $57.50 $57.50 Journey Level 240 $65.65 $66.85 $68.05 Fence Erector 20 $77.69 $77.69 $77.69 Journey Level 1900 $46.25 $47.55 $48.70 General Laborer 2300 $47.72 $49.02 $50.17 Asphalt Raker 120 $47.22 $48.52 $49.67 Concrete Crewman 220 $65.50 $66.80 $67.95 Guard Rail 10 $50.10 $51.40 $52.55 Pipelayer 130 $58.30 $59.60 $60.75 Traffic Control Supervisor 40 $46.75 $48.05 $49.20 Blade(finish & bluetop) 200 $54.32 $55.62 $56.87 H.D. Mechanic 30 $54.32 $55.57 $56.82 Paving Machine 200 $52.37 $53.67 $54.92 Rollerman 400 $52.37 $53.67 $54.92 Screed Operator 200 $52.37 $53.67 $54.92 Power Broom 90 $52.37 $53.67 $54.92 Backhoes & Hoe Ram 30 $52.37 $53.67 $55.20 Vactor Guzzler, Super Sucker 10 $66.00 $67.30 $68.55 Roto Mill 90 $66.00 $67.30 $68.55 Posthole Auger or Punch 10 $52.80 $54.10 $55.35 Backhoe (45,000 GW & under) 380 $52.37 $53.67 $54.92 Dump Truck (E. WA -690) 800 $49.66 $51.48 $52.67 Dump Truck & Trailer (E. WA - 690) 500 $49.88 $51.53 $52.89 Other Trucks (E. WA -690) 30 $49.88 $51.53 $52.89 Transit Mixer 10 $49.88 $49.88 $49.88 Prevailing Wage Breakdown 1/1/2016 1/1/2017 1/1/2018 Increase % Inc $55.02 $57.50 $57.50 $0.00 0.00% $39.60 $40.80 $42.00 $1.20 2.94% $31.41 $31.41 $31.41 $0.00 0.00% $33.61 $34.91 $36.06 $1.15 3.29% $35.71 $37.01 $38.16 $1.15 3.11% $36.25 $37.55 $38.70 $1.15 3.06% $35.71 $37.01 $38.16 $1.15 3.11% $35.71 $37.01 $38.16 $1.15 3.11% $36.25 $37.55 $38.70 $1.15 3.06% $34.61 $35.91 $37.06 $1.15 3.20% $41.51 $42.81 $44.06 $1.25 2.92% $41.51 $42.81 $44.06 $1.25 2.92% $41.24 $42.54 $43.79 $1.25 2.94% $41.24 $42.54 $43.79 $1.25 2.94% $41.24 $42.54 $43.79 $1.25 2.94% $40.03 $41.33 $42.58 $1.25 3.02% $40.96 $42.26 $43.79 $1.53 3.62% $41.24 $42.54 $43.79 $1.25 2.94% $41.24 $42.54 $43.79 $1.25 2.94% $40.64 $41.94 $43.19 $1.25 2.98% $40.96 $42.26 $43.51 $1.25 2.96% $39.32 $41.14 $42.33 $1.19 2.89% $39.49 $41.14 $42.50 $1.36 3.31% $39.21 $40.86 $42.22 $1.36 3.33% $37.00 $37.00 $37.00 $0.00 0.00% CITY OF SPOKANE VALLEY Request for Council Action Meeting Date: February 6, 2018 Department Director Approval: Check all that apply: ['consent ❑ old business ® new business ['public hearing ['information ❑admin. report ['pending legislation ['executive session AGENDA ITEM TITLE: Motion Consideration: Street Sweeping Service Contract — 2018 Option year GOVERNING LEGISLATION: RCW chapter 39.04; RCW 90.48; Chapter 173-200 WAC; Title 33 U.S.C. 1251-1376 PREVIOUS COUNCIL ACTION TAKEN: Approval and award of Street Sweeping Services Agreement 2/10/2015, and subsequent annual renewals for 2016 and 2017. Admin Report January 30, 2018. BACKGROUND: In 2015, City staff prepared a Request for Bid for Street Sweeping Services and received a bid proposal from AAA Sweeping. The proposal was reviewed by staff and found to be responsible and acceptable and Council awarded the bid to AAA Sweeping, LLC. This contract may be extended up to four additional one year terms if mutually agreed by both parties. This will be the third of four renewal terms that may be exercised by the City. Upon request by the Contractor, contract specifications note that the City and Contractor may negotiate a rate increase for each option year exercised but shall not be increased or decreased by more than the percent change in the Consumer Price Index for All Urban Consumers (CPI -U) or 3%, whichever is smaller. The CPI -U increased 2.2% for the contract specified period (October 1, 2016 — September 30, 2017). The Contractor requested the full 2.2% hourly rate increase available based on the following items: • Prevailing wage rates increased an average of 3.3%; and, • Health insurance rates increased over 22%. Staff verified that the 2.2% rate increase is reasonable based on increases in wages and benefits and also when considering fuel costs increases of over 20% from October 1, 2016 to September 30, 2017. AAA Sweeping provided a good level of service throughout the 2017 contract year and staff recommends exercising the 2018 option year with the 2.2% hourly rate increase. The renewal amount is recommended at the same contract amount as in previous years. OPTIONS: Move to authorize the City Manager to finalize and execute the 2018 option year contract renewal with AAA Sweeping; or take other action deemed appropriate. RECOMMENDED ACTION OR MOTION: Move to authorize the City Manager to finalize and execute the 2018 option year contract renewal with AAA Sweeping, in the amount of $490,200.00. BUDGET/FINANCIAL IMPACTS: This contract will be funded by the approved 2018 Budget STAFF CONTACT: Bill Helbig, City Engineer ATTACHMENTS: Renewal Letter and proposed 2018 hourly rates; AAA Sweeping Contract j January 23, 2018 AAA Sweeping, LLC PO Box 624 Veradale, WA 99037 OFFICE OF THE CITY ATTORNEY CARY P. DRISKELL - CITY ATTORNEY ERIK J. LAMB - DEPUTY CITY ATTORNEY 10210 East Sprague Avenue • Spokane Valley, WA 99206 509.720.5105 • Fax: 509.688.0299 • cityattorney@spokanevalley.org Re: Implementation of 2018 option year, Agreement for Street Sweeping Services, Contract number 15-020.04 Dear Mr. Sargent: The City executed a contract for provision of Street Sweeping Services on February 18th 2015, by and between the City of Spokane Valley, hereinafter "City", and AAA Sweeping, LLC, hereinafter "Contractor" and jointly referred to as "Parties." The Request for Proposal states that it was for one year, with four optional one-year terms possible if the parties mutually agree to exercise the options each year. This is the third of four possible option years that can be exercised and runs through December 31, 2018. The City would like to exercise the 2018 option year of the Agreement. The Compensation as outlined in Exhibit A, 2018 Cost Proposal, includes the labor and material cost negotiated and shall not exceed $490,200.00. The history of the annual renewals is set forth as follows: Original contract amount .$ 490,200.00 2016 Renewal $ 490,200.00 2017 Renewal $ 490,200.00 2018 Renewal $ 490,200.00 All of the other contract provisions contained in the original Agreement are in place and will remain unchanged in exercising this option year. If you are in agreement with exercising the 2018 option year, please sign below to acknowledge the receipt and concurrence to perform the 2018 option year. Please return two copies to the City for execution, along with current insurance information. A fully executed original copy will be mailed to you for your files. CITY OF SPOKANE VALLEY AAA SWEEPING, LLC Mark Calhoun, City Manager Name Title ATTEST: Christine Bainbridge, City Clerk APPROVED AS TO FORM: Office of the City Attorney Exhibit A — 2018 Cost Proposal Street Sweeping Services Task/Item Unit Hourly Rate Sweeping, Mechanical Type Hour $161.85 Sweeping, Regenerative Air Type Hour $161.78 Sweeping, High Efficiency Vacuum Type Hour $161.70 Water Truck or Truck Mounter Power Washer Hour $121.17 Foreman Hour $57.05 Dump Truck Hour $120.64 Loader Hour $115.13 CITY OF SPOKANE VALLEY Request for Council Action Meeting Date: February 6, 2018 Department Director Approval: Check all that apply: ['consent ❑ old business ['new business ['public hearing ['information ® admin. report ['pending legislation ['executive session AGENDA ITEM TITLE: Administrative report — proposed Ordinance reauthorizing the joint Spokane Housing Authority. GOVERNING LEGISLATION: Chapter 35.82; Resolution 03-047. PREVIOUS COUNCIL ACTION TAKEN: Adoption of Resolution 03-047 authorizing creation of joint Spokane Housing Authority. BACKGROUND: The Spokane Housing Authority (the "Authority") is a joint housing authority established pursuant to chapter 35.82 RCW to provide affordable housing opportunities within the entire Spokane County region, including within the boundaries of the City of Spokane Valley (City). The Authority was initially created in in 1971 within the City of Spokane, and was expanded in 2001 to include the entire County. After incorporation, the City adopted Resolution 03-047 establishing the Authority as a joint housing authority within the City limits. The Authority has worked since establishment to provide safe, sanitary, and affordable housing opportunities to low -to -moderate income and senior citizens. It operates a number of affordable housing facilities and provides other types of assistance as well. The Authority operates independently from the City and no City funds or staff are used in Authority business. However, the City appoints two members to represent the City on the Authority commission. The City's current representatives are Gretchen Campbell and Keith James. Recently, the Authority determined that a number of the specific requirements set forth in the original authorizing documents, including Resolution 03-047, were burdensome and inflexible. These included specific designation of personnel, meeting times, and other operational requirements. These requirements make it difficult for the Authority to conduct its business in the most efficient manner. Accordingly, the Authority approached the City, Spokane County, and the City of Spokane to request that each re-establish the Authority and to allow more operational flexibility with things such as meeting times and specific personnel that are required to run the Authority. Staff from the Authority, the City, Spokane County, and the City of Spokane have worked to draft an appropriate Ordinance for each jurisdiction to adopt to re-establish the Authority with the flexibility it desires. The proposed Ordinance maintains the same mission and goals for the Authority and the Authority will continue to provide the same type and level of service and opportunities that it has provided historically. Staff from the Authority have included a more detailed memo regarding the proposed changes. Further, Staff from the Authority will be available for questions regarding the proposed Ordinance and to provide an update on Authority business. Page 1 of 2 OPTIONS: Consensus to proceed with first reading at a future council meeting; or take other action deemed appropriate. RECOMMENDED ACTION OR MOTION: Consensus to proceed with first reading at a future council meeting. BUDGET/FINANCIAL IMPACTS: N/A. STAFF CONTACT: Erik Lamb, Deputy City Attorney. ATTACHMENTS: (1) Memo from SHA; (2) Proposed Ordinance; (3) Spokane Valley Resolution 03-047 Page 2 of 2 Spokane Housing Authority MEMORANDUM DATE: January 29, 2018 TO: Erik Lamb, Deputy City Attorney City of Spokane Valley FROM: Pam Tietz, Executive Director SUBJECT: Spokane Housing Authority Joint Ordinance Background The Spokane Housing Authority was originally established in accordance with RCW 35.82 on June 13, 1982 by a City of Spokane Resolution 255-1. For a Housing Authority to exist and operate, the RCW requires a declaration of need by local jurisdictions. SHA was later expanded as a Joint Housing Authority in accordance with RCW 35.82.300. This was first to include unincorporated areas of Spokane County and then adding the City of Spokane Valley in 2003. The City of Spokane Valley, City of Spokane and Spokane County then adopted one additional resolution to approve the expansion of the board from five (5) members to six (6) members to allow for one new board member, who must be a participant of SHA services or "Directly Assisted Commissioner" and to establish that the City of Spokane Valley had the authority appoint two of the six Commissioners (one slot ceded from Spokane County). The original resolutions adopted by each jurisdiction included provisions that ideally would be in agency bylaws or that periodically change. An example of this would be when regular meetings will be held, the order of business on the agenda, what will be on a consent agenda, and who the existing board is. This can create issues from an operating perspective and some confusion as the board changes. In addition, Spokane County has long held that they should have equal representation on SHA's board and that there was some confusion when one of their two slots was ceded when the updated resolution added a Directly Assisted Commissioner. The addition of this Commissioner also took SHA's Board to an even number when ideally we should have an odd number of Commissioners in the case of a tie. Proposal SHA has proposed a new Joint Ordinance for each of the three jurisdiction's consideration. The changes are not substantial; however would simplify things from an operating standpoint; give Spokane County an additional Commissioner position on SHA's Board; and make the total number of board members 7 (an odd number). The proposed ordinance has been vetted by each local jurisdictions legal counsel and the proposed ordinance has been agreed to in principal. It is my recommendation that the updated Joint Ordinance be adopted. END OF MEMORANDUM 1 DRAFT CITY OF SPOKANE VALLEY SPOKANE COUNTY, WASHINGTON ORDINANCE NO. 18 - AN ORDINANCE OF THE CITY OF SPOKANE VALLEY, SPOKANE COUNTY, WASHINGTON, CONFIRMING THE FORMATION OF THE SPOKANE HOUSING AUTHORITY AS A JOINT HOUSING AUTHORITY; PROVIDING FOR MATTERS REQUIRED PURSUANT TO RCW 35.82.300; REPEALING CERTAIN RESOLUTIONS; AND OTHER MATTERS RELATING THERETO. WHEREAS, the Washington Legislature, by enactment of Chapter 23, Section 4, of the Laws of 1939, as amended (currently codified as RCW 35.82.030), created in each city and in each county of the state a public body corporate and politic known as the housing authority. Such statute further provides that no such authority shall transact any business or exercise its powers under chapter 35.82 RCW until or unless the governing body of the city or the county, as the case may be, declares by resolution that there is need for an authority to function in such city or county. Pursuant to a resolution adopted December 13, 1971 by the City of Spokane's (Spokane) City Council Spokane declared a need for a housing authority to function within Spokane, and named such housing authority as the "Housing Authority of the City of Spokane;" and WHEREAS, there are unsanitary and unsafe inhabited dwellings located in the incorporated cities and towns within Spokane County (County), and in the unincorporated area of the County, as well as a shortage of safe and sanitary dwelling accommodations available at rents affordable to persons of low to moderate income and to senior citizens. These conditions constitute a threat to the health, safety and welfare of the residents of the County. It appears likely that substandard housing conditions cannot entirely be relieved by the private sector; and WHEREAS, RCW 35.82.300 authorizes cities and counties to form joint housing authorities. To do so, the legislative authorities of one or more counties and the legislative authorities of any city or cities within any of those counties or in another county or counties must authorize the joint housing authority by ordinance, which ordinance is required to prescribe: (1) the number of commissioners of the joint housing authority, (2) the method for their appointment, (3) the length of their terms, (4) the method for their removal; (5) the election of officers of the joint housing authority; (6) the allocation of all costs of the joint housing authority; and (7) any other matters necessary for the operation of the joint housing authority; and WHEREAS RCW 35.82.300(4) provides that a "joint housing authority shall have all the powers as prescribed by [chapter 35.82 RCW] for any housing authority" and that "[t]he area of operation of a joint housing authority shall be the combined areas, defined by RCW 35.82.020(6), of the housing authorities created in each city and county authorizing the joint housing authority;" and WHEREAS, pursuant to Resolution No. 01-83, adopted by the Spokane City Council on September 24, 2001, and Resolution No. 1-0752, adopted by the Board of County Commissioners on August 14, 2001, Spokane and the County authorized the formation of the "Spokane Housing Authority" (Authority) as a joint housing authority within the boundaries of Spokane and the unincorporated portions of the County. Pursuant to Resolution No. 03-047, adopted by the Spokane Valley City Council on September 23, 2003, the City of Spokane Valley (City) authorized the formation of the Authority as a joint housing authority within the boundaries of the City. The Board of County Commissioners and the Spokane City Council have further adopted resolutions delegating to the Spokane Valley mayor the authority to appoint two of the Authority's commissioners, and increasing the number of Authority commissioners from five to six; and WHEREAS, the Spokane City Council, City of Spokane Valley City Council, and Board of County Commissioners have determined there remains a continuing need for a housing authority within the Spokane region. There exists a need to update the ordinances and resolutions authorizing the formation of Ordinance 18 -XXX Page 1 of 5 DRAFT the Authority to provide for the efficient governance of the Authority and to allow expansion of the Authority to areas not currently served by the Authority; and WHEREAS, the City Council hereby declares there remains a continuing need for a housing authority to function in the City, and hereby reaffirms each previous declaration of such need by the City Council. The City Council hereby determines it is necessary and desirable to adopt an updated ordinance to provide for the efficient governance of the Authority and to allow expansion to areas outside of the City, Spokane, and unincorporated areas of the County. NOW THEREFORE, the City Council of the City of Spokane Valley, Spokane County, Washington, ordains as follows: Section 1. Finding of Necessity. Upon review of the information before it and in consideration of material provided to it, the City Council of the City makes the following determinations: A. The City Council hereby adopts the recitals set forth in this Ordinance; B. Access to safe, secure, and affordable housing is important to the residents of the City, Spokane, and the County, collectively "the Community;" C. Access to this type of housing is increasingly difficult to many residents of the Community; and D. The Spokane Housing Authority (the "Authority"), with support from the Community, has successfully undertaken many initiatives to provide more housing opportunities, but there is still an unmet need that can best be addressed by the collective approach of the Community. Section 2. Authorization of Authority. A joint housing authority (within the meaning of RCW 35.82.300), to be known as "Spokane Housing Authority," is authorized by the City Council to be formed within the boundaries of the City. Section 3. Commissioners. The powers of the Authority are hereby vested in the Authority's commissioners in office from time to time. The commissioners in office from time to time shall be referred to as the Authority's "Board of Commissioners" (the Board). A. Number. The number of commissioners of the Authority shall be seven. Upon formation, one of the Authority's commissioners shall be designated as the "Assisted Commissioner", two of the Authority's commissioners shall be designated as the "Spokane Commissioners", two of the Authority's commissioners shall be designated as the "Spokane Valley Commissioners", and two of the Authority's commissioners shall be designated as the "County Commissioners." B. Method for Appointment. The Authority's commissioners shall be appointed and re -appointed in the following manner 1. Assisted Commissioner. The Assisted Commissioner shall be an individual who is directly assisted by the Authority (e.g. a resident of a housing project owned by the Authority, a recipient of Section 8 Housing Choice Voucher administered by the Authority) at the time such individual is appointed as the Assisted Commissioner. The Assisted Commissioner shall be appointed by the Authority's Board. Such appointment shall be evidenced by a resolution of the Board, which resolution shall be retained by the Authority's Executive Director (as defined herein). Such resolution shall be conclusive evidence of the due and proper appointment of the Assisted Commissioner. 2. Spokane Commissioners. Each Spokane Commissioner shall be an individual who, at the time such individual is appointed or re -appointed as a Spokane Commissioner, is a resident of Spokane Each Spokane Commissioner shall be appointed by the Mayor of Spokane and confirmed by the Spokane City Council. Such appointment shall be evidenced in writing by the Mayor and the Spokane City Council (or by the Spokane City Clerk reflecting action by the Spokane City Ordinance 18 -XXX Page 2 of 5 DRAFT Council), and transmitted to the Authority's Executive Director. Such writing(s) shall be conclusive evidence of the due and proper appointment of the Spokane Commissioner to which the writing pertains. 3. Spokane Valley Commissioners. Each Spokane Valley Commissioner shall be an individual who, at the time such individual is appointed or re -appointed as a Spokane Valley Commissioner, is a resident of Spokane Valley. Each Spokane Valley Commissioner shall be appointed by the Mayor of Spokane Valley and confirmed by the Spokane Valley City Council. Such appointment shall be evidenced in writing by the Mayor and the Spokane Valley City Council (or by the Spokane Valley City Clerk reflecting action by the Spokane Valley City Council) and transmitted to the Authority's Executive Director. Such writing(s) shall be conclusive evidence of the due and proper appointment of the Spokane Valley Commissioner to which the writing pertains. 4. County Commissioner. Each Spokane County Commissioner shall be an individual who, at the time such individual is appointed or re -appointed as the County Commissioner, is a resident of Spokane County (regardless of whether such individual resides in an incorporated city or town or in the unincorporated area of the County; however, they may not reside inside the City of Spokane or the City of Spokane Valley city limits). The County Commissioners shall be appointed by the Board of County Commissioners. Such appointment shall be evidenced in writing by the Board of County Commissioners (or by the Clerk of the Board of County Commissioners reflecting action by the Board of County Commissioners) and transmitted to the Authority's Executive Director. Such writing shall be conclusive evidence of the due and proper appointment of the County Commissioner. C. Length of Terms. Each commissioner shall be appointed (or re -appointed) for a term of office of five years from the date such commissioner is appointed (or re -appointed, if applicable). At the end of a commissioner's term of office, the commissioner shall hold office until his or her successor has been appointed, unless sooner removed according to this Ordinance. Notwithstanding the foregoing, a person appointed as the Assisted Commissioner may serve in that position only as long as he or she is directly assisted by the Authority. D. Method of Removal. 1. The Assisted Commissioner may be removed for neglect of duty, or misconduct in office. Any such removal shall be evidenced in a resolution of the Board. The Assisted Commissioner shall be removed only after he or she shall have been given a copy of the charges by the Board Chair. Removal of the Assisted Commissioner requires a majority vote of the Board. 2. The Mayor of Spokane, with confirmation by the Spokane City Council, may remove a Spokane Commissioner for neglect of duty or misconduct in office. A Spokane Commissioner shall be removed only after he or she shall have been given a copy of the charges by (or on behalf of) the Mayor of Spokane 3. The Mayor of Spokane Valley, with confirmation by the City of Spokane Valley Council may remove a Spokane Valley Commissioner for neglect of duty, or misconduct in office. A Spokane Valley Commissioner shall be removed only after he or she shall have been given a copy of the charges by (or on behalf of) the Mayor of Spokane Valley. 4. The Board of County Commissioners may remove the County Commissioner for neglect of duty or misconduct in office. The County Commissioner shall be removed only after he or she shall have been given a copy of the charges by (or on behalf of) the chairperson. Ordinance 18 -XXX Page 3 of 5 DRAFT E. Vacancies. A mid-term vacancy resulting from the death, resignation or removal of a commissioner shall be filled by the appointment of a replacement commissioner. The replacement commissioner shall be appointed in the manner set forth in Section 3(B). The replacement commissioner shall serve for the remaining stated term of the replaced commissioner; however, if the remaining term of the replaced commissioner is less than one year at the time the replacement commissioner is appointed, the replacement commissioner shall serve for a full five-year term (measured pursuant to Section 3(C) of this ordinance). F. Quorum. Four commissioners shall constitute a quorum of the Board for the purpose of conducting its business and exercising its powers and for all other purposes Action may be taken by the Board upon a vote of a majority of the commissioners present at the time such action is taken, unless in any case the bylaws of the Authority shall require a larger number. G. Officers of the Board. The Board shall select from among its commissioners a Chair and a Vice Chair of the Authority, each of whom shall serve in such capacity until the Board appoints a successor. H. Compensation. A commissioner shall receive no compensation for his or her services for the Authority, in any capacity, but he or she shall be entitled to the necessary expenses, including traveling expenses, incurred in the discharge of his or her duties as a commissioner. I. Existing Commissioners. The commissioners in office on the effective date of this Ordinance shall continue to serve the respective terms, subject to removal pursuant to Section 2(D) of this Ordinance. Section 4. Bylaws. The Board may adopt, and from time to time may amend or restate, bylaws and other rules of operation for the Authority. Bylaws of the Authority shall include provisions for annual, regular and special meetings of the Board. The Bylaws shall be consistent with this Ordinance and chapter 35.82 RCW. Section 5. Officers, Agents and Employees. The Authority may employ an Executive Director of the Authority. If an Executive Director is employed, that individual also shall be Secretary of the Authority. The Authority also may employ technical experts and such other officers, agents and employees, permanent and temporary, as it may require, and shall determine their qualifications, duties and compensation. For such legal services as it may require, the Authority may employ its own counsel and legal staff. The Authority, acting through the Board, may delegate to one or more of its agents or employees such powers or duties as it may deem proper. Section 6. Allocation of Costs of the Authority. A. The Authority is and shall be solely responsible for all debts and operating expenses incurred in the operation of the Authority. No costs of the Authority shall be allocated to Spokane, Spokane Valley or the County. The obligations of the Authority shall not be a debt of Spokane, Spokane Valley, the County, the State of Washington or any political subdivision of the State of Washington (other than the Authority). Subject to Section 6(B) of this Ordinance, neither Spokane, Spokane Valley, the County, the State of Washington nor any political subdivision of the State of Washington (other than the Authority), shall be liable for the obligations of the Authority, nor in any event shall obligations of the Authority be payable out of any funds or properties other than those of the Authority. B. Nothing in Section 6(A) of this Ordinance shall prevent Spokane, Spokane Valley, the County, the State of Washington or a political subdivision of the State of Washington from providing assistance to the Authority, financial or otherwise, under the Housing Cooperation Law (chapter 35.83 RCW) or any other applicable law, or prevent the Authority from using any such assistance to pay obligations of the Authority. Ordinance 18 -XXX Page 4 of 5 DRAFT Section 7. Assumption of Responsibilities. The Authority assumes all of the contractual and financial liabilities for the Housing Authority of the City of Spokane, as such liabilities existed on the date the Authority became a joint housing authority under RCW 35.82.300. Section 8. Deactivation of the Authority. Upon deactivation of the Authority as provided by law, the assets of the Authority shall be applied and distributed pursuant to RCW 35.82.325. However, if the Housing Authority of the City of Spokane is reactivated at the time the Authority is deactivated, it shall be entitled to the return of all assets held by it prior to the organization of the Authority, and the Housing Authority of the City of Spokane shall assume all debts encumbering and/or associated with said assets. Section 9. Repeal of Certain Prior Acts. The City intends for this Ordinance to replace all prior authorizing actions and hereby repeals all prior official acts related to authorizing the Authority that are contrary to this Ordinance, including Resolution No. 03-047, and those actions shall have no further force and effect other than to evidence that the Authority was duly organized as a joint housing authority pursuant to RCW 35.82.300, and has operated as a joint housing authority at all times since September 24, 2001. Such repeal shall not be effective until the date this Ordinance and the other substantive provisions become effective. Section 10. Ratification of Past Acts. All acts heretofore taken by Spokane, Spokane Valley and the County to organize the Authority as a joint housing authority under RCW 35.82.300 are hereby ratified, confirmed and approved. Section 11. Severability. If any part of this Ordinance is declared unenforceable, invalid, or unconstitutional, such unenforceability, invalidity, or unconstitutionality shall not affect the enforceability, validity, or constitutionality of the remainder. Section 12. Effective Date. This Ordinance shall be in full force and effect on the latest of (a) the date an ordinance substantially similar to this Ordinance takes effect as to Spokane under Article III, Section 19.B, of the Spokane City Charter; (b) the date an ordinance substantially similar to this Ordinance is enacted by the County, or (c) five days after the date of publication of this Ordinance or a summary thereof in the official newspaper of the City as provided by law. Passed by the City Council of the City of Spokane Valley this day of , 2018. City of Spokane Valley ATTEST: L.R. Higgins, Mayor Christine Bainbridge, City Clerk Approved as to Form: Office of the City Attorney Date of Publication: Effective Date: Ordinance 18 -XXX Page 5 of 5 CITY OF SPOKANE VALLEY SPOKANE COUNTY, WASHINGTON RESOLUTION NO. 03-047 A RESOLUTION OF THE CITY COUNCIL OF THE CITY OF SPOKANE VALLEY, SPOKANE. COUNTY, WASHINGTON, PROVIDING FOR APPOINTMENT, MEMBERS OF THF.. BOARD OF COMMISSIONERS AND OPERATIONAL RULES FOR THE SPOKANE HOUSING AUTHORITY; AND PROVIDING FOR OTHER MATTERS PROPERLY RELATING THERETO . JOINT C1TY/COUNTY HOUSING AUTHORITY CITY OF SPOKANE VALLEY Spokane County, Washington BE FF RESOLVED BY THE CITY COUNCIL OF THE CITY OF SPOKANE VALLEY, of Spokane County, Washington: WHEREAS, the City of Spokane Valley, Washington ("CITY"), is a noncharter code city duly organized and existing under and by virtue of the Constitution and the laws of the State of Washington; and WHEREAS, the Council of the CITY ("COUNCIL") recognizes the public interest in sustaining affordable housing for the residents of the city and the surrounding community; and WHEREAS, by Resolution dated May 13, 2003, COUNCIL recognized the need for tow -income housing; and WHEREAS, the Spokane Housing Authority ("AUTHORITY") has provided services within the city limits of the city of Spokane Valley; and WHEREAS, recognition of such geographical service area was recognized by Resolution of both the City of Spokane and Spokane County deferring appointment to CITY, one member of the Board of Commissioners of the AUTHORITY ("BOAR.D") who works or resides within the city of Spokane Valley; and WHEREAS, every housing authority in the State of Washington is authorized to do any and all things necessary or desirable to secure the financial aid or cooperation of the federal government in the undertaking, construction, maintenance or operation of any housing project by such authority pursuant to RC\V 35.82.800; and WHEREAS, AUTHORITY has in the past and will in the future, secure the financial aid and cooperation of the federal government and is solely responsible for all debts and operating expenses incurred in the operation of AUTHORI'T'Y. NOW THEREFORE, IT IS HEREBY FOUND DETERMINED AND ORDERED as follows: Section I: FINDING OF NECESSITY Upon review of the information before it and after consideration of material provided to it, COUNCIL makes the following determinations: Rcsolunion 03-047 Page 1 of 6 (a) The affordability of adequate housing for a number of residents within the boundaries of the city of Spokane Valley is an increasing problem; (b) AUTHORITY has entered into a number of agreements with other municipalities within Spokane County to assist. with this problem and has had success providing more housing opportunities for low income individuals, but the problem of adequate housing for low income residents of this community still remains; Section 2: AUTHORiTY (a) Name of Authority. The name of the Authority shall be and remain "Spokane Housing Authority." (b) Seal of the Authority. The seal of the Authority shall be in the form of a circle and shall bear the name of the Authority and the year of its organization as a joint city/county housing authority. (c) Office of Authority. The office of the Authority shall be at such place in the County of Spokane, Washington, as the Authority may from time to time designate by Resolution. The official office of the Authority is presently located at 55 W. Mission, Spokane, Washington. Section 3: APPOINTiVIENT AND TENURE OF COMMISSION A board of five (5) Commissioners (BOARD) composed of the following shall govern AU`i'HORI'I'Y: (a) Membership of the BOARD. One (1) individual who is directly assisted by AUTHORITY, jointly appointed by the Mayor of the City of Spokane, the Mayor of the City of Spokane Valley, and the Chair of the Board of County Commissioners; Two (2) individuals who work or reside within the city limits of the city of Spokane appointed by the Mayor and confirmed by the Council of the City of Spokane; One (1) individual who works or resides in unincorporated Spokane County, Washington, appointed by the Board of Commissioners of Spokane. County; Washington; One (1) individual who works or resides within the city limits of the city of Spokane Valley, appointed by the Mayor and confirmed by COUNCIL of CiTY of Spokane Valley; (b) Existing BOARD. The term of each appointment shall be for five (5) years on a rotating basis in concurrence with provisions under RCW 35.82.040. With the establishment of the joint city/county housing authority, the following Commissioners and terns shall be certified as follows: Julia Rahman — SHA -assisted Representative 3/15/2006 William Zeck —City of Spokane Representative 3/15/2004 Terri Symbol — County of Spokane Representative 3/15/2002 Resolution 03-047 Page 2 of 6 Richard Brittain — City of Spokane Representative 3/15/2005 Janet Bastine — City of Spokane Valley Representative 3/15/2008 Any seat vacated prior to the expiration of the term shall be filled by the appropriate jurisdiction and shall be for the unexpired term of that Commissioner's seat. (c) Removal of Commissioner. For inefficiency or neglect of duty or misconduct in office, a Commissioner may be removed by the Mayor (if a City appointee); the Chair of the Board of County Commissioners (if a County appointee); and the Mayor of Spokane and Chair jointly as SHA -assisted representative appointee. A Commissioner may be removed only after having been given a copy of the charges at least ten (10) days prior to the hearing thereon and after having an opportunity to be heard in person or by Council. In the event of the removal of any Commissioner, a record of the proceedings, together with the charges and findings thereon, shall be filed in the Office of the Secretary. Section 4: OFFICERS (a) Officers. The officers of AUTHORITY shall be a Chair, a Vice -Chair and a Secretary who shall be the Executive Director. (b) Chair. The Chair shall preside at all meetings of the BOARD. Except as otherwise authorized by Resolution of the BOARD, the Chair shall sign all contacts, deed, and other instruments made by AUTHORITY. At each meeting, the Chair shall submit such recommendations and information as the Chair considers proper concerning the business, affairs and policies of AUTHORITY. (c) Vice -Chair. The Vice -Chair shall perform the duties of the Chair in the absence or incapacity of the Chair. In case of the resignation or death of the Chair, the Vice -Chair shall perform the duties as are imposed on the Chair until such times as BOARD shall elect a new Chair. (d) Secretary. The Secretary shall be the Executive Director of AUTHORITY and as such, shall have general supervision over the administration of its business and affairs, subject to the direction of AUTHORITY. The Executive Director shall be charged with the management of the housing projects of AUTHORITY. The Secretary shall keep the records of BOARD, shall act as secretary of the meetings of BOARD and record all votes, and shall keep a record of the proceedings of' BOARD in a journal of proceedings to be kept for such purposes, and shall perform all duties incident to the office. The Secretary shall keep in safe custody, the seal of AUTHORITY and shall have the power to affix such seal to all contracts and instruments authorized to be executed by AUTHORITY. The Secretary shall have the care and custody of all funds of AUTHORITY, and shall deposit the same in the name of AUTHORITY in such bank or banks as AUTHORITY may select. The Secretary shall sign all orders and checks for the payment of money and shall pay out and disburse such moneys under the direction of AUTHORITY. Except as otherwise authorized by Resolution of BOARD, all such orders and cheeks shall be countersigned by the Chair. The Secretary shall keep regular books of accounts showing receipts and expenditures and shall render to BOARD, at each regular meeting (or more often if requested), an account of all AUTHORITY transactions and the financial condition of AUTHORITY. The Secretary shall give such bond for the faithful performance of these duties as BOARD may determine. Resolution 03.047 ['age 3 of 6 The compensation of the Secretary shall be determined by BOARD, provided that a temporary appointee selected from among the Commissioners of AUTHORITY shall serve without compensation (other than the payment of necessary expenses). (e) Other Duties. The officers of AUTHORITY shall perform such other duties and functions as may from time to time be required by BOARD or the by-laws or rules and regulations of AUTHORITY. (t) Election of Appointment. The Chair and Vice -Chair shall be elected at the annual meeting of AUTHORITY from among the Commissioners of AU'T'HORITY, and shall hold office for one (1) year or until their successors are elected and qualified. The Secretary shall be appointed by AUTHORITY. Any person appointed to fill the office of Secretary, or any vacancy therein, shall have such term as AUTHORITY Fixed, but no Commissioner of AUTHORITY shall be eligible for this office except as a temporary appointee. (g) Vacancies. Should the office of Chair or vice -Chair become vacant, AUTHORITY shall elect a successor from its membership at the next regular meeting, and such election shall be for the unexpired term of said office. When the office of the Secretary becomes vacant, AUTHORITY shall appoint a successor as aforesaid. Section 5: MEETINGS (a) Annual Meeting. The annual meeting of AUTHORITY shall be held on the third Monday of October at 3:30 p.m. at the regular meeting place of AUTHORITY. (b) Regular Meetings. Regular meetings shall be held without notice at such time and place as may from time to time be determined and given public, legal notice. (c) Special lviectings. The Chair of the BOARD may, when deemed expedient, and shall, upon the written request of two (2) Commissioners of AUTHORITY, call a special meeting of the BOARD for the purpose of transacting any business designated in the call. The call for a special meeting may be delivered to each Commissioner of AUTHORITY to either the home or business address at least two (2) days prior to the date of the special meeting. At such special meeting, no business shall be considered other than as designated in the call, but if all of the Commissioners of AUTHORITY are present at a special meeting, any and all business may be transacted at such special meeting. (d) Quorum. The powers of AUTHORITY shall be vested in the Commissioners thereof in office from time to time. Three (3) Commissioners shall constitute a quorum for the purpose of conducting its business and exercising its powers and for all other purposes, but a smaller number may adjourn from time to time until a quorum is obtained. When a quorum is in attendance, action may be taken by AUTHORITY upon vote of the majority of the Commissioners present. (e) Order of Business. At the regular meeting of AUTHORITY, the following shall be the order of business: 1. Convening of Meeting Action on proposed Resolutions and Motions Resolution 03-047 Page 4 of 6 3. Consent Calendar Approval of minutes of previous meeting Review of month-end Financial Reports Department reports Resident Group reports News & Notes 4. New Business 5. Unfinished Business 6. Adjournment All Resolutions shall be in writing and shall be copied in a journal of the proceedings of BOARD. (f) Manner of Voting. The voting on all questions coming before AUTHORITY shall be by voice vote, and the Ayes and Noes shall be entered upon the minutes of such meeting, except on the election of officers which may be by ballot. (g) Sub -Committees. Sub -committees may be established by the Chair as a standing or ad- hoc committee. Sub -committees shall consist of two (2) Commissioners. At the request of the sub- committe, AUTHORITY personnel may be assigned by the Secretary. Section 6: AUTHORITY FOR OPERATION (a) Statutory. AUTHORITY shall have the legal authority and the complete obligations as set forth in the laws and Constitution of the State of Washington. Nothing set forth herein is intended in any way to limit this authority or AUTHORITY'S ability to operate. (b) Assumption of Responsibilities. AUTHORITY assumes all of the contractual and financial liabilities for the Spokane Housing Authority. (c) Professional Services. BOARD of AUTHORITY shall have the authority, from time to time, to appoint the necessary professionals to assist it, including but not limited to legal counsel, underwriting and financial services and other professional assistance deemed necessary. (d) Bylaws.. BOARD may adopt, and from time to time amend, bylaws and other rules of operation. (e) Financial Responsibility. AUTHORITY shall be responsible for its own financial and other obligations. Absent specific action by COUNCIL, CITY shall have no financial or other responsibility for the operation of AUTHORITY. Section 7: GENERAL, AUTHORIZATION The Mayor, Chief Administrative Officer and the City Attorney, as agents and representatives of CITY are hereby authorized and directed to do everything necessary to accomplish the acts set forth in this Resolution. Rexduiiun 03-047 Page 5 of 6 Section 8: RATIFICATION OF PAST ACTS All acts as heretofore taken by CITY officers, staff, attorneys and agents consistent with the terms and purposes of this Resolution are hereby ratified, confirmed and approved. Section 9: SEVERABILITY If any one or more of the covenants or agreements provided in this Resolution to be performed on the part of CI'T'Y shall be declared by any court of competent jurisdiction to be contrary to law, then such covenant or covenants, agreement or agreements, shall be null and void and shall be deemed separable from the remaining covenants and agreements of this Resolution and shall in no way affect the validity of the other provisions of this Resolution. Section 10: REPEALER All Resolutions or parts thereof in conflict herewith are, to the extent of such conflict, hereby repealed, and shall have no further force or affect. AT - Section 1 I: EFFECTIVE DATE This Resolution shall take effect immediately upon its adoption. ADOPTED this 23`I day of September, 2003. ristine Bainbridge, City Clerk APPROVED AS TO FORM: War 'tat ey Sch Iv Interim City Attorney Resolution 03-U47 CITY OF SPOKANE VALLEY Michael DeVleminayor Paec 6 of 6 CITY OF SPOKANE VALLEY Request for Council Action Meeting Date: February 6, 2018 Check all that apply: ['consent ❑ old business ['information ® admin. report Department Director Approval: ❑ ['new business ['public hearing ['pending legislation ['executive session AGENDA ITEM TITLE: Pre -Law Enforcement Academy GOVERNING LEGISLATION: Interlocal Agreement for Law Enforcement Services as Provided by the Spokane County Sheriffs Office to the City of Spokane Valley. PREVIOUS COUNCIL ACTION TAKEN: Approved Interlocal Agreement 17-104 on July 25, 2017 BACKGROUND: Staffing shortages in the Spokane Valley Police Department have prevented the Department from reaching its full potential. Many more scheduled retirements over the next few years could exacerbate this problem. The Department has already taken steps to fill vacancies through the use of hiring bonuses, enhanced job recruitment, and accessing nationwide Public Safety Testing applicant pools. In order to meet the current and future staffing needs, the Spokane Valley Police Department (SVPD) is requesting support from the Spokane Valley City Council to implement an internal Spokane County Sheriffs Office (SCSO) training academy. Currently, officer candidates hired by the SCSO have to wait until the next scheduled State-run academy, which could be six months or more. Additionally, academies are not always held on the east side of the state, requiring candidates to spend 18 weeks on the west side of the state. The delay before training begins often results in SVPD losing candidates to other jurisdictions than can start them more quickly. The lengthy training in a State academy without supervision or assistance from SVPD and the SCSO that hired them results in candidates quitting the program, washing out, or problems going unnoticed until later in the field training portion of their training, resulting in wasted time and effort and having to wait until the next state academy to fill those positions. Having a local pre -academy will allow candidates to begin training immediately, acclimate to the community and the organization, allow training officers to provide assistance to identify problems with candidates, improving success rates and determining early on if a candidate is not suited for police work. The Department is hopeful the State will accept the SCSO Academy as a full accredited academy that can be used in lieu of the state academy, which would allow more tailored training and get officers on the street more quickly. The State academies would still be used to handle overflow candidates. In conjunction with the SCSO pre -academy, Chief Werner is recommending that we shift a current unfilled shared detective position to a training sergeant position that would accompany officer candidates through the training process and increase successful training completion rates and provide a higher level of training. OPTIONS: Provide feedback to staff on level of support for SCSO Pre -training Academy, and Training TAC (Teacher, Administrator, Counselor) Officer. RECOMMENDED ACTION OR MOTION: Provide feedback to Staff. BUDGET/FINANCIAL IMPACTS: Academy would reduce training time and fill open positions sooner, potentially reducing overtime for meeting minimum staffing levels for unfilled positions. There is an initial $45,000 ($22,500 SV Share) one-time cost for a review by WSU. If the pre - academy becomes a full replacement academy, there would be additional costs that would be funded through savings achieved. The TAC Officer has no impact compared to a filled Safe Street Detective position that will be shifted, but would be approximately $50,000 more annually than that same unfilled detective position. STAFF CONTACT: Morgan Koudelka, Senior Administrative Analyst; Mark Werner, Spokane Valley Police Chief. ATTACHMENTS: PowerPoint, Service and Cost Impact Statement Providing Innovative Training Solutions Future Training Solution 1 Today's Talking Points • Training Solution Vision • Current Training Process for the Basic Deputy • Future Training Solution • Training Enhancements • Resources Needed to Meet the Vision • Desired Outcomes • Strategic Assistance Future Training Solution 2 Vision Through partnerships with higher education and key community leadership, the SCSO and SVPD will develop an adult based, self sustainable, innovative and a `procedural -justice -focused' law enforcement Pre -Basic training academy, meeting the need of the SCSO, SVPD, Community we serve, and the Training Recommendation authored by the President's 21st Century Policing Task Force. Future Training Solution Current Basic Training Process Pre Academy 1 week • Future Training Solution Washington State Academy 18 Weeks Post Academy Training 4 Weeks FTO Program 18 Weeks 41 Weeks of Training •4 Future Training Solution 1 week Pre - Academy Future Training Solution Academy + Coach Car Learning Platform 22 weeks 23 Weeks Ready to Work Alongside the Community Future Training Solution Current Training Costs/Resources 1 week of Pre - Academy 18 weeks at WCJTC BLEA 4 weeks of Post Academy Training 18 Weeks of Field Training 1640 Hours X $38 = $62,320 per new hire 18 new hires per year $1,121,760 Future Training Costs 1 week of Pre - Academy 880 hour (22 weeks) SCSO Academy 920 hours X $38 = $34,960 per New Hire 18 New Hires per year $629,280 Savings per year $492,480 Training Enhancements Communication and Behavior Observation Crisis Intervention Training Community Oriented Policing Prompt Application of Learning Greater Level of Retention and Transfer of new skill and knowledge • Research Based/ Strategic Social Interaction Model • Bias (Explicit & Implicit), Emotional and Cultural Intelligence • Procedural Justice & Community Trust Building • Base Line vs. Anomaly • Interact with Crisis Situations using de-escalation techniques , improving officers safety and the community safety • Exposed to and understanding of local mental health profession • Exposed to Community Groups • Listen and articulate what the Community is saying • Able to work with a coach on how to best respond to the Community • Weekly Reality Based Training (Performance and Technology Based) • Exposed to and participate in activities while riding in the car with a coach 8 hours a week • Example: Use of Radio, New World, Geographic's, Traffic, Officer Safety, Communication, Crisis Intervention etcetera. • 11 weeks with a coach (Learning Platform) • Further Assignments will be facilitated by the coach • Testing and Evaluation What Resources Are Needed To Meet The Vision? Logistical Needs i Personnel Teacher, Administrator, Counselor (TAC) Defensive Tactics/Reality Based Instructor Firearms Instructor Accreditation Manager Future Training Solution Technology Tablet's Augmented Virtual & Reality Based Learning Evaluation Emergency Vehicle Operation Skid Car VirTra: Firearms Training Sim Develop a 21st Century Policing Academy Partner with WSU Instructional Systems Design (ADDIE) Develop innovative content Develop a new and innovafive learning platform for the coach/car Implement pre and post evaluation tools WIDS Document Outcomes Demonstrates alignment with National Standards Common Curriculum Secure client Owned data Guidance for development of high quality curriculum •8 President Task Force on 21e6 Century IPolicing Training Recommendation • Community Policing • Interpersonal and Communication Skills • Bias Awareness • Scenario -Based, Situational Decision Making • Procedural Justice and Impartial Policing • Trauma and Victim Services • Languages and Cultural Responsiveness Desired Outcome —N— 'Procedural-Justice- Focused' 'Procedural -Justice - Focused' Researched Based & Best Practice Accreditation (IADLEST) von of irccfor IADLEST m 52% .,asrg'a a�a']43'Tn f4' • Future Training Solution Innovative Sustainable Training Platform Decreased Stress Training will meet community & organization needs Decreased Overtime Augmented Virtual & Reality Based Training & Technology j Money Saved • Immediate Application • Defining Emotional - Cognitive Moments for learning • Appropriate and measured stress inoculation. • Objective, timely, measured feedback (i.e., self, peers, instructors, etc.) •9 Strategic Assistance Spokane Valle Spokane Valley Mayor • City Manager City Council Police Chief Washington State University Research Team, Spokane Iri1 Oversight Committees Political Groups •Local Legislators • W ASPC ociation of County Officials Future Training Solution TAC (Teacher, Administrator, Counselor) Officer Position Cost Impact and Service Level Impact Estimate Service Level Impact 111111110 hared Safe Streets Detective (Vacant 5 years) Safe Streets Task Force - The Regional Safe Streets Task Force Unit, which focuses on narcotics and gang investigations, currently has 1 sergeant, 4 detectives, and 1 deputy. One of the detective positions has been vacant for several years and those duties have been absorbed by other members of the unit and other units. There is no estimated impact on the service provided by the Safe Streets Unit. Training - The creation of the TAC position is expected to increase the officer candidate training completion percentage, identify officer candidate problems sooner, and reduce officer candidate training time, accelerating the time required for the officer candidate to become a full officer and be assigned to a platoon. Cost Impact This position will be filled by a patrol sergeant who is currently on injury leave. The FTE comes from a Safe Streets detective position that has been unfilled and has had no costs to Spokane Valley. The patrol sergeant position will be backfilled. The total cost to Spokane Valley depends on the scenario. Scenario 1: The SCSO Academy replaces the State Academy (This would likely be several years in the future as both academies would likely be necessary to meet all the hiring needs of the next few years) TAC Sergeant Salary and Benefits: $140,359 Spokane Valley Portion (50%): $70,180 Scenario 2: The SCSO Academy operates in conjunction with the State Academy TAC Sergeant Salary and Benefits: $140,359 Less 40% of 9 month's salary *: ($42,108) Subtotal TAC Sergeant S&B: $98, 251 Spokane Valley Portion (50%): S49,126 * A portion of the TAC Officer's salary would be reimbursed by the State. Note: The Safe Streets Detective position has been unfilled due to staffing shortages and prioritization of existing personnel. Typically Spokane Valley would have been paying approximately half of this shared position, about $60,000 - $75,000. CITY OF SPOKANE VALLEY Request for Council Action Meeting Date: February 6, 2018 Check all that apply: ['consent ❑ old business ['information ® admin. report Department Director Approval: ['new business ['public hearing ['pending legislation ['executive session AGENDA ITEM TITLE: Police Vehicle Colors and Graphics GOVERNING LEGISLATION: Interlocal Agreement for Law Enforcement Services as Provided by the Spokane County Sheriff's Office to the City of Spokane Valley. PREVIOUS COUNCIL ACTION TAKEN: Approved Interlocal Agreement 17-104 on July 25, 2017 BACKGROUND: The Council approved the current Interlocal Agreement for Law Enforcement Services in July of 2017, which stipulated that vehicles assigned to the City shall display the color, identification and logo of our City. Council indicated during the negotiation process that they preferred to keep the Spokane Valley Police vehicles light blue in color. Police Chief Werner has asked that the Council consider some alternatives to ordering light blue police vehicles from the Ford factory. The alternatives are based upon ordering white vehicles and applying vinyl wraps and graphics locally to the vehicles. These alternatives would expedite shipments and maintain consistency regardless of changes in colors available at the factory. This presentation presents several options for the Council to consider. OPTIONS: 1.) Continue to order light blue vehicles from Ford; 2.) Order white vehicles and apply a two-tone partial wrap locally; or 3.) Order white vehicles and apply a full light blue wrap locally. RECOMMENDED ACTION OR MOTION: Provide feedback to Staff. BUDGET/FINANCIAL IMPACTS: Depends on the option selected. STAFF CONTACT: Morgan Koudelka, Senior Administrative Analyst Mark Werner, Spokane Valley Police Chief ATTACHMENTS: PowerPoint Police Vehicle Colors SeniorAdministrative Analyst Morgan Koudelka SpokaneValley Police Lt. Jay McNaII SpokaneValley Police Chief Mark Werner S`�'"okane Valley SPOKANE VALLEY POLICE DEPARTMENT VEHICLE COLOR AND GRAPHICS • As part of the 2017 negotiations, Council decided to maintain the current light blue color for police vehicles. This is a Ford factory color. POLICE VEHICLES (CONT.) • Recently, staff was approached by police Chief Werner and asked to consider some different alternatives. • The reasons for looking at alternatives are as follows. • We do not know how long Ford will offer the current Light Blue as a color. This happened once before when Ford discontinued the Ice Blue color the City had been using on Police Vehicles since incorporation. • Ford will only fill orders for Light Blue as enough orders are accumulated to make it worthwhile. This delays orders for an unknown period of time and makes planning more difficult. • If a vehicle is destroyed an immediate replacement is not available. • If vehicles are acquired with a different color, painting the vehicles will cost $5,000 - $6,000. 3 OPTION i -WHITE WITH WRAP • Order the vehicles white • Apply a vinyl wrap locally • Pros • Expedites orders of vehicles • Allows flexibility for colors • Protects City against discontinuation of factory color • Lower cost than re -painting • Cons • Light Blue is not currently an extra charge from Ford and an after -market wrap would be an added charge 4 OPTION iA-TWO-TONE PARTIAL WRAP 5 OPTION iA-TWO-TONE PARTIAL WRAP (CONT.) �IA.LLEV. �� SF'OILANEonto CRIME CHECK 45 . OPTION 3A COSTS AND BENEFITS • Pros • Less expensive than full wrap • $1,548 per vehicle • $1o,836 to wrap 7 new vehicles per year (estimated replacement schedule) • $1o8,78o to wrap all existing vehicles (if Council chose to change all vehicles now for consistency, as it would take approximately 10 years to change all vehicles through replacement). • Two-tone presents a more distinctive law enforcement color scheme • Expedites factory ordering and wrap processing time • Controls consistency of fleet identity • Cons • Adds costs when not currently necessary OPTION iA-ALTERNATIVE COLOR SCHEMES • Green and White matches County Sheriff color scheme, giving the appearance of a greater police presence, and making it easier for County deputies to work in or provide aid to Spokane Valley • Black and White provides a more traditional police color scheme • "Spokane Valley" graphic on side can be made larger to increase identity and distinction of City. SVPD logo remains on rear of vehicles. OPTION iB-FULL-BODY WRAP OPTION iB- COSTS AND BENEFITS • Pros • Eliminates waiting for new and replacement vehicles • Maintains existing color scheme • Cons • More expensive than partial wrap • $2,948 per vehicle • $2o,636 to wrap 7 new vehicles per year • Increases current costs when it is not currently necessary 10 OPTION i -STATUS QUO • Keep existing color scheme — Full Light Blue • Keep ordering color from Ford factory • Pros • No additional cost as long as Ford continues to provide color • Maintains SVPD color identity • Cons • Likely will have to wait longer for orders to be filled • Will not be able to quickly replace a destroyed vehicle • If Ford discontinues color, City may have short notice to determine response 11 CONTINGENCY PLAN FOR OPTION 2 • If Ford discontinues color: A. Choose another factory color B. Order white vehicles and wrap to blue C. Order white vehicles and wrap with another color scheme 12 OPTION i—HYBRID OPTION • Keep ordering Light Blue vehicles from Ford but utilize white vehicles with wrap when SVPD needs immediate replacement vehicles. 13 Year Budget Actual Over/(Under) 2014 $18,144,552 $ 17,181, 226 $ (963,326) 2015 $18,896,608 $ 17,758,027 $ (1,138,581) 2016 $ 19,713,401 $ 17,838,656 $ (1,874,745) LAW ENFORCEMENTAGREEMENT HISTORICAL BUDGETTO ACTUAL COSTS 14 NEXT STEPS • Council Feedback • OrderVehicles • Paint or wrap remaining existing vehicles that need to match patrol vehicles 15 To: From: Re: DRAFT ADVANCE AGENDA as of February 1, 2018; 10:30 a.m. Please note this is a work in progress; items are tentative Council & Staff City Clerk, by direction of City Manager Draft Schedule for Upcoming Council Meetings February 13, 2018, Special Meeting, Winter Workshop, 8:30 a.m. — 3:00 p.m. [due Tue, Feb 61 February 13, 2018, 6 pm Council Meeting Cancelled February 20, 2018, Study Session, 6:00 p.m. [due Tue, Feb 13] ACTION ITEM: 1. First Reading Proposed Ordinance 18-005, Spokane Housing Authority Re -Authorization, E.Lamb (10 min) NON -ACTION ITEMS 2. Functional Classification of Streets - Colin Quinn -Hurst (20 minutes) 3. Barker Grade Separation Contract — Gloria Mantz, Bill Helbig (20 minutes) 4. Advance Agenda (5 minutes) [*estimated meeting: 55 mins] February 27, 2018, Formal Meeting Format, 6:00 p.m. [due Tue, Feb 20] Proclamation: Developmental Disabilities Awareness Month 1. Consent Agenda (claims, payroll, minutes) (5 minutes) 2. Second Reading Ordinance 18-003 Amending Street Standards — Henry Allen, Micki Harnois (15 minutes) 3. Second Reading Ordinance 18-004 Updating Subdivision Regulations — Lori Barlow 4. Second Reading Ordinance 18-005 Spokane Housing Authority, Re-Auth. —E.Lamb 5. Motion Consideration: Barker Grade Separation Contract — Gloria Mantz, Bill Helbig 6. Admin Report: Potential Grant Opportunities (FMSIB and CSP) — Adam Jackson 7. Admin Report: Advance Agenda 8. Info Only: (a)Dept Reports; (b) Potential grant Opps (SRTC, SRTS, PBS) [*estimated meeting: 85 mins] (10 minutes) (10 minutes) (20 minutes) (20 minutes) (5 minutes) March 6, 2018, Study Session, 6:00 p.m. 1. Proposed Amended TIP — Colin Quinn -Hurst 2. Accomplishments Report (2017) 3. Advance Agenda March 13, 2018, Formal Meeting Format, 6:00 p.m. 1. PUBLIC HEARING: Proposed Amended 2018 TIP — Colin Quinn -Hurst la. Proposed Resolution Amending 2018 TIP 2. Consent Agenda (claims, payroll, minutes) 3. Motion Consideration: Potential Grant Opportunities (FMSIB and CSP) — Adam Jackson 4. Admin Report: Potential Grant Opportunities (SRTC, SRTS, PBS) — Adam Jackson 5. Advance Agenda [due Tue, Feb 271 (20 minutes) (— 90 minutes) (5 minutes) [*estimated meeting: 115 mins] [due Tue Mar 61 (15 minutes) March 20, 2018, Study Session, 6:00 p.m. 1. Painted Hills Update — John Hohman, Cary Driskell, Erik Lamb 2. Advance Agenda (5 minutes) (20 minutes) (20 minutes) (5 minutes) [*estimated meeting: 65 mins] [due Tue Mar 131 (25 minutes) (5 minutes) Draft Advance Agenda 2/1/2018 1:09:36 PM Page 1 of 2 March 27, 2018, Formal Meetin2 Format, 6:00 p.m. 1. Consent Agenda (claims, payroll, minutes) 2. Motion Consideration: Potential Grant Opportunities (SRTC, SRTS, PBS) 3. Advance Agenda 4. Info Item: Department Reports April 3, 2018, Study Session, 6:00 p.m. 1. Airport Update — Larry Krauter April 10, 2018, Formal Meetin2 Format, 6:00 p.m. 1. Consent Agenda (claims, payroll, minutes) April 17, 2018, Study Session, 6:00 p.m. April 24, 2018, Formal Meetin2 Format, 6:00 p.m. 1. Consent Agenda (claims, payroll, minutes) 2. Info Item: Department Reports Mav 1, 2018, Study Session, 6:00 p.m. 1. Advance Agenda Mav 8, 2018, Formal Meeting Format, 6:00 p.m. 1. Consent Agenda (claims, payroll, minutes) *time for public or Council comments not included OTHER PENDING AND/OR UPCOMING ISSUES/MEETINGS: Alarm Registration Update Citizen Recognition (city keys) Donation Recognition Duplex/Single Family Dwellings Definition Governance Manual ITS/SRTMC Discussion Naming City Facilities Protocol Police Dept Quarterly Rpt (April, July, Oct, Jan) Police Precinct Lease Renewal (Nov '18) Retail Recruitment Follow-up Sign Ordinance Street Illumination (ownership, cost, location) Tobacco 21 Resolution Transportation & Infrastructure Utility Facilities in ROW [due Tue Mar 201 (5 minutes) (10 minutes) (5 minutes) — Adam Jackson [due Tue Mar 271 (15 minutes) [due Tue April 31 (5 minutes) [due Tue April 101 [due Tue April 171 (5 minutes) [due Tue April 241 [due Tue Mav 11 (5 minutes) Draft Advance Agenda 2/1/2018 1:09:36 PM Page 2 of 2