Disputes Not Related to Contract Services The Engineer shall be responsible for the settlement of all contractual and administrative issues arising out of any procurement made by the Engineer in support of the services authorized herein.
Vendor’s Resellers as Related to This Agreement Vendor’s Named Resellers (“Resellers”) under this Agreement shall comply with all terms and conditions of this agreement and all addenda or incorporated documents. All actions related to sales by Authorized Vendor’s Resellers under this Agreement are the responsibility of the awarded Vendor. If Resellers fail to report sales to TIPS under your Agreement, the awarded Vendor is responsible for their contractual failures and shall be billed for the fees. The awarded Vendor may then recover the fees from their named reseller. Support Requirements If there is a dispute between the awarded Vendor and TIPS Member, TIPS or its representatives may, at TIPS sole discretion, assist in conflict resolution if requested by either party. TIPS, or its representatives, reserves the right to inspect any project and audit the awarded Vendor’s TIPS project files, documentation and correspondence related to the requesting TIPS Member’s order. If there are confidentiality requirements by either party, TIPS shall comply to the extent permitted by law. Incorporation of Solicitation The TIPS Solicitation which resulted in this Vendor Agreement, whether a Request for Proposals, the Request for Competitive Sealed Proposals or Request for Qualifications solicitation, or other, the Vendor’s response to same and all associated documents and forms made part of the solicitation process, including any addenda, are hereby incorporated by reference into this Agreement as if copied verbatim. SECTION HEADERS OR TITLES THE SECTON HEADERS OR TITLES WITHIN THIS DOCUMENT ARE MERELY GUIDES FOR CONVENIENCE AND ARE NOT FOR CLASSIFICATION OR LIMITING OF THE RESPONSIBILITES OF THE PARTIES TO THIS DOCUMENT. STATUTORY REQUIREMENTS Texas governmental entities are prohibited from doing business with companies that fail to certify to this condition as required by Texas Government Code Sec. 2270. By executing this agreement, you certify that you are authorized to bind the undersigned Vendor and that your company (1) does not boycott Israel; and (2) will not boycott Israel during the term of the Agreement. You certify that your company is not listed on and does not and will not do business with companies that are on the Texas Comptroller of Public Accounts list of Designated Foreign Terrorists Organizations per Texas Gov't Code 2270.0153 found at xxxxx://xxxxxxxxxxx.xxxxx.xxx/purchasing/docs/foreign-terrorist.pdf You certify that if the certified statements above become untrue at any time during the life of this Agreement that the Vendor will notify TIPS within three (3) business day of the change by a letter on Vendor’s letterhead from and signed by an authorized representative of the Vendor stating the non-compliance decision and the TIPS Agreement number and description at: Attention: General Counsel ESC Region 8/The Interlocal Purchasing System (TIPS) 0000 Xxxxxxx 000 Xxxxx Xxxxxxxxx, XX,00000 And by an email sent to xxxx@xxxx-xxx.xxx Insurance Requirements The undersigned Vendor agrees to maintain the below minimum insurance requirements for TIPS Contract Holders: General Liability $1,000,000 each Occurrence/ Aggregate Automobile Liability $300,000 Includes owned, hired & non-owned Workers' Compensation Statutory limits for the jurisdiction in which the Vendor performs under this Agreement. Umbrella Liability $1,000,000 When the Vendor or its subcontractors are liable for any damages or claims, the Vendor’s policy, when the Vendor is responsible for the claim, must be primary over any other valid and collectible insurance carried by the Member. Any immunity available to TIPS or TIPS Members shall not be used as a defense by the contractor's insurance policy. The coverages and limits are to be considered minimum requirements and in no way limit the liability of the Vendor(s). Insurance shall be written by a carrier with an A-; VII or better rating in accordance with current A.M. Best Key Rating Guide. Only deductibles applicable to property damage are acceptable, unless proof of retention funds to cover said deductibles is provided. "Claims made" policies will not be accepted. Vendor’s required minimum coverage shall not be suspended, voided, cancelled, non-renewed or reduced in coverage or in limits unless replaced by a policy that provides the minimum required coverage except after thirty (30) days prior written notice by certified mail, return receipt requested has been given to TIPS or the TIPS Member if a project or pending delivery of an order is ongoing. Upon request, certified copies of all insurance policies shall be furnished to the TIPS or the TIPS Member. Special Terms and Conditions • Orders: All Vendor orders received from TIPS Members must be emailed to TIPS at tipspo@tips- xxx.xxx. Should a TIPS Member send an order directly to the Vendor, it is the Vendor’s responsibility to forward a copy of the order to TIPS at the email above within 3 business days and confirm its receipt with TIPS. • Vendor Encouraging Members to bypass TIPS agreement: Encouraging TIPS Members to purchase directly from the Vendor or through another agreement, when the Member has requested using the TIPS cooperative Agreement or price, and thereby bypassing the TIPS Agreement is a violation of the terms and conditions of this Agreement and will result in removal of the Vendor from the TIPS Program. • Order Confirmation: All TIPS Member Agreement orders are approved daily by TIPS and sent to the Vendor. The Vendor should confirm receipt of orders to the TIPS Member (customer) within 3 business days. • Vendor custom website for TIPS: If Vendor is hosting a custom TIPS website, updated pricing when effective. TIPS shall be notified when prices change in accordance with the award.
Data Reporting 1. Maintain and adhere to data system software and encrypted portable computer device updates, and interface capability requirements for each computer located within the facility, and as specified in the Contract and required by County.
Data Retention The Company will hold and use the Data only as long as is necessary to implement, administer and manage the Grantee’s participation in the Plan, or as required to comply with legal or regulatory obligations, including under tax and security laws.
Work-Related Injury or Illness In the event of an eligible employee’s absence from work being due to work related injury or work related illness, contributions at the normal rate will continue for the period of the absence provided that:
Statement of Grievance The grievance shall contain a statement of:
DATA REQUESTS Upon the written request of the District, the State Auditor’s Office, the Appraisal District, or the Comptroller during the term of this Agreement, the Applicant, the District or any other entity on behalf of the District shall provide the requesting party with all information reasonably necessary for the requesting party to determine whether the Applicant is in compliance with its rights, obligations or responsibilities, including, but not limited to, any employment obligations which may arise under this Agreement.
Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)
Data Requirements • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.
Definition of Grievance A grievance shall be defined as any difference arising out of the interpretation, application, administration, or alleged violation of the Collective Agreement.
