LAST UPDATED: December 2, 2020
Introduction
This Support Policies document describes Luminoso Technologies’ support levels and priorities, response times, and service levels.
Customer Support
- Luminoso offers Customer Support, outlined as follows:
| Type | Included Services | Support Channels | Response Hours | Support Fees | Response Times |
|---|---|---|---|---|---|
| Standard Support | Initial onboarding training | Email Web | M-F, 9am-5pm US ET except major holidays | Included | As defined below |
- Customers may contact Luminoso at any time via the support channels available to the level of Customer Support identified in their license agreement to submit a Support Ticket. Support tickets are created by either entering them directly in the portal (support.luminoso.com), or by emailing support@luminoso.com.
- Initial response times are dependent upon the Priority Level set by the customer at the time that they submit a Support Ticket, as follows:
| Support Ticket Priority Level | Issue Type | Initial Response Time |
|---|---|---|
| P1 | System Outage Critical feature failure | 15 minutes |
| P2 | Authentication Issues Non-critical feature failure | 30 minutes |
| P3 | General Questions Enhancement Requests | 4 hours |
- Support Ticket Workflow
- Support tickets enter the support queue in a “New” state, not yet assigned to a support representative. An automated response will be provided to evidence receipt and indicate that a support ticket is in queue.
- Ticket Status:
| Status | Description |
|---|---|
| New | Ticket has been submitted, but has not been assigned to a support representative. |
| Open | A support representative is actively resolving the matter. |
| Pending | Ticket is assigned to a support representative and is awaiting a response from the customer. Normally the client’s response is required to further process the ticket. |
| Solved | There are no outstanding questions and the reported issue is solved. Customers receive an automated email indicating that Luminoso considers the matter “Solved.” A customer may re-enter the Open Status by replying to the automated email |
| Closed | Once a ticket has been deemed Solved for four ( 4 ) calendar days with no response from the customer, it will be Closed. |
Luminoso AWS Cloud Offerings
- Uptime Commitment
- Luminoso’s goal is to maintain System Availability at 99.5%.
- Root-cause Analysis reports will be the system of record for determining System Availability.
- Exceptions:
- Problems identified by Luminoso or Company to be caused by components (hardware, software, network, maintenance), over which Luminoso has no direct operational and/or administrative responsibility and control, including, but not limited to application, database, public internet, network, and end user-controlled problems.
- An event in which responsibility or ownership of the root cause is undetermined; either as between Luminoso and Company, or Luminoso and another Ecosystem partner, unless Company provides reasonably convincing support of Luminoso’s responsibility within thirty (30) days after the end of event impact.
- Company’s failure to implement Luminoso’s reasonable written recommendations regarding issues that affect redundancy, capacity, or quality of service within ninety (90) days from the delivery of such recommendations, including any third party developed software implemented by Company.
- Force majeure events as defined in the Agreement.
- Outages involving those services determined to be non-transactional services, to include, but not limited to, hosted reporting, and service management tools.
- Scheduled Maintenance. Luminoso reserves the right to conduct maintenance during a weekly recurring maintenance schedule (Saturdays between 6AM and 8AM ET for US deployments or GMT for European deployments) unless the day and time is changed upon mutual agreement by both parties. Any Outage related to Scheduled Maintenance will not be included in the calculation Aggregate Downtime Minutes. Luminoso will notify Company in advance in the event it is required to extend a maintenance window for any reason. Luminoso reserves the right, upon three (3) days prior notice to Company, to conduct drills within the Hosted Service production environment during the standard maintenance window.
- Urgent Maintenance. Urgent Maintenance, while being conducted, may degrade the quality of the Hosted Services, or may cause an Outage of the Hosted Services. Any Outage related to Urgent Maintenance will be included in the calculation of Aggregate Downtime Minutes. Luminoso may undertake Urgent Maintenance at any time Luminoso deems necessary. Luminoso will provide notice of Urgent Maintenance to Company as soon as is commercially practicable under the circumstances.
- “System Availability” shall mean the percentage derived from the following formula:
Total Minutes in Monthly Billing Period / (Total Minutes in Monthly Billing Period + Aggregate Downtime Minutes)
- Calculating “Aggregate Downtime Minutes”: Aggregate downtime minutes shall be calculated as the number of minutes during which the Hosted Services were failing to respond to API calls, based on Luminoso monitoring applications, logs, and additional information provided by Company.
- “Total Minutes in Monthly Billing Period” means the total number of minutes during a Monthly Billing Period and does not include Aggregate Downtime Minutes as they are not billable.
- Communication
- In the case of a Failure Event, Luminoso shall use all reasonable commercial efforts to notify Customer of the Failure Event, identify the source of such Failure Event, and resolve the Failure Event as quickly as possible. Luminoso will maintain a ticket-tracking system, which will be used to record Severity 1, Severity 2 and Severity 3 events.
- Luminoso will provide email notifications to Customers of any material Outage. Notifications will be sent to the specified contact, and to any other contact identified in writing to Luminoso. Initial and update notifications will be sent at Luminoso’s discretion.
- Severity levels of Failure Events:
- “Severity 1 Event” shall mean an event in which the Hosted Service fails to successfully process at least 10% of API calls and the cause of the event is not due to any of the exceptions outlined in Section 3 of this policy.
- “Severity 2 Event” shall mean an event in which the Hosted Service fails to successfully process greater than 1% but less than 10% of API calls and the cause of the event is not due to any of the exceptions outlined in Section 2 of this policy.
- “Severity 3 Event” shall mean an event in which the Hosted Service fails to successfully process less than 1% of API calls. This level may also be assigned to an incident during which a user experiences minimal or no loss of service. This level is typically used for low-level alerts, questions, comments and enhancement requests and is resolved at the discretion of Luminoso.
- Initial and update notifications will be sent within the following intervals from event detection, based on the classification of the event.
| Severity Classification | Initial Notification | Updates, until resolved |
|---|---|---|
| Severity 1 | Within 15 minutes | Every 30 minutes |
| Severity 2 | Within 1 hour | Every 2 hours |
| Severity 3 | At Luminoso’s discretion | At Luminoso’s discretion |
Luminoso Onsite Software Release and Support
- Luminoso Onsite software releases follow a quarterly cadence with major versions occuring at most once per year.
- Luminoso will support the current and previous major version of onsite releases.
- The End of Sale for a major version will be applicable when a new major version is released.
- Upgrades will also only be supported to the next major version. For example: upgrades are supported from 1.x to 2.x, but not from 1.x to 3.x. In that case you would need to first upgrade from 1.x to 2.x, and then upgrade from 2.x to 3.x.
- Luminoso will keep the following Product release chart updated on www.luminoso.com for reference purposes.
| Version | Product | Release Quarter | Release Date | End of Support |
|---|---|---|---|---|
| 1.7 | Compass | Q1 2019 | 2019-01 | 2020-09-02 |
| 1.7 | Daylight | Q1 2019 | 2019-01 | 2020-09-02 |
| 1.8.0 | Compass | Q2 2019 | 2019-05 | 2020-09-02 |
| 1.8.0 | Daylight | Q2 2019 | 2019-05 | 2020-09-02 |
| 1.8.1 | Daylight | Q3 2019 | 2019-07-10 | 2020-09-02 |
| 1.8.2 | Compass | Q3 2019 | 2019-08-01 | 2020-09-02 |
| 2.0 | Compass | Q3 2019 | 2019-08-31 | 2021-09-02 |
| 2.0 | Daylight | Q3 2019 | 2019-08-31 | 2021-09-02 |
| 2.1 | Compass | Q4 2019 | 2019-11-30 | 2021-09-02 |
| 2.1 | Daylight | Q4 2019 | 2019-11-30 | 2021-09-02 |
| 2.2 | Compass | Q1 2020 | 2020-02-29 | 2021-09-02 |
| 2.2 | Daylight | Q1 2020 | 2020-02-29 | 2021-09-02 |
| 2.3 | Compass | Q2 2020 | 2020-05-31 | 2021-09-02 |
| 2.3 | Daylight | Q2 2020 | 2020-05-31 | 2021-09-02 |
| 3.0 | Daylight | Q3 2020 | 2020-09-02 | 2022-09-01 |
| 3.1 | Daylight | Q4 2020 | 2020-11-30 | 2022-09-01 |
| 3.2 | Daylight | Q1 2021 | 2021-03-04 | 2022-09-01 |
| 4.0 | Daylight | Q3 2021 | 2021-09-01 |