Product Entitlement Supplement Sample Clauses

Product Entitlement Supplement. The “Product Entitlement Supplement” sets forth any supplemental usage rights, restrictions, and terms specific to a particular Software product. The Product Entitlement Supplement may be found at xxx.xxxxxx.xxx/xxxxx/xxxxxxxxxx (or a successor URL) and is incorporated by reference and an integral part of the Agreement.
AutoNDA by SimpleDocs

Related to Product Entitlement Supplement

  • Agreement Scope The scope of this Agreement is as prescribed in section 46 of the Act, setting out: • the health services to be provided to the State by the HSP, • the TTR in support of the health services to be provided, • the funding to be provided to the HSP for the provision of the health services, including the way in which the funding is to be provided, • the performance measures and operational targets for the provision of the health services by the HSP, • how the evaluation and review of results in relation to the performance measures and operational targets is to be carried out, • the performance data and other data to be provided by the HSP to the Department CEO, including how, and how often, the data is to be provided, and • any other matter the Department CEO considers relevant to the provision of the health services by the HSP. Where appropriate, reference will be made in this Agreement to Policy Frameworks issued by the Department CEO pursuant to Part 3, Division 2 of the Act.

  • Lost Card Notification If you believe the Card has been lost or stolen, you will immediately call the Credit Union at 000-000-0000 or 000-000-0000.

  • Payment Schedule Except as provided in section 6.10 Travel, Meals and Lodging, payments will only be made based on Deliverables outlined within the Authorized User Agreement. Any invoice not related directly to a completed deliverable will be rejected. Any charge included on the invoice without backup documentation as specified in the Authorized User Agreement (travel receipts, etc.) may be removed. Any outstanding charges un-invoiced or removed from the invoice must be submitted/resubmitted within 120 Calendar days or may not be reimbursed. Each Deliverable may contain a retainage allotment as specified within the Authorized User Agreement. Each invoice is to include a detailed and itemized list of all retainage withholds that are in place since the activation of the Authorized User Agreement. Payment schedule shall be based on the final Authorized User Agreement as negotiated by the Authorized User and Contractor. Payment is only to be made after the deliverable within the Authorized User Agreement is accepted by the Authorized User. A Contractor is encouraged to submit no more than one invoice per month. Invoices must include cumulative retainage holdback. Invoices submitted to an Authorized User must include backup documentation as defined in the negotiated Authorized User Agreement.

  • LIABILITY FOR UNAUTHORIZED USE-LOST/STOLEN CARD NOTIFICATION You agree to notify Credit Union immediately, orally or in writing at Florida Credit Union, X.X. Xxx 0000, Xxxxxxxxxxx, XX 00000 or telephone (000) 000-0000 twenty four

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • Balancing Authority Area Notification At least three months before Initial Synchronization Date, the Interconnection Customer shall notify the CAISO and Participating TO in writing of the Balancing Authority Area in which the Large Generating Facility intends to be located. If the Interconnection Customer intends to locate the Large Generating Facility in a Balancing Authority Area other than the Balancing Authority Area within whose electrically metered boundaries the Large Generating Facility is located, and if permitted to do so by the relevant transmission tariffs, all necessary arrangements, including but not limited to those set forth in Article 7 and Article 8 of this LGIA, and remote Balancing Authority Area generator interchange agreements, if applicable, and the appropriate measures under such agreements, shall be executed and implemented prior to the placement of the Large Generating Facility in the other Balancing Authority Area.

  • END USER AGREEMENTS (“EUA H-GAC acknowledges that the END USER may choose to enter into an End User Agreement (“EUA) with the Contractor through this Agreement, and that the term of the EUA may exceed the term of the current H-GAC Agreement. H-GAC’s acknowledgement is not an endorsement or approval of the End User Agreement’s terms and conditions. Contractor agrees not to offer, agree to or accept from the END USER, any terms or conditions that conflict with those in Contractor’s Agreement with H-GAC. Contractor affirms that termination of its Agreement with H-GAC for any reason shall not result in the termination of any underlying EUA, which shall in each instance, continue pursuant to the EUA’s stated terms and duration. Pursuant to the terms of this Agreement, termination of this Agreement will disallow the Contractor from entering into any new EUA with END USERS. Applicable H-GAC order processing charges will be due and payable to H-GAC

  • Certification Regarding Entire TIPS Agreement Vendor agrees that, if awarded, Vendor's final TIPS Contract will consist of the provisions set forth in the finalized TIPS Vendor Agreement, Vendor's responses to these attribute questions, and: (1) The TIPS solicitation document resulting in this Agreement; (2) Any addenda or clarifications issued in relation to the TIPS solicitation; (3) All solicitation information provided to Vendor by TIPS through the TIPS eBid System; (3) Vendor’s entire proposal response to the TIPS solicitation including all accepted required attachments, acknowledged notices and certifications, accepted negotiated terms, accepted pricing, accepted responses to questions, and accepted written clarifications of Vendor’s proposal, and; any properly included attachments to the TIPS Contract. Does Vendor agree? Yes, Vendor agrees 3 Minimum Percentage Discount Offered to TIPS Members on all Goods and Services (READ 6 CAREFULLY) Please read thoroughly and carefully as an error on your response can render your contract award unusable. TIPS Members often turn to TIPS Contracts for ease of use and to receive discounted pricing. What is the minimum percentage discount that you can offer TIPS Members off of all goods and service pricing (whether offered through Pricing Form 1, Pricing Form 2, or in another accepted format) that you offer? Only limited goods/services specifically identified and excluded from this discount in Vendor’s original proposal may be excluded from this discount. Vendor must respond with a percentage from 0%-100%. The percentage discount that you input below will be applied to your "Catalog Pricing", as defined in the solicitation, for all TIPS Sales made during the life of the contract. You cannot alter this percentage discount once the solicitation legally closes. You will always be required to discount every TIPS Sale by the percentage included below with the exception of limited goods/services specifically identified and excluded from this discount in Vendor’s original proposal. If you add goods or services to your "Catalog Pricing" during the life of the contract, you will be required to sell those new items with this discount applied.

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

  • Additional Requirements from Authorized Users An Authorized User may have distinct requirements that must be met by all individuals employed by or working for the Authorized User. The Contractor’s Staff Members will be expected to comply with these requirements as a condition of the placement.

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