Country Specific Terms and Notifications Sample Clauses

Open Split View

Download

Share

Cite

Country Specific Terms and Notifications 

Sample 1Sample 2

Save

Copy

Related to Country Specific Terms and Notifications

• Country Specific Terms Appendix A contains additional terms and conditions of the Agreement applicable to Participants residing in those countries. In addition, Appendix A also contains information and notices of exchange control and certain other issues of which the Participant should be aware.

• Country-Specific Provisions Argentina

• License Terms This license is for one full Semester. It cannot be cancelled or terminated except under the conditions cited in this license.

• Specific Terms and Conditions To the extent that Contractor has received an award for Lot 4, Implementation Services, the following terms and conditions apply to Lot 4 Implementation Services. All Services covered under Lot 4 – Implementation Services must be performed within CONUS. An RFQ for this Lot will be awarded based on, and result in, a deliverable-based Statement of Work (SOW) which will be incorporated into an Authorized User Agreement. The RFQ will include but is not limited to: Authorized User timeframes; system integration requirements; and other risks that may affect the cost to the Authorized User. All responses to RFQs must include detailed price information, including but not limited to: hours required per title, cost per hour, etc. Travel, lodging and per diem costs must be itemized in the total quote and may not exceed the rates in the NYS OSC Travel Policy. More information can be found at xxxx://xxx.xxx.xxxxx.xx.xx/agencies/travel/travel.htm. All costs must be itemized and included in the Contractor’s quote. Article 17-B of the New York State Executive Law provides for more meaningful participation in public procurement by certified Service-Disabled Veteran-Owned Businesses (“SDVOB”), thereby further integrating such businesses into New York State’s economy. OGS recognizes the need to promote the employment of service-disabled veterans and to ensure that certified service-disabled veteran-owned businesses have opportunities for maximum feasible participation in the performance of OGS contracts. In recognition of the service and sacrifices made by service-disabled veterans and in recognition of their economic activity in doing business in New York State, Bidders are expected to consider SDVOBs in the fulfillment of the requirements of the Contract. Such participation may be as subcontractors or suppliers, as protégés, or in other partnering or supporting roles.

• Specific Terms Whenever used in this Agreement, the following words and phrases, unless the context otherwise requires, shall have the following meanings:

• CLOUD SPECIFIC TERMS AND CONDITIONS To the extent that Contractor has received an award for Lot 3, Cloud, the following terms and conditions apply to Lot 3, Cloud. For the duration of an Authorized User Agreement, the Cloud Solution shall conform to the Cloud Solution Manufacturer’s specifications, Documentation, performance standards (including applicable license duration, warranties, guarantees, Service Level Agreements, service commitments, and credits). Contractor is responsible for providing physical and logical security for all Data, infrastructure (e.g. hardware, networking components, physical devices), and software related to the services the Contractor is providing under the Authorized User Agreement. All Data security provisions agreed to by the Authorized User and Contractor within the Authorized User Agreement may not be diminished for the duration of the Authorized User Agreement without prior written agreement by the parties amending the Authorized User Agreement.

• Publicity; Terms of Agreement (a) The Parties agree that the material terms of this Agreement are the Confidential Information of both Parties, subject to the special authorized disclosure provisions set forth in Section 12.2 and this Section 12.3. The Parties have agreed to make a joint public announcement of the execution of this Agreement substantially in the form of the press release attached as Exhibit F on or after the Effective Date. (b) After issuance of such joint press release, if either Party desires to make a public announcement concerning the material terms of this Agreement, such Party shall give reasonable prior advance notice of the proposed text of such announcement to the other Party for its prior review and approval (except as otherwise provided herein), such approval not to be unreasonably withheld, except that in the case of a press release or governmental filing required by Applicable Law (where reasonably advised by the disclosing Party’s counsel), the disclosing Party shall provide the other Party with such advance notice as it reasonably can and shall not be required to obtain approval therefor. A Party commenting on such a proposed press release shall provide its comments, if any, within five (5) Business Days (or within three (3) Business Days in the event that Ambrx (or its Affiliate) is a public reporting company) after receiving the press release for review and the other Party shall give good faith consideration to same. Ambrx shall have the right to make a press release announcing the achievement of each milestone under this Agreement as it is achieved, and the achievements of Regulatory Approvals as they occur, subject only to the review procedure set forth in the preceding sentence. In relation to BMS’ review of such an announcement, BMS may make specific, reasonable comments on such proposed press release within the prescribed time for commentary, but shall not withhold its consent to disclosure of the information that the relevant milestone or Regulatory Approval has been achieved and triggered a payment hereunder. Neither Party shall be required to seek the permission of the other Party to repeat any information regarding the terms of this Agreement that have previously been publicly disclosed by such Party, or by the other Party, in accordance with this Section 12.3. For clarity, neither Party shall disclose the financial terms of this Agreement without the prior written approval of the other Party, except as and to the extent otherwise expressly permitted under this Agreement. (c) The Parties acknowledge that either or both Parties may be obligated to file under Applicable Law a copy of this Agreement with the SEC or other Government Authorities. Each Party shall be entitled to make such a required filing, provided that it requests confidential treatment of at least the financial terms and sensitive technical terms hereof and thereof to the extent such confidential treatment is reasonably available to such Party. In the event of any such filing, each Party will provide the other Party with a copy of this Agreement marked to show provisions for which such Party intends to seek confidential treatment not less than five (5) Business Days prior to such filing (and any revisions to such portions of the proposed filing a reasonable time prior to the filing thereof), and shall reasonably consider the other Party’s comments thereon to the extent consistent with the legal requirements, with respect to the filing Party, governing disclosure of material agreements and material information that must be publicly filed, and shall only disclose Confidential Information which it is advised by counsel or the applicable Governmental Authority is legally required to be disclosed. No such notice shall be required under this Section 12.3(c) if the substance of the description of or reference to this Agreement contained in the proposed filing has been included in any previous filing made by either Party hereunder or otherwise approved by the other Party. (d) Each Party shall require each of its Affiliates and private investors to which Confidential Information of the other Party is disclosed as permitted hereunder to comply with the covenants and restrictions set forth in Sections 12.1 through Section 12.3 as if each such Affiliate and each such investor were a Party to this Agreement and shall be fully responsible for any breach of such covenants and restrictions by any such Affiliate or investor.

• Vendor’s Specific Warranties, Terms, and License Agreements Because TIPS serves public entities and non-profits throughout the nation all of which are subject to specific laws and policies of their jurisdiction, as a matter of standard practice, TIPS does not typically accept a Vendor’s specific “Sale Terms” (warranties, license agreements, master agreements, terms and conditions, etc.) on behalf of all TIPS Members. TIPS may permit Vendor to attach those to this Agreement to display to interested customers what terms may apply to their Supplemental Agreement with Vendor (if submitted by Vendor for that purpose). However, unless this term of the Agreement is negotiated and modified to state otherwise, those specific Sale Terms are not accepted by TIPS on behalf of all TIPS Members and each Member may choose whether to accept, negotiate, or reject those specific Sale Terms, which must be reflected in a separate agreement between Vendor and the Member in order to be effective.

• Product Specific Terms these terms apply to specific Products referenced in this section.

• Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient. (b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program. (c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only. (d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use. (e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient. (f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor. (g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient. (h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes. (i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5. (j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.