Exhibit A - Service Level Agreement

Technical Support

Under this agreement, monitoring by Company personnel of the Cuick Trac environment will occur on a 5-days a week (Monday – Friday) basis with service hours of 8:00am-6:00pm CST. Remediation services will be provided only during business hours unless otherwise specifically stated in the SOW. Company will respond to problems, errors, or interruptions in the provision of the Services in the timeframe(s) described below. Severity levels will be determined by Company at its reasonable discretion and in accordance with industry best practices. All remediation services will initially be performed remotely; Company will provide onsite service only if remote remediation is ineffective and, under all circumstances, only if covered under the Service plan selected by Customer.


All time frames are calculated as of the time that Company is notified of the applicable issue / problem by Customer through Company’s designated support portal, help desk, or by telephone. Notifications received in any manner other than described herein may result in a delay in the provision of remediation efforts. Help desk support provided outside of Company’s normal service hours will be billed to Customer at the hourly rate of $130/ hour (2- hour minimum applies), and support provided between 11:00pm-6:00am CST will be billed to Customer at the hourly rate of $500/ hour. For support to locations in significantly different time zones, 2+ days notice for anticipated priority support is recommended. Support requiring on-site visits will be billed to Customer at the flat rate of $2000/ day, plus expenses (based upon the approved United States Federal Government Per Diem rate for that fiscal year), only if pre-approved in writing by Customer.

Service Level Defaults

In the event of a Service Level Default, the corresponding Service Level Credit will be creditable to Customer; provided, however, that in no event will the total amount of Service Level Credits creditable to Customer for a single month exceed the “At Risk Amount” for that month.

If Company believes that a Service Level Default should be excused, then Company will so state in the applicable Service Level Report. In the applicable Service Level Report, Company will also indicate the following:

1. Which Service Levels are affected by the exemptions and the calculation of the actual performance values of the affected Service Levels, both with and without taking into account the effect of the excuses concerned; and

2. All of the circumstances that give rise to the claimed exemption, in sufficient detail to permit Customer to evaluate whether Company’s claim of exemption is valid.

At Risk Amount

In no event will the total amount of Service Level Credits in a single month exceed, in total, 75 percent of the aggregate amount of all Cuick Trac Enclave Charges for the applicable month (the “At Risk Amount” for the applicable month) within the first year of the Agreement. The At Risk Amount will reduce to 50 percent after the first year.

 

Service Level Credits

For purposes of calculating the Service Level Credit, Customer will allocate a certain number of points (“Service Level Credits”) to each of the Service Levels; provided, however, that the aggregate Credits allocated among all Service Levels will not exceed 100.

Service Level Credits will be calculated monthly. Customer will be entitled to a Service Level Credit for each Service Level Default that occurs during such month. Any Service Level Credits will begin to accrue for Service Level Defaults three (3) months after the Service Commencement Date for the applicable Service Level.

For Service Level Defaults, each Service Level Credit is equal to the product of: (1) the Service Level Credits applicable to the affected Service Level, divided by 100, multiplied by; (2) the “At Risk Amount”. Below is a sample calculation.

If Company has failed to meet a Service Level during the prior month; to which Customer has allocated 30 Service Level Credits; and Company’s total Cuick Trac Enclave Charges to Customer for such month for the Services are $10,000, the applicable Service Level Credit would be computed as follows:

(Service Level Credits / 100) X “At Risk Amount” = (30 / 100) X (Cuick Trac Enclave Charges X 75%) = (30 / 100) X ($10,000 * 75%) = $2,250

Service Level Credits will be calculated and paid monthly and adjusted in the invoice for the applicable month.

 

Internet Service Connection

The Cuick Trac secure virtual enclave requires an active internet service provider (“ISP”) connection for access. Based upon individual needs, it is strongly recommended that Customer obtain a primary and secondary ISP with automatic fail-over to prevent loss of connectivity. Customer understands and agrees that Company has no control over ISP services and shall not be held liable for any loss or work stoppages caused by ISP outages and Company shall be held harmless in the event of any such losses.  Any IP addresses provided to Customer by Company during the term of the Agreement are managed by Company and Company will retain these IP addresses after termination of the Agreement, meaning that they may not be transferred or utilized by Customer after termination of the Agreement.

White Listed Software

Software that is not on the Cuick Trac approved white-list, but may be in use in the Customer’s networks, will be analyzed for security concerns and explicitly approved on a case-by-case basis. Company cannot and will not provision software that creates unmitigated vulnerability within the environment.

Customer understands and agrees that software that is not part of the Cuick Trac whitelist may pose additional risk to Customer’s environment. To the extent Customer requests Company to implement non-whitelisted software, Customer accepts the incremental risk inherent to such software.  The Company is not liable for software implemented at Customer’s request.

Patch Management

Company shall keep all managed and/ or hosted equipment and software current with critical patches and updates (“Patches”) as such Patches are released by the manufacturers of the applicable hardware or software. Patches and updates are developed by third party vendors and, on rare occasions, may cause system instability. Company shall refrain from installing a Patch if Company is aware of technical problems caused by a Patch, or believes that a Patch may render the System, or any portion of the System, unstable or present an information security vulnerability or may otherwise create a NIST 800-171 compliance violation without Customer’s prior consent.

Service Level Descriptions

This shows the descriptions of the required Service Levels.

1) Incident Response Time

Service Level Description
Measures the percentage of Incidents where Company Responds to Incidents within the Required Timeframe, depending on priority
Monitoring Interval
Monthly
Service Level Credit
20
Formula
Number of Incidents during the Month to which Company Responds to within the Required Timeframe, divided by the number of Incidents for the corresponding Priority, with the result expressed as a percentage to two decimal places For purposes of this Service Level: “Response” means a Ticket for the applicable Priority Incident has been opened and assigned to Company Personnel for Resolution “Required Timeframe” means: With respect to Response from Company after notified by Customer through designated support portal during service hours: - Priority 1 Incident within 1 hour - Priority 2 Incident within 4 hours - Priority 3 incident within 1 business day - Priority 4 incident within 3 business days
Service Level Metric
Measured Separately for Response and Resolution ≥ 98.00% within the Required Timeframe for Priority 1 ≥ 93.00% within the Required Timeframe for Priority 2 ≥ 90.00% within the Required Timeframe for Priority 3 ≥ 90.00% within the Required Timeframe for Priority 4

2) Incident Resolution Time

Service Level Description
Measures the percentage of Incidents where Company Resolves such Incidents within the Required Timeframe, depending on priority
Monitoring Interval
Monthly
Service Level Credit
30
Formula
Number of Incidents during the Month to which Company Resolves such Incident within the Required Timeframe, divided by the number of Incidents for the corresponding Priority, with the result expressed as a percentage to two decimal places For purposes of this Service Level: “Resolve” means the Services that were the subject of the Incident have been restored to normal use and operations “Required Timeframe” means: With respect to Resolution after Company was notified through designated support portal during business hours: - Priority 1 Incident within 3 hours
- Priority 2 Incident within 8 hours - Priority 3 incident within 1 business day - Priority 4 incident within 2 business days 
Service Level Metric
Measured Separately for Response and Resolution ≥ 98.00% within the Required Timeframe for Priority 1 ≥ 93.00% within the Required Timeframe for Priority 2 ≥ 90.00% within the Required Timeframe for Priority 3 ≥ 90.00% within the Required Timeframe for Priority 4  

3) Availability

Service Level Description
Measures the percentage of time that each System is Available
Monitoring Interval
Monthly but only between 7:00am-6:00pm CST on weekdays excluding holidays
Service Level Credit
40
Formula
Total time a System is Available plus Planned Downtime divided by total time during the Month with the result expressed as a percentage to two decimal places For purposes of this Service Level: “Available” means the System is operational, functional and usable to End Users/Applications “Planned Downtime” means the time during the Month when, as notified by Company to Customer, the System will not be Available in order to implement upgrades, repairs and other changes
Service Level Metric
≥ 99.5% Availability for System measured in aggregate and no more than 1 System having an individual Availability of less than 99% If any downtime is incurred due to underlying infrastructure outside the control of the vendor, then that downtime is not counted as not Available.

Services Provided

ID
Task/ Function
Description
1.
System Administration
Company will perform system administration activities for the technological environment in scope, including but not limited to: i. managing access privileges. ii. creating new user accounts and groups with appropriate security access. iii. administering passwords and IDs. iv. disabling and re-enabling functionality when security actions require shutting down functionality to address issues. v. purging operational records, files, and accounts.
2.
Priority 1 Outages
For all Priority 1 Outages, Company will, as part of the documented Incident, Event, and Problem Management: i. notify Customer of Outage detection. ii. open an Incident Resolution Bridge with Customer. iii. provide a summary description of the Outage, including an initial assessment of the Outage, the corrective action required from Company and an estimated time frame for service restoration. iv. provide Customer updates. v. perform appropriate communication in accordance with the Event management process. vi. coordinate with Service Desk to ensure hot news broadcasts address Priority 1 Outages.
3.
Emergency Services Needs
Company will apply an appropriate level of effort, resources, and commitment to resolving Emergencies. Customer and Company will form rapid response teams to immediately identify the underlying cause of the Emergency, work to eliminate or mitigate the impact and seek ways to prohibit or minimize the reoccurrence. Rapid response teams will be comprised of Company management and senior technical subject matter experts as the emergency warrants.

Service Ticket Priorities

Ticket Priorities: All tickets are worked from highest priority to lowest priority and from oldest to newest. Service hours are from 8am-6pm CST.

 

P1 – Priority 1: Critical

Examples of P1:

●       Large degradation of service impacting most or all of the business.

●       Server Down

●       Network Down

●       Email Down

●       Fire, flood, etc.

P2 – Priority 2: High Priority

Examples of P2:

●       Backups failing ≥ 3 days in a row

●       Company communications, IE email, being down

●       Critical use workstation down

●       Customer has requested service be completed within 24 hours

●       Ticket has been open for more than 60 days

P3 – Priority 3: Medium Priority

Examples of P3:

●       Backups failing ≥ 2 days in row

●       New user provisioning

●       One or more users productivity is hindered

●       Problem is inconveniencing multiple users

●       Workstation down

●       Customer has requested service be completed within 48 hours

●       Ticket has been opened for more than 30 days

P4 – Priority 4: Low Priority

Examples of P4:

●       Any item not having met the criteria for P1, 2, or 3 and not specifically requested by the Customer to be higher priority than to be done on a monthly maintenance period

●       Scheduled work for the Customer

●       Monthly maintenance, updates, etc.