Planning and Private Enterprise Sample Clauses

Planning and Private Enterprise. 37 a. General. 37 b. Governmental and Private Nonprofit Providers of Nonemergency Transportation. 37 c. Not Applicable. 38 Section 14. Preference for United States Products and Services. 38 a. Not Applicable. 38 b. Cargo Preference-Use of United States-Flag Vessels. 38 c. Fly America. 38 Section 15. Procurement. 38 a. Federal Standards. 38 b. Full and Open Competition. 38 c. Exclusionary or Discriminatory Specifications. 39 d. Geographic Restrictions. 39 e. In-State Bus Dealer Restrictions. 39 f. Neutrality in Labor Relations. 39 g. Federal Supply Schedules. 39 h. Force Account. 39 i. FTA Technical Review. 39 j. Project Approval/Third Party Contract Approval. 39 k. Preference for Recycled Products. 40 l. Clean Air and Clean Water. 40 m. National Intelligent Transportation Systems Architecture and Standards. 40 n. Rolling Stock. 40 o. Bonding. 41 p. Architectural Engineering, or Related Services. 41 q. Design-Build Projects. 42 r. Award to Other than the Lowest Bidder. 42 s. Award to Responsible Contractors. 42 t. Access to Third Party Contract Records. 43 u. Electronic and Information Technology. 43 Section 16. Leases. 43 a. Capital Leases. 43 b. Not Applicable. 43 Section 17. Patent Rights. 43 a. General. 44 b. Federal Rights. 44 c. License Fees and Royalties. 44 Section 18. Rights in Data and Copyrights. 44 a. Definition. 44 b. General. 44 c. Federal Rights in Data and Copyrights. 44 d. Not Applicable. 45 e. License Fees and Royalties. 45 f. Hold Harmless. 45 g. Restrictions on Access to Patent Rights. 45 h. Data Developed Without Federal Funding or Support. 45 i. Not Applicable. 46
AutoNDA by SimpleDocs
Planning and Private Enterprise. Sub-Recipient agrees to implement the Project in accordance with the following Federal planning and private enterprise provisions: 49 U.S.C. §§ 5303, 5304, 5306, and 5323(a)(1); Joint FHWA/FTA regulations, “Statewide Transportation Planning; Metropolitan Transportation Planning,” 23 C.F.R. Part 450 and 49 C.F.R. Part 613 and any amendments thereto. In addition to providing opportunities to participate in planning described in Paragraph 21 of these Terms, to the extent feasible, Sub-Recipient agrees to comply with 49 U.S.C. § 5323(k), which affords governmental agencies and nonprofit organizations that receive Federal assistance for nonemergency transportation from Federal Government sources (other than U.S. DOT) an opportunity to be included in the design, coordination, and planning of transportation services. To the extent applicable during the implementation of the Project, Sub-Recipient agrees to take into consideration the recommendations of Executive Order No. 12803, “Infrastructure Privatization,” 31 U.S.C. § 501 note, and Executive Order No. 12893, “Principles for Federal Infrastructure Investments,” 31 U.S.C. § 501 note. Audit and Inspection. Sub-Recipient will permit UTA, the Comptroller General of the United States and the Secretary of the United States Department of Transportation or their authorized representatives, to inspect all motor vehicle equipment, facilities and Project Equipment, all transportation services rendered by Sub-Recipient by the use of such vehicles and/or equipment, and all relevant Project data and records. All payments made by Sub-Recipient to any potential subcontractors for services required by these Terms shall be subject to audit by UTA. Sub-Recipient shall also permit the above named persons to audit the books, records and accounts of Sub-Recipient pertaining to the Project. If Sub-Recipient receives over $500,000 in Federal funds from all sources, Sub-Recipient shall submit an audit to UTA annually, following the procedures set forth in 2 CFR 200 Subpart F, 2 CFR § 200.500 et. seq.
Planning and Private Enterprise. (1) General The Contractor agrees to implement the Project in accordance with the following Federal planning and private enterprise provisions:
Planning and Private Enterprise 

Related to Planning and Private Enterprise

  • Red Hat Enterprise Linux Developer Suite Red Hat Enterprise Linux Developer Suite provides an open source development environment that consists of Red Hat Enterprise Linux with built-in development tools, certain Red Hat Enterprise Linux Add-Ons, Red Hat Enterprise Linux for Real Time, Smart Management and access to Software Maintenance, but no Development or Production Support. If you use any of the Subscription Services or Software associated with Red Hat Enterprise Linux Developer Suite for Production Purposes, or use the Red Hat Enterprise Linux Software Subscription entitlement independently, you agree to purchase the applicable number of Units of the applicable Software Subscription. Red Hat does not provide Production Support or Development Support for Red Hat Enterprise Developer Suite.

  • INTERNET PLANNING, ENGINEERING AND OPERATIONS ‌ Job Title: Internet/Web Engineer Job#: 2620 General Characteristics Integrally involved in the development and support of all Internet/Intranet/Extranet sites and supporting systems. Works closely with other IT groups and customers to define the system design and user interface based on customer needs and objectives. Participates in all phases of the development and implementation process, and may act as a project manager on special projects. Ensures the integration of the Web servers and all other supporting systems. Responsible for system tuning, optimization of information/data processing, maintenance and support of the production environment.

  • Associated Enterprises (a) an enterprise of a Contracting State participates directly or indirectly in the management, control or capital of an enterprise of the other Contracting State, or

  • Mining and Industrial Cooperation 1. The aims of cooperation in mining and industry sectors, carried out in the mutual interest of the Parties and in compliance with their policies, will be: (a) to focus cooperative activities towards sectors where mutual and complementary interests exist; and (b) to build on existing agreements and arrangements already in place between the Parties. 2. Mining and Industrial cooperation may include work in, but not be limited to, the following areas: (a) bio-mining (mining using biotechnology procedures); (b) mining techniques, specially underground mining, and conventional metallurgy; (c) productivity in mining; (d) industrial robotics for mining and other sector applications; (e) informatics and telecommunication applications for mining and industrial plant production; and (f) software development for mining and industrial applications. 3. The Parties will encourage and facilitate, as appropriate, the following activities including, but not limited to: (a) exchange of information, documentation and institutional contacts in areas of interest; (b) mutual access to academic, industrial and entrepreneurial networks in the area of mining and industry; (c) identification of strategies, in consultation with universities and research centres, that encourage joint postgraduate studies, research visits and joint research projects; (d) exchange of scientists, researchers and technical experts; (e) promotion of public/private sector partnerships and joint ventures in the support of the development of innovative products and services specially related to productivity in the sector activities; (f) technology transfer in the areas mentioned in paragraph 2; (g) designing of innovation technology models based in public/private cooperation and association ventures; and (h) information and experience exchange on mining environmental issues.

  • Felling and Bucking Felling shall be done to minimize breakage of Included Timber and dam- age to residual timber. Unless agreed otherwise, felling shall be done by saws or shears. Bucking shall be done to permit removal of all minimum pieces set forth in A2. Purchaser may buck out cull material when necessary to produce pieces meeting Utilization Standards. Such bucked out material shall contain a minimum amount of sound wood, not in excess of the net scale in percentage of gross scale, or based on the merchantability factor, whichever is stated in A2. If necessary to assess extent of defect, Purchaser shall make sample saw cuts or wedges. B6.411 Felling in Clearings. Insofar as ground conditions, tree lean, and shape of clearings per- mit, trees shall be felled so that their tops do not extend outside Clearcutting Units, construction clearings, and ar- eas of regeneration cutting. B6.000 Xxxxx Xxxxxxx. Stumps shall not exceed, on the side adjacent to the highest ground, the maximum heights set forth in A6, except that occasional stumps of greater heights are acceptable when Purchaser determines that they are necessary for safe and efficient conduct of logging. Unless otherwise agreed, Purchaser shall re-cut high stumps so they will not exceed heights specified in A6 and shall dispose of severed portions in the same manner as other logging debris. The xxxxx heights shown in A6 were selected with the objective of maximum reasonable utilization of the timber, unless Sale Area Map shows special areas where xxxxx heights are lower for aesthetic, land treatment, or silvicultural rea- sons.

  • Indiana Veteran Owned Small Business Enterprise Compliance Award of this Contract was based, in part, on the Indiana Veteran Owned Small Business Enterprise (“IVOSB”) participation plan, as detailed in the IVOSB Subcontractor Commitment Form, commonly referred to as “Attachment A-1” in the procurement documentation and incorporated by reference herein. Therefore, any changes to this information during the Contract term must be approved by IDOA’s IVOSB Division (“IVOSB Division”) and may require an amendment. It is the State’s expectation that the Contractor will meet the subcontractor commitments during the Contract term. The following certified IVOSB subcontractor(s) will be participating in this Contract: [Add additional IVOSBs using the same format.] IVOSB COMPANY NAME PHONE EMAIL OF CONTACT PERSON PERCENT Briefly describe the IVOSB service(s)/product(s) to be provided under this Contract and include the estimated date(s) for utilization during the Contract term: A copy of each subcontractor agreement must be submitted to the IVOSB Division within thirty (30) days of the effective date of this Contract. The subcontractor agreements may be uploaded into Pay Audit (Indiana’s subcontractor payment auditing system), emailed to XxxxxxxXxxxxxxxXxxxxxxxxx@xxxx.XX.xxx, or mailed to IDOA, 000 X. Xxxxxxxxxx Street, Room W-478, Indianapolis, IN 46204. Failure to provide a copy of any subcontractor agreement may be deemed a violation of the rules governing IVOSB procurement and may result in sanctions allowable under 25 IAC 9-5-2. Requests for changes must be submitted to XxxxxxxXxxxxxxxXxxxxxxxxx@xxxx.XX.xxx for review and approval before changing the participation plan submitted in connection with this Contract. The Contractor shall report payments made to certified IVOSB subcontractors under this Contract on a monthly basis using Pay Audit. The Contractor shall notify subcontractors that they must confirm payments received from the Contractor in Pay Audit. The Pay Audit system can be accessed on the IDOA webpage at: xxx.xx.xxx/xxxx/xxxx/xxxxxxxx.xxx. The Contractor may also be required to report IVOSB certified subcontractor payments directly to the IVOSB Division, as reasonably requested and in the format required by the IVOSB Division. The Contractor’s failure to comply with the provisions in this clause may be considered a material breach of the Contract.

  • Training and Professional Development C. Maintain written program procedures covering these six (6) core activities. All procedures shall be consistent with the requirements of this Contract.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Partnership Working 7.1 Partnerships will be supported by local authorities on four levels between:

  • Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

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