Activity Statement Sample Clauses

Activity Statement. When on an INSYGHT project, INSYGHT requires you to record and use the daily activity statement found in Zoho and must be submit this to INSYGHT weekly. The activity statement must record all issues, risks and activity. A failure to record or submit more than 2 activity statements per quarter is deemed a material breach of the agreement between INSYGHT and You.
AutoNDA by SimpleDocs

Related to Activity Statement

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

  • Daily Statement On each Banking Day on which any Participating Funds have an outstanding repurchase transaction, Repo Custodian shall deliver by facsimile to Custodian and to the Participating Funds a statement identifying the Securities held by Repo Custodian with respect to such repurchase transaction and the cash and Cash Collateral, if any, held by Repo Custodian in the Transaction Account, including a statement of the then current Market Value of such Securities and the amounts, if any, credited to the Transaction Account as of the close of trading on the previous Banking Day. Repo Custodian shall also deliver to Custodian and the Participating Funds such additional statements as the Participating Funds may reasonably request.

  • Privacy Statement The Parties agree to keep all information related to the signing and fulfillment of this Agreement confidential, and not to disclose it to any third parties, except for subcontractors involved in this agreement, unless prior written consent is obtained from the other Party. Should subcontractors be engaged under this agreement, they are required to adhere to its terms and conditions.

  • Monthly Statement The Contractor shall submit a statement to the Engineer at the end of each month, in a tabulated form approved by the Engineer, showing the amounts to which the Contractor considers himself to be entitled. The statement shall include the following items, as applicable; - the value of the Permanent Work executed up to the end of previous month - such an amount (not exceeding 75 percent of the value) as the Engineer may consider proper on account of materials for permanent work delivered by the Contractor in the site - such amount as the Engineer may consider fair and reasonable for any Temporary Works for which separate amounts are provided in the Bill of Quantities - adjustments under Clause 70 - any amount to be withheld under retention provisions of Sub-clause 60.3 - any other sum to which the Contractor may be entitled under the Contract If the Engineer disagrees with or cannot verify any part of the statement, the Contractor shall submit such further information as the Engineer may reasonably require and shall make such changes and corrections in the statement as may be directed by the Engineer. In cases where there is difference in opinion as to the value of any item, the Engineer’s view shall prevail.

  • 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

  • REPORT ON CONTRACT SALES ACTIVITY AND ADMINISTRATIVE FEE PAYMENT A. CONTRACT SALES ACTIVITY REPORT. Each calendar quarter, Supplier must provide a contract sales activity report (Report) to the Sourcewell Supplier Development Administrator assigned to this Contract. Reports are due no later than 45 days after the end of each calendar quarter. A Report must be provided regardless of the number or amount of sales during that quarter (i.e., if there are no sales, Supplier must submit a report indicating no sales were made). The Report must contain the following fields: • Participating Entity Name (e.g., City of Staples Highway Department); • Participating Entity Physical Street Address; • Participating Entity City; • Participating Entity State/Province; • Participating Entity Zip/Postal Code; • Participating Entity Contact Name; • Participating Entity Contact Email Address; • Participating Entity 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 Supplier. B. ADMINISTRATIVE FEE. In consideration for the support and services provided by Sourcewell, the Supplier will pay an administrative fee to Sourcewell on all Equipment, Products, and Services provided to Participating Entities. The Administrative Fee must be included in, and not added to, the pricing. Supplier may not charge Participating Entities more than the contracted price to offset the Administrative Fee. The Supplier will submit payment to Sourcewell for the percentage of administrative fee stated in the Proposal multiplied by the total sales of all Equipment, Products, and Services purchased by Participating Entities under this Contract during each calendar quarter. Payments should note the Supplier’s name and Sourcewell-assigned contract number in the memo; and must be mailed to the address above “Attn: Accounts Receivable” or remitted electronically to Sourcewell’s banking institution per Sourcewell’s Finance department instructions. Payments must be received no later than 45 calendar days after the end of each calendar quarter. Supplier agrees to cooperate with Sourcewell in auditing transactions under this Contract to ensure that the administrative fee is paid on all items purchased under this Contract. In the event the Supplier is delinquent in any undisputed administrative fees, Sourcewell reserves the right to cancel this Contract and reject any proposal submitted by the Supplier in any subsequent solicitation. In the event this Contract is cancelled by either party prior to the Contract’s expiration date, the administrative fee payment will be due no more than 30 days from the cancellation date.

  • Problem Statement School bus fleets are aging, and our communities have poor air quality. Replacing school buses with zero emission school buses will address both of these issues.

  • eXtensible Business Reporting Language The interactive data in eXtensible Business Reporting Language included or incorporated by reference in the Registration Statement fairly presents the information called for in all material respects and has been prepared in accordance with the Commission’s rules and guidelines applicable thereto.

  • Direct Sales The Manager will advise you promptly, on the Offering Date, as to the Securities purchased by you pursuant to the Underwriting Agreement that you will retain for direct sale. At any time prior to the termination of the applicable AAU, any such Securities that are held by the Manager for sale but not sold may, on your request and at the Manager’s discretion, be released to you for direct sale, and Securities so released to you will no longer be deemed held for sale by the Manager. You may allow, and Dealers may reallow, a discount on sales to Dealers in an amount not in excess of the Reallowance set forth in the applicable AAU. You may not purchase Securities from, or sell Securities to, any other Underwriter or Dealer at any discount or concession other than the Reallowance, except with the prior consent of the Manager.

  • Billing Information 6.1 NLT and the RL shall provide each other with information within their possession that is necessary to allow them to provide accurate and timely billing to each other and to any other relevant third parties.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!