Handover Protocol Sample Clauses

Handover Protocol. 1. The handover and takeover of the Subject of the Sub-lease and the course of the sub-lease period (Event) shall be recorded in the handover protocol (hereinafter referred to as the “Handover Protocol”). The Handover Protocol shall specify any and all necessary facts as well as all facts required by the Contracting Parties, in particular the exact time of the takeover of the Subject of the Sub-lease by the Sub-Lessee and the handover of the Subject of the Sub-lease back to the Lessee, its condition, equipment, and the arrangement and layout of the Subject of the Sub-lease pursuant to Annex no. 2 to this Contract. The Handover Protocol shall also include any and all damage to the movables, decorations, structural elements, fittings and other equipment of the catering premises. In such a case, the time of the ascertainment of damage, the damage description and cause as well as the Sub-lessee’s statement regarding the extent and cause of the damage shall be recorded in the Handover Protocol. 2. The names of the persons writing up the Handover Protocol and making any records therein shall be listed in the head thereof. The Handover Protocol shall be signed by the OD Representative on behalf of the Lessee and by the SL Representative on behalf of the Sub-Lessee. In case of a difference of opinion between these persons on any matter, both opinions shall be recorded in the Handover Protocol, however for an urgent resolution of any situation, the stance of the OD Representative shall prevail and the SL Representative undertakes to respect the OD Representative’s instructions.
Sample 1Sample 2
AutoNDA by SimpleDocs
Handover Protocol. The Parties will sign the Handover Protocol after: the Parties prepare a record of the completed Pilot Operation and Penetration Test (if relevant) the Customer checks and confirms the completeness of the updated Documents and the Contractor fulfils the obligation pursuant to sub. 5.5.5. hereof, if applicable. The Handover Protocol will contain a list of the remaining Defects and security issues detected during the Penetration Test with the time period set for removal thereof; in the absence of a written agreement about this time period for defect removal, the time period is assumed to be 14 (fourteen) Business Days from the day of signing of the Handover Protocol.
Sample 1Sample 2
Handover Protocol. The Parties will sign the Handover Protocol after: the Customer checks and confirms the completeness of the updated Documents and the Contractor fulfils the obligation pursuant to sub. 5.5.5. hereof, if applicable. The Handover Protocol will contain a list of the remaining Defects with the time period set for removal thereof; in the absence of a written agreement about this time period for defect removal, the time period is assumed to be 14 (fourteen) Business Days from the day of signing of the Handover Protocol.
Sample 1
Handover Protocol. No. 4 Layout of the Subject of the Sub-lease
Sample 1
Handover Protocol. No. 4 Layout of the Subject of the Sub-lease Signed in Prague on 31.3.2022 Lessee: Sub-lessee: …………………………………………. …………………………………………. Mgr. Xxxxxxxxx Xxxxx Xx. Xxxxxx Xxxxxxxxxx Chairman of the Board of Directors President Obecní dům a.s. Gesellschaft der Xxxxxx des Sanct Georgs Orden …………………………………………… Mgr. Xxx Xxxxxx Vice-chairman of the Board of Directors Obecní dům a.s.
Sample 1
Handover Protocol. Transfer of ownership rights
Sample 1
Handover Protocol. Upon delivery of the Software and the Software documentation, the Parties shall sign a handover protocol confirming that the Software and the Software documentation have been delivered in accordance with the terms of this Agreement („the Handover Protocol“). The Handover Protocol shall include: A reference to this Agreement; Identification of the Parties; What is being delivered; List of the Software documentation and other documentation supplied, if applicable; List of the Software licences acquired as part of the Software (including third party software licences); Any pending items and any defects found which do not prevent acceptance (with date of rectification or date of delivery of pending items); Date and place of delivery and acceptance; Signatures of the representatives of the Licensor and the Licensee. The information required in Articles 13.3 and 13.4. of this Agreement.
Sample 1
AutoNDA by SimpleDocs

Related to Handover Protocol

  • Protocol The attached Protocol shall be an integral part of this Agreement.

  • Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

  • 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 Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • HUB Subcontracting Plan The Owner has adopted Exhibit H, Policy on Utilization of Historically Underutilized Business ("Policy"), which is incorporated herein by reference. Contractor, as a provision of the Agreement must comply with the requirements of the Policy and adhere to the HUB Subcontracting Plan submitted with Contractor's Proposal and attached as Exhibit I. No changes to the HUB Subcontracting Plan can be made by the Contractor without the prior written approval of the Owner in accordance with the Policy.

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