Problem Deficiencies and Justification Sample Clauses

Problem Deficiencies and Justification. ‌ Some of the issues identified within the proposed project limits are as follows: • The performance measure identified in TAMP for the mainline existing asphalt pavement is, 5.1 miles in fair condition and 0.90 miles in poor condition, see Attachment K. _____ • The 2019 Deflection Study Report (Attachment J) indicates a maximum International Roughness Index (IRI) of 220 inches/mile in the EB direction and 273 inches/mile in the WB direction. As per Highway Design Manual (HDM), the maximum allowable value of IRI that does not require special consideration for design is 170 inches/mile. • The Automated Pavement Condition Survey (APCS) data for year 2016, collected for the most recent surface distresses showed signs of alligator, longitudinal and transverse cracks throughout the project limits. • The average 80th percentile deflection measurements at various test sections along EB and WB traveled way lanes, are greater than the tolerable deflections at the surface (TDS). • Shoulder widths along SR 119 within the project limits are nonstandard. The typical shoulder width is 2’ wide, except at the new subdivisions and new developments. • Pedestrian and bicycling facilities currently exist in segments around new subdivisions/developments only. • Fixed objects such as utility poles, large and small diameter trees are within the CRZ of the highway facility. • There are numerous flooding issues reported by Caltrans Maintenance at several locations along SR 119. Within the community of Pumpkin Center there is severe flooding and standing storm water issues.
AutoNDA by SimpleDocs
Problem Deficiencies and Justification 

Related to Problem Deficiencies and Justification

  • Failure to Meet Timelines Failure by the Union to comply with the timelines will result in the automatic withdrawal of the grievance. Failure by the Employer to comply with the timelines will entitle the Union to move the grievance to the next step of the procedure.

  • Rationale/Justification The Cisco Certified Network Associate Security (CCNA® Security) certification represents industry acknowledgement of technical skill attainment of competencies in the IT Security program.

  • Reasonable Suspicion Testing All Employees Performing Safety-Sensitive Functions A. Reasonable suspicion testing for alcohol or controlled substances may be directed by the Employer for any employee performing safety-sensitive functions when there is reason to suspect that alcohol or controlled substance use may be adversely affecting the employee’s job performance or that the employee may present a danger to the physical safety of the employee or another. B. Specific objective grounds must be stated in writing that support the reasonable suspicion. Examples of specific objective grounds include but are not limited to: 1. Physical symptoms consistent with alcohol and/or controlled substance use; 2. Evidence or observation of alcohol or controlled substance use, possession, sale, or delivery; or 3. The occurrence of an accident(s) where a trained manager, supervisor or lead worker suspects alcohol or other controlled substance use may have been a factor.

  • Rectification Where the surface irregularity of sub-grade and the various pavement course fall outside the specified tolerances contractor shall be liable .to rectify these in the manner described below and to the satisfaction of the Engineer - in-charge. .

  • Duty to report Force Majeure Event 21.5.1 Upon occurrence of a Force Majeure Event, the Affected Party shall by notice report such occurrence to the other Party forthwith. Any notice pursuant hereto shall include full particulars of: (a) the nature and extent of each Force Majeure Event which is the subject of any claim for relief under this Article 21 with evidence in support thereof; (b) the estimated duration and the effect or probable effect which such Force Majeure Event is having or will have on the Affected Party’s performance of its obligations under this Agreement; (c) the measures which the Affected Party is taking or proposes to take for alleviating the impact of such Force Majeure Event; and (d) any other information relevant to the Affected Party’s claim. 21.5.2 The Affected Party shall not be entitled to any relief for or in respect of a Force Majeure Event unless it shall have notified the other Party of the occurrence of the Force Majeure Event as soon as reasonably practicable, and in any event no later than 10 (ten) days after the Affected Party knew, or ought reasonably to have known, of its occurrence, and shall have given particulars of the probable material effect that the Force Majeure Event is likely to have on the performance of its obligations under this Agreement. 21.5.3 For so long as the Affected Party continues to claim to be materially affected by such Force Majeure Event, it shall provide the other Party with regular (and not less than weekly) reports containing information as required by Clause 21.5.1, and such other information as the other Party may reasonably request the Affected Party to provide.

  • Problem Statement School bus fleets are aging, and our communities have poor air quality. Replacing school buses with zero emission school buses will address both of these issues.

  • Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.

  • Deviation from Grievance Procedure The Employer agrees that, after a grievance has been discussed at Step 2 of the grievance procedure the Employer or his representatives shall not initiate any discussion or negotiations with respect to the grievance, either directly or indirectly with the aggrieved employee without the consent of the xxxxxxx or the Union.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • Notification of Error The Trust will notify USBFS of any discrepancy between USBFS and the Trust, including, but not limited to, failing to account for a security position in the Fund’s portfolio, upon the later to occur of: (i) three business days after receipt of any reports rendered by USBFS to the Trust; (ii) three business days after discovery of any error or omission not covered in the balancing or control procedure; or (iii) three business days after receiving notice from any shareholder regarding any such discrepancy.

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