Software Support Policy

I. Overview

This Software Support Policy (“Support Policy”) describes the policies and procedures under which Micropsi Industries (“Micropsi”) provides technical support and maintenance services (“Support”) for its proprietary software product(s) (“Software”) to its customers who have purchased a license to the Software (each, a “Customer”).

Support is provided for the Software pursuant to the separate Master Software License, Service, and Support Agreement (“MSA”) and Order Form under which Customer has purchased Annual Support and is subject to the terms and conditions of that MSA, Order Form, and the terms of this Support Policy. Support is provided for the term specified in the Order Form. If Support is terminated, Micropsi’s obligation to provide Support will cease at that time.  

Support is provided through Micropsi’s online web-based support portal located at micropsi.zendesk.com/hc/en-us ("Support Portal”) and telephonically, as indicated on the support page.

This Support Policy may be updated by Micropsi from time to time, at our sole discretion, and sets forth expectations for Support between the Customer organization and Micropsi’s Support organization, including:

1. Who is authorized to submit issues;
2. How to submit issues;
3. What types of issues are supported; and
4. How and when Micropsi resolves and closes reported issues.

II. Definitions

1. Contact: means qualified individuals knowledgeable in the internal systems, tools, policies, and practices in use by Customer and proficient users of the Software. Customers are expected to make every effort to ensure that the individuals that are designated as authorized contacts are qualified to support the Customer teams internally.
2. Documentation: means Micropsi’s online user guides, documentation, and help and training materials, as updated from time to time, accessible via the Support Portal.
3. Incident: means each individual issue with the Software or associated products reported to Micropsi.
4. Product Releases: are specific versions of the core Software product.
5. Releases: are updates to the Software that provide: (1) new features, modifications, or enhancements to the Software; (2) updates to features, code corrections, patches, and other general updates of the Software; or (3) fixes to the Software. Releases do not include separate or different products marketed by Micropsi under a different name.

III. Scope of Support

1. What Support Includes.
   ‍
   If Customer is current on payment for the Support, Micropsi shall provide Customer with Support consisting of the following:
   ‍
   1. Ongoing access to Micropsi – MIRAI cloud services in order to update Skills with new Episodes, or create new skills;
   2. Warrantee support for third party equipment, per the terms of that manufacturer, provided to the Customer by Micropsi under an order form;
   3. Web and phone-based submissions of Incidents;
   4. Releases and Product Releases of the Software;
   5. The Documentation, including an online knowledge base of information and solutions that provides up-to date information on the Software and a forum where Customer, partners, and other users of Micropsi’s Software and other products can share information and ideas about how to use the Software;
   6. Guidance and troubleshooting to Customer in connection with questions and issues arising from the following Customer activities with respect to the Software:
      ‍
      1. Basic Configuration Issues: Micropsi will troubleshoot Customer’s configuration settings for existing installations of Supported Products (as defined below in section III.C) to ensure proper operation and connectivity.
      2. Usage Issues: Micropsi will answer Customer’s “how to” questions related to standard and intended Software usage.
      3. Efforts to Correct the Software: Micropsi will make commercially reasonable efforts to correct bugs or other errors in the Software. Customer acknowledges that Micropsi is not required to correct every bug, error, or problem with the Software that it reports to Micropsi or of which Micropsi is otherwise made aware and that Micropsi does not guarantee resolution times.
2. What Support Excludes.
   
   Customer acknowledges that if a non-supported Incident is submitted, they may be referred to their Partner of record or another authorized Micropsi Partner.  If Customer chooses to engage their Partner or another authorized Micropsi Partner, any costs associated with the resolution of non-supported Incidents will be Customer’s responsibility.  The following are excluded from Micropsi Support obligations:
   ‍
   1. Altered or modified Software, unless altered or modified by Micropsi;
   2. Software that has not been installed, operated, or maintained in accordance with the Documentation;
   3. Custom solutions or actions.
3. Software Versions Covered.
   ‍
   1. Supported Versions: Micropsi will provide Support only for the Software products specified in this Support Policy.  Micropsi supports use of the Software only as specified in the Documentation. Micropsi’s Support obligations do not cover hardware, operating systems, networks, or third-party software. Customer understands that Micropsi may need additional information as to Customer’s use of the Software during the term of this Support Policy.
   2. End of Life: Micropsi will provide Support of a Product Release or Release for nine (9) months after issuance of the end of life notice.
   3. Supported Product Versions: Micropsi will provide Support for the current and the preceding Product Release (N-1) for all on-premises, and cloud products.
4. Lapsed Support.
   ‍
   1. Support may be reinstated after any lapse due to termination or expiration of Support within six months of the lapse upon payment of a reinstatement fee equal to 20% of the then-current Support purchase.  After a lapse of more than six months, reinstatement will require the purchase of a new license in order to receive the full entitlements of a Software purchase and Support.

IV. Incident Submission and Resolution

Customer shall obtain Support by reporting Incidents. Incidents shall be tracked from initial report through final resolution.

1. Submitting Incidents
   ‍
   1. Who May Submit Incidents?
      
      Support is intended to provide assistance for issues and questions beyond what is covered in the Documentation. At the time of purchase, Customer may designate as many authorized Contacts as required.  However, anyone employed and authorized by the Customer may be added at any time through the customer portal or by submitting a request through the support process outlined in this Support Policy.
   2. Customer Obligations.
      ‍
      1. Customer will ensure that when an authorized Customer Contact submits an Incident, that individual will have full access and permissions required to troubleshoot the Incident and is authorized to make recommended changes to the Customer’s network, and/or applicable Products to help troubleshoot or resolve the issue.
      2. Customer will give Micropsi reasonable access to the Product and systems where the Software is deployed as necessary for Micropsi to determine the cause of the problem and find a resolution. Customer is solely responsible for Customer’s data, information, and software, including making back-up copies and security. Micropsi recommends Customers create backup copies of configuration files before any work is performed.
      3. Customer acknowledges that not implementing a Release may render the Software unusable or nonconforming and Customer assumes all risks arising from the failure to install such Software Updates. Even if Customer has paid the applicable fees, Micropsi will not be required to provide Support if Customer has not properly implemented all Releases provided by Micropsi.
   3. How to Submit Incidents.
      ‍
      Unless otherwise specified in a supplemental support plan purchased by Customer, Incidents are to be submitted to Micropsi by an authorized Contact through the Support Portal or via phone, based on the level of Support purchased by Customer, as outlined in the applicable Annex.
   4. How to Report an Incident.
      ‍
      In order to expedite the resolution of Incidents, Micropsi expects that Customer will make every attempt possible to:
      ‍
      1. Provide the information required in a support request, including MIRAI Controller ID, MIRAI Software Version, Robot Version, etc.
      2. Verify that the Incident is reproducible (as applicable).
      3. Provide information necessary to help Micropsi track, prioritize, reproduce, or investigate the Incident.
      4. Provide a full description of the issue and expected results.
      5. Categorize issues (technical question, defect, license request, enhancement request, etc.).
      6. List steps to reproduce the issue and relevant data.
      7. Provide any applicable log files (de-identified of sensitive data if appropriate).
      8. Provide exact wording of all issue-related error messages.
      9. Describe any special circumstances surrounding the discovery of the issue, e.g., first occurrence or occurrence after a specific event, frequency of occurrence, business impact of the problem on Customer, and suggested urgency.
      10. Identify any existing Incident number in any ongoing communications with Micropsi.
2. Support Response and Incident Resolution
   ‍
   1. Micropsi Incident Response.
      ‍
      For each Incident reported by Customer in accordance with these procedures, Micropsi shall:
      ‍
      1. Confirm receipt of the reported Incident within the acknowledgement time specified in the applicable Annex.
      2. Set a Priority Level for the Incident in accordance with the terms in section IV.B.2 below.
      3. Use commercially reasonable efforts to respond to the Incident within the time specified in the applicable Annex.
      4. Analyze the Incident and, as applicable, verify the existence of the problem(s) resulting in the Incident, which may include requesting that Customer provide additional information, logs, and re-execution of commands to help identify the root cause and dependencies of the reported issue.
      5. Give Customer direction and assistance in resolving the Incident.
      6. Keep a record of ongoing communications with Customer.
      7. Use commercially reasonable efforts to respond to the Incident in accordance with the Initial Response times set forth in the applicable Annex.
      8. Upon request of Customer, discuss Severity Level and ongoing communication time frame. Micropsi may modify the Incident’s Severity Level at its sole discretion.
   2. Severity Levels.
      ‍
      Micropsi will prioritize Incidents according to the following criteria:
      • Severity 1 (“S1”) is the highest priority and receives first attention. S1 Incidents are to be submitted when Customer cannot access the Software.
      • Severity 2 (“S2”) indicates a reported Incident where the issue has severely impacted the performance of the Software’s intended use and is causing a material and adverse impact to the Customer’s operations; or Software is not operating in a material respect within the documented functionality.
      • Severity 3 (“S3”) indicates a reported Incident where the issue has an impact on the performance and/or functionality of the Software has a minor  impact on the Customer’s operations.
      • Severity 4 (“S4”) indicates a reported Incident requesting assistance and may include questions of how to use the Software.  It may also include a reported Incident where the Software is operating within the documented functionality and Customer would like to record an idea for inclusion in future releases. Micropsi will not provide feedback on such enhancement requests, and these Support Cases are closed once the information has been recorded in our Product Request tool.
   3. Resolution and Closure of Incidents.
      ‍
      Incidents shall be closed in the following manner:
      ‍
      1. For solvable issues, depending on the nature of the issue, the resolution may take the form of an explanation, recommendation, usage instructions, workaround instructions, or advising Customer of an available release that addresses the issue.
      2. In the event that custom or unsupported plug-ins, modules, or custom code is used, Micropsi may ask, in the course of attempting to resolve the issue, that Customer remove any unsupported plug-ins, modules, or custom code.  If the problem disappears upon removal of an unsupported plug-in or module, then Micropsi may consider the issue to be resolved. Supported plug-ins or modules are defined as those listed and defined as supported in in the Documentation.
      3. For issues outside of scope as outlined in this document, Micropsi may close issues by identifying the Incident as outside the scope of Support.
      4. Dropped Issues. Micropsi may close an Incident if the Contact has not responded after two (2) weeks from the date that Micropsi requested additional information required to solve the Incident. Customer may request Incidents be re-opened. At Micropsi’s sole discretion, Incidents will be re-opened for further investigation if the Incident is deemed to be solvable.