dokumendiregister.ee
OtsingAsutusedMCP
Otsing›Tervise- ja heaolu infosüsteemide keskus
Muu lepingAvalik

Leping

Tervise- ja heaolu infosüsteemide keskus · 28. detsember 2020
Viit
3-9/2508-3
Registreeritud
28. detsember 2020
Dokumendi liik
Muu leping
Funktsioon
3 Finantsarvestus ja asutuse varade haldus
Sari
3-9 Riigihankelepingud
Toimik
3-9/2020
Vastutaja
Jaak Vaabel (TEHIK, Üldosakond, Õigustalitus)

Failid

  • 📎Maintenance agreement TEHIK.asice667 KB

Sisu (failidest)

Annex 3 Support Plan for SAP Enterprise Support 1. SAP Support Model for SAP Enterprise Support multi-step upgrade to a target Release in mainstream maintenance. 1.1. Under the SAP Support Model for SAP Enterprise - The Supplier shall make available to or provide the Support: Customer with new Releases and Correction Packages of the Software without undue delay after - The Supplier is the primary support provider for they become available from SAP for delivery to end Software and all contacts relating to Support Services users. The Customer acknowledges and agrees that are to be addressed to the Supplier. some updates may be subject to a separate charge - The Supplier will receive Incidents from the and/or may require upgrades in the Customer’s Customer’s helpdesk which is responsible for operating systems, databases or other middleware Incident Root Cause Analysis. The Customer may components. subcontract the Customer helpdesk to the Supplier, - Support Packages - Correction Packages to reduce the pursuant to a separate agreement. effort of implementing single corrections as released - In the event that the Incident has not been solved in by SAP. Support Packages may also contain the First and Second Level Support for Software corrections to adapt existing functionality to changed (including Third Party Software/Products) as defined legal and regulatory requirements, for example in the in Clause 5 below the Supplier shall forward the area of human resources. Incident to SAP with respect to Third Level Support - For Releases of SAP Business Suite 7 core (Development Support). The Customer agrees that to applications, (starting with SAP ERP 6.0 and with the extent that Software contains Third Party Releases of SAP CRM 7.0, SAP SCM 7.0, SAP SRM Software/Products, SAP requires the support of the 7.0 and SAP PLM 7.0 shipped in 2008), enhanced vendor of the Third Party Software/Products to functionality and/or innovation is provided through provide Third Level Support. Enhancement packages or by other means as - SAP will, in addition to priority 1 (“very high”) available. messages, receive vital alerts reported by SAP - Technology updates to support third-party operating EarlyWatch® Alert and Top-Issues from the systems and databases. Details on SAP’s release Supplier. strategy and recommendations for technology - The Supplier will examine vital alerts reported by SAP updates for SAP’s enhancement packages are outlined EarlyWatch® Alert and work to resolve Top-Issues on the SAP Support Portal. directly with the Customer. The Supplier will forward - Available Software change management, such as critical reports to SAP if any. SAP EarlyWatch® Alert changed configuration settings or Enterprise Support for SAP Business Objects branded products is Solution upgrades, is extensively supported. For currently only available if the Customer’s Software example with content and information material, tools also comprises of SAP Business All-In-One (see SAP for client copy and entity copy, and tools for Note 1393207). comparing and synchronizing of customizing. - Incidents related to Software and Third Party - Configuration guidelines and content for Enterprise Software/Products with priority 1 (“Very High”) shall Support Solutions is usually shipped via SAP Solution be submitted in English. Manager Enterprise Edition. - Best practices for SAP System Administration and 2. Scope of SAP Enterprise Support SAP Solution Operations for Enterprise Support Solutions are provided. Details are outlined on the 2.1. This Clause describes the standard services which the SAP Support Portal. Customer receives (depending on the maintenance phase; - SAP configuration and operation content is please see Clause 3.1 and 3.2 below) via/from the supported as integral part of Enterprise Support Supplier and from SAP under SAP Enterprise Support. Solutions The full scope of SAP Enterprise Support includes at - Content, tools and process descriptions for SAP current the elements described below. Lifecycle Management are part of the SAP Solution Manager Enterprise Edition, the Enterprise Support 2.2. Continuous Improvement and Innovation Solutions and/or the applicable documentation for the Software Enterprise Support Solutions. - New Software Releases of the licensed Software as well as tools and procedures for upgrades. Upgrades 2.3. Global Support Backbone to new Releases are supported in mainstream maintenance. Upgrades to new Releases are not - SAP Support Portal - SAP's knowledge database and supported in extended or customer-specific SAP’s extranet for knowledge transfer on which SAP maintenance, unless this is necessary as one step in a makes available content and services to end users (including the Customer) of SAP only. Annex 3 Maintenance Agreement Estonia v1.3 20180628 1/8 - SAP Notes on the SAP Support Portal document - Content and supplementary tools designed to help software errors and contain information on how to increase efficiency, which may include remedy, avoid and bypass these errors. SAP Notes implementation methodologies and standard may contain coding corrections that the Customer procedures, an Implementation Guide (IMG) and can implement into its SAP system. SAP Notes also Business Configuration (BC) Sets. document other problems or end user questions and - Access to guidelines via SAP Support Portal, which recommended solutions (e.g. customizing settings). may include implementation and operations best - SAP Note Assistant - a tool to install specific practices, processes and other content designed to corrections and improvements to SAP components. help reduce costs and risks. Such content currently - SAP Solution Manager Enterprise Edition shall be includes: used in accordance with the terms and conditions of o End-to-End Solution Operations: Assists the this Agreement (including its Annexes). Customer with the optimization of the end-to- end operations of the Customer’s SAP Software 2.4. Mission Critical Solution Support Solution. o Run SAP Methodology: Assists the Customer - Technical Quality Checks as described in Clause 9 with application management, business process below. Advanced remote services for technical operations, and administration of the SAP problems to follow-up on vital alerts reported by SAP NetWeaver® technology platform, and EarlyWatch® Alert and Top-Issues, as applicable. currently includes: - If not otherwise agreed in Annex 1, the Supplier will ▪ The SAP standards for solution operations activate SAP EarlyWatch® Alert as a mandatory part ▪ The roadmap of Run SAP to implement of SAP Enterprise Support. The Customer shall end-to-end solution operations confirm the activation process of SAP EarlyWatch® ▪ Tools, including the SAP Solution Manager Alert to the Supplier. application management solution - Access to global message handling through SAP for ▪ Additional information on the Run SAP Software Incidents with priority 1 (“very high”). methodology is published on the SAP - Access to global 24x7 Root Cause Analysis Support Portal (“production down support”) and escalation (http://service.sap.com/runsap) procedures to get access to resources available to - Participation in SAP's end user and partner provide a solution to severe problems, in accordance community (via SAP Support Portal), which with Clauses 5 and 6 below. provides information about best business practices, service offerings, etc. 2.5. Other Components, Methodologies, Content and - The Supplier and the Customer shall jointly enter Community Participation into a continuous service and action planning process for the Enterprise Support Solutions of the - Monitoring components and agents for systems. Such Customer. This process shall focus on the components and agents are designed to monitor identification of special events (i.e. project planning, available resources and collect system status implementation, Go-Live, ongoing operations etc.) information of the Enterprise Support Solutions (e.g. during the lifecycle of the SAP Enterprise Support SAP EarlyWatch® Alert). Solutions of the Customer, with the goal to mitigate - Pre-configured software solution test templates and potential risk for the Customer. software solution test cases. Such test templates and test cases are usually delivered via the SAP Solution 3. Limitations Manager Enterprise Edition. In addition the SAP Solution Manager Enterprise Edition assists the 3.1. SAP Enterprise Support is only provided for Software in Customer’s testing activities with functionalities accordance with the then applicable maintenance phases that currently includes: per Software Release as currently outlined on the SAP o Test administration for Software by using the Support Portal (http://service.sap.com/releasestrategy). functionality provided as part of the SAP Solution Manager Enterprise Edition 3.2. The scope of services based on the SAP Enterprise o Quality Management for management of Support offering (as outlined in Clause 2 above) depends „Quality-Gates“ on the respective maintenance phase for the Software o SAP-provided tools for automatic testing Release. SAP and accordingly the Supplier will only o SAP provided tools to assist with optimizing provide the full scope of SAP Enterprise Support during regression test scope. Such tools support the first maintenance phase, so called “Mainstream identifying the business processes that are Maintenance”. After expiration of the Mainstream affected by a planned SAP Software Solutions Maintenance, SAP and accordingly the Supplier may offer change and make recommendations for the test different services. For up-to-date release planning scope as well as generating test plans (details are information and further information on services published on SAP Support Portal). information is provided at the Product Availability Matrix (PAM) at http://service.sap.com/pam. Annex 3 Maintenance Agreement Estonia v1.3 20180628 2/8 3.3. The Supplier or SAP does not support operating systems, 4. Technical requirements databases and other third-party components, which have run out of support by their suppliers/vendors. The 4.1. The Customer must ensure that it has necessary Customer may therefore have to upgrade to newer communications connections between the Supplier and versions of such operating system, databases and other the Customer as well as between SAP and the set up for third-party components that are supported for Enterprise remote support to be provided efficiently by the Supplier Support Solutions. The Supplier and/or SAP are only and/or SAP. The communications connections shall be able to support third party operating systems, databases operable at all times and allow satisfactory response and other third-party components if and to the extent the times. The Customer may have to obtain a separate respective supplier/vendor offers an extension of license for relevant software if appropriate and required support for its product. If this extension is defined as for satisfactory remote support. chargeable by the vendor, Supplier may offer the extension of support for products of these vendors if 4.2. The hardware and software of the Customer must at least licensed via Supplier. Pricing is available upon request meet the list of requirements published on SAP Support (details on vendor/supplier offerings will be published on Portal. SAP Support Portal at http://service.sap.com/maintenance). 4.3. In particular, the following technical requirements are mandatory: 3.4. SAP Enterprise Support is provided for the Customer only if all of the Customer’s installations of Software - Telecommunications infrastructure belonging to the same SAP product family are covered by o Fast Internet connection (minimum asymmetric the SAP Enterprise Support. digital subscriber line (ADSL) standard, greater bandwidth recommended) 3.5. Failure to use the maintenance services provided by the o Telephone system Supplier and SAP such as SAP Technical Quality Checks o Other support related IT components from SAP and SAP EarlyWatch® Alert for the Customer can result namely the remote support component in the case in a situation where the Supplier or SAP is unable to of the Customer using only SAP BusinessObjects identify potential problems and provide support in products eliminating those problems. This, in turn, might result in unsatisfactory software performance for which the 4.4. In case the Customer has more than one support delivery Supplier and/or SAP accepts no responsibility. model (e.g. support delivered directly by SAP and support delivered by the Supplier) within one solution area, the 3.6. Support Services will not be provided in the event that: Customer must run the different support delivery model a. an Incident arises because the Customer or a third on a separate technical installation from the one(s) already party other than SAP has altered or modified the in place for the existing support delivery model. Software without authorization from SAP or the Supplier; 4.5. The Customer shall b. the Customer is in breach of the License Agreement; a. use only a SAP supported Release of the Software; c. a problem arises in connection with the use of non- b. cooperate fully with the Supplier’s and SAP’s SAP products which were not licensed through SAP personnel in the diagnosis of any Incident and/or the as part of the Software; error or defect in the Software or the applicable d. an Incident is in the Customer’s area of responsibility Documentation; and and result, for example, from lack of or incorrect c. make available to the Supplier and SAP free of charge business design, incorrect operation or faulty all information, facilities and services reasonably hardware; required by the Supplier or SAP to enable the Supplier e. the Software is used on any computer system other or SAP to perform the Support Services. than a Designated Unit; f. the Designated Unit is not specified in the applicable 4.6. A remote setup service (“Initial Assessment”) for the documentation as certified to be compatible; or Enterprise Support Solutions of the Customer based on g. the Software is used on hardware or software that SAP standards and documentation shall be performed by does not meet the requirements published on SAP the Supplier and the Customer. The Customer must Support Portal. correctly implement all the recommendations of the setup service classified as mandatory. The data collected 3.7. The Supplier shall not provide Support Services for Third during the setup Service Session shall be validated once Party Products for which the Customer has not obtained every year by the Customer and the Supplier. a license as part of the Software. The Supplier shall not provide any functional training concerning Third Party Software/Product Annex 3 Maintenance Agreement Estonia v1.3 20180628 3/8 5. Incident Processing cannot be carried out. For example, it could be a function that is not available from time to time or that 5.1. Unless otherwise agreed in Annex 1, the Customer shall does not work as it should. have a helpdesk with qualified technical contact persons - Low – If a business process of the Customer is not that will be responsible for Root Cause Analysis and shall affected, the Incident must be assigned priority Low. report Incidents to the Supplier. For possible For example, it could be a function that is not communication directly with SAP at least one of the available from time to time or that does not work as contact persons in the help desk shall be English it should but that is not necessary for daily business. speaking. 5.8. First Level Support provided by the Supplier covers the 5.2. The Customer’s helpdesk shall report an Incident to the reception of all Incidents from the Customer and includes Supplier a) in the Supplier’s SAP Solution Manager the following tasks: Enterprise Edition or b) using the supplier’s Support Services contact information as set forth in Annex 1. The - Accepting the Incident Supplier may update the Support Services contacts - Incidents related to Software and Third Party information by providing a prior written notification Software/Products that are forwarded directly thereof to the Customer. through the SAP Support Network to SAP must be written in English. 5.3. When Incidents are reported, the Supplier will provide - Completing the problem description. Getting missing support to the Customer during Local Office Time by data and information from the Customer, if providing information on how to remedy, avoid and necessary. bypass errors. This applies to all types of the Software - Checking priority of Incidents resold by the Supplier to the Customer: SAP Software - Searching for available technical notes or previous and Third Party Software/Products. 24/7 service shall be customer Incidents that reported a similar/identical available for Priority 1 (“Very High”) Incidents as set issue or other sources of information and assigning forth in Clause 6 below. the available technical notes or information to the Incident. 5.4. The Customer can send an error message at any time of day or night, every day of the week using email or the 5.9. Second Level Support provided by the Supplier is Suppliers online service. The Customer can contact the subsequent to First Level Support and includes the Supplier also by telephone during the Local Office Time. following tasks: 5.5. Unless otherwise agreed in Annex 1 the Customer shall - Searching for errors using the data provided by the ensure at all times that it has established a remote Customer. connection which meets the technical specifications set - Analyzing the Incident’s specific technical data and forth in this Support Plan and as may be published on the document the progress in the Incident. SAP Support Portal. - Discussing the problem with the Customer. If necessary, remote connection to the Customer’s 5.6. When sending the Supplier an Incident message, the system. content of the Incident must be clearly expressed and - Reproducing and isolating the Incident necessary information for its evaluation provided. - Deciding if the Incident is due to a defective or a non- defective cause. 5.7. When the Incident is reported the priority of the Incident o Propose appropriate system configuration or shall be chosen by the Customer according to the workaround if the cause for the Incident is non- following definitions (SAP Note 67739): defective. o Forward Incident to Third Level Support if the - Very high – The Incident may only be assigned cause for the Incident is a Software impairment or priority Very high if an important business process of fault and if no note is available to solve the the Customer cannot be carried out. It could be a Incident. production shutdown or the stoppage of a core - Continually documenting the solution approach. business process in the SAP system. This category - Testing the solution may only be used for Customer Production Systems. o The solution must first be checked and tested in a - High – The Incident may only be assigned priority test system. High if an important business process of the o Backing up all relevant data before the solution is Customer is seriously affected. That means, necessary installed. key activities cannot be carried out. It could be an o Working with the Customer to check and test the urgently required function that is not available from solution in the Customer Production System. time to time or that does not work as it should. - Communicating the solution to the Customer - Medium – If another business process of the o If necessary, the solution will be provided to the Customer is affected, the Incident may be assigned Customer by telephone. priority Medium. That means, necessary activities Annex 3 Maintenance Agreement Estonia v1.3 20180628 4/8 - Summarizing status of Incident before forwarding to The Customer acknowledges that to the extent the cause Third Level Support. of the defect in the Incident indicates a previously unknown problem with the Software coding, the Supplier 5.10. “Third Level Support” (or “Development Support”) will forward the Incident to SAP for Third Level Support related to Software provided by SAP and/or by a Third as defined in Clause 5.10 above and that the 24/7 service Party Vendor related to Third Party Software/Products for the Priority 1 “very high” Incidents may in certain provided under this Agreement shall include the events be provided also directly through SAP. following tasks: 6.2. “Initial Response Time” means that the Supplier, or in - Receiving Incident via SAP Support Network with the event of Priority 1 “very high” Incident, the Supplier the help of the Supplier's SAP Solution Manager or SAP, will confirm receipt of an Incident and provide Enterprise Edition, if applicable. the Customer with an initial qualified response. - Analyzing in detail recorded traces and error messages forwarded to the Customer. 6.3. “Maximum Processing Time” means the amount of time - Creating or modifying existing SAP Notes regarding: used by the Supplier for the processing of a Priority 1 o The identified cause of the defect. “very high” Incident in total and with respect to an o The process of the Incident Remedy with all Incident with any other priority the time used by the requested information and material (e.g. bug fixes, Supplier for the processing of such a Priority 2-4 Incident patches, description of workarounds) to update before forwarding it to SAP if required. SAP’s support system. - Specifying expected duration to fix defects by 6.4. The Maximum Processing Time refers only to that part patches, bug fixes or Support Packages. of the processing time, when the Incident is being - Recommending workarounds. processed by the Supplier (“Processing Time”). The - Accessing the Customer’s systems via SAP Support Processing Time does not include the time, when the Network or, if applicable, the connection provided by Incident is being processed by any other party including the Customer: but not limited the time when the Incident is on status o To analyze the Customer’s system regarding the “Supplier Proposed Solution”, “SAP Action”, “Customer Incident. Action” or “SAP Proposed Solution”, whereas: o To assist the Customer in order to perform the - the status “Supplier Proposed Solution” means the required and applicable Incident Remedy by using Supplier has provided a solution or a workaround for workaround recommendations or fixes. the Incident to the Customer without forwarding the - To change coding, provide fixes and create patches. Incident to SAP for Third Level Support; - the status “SAP Action” means that the Supplier has 5.11. Whenever an Incident is forwarded to the next support forwarded the Incident to SAP for Third Level level as defined in this Clause 5, the Customer will be Support (including also the event that SAP has notified. handed the Incident over to a technology or software partner of SAP or a third party vendor of SAP outside 6. Initial Response Times and Maximum Processing the SAP organization for further processing); Times - the status “Customer Action” means the Incident has been handed over to the Customer for actions; and 6.1. The following Initial Response Times and Maximum - the status “SAP Proposed Solution” means the Processing Times will be applied to the Supplier’s Supplier has received from SAP a solution, a communication with the Customer: workaround or an action plan for an Incident that was forwarded to SAP for Third Level Support and has Priority of Initial Response Maximum provided it or information thereof to the Customer or Incident Time Processing SAP has provided such a solution, workaround or Time action plan to the Customer directly. 1 = very high 1 hour 4 hours (7*24 h) (7*24 h) 6.5. When calculating the Initial Response Time and the Maximum Processing Time the time used by the Supplier 2 = high 4 working hours 2 working days for the initial response to or processing of a Priority 1 before forwarding “very high” Incident is measured in real time, regardless to SAP if required of Local Office Time. For Incidents with any other 3 = medium 8 working hours 4 working days before forwarding priority, the time used by the Supplier for the initial to SAP if required response to or processing of the Incident is measured in 4 = low 16 working hours 8 working days working hours during the Supplier’s Local Office Time. before forwarding to SAP if required 6.6. For priority 1 (“very high”) Incidents the Maximum Processing Time shall be deemed to be met upon the The time frames as specified in the table above shall earliest of the following events: commence upon receipt of the Incident by the Supplier. Annex 3 Maintenance Agreement Estonia v1.3 20180628 5/8 a. the Supplier proposes a solution or a workaround to - Incidents are related to Releases of Software which the Customer without forwarding the Incident to have been released by SAP under the Unrestricted SAP for Third Level Support (status “Supplier Shipment status Proposed Solution”); - Incidents are related to a Software Release which is b. the Supplier provides the Customer a solution or a under Mainstream Maintenance or Extended workaround received from SAP for an Incident Maintenance as defined in forwarded to SAP for Third Level Support or SAP http://service.sap.com/releasestrategy; and provides such a solution or workaround to the - The support tools required by SAP for the analysis of Customer directly (status “SAP Proposed Solution”); certain types of Incidents and available for the SAP c. the Supplier informs the Customer of an action plan support (e.g. currently SAP Solution Manager received from SAP for an Incident which has been Diagnostics for Java-related Incidents) are forwarded to SAP for Third Level Support or SAP implemented by the Customer. A list of the required provides such an action plan to the Customer directly support tools to be installed is published on the SAP (status “SAP Proposed Solution”); or Support Portal. d. the Customer agrees to reduce the priority of the Incident; 6.11. For priority 1 (“very high”) Incidents, the following provided that the total amount of Processing Time used prerequisites have to be fulfilled: by the Supplier for the processing of the Incident in - The Supplier, subject to acceptance of SAP, accepts question does not exceed the Maximum Processing Time the Incident as being priority 1 (“very high”). defined for the Priority 1 (“very high”) Incident in the - Incidents are generated by the Customer in English schedule set forth in Clause 6.1 above. - The issue and its business impact have to be described in detail. 6.7. For Incidents with any other priority than Priority 1 - An English-speaking contact is provided by the (“very high”) the Maximum Processing Time shall be Customer. deemed to be met upon the earliest of the following - A contact person must be nominated for opening the events: remote connection to the system and to provide the a. the Supplier proposes a solution or a workaround to necessary log-on data. the Customer without forwarding the Incident to SAP for Third Level Support (status “Supplier 6.12. The following types of priority 1 (“very high”) Incidents Proposed Solution”); or are excluded from the Initial Response Time and b. the Supplier forwards an Incident to SAP for Third Maximum Processing Time, in case of priority 1 (“very Level Support whether by SAP or a Third Party high”): Vendor as set forth in Clause 5.10 above (status “SAP - Message regarding a Release, version and/or Action”); functionalities of Software developed specifically for provided that the total amount of Processing Time used the Customer including those developed by SAP SE’s by the Supplier for the processing of the Incident in Custom Development and/or by SAP SE’s question does not exceed the Maximum Processing Time subsidiaries, except for Supplier Custom Code defined for the priority level of the Incident in the developed with the SAP development workbench. schedule set forth in Clause 6.1 above. - Messages regarding country versions that are not part of the Software and instead are realized as Supplier 6.8. The Supplier will inform the Customer of a possible add-ons, Enhancements, or Modifications are action plan provided by SAP. Such information shall expressly excluded even if these country versions include descriptions of: were created by SAP or an associated organization. - the status of the resolution process; - The root-cause behind the message is not a - the next steps planned by SAP and the responsible malfunction, but a missing functionality persons allocated by SAP; (“development request”) or the message is ascribed to - required cooperation by the Customer a consulting request (as per SAP Note 83020). - date and time for the next status update from SAP; - The Release has entered the phase for “customer- - due dates for actions taken by SAP, to the extent specific” maintenance. possible. 6.9. The Supplier will provide to the Customer regular status 7. SAP Solution Manager Enterprise Edition updates on the processing of priority 1 (“very high”) Incidents as provided by SAP to the Supplier which 7.1. Unless otherwise agreed in Annex 1 the Supplier and SAP include: will use the SAP Support Network including SAP - results of actions undertaken so far Solution Manager Enterprise Edition for all Support - next steps planned Services, including but not limited to receiving Incidents - date and time for next status update. and Incident Remedies, Incident processing, application management and for all communication between the 6.10. The Initial Response Times and the Maximum Processing Supplier, SAP and the Customer. Times shall only apply if the following conditions are met: Annex 3 Maintenance Agreement Estonia v1.3 20180628 6/8 7.2. Should the Customer want to operate its own SAP - non-IT shared services capabilities, including without Solution Manager Enterprise Edition it may be granted a limitation HR, finance or procurement. license to use the SAP Solution Manager Enterprise Edition in accordance with the usage terms and scope 7.6. The Customer shall acknowledge and accept the stipulated in this Annex 3, the License Agreement and provisions of the SAP Solution Manager Enterprise the EULA, however the terms of this Annex 3 shall Edition Software usage rights by means of ordering or prevail. downloading the Software. The Customer may not transfer its possible usage rights to the SAP Solution 7.3. If the Customer has been granted usage rights for the Manager Enterprise Edition to any third party. All rights SAP Solution Manager Enterprise Edition subject to the to the SAP Solution Manager Enterprise Edition and conditions contained in this Clause 7 the SAP Solution associated services are owned by SAP. Manager Enterprise Edition may be used by the Supplier and the Customer solely for the following purposes: 7.7. The Customer’s usage rights to the SAP Solution - delivery of SAP Enterprise Support and Support Manager Enterprise Edition shall terminate upon the Services for Customer solutions including delivery earlier of: and installation of software and technology - termination of the reselling agreement between SAP maintenance for Enterprise Support Solutions; and and the Supplier; - application lifecycle management for Customer - termination of the support agreement between the Solutions and for any other software components and Supplier and the Customer; or IT assets licensed or otherwise obtained by the - termination of the support agreement between the Customer from third parties provided such third party Supplier and SAP with regards to the Customer. software, software components and IT assets are operated in conjunction with Enterprise Support 7.8. In case SAP Solution Manager Enterprise Edition is Solutions and are required to complete the installed for Customer usage, the Supplier and SAP will, Customer’s business processes as documented in the where necessary, use the SAP Solution Manager solution documentation in SAP Solution Manager Enterprise Edition to remotely access the Software within Enterprise Edition (“Additional Supported Assets”). the Customer’s SAP environment for the implementation Such application lifecycle management is limited of an Incident Remedy. The Customer hereby consents solely to the following purposes: to such remote access. o implementation, configuration, testing, operations, continuous improvement and 7.9. The Customer shall maintain the solution landscape and diagnostics core business processes in SAP Solution Manager o incident management (service desk), problem Enterprise Edition at least for all Customer Production management and change request management as Systems and systems connected to the Customer enabled using SAP CRM technology integrated in Production Systems. SAP Solution Manager Enterprise Edition o administration, monitoring, reporting and 7.10. The Customer shall document any implementation or business intelligence as enabled using SAP Net- upgrade projects within the SAP Solution Manager Weaver technology integrated in SAP Solution Enterprise Edition. The detailed guidelines for this Manager Enterprise Edition. Business intelligence documentation can be found in the document "Solution may also be performed provided the appropriate Documentation" provided by SAP on the SAP Support SAP BI software is licensed by the Supplier. Portal at http://service.sap.com/supportstandards. 7.4. The right to use any SAP Solution Manager Enterprise Edition capabilities under SAP Enterprise Support other 8. SAP EarlyWatch® Alert than those listed in Clause 7.3 above is subject to a separate written agreement with SAP or the Supplier, as 8.1. Unless otherwise agreed in Annex 1 SAP EarlyWatch® applicable, even if such capabilities are accessible through Alert is mandatory for SAP Enterprise Support. The or related to SAP Solution Manager Enterprise Edition. Supplier will activate SAP EarlyWatch® Alert in the Customer Production System and transfer into its own 7.5. The SAP Solution Manager Enterprise Edition shall not SAP Solution Manager Enterprise Edition. SAP be used for: EarlyWatch® Alert should be used weekly on the - CRM scenarios such as service plans, contracts, Customer Production System. It will be checked by the service confirmation management, except as CRM Supplier not less frequently than four times per year. scenarios are expressly stated in Clause 7.3 above; - SAP NetWeaver usage types other than those stated above or - application life-cycle management and in particular incident management (service desk) except for Customer Solutions and Additional Supported Assets and Annex 3 Maintenance Agreement Estonia v1.3 20180628 7/8 9. Technical Quality Checks terms and conditions for SAP Standard Support, including without limitation, pricing. The Supplier may 9.1. SAP may deliver Technical Quality Checks (the require Customer to execute an amendment or other “Technical Quality Check” or “TQC) in case of vital document to the Agreement confirming Customer’s alerts reported by SAP EarlyWatch® Alert or in case SAP selection and the Supplier’s and/or SAP’s then-current - after analyzing the Customer’s situation - agrees that terms and conditions. Such selection is permissible only such a service is needed to handle a Top-Issue or to de- if at least one of the Support Services comprising SAP escalate a critical situation at the Customer’s site. The Enterprise Support for the Customer has completed its TQC might consist of one or more manual, self-service Initial Term. or automatic remote Service Sessions. 10.3. Any selection applies to all Enterprise Support Solutions 9.2. At the end of each Technical Quality Check SAP will of the Customer within the same SAP product family, and provide the Supplier and/or the Customer with an action shall be on the Supplier’s and/or SAP’s then-current plan and/or written recommendations. terms and conditions for SAP Standard Support, including without limitation, pricing, and shall commence 9.3. All or parts of the Technical Quality Check sessions may as of January 1st of the immediately following calendar be delivered by SAP and/or a certified SAP partner acting year or shall commence as of the beginning of the new as SAP’s subcontractor and based on SAP standards and renewal period for orders that are not solely on a calendar methodology. year renewal basis. In case of such selection of SAP Standard Support, delivery of SAP Standard Support shall 9.4. SAP cannot deliver a TQC for Third Party Software/ commence as of this January 1st and shall be subject to Products. an Initial Term as defined in the Support Plan for SAP Standard Support. 9.5. TQC can be re-scheduled only once. Re-scheduling must take place at least 20 working days before the planned 10.4. The change of SAP Support Model referred to herein delivery date. If the Customer fails to follow these may require new support orders be made by the Supplier guidelines, SAP (or the Supplier) is not obliged to deliver from SAP. The Customer undertakes to give all necessary the TQC. information and assistance to the Supplier, as it may require. The Customer shall pay all possible additional costs and expenses resulting from such SAP Support 10. Change of SAP Support Model from SAP Enterprise Model change. Support to SAP Standard Support 10.5. In case of a change of the SAP Support Model by the 10.1. Provided the Customer is not in default of any of its Customer, Customer’s liability to pay the fees obligations under this Agreement, the Customer may commences in the month the change of the SAP Support select SAP Standard Support instead of SAP Enterprise Model will become effective for the Customer. Support with four (4) months written notice to the Supplier either (i) with respect to all Software belonging 10.6. In the event that the Customer selects to replace SAP to the same group of SAP product family for SAP Enterprise Support by SAP Standard Support, the former Enterprise Support that are solely on a calendar year usage rights of SAP Solution Manager Enterprise Edition renewal basis, prior to the start of the Renewal Term that under the SAP Enterprise SAP Support Model shall follows the Initial Term that commenced as of cease. Thereafter, the Customer’s use of SAP Solution Customer’s first order for SAP Enterprise Support; or (ii) Manager shall be governed by the terms and conditions with respect to all Support Services that are not solely on of SAP Standard Support only. The Customer shall not a calendar year renewal basis, prior to the start of the first use any functionalities reserved for SAP Enterprise renewal period in any calendar year that follows the Initial Support. No usage rights are granted to the Customer for Term that commenced as of Customer’s first order for any functionality reserved for SAP Enterprise Support of SAP Enterprise Support and (iii) with respect to a the SAP Solution Manager Enterprise Edition if the selection where orders are on a calendar year renewal Customer receives only SAP Standard Support. basis as well as not solely on a calendar year renewal basis, only prior to the start of the calendar year renewal period in any calendar year that follows the Initial Term that commenced as of Customer’s first order for SAP Enterprise Support for all orders of Enterprise Software Solutions. 10.2. Such selection shall be stated by the Customer in the notice letter, and shall terminate SAP Enterprise Support effective with the commencement of SAP Standard Support. Any such selection shall apply to all Enterprise Support Solutions within the same SAP product family and shall be on the Supplier’s and/or SAP’s then-current Annex 3 Maintenance Agreement Estonia v1.3 20180628 8/8 Annex 4 Page 1 (4) DATA PROCESSING ANNEX 1 BACKGROUND AND PURPOSE 1.1 The terms of this Annex shall apply to the Agreement between S.Y.B. Estonia OÜ (“Supplier”) and the firm, company, corporation or other entity (“Customer”) with whom the Supplier has entered into an agreement regarding the provision of software and/or services (“Agreement”) if Personal Data is Processed by the Supplier and/or its Subcontractors based on the Agreement. 1.2 The Parties acknowledge and agree that with regard to the Processing of the Personal Data under this Annex, the Customer is the Controller and the Supplier is the Processor. 1.3 This Annex does not apply to the Processing of the Personal Data which belongs to the Supplier’s Customer and Prospect Register. The Supplier is the Controller of the Supplier’s Customer and Prospect Register. 2 DEFINITIONS As used in this Annex the following terms shall have the following meanings: “Controller” means the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of Personal Data. “Laws” means mandatory laws in force from time to time in Finland, Estonia and Lithuania (together referred to as “Countries”) relating to the protection of Personal Data and the Processing, including but not limited to the EU General Data Protection Regulation 2016/679 (“GDPR”), and all binding EU and national data protection legislation in force in the Countries. “Personal Data” means any information relating to an identified or identifiable natural person (“Data Subject”) which information is Processed under the Agreement on behalf of the Customer. An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person. “Personal Data Breach” means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Personal Data transmitted, stored or otherwise Processed. “Process” or “Processing” means any operation or set of operations which is performed on the Personal Data or on sets of Personal Data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction. “Processor” means a natural or legal person, public authority, agency or other body, which Processes the Personal Data on behalf of the Controller. “Separate Pricing” is defined in Section 3. “Service” or “Services” means the responsibilities of the Supplier under the Agreement to provide software and/or services to the Customer. “Third Parties” is defined in Section 3. Annex 4 Page 2 (4) 3 PROCESSING 3.1 The types of the Personal Data and categories of the Data Subjects of Personal Data can be the Customer’s users’: (a) name; (b) user name; (c) title; (d) position; (e) email address; (f) employer or other organization; (g) phone number; and (h) possible Personal Data in IP address. 3.2 The Supplier and any person acting under the authority of the Supplier, who has access to the Personal Data, may Process the Personal Data only on documented instructions from the Customer, including with regard to transfers of Personal Data to a country outside the European Economic Area (EEA) and European Union (EU) or an international organisation, unless required to do so by EU or EU member state law to which the Supplier is subject. In such a case, the Supplier shall inform the Customer of that legal requirement before the Processing, unless that law prohibits such information on important grounds of public interest. Such instructions are hereby given by the Customer to the Supplier and include and are limited to: the Customer gives the Supplier instructions to Process the Personal Data in order for the Supplier and its subcontractors to provide the Services to the Customer in accordance with the Service specification applicable to the Agreement. If the Customer desires to amend the documented instructions or give new documented instructions to the Supplier, the amended and new instructions are subject to the Supplier’s written consent and may be priced in accordance with the Separate Pricing. 3.3 The Supplier shall: 3.3.1 ensure that persons authorised to process the Personal Data on its behalf have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality; 3.3.2 in accordance with the Separate Pricing, taking into account the nature of the Processing, assists the Customer by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Customer 's obligation to respond to requests for exercising the Data Subject's rights laid down in the Laws; 3.3.3 in accordance with the Separate Pricing, assist the Customer in ensuring compliance with the obligations pursuant to the Laws, in the performance of data protection impact assessments and consultations with the supervisory authorities as required pursuant to the Laws; 3.3.4 in accordance with the Separate Pricing, as requested by the Customer in writing, delete or return all Personal Data to the Customer after the end of the provision of the Services relating to the Processing, and delete existing copies unless EU or EU member state law requires storage of the Personal Data; and 3.3.5 in accordance with the Separate Pricing, make available to the Customer information necessary to demonstrate compliance with the obligations laid down in the Laws and allow for and contribute to audits, including inspections, conducted by the Customer or another auditor mandated by the Customer to audit the Supplier’s compliance with this Annex. The Supplier shall inform the Customer if, in its opinion, the Customer’s instruction infringes the Laws. The Customer shall notify the Supplier of the audit in writing at least thirty (30) days in advance. The auditor may not be a competitor of the Supplier or other company in the Supplier’s group of companies. The information regarding the Supplier’s operations learnt during the audits are the Supplier’s trade secrets. The Customer is liable for the auditor’s compliance with the terms of the Agreement. 3.4 Based on the Agreement, the Supplier might provide to the Customer third party software and those third parties might provide services for the purpose of the Customer. Those third parties Annex 4 Page 3 (4) (“Third Parties”) are not subcontractors of the Supplier and are not acting under the authority of the Supplier. 3.5 If based on the Laws or any other applicable legislation, regulations or decisions of authorities or the Customer’s instructions, the Supplier is at any time instructed or required to assist the Customer in performing the Customer’s obligations to respond to requests for exercising the Data Subjects’ rights or is otherwise required to perform any other tasks or activities relating to the Personal Data or the Processing that are not the Supplier’s Service duties, the Customer shall pay to the Supplier a separate price for such tasks or activities on a time and material basis in accordance with the Supplier’ consultation price list in force from time to time (such prices payable by the Customer to the Supplier are referred to as “Separate Pricing”). These tasks or activities can be e.g. providing information to a Data Subject on the Personal Data possessed by the Supplier, or removing or transferring Personal Data or responding or reporting to data protection authorities or allowing audits or inspections. 4 USE OF SUBCONTRACTORS The Supplier may engage subcontractors i.e. sub-Processor(s) for the purpose of the Processing. The Supplier may use also its group companies as its subcontractors. The Supplier has entered into data processing agreement(s) with the subcontractors, or the Processing by the Supplier’s group companies can be based on the Supplier’s legitimate interest where applicable under the Laws. 5 CUSTOMER’S DUTIES 5.1 The Customer acts as the Controller in relation to all Personal Data. The Customer is (among other things) liable for the correctness of the Personal Data and the lawfulness of the Processing of the Personal Data and for other duties and liabilities of the Controller. 5.2 The Customer shall take backup copies of the Personal Data before providing the Personal Data to the Supplier or its sub-Processors. 5.3 The Customer warrants to the Supplier that: (a) the Personal Data has been obtained lawfully; (b) the Services to be provided by the Supplier and its sub-Processors will be consistent with and appropriate to the specified and lawful purposes for which the Customer is engaged in relation to the Personal Data; (c) the Customer has not and will not disclose the Personal Data or any part thereof to the Supplier or its sub-Processors in a manner incompatible with applicable legislation; and (d) the Supplier and its sub-Processors are authorized under applicable legislation to Process the Personal Data. 5.4 The Customer undertakes that the Personal Data will not contain anything unlawful and that the Personal Data or its storage or other Processing by the Supplier and its sub-Processors for the provision of the Services does not infringe any rights of third parties. 6 SECURITY Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the Processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, the Customer and the Supplier shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate: (a) in accordance with the Separate Pricing and as reasonably instructed by the Customer, the pseudonymisation and encryption of the Personal Data, (b) the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services; (c) the ability to restore the availability and access to the Personal Data in a timely manner in the event of a physical or technical incident; and (d) a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the Processing. 7 NOTIFICATION OF PERSONAL DATA BREACH 7.1 The Supplier shall notify the Customer without undue delay after becoming aware of a Personal Data Breach. Annex 4 Page 4 (4) 7.2 The Supplier shall in accordance with the Separate Pricing, assist the Customer in ensuring compliance with the Customer’s obligations pursuant to Laws to notify the Personal Data Breach to the supervisory authority and/or to the Data Subjects, taking into account the nature of the Processing and the information available to the Supplier. 8 TRANSFER OF PERSONAL DATA TO THIRD COUNTRIES 8.1 The Supplier and its subcontractors do not themselves transfer the Personal Data to countries outside the European Economic Area (EEA) and European Union (EU) (“Third Country”) unless agreed with the Customer. 8.2 If the Customer or a user of the Customer uses the provided software or Services in Third Countries or if the Customer or a user contacts the Supplier or its subcontractor in Service matters from locations in Third Countries, it is deemed that the Customer has consented to the transfer of the relevant Personal Data to Third Countries for the said purpose. 9 LIMITATION OF LIABILITY 9.1 For the avoidance of doubt, the limitations of liability and disclaimers of warranties elsewhere in the Agreement shall apply also to this Annex. 9.2 Without limiting the validity of limitations of liability or disclaimer of warranties in the Agreement, the Supplier shall not be liable for any failures or damages caused by (i) the non-performance or delay by the Customer or (ii) the inaccuracy, incorrectness or illegality of the Personal Data, materials, information, data or instructions provided by the Customer to the Supplier or its sub- Processors. Annex 5 Processing of Personal Data by SAP The Supplier is not liable for SAP’s compliance of SAP’s obligations. 1. Obligations of the Customer 1.1 The Customer shall be solely responsible for the permissibility of the processing of personal data by SAP and the Supplier as well as for safeguarding the rights of the data subjects. SAP is entitled to process personal data of the Customer as required for SAP to fulfill its contractual obligations towards the Supplier. The Supplier is entitled to process personal data of the Customer as required for the Supplier to fulfill its contractual obligations towards the Customer. 1.2 The Customer shall give commissions related to the processing of personal data and parts thereof to the Supplier or SAP in writing, by facsimile, via e-mail, via SAP’s support portal or implied by making use of the SAP Products. 1.3 The Customer shall make available the personal data for processing to SAP and the results of the processing shall be transferred back by SAP by using a defined transfer procedure or in accordance with the functionality implemented in the SAP products. 1.4 The Customer shall inform the Supplier without delay, if the Customer detects errors or irregularities when examining the results of the processing of personal data. 2. Obligations of SAP 2.1 SAP shall process the personal data of the Customer exclusively in accordance with the Customer’s instructions communicated directly to SAP or relayed to SAP by the Supplier. Instructions may include (without limitation) the correction, erasure and/or the blocking of personal data. The personal data shall not be used by SAP for any other purpose. SAP shall not preserve such personal data longer than instructed by the Supplier. The statutory preservation periods remain unaffected. 2.2 For processing personal data, SAP shall only use personnel which committed themselves to observe data secrecy and secrecy of telecommunications in accordance with Article 16 of Directive 95/46/EC. 2.3 SAP shall implement all technical and organisational measures to comply with the requirements of Article 17 no. 1 of Directive 95/46/EC. In particular, SAP shall take and regularly check the following protection measures: • Access Control: SAP shall install access control systems. • System Access Control: SAP shall control and log access to data processing systems. • Data Access Control: SAP shall define, implement and monitor a concept for user rights, rules for passwords and login procedures. • Data Transmission Control: SAP shall ensure personal data transmission in encrypted form or by a secure alternative procedure. Transmissions must be logged and guidelines for personal data transmissions must be laid down in writing. • Data Input Control: SAP shall implement a detailed logging system for input, modification and deletion of personal data. • Job Control: SAP shall define in writing and establish control mechanisms to ensure that data are processed strictly in accordance with the instructions of the Provider. • Availability Control. SAP shall run a state of the art backup system and define a restore operation procedure to protect personal data from accidental destruction or loss. • Data Separation Control: SAP shall ensure by technical means and defined organisational procedures that personal data collected for different purposes (e.g. different Providers) can be processed separately. Technical means can be separated computer systems or demonstrably logical separation. Access by one customer to the data of any other customer must be prevented. 2.4 If the security measures implemented by SAP do not meet the legal requirements, SAP shall notify the Supplier without delay. 2.5 SAP shall notify the Supplier and/or the Customer, if SAP considers an instruction given by the Customer (directly or indirectly via the Supplier) to be in violation of data protection regulations. SAP shall not be obliged to perform a comprehensive legal examination. 1(2) 2.6 At the Supplier’s written request, SAP shall reasonably support the Customer in dealing with requests from individual data subjects and/or a supervisory authority with respect to the processing of personal data controlled by the Customer. The Customer may give such reasonable instructions to the Supplier who will communicate them to SAP. Such support by SAP and the Supplier shall be at the Customer’s expense. SAP shall notify the Supplier about inspections and measures of a supervisory or any other competent authority. 3. Subcontractors 3.1 SAP is authorized to engage subcontractors for the processing of personal data in such manner that they shall act as further sub-commissioned processors of personal data (Unter-Auftragsdatenverarbeiter). SAP shall pass on to its subcontractors all SAP's obligations vis-à-vis the Supplier and obligate sub-commissioned processors of personal data to obey all relevant data protection rules. 3.2 SAP may engage sub-contractors that may provide support, including access to personal data, in connection with performing its contractual obligations and which are not to be regarded as sub-commissioned processors of personal data. Such support may be provided by sub-contractors engaged by SAP. In such cases SAP shall be obliged to provide in the sub-contracting agreement with such support provider for appropriate contractual provisions in accordance with applicable data protection laws and to take the appropriate control measures, in order to ensure the protection and security of the personal data processed hereunder. 4. Monitoring Rights 4.1 The Supplier shall have all necessary right to verify in accordance with Article 17 no. 2 of Directive 95/46/EC that SAP processes the personal data duly. These monitoring rights shall be carried out in coordination with SAP. After notifying SAP the monitoring can be carried out, in particular, during SAP’s usual business hours on SAP’s premises where the personal data processing is performed. To the extent that any personal data controlled by the Customer is processed by SAP, the Customer shall have the same monitoring rights as the Supplier. 4.2 SAP shall ensure that the Supplier has the monitoring rights set forth in Section 4.1 also vis-à-vis sub-commissioned processors of personal data retained by SAP. 4.3 SAP shall reasonably support the Supplier throughout these verification processes and provide the Supplier with the required information. 4.4 SAP shall contractually safeguard the Supplier's powers of disposal and monitoring rights under this Annex vis-à- vis SAP's subcontractors who may come into contact with the personal data. 4.5 Services rendered by SAP and the Supplier in connection with the Customer’s monitoring rights shall be at the Customer’s expense. 5. Special Confidentiality Obligation; Obligation to Observe Data Secrecy 5.1 SAP undertakes to the Supplier to treat the personal data, which have become known to SAP, confidential and to use such data exclusively for the commissioned data processing. 5.2 SAP undertakes to the Supplier to impose on its employees, who may obtain knowledge of personal data, the same obligations as entered into above by SAP. 2(2) Agreement Number: 23820060 License Agreement name, date and number: Master Software Supply and License Agreement, 15.12.2020, 23820058 Purchase Order date and number: 15.12.2020, 23820059 SOFTWARE MAINTENANCE AGREEMENT for SAP Enterprise Support 3.2. The scope of the Support Services is described in 1. Parties more detail in the Support Plan in Annex 3. 1.1. This Software Maintenance Agreement (”Agreement”) is entered into by: 3.3. SAP Enterprise Support chosen by the Customer a) S.Y.B. ESTONIA OÜ (Reg. Number shall cover all of Customer’s installations of 10991629) with its registered office at Lõõtsa Software belonging to the same SAP software 8, 11415 Tallinn, Estonia (“Supplier”); and product family. If the Customer at any particular time orders another SAP Support Model than b) TERVISE JA HEAOLU previously provided, the Customer will be required INFOSÜSTEEMIDE KESKUS (Reg. to change the same SAP Support Model for all of Number 70009970 ) with its registered office its Software installations on the then-current terms at Uus-Tatari 25, 10134 Tallinn and conditions. The conditions under which such (“Customer”). SAP Support Model change can be made are specified in the Support Plan in Annex 3. 1.2. The Supplier and the Customer are hereinafter jointly referred to as the “Parties” and 3.4. When providing Support Services, the Supplier will independently as a “Party”. cooperate with SAP Support as described in this Agreement, including the Support Plan. For the 2. Background and purpose purposes of providing the Support Services the Supplier will provide SAP with the contact details 2.1. By the license agreement specified above (“License (name and address) of the Customer, details of the Agreement”) the Customer has obtained a license licensed Software (product and country version) as to use the Software specified in Annex 1 to this well as details of this Agreement and other Agreement. arrangements concluded between the Supplier and the Customer. The Customer agrees to the delivery 2.2. As a value added reseller partner of SAP Estonia of the above information to SAP and that SAP may OÜ (SAP) the Supplier is authorized to market, sell contact the Customer directly regarding any aspect and deliver support for the Software in its own of the Support Services. The Customer is, however, name and for its own account. not entitled to send any Incidents related to Software and Third Party Software/Products 2.3. The Agreement describes the scope and provision directly to SAP but must first contact the Supplier’s of and sets out the terms and conditions on which support organization. the Supplier shall provide software support and maintenance services to the Customer for the 4. Fees and payment Software. 4.1. The Support Fee is specified in Annex 1. The 3. Support Services Support Fee is determined by the quality and amount of Software and Support Services provided 3.1. Subject to the terms and conditions set out in this from time to time. The Support Fee is subject to the Agreement, including, without limitation, value added tax unless the transaction is exempt. Customer’s payment of applicable Support Fees, the Supplier hereby agrees to provide Support 4.2. Unless otherwise specified in Annex 1, the Support Services to the Customer for the Software specified Fee shall be paid by the Customer to the Supplier in Annex 1, as amended from time to time. annually in advance. Payment is due to the Supplier within fourteen (14) calendar days of the date of the invoice. In the first year of the Support Services for Maintenance Agreement Estonia v1.3 20180628 1/3 Software the fees will be invoiced from the month data stored in the system. The Customer shall of the delivery of the Software to the Customer to ensure and be responsible for that any person the end of the respective calendar year. concerned has given any necessary consent under applicable data protection legislation for the 4.3. In addition to Support Fee increases based on processing of the data by the Supplier and/or SAP addition of new Software into the scope of the for the purposes of rendering the Support Services applicable Support Services, the Supplier has the in accordance with this Agreement. right to increase the Support Fee once during a calendar year at the maximum by five (5) per cent 5.4. The Supplier and SAP, or any third party authorized without an obligation to notify the Customer in by the Supplier or SAP, shall be entitled to contact advance. employees of the Customer for surveys regarding the satisfaction of the Customer with the Software 4.4. If the Supplier wishes to increase the Support Fee and/or the Support Services or any consulting by more than five (5) per cent it shall notify the services or education services provided. The Customer of the increase in advance sixty (60) days Supplier and SAP shall also be entitled to directly prior to the increase becoming effective. In case of contact the Customer and its employees for risk and an increase pursuant to this Clause 4.4 the Customer quality management purposes. The Customer shall may terminate the Agreement by giving a fifty (50) ensure that the employees of the Customer have calendar days prior notice to the effective date of given any necessary consent under applicable data such fee increase. protection legislation for the processing of data for the purpose of this Clause 5.4. 4.5. Should it appear that the Incident notified by the Customer is not included in the Support Services to 5.5. The Supplier and SAP are entitled to use be provided subject to the Support Fee the Supplier information about the Customer as far as this is is entitled to charge the Customer for the time used useful for the further development of the Software for the search and location of the error or defects and/or the provision of Support Services or any causing the Incident in accordance with its then consulting services or education services offered as current consultancy service price list. well as for internal business or any marketing purposes, provided the confidentiality of the 4.6. Without prejudice to the Supplier’s right to Customer’s trade secrets is maintained. terminate this Agreement under Clause 4 of Annex 2, the Supplier has the right to discontinue the 5.6. The Customer shall be responsible for making of provision of the Support Services by notifying the the back-up copies of the Software and the Customer, if the Customer fails to make due Customer’s databases, computer records and all payments of any of the Support Fees or a part other files and documents in accordance with the thereof in accordance with this Agreement. best computing practice and securing the accuracy and functionality of the back-up copies. 5. System access and processing of data 6. License grant and intellectual property rights 5.1. The Incident processing system automatically collects system data related to system error 6.1. Any Software provided to the Customer hereunder messages (for example, transaction code, program shall be subject to the terms and conditions as well ID, Support Package level and Incident number). as restrictions set forth in the License Agreement. The Customer consents to the processing of such system data by the Supplier and SAP. 7. Claims and limitation of liability 5.2. The Customer shall provide and maintain remote 7.1. Any claim or request that the Customer might have access for the Supplier and SAP to the Software for arising out of or relating to this Agreement or the which Support Services are provided. The Supplier provision of the Support Services shall be settled and SAP are entitled to access the Customer’s between the Supplier and the Customer and shall systems in order to render any Support Services, not be brought against the SAP. including but not limited to Incident Root Cause Analysis, in accordance with this Agreement. The 7.2. Under no circumstances shall the Supplier be liable Customer hereby grants the Supplier and SAP to the Customer for indirect damages, including but remote access without restrictions regarding the not limited to damages resulting from loss of nationality of the employee(s) of the Supplier or income, loss of profit, loss or disruption of data, SAP who process(es) the Incident or the country in loss of anticipated savings, loss of goodwill, loss of which the employees are located. contracts, business interruption, lost or wasted management time or time of other employees or 5.3. When accessing the Customer’s system, the contractors and any other incidental or Supplier and/or SAP may get access to personal consequential losses. Maintenance Agreement Estonia v1.3 20180628 2/3 7.3. The Supplier shall not be liable to the Customer for any loss arising out of any failure by the Customer 8.2. Should there be a contradiction between this main to keep full and up-to-date back-up copies of the body of the Agreement and Annex 1, the terms of Software and data it uses in accordance with best Annex 1 shall apply. Should there be a contradiction computing practice. between this main body of the Agreement and the other Annexes, the terms of this main body of the 7.4. Under no circumstances shall the total liability of Agreement shall prevail. the Supplier arising out of this Agreement exceed an amount equal to the Support Fees paid for the 8.3. The Supplier reserves the right to change any terms Support Services giving rise to the claim for the of this Agreement or its Annexes, as may be Initial Term or Renewal Term, as applicable, during reasonably required and consistent with SAP’s which the event giving rise to the claim occurred. practices. Any such changes to terms shall become Any liability which cannot be excluded by law is not effective one (1) month after written notice by the excluded. Supplier to the Customer, unless otherwise specified therein. 7.5. Except in cases of intent or gross negligence all claims against the Supplier in contract, tort, or 8.4. If the justified interests of the Customer are otherwise are barred after a period of ten (10) negatively affected by any changes, the Customer is months from the date on which the Customer entitled to terminate the Agreement by giving obtains knowledge of the damage; irrespective of fourteen (14) days prior written notice to the date this knowledge, such claims are barred at the latest on which the changed terms will become effective. two (2) years from the date of the damaging event. If the Customer does not terminate within the said period, the changes are deemed to be accepted by 7.6. The Supplier assumes product liability towards the the Customer. Customer only to the extent that such liability is mandatory under applicable national legislation. 9. Term The Supplier does not assume product liability to any further extent. This Agreement shall come into force on the date when the last one of the Parties has signed it 7.7. The limitations mentioned above do not apply to (“Effective Date”) and, unless earlier terminated in liability for damages caused by intentional act or accordance with Clause 4 of Annex 2, shall be in gross negligence. force as long as an Initial Term or Renewal Term of the Support Services for any Software specified in 8. Annexes and Changes to terms Annex 1 is in force. 8.1. The following Annexes to this Agreement constitute an integral part of this Agreement: Annex 1 Supported Software and Support Fees Annex 2 General Terms and Conditions for SAP Enterprise Support Annex 3 Support Plan for SAP Enterprise Support. Annex 4 S.Y.B. Estonia OÜ Customer Data Processing Annex 5 Processing of Personal Data by SAP Place and Date: Tallinn, 15.12.2020 Place and Date: Tallinn, 15.12.2020 S.Y.B. ESTONIA OÜ CUSTOMER _______________________________________ ____________________________________ Toomas Mihkelson Katrin Reinhold Procurator Director Maintenance Agreement Estonia v1.3 20180628 3/3 Customer: Tervise ja Heaolu Infosüsteemide Keskus Software Maintenance Agreement nr. 23820060 Annex 1 Supported Software and Support Fees for SOFTWARE MAINTENANCE AGREEMENT SAP Support Model: VAR Delivered SAP Enterprise Support Initial Term** Renewal Term** (**In deviation from the main rule as set forth in Annex 2) Supported Software Item: Item Quantity: Net Support Fee: Start Date: End Date: SAP Adaptive Server Platform (cores) 6 21,750.00 01-01-21 - 31-12-21 01.01 - 31.12 SAP PowerDesigner EnterpriseArchidect 1 * Yearly (01.01 - 31.12) maintenance fee 21750 € Support Fees Total Net EUR: 21,750.00 Payment Terms: Payment is due to the Supplier within fourteen (14) calendar days of the date of the invoice. In the first year of Support Fees will be invoiced from the month of delivery of the Software to the Customer to the end of the respective calendar year. SAP Solution Manager Enterprise Edition and SAP EarlyWatch® Alert: SAP Solution Manager Enterprise Edition and SAP EarlyWatch® Alert shall not be requirements for or applicable to the Customer. Incidents shall be reported to the Supplier with the Support Services contact information set forth below. Remote Connection Requirements: (Choose the correct option based on the applicable grounds for exemptions and mark it with a cross) ___ The requirements for remote connections as set forth in the Agreement shall be applicable with respect to the Customer. * X The requirements for remote connections as set forth in the Agreement shall not be applicable with respect to the Customer. As a result thereof the maximum processing time set forth for the Supplier in Clause 6.1 and the SLA for the Very High priority Incidents set forth in Clause 7.1 of Annex 3, Support Plan for SAP Enterprise Support are not applicable either. An Incident that is to be processed shall be solved by phone or email. * It is acknowledged that some customers may have strict policies regarding connectivity outside their network. These can be mandated by company or local policies. By choosing the option not to fulfil the requirements for remote connections the Customers is requested to provide documentation of such policies to the Supplier or pinpoint the page/chapter/paragraph where such restriction is stated along with the signing of this Annex 1. S.Y.B. Estonia OÜ Support contact information: Local Office Time (Monday - Friday from 8:00 to 16:00): Phone +372 6181 300 E-mail [email protected] Online Form www.syb.ee/support + call +372 6181 300 Priority "Very High" outside Local Office Time: Online Form www.service.sap.com/message (see more detailed instructions how to open a technical support case from the S.Y.B. Support User Guide) Authorized Technical Contact Persons for Customer Helpdesk: Name: Ardo Abel Name: Phone: +372 56251090 Phone: E-mail: [email protected] E-mail: By signing this Annex 1 the Customer confirms that all of its installations of Software belonging to the same SAP product group with the Software specified above in this Annex 1 are covered by Support Services. This Annex 1 comes into force when it has been executed by both Parties and it overrides and supersedes any previous Annex 1. This Annex 1 is made in two original copies, one for each Party. S.Y.B. Estonia OÜ Tervise ja Heaoluinfosüsteemide Keskus "Supplier" "Customer" Authorized Signature: Name / Title: Toomas Mihkelson/ Procurator Katrin Reinhold/ Director Date Signed: 15.12.2020 15.12.2020 S.Y.B. ESTONIA OÜ Lõõtsa 8 EE-11415 TALLINN Phone +372 6181 575 Annex 1 Maintenance Agreement Estonia v1.3 20180628 www.syb.ee Annex 2 General Terms and Conditions for SAP Enterprise Support 1. Definitions as SAP’s or the Supplier’s support organization is 1.1. In this Agreement and its Annexes (as applicable informed, the support event becomes an Incident. from time to time), unless otherwise defined elsewhere in this Agreement or the context otherwise “Incident Remedy” shall mean the remedy for an requires, the capitalized terms shall have the meaning Incident taking the form of eliminating the defect, defined in this Clause 1. Definitions the singular providing a new program version, or demonstrating include plural and vice versa. how to avoid the effects of the defect with reasonable effort. Incident Remedy corresponds to “Confidential Information” shall mean the error corrections, patches, bug fixes, workarounds, Software, its source codes (notwithstanding the fact replacement deliveries, or any other type of Software that the source code is not licensed to the Customer), or documentation corrections or Modifications. the Documentation, any Proprietary Information, and any other information or business secret marked “Incident Root Cause Analysis” shall mean the in written from as confidential by the disclosing party analysis and classification of an Incident as a at the time of the disclosure or, insofar as such hardware problem, handling issue, data quality issue, information is provided verbally, is designated as software fault, error or malfunction, etc. Treatment confidential or can be readily recognized as such. and routing of such Incident is dependent on the result of the Incident classification. “Correction Level” or “Correction Package” shall mean a change in the Software as between “Initial Term” shall, unless otherwise stated in Versions. Annex 1, mean the period of time between (i) the date the Supplier has started to provide SAP “Custom Code” shall mean software code which Enterprise Support to the Customer for the first time has been programmed either by the Supplier with regards to a particular Software (including, but (Supplier Custom Code) or the Customer (Customer not limited to cases where the Customer has changed Custom Code) and not by SAP/SAP SE. the SAP Support Model from SAP Standard Support to SAP Enterprise Support) and (ii) December, 31st “Customer Production System” shall mean a live of the next full calendar year following such date; SAP system used for the Customer’s internal however, if the provision of support starts on business operations and where the Customer’s data January 1st of a calendar year, the Initial Term shall is recorded at Customer site. end December 31st of the same calendar year. For “Documentation” shall mean SAP sales of SAP BusinessObjects products, “Initial Aktiengesellschaft’s (SAP SE) standard manual(s), in Term” shall mean one year from the Sales Order any medium (including electronic form). Effective Date, except that if there is a joint transaction (sales of SAP BusinessObjects products “Enhancement” shall mean any developments that and SAP Business All-in-One product in one deal), customize, enhance, or change existing SAP the Initial Term shall be aligned with the Initial Term functionality including but not limited, any new for the SAP Business All-in One products. APIs, alternative user interfaces and/or extensions of SAP data structures. “Local Office Time” and “Local Office Hours” shall mean from 8:00 am to 16:00 pm Monday to “Enterprise Support Solution” shall mean all Friday, in accordance with the applicable public Software licensed by the Customer which is covered holidays in Estonia. by SAP Enterprise Support. This shall exclude Software to which special support agreements apply. “Modification” shall mean (i) any Enhancements and (ii) any alteration to the Software including, but “Go-Live” shall mark the point in time from when, not limited to, a change made to the source code after implementation of the Software or an upgrade and/or metadata of the Software. of the Software, the Software is used by the Customer for the processing of real data in live “Program Concepts” shall mean means the operation mode and for running the Customer’s concepts, techniques, ideas and know-how business. embodied and expressed in any computer programs or modules included in the Software, including their “Incident” shall mean the support event starting structure, sequence and organisation. with a malfunction or functional impairment of the Software which – with reasonable probability – is “Proprietary Information” shall mean (i) with based on a defect or error of the Software. As soon respect to Supplier the Software and Documentation and any complete or partial copies thereof, the Annex 2 Maintenance Agreement Estonia v1.3 20180628 1/5 Program Concepts, Third-Party Database, any other support-related information. SAP posts the support third-party software licensed with or as part of the knowledge in its technical information database Software, benchmark results; and (ii) business secrets currently existing in the form of Notes, TopNotes, and other information reasonably identifiable as and Hot News. confidential and proprietary information of the “Service Session” shall mean a sequence of support Supplier, SAP or their licensors or the Customer, activities and tasks carried out remotely (“remote excluding, any part of the Supplier’s, SAP’s or the services”) to collect further information on an Customer’s Proprietary Information which: (a) is or Incident in a Customer Production System resulting becomes publicly available through no act or failure in a list of recommendations to improve the actual of the other Party; or (b) was or is rightfully acquired Customer system status. Such sessions may run by the other Party from a source other than the manually, as a self-service or be fully automated. disclosing Party prior to receipt from the disclosing Party; or (c) becomes independently available to the “Software” shall mean the SAP software (including other Party as a matter of right. any Third Party Software/Product) specified from time to time in Annex 1 to this Agreement, “Release” shall mean each issuance of the Software comprising the executable computer programs and identified by the numeral to the left of the decimal their associated written documents, notably point (e.g. 3.0). Documentation, and any Releases, Versions, “Renewal Term” shall, unless otherwise stated in Correction Levels or Correction Packages of the Annex 1, mean any calendar year following the Initial Software or other Incident Remedies provided in Term, with the year immediately following the Initial relation thereto under this Agreement as well as any Term being the “1st Renewal Term”. complete or partial copies or replacements of any of the foregoing. “SAP Support Portal” shall mean SAP’s Web- based information repository available for the “Support Fee” shall mean the fee payable by the Customer at http://service.sap.com/. Customer to the Supplier for the Support Services as applicable from time to time. The Support Fee “SAP Software Solution” shall mean a group of applicable at the conclusion of this Agreement is one or multiple Customer Production Systems specified in Annex 1. running Software and focusing on a specific functional aspect of the Customer’s business. Details “Support Plan” shall mean the plan describing the and examples are outlined on the SAP Support Support Services available from time to time under Portal (as specified in SAP Note 1324027 or any the selected SAP Support Model. The current future SAP Note which replaces SAP Note Support Plan has been attached to this Agreement as 1324027). Annex 3. “SAP Solution Manager Enterprise Edition” “Support Services” shall mean the maintenance shall mean a support application which is available to services under SAP Enterprise Support to be the Customers who are covered by defined provided by the Supplier to the Customer under this maintenance and support programs of SAP Agreement. Software. The scope of usage of the SAP Solution “Third-Party Database” means any database Manager Enterprise Edition depends on the software, the rights in which belong to a third party applicable SAP Support Model and is specified in licensed to the Customer through the Supplier. Annex 3. “Third Party Software/Product(s)” shall mean a “SAP Support” shall mean SAP’s support software or product owned by a third party other organization. than SAP or SAP SE and distributed by the Supplier “SAP Support Model” shall mean the unified as a “supplementary product” or as a separate support engagement between SAP and the Supplier component. as SAP’s VAR partner and the Supplier and the “Top-Issue” shall under SAP Enterprise Support Customer, currently SAP Enterprise Support as mean very special and critical Incidents, identified by defined in this Agreement and its Annexes or SAP SAP EarlyWatch® Alert or the Supplier and Standard Support. prioritized jointly by SAP and the Supplier in “SAP Support Network” shall mean SAP’s global accordance with the SAP standards, which (i) may service and support backbone for managing end-to- endanger the Go-Live of Customer pre-Production end Incident management and software System or (ii) have a significant business impact on a updates/life-cycle management. It consists of SAP core Customer’s Production System. Technical Support Database, SAP Solution Manager “Unrestricted Shipment” shall mean the phase of Enterprise Edition, and SAP Support Portal. delivery during which a Software Release is generally “SAP Technical Support Database” shall mean a available to all end users. technical information database provided and maintained by SAP in which SAP posts technical Annex 2 Maintenance Agreement Estonia v1.3 20180628 2/5 “Version” shall mean each issuance of each Release the Supplier shall have received an amount equal to identified by the numeral to the right of the decimal the payment otherwise required. point (e.g. 3.1). 2.5. The Customer can offset claims only if they are 2. Payment and Taxes uncontested or ordered by a court of law. 2.1. In case of late payment, in addition to Supplier’s right 3. Confidential Information to collect annual interest on late payment at the rate of 10 % Customer will reimburse the Supplier for all 3.1. The Parties shall treat as confidential all Confidential reasonable costs incurred (including reasonable Information of the other Party acquired in attorneys’ fees) in collecting past due amounts. connection with this Agreement. Such Confidential Information shall only be used in accordance with 2.2. All Support Fees are subject to statutory sales / the purposes of this Agreement and may not be turnover tax / value added tax unless the transaction disclosed to any third parties. Each Party shall treat is exempt. The Support Fees set forth in Annex 1 are this Agreement and its terms as Confidential exclusive of value added tax. Information of the other Party. 2.3. If the Customer is required by law to withhold 3.2. Notwithstanding Clause 3.1 above, the Supplier may income or corporation tax or a similar tax disclose necessary information (whether (hereinafter “Withholding Tax”) from any gross Confidential Information or not) regarding the payment to the Supplier under this Agreement, the Customer to SAP for the purpose of providing or Customer shall be entitled to withhold or deduct otherwise relating to the Support Services in such tax from the gross amount to be paid if and to accordance with this Agreement. By signing this the extent that the Supplier may offset the Agreement the Customer gives its consent to the withholding income and corporate tax liabilities above disclosures by the Supplier. according to the law of the country of residence of the Supplier against its income or corporate tax 3.3. Confidential Information shall not include liabilities. However, the Customer shall use all information that: endeavours to reduce any such withholding payable a. has become generally known or accessible to the lowest possible rate subject to compliance through no fault of the receiving Party; with all applicable laws and double taxation treaties. b. was in the possession of the receiving Party or The Supplier will cooperate with the Customer to the known to it or brought in material form by the extent that is necessary to apply for such reduction, receiving Party before the receipt from the especially by, but not limited to, providing necessary disclosing Party without infringing any forms to the Customer or the relevant tax authority. confidentiality obligations; Otherwise, the Customer is entitled to withhold tax c. was independently developed by the receiving at standard rates according to the relevant laws. The Party without the use of Confidential Customer will in the case of any withholding of any Information; Withholding Tax provide to the Supplier receipt d. was lawfully disclosed to the receiving Party by a from the relevant tax authority to which such third party not bound by any confidentiality Withholding Tax has been paid. In case the Supplier obligation in respect of such information; under this Agreement is not entitled to offset the e. was revealed by the receiving Party after prior withholding income and corporate tax liability written consent of the disclosing Party; or according to the law of the country of residence, the f. has to be disclosed according to statutory law or Supplier and the Customer mutually agree in writing regulation if this requirement is made known to whether the Customer shall be entitled to withhold the disclosing Party without any undue delay and taxes on account of the Supplier from the the scope of such disclosure is restricted as far as contractually agreed payments. The fact that such possible, or information that has to be disclosed offset is not possible (or not possible in a specific due to a court decision if the disclosing Party is year) shall be notified by the Supplier to the informed of this decision without undue delay Customer. and there is no possibility to appeal against such decision. 2.4. All other taxes or charges of any kind (including but not limited to, customs duties, tariffs, excise, gross 3.4. The Parties shall only make Confidential receipts, sales and use and value added tax) except Information accessible to employees or third parties income tax or corporation tax (or similar taxes) will to the extent necessary to perform the obligations be borne by the Customer. If any such tax or duty under this Agreement, and provided that such has to be withheld or deducted from any payment persons are put under a corresponding under this Agreement, the Customer shall increase confidentiality obligation. Either Supplier or the payment under this Agreement by such amount as Customer may disclose this Agreement to shall ensure that after such withholding or deduction, Annex 2 Maintenance Agreement Estonia v1.3 20180628 3/5 government agencies and other persons with a 5. Force majeure legitimate need for the information. 5.1. If the performance of this Agreement or any 3.5. The foregoing confidentiality obligation shall survive obligation under it is prevented, restricted or the termination of this Agreement. interfered with by reason of any act of God, act of government, war, terrorism, riots, strike or labour 4. Termination dispute embargo, acts of civil or military authority, failure of transportation, facilities or energy sources, 4.1. The Customer may terminate the Support Services fire or flood or other casualty, Internet or for any Software specified in Annex 1 -by giving the telecommunications failure, or failure of Supplier one hundred and twenty (120) days prior subcontractors or suppliers arising from a like cause, written notice to the end of either i) the Initial Term or from any other cause not arising within the or ii) any Renewal Term for the Software in question reasonable control of the affected Party, the affected provided that the Support Services for all of Party shall be excused from such performance for so Customer’s SAP Software installations belonging to long as and to the extent that such force prevents, the same SAP product family (whether provided restricts or interferes with that Party’s performance. under this Agreement or under another software If such conditions continue for a period of more maintenance agreement) shall always be terminated than three (3) consecutive months, either Party shall simultaneously. have the right to terminate this Agreement upon twenty (20) days prior written notice to the other 4.2. The Supplier may terminate Support Services for any Party. Software specified in Annex 1 by giving the Customer sixty (60) days prior written notice to the 6. Export restrictions end of either i) the Initial Term or ii) any Renewal Term. 6.1. The Customer acknowledges that the Software or parts of the Software and related technical 4.3. Notwithstanding Clause 4.2 above, the Supplier may information are subject to U.S. and/or European or terminate this Agreement upon fourteen (14) days other export control laws, including applicable prior written notice to the Customer if the Customer national laws, which may prohibit their delivery to fails to pay any portion of or all remuneration due certain countries. The Customer undertakes not to and owed for the Support Services ordered by the export or reexport Software or technology in Customer. connection therewith contrary to the export control regulations of the United States of America, the 4.4. Notwithstanding Clause 4.2 above, the Supplier may European Community, applicable national laws and terminate the Support Services for any Software regulations, and other export control laws in the area specified in Annex 1 or this Agreement in its of the European Community and, in particular to entirety, as applicable if all Customer’s installations obtain the required export licenses. The Customer is of Software belonging to the same SAP product responsible for obtaining the necessary export- family with the respective Software are not under license if the Software, subject to the License maintenance under the same SAP Support Model. Agreement, is transferred to another location. 4.5. In case the License Agreement is terminated for 7. Miscellaneous whatever cause, the Supplier shall have the right to simultaneously terminate this Agreement with regard 7.1. This Agreement may not be assigned by the to the respective Software by giving the Customer a Customer without the Supplier’s prior written written notice thereof. consent. Any such purported assignment shall be void. The terms and conditions of this Agreement 4.6. Either Party may terminate this Agreement in its shall be binding upon any permitted assignees or entirety or with respect to Support Services for transferees. However, the Supplier may assign this certain Software specified in Annex 1 upon any Agreement to any company belonging to the same material breach of this Agreement by the other Party group of companies or to SAP or another company which is capable of remedy but has not been appointed by SAP, if necessary for the provision of remedied within thirty (30) calendar days after Support Services. written notice from the non-breaching Party requiring such breach to be remedied. Termination 7.2. This Agreement together with its Annexes forms the shall not relieve the Customer from paying all fees entire agreement of the Parties relating to the subject accruing prior to termination and shall not limit matter hereof and supersedes all previous and either Party from pursuing any other available contemporaneous agreements, communications, remedies. representations, or agreements regarding the same subject matter. Annex 2 Maintenance Agreement Estonia v1.3 20180628 4/5 7.3. All notices relating to this Agreement shall be in writing and delivered in person, by overnight delivery service or first class prepaid mail with return receipt requested, to the address of the other Party specified above or the address specified by such Party in accordance with this Clause, and shall be deemed to be given when delivered if delivered in person or by overnight delivery service and upon the expiration of seven (7) days after sending if sent by mail, unless the return receipt provides an earlier date. 7.4. Should any provision in this Agreement be or become ineffective or if this Agreement is incomplete, this will not affect the validity of the remaining provisions of this Agreement. The ineffective provision must be replaced by an enforceable provision that achieves as nearly as possible the business purpose, intent and economic effect of the ineffective provision. 7.5. The failure or delay by either Party to enforce any term of this Agreement shall not be deemed a waiver of such term. 7.6. Subject to what has been set forth about the Supplier’s right to change the terms of this Agreement under Clause 8 of the main body of this Agreement, all other amendments to the Agreement shall be made in writing and shall be signed by both Parties in order to be binding. 8. Governing law and jurisdiction 8.1. This Agreement shall be governed by, and construed and enforced in accordance with the laws of Estonia, without regard to conflict of law principles. 8.2. Any disputes arising out of or in connection with this Agreement, including any disputes regarding the existence, validity or termination, shall be settled by arbitration in accordance with the Rules of the Arbitration Court of the Estonian Chamber of Commerce and Industry and in force at the time when such proceedings are commenced. The number of arbitrators shall be three (3). The arbitration referred to above is the Arbitration Court of the Estonian Chamber of Commerce and Industry. Annex 2 Maintenance Agreement Estonia v1.3 20180628 5/5
Allikas: Tervise- ja heaolu infosüsteemide keskus dokumendiregister →
dokumendiregister.eeAsutusedEesti avalike dokumendiregistrite otsing · nimistu.ee andmetel