– Particulate Matter Conformity Determination Sample Clauses

– Particulate Matter Conformity Determination. In order for the project to obtain an FHWA conformity determination, a separate conformity determination for fine particulate matter (PM2.5) is needed before the Draft Environmental Document is issued for public review. The conformity process consists of completing a PM2.5 Assessment Form and related deliverables, engaging in interagency consultation with the Bay Area Air Quality Conformity Task Force (chaired by the Metropolitan Transportation Commission [MTC]), and engaging in public participation as part of the Draft Environmental Document public review. Potential PM2.5 effects from transportation projects are strongly correlated with truck volumes and percentages compared to overall traffic volumes on the same roadways. The US 000/Xxxxxxxx Xxxx interchange has high total vehicle volumes but relatively low truck 1 Caltrans District 4 currently advises the use of this model for construction emissions evaluations in the Bay Area.
AutoNDA by SimpleDocs

Related to – Particulate Matter Conformity Determination

  • Change Order Conditions All Change Orders are issued under the following conditions and shall contain the following language as appropriate:

  • Independence from Material Breach Determination Except as set forth in Section X.D.1.c, these provisions for payment of Stipulated Penalties shall not affect or otherwise set a standard for OIG’s decision that CHSI has materially breached this CIA, which decision shall be made at OIG’s discretion and shall be governed by the provisions in Section X.D, below.

  • Purchase Order Requirements Customers shall use a Request for Quote per section 287.056(2), Florida Statutes, when making purchases off of this State Term Contract. Customers shall issue Request for Quotes to at least 25 vendors approved to provide IT Staff Augmentation services in accordance with section 287.0591(5), Florida Statutes. Customers shall order services from the Request for Quote via a Purchase Order with the Customers’ selected Contractor. The terms of the Purchase Order shall not conflict with the terms and conditions established by this Contract. In accepting a Purchase Order, the Contractor recognizes its responsibility for all tasks and deliverables contained therein, warrants that it has fully informed itself of all relevant factors affecting accomplishment of the tasks and deliverables and agrees to be fully accountable for the performance thereof.

  • Product Specific Terms these terms apply to specific Products referenced in this section.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 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, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Dispute Process In the event of any Dispute, the Parties agree that they shall undertake a process to promote the resolution of a Dispute in the following order:

  • Formal Dispute Process Members representing: (i) any one of the three state Participant Groups or (ii) an aggregate of at least six (6) votes, may appeal the informal Dispute by signing and furnishing to the Regional Director, the Program Manager, and each other Member, a written request to initiate a formal Dispute. This request must, with reasonable specificity, identify the issue(s) in Dispute, the relief sought, and any supporting documentation. If such a request is not received by the Regional Director within ten

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

  • DISPUTE PROCEDURE (1) Unless otherwise provided in the Council's Constitution or in this Collective Agreement, any dispute within the registered scope of the Council shall be resolved as set out below:

Time is Money Join Law Insider Premium to draft better contracts faster.