Service Level Agreement (SLA)
Each tier of feature service provides increasing levels of support and service assurances that are aligned with the capability of DLH.io to support our customers.
The table(s) below provide a breakdown of each service feature tier align with the respective SLA attributes that will allow each customer to understand expectations surrounding use of the DLH.io service.
These SLA's are backed by the DLH.io Support Team, so that when an support ticket is submitted by a customer regarding an issue, bug, or other unexpected behavior of the platform, our team is ready to receive and handle the requests to resolution. Customers can report incidents and submit support requests via our DLH.io Support Portal, https://support.datalakehouse.io. We maintain a team of engineers and support technicians that provide a sufficient balance for ticket triage and ticket resolution handling for our growing customer base.
If DLH.io is unable to maintain the service levels for each Service offerred as described further in this SLA, then the Customer may be eligible for a credit which may go towards its monthly service fees. This SLA may be updated from time to time where the most recent version of this is found in the legal section of our website, httpss://datalakehouse.com/legal/
Core Service Name
Monthly Uptime %
Core Web Application
This is the main UI access point
The developer API used to interact programatically with DLH.io
Dashboards representing DLH.io analytics applications marketplace items
Models related to the transformation of data for application specific ontologies
This is the time it takes for a support agent to respond via email to any issue once submitted by a customer. Requests for support must be submitted via the DLH.io support portal in order to qualify for the response times and SLAs outlined.
Initiate Response Times
One of our DLH.io agents will respond to your support ticket request in accorance with the ticket severity as outline in this table:
Business Critical Plan
(Urgent & Production Delays)
Where any part of the reported feature has an impact to your production systems have a significant risk of loss due to issues with the platform.
Level 2 (High Priority)
An effective result of the platform's current status is affecting the ability to use the DLH.io solution for it's desired and already incorporated process results. A work-around may be temporarily in place but a solution needs to be delivered quickly.
Level 3 (Issue/Bug)
Functionality in the desired use of the platform is mainly accessible and operational, however some functionality of the DLH.io platform appears to have a moderate or low impact on performance expectations.
Level 4 (Low Priority)
Some functionality in the platform seems to be having an impact on desired behavior or utility. However, the impact is minimal as it relates to critical systems or use of a specific feature.
Maintenance windows are periods of time where updates (new features, fixes, enhancements, etc.) are made to the platform.
Our attempts to provide several days, often a week's, advance notice of maintenance to the platform. For potential break-fix updates the platform will use times of the day where the least amount of activity on the platform is taking place.
Customers with custom or decicated environments (usually those on the Business Critical plan(s)) may have additional options to delay maintenance windows in order to ensure their processes or maintenance windows can be in alignment.
While we have solid platform update processes in place, the typical maintenance window only last between 1-2 hours, with a maximum maintenance window of 8 hours. During maintenance windows customers are encouraged to communicate to their users any potential downtime that may result from data freshness delays.
If there are any concerns regarding maintenance windows please submit a ticket to our Customer Support portal.