Customer Application Compatibility with Transaction Recorder Sample Clauses

The 'Customer Application Compatibility with Transaction Recorder' clause establishes that the customer's software or systems must be compatible with the transaction recording solution provided. In practice, this means the customer is responsible for ensuring their applications meet any technical requirements or integration standards necessary for the transaction recorder to function properly, such as supporting specific data formats or communication protocols. This clause helps prevent operational issues by clarifying responsibility for compatibility, thereby reducing the risk of service disruptions or data loss due to mismatched systems.
Customer Application Compatibility with Transaction Recorder. (i) Customer must complete the ITS before launching the Transaction Recorder under the Agreement. (ii) Customer will (a) accurately report Billable Transactions using the Transaction Recorder and (b) only use the Services to generate Billable Transactions except as specified in Section 2.2.1(e)(iii) and [***]. (iii) Customer must generate a unique transaction ID when using the Services as required by the Documentation. For clarity, transaction IDs may be generated that will not result in a completed Trip (“Unbillable Trips”). Unbillable Trips will not be included in Billable Transactions reporting, invoicing or payments.

Related to Customer Application Compatibility with Transaction Recorder

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Drug-Free Workplace Certification As required by Executive Order No. 90-5 dated April 12, 1990, issued by the Governor of Indiana, the Company hereby covenants and agrees to make a good faith effort to provide and maintain a drug-free workplace at the Project Location. The Company will give written notice to the IEDC within ten (10) days after receiving actual notice that the Company, or an employee of the Company in the State of Indiana, has been convicted of a criminal drug violation occurring in the workplace. False certification or violation of this certification may result in sanctions including, but not limited to, suspension of payments under the Agreement, termination of the Agreement and/or debarment of contracting opportunities with the State for up to three (3) years. In addition to the provisions of the above paragraph, if the total amount set forth in the Agreement is in excess of $25,000.00, the Company agrees that it will provide a drug-free workplace by: A. Publishing and providing to all of its employees a statement notifying them that the unlawful manufacture, distribution, dispensing, possession or use of a controlled substance is prohibited in the Company’s workplace, and specifying the actions that will be taken against employees for violations of such prohibition;

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Contract Sales Reporting. Contractor shall report total Contract sales quarterly for this Cooperative Purchasing Agreement to Enterprise Services, as set forth below. Contract Sales Reporting System. Contractor shall report quarterly Contract sales in Enterprise Services’ Contract Sales Reporting System. Enterprise Services shall provide Contractor with a login password and a vendor number. The password and vendor number shall 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 Contract. If there are no Contract sales during the reporting period, Contractor must report zero sales. Due dates for Contract Sales Reporting. Quarterly Contract Sales Reports must be submitted electronically by the following deadlines for all Contract sales invoiced during the applicable calendar quarter: Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.25 percent on the purchase price for all Cooperative Purchasing Agreement sales (the purchase price is the total invoice price less applicable sales tax) under this Cooperative Purchasing Agreement. The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Contract sales invoiced (not including sales tax) x .0125. 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 shall invoice Contractor quarterly based on Contract sales reported by Contractor. Contractor is not to remit payment until Contractor receives an invoice from Enterprise Services. Payments must be received within thirty (30) calendar days of the invoice issue date from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference the invoice number. Contractor’s VMF payment to Enterprise Services must reference this Contract number, the year and quarter for which the VMF is being remitted, and Contractor’s name as set forth in this Contract, if not already included on the face of the check. Contractor’s failure to report accurate total net Contract sales, to submit a timely Contract sales report, or to remit timely payment of the VMF to Enterprise Services, shall be cause for Enterprise Services, at its discretion, to suspend Contractor or terminate this Contract or exercise 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) calendar days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Contract Sales Report. Contractor shall provide to Enterprise Services a detailed annual Contract sales report. Such report shall include, at a minimum, the following: The Goods and/or Services sold and provided (including, as applicable, category or another identifier); Services purchased by Purchaser; and Contract price. This report must be provided in an electronic format that can be read by Microsoft (MS) Excel. Such report is due within thirty (30) calendar days of the annual anniversary of the effective date of this Contract.