Project Change Request (PCR) Process Sample Clauses

Project Change Request (PCR) Process. Agency must obtain approval from State’s Bridge STIP Coordinator and State’s Bridge Engineer for changes to the Project’s scope, schedule, or budget by submitting a PCR, as specified in Paragraphs 10 a-f, below. Agency shall be fully responsible for all costs attributable to changes to the established Project scope, schedule or budget made prior to an approved PCR. Amendments to this Agreement are required for all approved PCRs. a. Scope - A PCR is required for any significant change or reduction in the scope of work described in the Project Description in Terms of Agreement, paragraph 1.
Sample 1Sample 2
AutoNDA by SimpleDocs
Project Change Request (PCR) Process. Changes that represent an amendment to the Services must be in a writing signed by authorized representatives of both parties, according to the process set forth below (the PCR Process). IBM and WSI will collaboratively conduct the following PCR process, and select a tool or set of tools to manage the process, as follows: 1. Requests for changes and responses will be made only by Project Executives. Prior to submitting requests, the Project Executives will discuss the proposed change and determine if the PCR Process is appropriate or whether the change can be handled in a more expeditious manner. 2. Requests will be made in writing, using an agreed to format, to the appropriate Project Executive. 3. The response to the change request will be made in writing, using an agreed to format, within five (5) business days of agreed definition of WSI requirements where resource pricing is based on existing pricing metrics, otherwise 10 business days. 4. In the event of a request from WSI, IBM’s response will delineate how the change affects Services, timeline, and/or fees. If IBM proposes an increase in fees, supporting detail for the proposed increase will be provided that demonstrates how IBM’s cost of providing the Service is impacted by the request. 5. If development of a response requires significant investigation that results in incremental costs to the investigating party, the parties may meet and determine an appropriate charge for the investigation. 6. A mutually signed request will be required to implement a Change. 7. In the event agreement on the change request cannot be reached, either party may choose to follow the Dispute Resolution Process. 8. Additionally, WSI and IBM agree that: (a) A mutually signed PCR will be deemed an amendment to this Agreement; (b) Day-to-day change management that does not constitute an amendment to the Services will be addressed via the Change Management Process defined in section 4.0(d); and (c) Any modification of the Services requested by WSI as a result of laws applicable to WSI will be considered a PCR covered by this Section.
Sample 1
Project Change Request (PCR) Process. Agency must obtain approval from State’s Contact for changes to the Project’s scope, schedule, or budget as specified in paragraphs 6a, 6b and 6c, below. Agency shall be fully responsible for all costs that occur outside the established Project scope, schedule or budget and prior to an approved PCR. Amendments to this Agreement are required for all approved PCRs. a. Scope - A PCR is required for any significant change or reduction in the scope of work described in the Project Description (Paragraph 1 of this Exhibit). A significant change in project scope includes any scope element or item that: a. Would increase project cost by 10% or $100,000, whichever is less; b. Is outside of the intent of the current project scope, as determined by the ODOT Program Manager; or, c. Does not meet the minimum standards of the American Association of State Highway and Transportation Officials (AASHTO) or the Manual on Uniform Traffic Control Devices (MUTCD). b. Schedule– A PCR is required if Agency or State’s Contact anticipate that any Project Milestone will be delayed by more than ninety (90) days, and also for any change in schedule that will require amendment of the Statewide Transportation Improvement Program (STIP).
Sample 1
Project Change Request (PCR) Process. Agency must obtain approval from State’s contact for changes to the Project’s scope, schedule, or budget as specified in Xxxxxxxxxx 0x, 0x xxx 0x, xxxxx. Agency shall be fully responsible for all costs that occur outside the established Project scope, schedule or budget and prior to an approved PCR. Amendments to this Agreement are required for all approved PCRs. a. Scope – A PCR is required for any significant change or reduction in the scope of work described in the Project Description (Paragraph 1 of this Exhibit). b. Schedule – A PCR is required if Agency or State’s contact anticipate that any Project Milestone will be delayed by more than ninety (90) days, and also for any change in schedule that will require amendment of the Statewide Transportation Improvement Program (STIP).
Sample 1

Related to Project Change Request (PCR) Process

  • Project Changes 1.8.1. All changes shall be administered per the UGC. 1.8.2. Upon authorization by the Owner, the Owner or Architect/Engineer will prepare and issue all changes to the Contract affecting cost, scope and/or time as a formal Change Order to the Contract on the standard University of Texas MD Xxxxxxxx Cancer Center Change Order form. The Change Order may include separate change issues, identified as Change Proposals and field orders. 1.8.3. Upon authorization by the Owner, Change Proposals may be issued to the Architect/Engineer for pricing by the Contractor. Contractor shall submit pricing to the Owner within twenty-one (21) days and pricing shall be indicated on the standard Owner "Change in Work Cost Analysis" ("Cost Analysis") form provided in the Pre-Construction Conference Brochure. Contractor may not include a Change Proposal within a Change Order unless the Owner has accepted the Change Proposal. 1.8.3.1. The Contractor shall summarize all costs for each change at each level of subcontractor and supplier by preparing the "Cost Analysis" form, and shall provide each subcontractor's cost summary on separate "Cost Analysis" forms as backup. Additional support documentation from both the Contractor and Contractor’s subcontractors is encouraged, but such will not replace use of the standard form. 1.8.3.2. When the Contractor believes it is entitled to a time extension, Contractor shall so state as part of Contractor’s response to the Change Proposal, including a justifica- tion for a time extension. Owner may grant time extensions only if a Change Proposal affects the activities on the Longest Path of an Owner approved Work Progress Schedule; i.e., when the Work impacts the "Contract Substantial Completion Date". 1.8.3.3. If the Owner’s Project Manager and Contractor cannot mutually agree upon a fair and reasonable cost and time settlement, the Owner’s Project Manager may: 1) Reject the quotation and void the Change Proposal, 2) Issue instructions to the Contractor to proceed on a time and material basis for a price to be determined later not to exceed a fixed maximum dollar and time, or 3) Issue a Unilateral Change Order. 1.8.3.4. The Owner’s Construction Inspector and/or Owner’s Project Manager may issue field orders directly to the Contractor for minor changes to the Contract, which can be negotiated in the field. Pricing backup is at the discretion of the Owner’s Construction Inspector, but pricing backup is required for any field order, the pricing backup is to be outlined on the "Cost Analysis" form. When the Owner and Contractor have signed the field order, the Work is authorized and the field order may be included in the next Change Order. 1.8.4. Request for payment for Change Order work may be submitted only after the Change Order has been fully executed.

  • PRODUCT AND PRICING CHANGE REQUESTS Supplier may request Equipment, Product, or Service changes, additions, or deletions at any time. All requests must be made in writing by submitting a signed Sourcewell Price and Product Change Request Form to the assigned Sourcewell Supplier Development Administrator. This approved form is available from the assigned Sourcewell Supplier Development Administrator. At a minimum, the request must: • Identify the applicable Sourcewell contract number; • Clearly specify the requested change; • Provide sufficient detail to justify the requested change; • Individually list all Equipment, Products, or Services affected by the requested change, along with the requested change (e.g., addition, deletion, price change); and • Include a complete restatement of pricing documentation in Microsoft Excel with the effective date of the modified pricing, or product addition or deletion. The new pricing restatement must include all Equipment, Products, and Services offered, even for those items where pricing remains unchanged. A fully executed Sourcewell Price and Product Change Request Form will become an amendment to this Contract and will be incorporated by reference.

  • Change Request Either Landlord or Tenant may request Changes after Landlord approves the Approved Plans by notifying the other party thereof in writing in substantially the same form as the AIA standard change order form (a “Change Request”), which Change Request shall detail the nature and extent of any requested Changes, including (a) the Change, (b) the party required to perform the Change and (c) any modification of the Approved Plans and the Schedule, as applicable, necessitated by the Change. If the nature of a Change requires revisions to the Approved Plans, then the requesting party shall be solely responsible for the cost and expense of such revisions and any increases in the cost of the Tenant Improvements as a result of such Change. Change Requests shall be signed by the requesting party’s Authorized Representative.

  • Change Requests 4.1.1. Either party can request changes to the Service.

  • 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 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: 6.1 Substantial Site work completed. On or before December 31, 2020 Interconnection Customer must demonstrate completion of at least 20% of project site construction. At this time, Interconnection Customer must submit to Interconnected Transmission Owner and Transmission Provider initial drawings, certified by a professional engineer, of the Customer Interconnection Facilities. 6.2 Delivery of major electrical equipment. On or before December 31, 2021, Interconnection Customer must demonstrate that all generating units have been delivered to Interconnection Customer’s project site.

  • Change Order The Change Order is then submitted to the Project Manager who immediately processes the CO with OPC as required by Bulletin 3.5 and BGS’ Contracting Plan.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives. C.1. <Title> Deliverable 1

  • Change Orders Any alteration or deviation from the Services mentioned or any other contractual specifications that result in a revision of this Agreement shall be executed and attached to this Agreement as a change order (“Change Order”).

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