The MAP component Sample Clauses

The MAP component clause defines the requirements and responsibilities related to the use or integration of a Mapping Application Platform (MAP) within the agreement. Typically, this clause outlines how the MAP will be accessed, maintained, or updated, and may specify technical standards, data sharing protocols, or user permissions. By clearly delineating the expectations and obligations regarding the MAP, this clause ensures both parties understand their roles and helps prevent disputes over platform usage or data management.
The MAP component. The Co-ordinating Unit of MAP (MEDU), as the overall Project Co-ordinator, exercises guidance and supervision of the implementation of the Project. PAP/RAC, as the MAP Project Implementing Centre, is responsible for co-ordination, guidance and implementation of the Project, in co-operation with MESPE in its role of the National Focal Point, and with the National Project Co-ordinator. Furthermore, PAP/RAC co-ordinates the activities with other MAP components involved in the Project. Finally, it is responsible for the co-ordination of preparation of final Project documents. In addition, the Project will benefit from the use of the MCSD documents related to individual Project activities. Other MAP components involved in the Project, BP/RAC, SPA/RAC, ERS/RAC and REMPEC, are responsible for the implementation of respective Individual activities, under the logistical co-ordination of PAP/RAC, and in co-operation with relevant national authorities/institutions responsible for the respective activities. MAP professionals and consultants act in accordance with their respective TORs. The area of consultancy needed and the selection of the consultant shall be defined by the Inception Report and agreed by the Aide-Mémoire, to the satisfaction of MESPE, in order to ensure proper use of resources and transparency.
View SourceView Similar (2)
The MAP component. The Co-ordinating Unit of MAP (MEDU) exercises guidance and supervision of the implementation of the Project. PAP/RAC, as the MAP Project Implementing Centre, is responsible for co-ordination, guidance and implementation of the Project, in co-operation with Montenegrin national and local authorities. Furthermore, PAP/RAC co-ordinates the activities with other MAP components involved in the Project with the assistance of the National Project Co-ordinator. Finally, it is responsible for the co-ordination of preparation of the final Project documents. In addition, the Project will benefit from the use of the MCSD, EU and other documents related to individual Project activities. Other MAP components involved in the Project – SPA/RAC, INFO/RAC, CP/RAC and MEDPOL, are responsible for the implementation of respective individual activities, under the logistical co- ordination of PAP/RAC, and in co-operation with the National Project Co-ordinator and relevant national authorities/institutions responsible for the respective activities. MAP professionals and consultants will act in accordance with their respective ToRs. The area of consultancy needed and the selection of the consultant shall be defined in the Inception Report. The Project organisational structure is presented in the Figure 2-3. RACs
View Source
The MAP component. The Co-ordinating Unit of MAP (MEDU), as the overall Project Co-ordinator, will exercise guidance and supervision of the implementation of the Project. PAP/RAC, as the MAP Project Implementing Centre, will be responsible for co-ordination, guidance and implementation of the Project by engaging a national Project Co-ordinator and, in co-operation with the National Project Director in his role as National Focal Point. Furthermore, PAP/RAC, through the National Project Co-ordinator, will co-ordinate the activities with other MAP components involved in the Project and be responsible for the co-ordination of preparation of final Project documents. In addition, the Project will benefit from the inputs of specialised Regional Activity Centres (RACs), such as BP/RAC and SAP/RAC and the use of the MCSD documents related to individual Project activities. The RACs involved in the Project, (BP/RAC and SPA/RAC) will be responsible for the implementation of respective Activities, under the logistical co-ordination of PAP/RAC, through the National Project Co-ordinator, and in co-operation with relevant national authorities/institutions responsible for the respective activities. The area of consultancy needed and the selection of the consultant shall be defined by the Inception Report and agreed by the Aide-Mémoire, to the satisfaction of the National Project Director to ensure proper use of resources and transparency.
View Source

Related to The MAP component

  • Components Patheon will purchase and test all Components (with the exception of Client-Supplied Components) at Patheon’s expense and as required by the Specifications.

  • Third Party Components The Products and Services may contain third party components (including open source software) subject to separate license agreements. To the limited extent a third party license expressly supersedes this ▇▇▇▇, such third party license governs Customer’s use of that third party component.

  • Combination Product The term “

  • Meter Testing Company shall provide at least twenty-four (24) hours' notice to Seller prior to any test it may perform on the revenue meters or metering equipment. Seller shall have the right to have a representative present during each such test. Seller may request, and Company shall perform, if requested, tests in addition to the every fifth-year test and Seller shall pay the cost of such tests. Company may, in its sole discretion, perform tests in addition to the fifth year test and Company shall pay the cost of such tests. If any of the revenue meters or metering equipment is found to be inaccurate at any time, as determined by testing in accordance with this Section 10.2 (Meter Testing), Company shall promptly cause such equipment to be made accurate, and the period of inaccuracy, as well as an estimate for correct meter readings, shall be determined in accordance with Section 10.3 (Corrections).

  • OPEN SOURCE COMPONENTS The DS Offerings may include open source components. Whenever notices (such as acknowledgment, copies of licenses or attribution notice) are required by the original licensor, such notices are included in the Documentation of the DS Offerings. Moreover, some open source components may not be distributed and licensed under the terms of the Agreement but under the terms of their original licenses as set forth in the Documentation of the DS Offerings themselves. Source code for open source software components is available upon request. Except for components mentioned in the section EXCLUSIONS below, the warranty and indemnification provided by DS under the Agreement apply to all open source software components and shall be provided by DS and not by the original licensor, but only for the use of the DS Offerings that is in compliance with the terms of the Agreement, and in conjunction with the DS Offerings. The original licensors of said open source software components provide them on an “as is” basis and without any liability whatsoever to Customer.