Project Procedures Manual Sample Clauses

Project Procedures Manual. Contractor shall, no later than one hundred twenty (120) days after the Provisional Commencement Date hereunder, deliver to Owner six (6) copies in English of a manual, in form and substance satisfactory to Owner, which provides the guidelines by which the normal working relationships will be conducted between Owner and its representatives and Contractor (the "Project Procedures Manual"). The Project Procedures Manual will contain, among other materials, an organizational chart, correspondence procedures, a project filing system, procedures for the review of the Design Documents and Project progress, and verification procedures to be implemented for Owner with respect to the Contract Price.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Project Procedures Manual. Within thirty (30) Days after the Effective Date, Contractor shall submit to Owner’s Representative for review and approval, such approval not to be unreasonably withheld, Contractor’s proposed Project Procedures Manual which shall, at a minimum, cover the topics described in Section 01100 of the Technical Specifications.
Sample 1
Project Procedures Manual. Prior to the date hereof, Contractor shall have prepared and attached in Appendix W hereto the Project Procedures Manual, which shall, by mutual agreement between Owner and Contractor (such agreement not to be unreasonably withheld or delayed), be revised in accordance with any comments relating thereto from Owner. Upon notice from Owner, Contractor shall deliver to Owner six (6) copies in English of the final Project Procedures Manual as so revised.
Sample 1
Project Procedures Manual. The CONSULTANT will prepare a Project Procedures Manual (PPM) that will establish the scope of work, budget, schedule, organizational procedures, responsibilities, and lines of communication for the PROJECT. The management procedures and systems outlined in this plan will be instituted to encourage communication and the exchange of information between the CONSULTANT’s team and the City. Deliverables: ▪ Six (6) hard copies of initial PPM ▪ Updates in electronic format
Sample 1
Project Procedures Manual. The CMR shall meet with both APS and the A/E immediately upon notification of selection to develop a Project Procedures Manual. The purpose of the Project Procedures Manual is to establish administrative procedures for guidance to the CMR in the performance of CMR services. This document is not a Contract Document and shall not modify in any way any requirement, provision, term, right or obligation set forth in the Contract Documents. Unless directed otherwise by APS, the CMR shall submit the manual to APS for approval within twenty-one (21) days of issuance of the Pre- Construction Phase notice to proceed (NTP). The CMR shall be responsible for creating and maintaining any revisions to the Project Procedures Manual which will contain, but is not limited to, the following:
Sample 1
Project Procedures Manual. Prepare the PPM, with some elements pulled directly from the CM Procedures Manual discussed above, under Task 1, and other elements from the contra t documents. The PPM will provide detailed and PVL pro ect-specific procedures for the flow and control of communications and project documents during the construction phase The Manual will include details and/or contract procedures for the following major topics: ▪ RCTC-HDR Team Organization ▪ Contractor Organization ▪ Roles & Responsibilities ▪ Lines of Communication Hierarchy ▪ Communication Formats ▪ Community Relations/Media ▪ Emergency Response Procedur s ▪ OSHA & Other Communications ▪ Notice Procedures ▪ Labor Compliance ▪ Environmental Compliance ▪ BNSF/SCRAA Coordination ▪ FTA Requirements ▪ Safety Program ▪ Meetings ▪ Project Controls ▪ Cost Segregation/Trending ▪ Progress Payments ▪ Schedule Reviews ▪ Submittals ▪ Requests for Substitutions ▪ Requests for Information ▪ Cha ges ▪ Delays ▪ Dispute & Claim Resolution ▪ QC/ A Requirements & Res onsibilities ▪ Non-Compliance Reports ▪ Survey Control ▪ Contract Close-Out ▪ As-Built Documentation ▪ Document Control Requirements ▪ Project File Requirements The PPM will reference other stand alone documents that will be utilized in managing the PVL. The PPM is not intended as a substitute for the Contract and will state that in the event of a conflict, the Contract requirements will govern. The initial draft of the PPM will be updated, as needed, to reflect the 100% design documents and any changes to procedures made by addenda issued during the bid period. pon review and approval by RCTC, the PPM will be distr buted at the Pre-construction Meeting and each section discussed, allowing for questions or clarifications. The Manual will be corrected or updated, as necessary, during the construction phase. This manual will incorporate any stand alone documents required.
Sample 1

Related to Project Procedures Manual

  • Escalation Procedures 48.1 The Standard Practices outlines the escalation process which may be invoked at any point in the Service Ordering, Provisioning, and Maintenance processes to facilitate rapid and timely resolution of disputes.

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

  • New Procedures New procedures as to who shall provide certain of these services in Section 1 may be established in writing from time to time by agreement between the Fund and the Transfer Agent. The Transfer Agent may at times perform only a portion of these services and the Fund or its agent may perform these services on the Fund's behalf;

  • Policies and Procedures i) The policies and procedures of the designated employer apply to the employee while working at both sites.

  • Standard Operating Procedures Over approximately the past eight years, the Parties have been supplying select Products to one another for use in the operation of their respective businesses within the United States of America, Canada and Mexico. The Parties developed and been following certain standard operating procedures in connecting with, among other topics, forecasting, production planning, ordering, delivering and resolving claims on the Products supplied to one another (the “Current SOPs”). The Parties will be updating their respective business systems over the next six months, and the updates to these business systems will require the Parties to modify the Current SOPs. Once the Parties have completed the updates to the business systems and agreed on the necessary modifications to the Current SOPs, the Parties will sign a written amendment to this Agreement appending the updated standard operating procedures (the “Updated SOPs”). Until the Parties have signed a written amendment appending the Updated SOPs, the parties will continue to follow the Current SOPs. The Parties will comply with the applicable SOPs in connection with the purchase and sale of products identified in a Purchase Schedule. The Parties may add terms and conditions to, and amend the terms and conditions of, the SOP in a Purchase Schedule, but any additional and amended terms and conditions in a Purchase Schedule supplementing and modifying the SOP will only apply the specific products identified in that Purchase Schedule for its duration.

  • Amendment Procedures Amendments to this Agreement may be proposed only by the General Partner. To the fullest extent permitted by law, the General Partner shall have no duty or obligation to propose or approve any amendment to this Agreement and may decline to do so free of any duty or obligation whatsoever to the Partnership, any Limited Partner or any other Person bound by this Agreement, and, in declining to propose or approve an amendment to this Agreement, to the fullest extent permitted by law shall not be required to act in good faith or pursuant to any other standard imposed by this Agreement, any Group Member Agreement, any other agreement contemplated hereby or under the Delaware Act or any other law, rule or regulation or at equity, and the General Partner in determining whether to propose or approve any amendment to this Agreement shall be permitted to do so in its sole and absolute discretion. An amendment to this Agreement shall be effective upon its approval by the General Partner and, except as otherwise provided by Section 13.1 or Section 13.3, the holders of a Unit Majority, unless a greater or different percentage of Outstanding Units is required under this Agreement. Each proposed amendment that requires the approval of the holders of a specified percentage of Outstanding Units shall be set forth in a writing that contains the text of the proposed amendment. If such an amendment is proposed, the General Partner shall seek the written approval of the requisite percentage of Outstanding Units or call a meeting of the Unitholders to consider and vote on such proposed amendment. The General Partner shall notify all Record Holders upon final adoption of any amendments. The General Partner shall be deemed to have notified all Record Holders as required by this Section 13.2 if it has posted or made accessible such amendment through the Partnership’s or the Commission’s website.

  • Review Procedures The Parties agree to jointly conduct a review, sampling transactions of the incidents managed under this Agreement. Findings that are inconsistent with the normal or accepted way of doing business will be reconciled on a case by case basis. Any decision to further examine records will be considered on a case by case basis and appropriate follow up action agreed upon by all agencies involved. Payment for Protection Services (use if appropriate) Geographic, Statewide or Sub-Geographic (local) operating plans and procurement documents or agreement will establish billing procedures for Fee Basis Protection Services.

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

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