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.
PREVAILING WAGE RATES - PUBLIC WORKS AND BUILDING SERVICES CONTRACTS If any portion of work being Bid is subject to the prevailing wage rate provisions of the Labor Law, the following shall apply:
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.
Certification Regarding Prohibition of Boycotting Israel (Tex Gov. Code 2271) If (a) Vendor is not a sole proprietorship; (b) Vendor has ten (10) or more full-time employees; and (c) this Agreement or any agreement with a TIPS Member under this procurement has value of $100,000 or more, the following certification shall apply; otherwise, this certification is not required. Vendor certifies, where applicable, that neither the Vendor, nor any affiliate, subsidiary, or parent company of Vendor, if any, boycotts Israel, and Vendor agrees that Vendor and Vendor Companies will not boycott Israel during the term of this Agreement. For purposes of this Agreement, the term “boycott” shall mean and include refusing to deal with, terminating business activities with, or otherwise taking any action that is intended to penalize, inflict economic harm on, or limit commercial relations with Israel, or with a person or entity doing business in Israel or in an Israeli-controlled territory but does not include an action made for ordinary business purposes. When applicable, does Vendor certify? Yes
Unbundled Sub-Loop Concentration System (USLC 2.9.1 Where facilities permit and where necessary to comply with an effective Commission order, BellSouth will provide <<customer_name>> with the ability to concentrate its sub-loops onto multiple DS1s back to the BellSouth Central Office. The DS1s will then be terminated into <<customer_name>>’s collocation space. TR-008 and TR303 interface standards are available.
Cooperation on Preventing End User Fraud The Parties agree to cooperate fully with one another to investigate, minimize, prevent, and take corrective action in cases of fraud.
Use of Interconnection Facilities by Third Parties 6551 Error! Hyperlink reference not valid.9.9.1 Purpose of Interconnection Facilities. 6551
Certification Regarding Prohibition of Certain Terrorist Organizations (Tex Gov. Code 2270) Vendor certifies that Vendor is not a company identified on the Texas Comptroller’s list of companies known to have contracts with, or provide supplies or services to, a foreign organization designated as a Foreign Terrorist Organization by the U.S. Secretary of State. Does Vendor certify? 3 Yes
Green Economy/Carbon Footprint a) The Supplier/Service Provider has in its bid provided Transnet with an understanding of the Supplier’s/Service Provider’s position with regard to issues such as waste disposal, recycling and energy conservation.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.