Software Support Policy

This document including all exhibits describes various aspects of Software Support such as scope, responsibility, contact details, response times and error correction services for the specified licensed Software in an Order Form.

Any capitalized terms used in this document in relation to Software Support which are not specifically defined in this document but defined in the relevant Software License Agreement, hereafter referred as “Agreement”, have the meaning as described in the Agreement.

Incident Severity-wise support hours and Response time

Official Support Contact Channels

Customer may contact TCS to report an error and request Software Support services by any of the following methods:

• Toll free Numbers, please refer to Exhibit C.
• Support team email: ignio.support@digitate.com.
• TCS provided incident management portal available at: https://support.digitate.com

Customer Responsibilities

General responsibilities during regular operations:

• Operations engineer shall ensure periodic data backup/ maintenance of the Customer Environment including Software configuration data.
• Ensure all non-production environments including production replica environment are always on the latest Patch, Service Pack of the Named Version with relevant data and all licensed functionalities of the Software to deploy and validate fixes, Patches, Service Packs, etc.
• Apply all security and emergency Patches without any undue delay upon receiving the notification from the Software Store or recommendation from Software Support team.
• Operations engineer by Customer: TCS recommends Customer to appoint support engineers trained in administration and operation of the Software. Refer Exhibit D for details on recommended attributes of Operations engineer.

Pre-requisites and responsibilities during incident lifecycle

Before incident registration:

• Operations engineer shall perform initial analysis of issues or query received from Authorized Users and provide information, resolution or workaround for known issues.
• If Operations engineer is unable to provide resolution, Operations engineer shall register incident through the official support channels and provide the relevant information during incident registration. For details on Operations engineer responsibilities during incident lifecycle, refer Exhibit D.

During incident investigation:

• Promptly respond to inquiries from Software Support team.
• TCS may request use of remote screen-sharing tools solely for the purpose of analysis of the incident and only if such analysis cannot be conducted solely through an examination of the logs and related files. TCS shall ensure that the information received from Customer during remote screen-sharing shall be used solely for the purpose of providing Software Support to Customer.
• Upon request by Software Support team, Customer shall approve and facilitate screen-sharing access to development and/or test and production environments to Software Support team for troubleshooting the reported issues.
• Provide additional logs and any other investigative information requested by Software Support team for troubleshooting the reported issues.

Post provision of incident resolution

• Apply TCS provided resolution on non-production environments and perform extensive regression testing.
• Apply TCS-provided resolution on production environment only after thorough verification and after performing necessary system backup.

TCS shall not be liable for any delay or failure in the performance of its obligations hereunder, if and to the extent such delay or failure is caused by the actions or omissions of the Customer or its agents or due to a breach of any terms by Customer of the Agreement for the Software to which this support pertains. TCS shall undertake commercially reasonable measures, as may be necessary, to correct or remedy such failures or delays by the Customer.

EXHIBIT A: Definitions

The following table describes the terms used in this document and their definitions.

EXHIBIT B: End of Version and End of Life Policy

TCS provides support for the Software as given below, subject to the Software End of Life Policy.

*The support timelines applicable to Named Version ‘Butterfly’ are as per table given below.

Following are the support timelines for currently supported Named Versions

Software End of Life Policy

At any time after the conclusion of minimum three (3) years from the date of the GA of the highest Named Version of a Software, TCS may, at its sole discretion, end all on-going or planned software development, maintenance and support (“Software End of Life”) for the particular Software. At least 12 months prior to the effective date of the Software End of Life, TCS shall post a notification on Software Store.

During the timeframe between when Software End of Life notification is posted on Software Store and the actual effective date of Software End of Life, the Software will be supported as follows:

• No new enhancements will be made to the Software.
• No enhancements will be made to the Software to support new or updated versions of the platforms on which the Software runs or to which it connects.
• Software Support team will direct Customer to existing fixes, Patches, Service Packs, or workarounds applicable to the reported case.
• TCS shall develop new hot fixes for problems of high technical impact. With Customer’s assistance, Parties shall mutually determine the degree of impact and exposure and the applicable commercially reasonable remedies.

EXHIBIT C: Toll-free numbers

The following table lists the toll-free numbers by country.

EXHIBIT D: Attributes of Customer Operations engineer:

Customer shall appoint Operations engineer(s) trained on all relevant aspects of the Software who will typically analyze the symptoms, replicate the issue, determine the probable cause, propose solution or workaround and work with Customer to apply the solution or work around.

Operations engineer would typically handle and provide information that includes:

• Detailed investigation analysis with relevant logs, and investigation information
• Creating problem description
• Environment / build details
• Steps to reproduce
• Actual results and expected results

It is recommended that Operations engineers be trained in:

• Linux skills
• Basic networking knowledge
• Java runtime experience and diagnostics skills
• Database experience

Version: Software Support, March 2021

Release Date: July 12, 2021

Copyright © 2022 Tata Consultancy Services Limited. All Rights Reserved.