Completion of change request Form Sample Clauses

Completion of change request Form. To request a change to the MetaPack Global Platform, Customer must complete the change request form set out at Appendix A to this Schedule 4, and either (i) deliver it via email to MetaPack at the nominated email address set out in Schedule 5; or (ii) login via the the MetaPack Customer portal and create a change request case. Any change request form must state the relevant purchase order number before MetaPack will commence work. MetaPack may at its sole discretion elect to accept, refuse or propose a variation to the change request.
AutoNDA by SimpleDocs

Related to Completion of change request Form

  • CHANGE REQUEST PROCEDURE (a) Any Change Request of Customer or SAP must be in writing and in the format as provided by SAP.

  • 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 Request Procedures 4.1. Either party can request changes to the Service in accordance with the change request form attached to the Order Form or provided by SAP from time to time (“Change Request”).

  • Certification of Completion Certification of completion of the program will be contingent upon Resident successfully completing the core requirements of the Program, returning all property of the Medical Center such as books, equipment, etc., and having settled any other professional or financial obligations to the Medical Center. The certificate will be issued in accordance with the provisions of the ASHP Regulations on Accreditation of Pharmacy Residencies and signed by the RPD and the Chief Executive Officer of the organization. A certificate will not be issued to anyone who does not complete the program’s requirements. Core requirements to successfully complete the program include: • Possess a valid pharmacist license from the Pennsylvania State Board of Pharmacy by October 31st of the residency year. • Successful completion of core learning experiences and required longitudinal learning experiences as defined in the learning experience descriptions • Completion of all R1 goals/objectives with a status of achieved by the end of the residency. Completion of 100% of the remaining goals/objectives for the program with at least 50% of the objectives having a status as achieved. All objectives must have a minimum status of satisfactory progress. • All evaluations must be completed in accordance with ASHP Accreditation Standard as outlined in the Resident Agreement • Completion of pharmacokinetic certification by October 31 of residency year • Completion of inpatient anticoagulation certification by October 31 of residency year. • Completion of major project, which includes meeting all project deadlines and submission of written manuscript of completed project to the RAC. • Assigned projects (MUE, drug review, class review, and management project) have been completed • Presentation of at least one major CME program. • Completion of minimum staffing requirements as described in section 2.7 • Adherence to the organization’s attendance standards and as described in this document under Exhibit A.

  • Construction Change Directive A written order prepared and issued by the District, the Construction Manager, and/or the Architect and signed by the District and the Architect, directing a change in the Work.

  • Request for Waiver A. Prior to submission of a request for a partial or total waiver, Bidder/Contractor shall speak to the Designated Contacts of the OGS Office of Minority- and Women-Owned Business Enterprises for guidance.

  • Execution of Change Orders Change Orders shall be signed by the Contractor, ordinarily certified by the Design Professional, and approved by the Owner in accordance with the form of Change Order prescribed by the Owner. No request for payment by the Contractor for a Change Order shall be due, nor shall any such request appear on an Application for Payment, until the Change Order is executed by the Owner. In the event of emergency (see Article 1.4.4) or significant impact to the Overall Project Schedule, the Owner shall direct the Change Order to proceed upon a Force Account until the cost and time is resolved in the manner set forth in Paragraph 3.2.7.3 below.

  • Escrow Format Specification 3.1. 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.

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

  • No Cost Change Request The Authorized User reserves the right to reasonably amend a Fixed-Price Deliverable, provided the amendment does not materially change the Scope of the Deliverable, without a cost increase. Although the Authorized User has endeavored to identify many tasks associated with a Fixed-Price Deliverable (Tasks), additional Tasks which can reasonably be anticipated to carry out the Deliverable shall be within the scope of the Deliverable, and shall not result in a cost increase. An Authorized User shall use Appendix F, Attachment 4, No Cost Change Request Template to reflect such modifications. Written approval of the No-Cost Change Request is required from both the Authorized User and the Contractor.

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