Develop Project Control Document Clause Samples

The 'Develop Project Control Document' clause requires the creation of a formal document that outlines the methods and procedures for monitoring and managing a project's progress. This document typically details reporting requirements, key performance indicators, and processes for addressing deviations from the project plan. By establishing clear guidelines and expectations for project oversight, the clause ensures that all parties have a shared understanding of how the project will be controlled, reducing the risk of miscommunication and helping to keep the project on track.
Develop Project Control Document. Within thirty (30) calendar days of the effective date of the Agreement, the Contractor shall create, and deliver to County, two PCDs, one for the Sheriff’s Department and one for the Probation Department, consistent with this Exhibit B (Statement of Work). The contents of each PCD shall include the relevant elements of the following:
View SourceView Similar (2)
Develop Project Control Document. CONTRACTOR shall develop a Project Control Document (hereafter “PCD”) that shall include, without limitation; a detailed work plan with identified Milestones. Additionally, CONTRACTOR shall review the communication process, which shall include, without limitation, weekly Project Status Reports, as described in Task 2 (Project Management). As a first step in the preparation of the PCD, CONTRACTOR shall review, clarify and refine all project goals. This process shall ensure that all involved parties have clearly defined and agreed upon all project goals. CONTRACTOR shall present such goals for written approval to COUNTY’s Project Director, which may be granted or withheld in his/her sole discretion. Subsequently, CONTRACTOR shall prepare a PCD that includes, without limitation, the following: (A) Designs the project’s approach and training strategy for COUNTY staff, including trainers and Users, based on COUNTY’s requirements and CONTRACTOR’s
View Source
Develop Project Control Document. Contractor shall develop a Project Control Document (hereafter “PCD”) that shall include, without limitation; a detailed work plan with identified Milestones. Additionally, Contractor shall review the communication process, which shall include, without limitation, weekly Project Status Reports. As a first step in the preparation of the PCD, Contractor shall review, clarify, and refine all project goals. This process shall ensure that all involved parties have clearly defined and agreed upon all project goals. Contractor shall present such goals for written approval to County’s Project Director, which may be granted or withheld in his/her sole discretion. Subsequently, Contractor shall prepare a PCD that includes, without limitation, the following: (A) Designs the project’s approach and training strategy for County staff, including trainers, technical staff and users, based on County’s requirements and Contractor’s project and training approach. (B) Discusses the expected roles and responsibilities of Contractor and County project organizations and develops a communication strategy for sharing the context and vision of the project to the project team members at large. (C) Confirms and documents project scope. (D) Reviews and confirms detailed project plan, including, without limitation, the resources, dependencies, and start and end dates for all Tasks and Subtasks. (E) Defines project communication strategy. (F) Defines and documents the project organization, including, without limitation, defining the roles and responsibilities of the project team members. (G) Defines testing strategy for all levels of testing. (H) Identifies project team. Contractor shall develop this PCD consistent with this Exhibit A, (Statement of Work). Contractor shall specifically address each Task and Subtask to be performed in the PCD. The order in which Contractor shall perform the Tasks and Subtasks and the order in which Contractor shall produce the Deliverables shall be apparent in the PCD. Contractor must formally present the PCD for prior written approval of Treasurer and Tax Collector, which may be granted or withheld in his/her sole discretion. Any subsequent significant modifications to the PCD shall require the prior written approval of Treasurer and Tax Collector, which may be granted or withheld in his/her sole discretion. Any subsequent modifications to the PCD, which are not significant, shall require the prior written approval of County’s Project Director, which ma...
View Source

Related to Develop Project Control Document

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

  • Design Development Documents See Section 2, Part 1, Article 2.1.5.

  • 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 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 DFPS and the Grantee.