Change Request Template Sample Clauses

Change Request Template. If after receipt of the Repair Order, the subcontractor determines that the workscope needs to be modified (e.g. from minor repair to major repair or from minor repair to test), the subcontractor shall provide this request utilizing a Change Request Template to the Buyer for disposition and stop all work on the component until a disposition is provided. Subcontractor shall request the Change Request Template to be utilized from Buyer and Buyer will furnish said template to subcontractor. At a minimum, workscope change request to AAR shall contain the minimum following information: Repair Order #, Date Submitted, OEM Part Number, NSN, Part Nomenclature, List Serial Number, Reason of Change Request, Submitted by Contact Information. If the workscope change is approved by Xxxxx, Buyer shall issue an updated Repair Order to authorize continuence of the work. If the request is not approved by Buyer, then the subcontractor shall coordinate with the Buyer for disposition instructions.
Change Request Template 

Related to Change Request Template

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

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

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

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