CONTRACT SALES ACTIVITY REPORT Each calendar quarter, Vendor must provide a contract sales activity report (Report) to the Sourcewell Contract Administrator assigned to this Contract. A Report must be provided regardless of the number or amount of sales during that quarter (i.e., if there are no sales, Vendor must submit a report indicating no sales were made). The Report must contain the following fields: • Customer Name (e.g., City of Staples Highway Department); • Customer Physical Street Address; • Customer City; • Customer State/Province; • Customer Zip Code; • Customer Contact Name; • Customer Contact Email Address; • Customer Contact Telephone Number; • Sourcewell Assigned Entity/Participating Entity Number; • Item Purchased Description; • Item Purchased Price; • Sourcewell Administrative Fee Applied; and • Date Purchase was invoiced/sale was recognized as revenue by Vendor.
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.
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
Progress Report By March 1 of each year, ***** will submit a written annual report to Stanford covering the preceding calendar year. The report will include information sufficient to enable Stanford to satisfy reporting requirements of the U.S. Government and for Stanford to ascertain progress by ***** toward meeting this Agreement’s diligence requirements. Each report will describe, where relevant: *****’s progress toward commercialization of Licensed Product, including work completed, key scientific discoveries, summary of work-in-progress, current schedule of anticipated events or milestones, market plans for introduction of Licensed Product, and significant corporate transactions involving Licensed Product. ***** will specifically describe how each Licensed Product is related to each Licensed Patent.
Monthly Report A. A Monthly Report shall be submitted within ten (10) calendar days of the end of each calendar month of the Period of Operation. Each Monthly Report shall be signed, dated, and certified by Concessionaire, Concessionaire’s Bookkeeper, or Accountant, and contain a Statement of Total Gross Receipts, excluding New Jersey State Sales Tax, derived by Concessionaire from operation of the Concession during the previous month. Each Monthly Report shall be based on the daily “Z” tapes or Point-of-Service (POS) device equivalent for that same month showing each day’s sales activity. Failure on the part of Concessionaire to provide the Monthly Report, when due, shall constitute a material breach of this Agreement subject to Suspension of Operations and/or Termination, in accordance with the terms and conditions set forth in Paragraphs 9 and 10. Concessionaire shall provide Department with any additional written clarification and/or information necessary to confirm the accuracy of any or all of Concessionaire’s Monthly Reports.
B. The signed, dated and certified Monthly Report must be submitted, in the Department- approved format, within ten (10) calendar days of the end of each calendar month of the Period of Operation.
Management Report Promptly upon receipt thereof, copies of all detailed financial and management reports submitted to Borrower or any other Loan Party by independent auditors in connection with each annual or interim audit made by such auditors of the books of Borrower or any other Loan Party.
SUBMISSION OF THE MONTHLY MI REPORT 4.1 The completed MI Report shall be completed electronically and returned to the Authority by uploading the electronic MI Report computer file to MISO in accordance with the instructions provided in MISO.
4.2 The Authority reserves the right (acting reasonably) to specify that the MI Report be submitted by the Supplier using an alternative communication to that specified in paragraph 4.1 above such as email. The Supplier agrees to comply with any such instructions provided they do not materially increase the burden on the Supplier.
Compliance Statement Within thirty (30) days after the last day of each month and together with the statements set forth in Section 5.3(c), a duly completed Compliance Statement, confirming that as of the end of such month, Borrower was in full compliance with all of the terms and conditions of this Agreement, and setting forth calculations showing compliance with the financial covenants set forth in this Agreement and such other information as Bank may reasonably request;
Weekly Reports The Administrator must, on a weekly basis, provide written reports to Class Counsel and Defense Counsel that, among other things, tally the number of: Class Notices mailed or re-mailed, Class Notices returned undelivered, Requests for Exclusion (whether valid or invalid) received, objections received, challenges to Workweeks and/or Pay Periods received and/or resolved, and checks mailed for Individual Class Payments and Individual PAGA Payments (“Weekly Report”). The Weekly Reports must include provide the Administrator’s assessment of the validity of Requests for Exclusion and attach copies of all Requests for Exclusion and objections received.
Monthly Reporting Within twenty (20) calendar days following the end of each calendar month, Registry Operator shall deliver to ICANN reports in the format set forth in Specification 3 attached hereto (“Specification 3”).
