12.1The Services shall be available 99.9%, measured monthly, excluding holidays and weekends and scheduled maintenance, excluding outages which are beyond our control (for example, outages caused by integration failures of ERP systems, marketplaces, e-commerce websites etc.), or software releases. If you request maintenance during these hours, any uptime or downtime calculation will exclude periods affected by such maintenance. Further, any downtime resulting from outages of third party connections or utilities or other reasons beyond our control will also be excluded from any such calculation. Your sole and exclusive remedy, and our entire liability, in connection with Service availability shall be that for each period of downtime lasting longer than [one hour], we will credit you 5% of Service fees for each period of 30 or more consecutive minutes of downtime; provided that no more than one such credit will accrue per day. Downtime shall begin to accrue as soon as you, the Customer (with notice to us, the Company) recognizes that downtime is taking place, and continues until the availability of the Services is restored. In order to receive downtime credit, you must notify us in writing within 24 hours from the time of downtime, and failure to provide such notice will forfeit the right to receive downtime credit. Such credits may not be redeemed for cash and shall not be cumulative beyond a total of credits for one (1) week of Service Fees in any one (1) calendar month in any event. We will only apply a credit to the month in which the incident occurred. Intentional blocking or limiting of data communications or other service in accordance with our policies shall not be deemed to be a failure to provide adequate service levels under this Agreement.
12.2We as a company are frequently developing, enhancing and deploying new releases. In all such cases, the customers are notified in advance, and if such deployment would result in a downtime, such downtimes will not be considered as part of uptime metrics.
12.3System SLA Metrics. System SLA's are defined by both severity of the issue and also the cause of the issue. For example, an issue may be severe, but if the cause of the issue is very difficult to solve, then it may take longer to resolve.
Item Definition
P1 Software system is inaccessible or disruption of service as a result of bug, system configuration issues, data inconsistency issue
P2 Minor usability fixes or feature requests which take less than 2 weeks to implement
P3 Major usability fixes or feature requests which take 2 weeks to 4 months to implement
MAT Mutually agreed timeline
RCA Root cause analysis
TTR Time to respond
TTF Time to fix
Priority RCA TTR TTF Total
P1 System inaccessible due to networking, operating system, cloud related issues 4 4 8
P1 Minor Bug which takes less than 1 day to fix 8 8 16
P1 Major Bug which takes more than 1 day to fix 8 24 32
P1 Software scalability issues 8 40 48
P1 Data inconsistency issues (if any) 8 40 48
P2 Minor usability fixes or feature requests which take less than 2 weeks to implement 80 MAT MAT
P3 Major usability fixes or feature requests which take 2 weeks to 2 months to implement 160 MAT MAT
12.6P2 and P3 will be taken only if the request is aligned with the roadmap of Omniful Products from a feature perspective, and is architecturally applicable.
12.7In case we need some data / responses from you to fix the P1 issue, then SLAs will be affected by the response times of the client.
You expressly agree that the exclusive jurisdiction for any claim or dispute under these Terms and or your use of the Services resides in the courts located in Dubai, United Arab Emirates, and you further expressly agree to submit to the personal jurisdiction of such courts for the purpose of litigating any such claim or action. If it turns out that a particular provision in these Terms is not enforceable, that will not affect any other provision.