Project Control Document Sample Clauses

Project Control Document. Pursuant to Paragraph 1.0 (Task 1 Project Planning – Project Control Document (PCD)) of Attachment A.1 (Tasks and Deliverables) to Exhibit A (Statement of Work), Contractor must deliver to the County a PCD which includes a Detailed Work Plan (DWP). The DWP will be derived for all Work relating to Solution Implementation Services and to the extent necessary, for System Maintenance, as described in Exhibit A (Statement Work) to this Contract. Changes to the PCD must be made upon mutual agreement, in writing, by both the County and Contractor Project Director by Change Notice or otherwise, provided that both the County and Contractor respective Project Directors agree to alter the Project schedule such that it does not prejudice either party’s right to claim that such alterations constitute an Amendment to this Contract that will be governed by the terms of Paragraph 10.3 (Amendments) above.
View SourceView Similar (5)
Project Control Document. Phase II
View Source
Project Control Document. The PCD shall include, without limitation, the following components: (a) A review of the shared vision for CONTRACTOR/COUNTY relationship and the strategic goals of the implementation effort (b) Confirmation and documentation of project scope, phasing, and automation objectives; (c) A review and confirmation of the detailed project plan including, without limitation, start and end dates for all Tasks and Subtasks, work breakdown structure, Task dependencies, and assignments by Task and Subtask; (d) Definition of Customizations, testing, training, and implementation strategy for all Application Software Modules; (e) Identification of CONTRACTOR’s project team and project organization including, without limitation, defining the roles and responsibilities of the project team members; and (f) Identification of project risks and how to address these risks. . .
View Source
Project Control Document. Create Phase 1 Project Kick-Off
View Source
Project Control Document. Contractor shall produce the Project Control Document (PCD), which shall include, without limitation, the following components: (A) Project approach and training strategy. (B) Project organization chart and role descriptions. (C) Project scope. (D) Detailed project plan. (E) Project communications strategy. (F) Project organization and roles and responsibilities of team members. (G) Testing strategy for all levels of testing. (H) Project team members. The PCD shall be subject to written approval of the County Project Director, which may be granted or withheld in his/her sole discretion. Subsequent to approval, Contractor shall update the Detailed Project Plan and other applicable sections of the PCD weekly as part of the weekly Project Status Reports as set forth in Subtask 2.1 (Prepare Weekly Status Reports (PSRs)).
View Source
Project Control Document. The PCD shall include, without limitation, the following components:
View Source

Related to Project Control Document

  • Project Documents In addition to any other pertinent and necessary Project documents, the following documents shall be used in the development of the Project: A. TxDOT 2011 Texas Manual of Uniform Traffic Control Devices for Streets and Highways, including latest revisions B. Texas Department of Transportation's Standard Specifications for Construction of Highways, Streets, and Bridges, 2014 or 2024, as applicable and as amended

  • Project Agreement 1.1 If applicable, the Department will recommend approval of the project by the Federal Highway Administration. 1.2 The Sponsor agrees to comply with Title VI of the Civil Rights Act of 1964, 78 Stat. § 252, 42 U.S.C. § 2000d et seq., and all requirements imposed by or pursuant to Title 49, Code of Federal Regulations, Part 21 - “Nondiscrimination in federally assisted programs of the Department of Transportation - effectuation of Title VI of the Civil Rights Act 1964". 1.3 The DEPARTMENT and SPONSOR mutually recognize that each party is a governmental entity subject to the provisions of the Governmental Tort Claims Act (51 O.S. § 151 et seq.). The DEPARTMENT and SPONSOR hereby mutually agree that each is and may be held severally liable for any and all claims, demands, and suits in law or equity, of any nature whatsoever, paying for damages or otherwise, arising from any negligent act or omission of any of their respective employees, agents or contractors which may occur during the prosecution or performance of this Agreement to the extent provided in the Governmental Tort Claims Act. Each party agrees to severally bear all costs of investigation and defense of claims arising under the Governmental Tort Claims Act and any judgments which may be rendered in such cause to the limits provided by law. Nothing in this section shall be interpreted or construed to waive any legal defense which may be available to a party or any exemption, limitation or exception which may be provided by the Governmental Tort Claims Act. 1.4 The Sponsor understands that should it fail to fulfill its responsibilities under this Agreement, such a failure will disqualify the Sponsor from future Federal-aid funding participation on any proposed project. Federal-aid funds are to be withheld until such a time as an engineering staff, satisfactory to the Department has been properly established and functioning, the deficiencies in regulations have been corrected or the improvements to be constructed under this Agreement are brought to a satisfactory condition of maintenance.

  • Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.

  • Project Agreements Provided that where the company commences work on a project where a site agreement exists to which the company is contractually obligated or where a site agreement exists between the union and the client or their agent that provides for higher rates of pay and conditions, the conditions contained in any such site agreement will take precedence over this Agreement for the duration of the project.