Regular Activity Statements Sample Clauses

Regular Activity Statements. You will receive a monthly statement detailing the support activity for the period. Regular reviews can be scheduled at your request to ensure that all parties are completely satisfied with the level of support and the direction of the relationship Future and your organisation have developed. Next Level Support - Managed Support Agreement (MSA) Future Computers also has a next level service level agreement above the standard Customer Support Agreement (CSA) listed above. For the Managed Support Agreement (MSA) the cost is the same per hour but you are agreeing to a minimum visit/login per month to carry out preventive maintenance. The time required will depend on the complexity of your network and will be decided upon acceptance of this agreement. In accepting the MSA we then provide a host of extra services to capture system data on your network and automatically alert us to any issues that might be present. Preventative Maintenance Tasks Onsite or remote tasks:  Inspection App task list and provided client report (new Q2 this year)  Check and action server event logs  Check Backups and Verify data restore  Check integrity of hard drive and free space  Check UPS connectivity and perform self-test  Check Anti-Virus logs and carry out required updates on server(s)  Check servers operating system has latest critical/security updates and service packs as necessary  Check server power supply fans and airflow These tasks are carried out every maintenance visit without fail to ensure the integrity of the network and prevent any possible issues. MSA Inclusions The benefits of being a MSA customer is the below which do not form any extra charges to you but we include them for ease of management of your network:  Dedicated sales account manager – To action any renewals and new quotes for your network  Service help desk – For first touch/fix calls  Service level agreements as outlined in the MSA contract. Priority service for on demand calls above those on queue based On Demand clients  Remote system monitoring software and incident alerting (loaded on your servers and lets us know if there is any issues between visits)  TNI - System auditing software (loaded on your servers to identify what assets are connected to your network – desktops, laptops, printers etc etc)  TeamViewer - Remote assistance software (loaded on your servers and used on your desktops for easy access to assist users in remote on demand calls) 24*7 System Monitoring/Alerting softwar...
AutoNDA by SimpleDocs

Related to Regular Activity Statements

  • Regular Reports Grantee shall provide, in a prompt and timely manner, financial, operational and other reports, as requested by the Department, in form and substance satisfactory to the Department. Such reports, including any copies, shall be submitted on recycled paper and printed on double-sided pages, to the maximum extent possible.

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

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

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

  • Monthly Status Reports 19.1.1 During the Operation Period, the Concessionaire shall, no later than 7 (seven) days after the close of each month, furnish to the Authority and the Independent Engineer a monthly report stating in reasonable detail the condition of the Project including its compliance or otherwise with the Maintenance Requirements, Maintenance Manual, Maintenance Program and Safety Requirements, and shall promptly give such other relevant information as may be required by the Independent Engineer or the Authority. In particular, such report shall separately identify and state in reasonable detail the defects and deficiencies that require rectification.

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

  • Monthly Progress Reports During the Construction Period, the Concessionaire shall, no later than 7 (seven) days after the close of each month, furnish to the Authority and the Independent Engineer a monthly report on progress of the Construction Works and shall promptly give such other relevant information as may be required by the Independent Engineer.

  • Monthly Statements Each month we will send you a statement showing purchases, cash advances, payments, and credits made to your Account during the billing cycle, as well as your “New Balance”, any Finance Charge and any late charges. Your statement also will identify the minimum monthly payment you must make for that billing period and the date it is due. You agree to retain for statement verification copies of transaction slips resulting from each purchase, each advance, and other transactions on your Account. Unless you notify us of a billing error in accordance with the section entitled “Your Billing Rights”, you accept your monthly statement as an accurate statement of your Account with us.

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

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