Develop Project Control Document Sample Clauses

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:
AutoNDA by SimpleDocs
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
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...

Related to Develop Project Control Document

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

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