SCOPE OF WORK/PROJECT REQUIREMENTS Sample Clauses

SCOPE OF WORK/PROJECT REQUIREMENTS. Describe required project requirements in detail. Under no circumstance should a SOW be developed or an SOW RFP be released where the deliverables are not quantified or the criteria for acceptance are not defined. Be clear and concise. The deliverables identified here should be directly tied to payment provisions. CHANGE ORDERS We do not anticipate the need to make change orders, however, if it becomes necessary, such work must be authorized by the State in writing before such work can proceed and may require an amendment to the SOW Agreement. SUBCONTRACTORS Identify all proposed subcontractors and their full roles that may be involved completing the Scope of Work. No work shall be subcontracted without knowledge of and approval by the State.
AutoNDA by SimpleDocs
SCOPE OF WORK/PROJECT REQUIREMENTS. Describe required project requirements in detail. Under no circumstance should a SOW be developed or an SOW RFP be released where the deliverables are not quantified or the criteria for acceptance are not defined. Be clear and concise. The deliverables identified here should be directly tied to payment provisions. SAMPLE
SCOPE OF WORK/PROJECT REQUIREMENTS. 7.1. Describe project scope of work, special requirements, schedule and completion dates, etc., in detail. (Under no circumstance should a SOW be developed, or a SOW RFP be released, where the deliverables are not quantified or the criteria for acceptance are not defined. Be clear and concise. The deliverables identified here should be directly tied to payment provisions)
SCOPE OF WORK/PROJECT REQUIREMENTS 

Related to SCOPE OF WORK/PROJECT REQUIREMENTS

  • Scope of Work The Contractor has overall responsibility for and shall provide and furnish all materials, equipment, tools and labor as necessary or reasonably inferable to complete the Work, or any phase of the Work, in accordance with the Owner’s requirements and the terms of the Contract Documents.

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

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

  • Project Scope The physical scope of the Project shall be limited to only those capital improvements as described in Appendix A of this Agreement. In the event that circumstances require a change in such physical scope, the change must be approved by the District Committee, recorded in the District Committee's official meeting minutes, and provided to the OPWC Director for the execution of an amendment to this Agreement.

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

  • REVIEW OF WORK The Consultant shall permit the City, its agents and/or employees to review, at any time, all work performed pursuant to the terms of this Agreement at any stage of the work;

  • Completion of Work Contractor is accountable for completing the Work within the Contract Time stated in the Contract, or as otherwise amended by Change Order.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

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

Time is Money Join Law Insider Premium to draft better contracts faster.