PROJECT SCHEDULE DEVELOPMENT REQUIREMENTS Sample Clauses

PROJECT SCHEDULE DEVELOPMENT REQUIREMENTS. 2.4.1 The Contractor shall assign a standard “Activity Code” using a custom field, to every activity or task; organized by at least the Project phase, xxxxx, xxxxxxxx, xxxxxxxx, xxxxx, xxxx, xxxxxxxxx, xx system, etc., (i.e. work breakdown structure) including the following primary Activity Codes: Activity Code & Description Activity Code & Description CP Contract Procurement C Construction PP Programming/Pre-Project Planning GC General Conditions SD Schematic Design SU Submittals DD Design Development FD Fabricate and Delivery CD Construction Documents CI Contractor Inspections BOR U.T. System Board of Regents OI Owner Inspections GMP Guaranteed Maximum Price Cx Commissioning TH THECB Approval TAB Test, Adjust, and Balance SP Subcontractor Bidding / Procurement OP Owner Provided - Contractor Installed
AutoNDA by SimpleDocs

Related to PROJECT SCHEDULE DEVELOPMENT REQUIREMENTS

  • Development Requirements The exterior wall standards set forth in this section shall apply to the structures located on the Property. At least ninety percent (90%) of the combined exterior surface area of all walls, including all stories of buildings / structures, shall consist of stone, brick, painted or tinted stucco, and factory tinted (not painted) split faced concrete masonry unit or similar material approved by the Director of Planning.

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

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

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

  • Project/Milestones Taxpayer develops and manufactures various products for use in the defense, aerospace and security industries. In consideration for the Credit, Taxpayer agrees to expand its operations at various locations throughout California, including El Segundo, Redondo Beach, Palmdale, Sunnyvale, Woodland Hills, Azusa and Rancho Xxxxxxxx. As part of its expansion, Taxpayer will invest in manufacturing equipment, computer and electrical equipment and make tenant improvements to the above facilities. Additionally, Taxpayer will hire full-time employees as part of its expansion (collectively, the “Project”). Further, Taxpayer agrees to satisfy the milestones as described in Exhibit “A” (“Milestones”) and must maintain Milestones for a minimum of three (3) taxable years thereafter. In the event Taxpayer employs more than the number of Full- time employees, determined on an annual full-time equivalent basis, than required in Exhibit A, for purposes of satisfying the “Minimum Annual Salary of California Full-time Employees Hired” and the “Cumulative Average Annual Salary of California Full-time Employees Hired,” Taxpayer may use the salaries of any of the Full-time employees hired and retained within the required time period. For purposes of calculating the “Minimum Annual Salary of California Full-time Employees Hired” and the “Cumulative Average Annual Salary of California Full-time Employees Hired,” the salary of any full-time employee that is not employed by the taxpayer for the entire taxable year shall be annualized. In addition, Xxxxxxxx agrees that any full-time employee hired after the effective date of this agreement that is a “qualified full-time employee” (as defined in RTC section 23636) shall be excluded from the calculation of the net increase of full-time employees required by this Agreement if Taxpayer claims the credit allowed by RTC section 23636.

  • For Product Development Projects and Project Demonstrations  Published documents, including date, title, and periodical name.  Estimated or actual energy and cost savings, and estimated statewide energy savings once market potential has been realized. Identify all assumptions used in the estimates.  Greenhouse gas and criteria emissions reductions.  Other non-energy benefits such as reliability, public safety, lower operational cost, environmental improvement, indoor environmental quality, and societal benefits.  Data on potential job creation, market potential, economic development, and increased state revenue as a result of the project.  A discussion of project product downloads from websites, and publications in technical journals.  A comparison of project expectations and performance. Discuss whether the goals and objectives of the Agreement have been met and what improvements are needed, if any.

  • Project Timeline The Project Timeline establishes a start and end date for each Phase of the Project. Developed during the Initiate & Plan Stage and revised as mutually agreed to, if needed, the timeline accounts for resource availability, business goals, size and complexity of the Project, and task duration requirements.

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

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

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