Financial and Economic Function
Financial and Economic Function Sample Clauses
Related to Financial and Economic Function
Trade and Economic Mixed Commission 1. The Parties hereby incorporate the Trade and Economic Mixed Commission (Mixed Commission) into this Agreement. 2. The Mixed Commission was established according to the Basic Agreement on Economic and Technical Cooperation between the Government of the People's Republic of China and the Government of the Republic of Peru, signed in Lima, on November 2nd, 1988. 3. The Mixed Commission is composed of officials as follows: (a) for China, the high ranking official of
PERFORMANCE MONITORING AND REPORTING Performance indicators
Safeguards Monitoring and Reporting 8. The Borrower shall do the following or cause the Project Executing Agency to do the following:
Monitoring and Reporting 3.1 The Contractor shall provide workforce monitoring data as detailed in paragraph 3.2 of this Schedule 8. A template for data collected in paragraphs 3.2, 3.3 and 3.4 will be provided by the Authority. Completed templates for the Contractor and each Sub-contractor will be submitted by the Contractor with the Diversity and Equality Delivery Plan within six (6) Months of the Commencement Date and annually thereafter. Contractors are required to provide workforce monitoring data for the workforce involved in delivery of the Contract. Data relating to the wider Contractor workforce and wider Sub-contractors workforce would however be well received by the Authority. Contractors and any Sub-contractors are required to submit percentage figures only in response to paragraphs 3.2(a), 3.2(b) and 3.2(c).
GOVERNANCE AND REPORTING Measure 3a Is the school complying with governance requirements? Meets Standard: The school materially complies with applicable laws, rules, regulations and provisions of the charter contract relating to governance by its board, including but not limited to: • Governing board composition and membership requirements pursuant to Ch. 302D, HRS • Governing board policies • Governing board reporting requirements • Procurement policies • State Ethics Code (Ch. 84, HRS), including conflict of interest policy Measure 3b Is the school holding management accountable? Meets Standard: The school materially complies with applicable laws, rules, regulations and provisions of the charter contract relating to oversight of school management, including but not limited to: • (For Education Service Providers [ESPs]) maintaining authority over management, holding it accountable for performance as agreed under a written performance agreement and requiring annual financial reports of the ESP • (For Others) oversight of management that includes holding it accountable for performance expectations that may or may not be agreed to under a written performance agreement Measure 3c Is the school complying with data and reporting requirements? Meets Standard: The school materially complies with applicable laws, rules, regulations and provisions of the charter contract relating to relevant reporting requirements to the State Public Charter School Commission, State Department of Education as the State Education Agency (SEA) and sole Local Education Agency (LEA) and/or federal authorities, including but not limited to: • Compliance with minimum educational data reporting standards established by the BOE • Maintaining and reporting accurate enrollment and attendance data • Maintaining and reporting accurate personnel data • Annual reporting and immediate notice requirements • Additional information requested by the State Public Charter School Commission
Record Keeping and Reporting 15.01 The Accredited Entity shall ensure that:
MANAGEMENT FUNCTIONS B-1 The Association recognizes that the management of the Hospital and the direction of the working forces are fixed exclusively in the Hospital and shall remain solely with the Hospital except as specifically limited by the provisions of this Agreement, and without restricting the generality of the foregoing, the Association acknowledges that it is the exclusive function of the Hospital to:
FINANCIAL AID I understand that aid described as “estimated” on my Financial Aid Award does not represent actual or guaranteed payment, but is an estimate of the aid I may receive if I meet all requirements stipulated by the relevant aid program. If my eligibility for financial aid changes for any reason, I understand that I will be responsible for any charges on my account that were previously covered by financial aid and that I will be responsible for repaying to the lender any credit balances that were refunded to me. I understand and agree that the federal financial aid I receive will be applied by the University for the payment of mandatory fees, and fees for tuition and room and board, which I owe the University. I further understand that if I want the University to apply my federal financial aid to other charges which appear on my fee xxxx during the academic year, I must complete a Title IV Financial Aid Authorization, which is available on the student administration system website, under the heading of “Student Help,” or by following this link: xxxxxxxxxxxx.xxxxx.xxx/xxxx/xxxxxxxx/xxxxxx-xxxxx-xx-xxxxxxxxx-xxx-xxxxxx/ I understand that all prizes, awards, scholarships and grants awarded to me by the University will be credited to my student account and applied toward any outstanding balance owed the University. I further understand that my receipt of a prize, award, scholarship or grant is considered a financial resource under federal Title IV financial aid regulations, and may therefore reduce my eligibility for other federal and/or state financial aid (i.e., loans, grants, Federal Work Study) which, if already disbursed to my student account, may have to be reversed and returned to the aid source. I understand that amounts I will owe for the repayment of my student loans may not be dischargeable in bankruptcy.
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: Field # Field Name Description 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
Information Management Information and Records
