Service Level Expectations (SLE)

1. Purpose

This Service Level Expectation (SLE) sets the shared expectations between Western Michigan University Information Technology (IT) and the WMU community. Our first priority is supporting students and the services that students, faculty, and staff rely on to learn and teach.

The SLE is built on three commitments.

  1. IT to the WMU community: what the community can expect from IT.
  2. The WMU community to IT: what IT needs from the community to provide effective service.
  3. IT to IT: the working practices IT teams build together so the community has a consistent experience.

Our standard

These expectations are the common standard for how WMU IT and the WMU community work together.

Sections 1 through 8 contain core commitments that rarely change. Variable details, such as hours, targets, and timeframes, are listed in Appendix B to allow for review and updating as necessary. When a new service, team, or function becomes part of WMU IT, it aligns with these expectations.

The standard is simple. The WMU community should experience one IT that is reliable, accessible, secure, accountable, and focused on the mission of Western Michigan University.  Key terms for understanding this SLE are defined below; additional terms and definitions can be found in Appendix A:

Key TermDefinition
Support CaseThe formal record created for each interaction with IT, including incidents, service requests, questions, consultations, and other requests for assistance.
RequesterAn individual affiliated with WMU, such as a student, faculty member, staff member, alum, or affiliate, who requests a service or submits a support case to WMU IT.
PriorityThe relative order in which work is addressed based on a combination of impact, urgency, risk, and institutional importance.
Critical Academic PeriodA period identified in the academic calendar when instructional and student-facing services are particularly sensitive to disruption. Critical academic periods include the first two weeks of an academic term, add/drop periods, registration, midterm examinations, final examinations, grade submission periods, and commencement activities.

2. Scope

This SLE applies to IT services and support provided to the WMU community, including faculty, staff, students, alumni, retirees, and other affiliates as defined by service eligibility requirements. It applies to the services in the IT service catalog and to the IT teams that deliver and support them.

Individual services may have additional service levels, requirements, or procedures. Those service-specific expectations supplement this SLE. Where the service catalog lists a different target or procedure for a service, the service-specific information applies to that service.

Core services for the WMU community

Every active WMU student, faculty member, and staff member has access to a core set of technology services, including network and Wi-Fi connectivity, a university account and email, file storage, and collaboration tools. The service catalog lists what is available by request, and what carries an additional cost. Access depends on active affiliation and on following university policies, and it changes or ends according to the university’s account lifecycle practices. Alumni, retirees, and other affiliates receive the services the catalog lists for their group. 

3. Our Priority: Students, Teaching, and Learning

When priorities compete, IT shall first protect the university, then support teaching and learning, and finally ensure the continuity of essential business operations. This approach ensures that the services most critical to student success and institutional continuity receive the highest level of attention during periods of constrained resources. 

Priority Decision Matrix

Priority TierService CategoryExamples
1Security, Safety, and ComplianceCybersecurity incidents, data breaches, identity compromise, life-safety systems, regulatory compliance issues
2Academic Mission-Critical ServicesLMS, student information systems, recruitment systems and cycles, registration, network, authentication, email, classroom and laboratory technology, advising systems, network and storage infrastructure, authentication systems, machine room systems and supports
3Core Administrative ServicesPayroll, benefits, financial aid, billing, accounting, finance, procurement, and financial reporting
4Individual Student and Faculty SupportIndividual access issues, workstation support, instructional technology support, faculty and student service requests
5Research and Sponsored ProgramsResearch systems, grant-supported services, funded agreements, compliance-related research activities
6Administrative and Business ServicesDepartmental applications, reporting systems, and other administrative operations
7Enhancements and Strategic InitiativesNew features, upgrades, optimization efforts, technical debt remediation, and project work

Priority Adjustment  

A support case shall be elevated by one priority level when it impacts an active class session, examination, grade submission deadline, a student's ability to register, make payments, or access coursework, or a faculty member's ability to teach.

During designated Critical Academic Periods, this uplift shall apply to all student-facing and instructional services. During designated Critical Operational Periods, it shall apply to affected core administrative services.

When multiple support cases share the same priority level, precedence shall be given to cases affecting students, instruction, and faculty teaching. Cases affecting core administrative services shall be addressed next, followed by all other work based on impact, risk, and scope of disruption.

Critical Period Management 

Critical Academic Periods and Critical Operational Periods, as defined in Appendix A, require elevated operational readiness. During these periods, IT shall:

  • Align staffing and on-call schedules with anticipated peak periods.
  • Restrict non-essential changes to affected systems and services.
  • Increase monitoring of critical services.
  • Accelerate incident response and escalation procedures.
  • Prioritize service restoration activities consistent with this SLE. 

4. IT Commitment to the WMU Community

4.1 Service Information and Access

The IT Service Catalog is the primary source of information about WMU IT services and service offerings. Where available, each service includes eligibility requirements, access and request procedures, support information, applicable costs, support boundaries, and service-specific expectations.

IT makes reasonable efforts to keep the catalog accurate and accessible. If information is missing or unclear, the WMU community may contact the Help Desk for assistance. The absence of a service from the catalog does not, by itself, determine whether IT supports that service.

4.2 Getting Help

Contact MethodDetails
HoursCurrent hours of operation can be found at https://wmich.edu/it/helpdesk. Extended or weekend hours during peak periods, such as the start of a term, are announced in advance.
Phone(269) 387-4357
Email@email
goWMUVisit go.wmich.edu and choose the "Contact Support" button.
Drop-inSecond Floor, University Computing Center
Self-help Articleshttps://go.wmich.edu/s/

For non-urgent requests, use goWMU so your request is tracked. For urgent issues, calling the Help Desk is the fastest way to receive assistance.

Audio Visual and Classroom Technology Support

If classroom technology is not functioning as expected or is preventing an instructional session from proceeding during scheduled classes, use the contact methods listed in section 4.2 “Getting Help” to report the issue and receive immediate troubleshooting assistance during supported hours. These incidents will be prioritized in accordance with the incident priority levels and response expectations defined in Appendix B.1. Support personnel will assess the issue and escalate to the appropriate responsible IT area to restore classroom functionality as quickly as possible, implementing an appropriate workaround when a full resolution cannot be achieved immediately. Support will continue until the issue is resolved, a suitable workaround is established, or the incident is transitioned to the appropriate support team.

4.3 Communication

IT communicates clearly, respectfully, and in plain language. For significant outages, degradations, and planned changes, IT shares what is affected, who is affected, what users should do, available workarounds, what IT is doing, and when to expect the next update. When a student-facing or instructional service is affected, students and faculty are notified first.

For Priority 1 (P1) incidents, WMU IT shall issue an initial notification upon confirmation of the incident through the IT Status Page and designated university communication channels. Status updates shall be provided at the frequencies defined in Appendix B. WMU IT shall issue a final notification when service is restored; the incident is resolved, or a stable workaround has been established.

Planned maintenance and other service-impacting changes shall be communicated in advance through the IT news page and other designated communication channels in accordance with the notice periods established in Appendix B. Emergency changes that cannot meet standard notice periods will be communicated as soon as practicable.

4.4 Security and Privacy

IT protects university technology and information and operates services in accordance with university requirements. IT responds to significant disruptions and security concerns and applies appropriate security and privacy practices.

4.5 Professional Conduct

IT provides professional, courteous, and respectful service. IT is honest about what is known and not known, what can and cannot be provided, delays and dependencies, and changes in expected resolution.

4.6 Clear Support Case Ownership

The individual receiving a support request retains accountability for its progress toward resolution, including coordinating handoffs, ensuring follow-through, and maintaining continuity until responsibility is explicitly transferred. These commitments to the community hold no matter how IT is organized.

5. WMU Community Commitment to IT

5.1 Use Established Channels

Members of the WMU community use the service catalog and the support channels in section 4.2 whenever possible. Established channels let IT track requests, prioritize work, keep service history, and spot broader needs. 

5.2 Provide Accurate Information

Requesters provide what IT needs to understand and resolve an issue, including what happened, when it occurred, what they were trying to do, who is affected, any error messages, what has already been tried, and accurate contact information so we can effectively communicate and work toward a solution. 

5.3 Respond and Participate in Resolution

Requesters respond when IT needs additional information, access to a device or system, testing, approval or decision, or confirmation that an issue is resolved. Timely responses help IT investigate issues and complete requests. 

ActivityRequester Expectation
Information, access, testing, approvals, or decisionsRequesters shall respond within 2 business days unless a shorter timeframe is communicated due to service impact or urgency.
Follow-up on support casesIf WMU IT is unable to proceed because requester action is required, WMU IT shall make at least two attempts to contact the requester over 5 business days before closing the support case. If the requester's default contact method relies on a channel affected by the reported issue or otherwise unavailable to them, WMU IT shall use an alternative contact method.
Confirmation of resolutionRequesters should confirm whether the issue is resolved within 3 business days of notification. If no response is received, WMU IT may close the support case as resolved.
Reopening a closed support caseRequesters may reopen a closed support case within 10 business days of closure. After that period, a new support case may be required.

When IT is waiting for information or action from the requester, progress toward applicable resolution targets is paused.

5.4 Follow University Technology and Security Requirements

Members of the WMU community follow university requirements on acceptable technology use, information security, data handling and privacy, account and credential security, university-owned technology, and required cybersecurity training. Suspected security incidents, compromised accounts, lost devices, and other security concerns are reported immediately. 

5.5 Involve IT Early

The WMU community involves IT when purchasing, adopting, integrating, or significantly changing technology that connects to university systems, handles university information, is used to conduct university business, or needs ongoing university technology support. Early involvement lets security, privacy, accessibility, integration, licensing, support, and sustainability be addressed before they become problems. A good first step is to consult your IT support representative. 

5.6 Understand Support Boundaries

Support levels vary by service and are defined in the IT Service Catalog and applicable service documentation.

Support CategoryCommunity Expectation
Fully SupportedWMU IT provides support for eligible university-owned devices, university-managed services, and enterprise applications within documented service boundaries and service levels.
Best EffortWMU IT provides reasonable assistance with access to university services from personally owned devices but cannot guarantee support for the device, operating system, or third-party software.
Not Supported or ReferredWMU IT generally does not support personal technology unrelated to university services or products outside its support responsibilities. When appropriate, WMU IT may refer users to another support provider or resource.

5.7 Treat IT Staff with Respect

IT staff are treated with courtesy and respect. Questions, concerns, and disagreements about IT services are welcome and are raised through the channels in section 7. 

6. IT Commitment to IT

WMU IT teams work together to provide consistent, coordinated, and accountable service to the WMU community. Internal team structures and responsibilities do not change the community's expectations under this SLE.

6.1 Support Tiers

Support tiers are levels of IT support organized by the expertise, access, and authority required to fulfill a request or resolve an incident. Support tiers are used to route work to the appropriate resources while maintaining clear ownership, communication, and accountability throughout the lifecycle of the support case. Escalation between tiers does not transfer accountability for ensuring the case progresses toward restoration or resolution.

TierWhoResponsibilities
Tier 0Self-ServiceKnowledge articles, service catalog information, status information, automated tools, password management tools, and other resources that enable users to address common needs independently.
Tier 1Help DeskPrimary point of contact for support. Logs and categorizes cases, performs initial diagnosis and troubleshooting, fulfills standard requests, communicates with requesters, and resolves cases using documented procedures whenever possible.
Tier 2Specialist Support TeamsIncludes desktop support, college and department IT, identity and access management, network services, and application support teams. Handles issues requiring specialized technical expertise, elevated access, system-specific knowledge, or location-specific support.
Tier 3Engineering Teams and Service OwnersResolves complex technical issues requiring advanced troubleshooting, root cause analysis, system-level changes, configuration modifications, development activities, or service owner decisions.
Tier 4Vendor or External SupportProvides expertise, support, access, fixes, or actions that can only be delivered by external vendors, cloud providers, or third-party service providers.

6.2 Escalation

Escalation is the transfer of a support case to the team or support tier with the expertise, access, authority, or resources required to advance resolution. Escalation shall be used to improve service outcomes and restore service as quickly as possible. It shall not be used solely to transfer workload, clear queues, or defer ownership.

The team receiving a support case remains accountable for taking appropriate action, and WMU IT remains accountable for coordinating resolution across all participating teams. Escalation shall not restart or extend any applicable response or resolution targets. 

A support case shall be escalated when one or more of the following conditions apply:

  1. Expertise or Access – Resolution requires technical knowledge, permissions, privileges, or system access not available to the current support tier, and all documented troubleshooting procedures appropriate to that tier have been completed.
  2. Impact – The support case is classified as Priority 1 (P1) or Priority 2 (P2), affects multiple users, disrupts a critical service, or significantly impacts instruction, research, business operations, or student success. P1 and P2 incidents shall be routed to the appropriate specialist teams immediately and, where practical, worked in parallel.
  3. Security – The support case involves, or is suspected to involve, a cybersecurity event, compromised account, unauthorized access attempt, malware infection, data exposure, or other information security concern.
  4. Dependency – Resolution depends on action, information, or coordination from another IT team, university department, vendor, cloud provider, or external service provider.
  5. Authority – Resolution requires a technical, business, risk, or service-level decision that exceeds the authority delegated to the current support tier.
  6. Time at Risk – The support case has consumed approximately 50% of its applicable resolution target without a clear and achievable path to resolution, requiring additional expertise, coordination, or management attention.

Misrouted Cases

When a support case is submitted or assigned to a team that does not support the request, the receiving team shall reassign it directly to the correct team within one (1) business day, with notes describing the issue and any work already completed. The case shall not be returned to the requester or the previous team unless the correct team cannot be identified, in which case it shall be returned to the WMU Help Desk, which retains ownership until it is placed with the right team. Reassignment does not reset the response or resolution clock.  

Management Escalation

In addition to technical escalation, support cases may be escalated to WMU IT leadership when service restoration is at risk, resolution targets are unlikely to be met, significant business impact exists, or cross-team coordination is required to remove barriers to resolution. 

7. Raising a Concern

A requester may raise a concern when a support case is not progressing as expected, a service target has not been met, the assigned priority appears incorrect, or the service experience is unsatisfactory.

Concerns may be submitted through the Help Desk or by replying to an existing support case. Raising a concern does not replace established support or escalation processes and does not interrupt work toward resolution.

WMU IT shall acknowledge the concern within one (1) business day, identify the individual or team accountable for review, and provide an expected timeframe for the next update. Accountability for the concern remains with the assigned service owner or support manager until the concern has been reviewed, addressed, and the outcome communicated to the requester. Escalation or reassignment of work does not transfer this accountability unless ownership is formally reassigned. 

8. Exceptions

Service expectations may be affected by circumstances outside WMU IT’s reasonable control, including vendor outages or delays, third-party service disruptions, utility or infrastructure failures, emergency security events, university closures, and natural disasters or other significant events.

When an exception affects service, WMU IT remains responsible for communicating the impact, coordinating with the vendor or provider, offering a workaround where one exists, and sharing a revised expectation when practical. 

Appendix A: Definitions

The following terms are used throughout this SLE and are listed in alphabetical order.

Business Day: Monday through Friday, excluding university holidays and closures.

Business Hours: 8:00 a.m. to 5:00 p.m. local time. Business hours are used for measuring applicable service targets unless otherwise specified. Service hours for individual services may differ.

Concern: A request for review when a requester believes service has not met established expectations. Concerns are distinct from support case escalations and are described in Section 7.

Core Administrative Service: A business-critical administrative or financial service that supports the university's daily operations, such as payroll, benefits administration, student financial aid, student billing, accounting, and financial reporting. The current list of core administrative services is provided in Appendix B.6.

Critical Academic Period: A period identified in the academic calendar when instructional and student-facing services are particularly sensitive to disruption. Critical academic periods include the first two weeks of an academic term, add/drop periods, registration, midterm examinations, final examinations, grade submission periods, and commencement activities.

Critical Operational Period: A period during which a core administrative service is particularly sensitive to disruption due to time-bound business requirements. Examples include payroll processing, benefits open enrollment, financial aid disbursement, fiscal year-end activities, tax filings, and audit deadlines. Applicable dates are established by the responsible business unit.

Escalation: The transfer of a support case to a higher support tier, specialized resource, or management level to obtain the expertise, access, authority, or attention required for resolution. Escalation procedures are described in Section 6.

Impact: The extent to which service disruption affects university operations, users, or business functions. Impact generally increases based on the number of individuals affected, the criticality of the service involved, and the effect on teaching, learning, student success, or institutional operations.

Incident: An unplanned interruption to an IT service or a reduction in the quality, availability, or performance of an IT service.

Major Incident: A Priority 1 incident, or any incident that significantly affects a large population, critical service, or core university operations and requires coordinated response, executive communication, and post-incident review.

Priority: The relative order in which work is addressed based on a combination of impact, urgency, risk, and institutional importance.

Resolution Time: The elapsed time from support case submission until the issue is permanently resolved, the requested service is fulfilled, or the support case is otherwise completed.

Response Time: The elapsed time from support case submission until WMU IT acknowledges the request and initiates investigation or fulfillment activities.

Restoration Target measures the time required to restore service to an acceptable level, either through corrective action or an approved workaround.

Service Catalog: The published inventory of WMU IT services, including service descriptions, eligibility requirements, request procedures, support options, approval requirements, and applicable costs.

Service Owner: The individual accountable for the overall performance, governance, and lifecycle management of a service.

Service Request: A request for a standard WMU IT service, product, access, information, or support that is routinely offered through the Service Catalog. Examples include account provisioning, access requests, software installation, and technology purchases.

Student-Facing or Instructional Service: Any service that directly enables learning, teaching, advising, research, registration, academic administration, or student interaction with the university. Examples include learning management systems, student information systems, classroom technology, and academic support platforms.

Support Case: The formal record created for each interaction with WMU IT, including incidents, service requests, questions, consultations, and other requests for assistance.

Support Case Owner: The designated WMU IT staff member responsible for coordinating activities related to a support case, maintaining communication with the requester, and ensuring appropriate progress toward resolution or reassignment.

Urgency: The degree to which an issue requires immediate attention based on timing, deadlines, operational needs, or potential consequences of delay. 

Appendix B: Default Targets and Operating Parameters

The targets and operating parameters in this appendix establish the default service expectations for WMU IT services. Service-specific targets documented in the Service Catalog, service agreements, or approved service documentation take precedence over these defaults. These values may be reviewed and updated outside the biannual SLE review process as service needs, business requirements, or operating conditions change. 

B.1 Priority Levels and Targets

  • Priority is assigned based on impact, urgency, and service criticality.
  • Response Target measures the time between support case submission and WMU IT's first response.  
  • Restoration Target measures the time required to restore service to an acceptable level, either through corrective action or an approved workaround.  
  • Resolution Target measures the time required to fully resolve the underlying issue, fulfill the request, or implement permanent corrective action.  
  • An Incident may be considered restored before it is resolved. When a workaround restores service, the Incident may be downgraded, monitored, or transitioned to problem or maintenance activities while permanent resolution is pursued.  
  • Targets are measured during applicable Business Hours, except for P1 Critical Incidents, which are measured continuously during Help Desk operating hours.
  • Target measurement is suspended when WMU IT is awaiting required information, access, approval, or action from the requester or an authorized university representative.
  • Service-specific targets published in Service Catalog supersede these default targets.
  • Approved exceptions under Section 8 may suspend or modify target measurement.

Default Incident Targets

PriorityDescriptionResponse TargetRestoration Target
P1 CriticalCritical Service is unavailable or severely impaired for a significant portion of the university, and no reasonable workaround exists. Examples include major outages affecting network connectivity, identity and authentication, the LMS, email, the student information system, classroom technology during scheduled instruction, payroll during payroll processing, or security incidents involving sensitive institutional data.15 minutes4 hours
P2 HighCritical Service is significantly degraded, or a department, class, or group of users is unable to perform essential activities. Includes student-facing services affected during a Critical Academic Period or administrative services affected during a critical operational period. A workaround may exist but is limited or inefficient.1 hour1 business day
P3 MediumOne requester or a small group is unable to perform a required business, academic, or administrative function, and no reasonable workaround exists.4 business hours3 business days
P4 LowService remains available with limited impact; an acceptable workaround exists, or the support case is a standard service request or low-impact issue affecting an individual requester.1 business day5 business days

Service Request Targets

Request TypeResponse TargetFulfillment Target
Standard Request1 business day5 business days
Complex Request1 business dayAs published in the Service Catalog

B.2 Service Availability

Unless otherwise defined in the Service Catalog, the target availability for Core Enterprise Services is 99.5% per calendar month, excluding approved maintenance windows and approved service target exceptions. 

B.3 Maintenance and Change Notice

Change TypeCommunication Expectation
Routine ChangeAt least 5 business days' notice when requester communication is required.
Service-Impacting ChangeAt least 2 weeks' notice when noticeable disruption or downtime is expected.
Emergency ChangeNotice may be shortened to protect services, restore service, or reduce risk; post-implementation review required.

B.4 Communication Frequency

Incident TypeCommunication Frequency
P1 Critical IncidentAt least every 2 hours
P2 High IncidentAt least every 4 business hours
Major IncidentPost-incident summary within 5 business days of closure, when practical.

Communication frequency may be adjusted by the Incident Manager based on incident conditions and available information; however, WMU IT remains accountable for providing timely status updates and restoration information.

B.5 Service Target Exceptions

When extraordinary circumstances materially affect WMU IT's ability to meet established targets, the responsible Service Owner, Support Manager, or designated WMU IT leader may approve a documented exception.

Approval shall include:

  • The reason for the exception.
  • The affected service or target.
  • The expected duration.
  • Revised expectations, when practical.
  • Communication to affected stakeholders.

An approved exception does not remove accountability for Incident Management, communication, coordination, or service restoration. The assigned Incident Manager and Service Owner remain accountable for managing the incident and communicating status until service is restored, or an alternative resolution is established. 

B.6 Core Administrative Services

The following services are designated as Core Administrative Services for purposes of prioritization, incident management, and Critical Operational Period designation:

  • Student Enrollment  
  • Student financial aid
  • Student billing and payment services
  • Payroll and time reporting
  • Benefits administration
  • Human resources systems
  • Finance and accounting systems