{"id":3736,"date":"2019-10-11T07:05:54","date_gmt":"2019-10-11T06:05:54","guid":{"rendered":"http:\/\/www.appcrobms.com\/?page_id=3736"},"modified":"2023-04-04T08:58:22","modified_gmt":"2023-04-04T07:58:22","slug":"sla-agreement","status":"publish","type":"page","link":"https:\/\/www.appcrobms.com\/de\/sla-agreement\/","title":{"rendered":"SLA Agreement"},"content":{"rendered":"

Service Level Agreement for APPCRO Products and Services<\/strong><\/h3>\n

This Service Level Agreement applies to and is incorporated by reference into the ordering document or contract made by and between the APPCRO (Service Provider) and the Customer (as identified on the order or contract). Service Provider may modify this Service Level Agreement from time to time by posting such amended Service Level Agreement to Service Provider\u2019s site, but will provide sixty (60) days advance notice to Customer before materially reducing the benefits offered to Customer under this Service Level Agreement.<\/p>\n

Service Provider SLA <\/strong>
\nDuring the term of the applicable contact, Service Provider will use reasonable efforts to achieve a Monthly Uptime Percentage of at least 99% for any calendar month. If Service Provider does not meet the Service Provider SLA, and so long as Customer\u2019s account with us is current, Customer will be eligible to receive the credits described below. These credits are Customer\u2019s exclusive remedy for any failure by Service Provider to meet the Service Provider SLA. Service Provider and Customer hereby agree as follows:<\/p>\n

1. DEFINITIONS<\/strong><\/h2>\n

The following definitions apply to this Addendum.<\/p>\n

    \n
  • Application Administration<\/em>
    \nSoftware installation and software updates (patches, upgrades, support, and maintenance)<\/li>\n
  • Technical Support<\/em>
    \nOnline email support during coverage hours, 24×7 access to support portal<\/li>\n
  • Service Management<\/em>
    \nClient activation, security monitoring, change control, problem management, and escalation procedures<\/li>\n
  • System Administration<\/em>
    \nSystem configuration, deployment, support, monitoring, response, repair, tuning and capacity planning<\/li>\n
  • Network Administration<\/em>
    \n<\/strong>Network provisioning, monitoring,\u00a0 response,\u00a0 repair,\u00a0 security,\u00a0 utilization\u00a0 management\u00a0 and\u00a0 capacity planning<\/li>\n
  • Data backup and retention<\/em>
    \nBackups of Customer data<\/li>\n
  • Software Availability<\/em>
    \nThe periods of time that the Software is available for use by Customer not including in scheduled downtime<\/li>\n
  • User Response Time<\/em>
    \nThe time it takes for the APPCRO to complete a user request and return a response<\/li>\n
  • Restoration of services<\/em>
    \nIn the event of a major disaster event, such as flooding of the hosting facility or an earthquake that destroys the infrastructure<\/li>\n
  • Maximum Restore Age
    \n<\/em>It is the maximum age of the data should we need to restore production data from backup<\/li>\n
  • Problem Response Time<\/em>
    \nProvision of user support with primary coverage in APPCRO local time excluding statutory holidays. Response time will be calculated by dividing the numbers of issues responded in its SLA level and we aim to be 90% or less during primary coverage.<\/li>\n
  • Problem Correction<\/em>
    \n<\/strong>Provision of any correction for a reproducible error in the application<\/li>\n
  • Downtime<\/em>
    \nmeans the time in which any service listed above is not capable of being accessed or used by the Customer, as monitored by Service Provider. \u201cMonthly Uptime Percentage\u201d means the total number of minutes in a calendar month minus the number of minutes of Downtime suffered in a calendar month, divided by the total number of minutes in a calendar month.<\/li>\n
  • \u201cExclusion from Downtime\u201d
    \nThe following are not counted as Downtime for the purpose of calculating Monthly Uptime Percentage:<\/li>\n<\/ul>\n

    Service unavailability caused by scheduled maintenance of the platform used to provide the applicable service (Service Provider will endeavor to provide seven days\u2019 advance notice of service-affecting scheduled maintenance); or<\/p>\n

    Service unavailability caused by events outside of the direct control of Service Provider or its subcontractor(s), including any force majeure event, the failure or unavailability of Customer\u2019s systems, the Internet, and the failure of any other technology or equipment used to connect to or access the service.<\/p>\n

     <\/p>\n

    On-Premise Security
    \n<\/strong>Customer ensures that Customer data is protected with physical security, data encryption, user authentication, application security, and more. Specific measures include:
    \n– All servers are located behind the firewall with only essential ports enabled.
    \n– All firewalls have Intrusion Detection enabled.
    \n– All Licensee data is stored in separate physical databases.
    \n– 128-bit SSL encryption<\/p>\n

    Customer is responsible for purchase and maintenance of its own equipment, hardware and access, including but not limited to network and data connection, to establish a connection to the Internet.<\/p>\n

    2. SLA LEVELS<\/strong><\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    L0<\/strong><\/span>
    \nBasic SLA
    \n<\/span><\/strong>(Default)
    \n<\/strong>Time Frame 1<\/td>\n    		Severity<\/strong><\/span><\/td>\nResponse time<\/strong><\/span><\/td>\nResolve time<\/strong><\/span><\/td>\nClaim procedure<\/strong><\/span><\/td>\n<\/tr>\n
    1 \u2013 Catastrophic<\/td>\n8 hours<\/td>\n2 days<\/td>\nNo<\/td>\n<\/tr>\n
    2 \u2013 High<\/td>\n2 days<\/td>\n4 days<\/td>\nNo<\/td>\n<\/tr>\n
    3 \u2013 Low<\/td>\n4 days<\/td>\n20 days<\/td>\nNo<\/td>\n<\/tr>\n
    4 – Limited<\/td>\n8 days<\/td>\nOn Agreement<\/td>\nNo<\/td>\n<\/tr>\n
    L1<\/strong><\/span>
    \nBronce SLA<\/span>
    \n<\/strong>Time Frame 1<\/td>\n    		Severity<\/strong><\/span><\/td>\nResponse time<\/strong><\/span><\/td>\nResolve time<\/strong><\/span><\/td>\nClaim procedure<\/strong><\/span><\/td>\n<\/tr>\n
    1 \u2013 Catastrophic<\/td>\n4 hours<\/td>\n1 day<\/td>\nYes<\/td>\n<\/tr>\n
    2 \u2013 High<\/td>\n1 day<\/td>\n2 days<\/td>\nYes<\/td>\n<\/tr>\n
    3 \u2013 Low<\/td>\n2 days<\/td>\n16 days<\/td>\nNo<\/td>\n<\/tr>\n
    4 – Limited<\/td>\n6 days<\/td>\nOn Agreement<\/td>\nNo<\/td>\n<\/tr>\n
    L2<\/strong><\/span>
    \nSilver SLA<\/span>
    \n<\/strong>Time Frame 2<\/td>\n    		Severity<\/strong><\/span><\/td>\nResponse time<\/strong><\/span><\/td>\nResolve time<\/strong><\/span><\/td>\nClaim procedure<\/strong><\/span><\/td>\n<\/tr>\n
    1 \u2013 Catastrophic<\/td>\n3 hours<\/td>\n6 hours<\/td>\nYes<\/td>\n<\/tr>\n
    2 \u2013 High<\/td>\n6 hours<\/td>\n12 hours<\/td>\nYes<\/td>\n<\/tr>\n
    3 \u2013 Low<\/td>\n12 hours<\/td>\n14 hours<\/td>\nNo<\/td>\n<\/tr>\n
    4 – Limited<\/td>\n4 days<\/td>\nOn Agreement<\/td>\nNo<\/td>\n<\/tr>\n
    L3<\/strong><\/span>
    \nGold SLA<\/span>
    \n<\/strong>Time Frame 3<\/td>\n    		Severity<\/strong><\/span><\/td>\nResponse time<\/strong><\/span><\/td>\nResolve time<\/strong><\/span><\/td>\nClaim procedure<\/strong><\/span><\/td>\n<\/tr>\n
    1 \u2013 Catastrophic<\/td>\n2 hours<\/td>\n4 hours<\/td>\nYes<\/td>\n<\/tr>\n
    2 \u2013 High<\/td>\n4 hours<\/td>\n8 hours<\/td>\nYes<\/td>\n<\/tr>\n
    3 \u2013 Low<\/td>\n8 hours<\/td>\n10 days<\/td>\nNo<\/td>\n<\/tr>\n
    4 – Limited<\/td>\n\u00a03 days<\/td>\n20 days<\/td>\nNo<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    2.1 Time Frames
    \n<\/strong>Time Frame 1 \u2013 Monday to Friday from 8:00 \u2013 16:00 in Info Novitas local time excluding statutory holidays
    \nTime Frame 2 \u2013 Monday to Saturday from 8:00 – 16:00 in Info Novitas local time excluding statutory holidays
    \nTime Frame 3 \u2013 Monday to Saturday from 8:00 – 20:00 in Info Novitas local time excluding statutory holidays<\/p>\n

     <\/p>\n

    2.2. Severity Level Definitions
    \n<\/strong>Support tickets are categorized according to a severity or business impact scale. Technical support requests within a severity level are generally processed on a first-come, first-served basis. Catastrophic (severity 1) and High-impact (severity 2) problems that require an immediate response or direct help of technical support specialists may be processed out of turn. These situations require the Customer personnel to be at their work locations until a fix is developed or workaround is available.<\/p>\n

    When submitting a Support ticket, you are requested to supply detailed information (such as details about service and platforms, steps to reproduce, exact error messages, logs, changes made to the system or environment prior to the issue, etc) for the Info Novitas support team to properly identify and diagnose the issue and speed up response and resolution of the ticket. Failure to supply this information upon request may result in a delay of support assistance.<\/p>\n

     <\/p>\n

    Severity 1 – Catastrophic
    \n<\/strong>A catastrophic problem in production systems that is determined to be a Product Error. A complete loss of Cloud Service or On-Premise Service:<\/p>\n

      \n
    • No user can interact with product or service<\/li>\n<\/ul>\n

      Severity 2 – High
      \n<\/strong>A high-impact problem in production systems that is determined to be a Product Error. Essential operations are seriously disrupted:<\/p>\n

        \n
      • A problem that affects essential operations of the product or the service in the management of the workload<\/li>\n
      • Service is working but with a high outage, loading hangs indefinitely or crashing<\/li>\n<\/ul>\n

        Severity 3 \u2013 Low
        \n<\/strong>Lower impact problem on a production system that is determined to be a Product Error. The system can continue essential operations:<\/p>\n

          \n
        • Any problem in the interfaces<\/li>\n
        • A problem that affects the functionality or features<\/li>\n
        • Impaired operation of service<\/li>\n
        • Performance degradation in any of the components<\/li>\n
        • Severity 1 and 2 problem with a temporary workaround available.<\/li>\n<\/ul>\n

          Severity 4 – Limited
          \n<\/strong>Any impact problem occurring on non-production system or question, comment, feature request, documentation issue or another non-impacting issue:<\/p>\n

            \n
          • Any problem with platform infrastructure not related with APPCRO Service<\/li>\n
          • Any problem from mismanagement and unsupported processes<\/li>\n
          • General usage, configuration question<\/li>\n
          • Cosmetic issues, including errors in the documentation<\/li>\n
          • Any problem due to configuration changes in production systems (Technical Assistance)<\/li>\n
          • Questions about integration (Integration Assistance)<\/li>\n
          • Problems on non-production systems, such as test and development systems<\/li>\n
          • Feature requests (Feature Enhancement)<\/li>\n<\/ul>\n

             <\/p>\n

            3. PROCEDURES AND METHODS OF MAINTENANCE<\/strong><\/h2>\n

            Maintenance procedure:
            \nMaintenance implies solving problems by APPCRO according to the Customer Service Request (CSR) application that relates to the delivered system.<\/p>\n

            Registration of CSRs is done by e-mail via APPCRO Help Desk at support@info-novitas.com or via the APCPRO Service Desk portal and telephone support.<\/p>\n

            Depending on the level of severity of the problem, the Severity category, priority is given to “1”, “2”, “3” or “4”. The client is responsible for classifying and allocating the appropriate priority level to a particular request in accordance with the above levels, and if the priority is not assigned or incorrectly defined, then it will be assigned to APPCRO.<\/p>\n

            After receiving the request, within the agreed response time, APPCRO begins to analyze the request. The answer will be sent to the Client in response to the registered CSR e-mail.<\/p>\n

            Performing Activities:
            \n<\/strong>Upon receiving maintenance request by the Customer of the Service, the Authorized Person of the Customer and APPCRO must agree orally or written (e-mail) on the seriousness of the problem.<\/p>\n

            When the Authorized Person of the Customer and APPCRO, in writing or verbally agree on the level of severity of the problem, APPCRO will initiate maintenance procedures in accordance with the terms and conditions, the type of maintenance applied.<\/p>\n

            APPCRO will, upon the expiration of response time, perform a continuous action to remedy the problem encountered and to notify the Customer of the Service in a timely manner or on his request for repair status.<\/p>\n

            APPCRO does not assume any responsibility for eliminating any problems with the Program in the event of non-existence or non-compliance with the security procedures by the Customer. The Customer must provide APPCRO in writing all safety procedures related to the operation of Services, and APPCRO is obliged to comply with the written security procedures when working in the Customers IT environment.<\/p>\n

            In the case of remote network maintenance, APPCRO employees will inform in advance of their actions on the Target Client’s server and make an agreement with the Employer’s employees.<\/p>\n

             <\/p>\n

            4. CLAIM PROCEDURE<\/strong><\/h2>\n

            To receive service credit for a particular calendar month, Customer must submit a claim by email to the support team within 30 days of the end of the month during which the Service did not meet the Service Provider SLA, and include the following information:<\/p>\n

              \n
            • Customer name and account number;<\/li>\n
            • the name of the service to which the claim relates;<\/li>\n
            • the name, email address, and telephone number of the Customer\u2019s designated contact;<\/li>\n
            • information supporting each claim of Downtime, including date, time, and a description of the incident and affected service, all of which must fall within the calendar month for which you are submitting a claim.<\/li>\n<\/ul>\n

               <\/p>\n

              Updated: 01 January 2023.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

              Service Level Agreement for APPCRO Products and Services This Service …<\/p>\n","protected":false},"author":4,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-3736","page","type-page","status-publish","hentry"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.appcrobms.com\/de\/wp-json\/wp\/v2\/pages\/3736","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.appcrobms.com\/de\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.appcrobms.com\/de\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.appcrobms.com\/de\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.appcrobms.com\/de\/wp-json\/wp\/v2\/comments?post=3736"}],"version-history":[{"count":5,"href":"https:\/\/www.appcrobms.com\/de\/wp-json\/wp\/v2\/pages\/3736\/revisions"}],"predecessor-version":[{"id":8548,"href":"https:\/\/www.appcrobms.com\/de\/wp-json\/wp\/v2\/pages\/3736\/revisions\/8548"}],"wp:attachment":[{"href":"https:\/\/www.appcrobms.com\/de\/wp-json\/wp\/v2\/media?parent=3736"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}