Quarterly Summary of FEDLINK User Activity Sample Clauses

Quarterly Summary of FEDLINK User Activity. The vendor shall submit quarterly the agency name, point-of-contact (POC), and total dollars obligated for the services provided under this BOA. The vendor may use the sample FEDLINK Quarterly Summary Report Forms provided (see attachment J.2.) or develop a computerized report as long as it provides the information identified below. Reports shall be suitable for import into a Microsoft Excel spreadsheet and shall be sent via email to the Contracting Officer as listed in section G.1. To facilitate FEDLINK reporting of usage, reports shall provide the following information: • Agency name • Agency point-of-contact (POC) and telephone number • FEDLINK ID • Delivery order number • Delivery order Not-to-Exceed (NTE) Total • Fiscal year amounts received for each customer • Current quarterly dollars expended for each customer
AutoNDA by SimpleDocs

Related to Quarterly Summary of FEDLINK User Activity

  • Quarterly Sales Reports The Contractor shall submit a completed Quarterly Sales Report electronically, in the required format, to the Department’s Contract Manager within thirty (30) calendar days after close of each quarter. The quarterly sales report can be found here: xxxxx://xxx.xxx.xxxxxxxxx.xxx/business_operations/ state_purchasing/vendor_resources/quarterly_sales_report_format. The Contract Quarterly Sales Report will include all sales and orders associated with this Contract from Customers received during the reporting period. Initiation and submission of the Sales Report is the responsibility of the Contractor without prompting or notification from the DMS Contract Manager. Failure to provide the quarterly sales report will result in the imposition of financial consequences and may result in the Contractor being found in default and the termination of the Contract. Initiation and submission of the quarterly sales report are the responsibility of the Contractor without prompting or notification by the Department. Sales will be reviewed on a quarterly basis. If no sales are recorded during the period, the Contractor must submit a report stating that there was no activity. If no sales are recorded in two consecutive quarters, the Contractor may be placed in probationary status or the Department may terminate the Contract. Quarter 1 – (July-September) – due 30 calendar days after the close of the period Quarter 2 – (October-December) – due 30 calendar days after the close of the period Quarter 3 – (January-March) – due 30 calendar days after the close of the period Quarter 4 – (April-June) due 30 calendar days after the close of the period Exceptions may be made if a delay in submitting reports is attributable to circumstances that are clearly beyond the control of the Contractor. The burden of proof of unavoidable delay shall rest with the Contractor and shall be supplied in a written form and submitted to the Department. The Department reserves the right to request additional sales information as needed.

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

  • XXX Hosting 10.1 XXX Hosting is not required for resale in the BellSouth region.

  • ANNUAL MASTER CONTRACT SALES REPORT Contractor shall provide to Enterprise Services a detailed annual Master Contract sales report. Such report shall include, at a minimum: Product description, part number or other Product identifier, per unit quantities sold, and Master Contract price. This report must be provided in an electronic format that can be read by MS Excel.

  • Quarterly Progress Reports The goal of this task is to periodically verify that satisfactory and continued progress is made towards achieving the objectives of this Agreement on time and within budget. The objectives of this task are to summarize activities performed during the reporting period, to identify activities planned for the next reporting period, to identify issues that may affect performance and expenditures, and to form the basis for determining whether invoices are consistent with work performed. The Recipient shall: • Prepare a Quarterly Progress Report which summarizes all Agreement activities conducted by the Recipient for the reporting period, including an assessment of the ability to complete the Agreement within the current budget and any anticipated cost overruns. Progress reports are due to the CAM the 10th day of each January, April, July, and October. The Quarterly Progress Report template can be found on the ECAMS Resources webpage available at xxxxx://xxx.xxxxxx.xx.xxx/media/4691. Product: • Quarterly Progress Reports

  • Web Hosting If Customer submits a Service Order(s) for web hosting services, the following terms shall also apply:

  • Multiple Listing Service (MLS) Due to rules administered by the local Multiple Listing Service (“MLS”), all details of any transaction that are procured by the Agency may be used for publication in the MLS. Seller hereby consents to such publication on an unrestricted basis whereas the Agency must comply with all applicable MLS rules to allow data about the Property to be shown and made available by the MLS in addition to other internet websites. MLS rules generally provide that any property entered into its database be updated within forty-eight (48) hours, or some other period of time, after all necessary signatures have been obtained in regard to the Property. Seller has the right to prohibit any and all publication of information in regard to a transfer of the Property. In order to exercise this right, the Seller is required to authorize a separate addendum provided by the Agency and attach to this Agreement.

  • SCOPE OF SERVICES/CASE HANDLING A. Upon execution by Xxxxxx, Attorneys are retained to provide legal services for the purpose of seeking damages and other relief in the Litigation. Client agrees that Xxxxxx may choose to associate additional law firm(s) and/or lawyer(s) to represent Client in connection with the investigation and prosecution of the rights Client has as a purchaser of publically traded securities of Xxxxxx, and Client understands that such representation shall be on the same terms as those described in this agreement.

  • Contract Quarterly Sales Reports The Contractor shall submit complete Quarterly Sales Reports to the Department’s Contract Manager within 30 calendar days after the close of each State fiscal quarter (the State’s fiscal quarters close on September 30, December 31, March 31, and June 30). Reports must be submitted in MS Excel using the DMS Quarterly Sales Report Format, which can be accessed at xxxxx://xxx.xxx.xxxxxxxxx.xxx/business_operations/ state_purchasing/vendor_resources/quarterly_sales_report_format. Initiation and submission of the most recent version of the Quarterly Sales Report posted on the DMS website is the responsibility of the Contractor without prompting or notification from the Department’s Contract Manager. If no orders are received during the quarter, the Contractor must email the DMS Contract Manager confirming there was no activity.

  • 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

Time is Money Join Law Insider Premium to draft better contracts faster.