Agreement Overview
Agreement Overview
Agreement Overview
This has the reference to the discussions and negotiations, and based on the
understanding made on 01 August 2019. This agreement is being executed on this day of 04
August 2019 by and between
M/S. Sonaiya software solutions having its office at No: 78, First floor, Marathiammal
complex, Mounasamy mutt street, Ambattur, Chennai 600053 and represented by
Mr. A.Murugappan, Proprietor here in after called as The Firm which team shall include all
its successors in interest, execution and assignee
and
M/S. Apisol Private Ltd, 10th East cross street, Gandhi Nagar East, Vellore – 632006
represented by Mr. CN.Aparajitha Which term shall mean and include all its successors in
interest, executor and or assignee.
This Agreement remains valid until superseded by a revised agreement mutually endorsed by
the stakeholders.
This Agreement outlines the parameters of below mentioned IT services covered as they are
mutually understood by the primary stakeholders.
4. Periodic Review
This Agreement is valid from the Effective Date outlined herein and is valid until further notice. This
Agreement should be reviewed at a minimum once per fiscal year; however, in lieu of a review
during any period specified, the current Agreement will remain in effect.
5. Service Agreement
The following detailed service parameters are the responsibility of the Service Provider in the
on-going support of this Agreement.
6.Payments
2. As per the discussions, Amount INR 30,000 per month. On 3rd of every month.
If tickets increased then the mentioned level, the bill value will differ according to that.
7. Service Management
Effective support of in-scope services is a result of maintaining consistent service levels. The
following sections provide relevant details on service availability, monitoring of in-scope
services and related components.
· 0-16 hours (during business hours) for issues classified as High priority.
· Within 48 hours for issues classified as Medium priority.
· Within 5 working days for issues classified as Low priority.
Those mentioned above where is only for working days and working hours.
The finished works may be deployed and checked other than official hours.
Other than priority the tickets resolving will consume time depends on it’s complexity.
The receiving ticket should have the following parameters,
Ticket Header,
In time,
Date,
Priority level,
Complexity column (which was filled by pro
Remarks.
Remote assistance will be provided in-line with the above timescales dependent on the
priority of the support request.