> For the complete documentation index, see [llms.txt](https://docs.bdb.ai/support-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bdb.ai/support-1/bdb-support/bdb-support-for-e2e-service-built-on-platform/application-service-levels.md).

# Application Service Levels

Support to platform, applications, use cases, dashboards, and all in scope will be delivered based on the established standards.

### Incident Severity

The team will follow the below-outlined incident severity for prioritizing the incidents and activities:

<table><thead><tr><th width="222">Activities in Supplier scope</th><th>Incident severity description</th></tr></thead><tbody><tr><td>Sev1</td><td>Production system unavailable, blocking business operations, affecting multiple business units/sites.</td></tr><tr><td>Sev2</td><td>The production system is available, but business operations are blocked due to some functionality that does not work as designed.</td></tr><tr><td>Sev3</td><td>Production system available, business operations running but not at the pace they should be due to functionality not working as designed.</td></tr><tr><td>Sev4</td><td>Production system available, business operations running at a normal pace, limited user impact.</td></tr></tbody></table>

Based on the service criticality and incident severity the service level ticket priority is defined below:

<table><thead><tr><th width="200">Service Level</th><th>Incident  Severity</th></tr></thead><tbody><tr><td>Application Criticality</td><td>Sev1                   Sev2                     Sev3                          Sev4</td></tr><tr><td>Gold</td><td>P 1                      P 2                          P3                              P4</td></tr></tbody></table>

### Support Standards

All Services have the below SLA.

All supported services will have the following Business Hours and SLAs for all Incident severity.

<table><thead><tr><th width="224">Availability </th><th>Support Hours</th></tr></thead><tbody><tr><td>8X5 – Working days</td><td>9AM - 5.30PM IST time M-F</td></tr><tr><td><strong>Priority vs Response/Fix Targets</strong></td><td>P1                      P2                         P3                            P4</td></tr><tr><td>Incident Response</td><td>4 h                      8 h                        8 h                          16 h</td></tr><tr><td>Incident Resolution</td><td>8 h                      16 h                       32 h                       48 h </td></tr></tbody></table>

### Important information regarding out of office/on-call support

* If required, a separate agreement is to be signed along with resource sizing for 24x7 support&#x20;
* The customer provides WVD with VPN connectivity for support and an on-call facility. (Unavailability of WVD will have an impact on On-call support)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bdb.ai/support-1/bdb-support/bdb-support-for-e2e-service-built-on-platform/application-service-levels.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.