Issue Date Comment Author Sample Clauses

Issue Date Comment Author. FINAL 21/11/2020 Agreed OLA with the provider till 10/2021 Xxxxxxxx Xx Xxxxx TERMINOLOGY The EGI glossary of terms is available at: xxxxx://xxxx.xxx.xx/wiki/Glossary For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Contents
AutoNDA by SimpleDocs
Issue Date Comment Author. FINAL 01/04/2021 OLA agreed with the Component Provider Xxxxxxxx Xx Xxxxx Xxx Xxxx TERMINOLOGY The EGI glossary of terms is available at: xxxxx://xxxx.xxx.xx/wiki/Glossary For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Contents The Services 4 Service hours and exceptions 6 Support 6 Incident handling 6 Service requests 6 Service level targets 6 Limitations and constraints 6 Communication, reporting and escalation 7 General communication 7 Regular reporting 7 Violations 7 Escalation and complaints 7 Information security and data protection 8 Responsibilities 8 Of the Component Provider 8 Of EGI Foundation 8 Of the Customer 8 Review, extensions and termination 9 The present Operational Level Agreement (“the Agreement’) is made between EGI Foundation (the Service Provider) and IN2P3-IRES (the Component Provider) to define the provision and support of the provided services as described hereafter. Representatives and contact information are defined in Section 6. OPERAS tackles the challenge of renewing scholarly communication practices in the context of Open Science. Its scope is on the SSH with a multidisciplinary perspective. OPERAS aims at opening the locks that prevent the sector from upgrading its practices and integrating with the Open Science principles. As a distributed research infrastructure, OPERAS will take a central position in the ecosystem of scholarly communication for SSH in Europe by coordinating the involved stakeholders. OPERAS will ensure effective dissemination and global access to research results, develop robust services that will directly enhance research outputs, offer open access to high quality content to facilitate research, and improve the scholarly communication infrastructure by sharing technologies and knowledge. OPERAS will monitor innovative scholarly practices and expectations of the scholarly community, allowing to rise up to the new ways in which research is conducted. The Customer is a consortium represented by the OPERAS AISBL. This Agreement is valid from 01/04/2021 to 30/06/2023. Once approved, this Agreement is automatically renewed, as long as the Component Provider does not express a decision to terminate the Agreement at least a month before the end date of the Agreement. The Agreement was discu...
Issue Date Comment Author. FINAL 08/06/2021 OLA agreed with the Component Provider Xxxxxxxxxx Xxxxxxxxx Xxxxxxxx Xx Xxxxx v0.2 06/12/2021 Extended agreement with the Component Provider till 12/2022 Xxxxxxxx Xx Xxxxx v0.3 11/01/2022 Updated the OLA template (v2.13) Xxxxxxxx Xx Xxxxx TERMINOLOGY The EGI glossary of terms is available at: xxxxx://xxxx.xxx.xx/wiki/Glossary For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Contents The Services 5 Service hours and exceptions 9 Support 9 Incident handling 9 Service requests 10 Service level targets 10 Limitations and constraints 10 Communication, reporting and escalation 10 General communication 10 Regular reporting 11 Violations 11 Escalation and complaints 11 Information security and data protection 12 Responsibilities 13 Of the Component Provider 13 Of EGI Foundation 13 Of the Customer 14 Review, extensions and termination 14 References 14 The present Operational Level Agreement (“the Agreement”) is made between EGI Foundation (the Service Provider) and GSI-LCG2 (the Component Provider) to define the provision and support of the provided services as described hereafter. Representatives and contact information are defined in Section 6. The EGI Applications on Demand (AoD)1 service allows user-friendly access to a portfolio of scientific applications and application hosting frameworks (Science Gateways, VREs) that are configured to use the dedicated pool of cloud computing and HTC clusters from EGI. The service also allows users to run their own simulation/analysis models with custom input data. The service operates as an open and extensible ‘hub’ for providers and e-infrastructure user support teams who wish to federate and share applications and services with individual researchers, or small, fragmented communities, typically referred to as ‘the long tail of science’. The User is a consortium represented by the EGI Foundation. This Agreement is valid from 01/06/2021 to 31/12/2022. Once approved, this Agreement is automatically renewed, as long as the Component Provider does not express a decision to terminate the Agreement at least a month before the end date of the Agreement. The Agreement was discussed and approved by the EGI Foundation and the Component Provider on
Issue Date Comment Author. FINAL 19/08/2016 OLA signed with the provider Xxxxxxxxxx Xxxxxxxxx Xxxxxxxx Xx Xxxxx v2 03/11/2017 OLA extended with the provider until 12/2018 Xxxxxxxx Xx Xxxxx v3 19/12/2018 OLA extended with the provider until 12/2019 Xxxxxxxx Xx Xxxxx v4 22/11/2019 OLA extended with the provider until 12/2020 Xxxxxxxx Xx Xxxxx TERMINOLOGY The EGI glossary of terms is available at: xxxxx://xxxx.xxx.xx/wiki/Glossary For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Contents
Issue Date Comment Author. FINAL 13/09/2016 OLA signed with the provider Xxxxxxxxxx Xxxxxxxxx Xxxxxxxx Xx Xxxxx v2 10/11/2017 Extended OLA with the provider till 01/2019 Xxxxxxxx Xx Xxxxx v3 19/12/2018 Extended OLA with the provider till 01/2020 Xxxxxxxx Xx Xxxxx v4 22/11/2019 Extended OLA with the provider till 01/2021 Xxxxxxxx Xx Xxxxx v5 12/01/2021 Extended OLA with the provider till 06/2023 Xxx Xxxx v6 18/01/2022 Update OLA template Xxx Xxxx v7 07/02/2023 Update OLA template Xxx Xxxx v8 01/07/2023 Extended OLA with the provider till 06/2024 Xxx Xxxx TERMINOLOGY The EGI glossary of terms is available at: xxxxx://xx.xxx.xx/glossary For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Contents
Issue Date Comment Author. FINAL 19/11/2019 OLA agreed with the provider Xxxxxxxxxx Xxxxxxxxx Xxxxxxxx Xx Xxxxx v0.2 08/09/2020 Extended agreement till 03/2021 (new EOSC-hub project end) Xxxxxxxx Xx Xxxxx v0.3 26/03/2021 Extended agreement till 06/2023 Xxxxxxxx Xx Xxxxx TERMINOLOGY The EGI glossary of terms is available at: xxxxx://xxxx.xxx.xx/wiki/Glossary For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Contents
Issue Date Comment Author. FINAL 26/10/2018 SLA agreed with the Customer Xxxxxxxx Xx Xxxxx Xxxxxxxxxx Xxxxxxxxx TERMINOLOGY The EGI glossary of terms is available at: xxxxx://xxxx.xxx.xx/wiki/Glossary For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Contents
AutoNDA by SimpleDocs
Issue Date Comment Author. FINAL 07/06/2016 OLA signed with the provider Xxxxxxxxxx Xxxxxxxxx Xxxxxxxx Xx Xxxxx v2 13/11/2017 OLA updated until 01/2019 Xxxxxxxx Xx Xxxxx TERMINOLOGY The EGI glossary of terms is available at: xxxxx://xxxx.xxx.xx/wiki/Glossary For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Contents
Issue Date Comment Author. FINAL 13/12/2016 SLA agreed with the Customer Xxxxxxxx Xx Xxxxx Xxxxxxxxxx Xxxxxxxxx V0.1 10/05/2018 Extension of the agreement till 01/01/2019 Xxxxxxxx Xx Xxxxx TERMINOLOGY The EGI glossary of terms is available at: xxxxx://xxxx.xxx.xx/wiki/Glossary For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Contents
Issue Date Comment Author. FINAL 31/01/2021 Agreed SLA with the Customer Xxxxxxxx Xx Xxxxx/EGI Foundation v0.2 16/07/2021 Added a statement to clarify that the unused budget during the service reporting period will be freed. Xxxxxxxx Xx Xxxxx/EGI Foundation v0.3 01/04/2022 Added P4U OLA with IFCA to provide GPU access. Added DataHub for dedicated space for the model repository. Added EGI Check-In. Xxxxxxxxx Xxxx-Xxxxxx, Xxxxxx Xxxxx Xxxxx. TERMINOLOGY The EGI glossary of terms is available at: xxxxx://xxxx.xxx.xx/wiki/Glossary For the purpose of this Agreement, the following terms and definitions apply. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. Contents The Services 4 Service hours and exceptions 6 Support 7 Incident handling 7 Service requests 8 Service level targets 8 Limitations and constraints 8 Communication, reporting and escalation 9 General communication 9 Regular reporting 10 Violations 10 Escalation and complaints 11 Information security and data protection 11 Responsibilities 11 Of EGI Foundation 11 Of the Customer 12 Finance and administration 12 9.1 Service Offers 12 9.2 Invoicing and Payment Schedule 13 Review, extensions and termination 13 The present Service Level Agreement (“the Agreement’) is made between EGI Foundation (the Service Provider) and DIGITbrain/xx.xxxxxxxxxx.xx (the Customer) to define the provision and support of the provided services as described hereafter. Representatives and contact information are defined in Section 6. DIGITbrain1 is an EU innovation program to give SMEs easy access to digital twins. A Digital Twin is a computer-based application/simulation that mimics the real production line of a company and runs in parallel with the real manufacturing process. Using this Digital Twin, companies can rationalise the manufacturing process, make predictions regarding expected machine failures and can predict maintenance needs. The Customer is a consortium represented by PNOConsultant. This Agreement is valid from 01/01/2021 to 31/12/2023. The Component Provider will guarantee the availability of the platform for a maximum of 90 days from the end of the agreement, or until the final DIGITbrain review takes place (with no additional costs). In order to review the terms and conditions for a possible additional extension, a check-point will take place 3 months before the end of this agreement. The Agree...
Time is Money Join Law Insider Premium to draft better contracts faster.