Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.
Suspension or Debarment Instructions Instructions for Certification 1. By answering yes to the next Attribute question below, the vendor and prospective lower tier participant is providing the certification set out herein in accordance with these instructions. 2. The certification in this clause is a material representation of fact upon which reliance was placed when this transaction was entered into. If it is later determined that the prospective lower tier participant knowingly rendered an erroneous certification in addition to other remedies available to the federal government, the department or agency with which this transaction originated may pursue available remedies, including suspension and / or debarment. 3. The prospective lower tier participant shall provide immediate written notice to the person to which this proposal is submitted if at any time the prospective lower tier participant learns that its certification was erroneous when submitted or has become erroneous by reason of changed circumstances. 4. The terms “covered transaction,” “debarred,” “suspended,” “ineligible,” “lower tier covered transaction,” “participants,” “person,” “primary covered transaction,” “principal,” “proposal” and “voluntarily excluded,” as used in this clause, have the meanings set out in the Definitions and Coverage sections of rules implementing Executive Order 12549. You may contact the person to which this proposal is submitted for assistance in obtaining a copy of those regulations. 5. The prospective lower tier participant agrees by submitting this form that, should the proposed covered transaction be entered into, it shall not knowingly enter into any lower tier covered transaction with a person who is debarred, suspended, declared ineligible or voluntarily excluded from participation in this covered transaction, unless authorized by the department or agency with which this transaction originated. 6. The prospective lower tier participant further agrees by submitting this form that it will include this clause titled “Certification Regarding Debarment, Suspension, Ineligibility and Voluntary Exclusion-Lower Tier Covered Transaction” without modification in all lower tier covered transactions and in all solicitations for lower tier covered transactions. 7. A participant in a covered transaction may rely upon a certification of a prospective participant in a lower tier covered transaction that it is not debarred, suspended, ineligible or voluntarily excluded from the covered transaction, unless it knows that the certification is erroneous. A participant may decide the method and frequency by which it determines the eligibility of its principals. Each participant may, but is not required to, check the Nonprocurement List. 8. Nothing contained in the foregoing shall be construed to require establishment of a system of records in order to render in good faith the certification required by this clause. The knowledge and information of a participant is not required to exceed that which is normally possessed by a prudent person in the ordinary course of business dealings. 9. Except for transactions authorized under paragraph 5 of these instructions, if a participant in a covered transaction knowingly enters into a lower tier covered transaction with a person who is suspended, debarred, ineligible or voluntarily excluded from participation in this transaction, in addition to other remedies available to the federal government, the department or agency with which this transaction originated may pursue available remedies, including suspension and / or debarment.
Dissemination of Research Findings and Acknowledgement of Controlled-Access Datasets Subject to the NIH GDS Policy It is NIH’s intent to promote the dissemination of research findings from use of controlled-access dataset(s) subject to the NIH GDS Policy as widely as possible through scientific publication or other appropriate public dissemination mechanisms. Approved Users are strongly encouraged to publish their results in peer-reviewed journals and to present research findings at scientific meetings.
Specific Restrictions on Use of Licensed Materials Unauthorized Use. Licensee shall not knowingly permit anyone other than Authorized Users to use the Licensed Materials.
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.
Deadlines for Providing Insurance Documents after Renewal or Upon Request As set forth herein, certain insurance documents must be provided to the OGS Procurement Services contact identified in the Contract Award Notice after renewal or upon request. This requirement means that the Contractor shall provide the applicable insurance document to OGS as soon as possible but in no event later than the following time periods: For certificates of insurance: 5 business days For information on self-insurance or self-retention programs: 15 calendar days For other requested documentation evidencing coverage: 15 calendar days For additional insured and waiver of subrogation endorsements: 30 calendar days Notwithstanding the foregoing, if the Contractor shall have promptly requested the insurance documents from its broker or insurer and shall have thereafter diligently taken all steps necessary to obtain such documents from its insurer and submit them to OGS, OGS shall extend the time period for a reasonable period under the circumstances, but in no event shall the extension exceed 30 calendar days.
Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.
Application of General Conditions These General Conditions set forth the terms and conditions generally applicable to the Development Grant Agreement to the extent and subject to any modifications set forth in such agreement.”
Acknowledgement of Existing Physical Conditions In undertaking the work under this Contract, the Contractor acknowledges that he has visited the premises and has taken into consideration all open and apparent conditions that might affect his work. No claim based on lack of knowledge of existing conditions shall be allowed unless the existing physical conditions cannot be discovered by a reasonably observant person. Any claims relating to conditions that are materially different from the Contract Documents that were not open and apparent may be adjusted as provided in this Part.
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
