Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.
Foreign Terrorist Organizations Contractor represents and warrants that it is not engaged in business with Iran, Sudan, or a foreign terrorist organization, as prohibited by Section 2252.152 of the Texas Government Code.
Special Permit from Relevant Ministerial/ Government Agencies and Foreign Capital Ownership Limitation Raw Material for Explosives (Ammonium Nitrate) with maximum foreign equity ownership of 49% and a special permit from the Minister of Defense (ISIC 2411) Industry of explosive materials and its components for industry need with maximum foreign equity ownership of 49% and a special permit from the Minister of Defense (ISIC 2429) Sugar Industry (Xxxxx Xxxxxxx Sugar, Refined Crystal Sugar and Raw Crystal Sugar) with maximum foreign equity ownership of 95% and a special permit from the Minister of Industry and the Minister of Agriculture, and it has to be integrated with the sugar plantation. The manufacturing of raw crystal sugar is required for any sugar manufacturer with sugarcane input capacity exceeding 8000 tons per day (ISIC 1542) Processing of plantation product industry (similar capacity or exceeding a certain capacity, according to Regulation of Minister of Agriculture Number 26 of 2007 with maximum foreign capital ownership of 95% with a special permit from Minister of Agriculture. - Fiber and Seed Cotton Industry (ISIC1514, 1711) - Crude oil industry (edible oil) from vegetable and animal, coconut oil industry, palm oil industry, rubber to be sheet, thick latex, crumb rubber industry, raw castor oil industry, sugar, sugar cane and sugar cane residue industry, black tea/green tea industry, dry tobacco leaves industry, Copra, Fiber, Coconut Charcoal, Dust, Nata de coco industry, Coffee sorting, cleaning and peeling industry, Cocoa cleaning, peeling and drying industry, cleaning and peeling seed other than coffee and cacao industry, cashew to be dry seed cashew and Cashew Nut Shell Liquid (CNSL) Industry, Peppercorn to be dry white pepper and dry black pepper industry (ISIC 1514, 2429, 1542, 1549, 1600, 2519, 1531)
CERTIFICATION REGARDING CERTAIN FOREIGN-OWNED COMPANIES IN CONNECTION WITH CRITICAL INFRASTRUCTURE (Texas law as of September 1, 2021) By submitting a proposal to this Solicitation, you certify that you agree to the following required by Texas law as of September 1, 2021: Proposing Company is prohibited from entering into a contract or other agreement relating to critical infrastructure that would grant to the company direct or remote access to or control of critical infrastructure in this state, excluding access specifically allowed by the Proposing Company for product warranty and support purposes. Company, certifies that neither it nor its parent company nor any affiliate of company or its parent company, is (1) owned by or the majority of stock or other ownership interest of the company is held or controlled by individuals who are citizens of China, Iran, North Korea, Russia, or a designated country; (2) a company or other entity, including governmental entity, that is owned or controlled by citizens of or is directly controlled by the government of China, Iran, North Korea, Russia, or a designated country; or (3) headquartered in China, Iran, North Korea, Russia, or a designated country. For purposes of this contract, “critical infrastructure” means “a communication infrastructure system, cybersecurity system, electric grid, hazardous waste treatment system, or water treatment facility.” See Tex. Gov’t Code § 2274.0101(2) of SB 1226 (87th leg.). The company verifies and certifies that company will not grant direct or remote access to or control of critical infrastructure, except for product warranty and support purposes, to prohibited individuals, companies, or entities, including governmental entities, owned, controlled, or headquartered in China, Iran, North Korea, Russia, or a designated country, as determined by the Governor.
Anti-Money Laundering/International Trade Law Compliance No Covered Entity is a Sanctioned Person. No Covered Entity, either in its own right or through any third party, (i) has any of its assets in a Sanctioned Country or in the possession, custody or control of a Sanctioned Person in violation of any Anti-Terrorism Law; (ii) does business in or with, or derives any of its income from investments in or transactions with, any Sanctioned Country or Sanctioned Person in violation of any Anti-Terrorism Law; or (iii) engages in any dealings or transactions prohibited by any Anti-Terrorism Law.
Foreign Asset/Account, Exchange Control and Tax Reporting The Participant may be subject to foreign asset/account, exchange control and/or tax reporting requirements as a result of the acquisition, holding and/or transfer of shares of Common Stock or cash (including dividends and the proceeds arising from the sale of shares of Common Stock) derived from his or her participation in the Plan, to and/or from a brokerage/bank account or legal entity located outside the Participant’s country. The applicable laws of the Participant’s country may require that he or she report such accounts, assets, the balances therein, the value thereof and/or the transactions related thereto to the applicable authorities in such country. The Participant acknowledges that he or she is responsible for ensuring compliance with any applicable foreign asset/account, exchange control and tax reporting requirements and should consult his or her personal legal advisor on this matter.
Public Entity Crimes A person or affiliate who has been placed on the convicted vendor list following a conviction of a public entity crime may not be awarded or perform work as a contractor, supplier, subcontractor, or consultant under a contract with any public entity in excess of the threshold amount provided in Florida Statutes, Section 287.017 for Category Two for a period of thirty-six (36) months from the date of being placed on the convicted vendor list.
Certification Regarding Business with Certain Countries and Organizations Pursuant to Subchapter F, Chapter 2252, Texas Government Code, PROVIDER certifies it is not engaged in business with Iran, Sudan, or a foreign terrorist organization. PROVIDER acknowledges this Purchase Order may be terminated if this certification is or becomes inaccurate.
Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES
