Modified Prime Contract Requirements Sample Clauses

Modified Prime Contract Requirements. Subcontractor acknowledges that the Prime Contract may be modified such that additional or modified requirements may need to be reflected in this Subcontract. In such event, VEIC will issue an amendment to this Subcontract to reflect the additional or modified Prime Contract terms and conditions. If Subcontractor fails to execute the proposed Subcontract amendment within the time period requested by VEIC, Subcontractor understands and accepts that VEIC may terminate this Subcontract immediately, in which case the provisions of Sections 15.b and 15.c above shall apply.
Sample 1Sample 2See All (7)
AutoNDA by SimpleDocs
Modified Prime Contract Requirements. The Subcontractor acknowledges that the Prime Contract may be modified such that additional or modified requirements may need to be reflected in this Subcontract. In such event, VEIC will propose an amendment to this Subcontract to reflect the additional or modified Prime Contract terms and conditions; if the Subcontractor fails to execute the proposed Subcontract amendment within the time period requested by VEIC, VEIC may terminate this Subcontract immediately and the provisions of Section 16.b and 16.c shall apply. [Signature pages follow.] Is SUBCONTRACTOR a CBE? Yes No If Yes: CBE Number: [Insert the CBE Number] Expiration Date: [Insert the Expiration Date] Preference Points: [Insert the Preference Points] Xxxx: [Insert the Xxxx] I attest that this information is accurate and valid. Also, I will immediately inform the DCSEU of any changes to our organization’s CBE status. Please attach a copy of your CBE certification to this signed contract. [INSERT THE SUBCONTRACTOR NAME] By: Print Name Signature IN WITNESS WHEREOF, Subcontractor and VEIC have caused this Subcontract to be executed as of the Effective Date. [INSERT THE SUBCONTRACTOR NAME] By: Name: Title: VERMONT ENERGY INVESTMENT CORPORATION By: Name: Title: Email: Email: Date: Date: Signature Page to VEIC/[Insert the subcontractor name] IQC Subcontract, DC-DC-[Insert the two-digit List of Attachments Attachment A Definitions and Acronyms Attachment B1 General Scope of Services and Pricing Provisions Attachment B2 Sample Work Order Attachment C Invoicing and Payments Attachment D Authorized Employees (NOTE: not required if Attachment E is included) Attachment E First Source Employment Agreement and Forms (Signature Conditionally Required) Attachment F Conflict of Interest Statement Attachment G Special Requirements Attachment H Xxxxx-Xxxxx and Related Acts, Provisions and Procedures Attachment I General Confidentiality Guidelines Memo and Protective Agreement (Signatures Required) Attachment J Rights in Data The following additional attachments are incorporated into this Subcontract by reference: Attachment Letter Document K U.S. Department of Labor Wage Determination No. 2015-4281 Revision No. 4, dated December 30, 2016 L Way to Work Amendment Act of 2006 - Living Wage Notice, xxxxx://xxxx.xx.xxx/sites/default/files/dc/sites/does/page_content/at tachments/OLLE%20Living%20Wage%20Notice%202017%20fi nal%2011-17-16.pdf M Way to Work Amendment Act of 2006 – Fact Sheet xxxxx://xxxx.xx.xxx/sites/default/...
Sample 1
Modified Prime Contract Requirements. The Subcontractor acknowledges that the Prime Contract is anticipated to be modified such that additional or modified requirements may need to be reflected in this Subcontract. In such event, VEIC will propose an amendment to this Subcontract to reflect the additional or modified Prime Contract terms and conditions; if the Subcontractor fails to execute the proposed Subcontract amendment within the time period requested by VEIC, VEIC may terminate this Subcontract immediately and the provisions of Section 16.b and 16.c shall apply. [Signature pages follow.] Is SUBCONTRACTOR a CBE? Yes No If Yes: CBE Number: [Insert the CBE Number] Expiration Date: [Insert the Expiration Date] Preference Points: [Insert the Preference Points]] Xxxx: [Insert the Xxxx]] I attest that this information is accurate and valid. Also, I will immediately inform the DCSEU of any changes to our organization’s CBE status. Please attach a copy of your CBE certification to this signed contract. [Insert the subcontractor’s name] By: Print Name Signature
Sample 1

Related to Modified Prime Contract Requirements

  • CONTRACT REQUIREMENTS a. NSF will exercise its responsibility for oversight and monitoring of procurements, contracts or other contractual arrangements for the purchase of materials and supplies, equipment or general support services under the award. The procedures set forth below must be followed to ensure that performance, materials and services are obtained in an effective manner and in compliance with the provisions of applicable Federal statutes and executive orders. The awardee must obtain written approval from the cognizant NSF Grants and Agreements Officer prior to entering into a contract if the amount exceeds $250,000 or other amount specifically identified in the agreement. Contracts clearly identified in the NSF award budget are considered approved at the time of award unless approval is withheld by the Grants and Agreements Officer. Contracts must be clearly identified in the NSF award budget on Line G6. Other. The threshold noted above also applies to cumulative increases in the value of the contractual arrangement after initial NSF approval. The awardee must not artificially segregate its procurements to lesser dollar amounts for the purpose of circumventing this requirement. A request to enter into a contract must include, at a minimum:

  • Subcontract Requirements As required by Section 6.22(e)(5) of the Administrative Code, Contractor shall insert in every subcontract or other arrangement, which it may make for the performance of Covered Services under this Agreement, a provision that said subcontractor shall pay to all persons performing labor in connection with Covered Services under said subcontract or other arrangement not less than the highest general prevailing rate of wages as fixed and determined by the Board of Supervisors for such labor or services.

  • SPECIAL CONTRACT REQUIREMENTS The Special Contract Requirements are provisions that relate directly to the performance of this contract.

  • Match Requirements There is no match required on the part of the Grantee under this Agreement.

  • Minimum System Requirements The following summarizes the minimum office system requirements for all Contractors and Architect/Engineer to possess in order to participate. It is the responsibility of all Contractors and Architect/Engineer to possess these minimum requirements at no additional cost to Princeton University.

  • 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.

  • Program Requirements A. The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Project Requirements Failure to comply with the following requirements will result in a suspension of all other operations:

  • Report Requirements The Company will send to the Reinsurer the following reports electronically, by the times indicated below:

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