Capacity Report Sample Clauses

Capacity Report. 1. CDDOs agree to report capacity using a mutually agreed upon template. The CDDO and KDADS will convene to develop or utilize previously mutually agreed upon key indicators for evaluating IDD System capacity. 2. The report shall be due annually on March 31st. 3. The Parties agree to cooperate in a proactive manner as needed to address systemic gaps.
Sample 1Sample 2
AutoNDA by SimpleDocs
Capacity Report. Supplier shall define manufacturing capacity for each Buyer unique step in the manufacturing process and total manufacturing capacity for each Product and/or family of Products. Supplier will also provide component supplier supply capacity information (collectively "Capacity Information") for unique, custom parts as mutually agreed. Capacity Information along with up-to-date information on Supplier manufacturing capacity model and cycle time plan will be provided to Buyer on the first day of each month in a monthly report or as requested by Buyer. Component supplier capacity information will be provided on an as-needed basis.
Sample 1Sample 2
Capacity Report. Borrower to supply to Agent a quarterly capacity report evidencing a list of users, in terms of DS3s leased the corresponding bxxxxxxx and the fact that a minimum level of 5 DS3s is being maintained after the end of the first third quarter of 2010.
Sample 1
Capacity Report. MiTAC shall define manufacturing capacity for each Hypercom unique step in the manufacturing process and total manufacturing capacity for each Finished Product and/or Finished Product Family. Capacity Information along with up-to-date information on MiTAC's manufacturing capacity model and cycle time plan will be provided to Hypercom [****]. Component vendor capacity information will be provided on an as-needed basis. In the Contemplated Amendment to this Agreement, MiTAC will use its best efforts to propose an approach by which each Component vendor will supply capacity information for Unique Component. [****] Confidential Treatment Requested
Sample 1

Related to Capacity Report

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

  • CMI/RAI MDS Report Recognizing the mutual objective of quality resident care, the Employer agrees to meet through the Union Management Committee with the Union as soon as practicable after the receipt of the annual CMI/RAI MDS report. The Employer agrees to provide the Union with staffing levels, and staffing mix information; the impact of related payroll costs on staffing levels and a written notice of the CMI/RAI MDS report for the facility. The purpose of this meeting is to discuss the impact of the CMI/RAI MDS report on the staffing levels in the Home, quality resident care, and provide the Union with an opportunity to make representation in that regard. The parties shall meet as necessary to discuss other changes or workload issues. The parties may invite additional participants to attend the meeting to support constructive review and discussion.

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

  • 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

  • Diversity Reporting Upon request, the Contractor will report to the Department its spend with business enterprises certified by the OSD. These reports must include the time period covered, the name and Federal Employer Identification Number of each business enterprise utilized during the period, commodities and contractual services provided by the business enterprise, and the amount paid to the business enterprise on behalf of each agency purchasing under the Contract.

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

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

  • System Security Review All systems processing and/or storing County PHI or PI must have at least an annual system risk assessment/security review which provides assurance that administrative, physical, and technical controls are functioning effectively and providing adequate levels of protection. Reviews should include vulnerability scanning tools.

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

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

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