240104 Vendor Agreement If responding to Part 1 the Vendor Agreement Signature Form (Part 1) must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, properly completed, and uploaded to this location. If Vendor has proposed deviations to the Vendor Agreement (Part 1), Vendor may leave the signature line of this page blank and assert so in the Attribute Questions and those shall be addressed during evaluation. Vendor must upload their current IRS Tax Form W-9. The legal name, EIN, and d/b/a's listed should match the information provided herein exactly. This form will be utilized by TIPS to properly identify your entity. Claim Form.pdf
Vendor Agreement (Part 1)
Vendor Agreement Signature Form (Part 1)
HHSC and Contractor Agreements HHSC and Contractor hereby agree:
A. That in the event any provision of this Contract becomes unenforceable or void all other provisions of this Contract will remain ineffect.
B. That the Contractor may not transfer or assign this Contract without the express prior written approval of HHSC.
C. That this Contract may be assigned to a state agency or agencies.
D. That HHSC may amend this Contract by written notice to the Contractor. HHSC reserves the right to amend this Contract through execution of a unilateral amendment signed by an HHSC person with delegated signature authority and provided to the Contractor under the following circumstances:
1. to correct an obvious clerical error in the Contract;
2. to incorporate new or revised federal or state statutes, rules or policies;
3. to comply with a court order or judgment; and
4. to change the name of the Contractor to reflect the Contractor's name as recorded by the Texas Secretary of State.
E. That nothing in this Contract or any conduct by a representative of HHSC relating to this Contract shall be construed as a waiver of the state's sovereign immunity to suit.
F. That neither party to this Contract waives its right to enforce a right under this Contract by failing to enforce or delaying the enforcement of any other right under this Contract.
G. That the Contractor is an independent contractor and not an employee of HHSC for any purpose. The Contractor and HHSC agreethat:
1. HHSC will not withhold or pay on behalf of the Contractor any sums for income tax, unemployment insurance, Social Security or any other withholding, or make available to the Contractor any of the benefits, including workers' compensation insurance coverage and health and retirement benefits, afforded to HHSC employees; and
2. the Contractor must indemnify HHSC from any liability, including attorneys' fees and legal expenses, incurred by HHSC with respect to claims that HHSC should have been withholding or making payments on behalf of the Contractor or providing benefits to the Contractor's employees.
H. That nothing in this Contract is intended to create a joint venture, a partnership or a principal-agent relationship.
I. That the Contractor assigns to HHSC all claims for overcharges associated with this Contract arising under the anti-trust laws of the United States, 15 U.S.C. §§ 1-38, or the anti-trust laws of the state of Texas, Tex. Bus. & Com. Code, §§ 15.01-.40.
J. That HHSC has authority to monitor and conduct fiscal and program compliance reviews of the Contractor and its subcontractor(s) to the extent of services provided under the terms of this Contract. The Contractor will grant on-site access at reasonable times to all records relating to services provided and payments received under the terms of this Contract to state and federal auditing agencies and personnel and representatives of HHSC and HHS when it is deemed necessary by such agencies for purposes of inspection, monitoring, auditing or evaluating Contractor's performance under this Contract and compliance with applicable state and federal laws, rules and regulations; the applicable HHSC provider handbook or manual; and this Contract. That for Title XX programs, HHSC shall, by Form 2029, Information Worksheet – POS Contract, set the rate or maximum amount of funds or both available to be paid to Contractor by HHSC. Form 2029 is incorporated into and made a part of this Contract and is effective for the time stated on the form. Form 2029 may be amended by HHSC as necessary to comply with state and federal laws and regulations or renewed by HHSC by a new Form 2029 and incorporated into and made part of this Contract.
K. That in compliance with §2262.003, Texas Government Code:
1. the state auditor may conduct an audit or investigation of any entity receiving funds from the state directly under the Contract or indirectly through a subcontract under the Contract;
2. acceptance of funds directly under the Contract or indirectly through a subcontract under the Contract acts as acceptance of the authority of the state auditor, under the direction of the legislative audit committee, to conduct an audit or investigation in connection with those funds; and
3. under the direction of the legislative audit committee, an entity that is the subject of an audit or investigation by the state auditor must provide the state auditor with access to any information the state auditor considers relevant to the investigation or audit.
L. That this Contract shall continue subject to the availability of appropriated funds or until the federal or state governments or both cease to participate in the program.
M. That any breach or violation of any of the provisions of this Contract or state or federal regulations shall make this entire Contract, at HHSC's option, subject to termination.
N. That if HHSC does not renew the Contractor's contract due to the Contractor's noncompliance with applicable federal or Texas statutes or rules, the Contractor cannot enter into another contract for a Community Services program until the application denial period established by HHSC expires.
O. That the venue for any lawsuit between HHSC and the Contractor shall be Travis County, Texas.
P. That this Contract may be terminated by:
Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times.
2) Compliance with the Software License Agreement is the responsibility of the Customer. DIR shall not be responsible for any Customer’s compliance with the Software License Agreement. If DIR purchases software licenses for its own use under this Contract, it shall be responsible for its compliance with the Software License Agreement terms and conditions.
Parties to Lock-Up Agreements The Company has furnished to the Underwriters a letter agreement in the form attached hereto as Exhibit A (the “Lock-up Agreement”) from each of the persons listed on Exhibit B. Such Exhibit B lists under an appropriate caption the directors and executive officers of the Company. If any additional persons shall become directors or executive officers of the Company prior to the end of the Company Lock-up Period (as defined below), the Company shall cause each such person, prior to or contemporaneously with their appointment or election as a director or executive officer of the Company, to execute and deliver to the Representatives a Lock-up Agreement.
One Agreement This Agreement and any related security or other agreements required by this Agreement, collectively:
(a) represent the sum of the understandings and agreements between the Bank and the Borrower concerning this credit;
(b) replace any prior oral or written agreements between the Bank and the Borrower concerning this credit; and
(c) are intended by the Bank and the Borrower as the final, complete and exclusive statement of the terms agreed to by them. In the event of any conflict between this Agreement and any other agreements required by this Agreement, this Agreement will prevail.
Client Agreement We are not required to enter into a written agreement complying with the Code relating to the services that are to be provided to you.
Assignment of Management Agreement As additional collateral security for the Loan, Borrower conditionally transfers, sets over, and assigns to Lender all of Borrower’s right, title and interest in and to the Management Agreement and all extensions and renewals. This transfer and assignment will automatically become a present, unconditional assignment, at Lender’s option, upon a default by Borrower under the Note, the Loan Agreement, the Security Instrument or any of the other Loan Documents (each, an “Event of Default”), and the failure of Borrower to cure such Event of Default within any applicable grace period.
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.
