Objectives of this deliverable Sample Clauses

Objectives of this deliverable. The present work was conducted from February 2014 to June 2014 within Task 5.1, Access and Presentation Requirements, as part of Work Package 5 on Archival Records Access Services in the E-­‐ARK project. The purpose of this deliverable is to identify and analyse existing solutions for providing access to digital material, study users’ needs and requirements for access services, and carry-­‐out a gap analysis between the two in order to identify gaps that must be bridged by future access services.
Sample 1
AutoNDA by SimpleDocs
Objectives of this deliverable. The aim of this document is to report on the activities performed on WP2 Task 2.6. The goal is to co-work with CompBioMed core partners on the selected HPC codes and report on the implementations of CompBioMed applications on emerging HPC architectures and porting to new and maturing architectures. The first step is to port the applications on Bull HPC platform, run scalability tests, then perform a profiling of the applications to target the most time-consuming function and loops for optimisations. Finally, the deliverable consists of this report and suggestions for improving the performances of the applications.
Sample 1
Objectives of this deliverable. This deliverable details the design process followed for the implementation of a co-created digital toolkit. Specifically, it describes the combination of methods that have been used during the process; such as interviews, benchmarking, and prototyping, among other tools. Overall, this process has been essential to better delineate the needs of targeted groups and to co-create the toolkit with several relevant stakeholders.
Sample 1
Objectives of this deliverable. The specific objectives for Task 6.1 within the DESTINY project are:  Provide a first overview and support understanding of the potential market for DESTINY’s  Identify relevant value-chains and stakeholders  Find relevant technology innovators, competing solutions, similar research and innovation trends  Set up the base to study new business models and developments for DESTINY technology As explained in the next Chapter, in this document the approach is to provide a first necessary step to build a seamless set of analyses and support the partners in analysing a complex framework while proceeding with the R&D developments. STUDY OBJECTIVES OF THIS REPORT ARE
Sample 1
Objectives of this deliverable. The objective of this deliverable is to report on the current state of concept and development of the urban platform integration and interoperability in Dresden demo site (WP3). The Urban Platform (UP) will be in charge of developing a number of services (see also D3.22) to improve city operation, decision-making services, citizen engagement, and to ensure the interaction between the city of Dresden and its citizens. All these developments will follow the same principles: ensuring open / citizen data, interoperability through open API (open Application Programming Interface) developments and assessing the evaluation process by considering the requirements of the Dresden monitoring plan outlined in Task 5.1. The Definition of interoperability test plan for Dresden is established by a harmonised approach among the three demos. Testing of new modules developed under the top of the Dresden Urban Platform ensures that the UP interoperates within those from Valencia and Antalya by following the open API concept in the Urban Platforms of Valencia and Antalya too. Additionally, the interoperability performance must be assessed in order to confirm that the functionality of the new services is preserved. Moreover, security and privacy issues are addressed. The objective of this deliverable is to report on the characteristics that the Urban Platform of Dresden is going to adopt in line with open data strategies, open APIs and data integration requirements. In the context of MAtchUP, the requirements of the Urban Platform must be specified, considering the Dresden demo site actions, interventions and the overall objectives of the project. These have to be carried out within the main chapters of MAtchUP: Mobility, Energy and ICT but also about the Non- Technical Actions facing economic and social aspects as well. Moreover, reference architectures for urban platforms and related European urban projects must also be taken into account. The definition of data models is important, since they are the frames to be followed for data exchange among modules. The fact of having a robust and well-defined data model will maximize the interoperability between the components of the system. Moreover, citywide metadata sets are made available in a catalogue. Finally, security and privacy issues are addressed, with special emphasis in the new European General Data Protection Regulation (GDPR), in order to deal with how security and privacy will be tackled.
Sample 1

Related to Objectives of this deliverable

  • Objectives of this Agreement The objectives of this agreement are as follows:

  • Objectives of Agreement The objectives of this Agreement are to:

  • Objectives and Scope 1. The Parties confirm their joint objective of strengthening their relations by developing their political dialogue and reinforcing their cooperation.

  • OBJECTIVES OF THE AGREEMENT 7.1 The parties agree that key objectives of this agreement are;

  • Copies of this Agreement This Agreement shall be executed in four counterparts; each party holds one and the restare used for the transaction of related formalities. Each of the copies shall be deemed as the original one and has the same effect. [The remainder of this page is intentionally left blank.] Exclusive Purchase Option Agreement

  • Benefits of this Agreement Nothing in this Agreement shall be construed to give to any Person other than the Company, the Rights Agent and the registered holders of the Rights Certificates (and, prior to the Distribution Date, registered holders of the Common Stock) any legal or equitable right, remedy or claim under this Agreement; but this Agreement shall be for the sole and exclusive benefit of the Company, the Rights Agent and the registered holders of the Rights Certificates (and, prior to the Distribution Date, registered holders of the Common Stock).

  • Deliverables Upon satisfactory completion of the work authorization, the Engineer shall submit the deliverables as specified in the executed work authorization to the State for review and acceptance.

  • SERVICES & DELIVERABLES Seller agrees to perform the services ("Services") and/or provide the goods ("Goods", which term shall include goods provided as part of any Services), described in any PO, in accordance with the applicable PO and with this Agreement. Acceptance of a PO and this Agreement shall occur (i) within five (5) days of receipt by the Seller; or, (ii) upon shipment of Goods; or, (iii) upon commencement of a Service, (whichever is the earlier). Seller shall be bound by the provisions of this Agreement, including all provisions set forth on the face of any applicable PO, whether Seller acknowledges or otherwise signs this Agreement or the PO, unless Seller objects to such terms in writing within five (5) days of receiving the Agreement and/or the PO, prior to shipping Goods or prior to commencing Services. This writing does not constitute a firm offer and may be revoked at any time prior to acceptance. This Agreement may not be added to, modified, superseded, or otherwise altered, except by a writing signed by an authorized Apple representative and specifically stated to be an amendment of this Agreement. Any terms or conditions contained in any acknowledgment, invoice, or other communication of Seller which are inconsistent with the terms and conditions of this Agreement, are hereby rejected. To the extent that this Agreement might be treated as an acceptance of Seller's prior offer, such acceptance is expressly made on condition of assent by Seller to the terms hereof and shipment of the Goods or beginning performance of any Services by Seller shall constitute such acceptance. Apple hereby reserves the right to reschedule any delivery or cancel any PO issued at any time prior to shipment of the Goods or prior to commencement of any Services. Apple shall not be subject to any charges or other fees as a result of such cancellation.

  • SCOPE OF THIS AGREEMENT 2.1. This Agreement, including Parts A through L, Tables One and Two and exhibits, specifies the rights and obligations of each Party with respect to the establishment, purchase, and sale of Local Interconnection, Collocation, resale of Telecommunications Services and Unbundled Network Elements. Certain terms used in this Agreement shall have the meanings defined in PART A – DEFINITIONS, or as otherwise elsewhere defined throughout this Agreement. Other terms used but not defined in this Agreement will have the meanings ascribed to them in the Act and in the FCC’s and the Commission’s rules, regulations and orders. PART B sets forth the general terms and conditions governing this Agreement. The remaining Parts set forth, among other things, descriptions of the services, pricing, technical and business requirements, and physical and network security requirements.

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

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