Diversity Report The Contractor shall report to each Customer, spend with certified and other minority business enterprises. These reports shall include the period covered, the name, minority code and Federal Employer Identification Number of each minority business utilized during the period, Commodities provided by the minority business enterprise, and the amount paid to each minority business on behalf of each purchasing agency ordering under the terms of this Contract.
COPIES OF REGULATORY REPORTS AND FILINGS Upon reasonable request, Competitive Supplier shall provide to the Town a copy of each public periodic or incident-related report or record relating to this ESA which it files with any Massachusetts or federal agency regulating rates, service, compliance with environmental laws, or compliance with affirmative action and equal opportunity requirements, unless the Competitive Supplier is required by law or regulation to keep such reports confidential. The Town shall treat any reports and/or filings received from Competitive Supplier as confidential information subject to the terms of Article 16. Competitive Supplier shall be reimbursed its reasonable costs of providing such copies.
COMPTROLLER’S REPORT ON CHAPTER 313 AGREEMENTS During the term of this Agreement, both Parties shall provide the Comptroller with all information reasonably necessary for the Comptroller to assess performance under this Agreement for the purpose of issuing the Comptroller’s report, as required by Section 313.032 of the TEXAS TAX CODE.
Progress Report 10.1 If required, you shall submit progress reports in connection with the Service (“Report”) on at least a monthly basis, or as we may require. The Report shall include a summary of the activities and accomplishments during the previous reporting period.
GRIEVANCE REPORT FORM Grievance # School District Distribution of Form 1. Superintendent
Royalty Reports After the first commercial sale of a Licensed Product anywhere in the world, LICENSEE shall submit to UNIVERSITY quarterly royalty reports on or before each February 28, May 31, August 31 and November 30 of each year. Each royalty report shall cover LICENSEE’s (and each Affiliate’s and Sublicensee’s) most recently completed calendar quarter and shall show:
ASSESSMENT REPORT Within 120 days following the general election held on November 2nd 2003, the returning officer of the munici- pality shall forward, in accordance with section 659.3 of the Act respecting elections and referendums in munici- palities (R.S.Q., c. E-2.2), an assessment report to the Chief Electoral Officer and the Minister setting out relevant ways to improve the trial and addressing, in particular, the following points : — the preparations for the election (choice of the new method of voting, communications plan, etc.) ; — the conduct of the advance poll and the poll ; — the cost of using the electronic voting system : – the cost of adapting election procedures ; – non-recurrent costs likely to be amortized ; – a comparison between the actual polling costs and the estimated polling costs using the new methods of voting and the projected cost of holding the general election on November 2nd 2003 using traditional methods ; — the number and duration of incidents during which voting was stopped, if any ; — the advantages and disadvantages of using the new method of voting ; — the results obtained during the addition of the votes and the correspondence between the number of ballot paper cards issued to the deputy returning officers and the number of ballot paper cards returned used and unused ; — the examination of rejected ballot papers, if it has been completed.
Regulatory Reporting Ultimus agrees to provide reports to the federal and applicable state authorities, including the SEC, and to the Funds’ Auditors. Applicable state authorities are those governmental agencies located in states in which the Fund is registered to sell shares.
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
Daily Job Reports 6.7.2.1 Developer shall maintain, at a minimum, at least one (1) set of Daily Job Reports on the Project. These must be prepared by Xxxxxxxxx's employee(s) who are present on Site, and must include, at a minimum, the following information:
