Description of Criteria & Function Sample Clauses

Description of Criteria & Function. An additional purpose of this Coordination Agreement is to describe the criteria for establishing the responsibilities of each Party for meeting the terms of this Coordination Agreement, the procedure for the exchange of information between the Parties, and procedures for resolving conflicts between the Parties. The goal of the coordination is to ensure that the Subbasin GSPs utilize the same data and methodologies, including but not limited to, groundwater elevation data, groundwater extraction data, surface water supply, total water use, changes in groundwater storage, water budgets, and sustainable yield during their development as required by SGMA and associated regulations. Additionally, this Coordination Agreement sets out the process for identifying a Plan Manager.
AutoNDA by SimpleDocs

Related to Description of Criteria & Function

  • Anti-Money Laundering and Identity Theft Prevention Related Duties Subject to the terms and conditions set forth herein, the Trust hereby delegates to the Transfer Agent the Delegated Anti-Money Laundering Duties and, where applicable, the Delegated Identity Theft Prevention Duties that are set forth in the Trust’s Anti-Money Laundering (“AML”) Program and Identity Theft Prevention Program (“IDTPP”) as described below. The Transfer Agent agrees to perform the Delegated Anti-Money Laundering Duties and the Delegated Identity Theft Prevention Duties, with respect to ownership of shares in the Fund for which the Transfer Agent maintains the applicable information subject to and in accordance with the terms and conditions of the Contract.

  • Anti-Money Laundering and Red Flag Identity Theft Prevention Programs The Trust acknowledges that it has had an opportunity to review, consider and comment upon the written procedures provided by USBFS describing various tools used by USBFS which are designed to promote the detection and reporting of potential money laundering activity and identity theft by monitoring certain aspects of shareholder activity as well as written procedures for verifying a customer’s identity (collectively, the “Procedures”). Further, the Trust and USBFS have each determined that the Procedures, as part of the Trust’s overall Anti-Money Laundering Program and Red Flag Identity Theft Prevention Program, are reasonably designed to: (i) prevent each Fund from being used for money laundering or the financing of terrorist activities; (ii) prevent identity theft; and (iii) achieve compliance with the applicable provisions of the Bank Secrecy Act, Fair and Accurate Credit Transactions Act of 2003 and the USA Patriot Act of 2001 and the implementing regulations thereunder. Based on this determination, the Trust hereby instructs and directs USBFS to implement the Procedures on the Trust’s behalf, as such may be amended or revised from time to time. It is contemplated that these Procedures will be amended from time to time by the parties as additional regulations are adopted and/or regulatory guidance is provided relating to the Trust’s anti-money laundering and identity theft responsibilities. USBFS agrees to provide to the Trust: (a) Prompt written notification of any transaction or combination of transactions that USBFS believes, based on the Procedures, evidence money laundering or identity theft activities in connection with the Trust or any Fund shareholder; (b) Prompt written notification of any customer(s) that USBFS reasonably believes, based upon the Procedures, to be engaged in money laundering or identity theft activities, provided that the Trust agrees not to communicate this information to the customer; (c) Any reports received by USBFS from any government agency or applicable industry self-regulatory organization pertaining to USBFS’ Anti-Money Laundering Program or the Red Flag Identity Theft Prevention Program on behalf of the Trust; (d) Prompt written notification of any action taken in response to anti-money laundering violations or identity theft activity as described in (a), (b) or (c) immediately above; and (e) Certified annual and quarterly reports of its monitoring and customer identification activities pursuant to the Procedures on behalf of the Trust. The Trust hereby directs, and USBFS acknowledges, that USBFS shall (i) permit federal regulators access to such information and records maintained by USBFS and relating to USBFS’ implementation of the Procedures, on behalf of the Trust, as they may request, and (ii) permit such federal regulators to inspect USBFS’ implementation of the Procedures on behalf of the Trust.

  • Vendor Certification of Criminal History Texas Education Code Chapter 22 8 Texas Education Code Chapter 22 requires entities that contract with school districts to provide services to obtain DEFINITIONS Covered employees: Employees of a contractor or subcontractor who have or will have continuing duties related to the service to be performed at the District and have or will have direct contact with students. The District will be the final arbiter of what constitutes direct contact with students. Disqualifying criminal history: Any conviction or other criminal history information designated by the District, or one of the following offenses, if at the time of the offense, the victim was under 18 or enrolled in a public school: (a) a felony offense under Title 5, Texas Penal Code; (b) an offense for which a defendant is required to register as a sex offender under Chapter 62, Texas Code of Criminal Procedure; or (c) an equivalent offense under federal law or the laws of another state. Vendor certifies: NONE (Section A): None of the employees of Vendor and any subcontractors are covered employees, as defined above. If this box is checked, I further certify that Contractor has taken precautions or imposed conditions to ensure that the employees of Vendor and any subcontractor will not become covered employees. Contractor will maintain these precautions or conditions throughout the time the contracted services are provided under this procurement. SOME (Section B): Some or all of the employees of Vendor and any subcontractor are covered employees. If this box is checked, I further certify that: (1) Vendor has obtained all required criminal history record information regarding its covered employees. None of the covered employees has a disqualifying criminal history; (2) If Vendor receives information that a covered employee subsequently has a reported criminal history, Vendor will immediately remove the covered employee from contract duties and notify the purchasing entity in writing within 3 business days; (3) Upon request, Vendor will provide the purchasing entity with the name and any other requested information of covered employees so that the purchasing entity may obtain criminal history record information on the covered employees; (4) If the purchasing entity objects to the assignment of a covered employee on the basis of the covered employee's criminal history record information, Xxxxxx agrees to discontinue using that covered employee to provide services at the purchasing entity. Certification Regarding "Choice of Law" Terms with TIPS Members Certification Regarding "Venue" Terms with TIPS Members Certification Regarding "Automatic Renewal" Terms with TIPS Members Certification Regarding "Indemnity" Terms with TIPS Members Certification Regarding "Arbitration" Terms with TIPS Members

  • General Criteria (a) If general criteria are required as part of the Application, only one (1) set shall be completed. General criteria measure the quality of the Land Manager’s overall OHV program. The Applicants shall answer these questions with respect to the entirety of the OHV operation, including all trails and areas available for OHV Recreation, not just specific Projects or Project Areas. (b) General criteria include, but are not limited to, the following: (1) OHV Opportunity and services provided, (2) Agency contribution to the overall cost of managing and delivering the OHV Opportunity, (3) Management of natural and Cultural Resources, (4) Effective education of rules/regulations, and (5) Past performance in completing and administering Xxxxx funded Projects. (c) Non-land manager Applicants required to complete the general criteria shall cooperate with the Land Manager(s) to obtain the information necessary to complete the general criteria section of the Application. Note: Authority cited: Sections 5001.5 and 5003, Public Resources Code. Reference: Sections 5024.1, 5090.32 and 5090.50, Public Resources Code.

  • 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

  • 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.

  • PUBLIC ENTITY CRIME Section 287.133(3)(d), Florida Statutes, provides that the Florida Department of Management Services shall maintain a list of the names and addresses of those who have been disqualified from participating in the public contracting process under this section. xxxx://xxx.xxx.xxxxxxxxx.xxx/business_operations/state_purchasing/vendor_infor xxxxxx/convicted_suspended_discriminatory_complaints_vendor_lists/convicted_ve ndor_list A person or affiliate who has been placed on The Convicted Vendor list following a conviction for a public entity crime shall not submit a bid on a contract with a public entity for the construction or repair of a public building or public work, shall not submit bids on leases of real property to a public entity, shall not be awarded or perform work as a contractor, supplier, subcontractor, or consultant under a contract with a public entity, and shall not transact business with any public entity in excess of the threshold amount provided in Florida Statute 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.

  • Governance and Anticorruption The Borrower, the Project Executing Agency, and the implementing agencies shall (a) comply with ADB’s Anticorruption Policy (1998, as amended to date) and acknowledge that ADB reserves the right to investigate directly, or through its agents, any alleged corrupt, fraudulent, collusive or coercive practice relating to the Project; and

  • Additional Functions Upon receipt of Proper Instructions, the Custodian shall take all such other actions as specified in such Proper Instructions and as shall be reasonable or necessary with respect to Repurchase Agreement transactions and the Securities and funds transferred and received pursuant to such transactions, including, without limitation, all such actions as shall be prescribed in the event of a default under a Repurchase Agreement.

  • Sanctions for Noncompliance In the event of a contractor’s noncompliance with the Non- discrimination provisions of this contract, the sponsor will impose such contract sanctions as it or the Federal Aviation Administration may determine to be appropriate, including, but not limited to: a. Withholding payments to the contractor under the contract until the contractor complies; and/or b. Cancelling, terminating, or suspending a contract, in whole or in part.

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