Terms and Conditions for Maintenance and Support Services
Effective Date: April. 1, 2021
- “Business Day” means Monday through Friday in Customer’s local time zone.
- “Business Hours” means 9:00 a.m. to 5:00 p.m. on Business Days.
- “Customer Representative” means the individual employee of Customer that submits an Issue via email or the Support Portal.
- “Issue” means a failure of the Supported Software to conform to the specifications set forth in the Documentation, resulting in the inability to use, or material restriction in the use of the Supported Software.
- “Long Term Support (LTS) Release” means stable and secure Software made generally available by Imply to its end user customers who want to ensure stable workflows and applications and are not looking to be part of alpha/beta features of the Software. The LTS Release is designated by Imply by means of a change to the four-digit year to the left of a first decimal point and includes ‘LTS’ at the end (e.g.,2021.01 LTS >> 2022.01 LTS).
- “Short Term Support (STS) Release” means feature rich Software released by Imply to its end user customers with access to alpha/beta features and fine-grained feature flags and feature lifecycle control. The STS Release is designated, by Imply by means of a change to the two-digit month to the right of the first decimal point which represents the year (e.g., 2021.02 >> 2021.03).
- “Software” means the Imply Analytics Platform and its underlying components as defined in the Agreement.
- “Supported Software” means the then-current LTS Release or STS Release of the Software. The STS Release of the software is supported for one month, whereas a LTS Release of the software, is supported for two (2) years from the release date. The first year includes bug fixes and security patches and second year includes only important security patches.
- “Update” means either a software modification or addition that, when made or added to the Supported Software, corrects the Issue, or a procedure or routine that, when observed in the regular operation of the Supported Software, eliminates the practical adverse effect of the Issue on Customer.
2. Support Services
|Subscription Level1||Number of Support Contacts||Maximum Monthly Issues|
d. Issue Prioritization & Initial Response Time SLAs: When a Customer Representative reports an Issue to Imply technical support via the Support Portal, Imply shall reasonably determine the priority level of the Issue pursuant to the following definitions and take the following actions:
Issue Priority Definitions & Initial Response Times
|Issue Priority Definitions||Estimated Initial Response Times for Enterprise||Estimated Initial Response Times for Mission Critical|
|Priority Level||Definition||Enterprise 24 x 7||Mission Critical 24 x 7|
|P1||A Priority One Issue means the (a) production system is severely impacted or completely shut down, or (b) production system operations or mission-critical applications are down.||4 Hours||1 Hour|
|P2||A Priority Two Issue means (a) the production system is functioning with limited capabilities, (b) the production system is unstable with periodic interruptions, (c) there is an error in an application in development that is in final testing, facing a critical time frame of going into production use or (d) due to an Issue development efforts cannot proceed, for an application in development.||1 Day||4 Hours|
|P3||A Priority Three Issue means there (a) are errors with workaround solutions in fully operational production systems, (b) there are errors in non-critical functions, (c) there is a time sensitive concern affecting performance or deliverables, or (iv) a major subsystem under development cannot proceed due to an Issue.||2 Business Days||1 Business Day|
|P4||A Priority Four Issue means there (a) is a need to clarify procedures or information in documentation, (b) there is a request for a product enhancement or new feature, (c) cosmetic or non-functional issues; or (d) Issues in Documentation.||3 Business Days||2 Business Days|
Imply Actions & Customer Responsibilities
|Priority||Imply Actions||Customer Responsibilities|
|P1||Imply will: (a) assign specialists to correct the Issue; (b) provide ongoing communication on the status of an Update or Issue resolution; and (c) simultaneously begin work to provide a temporary workaround or fix.||All responsibilities in Section 2(h) below|
|P2||Imply will: (a) assign specialists to correct the Issue; (b) provide ongoing communication on the status of an Update or Issue resolution; and (c) simultaneously begin work to provide a temporary workaround or fix.||All responsibilities in Section 2(h) below|
|P3||Imply will use resources available during local Business Hours until the Issue is resolved, or a workaround is in place. For Issues in Third Party Software, Imply will use reasonable efforts to liaise with the applicable project steward.||All responsibilities in Section 2(h) below|
|P4||Imply will triage the request, provide clarification where possible, and may include a resolution in a future LTS or STS Release.||Customer will be expected to provide information on use case and requirements for feature requests.|
h. Customer Responsibilities: Imply’s obligation to provide Support Services is conditioned upon Customer satisfying the following responsibilities:
(i) Customer has made reasonable efforts to resolve the Issue before reporting the Issue to Imply, including having the Issue reviewed by the Customer Representative;
(ii) Customer has provided Imply with sufficient information, including any reproducible test cases requested by Imply;
(iii) Customer has installed all available LTS or STS Releases;
(iv) Customer has procured, installed and properly maintained all equipment, telephone lines, communication interfaces and other hardware necessary to operate the Supported Software;
(v) Customer has designated personnel resources to provide necessary diagnostic information until an Update or LTS or STS Release is made available;
(vi) Customer agrees to receive communications via e-mail, telephone, and other formats, regarding the support services (such as communications concerning support coverage, Issues or other technical issues and the availability of new releases of the Software and training options).
i. Escalation: If Imply’s Response to an Issue is not received within the Estimated Response Time set forth in Section 2(d), Customer may escalate according to the following escalation process:
|Escalation Level||Resolution Owner||Escalation Trigger||Escalation Path|
|1||Imply Manager, Customer Operations||Response is not received within the Estimated Initial Response Time||Customer to send email to escalations at imply.io|
|2||Imply Director of Support & Services||Response is not received within twice the Estimated Initial Response Time||Customer to call +1 4156 8587|
Imply is not obligated to provide Support Services to Customer if:
(i) the Supported Software has been changed or modified (except if under the direct supervision of Imply) or damaged; the Issue is caused by Customer’s negligence, hardware malfunction, the configuration of the platform or datacenter, network latency or causes beyond the reasonable control of Imply;
(ii) the Issue is caused by any software not licensed or delivered through Imply;
(iii) Customer has not installed and implemented all available LTS or STS Release(s) for the Supported Software;
(iv) Customer has not paid the Support Services fees when due; or Customer has already submitted the Maximum Monthly Issues in the then-current calendar month.
k. Lifecycle Policy. Imply may, at its discretion, decide to retire Software and/or Services from time to time. The Imply Lifecycle Policy is set forth at https://docs.imply.io/en/support-terms.
l. Service Terms: These Support Service terms and conditions will automatically update to Imply’s then-current terms and conditions set forth at https://imply.io/subscription-support-maintenance-terms upon renewal of the Software.