Data Collection and Reporting 1. Grantee shall develop and use a local reporting unit that will provide an assigned location for all clients served within the Hospital. This information shall also be entered into Client Assignment and Registration (CARE)when reporting on beds utilized at the Hospital.
Data Collection Some downloaded software included in the Materials may generate and collect information about the software and usage and transmit it to Intel to help improve Intel’s products and services. This collected information may include product name, product version, time of event collection, license type, support type, installation status, hardware and software performance, and use. 9.
Billing and Collection The Originating party shall xxxx and collect such information service charges and shall remit the amounts collected to the Terminating Party less:
Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Comm South’s data from BellSouth’s data, the following shall apply:
Name Collision Report Handling 6.3.1 During the first two years after delegation of the TLD, Registry Operator’s emergency operations department shall be available to receive reports, relayed by ICANN, alleging demonstrably severe harm from collisions with overlapping use of the names outside of the authoritative DNS.
Collection Services 5.01 General 5-1 5.02 Solid Waste Collection 5-1 5.03 Targeted Recyclable Materials Collection 5-3
Approved Services; Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at xxxx://xxx.xxxxx.xxx/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.
Routing for Operator Services and Directory Assistance Traffic For a Verizon Telecommunications Service dial tone line purchased by MLTC for resale pursuant to the Resale Attachment, upon request by MLTC, Verizon will establish an arrangement that will permit MLTC to route the MLTC Customer’s calls for operator and directory assistance services to a provider of operator and directory assistance services selected by MLTC. Verizon will provide this routing arrangement in accordance with, but only to the extent required by, Applicable Law. Verizon will provide this routing arrangement pursuant to an appropriate written request submitted by MLTC and a mutually agreed-upon schedule. This routing arrangement will be implemented at MLTC's expense, with charges determined on an individual case basis. In addition to charges for initially establishing the routing arrangement, MLTC will be responsible for ongoing monthly and/or usage charges for the routing arrangement. MLTC shall arrange, at its own expense, the trunking and other facilities required to transport traffic to MLTC’s selected provider of operator and directory assistance services.
Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: For Calendar Quarter Ending Master Contract Sales Report Due March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 0.74 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0074. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. the sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing.
