Current and Forecasted Traffic Sample Clauses

Current and Forecasted Traffic. The District 4 Office of Planning developed the traffic forecasts for the 2062 design year on December 4, 2018. The 2022 Average Daily Traffic (ADT) on SR 87 from PM 0.0 to PM 6.1 is 208,700 vehicles. The ADT is expected to increase to a projected demand of 268,400 vehicles by 2062. Also, the 2020 percentage of trucks (% trucks) is 2.39%, and it is expected to remain at 2.39% in 2062. Table 4-5 shows the current and forecasted traffic information on SR 87 from PM 0.0 to PM 6.1 for design years 2018, 2022, 2032, 2042, and 2062. ADT 202,800 208,700 223,600 238,500 268,400 DHV — — — 18,400 — % Trucks 2.39 2.39 2.39 2.39 2.39 Median lanes TI — — 9.50 10.00 11.00 Median lanes ESAL — — 1,342,000 2,775,000 5,920,000 Two right lanes TI — — 11.00 12.00 13.00 Two right lanes ESAL — — 5,366,000 11,100,000 23,683,000 Notes: — = not applicable ADT = Average Daily Traffic DHV = Design Hourly Volume ESAL = Equivalent Single Axle Load PM = post mile(s) SR = State Route TI = Traffic Index The District 4 Office of Traffic Safety provided the accident data and analysis on July 22, 2020. A total of 1,048 accidents, with one fatal accident, occurred within the project limits (SR 87 from PM 0.0 to PM 6.1) during the most-recent available 3-year period (October 1, 2016, to September 30, 2019). The actual fatal accident rate is lower than the average fatal accident rate for similar facilities statewide. The fatal accident occurred on the southbound (SB) SR 87 off-ramp to Almaden Expressway on June 16, 2019, at 06:48 hours. Vehicle one (V1) was traveling at 80 miles per hour. Due to an unsafe speed, person 1 (P1) was unable to successfully negotiate the westerly curve in the roadway. This failure allowed the left rear of V1 to collide with a pile of dirt on the east side of the roadway. V1 then lost control and rotated in a counterclockwise direction, causing V1 to leave the west side of the roadway. V1 then collided with the sound wall on the west side of the roadway two times. The force by which V1 collided with the sound wall, caused V1 to overturn three times, colliding with the dirt embankment on the west side of the roadway each time. P1 sustained fatal injuries as a result of this collision. P1 caused the collision by traveling at an unsafe speed for then-current weather/traffic conditions. Table 4-6 compares the actual accident rates within the project limits with the average accident rates for similar facilities statewide during the study period. 1 340 707 1,048 0.001 0.3...
AutoNDA by SimpleDocs
Current and Forecasted Traffic. The current and forecasted traffic information for the project limits is shown below by segment. Ala-80 from PM R7.6 to CC-80 at Cutting Boulevard (PM 2.0): • Count Year (2020) average Daily • Construction Year (2022) ADT 238,200 • Design Year (2042) ADT 247,400 • Truck% 4.81% • 20-year Traffic Index (TI) 14.00 • 20-year Equivalent Single Axle Load (ESAL) 50,547,000 CC-80 from Cutting Boulevard (PM 2.0) to Hilltop Drive (PM 6.0): • Count Year (2020) ADT 258,600 • Construction Year (2022) ADT 260,100 • Design Year (2042) ADT 275,000 • Truck% 4.00% • 20-year TI 13.50 • 20-year ESAL) 43,862,000 CC-80 from Hilltop Drive (PM 6.0) to State Route (SR) 4 (PM 10.0) • Count Year (2020) ADT 245,000 • Construction Year (2022) ADT 246,500 • Design Year (2042) ADT 260,900 • Truck% 4.60% • 20-year TI 14.00 • 20-year ESAL 59,168,000 CC-80 from SR 4 (PM 10.0) to Xxxxxxxx (PM 13.5): • Count Year (2020) ADT 178,700 • Construction Year (2022) ADT 179,700 • Design Year (2042) ADT 189,900 • Truck% 4.37% 5.18% • 20-year TI 14.00 • 20-year ESAL 47,231,000 As shown in the tables below, the accident information classified as “All” considers all collisions, combining data on collisions that occurred in both the westbound direction and the eastbound direction of the project mainline segments, exclusive of the I-80 ramps, in Alameda County from PM R7.60 to PM 8.036 and in Contra Costa County from PM 0.0 to PM 13.5.
Current and Forecasted Traffic. The future travel forecasting was based on the assumption that the project location is a rural setting and planned land use in the area growth rate of 2.48% was used for forecasting purposes. Construction Year ADT (2024) 20,500 10,400 Future ADT (2044) 33,500 17,000 Future Year ADT (2064) 54,500 28000 DHV (2044) 2,850 1500 DHV (2064) 4,650 2,400 T (%) (2044, 2064) 6% 5% D (%) (2044, 2064) 60% 100% 20 Year ESAL (2044) 10,120,000 8,320,000 20 Year TI (2044) 12 11.5 40 Year ESAL (2064) 28,150,000 23,210,000 40 Year TI (2064) 13.5 13
Current and Forecasted Traffic. Table 4-5 lists current and forecasted traffic information for Main Line and Ramps on SR 4 within the project limits. Count Year ADT (2015) 90,800 Construction Year ADT (2026) 102,400 Design Year ADT (2046) 123,500 DHV (2046) 8,600 D% 54.1% Truck% 5.09% Notes: ADT = Average Daily Traffic D% = directional distribution (% of traffic moving in the peak travel direction) DHV = Design Hourly Volume SR = State Route Table 4-6 lists the estimated Traffic Indexes (TIs) and Equivalent Single Axle Loads (ESALs) for 20 years and 40 years after the completion of project construction for the mainline.
Current and Forecasted Traffic. Peak hour volumes for both AM and PM and average daily traffic (ADT) volumes for existing conditions and opening year and design year Build Alternative and No Build Alternative within the project limits are summarized in Table 4-2. 2 The TOAR qualitatively analyzed traffic conditions in the event that, due to funding and other constraints, the project opening year is 2026 instead of 2025, and subsequently the project design year is 2046 instead of 2045. See Sections 4.3.3.1 and 4.3.3.2, below. SB I-680: Between Alcosta and I-580 7,702 7,048 107,000 8,365 9,005 119,000 8,425 9,005 119,000 10,085 11,640 151,000 10,260 11,640 151,000 SB I-680: Between I- 580 and Stoneridge 5,080 5,618 81,000 5,900 6,315 89,000 5,950 6,335 89,000 6,795 8,240 112,000 6,995 8,330 112,000 SB I-680: Between Stoneridge and Xxxxxx 5,099 5,965 76,000 5,535 6,645 84,000 5,585 6,665 84,000 6,310 8,520 105,000 6,510 8,610 105,000 SB I-680: Between Sunol and Xxxxxxx 5,530 5,396 77,000 7,045 5,885 83,000 7,070 5,905 83,000 8,025 7,205 100,000 8,140 7,295 100,000 SB I-680: Between Xxxxxxx and Calaveras 7,031 5,573 92,000 8,795 6,735 102,000 8,795 6,735 102,000 10,095 8,760 125,000 10,095 8,760 125,000 NB I-680: Between Alcosta and I-580 6,777 6,965 96,000 7,250 7,755 108,000 7,250 7,755 108,000 9,845 9,590 139,000 9,845 9,590 139,000 NB I-680: Between I- 580 and Stoneridge 5,310 6,500 89,000 5,850 7,115 98,000 5,850 7,140 98,000 7,390 8,300 119,000 7,390 8,435 119,000 NB I-680: Between Stoneridge and Xxxxxx 4,637 4,549 80,000 5,640 5,935 88,000 5,640 5,965 88,000 7,115 6,850 107,000 7,115 7,005 107,000 NB I-680: Between Sunol and Xxxxxxx 4,608 4,687 72,000 5,145 5,215 80,000 5,145 5,305 80,000 6,665 6,260 100,000 6,665 6,305 100,000 NB I-680: Between Xxxxxxx and Calaveras 4,971 5,650 85,000 5,685 6,750 94,000 5,685 6,750 94,000 7,730 7,955 119,000 7,730 7,955 119,000 Source: Xxxx & Peers 2019
Current and Forecasted Traffic. The Design Hourly Volume (DHV) Total and the Annual Average Daily Traffic (AADT) is shown below in Table 1. Annual Average Daily Traffic (AADT) 6,500 7,826 8,190 Design Hour Volume (DHV) 810 933 1,000 Peak Hour Directional Vol % (NB/SB) 47.1/52.9 48.6/51.4 47.7/52.3 Truck Design Hourly Vol % (T) 11 11 11 Traffic Index (TI) 9 10 10.5 Design Speed (NB/SB) (mph) 55/30 55/30 55/30 *Northbound (NB), Southbound (SB), miles per hour (mph) TRUCKS IN ADT: 7.0% 10 YEAR TI: 8.5 Design Speed (V): 55 / 30 MPH 20 YEAR TI: 9.5 The following Collision Rate Summary Table shown below shows actual and average collision rates within the project location for the three-year period from January 1, 2016 thru December 21, 2018. The ‘actual’ collision rate in this segment is lower than the state ‘average’ for this type of facility. There was 1 reported collision during this three-year period. This collision was a rear end accident near PM 50.5 resulting from an obstruction on the roadway. The data from the 3-year collision history indicate that the nonstandard side slopes did not contribute to any collisions. There is no recognizable or correctable trend when reviewing the 3yr collision history. SB/SLO SR 1 0.00 .31 0.31 0.022 0.51 1.10 * The numbers in the table are units of collisions per million vehicle miles
Current and Forecasted Traffic. The District 3 Office of Traffic Forecasting and Modeling, provided the project limits' current and forecasted traffic data. See the traffic data shown in the tables below. Highway Post Mile SOL 080 40.7/R44.7 YOL 080 0.00/R11.72 YOL 050 0.00/3.12 SAC 050 0.00/L0.617 SAC 080 M0.00/M1.36 2019 140,000 150,795 149,198 198,012 123,530 2023 148,400 160,411 158,162 208,927 130,838 2029 161,000 174,834 171,608 225,300 141,800 2039 182,000 182,613 178,363 240,800 153,700 2049 203,000 190,391 185,117 256,300 165,600 2069 AADTT 245,000 205,948 198,626 287,300 189,400 2019 9,408 11,731 11,358 13,968 9,203 2023 9,972 12,479 12,043 14,736 9,751 2029 10,819 13,601 13,071 15,889 10,574 2039 12,230 14,205 13,591 16,986 11,465 2049 13,642 14,808 14,111 18,083 12,356 2069 DHV 16,464 16,015 15,151 20,277 14,138 2019 11,100 9,871 10,230 13,844 9,666 2023 11,700 10,679 10,972 14,470 10,388 2029 12,700 11,890 12085 15,410 11,470 2039 14,400 12,347 12,855 16,545 12,350 2049 16,000 12,803 13,625 17,680 13,230 2069 19,400 13,716 15,165 19,950 14,990 Directional % 55.0 53.0 54.0 54.0 67.0 DH Truck % 4.0 5.0 5.0 5.0 5.0 AADT=Average Annual Daily Traffic AADTT=Annual Average Daily Truck Traffic DHV=Design Hourly Volume ESALs & TIs SOL 080 40.7/R44.7 YOL 080 0.00/R11.72 YOL 050 0.00/3.12 Lane 1 Lane 2, 3,4 Lane 1 Lane 2,3 Lane 1 Lane 2, 3,4 2019 406,000 1,625,000 603,700 2,415,000 455,700 1,822,700 2023 430,000 1,722,000 613,800 2,455,000 463,300 1,853,000 2029 467,000 1,868,000 628,900 2,515,600 474,700 1,898,700 10-year 4,671,000 18,687,000 6,289,000 25,155,900 4,746,700 18,986,800 20-year 9,343,000 37,375,000 12,577,900 50,311,800 9,493,400 37,973,500 40-year 18,687,000 74,750,000 25,155,900 100,623,700 18,986,800 75,947,000 2019 8.0 9.5 8.5 10.0 8.0 9.5 2023 8.0 9.5 8.5 10.0 8.0 9.5 2029 8.0 9.5 8.5 10.0 8.0 9.5 10-year 11.0 12.5 11.0 13.0 11.0 13.0 20-year 11.5 14.0 12.0 14.5 12.0 14.0 40-year 12.5 15.0 13.0 15.5 13.0 15.0 2019 6.0 6.5 6.0 2023 6.0 6.5 6.0 2029 6.0 6.5 6.0 8.0 8.5 8.0 10-year 8.5 9.0 8.5 20-year 40-year 9.0 9.0 9.0 ESAL= Equivalent single axle load TI=Traffic Index ESALs & TIs SAC 050 0.00/L0.617 SAC 080 M0.00/M1.36 Lane 1 Lane 2,3,4 Lane 1 Lane 2,3,4 2019 538,700 2,154,600 279,600 1,118,200 2023 554,900 2,219,500 289,200 1,156,900 2029 579,200 2,316,700 303,800 1,215,400 10-year 5,548,900 22,195,400 2,892,300 11,569,300 20-year 11,097,700 44,390,900 5,784,600 23,138,500 40-year 22,195,400 88,781,700 11,569,300 46,277,000 2019 8.5 9.0 7.5 9.0 2023 8.5 9.0 8.0 9.0...
AutoNDA by SimpleDocs
Current and Forecasted Traffic. The current and forecasted traffic data were obtained from recently conducted traffic counts as well as a Port of Los Angeles/Port of Long Beach traffic model. The existing average daily traffic (ADT) along the intersection of Xxxxx Xxxxxxx Boulevard and Fries Avenue north of the existing at-grade rail crossing is approximately 13,440 vehicles per day. South Wilmington Grade Separation 5 January 22, 2007 Project Study Report Equivalent Under current conditions, the at-grade railroad crossing operates at a LOS D during the peak periods when a train is present. Future (2030) traffic volumes have been estimated based on anticipated growth in through-traffic and planned/proposed terminal developments in both Ports. By the year 2030, significant increases in traffic on Xxxxx Xxxxxxx Boulevard and Fries Avenue will also result in LOS F operating conditions at the at-grade rail crossing. Without a railroad grade separation, unit trains accessing the West Basin would continue to cause significant delays to truck and vehicle traffic ingress/egressing West Basin destinations. At-grade railroad crossing (AM) 10,829 B At-grade railroad crossing (PM) 13,440 E At-grade railroad crossing (AM) 18,854 D At-grade railroad crossing (PM) 23,399 F
Current and Forecasted Traffic 

Related to Current and Forecasted Traffic

  • Forecast Customer shall provide Flextronics, on a monthly basis, a rolling [***] forecast indicating Customer’s monthly Product requirements. The first [***] of the forecast will constitute Customer’s written purchase order for all Work to be completed within the first [***] period. Such purchase orders will be issued in accordance with Section 3.2 below.

  • TRUNK FORECASTING 57.1. CLEC shall provide forecasts for traffic utilization over trunk groups. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as facilities and/or equipment are available. Sprint shall make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Company forecast information must be provided by CLEC to Sprint twice a year. The initial trunk forecast meeting should take place soon after the first implementation meeting. A forecast should be provided at or prior to the first implementation meeting. The semi-annual forecasts shall project trunk gain/loss on a monthly basis for the forecast period, and shall include: 57.1.1. Semi-annual forecasted trunk quantities (which include baseline data that reflect actual Tandem and end office Local Interconnection and meet point trunks and Tandem-subtending Local Interconnection end office equivalent trunk requirements) for no more than two years (current plus one year); 57.1.2. The use of Common Language Location Identifier (CLLI-MSG), which are described in Telcordia documents BR 000-000-000 and BR 000-000-000; 57.1.3. Description of major network projects that affect the other Party will be provided in the semi-annual forecasts. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by CLEC that are reflected by a significant increase or decrease in trunking demand for the following forecasting period. 57.1.4. Parties shall meet to review and reconcile the forecasts if forecasts vary significantly.

  • Required Vendor Sales Reporting By responding to this Solicitation, you agree to report to TIPS all sales made under any awarded Agreement with TIPS. Vendor is required to report all sales under the TIPS contract to TIPS. If the TIPS Member entity requesting a price from the awarded Vendor requests the TIPS contract, Vendor must include the TIPS Contract number on any communications with the TIPS Member entity. If awarded, you will be provided access to the Vendor Portal. To report sales, login to the TIPS Vendor Portal and click on the PO’s and Payments tab. Pages 3-7 of the Vendor Portal User Guide will walk you through the process of reporting sales to TIPS. Please refer to the TIPS Accounting FAQ’s for more information about reporting sales and if you have further questions, contact the Accounting Team at xxxxxxxxxx@xxxx-xxx.xxx. The Vendor or vendor assigned dealers are responsible for keeping record of all sales that go through the TIPS Agreement and submitting same to TIPS.

  • Rolling Forecasts No later than ten (10) days of the Commencement Date, the Client shall provide Patheon with a written non-binding 18 month forecast of the volume of the Drug Product that the Client then anticipates will be required to be produced and delivered to the Client during each month of that 18 month period. Such forecast will be updated by the Client monthly on a rolling 18 month basis and updated forthwith upon the Client determining that the volumes contemplated in the most recent of such forecasts has changed by more than 20%. The most recent 18 month forecast shall prevail.

  • Year 2000 Compliance Each Party warrants that it has implemented a program the goal of which is to ensure that all software, hardware and related materials (collectively called “Systems”) delivered, connected with BellSouth or supplied in the furtherance of the terms and conditions specified in this Agreement: (i) will record, store, process and display calendar dates falling on or after January 1, 2000, in the same manner, and with the same functionality as such software records, stores, processes and calendar dates falling on or before December 31, 1999; and (ii) shall include without limitation date data century recognition, calculations that accommodate same century and multicentury formulas and date values, and date data interface values that reflect the century.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.50 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0150. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. The sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Master Contract Sales Report. Upon request, Contractor shall provide to Enterprise Services a detailed annual Master Contract sales report. Such report shall include, at a minimum: Product description, part number or other Product identifier, per unit quantities sold, and Master Contract price. This report must be provided in an electronic format that can be read by compatible with MS Excel. Small Business Inclusion. Upon Request by Enterprise Services, Contractor shall provide, within thirty (30) days, an Affidavit of Amounts Paid. Such Affidavit of Amounts Paid either shall state, if applicable, that Contractor still maintains its MWBE certification or state that its subcontractor(s) still maintain(s) its/their MWBE certification(s) and specify the amounts paid to each certified MWBE subcontractor under this Master Contract. Contractor shall maintain records supporting the Affidavit of Amounts Paid in accordance with this Master Contract’s records retention requirements.

  • Rolling Forecast (i) On or before the fifteenth (15th) calendar day of each month during the Term (as defined in Section 6.1 herein), Buyer shall provide Seller with an updated eighteen (18) month forecast of the Products to be manufactured and supplied (each a “Forecast”) for the eighteen (18) month period beginning on the first day of the following calendar month. The first two months of each Forecast will restate the balance of the Firm Order period of the prior Forecast, and the first three (3) months of the Forecast shall constitute the new Firm Order period for which Buyer is obligated to purchase and take delivery of the forecasted Product, and the supply required for the last month of such new Firm Order period shall not be more than one (1) full Standard Manufacturing Batch from the quantity specified for such month in the previous Forecast (or Initial Forecast, as the case may be). Except as provided in Section 2.2(a), Purchase Orders setting forth Buyer’s monthly Product requirements will be issued for the last month of each Firm Order period no later than the fifteenth calendar day of the first month of each Firm Order period, and such Purchase Order will be in agreement with the Firm Order period of the Forecast. If a Purchase Order for any month is not submitted by such deadline, Buyer shall be deemed to have submitted a Purchase Order for such month for the amount of Product set forth in Buyer’s Forecast for such month. (ii) The remainder of the Forecast shall set forth Buyer’s best estimate of its Product production and supply requirements for the remainder of the Forecast period. Each portion of such Forecast that is not deemed to be a Firm Order shall not be deemed to create a binding obligation on Buyer to purchase and take delivery of Products nor a binding obligation of Seller to deliver Products, except as otherwise provided in Section 2.2(f). (iii) Forecast and Purchase Orders shall be in full Standard Manufacturing Batches. If a Product has multiple SKUs, then the composite of the forecasted SKU must equate to the Standard Manufacturing Batch. One Purchase Order shall be issued for each full Standard Manufacturing Batch of Product and contain the required information set forth in Section 2.2(e) hereof.

  • Minimum Vendor License Requirements Vendor shall maintain, in current status, all federal, state, and local licenses, bonds and permits required for the operation of the business conducted by Vendor. Vendor shall remain fully informed of and in compliance with all ordinances and regulations pertaining to the lawful provision of goods or services under the TIPS Agreement. TIPS and TIPS Members reserve the right to stop work and/or cancel a TIPS Sale or terminate this or any TIPS Sale Supplemental Agreement involving Vendor if Vendor’s license(s) required to perform under this Agreement or under the specific TIPS Sale have expired, lapsed, are suspended or terminated subject to a 30‐day cure period unless prohibited by applicable statue or regulation.

  • Annual Compliance Statements The Master Servicer, the Special Servicer, the Certificate Administrator, the Custodian and, if it has made an Advance during the applicable calendar year, the Trustee shall furnish (and each of the Master Servicer, the Special Servicer, the Custodian and the Certificate Administrator (i) with respect to any Additional Servicer of such party that is a Mortgage Loan Seller Sub-Servicer, shall use commercially reasonable efforts to cause such Additional Servicer to furnish, and (ii) with respect to any other Additional Servicer of such party (other than any party to this Agreement), shall cause such Additional Servicer to furnish) (each such Additional Servicer and each of the Master Servicer, the Special Servicer, the Custodian, the Certificate Administrator and the Trustee (if applicable), a “Certifying Servicer”) to the Certificate Administrator, the Serviced Companion Loan Holders (or, in the case of a Serviced Companion Loan that is part of an Other Securitization Trust, the applicable Other Depositor and Other Exchange Act Reporting Party), the Operating Advisor (only in the case of an Officer’s Certificate furnished by the Special Servicer and after the occurrence and during the continuance of a Control Termination Event) and the Depositor on or before March 1 of each year, commencing in March 2017, an Officer’s Certificate (together with a copy thereof in XXXXX compatible format, or in such other format as otherwise agreed upon by the Depositor, the Certificate Administrator, the applicable Other Depositor, the applicable Other Exchange Act Reporting Party and the applicable Certifying Servicer) stating, as to the signer thereof, that (A) a review of such Certifying Servicer’s activities during the preceding calendar year or portion thereof and of such Certifying Servicer’s performance under this Agreement, or the applicable Sub-Servicing Agreement or primary servicing agreement in the case of an Additional Servicer, has been made under such officer’s supervision and (B) to the best of such officer’s knowledge, based on such review, such Certifying Servicer has fulfilled all its obligations under this Agreement, or the applicable Sub-Servicing Agreement or primary servicing agreement in the case of an Additional Servicer, in all material respects throughout such year or portion thereof, or, if there has been a failure to fulfill any such obligation in any material respect, specifying each such failure known to such officer and the nature and status thereof. The Master Servicer and the Special Servicer shall, and the Master Servicer and the Special Servicer shall cause (or, in the case of an Additional Servicer that is a Mortgage Loan Seller Sub-Servicer, shall use its commercially reasonable efforts to cause) each Additional Servicer hired by it to, forward a copy of each such statement to, prior to the occurrence and continuance of a Consultation Termination Event, the Controlling Class Representative and, for posting to the Rule 17g-5 Information Provider’s Website pursuant to Section 12.13, the Rule 17g-5 Information Provider. Promptly after receipt of each such Officer’s Certificate, the Depositor (and, in the case of a Serviced Companion Loan that is part of an Other Securitization Trust, the applicable Other Depositor and Other Exchange Act Reporting Party) may review each such Officer’s Certificate and, if applicable, consult with the Certifying Servicer, as applicable, as to the nature of any failures by such Certifying Servicer, respectively, or any related Additional Servicer with which the Master Servicer or the Special Servicer, as applicable, has entered into a servicing relationship with respect to the Mortgage Loans or the Companion Loans in the fulfillment of any Certifying Servicer’s obligations hereunder or under the applicable sub-servicing or primary servicing agreement. The obligations of each Certifying Servicer under this Section apply to each Certifying Servicer that serviced a Mortgage Loan or Companion Loan during the applicable period, whether or not the Certifying Servicer is acting in such capacity at the time such Officer’s Certificate is required to be delivered. With respect to each Outside Serviced Mortgage Loan serviced under the applicable Outside Servicing Agreement, the Certificate Administrator shall request, and upon receipt deliver to the Depositor, from a “Servicing Officer” or “Responsible Officer” (as such terms are defined in the applicable Outside Servicing Agreement), as applicable, of the related Outside Servicer, Outside Special Servicer, Outside Custodian, Outside Trustee and Outside Paying Agent or Outside Certificate Administrator an Officer’s Certificate in form and substance similar to the Officer’s Certificate described in this Section or such other form as is set forth in the Outside Servicing Agreement.

  • Year 2000 Compliant Borrower shall perform all acts reasonably necessary to ensure that (a) Borrower and any business in which Borrower holds a substantial interest, and (b) all customers, suppliers and vendors whose compliance is likely to be material to Borrower's business, become Year 2000 Compliant in a timely manner. Such acts shall include, without limitation, performing a comprehensive review and assessment of all Borrower's systems and adopting a detailed plan, with itemized budget, for the remediation, monitoring and testing of such systems. As used in this paragraph, "Year 2000 Compliant" shall mean, in regard to any entity, that all software, hardware, firmware, equipment, goods or systems utilized by or material to the business operations or financial condition of such entity, will properly perform date sensitive functions before, during and after the year 2000. Borrower shall, immediately upon request, provide to Agent such certifications or other evidence of Borrower's compliance with the terms of this paragraph as Bank may from time to time require.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!