Project VIs Sample Clauses

Project VIs. A validation project may contain unique elements due to the product’s design, use, or proposed MOC. The VA may identify these elements for special review and consideration. Project VIs are developed by the VA team solely to address unique project elements. They must meet one of the following criteria: a) New Technology – This is technology that is new to the FAA or the EASA as a whole, not just new to the VA team members. For instance, if technology used by the applicant were new to the VA team but not the VA itself, it would not be considered a Project VI. It is the VA management’s responsibility to make sure the VA team members are properly informed of the earlier use of the technology, VA standards and MOC.
AutoNDA by SimpleDocs

Related to Project VIs

  • Project 3.01. The Recipient declares its commitment to the objectives of the Project. To this end, the Recipient shall carry out the Project in accordance with the provisions of Article IV of the General Conditions.

  • Projects There shall be a thirty (30) km free zone around the projects excluding the Metro Vancouver Area. For local residents, kilometers shall be paid from the boundary of the free zone around the project. Workers employed by any contractor within an identified free zone who resides outside of that same free zone will be paid according to the Kilometer Chart from the project to their residence less thirty

  • Project Work PURCHASER shall complete the following projects in accordance with the specifications provided in Exhibits B, C, D, E, and F and written instructions from STATE. Project locations are shown on Exhibit A unless otherwise described. PURCHASER shall furnish all material unless otherwise specified.

  • Project Work Plan The Statement of Work is the formal document incorporated into the Grant. The Project Work Plan documents how the Grantee will achieve the performance measures outlined in the Grant. Changes to the Statement of Work require an amendment. Project Work Plans may be changed with written approval from PEI and the Grantee.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Project Completion The Contractor agrees to schedule a final job walk with the County. If required, the County will prepare a list of incomplete items, the “Punch List”. The Contractor agrees to complete the “Punch List” corrections and schedule a final project completion job walk. The County will sign the “Punch List” as completed when determined, the project is finished. The Contractor agrees to submit the following along with its final payment request:

  • Project Changes 1.8.1. All changes shall be administered per the UGC. 1.8.2. Upon authorization by the Owner, the Owner or Architect/Engineer will prepare and issue all changes to the Contract affecting cost, scope and/or time as a formal Change Order to the Contract on the standard University of Texas MD Xxxxxxxx Cancer Center Change Order form. The Change Order may include separate change issues, identified as Change Proposals and field orders. 1.8.3. Upon authorization by the Owner, Change Proposals may be issued to the Architect/Engineer for pricing by the Contractor. Contractor shall submit pricing to the Owner within twenty-one (21) days and pricing shall be indicated on the standard Owner "Change in Work Cost Analysis" ("Cost Analysis") form provided in the Pre-Construction Conference Brochure. Contractor may not include a Change Proposal within a Change Order unless the Owner has accepted the Change Proposal. 1.8.3.1. The Contractor shall summarize all costs for each change at each level of subcontractor and supplier by preparing the "Cost Analysis" form, and shall provide each subcontractor's cost summary on separate "Cost Analysis" forms as backup. Additional support documentation from both the Contractor and Contractor’s subcontractors is encouraged, but such will not replace use of the standard form. 1.8.3.2. When the Contractor believes it is entitled to a time extension, Contractor shall so state as part of Contractor’s response to the Change Proposal, including a justifica- tion for a time extension. Owner may grant time extensions only if a Change Proposal affects the activities on the Longest Path of an Owner approved Work Progress Schedule; i.e., when the Work impacts the "Contract Substantial Completion Date". 1.8.3.3. If the Owner’s Project Manager and Contractor cannot mutually agree upon a fair and reasonable cost and time settlement, the Owner’s Project Manager may: 1) Reject the quotation and void the Change Proposal, 2) Issue instructions to the Contractor to proceed on a time and material basis for a price to be determined later not to exceed a fixed maximum dollar and time, or 3) Issue a Unilateral Change Order. 1.8.3.4. The Owner’s Construction Inspector and/or Owner’s Project Manager may issue field orders directly to the Contractor for minor changes to the Contract, which can be negotiated in the field. Pricing backup is at the discretion of the Owner’s Construction Inspector, but pricing backup is required for any field order, the pricing backup is to be outlined on the "Cost Analysis" form. When the Owner and Contractor have signed the field order, the Work is authorized and the field order may be included in the next Change Order. 1.8.4. Request for payment for Change Order work may be submitted only after the Change Order has been fully executed.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Project Implementation The Borrower shall:

  • Construction Phase Services 3.1.1 – Basic Construction Services

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