Federally Recognized Tribal Governments in the Project Area Sample Clauses

Federally Recognized Tribal Governments in the Project Area. The U.S. Department of Interior, Bureau of Indian Affairs (BIA) maintains a list of 561 Federally Recognized Tribes (73 FR 66, April 4, 2008). Alaska Tribes in proximity to the proposed Port MacKenzie Rail Extension have been identified from this list. Proximity is defined as in or near the Little Susitna River and Knik Arm watersheds. The following Tribes, Tribal groups and Native corporations were notified by letter dated February 12, 2008 of the scoping process for the Port MacKenzie Rail Extension EIS, and have been advised that further information regarding government-to-government coordination would be forthcoming. Federally Recognized Tribes • Chickaloon Village Traditional Council • Knik Tribal CouncilNative Village of Eklutna • Native Village of Tyonek Alaska Native Corporations • Chickaloon-Moose Creek Native Association, Inc. • Xxxx Inlet Region, Inc. • Eklutna, Incorporated • Knikatnu, Incorporated • Tyonek Native Corporation
AutoNDA by SimpleDocs

Related to Federally Recognized Tribal Governments in the Project Area

  • Restricted Use By Outsourcers / Facilities Management, Service Bureaus or Other Third Parties Outsourcers, facilities management or service bureaus retained by Licensee shall have the right to use the Product to maintain Licensee’s business operations, including data processing, for the time period that they are engaged in such activities, provided that: 1) Licensee gives notice to Contractor of such party, site of intended use of the Product, and means of access; and 2) such party has executed, or agrees to execute, the Product manufacturer’s standard nondisclosure or restricted use agreement which executed agreement shall be accepted by the Contractor (“Non-Disclosure Agreement”); and 3) if such party is engaged in the business of facility management, outsourcing, service bureau or other services, such third party will maintain a logical or physical partition within its computer system so as to restrict use and access to the program to that portion solely dedicated to beneficial use for Licensee. In no event shall Licensee assume any liability for third party’s compliance with the terms of the Non-Disclosure Agreement, nor shall the Non-Disclosure Agreement create or impose any liabilities on the State or Licensee. Any third party with whom a Licensee has a relationship for a state function or business operation, shall have the temporary right to use Product (e.g., JAVA Applets), provided that such use shall be limited to the time period during which the third party is using the Product for the function or business activity.

  • Commitment to Diversity in Government Contracting The State of Florida is committed to supporting its diverse business industry and population through ensuring participation by minority-, women-, wartime-, and service-disabled veteran business enterprises in the economic life of the State. The State of Florida Mentor Protégé Program connects minority-, women-, wartime-, and service- disabled veteran business enterprises with private corporations for business development mentoring. We strongly encourage firms doing business with the State of Florida to consider this initiative. For more information on the Mentor Protégé Program, please contact the Office of Supplier Diversity at (000) 000-0000 or xxxxxxx@xxx.xxxxxxxxx.xxx. Upon request, the Contractor shall report to the Department, spend with certified and other minority business enterprises. These reports will include the period covered, the name, minority code and Federal Employer Identification Number of each minority Vendor utilized during the period, commodities and services provided by the minority business enterprise, and the amount paid to each minority Vendor on behalf of each purchasing agency ordering under the terms of this Contract.

  • Outside the United States If you acquired the software in any other country, the laws of that country apply.

  • Increasing Seat Belt Use in the United States Pursuant to Executive Order 13043, 62 FR 19217 (Apr. 18, 1997), Recipient should encourage its contractors to adopt and enforce on-the- job seat belt policies and programs for their employees when operating company-owned, rented or personally owned vehicles.

  • State of New York Executive Department Office of General Services Procurement Services ‌ Corning Tower - 00xx Xxxxx Xxxxxx Xxxxx Xxxxx Xxxxxx, XX 00000 THIS CONTRACT (hereinafter “Contract” or “Centralized Contract”) for the acquisition of Project Based Information Technology Consulting Services is made between the People of the State of New York, acting by and through the Commissioner of the Office of General Services (hereinafter “State” or “OGS”) whose principal place of business is the 41st Floor, Corning Tower, The Governor Xxxxxx X. Xxxxxxxxxxx Empire Xxxxx Xxxxx, Xxxxxx, Xxx Xxxx 00000, pursuant to authority granted under New York State Finance Law §163, and SVAM INTERNATIONAL, INC. (hereinafter “Contractor”), with its principal place of business at 000 Xxxx Xxxxx Xxxx, Xxxxx 000, Xxxxx Xxxx, XX 00000. The foregoing are collectively referred to as the “Parties.”

  • NO OBLIGATION BY FEDERAL GOVERNMENT The U.S. federal government is not a party to this Contract or any purchase by a Participating Entity and is not subject to any obligations or liabilities to the Participating Entity, Supplier, or any other party pertaining to any matter resulting from the Contract or any purchase by an authorized user.

  • Use of District Facilities 3.4.1 The Association, upon request to the School Director, may use District facilities for meetings and other Association business without cost where no additional cost is incurred by the District. If additional cost is incurred by the District, such cost will be borne by the Association.

  • Federal Government End Use Provisions We provide the Services, including related software and technology, for ultimate federal government end use solely in accordance with the following: Government technical data and software rights related to the Services include only those rights customarily provided to the public as defined in this Agreement. This customary commercial license is provided in accordance with FAR 12.211 (Technical Data) and FAR 12.212 (Software) and, for Department of Defense transactions, DFAR 252.227-7015 (Technical Data – Commercial Items) and DFAR 227.7202-3 (Rights in Commercial Computer Software or Computer Software Documentation). If a government agency has a need for rights not granted under these terms, it must negotiate with Us to determine if there are acceptable terms for granting those rights, and a mutually acceptable written addendum specifically granting those rights must be included in any applicable agreement.

  • Obligations of Registry Operator to TLD Community Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-­‐based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at xxxx://xxx.xxxxx.xxx/en/resources/registries/rrdrp with respect to disputes arising pursuant to this Section 2.19. Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto.

  • Special Rules Regarding Related Entities and Branches That Are Nonparticipating Financial Institutions If a Finnish Financial Institution, that otherwise meets the requirements described in paragraph 1 of this Article or is described in paragraph 3 or 4 of this Article, has a Related Entity or branch that operates in a jurisdiction that prevents such Related Entity or branch from fulfilling the requirements of a participating FFI or deemed-compliant FFI for purposes of section 1471 of the U.S. Internal Revenue Code or has a Related Entity or branch that is treated as a Nonparticipating Financial Institution solely due to the expiration of the transitional rule for limited FFIs and limited branches under relevant U.S. Treasury Regulations, such Finnish Financial Institution shall continue to be in compliance with the terms of this Agreement and shall continue to be treated as a deemed- compliant FFI or exempt beneficial owner, as appropriate, for purposes of section 1471 of the U.S. Internal Revenue Code, provided that:

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