Non Trading Operations Regulations
Non Trading Operations Regulations Sample Clauses
Related to Non Trading Operations Regulations
Terrorism Sanctions Regulations The Company will not and will not permit any Subsidiary to (a) become a Person described or designated in the Specially Designated Nationals and Blocked Persons List of the Office of Foreign Assets Control or in Section 1 of the Anti-Terrorism Order or (b) engage in any dealings or transactions with any such Person.
Currency and Foreign Transactions Reporting Act The operations of the Company are and have been conducted at all times in compliance with (i) the requirements of the U.S. Treasury Department Office of Foreign Asset Control and (ii) applicable financial recordkeeping and reporting requirements of the Currency and Foreign Transaction Reporting Act of 1970, as amended, including the Money Laundering Control Act of 1986, as amended, the rules and regulations thereunder and any related or similar money laundering statutes, rules, regulations or guidelines, issued, administered or enforced by any Federal governmental agency (collectively, the “Money Laundering Laws”) and no action, suit or proceeding by or before any court or governmental agency, authority or body or any arbitrator involving the Company with respect to the Money Laundering Laws is pending or, to the Company’s knowledge, assuming reasonable inquiry, threatened.
Procurement Regulations The contract shall be governed by the applicable provisions of the Mississippi Public Procurement Review Board Office of Personal Service Contract Review Rules and Regulations, a copy of which is available at 000 Xxxxx Xxxx Xxxxxx, Xxxxx 000X, Xxxxxxx, Xxxxxxxxxxx 00000 for inspection, or downloadable at xxxx://xxx.XXX.xx.xxx.
Operating Rules 6.1 Merchant must comply with the Operating Rules, as the same may be amended from time to time. The Operating Rules may change with little or no advance notice to Merchant and Merchant will be bound by all such changes. If Merchant objects to any change in the Operating Rules, it must immediately stop accepting new Transactions for Cards governed by the change. The Operating Rules will govern in the event that there is any inconsistency between the Merchant Agreement and the Operating Rules. However, nothing in the Merchant Agreement shall be construed to impose on Merchant a requirement (including a requirement under the Operating Rules) which is prohibited by mandatory provisions of applicable law (i.e., where the applicability of such provisions of law to the Merchant Agreement, and of the law’s prohibition to the particular requirement which otherwise would be imposed on Merchant hereunder, cannot lawfully be waived by agreement), but the requirement hereunder shall be construed to continue in effect and to be imposed on Merchant in all respects and at all times to the fullest extent possible without violating the law’s prohibition, with only those particular applications of the requirement which would violate the law’s prohibition deemed severed from the provisions hereof. 6.2 Operating Rules of the Debit Networks may differ among them with respect to the Transactions they allow. Bank, at its discretion, may require that the most restrictive requirements of one Debit Network apply to all of Merchant’s On-line Debit Card Transactions, regardless of Card type.
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
Enterprise Information Management Standards Performing Agency shall conform to HHS standards for data management as described by the policies of the HHS Chief Data and Analytics Officer. 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.
Public Procurement The Parties shall cooperate to develop conditions for open and competitive award of contracts for goods and services in particular through calls for tenders.
Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.
Developer Operating Requirements The Developer must comply with the Transmission Owner’s operating instructions and requirements including but not limited to Transmission Owner’s Operation Coordination Agreement, as it may change from time to time. The Developer must comply with all applicable NYISO tariffs and procedures, as amended from time to time. Whether or not the Large Generating Facility is eligible for the Transition Period LVRT Standard set forth in Appendix G will be determined by the Commission. The Large Generating Facility will comply with the Transition Period LVRT Standard pending issuance of an order by the Commission determining the appropriate LVRT standard. For purposes of compliance with Appendix G, the Transmission Owner has determined that the Developer shall maintain the Large Generating Facility in service during a three-phase fault for 7 cycles. Infrastructure security of New York State Transmission System equipment and operations and control hardware and software is essential to ensure day-to-day New York State Transmission System reliability and operational security. The Commission will expect the NYISO, all Transmission Owners, all Developers and all other Market Participants to comply with the recommendations offered by the President’s Critical Infrastructure Protection Board and, eventually, best practice recommendations from the electric reliability authority. All public utilities will be expected to meet basic standards for system infrastructure and operational security, including physical, operational, and cyber-security practices. All personnel working in Transmission Owner’s facilities will require security background checks prior to entering and working in such facilities. New York Independent System Operator, Inc. Attn: Vice President, Operations 0000 Xxxxxx Xxxx Schenectady, NY 12303 Senior Vice President of Transmission New York Power Authority 000 Xxxx Xx. Xxxxx Xxxxxx, XX 00000-0000 Re: Large Generating Facility Dear : On [Date] [Developer] has completed Trial Operation of Unit No. . This letter confirms that [Developer] commenced Commercial Operation of Unit No. at the Large Generating Facility, effective as of [Date plus one day]. Thank you. NYISO:
Procurement Standards For projects being managed by the Local Government and on the State highway system or that include state funding, the Local Government must obtain approval from the State for its proposed procurement procedure for the selection of a professional services provider, a contractor for a construction or maintenance project, or a materials provider.
