License Reporting. Government Integrator shall deliver to MS report information, via the format attached hereto as Exhibit B ("Report Format"), or such other format as MS shall specify from time to time in the future. Report information shall be itemized for each Program and shall be itemized for each Participating Agency under the Program. Such Report is due no later than the fifteenth (15th) day of each calendar month. Each such Report shall be sent to the following addresses: Microsoft Corporation Microsoft Corporation Dept. 551, One Microsoft Way 5335 Xxxxxxxxx Xxxxxx Xxxxxxx, XX 00000-0000 Suite 600 Attn: Special Agreement Accounting Attn: [*] Federal Contracts Manager Following receipt of each such Report, MS shall invoice Government Integrator and Government Integrator shall be obligated to pay MS the fees set forth in the relevant Program Agreement for each unit indicated on the Report. The Government Integrator's invoice address is identified in each Program Agreement.

License Reporting. No later than on the fifth (5th) Business Day following the end of each quarter of the Term agreed in the Purchase Order, the Licensee shall submit to the Licensor via email to xxxxx@xxxxxxxxxxx.xxx any changes to licensing (nodes consumption) in case of any changes the actual costs will be prorated on the basis of the rates stated below and invoiced accordingly.

License Reporting. No later than on the fifth (5th) Business Day following the end of each quarter of the Term agreed in the Purchase Order, the Licensee shall submit to the Licensor via email to xxxxx@xxxxxxxxxxx.xxx any changes to licensing (peers, orders, CAs), Organizations (MSPIDs), list of End Users, nodes consumption, in case of any changes the actual costs will be prorated on the basis of the rates stated below and invoiced accordingly. Such change in usage (change in Organizations (MSPIDs) and Nodes across all environments running on Software can be extracted from each deployed instance of the Software by following the guidelines in the following Link.

License Reporting. For Armory Services that are self-hosted you agree to allow Armory to collect telemetry data for the purposes of identifying the licenses being used. If telemetry data is unavailable, at Armory’s request, but in no case more than once per quarter, You agree to provide detail on the number of Users interacting with the Services and Armory may, at its discretion, require Customer to reduce its usage to its agreed to number of Users or, if Customer’s usage cannot be reduced to the licensed number of Users, charge Customer for any overage at the then market rate, unless a different rate is agreed to by the parties. Any licenses added pursuant to this section shall be coterminous with the remainder of Customer’s licenses and shall be billed on a pro-rata basis. Third party providers. Armory may use Stripe, Inc. and its affiliates as a third party service provider for payment services (e.g., card acceptance, merchant settlement, and related services) (a “Payment Processor”). By making or accepting any payments via the Services, you agree to be bound by Stripe’s Privacy Policy (currently accessible at xxxxx://xxxxxx.xxx/us/ privacy) and its Terms of Service (currently accessible at xxxxx://xxxxxx.xxx/ us/terms) and hereby consent and authorize Armory and Stripe to share any information and payment instructions you provide with one or more third parties to the minimum extent required to complete your transactions. By making payments on our Website, you also agree to be bound by Stripe’s services agreement at: xxxxx://xxxxxx.xxx/us/legal/ and Stripe’s connect agreement at: xxxxx://xxxxxx.xxx/connect-account/legal. Account and Environment Security Customer Data Your Responsibilities: You are solely responsible for your Customer Data. By importing, storing, or processing Customer Data with the Armory Services, You affirm, represent, and warrant that:

License Reporting. Contractor shall provide the State with the following information regarding the State’s Oracle software licenses and other State-paid software licenses installed on the HSEP on a quarterly, or more frequent basis as agreed upon by the parties, as part of Reporting for M&O Services specified in this section: 1. An Inventory of all of State’s software licenses installed in all environments managed within the scope of this Contract. 2. The Inventory shall include: a. the product name, version, number of licenses and vendor contact information. b. A list of installed product components. c. Specification of the characteristics of the physical and/or virtual server on which the licensed software is running including the number of physical or virtual CPU cores and other server characteristics as available to determine or enable a license count that helps satisfy the State’s software license reporting requirements. d. List of license keys to be sent to State via mutually agreed secure process. Table C – Transition Deliverables includes: (1) the Deliverable Identifier (“Req”) Number, (2) the Requirement Name, and (3) Due Date. • Transition Deliverables are non-Key Deliverables that do require Acceptance by the State. • Transition Deliverables are tied to Core M&O services monthly fee as specified in Attachment B. 3. T01 Lessons Learned document 30 days prior to Contract termination 3.T02 M&O Plan 90 days prior to Contract termination 3.T03 Project Management Plan 90 days prior to Contract termination

Related to License Reporting

Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.
CHILD ABUSE REPORTING CONTRACTOR hereby agrees to annually train all staff members, including volunteers, so that they are familiar with and agree to adhere to its own child and dependent adult abuse reporting obligations and procedures as specified in California Penal Code section 11164 et seq. and Education Code 44691. To protect the privacy rights of all parties involved (i.e., reporter, child and alleged abuser), reports will remain confidential as required by law and professional ethical mandates. A written statement acknowledging the legal requirements of such reporting and verification of staff adherence to such reporting shall be submitted to the LEA.
Sales Reporting Requirements This is a requirement of the TIPS Contract and is non-negotiable. By submitting this proposal, Vendor certifies that Vendor will properly report all TIPS sales. With the exception of TIPS Automated Vendors, who have signed an exclusive agreement with TIPS regarding reporting, all TIPS Sales must be reported to TIPS by either: (1) Emailing the purchase order or similar purchase document (with Vendor’s Name, as known to TIPS, and the TIPS Contract Name and Number included) to TIPS at xxxxxx@xxxx-xxx.xxx with “Confirmation Only” in the subject line of the email within three business days of Vendor’s acceptance of the order, or; (2) Within 3 business days of the order being accepted by Vendor, Vendor must login to the TIPS Vendor Portal and successfully self-report all necessary sale information within the Vendor Portal and confirm that it shows up accurately on your current Vendor Portal statement. No other method of reporting is acceptable unless agreed to by the Parties in writing. Failure to report all sales pursuant to this provision may result in immediate cancellation of Vendor’s TIPS Contract(s) for cause at TIPS’ sole discretion.
CONTRACT SALES REPORTING Contractor shall report total contract sales quarterly to Enterprise Services, as set forth below.
Required Vendor Sales Reporting By responding to this Solicitation, you agree to report to TIPS all sales made under any awarded Agreement with TIPS. Vendor is required to report all sales under the TIPS contract to TIPS. If the TIPS Member entity requesting a price from the awarded Vendor requests the TIPS contract, Vendor must include the TIPS Contract number on any communications with the TIPS Member entity. If awarded, you will be provided access to the Vendor Portal. To report sales, login to the TIPS Vendor Portal and click on the PO’s and Payments tab. Pages 3-7 of the Vendor Portal User Guide will walk you through the process of reporting sales to TIPS. Please refer to the TIPS Accounting FAQ’s for more information about reporting sales and if you have further questions, contact the Accounting Team at xxxxxxxxxx@xxxx-xxx.xxx. The Vendor or vendor assigned dealers are responsible for keeping record of all sales that go through the TIPS Agreement and submitting same to TIPS.
Sublicense Requirements Any Sublicense: (A) is subject to this Agreement; (B) will reflect that any sublicensee will not further sublicense; (C) will prohibit sublicensee from paying royalties to an escrow or other similar account; (D) will expressly include the provisions of Sections 8, 9, and 10 for the benefit of Stanford; and (E) will include the provisions of Section 4.4 and require the transfer of all the sublicensee’s obligations to *****, including the payment of royalties specified in the Sublicense, to Stanford or its designee, if this Agreement is terminated. If the sublicensee is a spin-out from *****, ***** must guarantee the sublicensee’s performance with respect to the payment of Stanford’s share of Sublicense royalties.
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.
Adverse Event Reporting Both Parties acknowledge the obligation to comply with the Protocol and / or applicable regulations governing the collection and reporting of adverse events of which they may become aware during the course of the Clinical Trial. Both Parties agree to fulfil and ensure that their Agents fulfil regulatory requirements with respect to the reporting of adverse events.
Progress Reporting 5. The IP will submit to UNICEF narrative progress reports against the planned activities contained in the Programme Document, using the PDPR. Unless otherwise agreed between the Parties in writing, these reports will be submitted at the end of every Quarter. The final report will be submitted no later than thirty (30) calendar days after the end the Programme and will be provided together with the FACE form.
Compliance Reporting a. Provide reports to the Securities and Exchange Commission, the National Association of Securities Dealers and the States in which the Fund is registered. b. Prepare and distribute appropriate Internal Revenue Service forms for corresponding Fund and shareholder income and capital gains. c. Issue tax withholding reports to the Internal Revenue Service.

License Reporting Sample Clauses

Filter & Search

Related Clauses

Parent Clauses

Related to License Reporting