Description of Proposed Contracting Requirements Sample Clauses

Description of Proposed Contracting Requirements. LLHP contract provisions have not previously been applied to FHWA funded projects due to its prohibition on Federal-aid highway projects. The scope of this SEP-14 pilot would be to assess the impact of utilizing LLHP contract provisions on full and open competition for Federal-aid projects. The pilot program will be used to compare and contrast the impact of LLHP contract provisions on competition for FHWA funded contracts against the long term benefit of creating a local workforce of skilled and qualified workers available to fill the employment needs for future transportation projects. Ultimately the goal is to evaluate whether utilization of LLHP contract provisions creates a competitive environment that result in the District receiving lower cost bids that are delivered with a reliable local labor force. The SEP-14 pilot will consist of the following:  DDOT will collect data during the bidding process and throughout the project to evaluate the impacts to the competitiveness of the contracting, including total project cost;  Contract provisions will require a good faith effort to meet the goals established for LLHP, as described in Section 3.1;  The impact on the local labor pool will be evaluated to determine whether there was an increase in the workforce of skilled and qualified workers available to fill the employment needs for future transportation projects; and  Preliminary, Interim and Final Reports will be submitted to FHWA to record findings and lessons learned. See Section 6 for Details
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Description of Proposed Contracting Requirements

  • Training Requirements Grantee shall:

  • COMPLIANCE WITH LICENSING REQUIREMENTS CONTRACTOR shall comply with all necessary licensing requirements and shall obtain appropriate licenses and display the same in a location that is reasonably conspicuous, as well as file copies of same with the County Executive Office.

  • Contracting Information Requirements Contractor represents and warrants that it will comply with the requirements of Section 552.372(a) of the Texas Government Code. Except as provided by Section 552.374(c) of the Texas Government Code, the requirements of Subchapter J (Additional Provisions Related to Contracting Information), Chapter 552 of the Government Code, may apply to the Contract and the Contractor agrees that the Contract can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter.

  • Data Submission Requirements As part of its registration and sponsorship of Registered Names in the Registry TLD, Registrar shall submit to the Registry System complete data as required by technical specifications of the Registry System that are made available to Registrar from time to time. Registrar hereby grants Registry Operator a non-exclusive, royalty free, non-transferable, limited license to such data for propagation of and the provision of authorized access to the TLD zone files and as otherwise required for Registry Operator to meet its obligations to ICANN and/or for Registry Operator’s operation of the Registry TLD.

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • Staffing Requirements Licensee will be in full compliance with the main studio staff requirements as specified by the FCC.

  • Selection of projects and financial parameters 4.1 Open calls and availability of funds (including number of calls, duration of calls, and estimated size):

  • Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).

  • Bidding Requirements The Advertisement or Invitation to Bid, Instructions to Bidders, Bid security form, if any, and the Bid form with any supplements.

  • Credentialing Requirements Registry Operator, through the facilitation of the CZDA Provider, will request each user to provide it with information sufficient to correctly identify and locate the user. Such user information will include, without limitation, company name, contact name, address, telephone number, facsimile number, email address and IP address.

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