This Service Level Agreement (SLA) sets the commitment that prevails between the Division of Information Technology and each university academic, administrative, and programmatic unit, as they are mutually understood by their primary stakeholders. This Agreement remains valid until superseded by a revised or new agreement mutually endorsed.
Either party may terminate the SLA within 60 Days business days notice.
This is a Service Level Agreement (SLA) between the Customer and UMD Division of Information Technology (DIT) to document the provision of:
DIT services are documented in the IT service catalog.
The CUI Environment is a compliant and secure computing environment that is used for the storage, viewing, and manipulation of data and information that the National Archives has designated as ‘CUI’. Specifically, the CUIE is designed to meet the guidelines of NIST SP 800-171.
CUIE Research Team responsibilities:
In addition, DIT provides infrastructure, staff, and processes including:
The primary stakeholder associated with this SLA are the DIT Research Computing team, and the Primary Owner, Approver, and Team Members listed in the Service Catalog Hosting CUIE Dashboard.
UMD IT responsibilities and/or requirements in support of this SLA include:
Customer responsibilities and/or requirements in support of this SLA include:
The CUIE is available for use 24 hours a day and 7 days a week except for periods of planned maintenance (Last Monday of the month 9 am to 11 am).
Planned maintenance and emergency maintenance situations.
If you are not satisfied with the level of service on a request, please contact the Service Owner and if necessary, the DIT Service Manager identified in Section 3.1.
A Service Request is defined as a request for information, or advice, or for a standard change or for access to a service.
Service Requests can be submitted through the IT Service Catalog or by calling the DIT Service Desk (301.405.1500). Current hours of operation are listed on the DIT Support Home Page identified in Section 5.2.
DIT’s objective is to acknowledge and assign Requests within 4 business hours of receipt. Requests will be fulfilled within five (5) days.
Campus priorities may require exceptions during certain times of the Academic year.
The CUI Environment is backed up on a daily schedule in order to support recovery from disaster scenarios. In the event of a catastrophic loss to the CUI Environment, a full recovery will be possible within 5 days, following the restoration of existing, or procurement of new, appropriate hardware.
Data recovery requested related to user deletions or error will be processed on a best effort basis, with restoration expected within 2 business days. Individual file recovery is not possible due to the encryption mechanisms of the system. Instead, full Vault or Drive recovery is used.
An incident is defined as any interruption in the normal functioning of a service or system.
Incidents can be reported to the DIT Service Desk (chat, 301.405.1500) during business hours. Current hours of operation are listed on the DIT Support Home Page identified in Section 5.2. Incidents may also be reported via email to itsupport@umd.edu.
Time spent on resolving Incidents that are customer caused will be billed at current hourly rate, including travel.
All reported incidents receive a priority number based on the impact and urgency of the service interruption.
Impact is determined based on the number of people/departments/buildings that are affected by the interruption or outage. Life-Safety issues are taken into consideration for assessing and assigning priorities.
Urgency is based on the acceptable delay to restore the service, based on the nature of the service outage.
DIT may prioritize incoming incident requests as P1 or P2 priority if it meets one or more of the following criteria:
SLA Targets are in Business Hours, unless otherwise specified in a specific service SLA, and Incident Response occurs M-F between 8 am and 5 pm, excluding UMD holidays and closure.
|
Priority |
Initial response to user and assignment of ticket to work group |
Resolution |
|---|---|---|
|
P1: Critical |
15 minutes |
4 hours |
|
P2: High |
1 hour |
8 hours |
|
P3: Normal |
4 business hours |
1 business day |
|
P4: Low |
4 business hours |
5 business days |
|
P5: Hold |
4 business hours |
No target |
The Maintenance Window for CUI Environment is published in the “Terms of Service” section of the service entry in the IT Service Catalog.
DIT reserves the right to modify the maintenance window with adequate notice.
The CUI Environment is provided at no cost to the researchers with approved uses, and when standard resource sets listed below are used. In some limited circumstance, there may be costs associated with project setup and customization of virtual machines beyond typical project setup and/or when non-standard configurations are required.
Researchers may choose from the following standard sets of resources:
4 CPU, 16 GB RAM
8 CPU, 32 GB RAM
16 CPU, 128 GB RAM
Storage requirements are determined per request typically not to exceed 10 TB.
Researchers may choose from Linux and Windows based operating systems, and the following standard set of software is provided on these systems:
Windows Software:
Linux Software:
Consulting hours may be charged when significant configuration changes are requested by a PI for their project that differ from default packages.
Consulting - $100 per hour.
The Customer will provide notice in writing of intent to discontinue use of service.
The Customer will provide the Division of IT a valid Driver Worktag in order to bill for services in the event billing is required.
Prices are subject to change on an annual basis.
Data should be described and listed in the request form for CUIE service, and should include all contractually obligated data protections. (In addition to local and Federal law, these requirements may be part of a Data Use Agreement you have signed, part of a Data Management Plan you have prepared, or part of an agreement with a sponsor or client).
The Service Owner is responsible for facilitating reviews of this document. Contents of this document may be amended as required, provided mutual agreement is obtained from the primary stakeholders and communicated to all affected parties.
Three weeks prior to the expiration of the Service Level Agreement, the Research Computing team will contact the Primary Owner or other designate, to notify of upcoming expiration. The Primary Owner may choose to renew the project for another term, or reject the request. Failure to renew will result in the project close out process to commence, which may include account deactivation, deletion, and removal of all data.
|
Version |
Date |
Author |
Revision notes |
|---|---|---|---|
|
1.0 |
4/15/2020 |
Sam Porter |
First Draft |
|
1.1 |
7/1/2020 |
Sam Porter |
Updated Introductory Pricing |
|
1.2 |
1/3/2021 |
Sam Porter |
Added section for data description |
|
1.3 |
9/22/2021 |
Sam Porter |
Added section to describe end of SLA procedures. |
|
1.4 |
1/26/2022 |
Sam Porter |
Moved Version info to the end of the document. |
|
1.5 |
11/05/2024 |
Prabhjot Sidhu |
Updated software versions |