EPM Enhancement Requests

Background and Purpose

EPM is a new service launching for campus and is currently onboarding customers. The purpose of this document is to provide guidance on change management processes.

In all cases, EPM will be following ITIL change management processes in Service Now. 

EPM Enhancement Requests Form

ITSO's can suggest changes to MECM, PatchMyPC, Jamf or Jamf application management by completing the EPM Change Request Form. Every change request will be vetted and validated by the EPM team. If your change is approved, it will follow the ITS change management process. Some requested changes will be reviewed with the EPM Committee before implementation. 

EPM Change Request Form

Change Scope

IN SCOPE 

The scope of the ITS Change Management Process is to manage all changes to IT service assets that may impact production Service Offerings. Listed below are example changes that are in scope for the ITS Change Management Process:  

• Software – Installation, patching, upgrade, or removal of software products, including operating systems, access methods, commercial off-the-shelf (COTS) packages, internally developed packages, and utilities. 
• Configuration Changes – Any additions, deletions, or modifications to the centralized environments, including permissions and configuration settings, Extension Attribute (EA) changes in Jamf.

OUT OF SCOPE 

Examples of activities that are outside the scope of the ITS Change Management Process include:  

• Changes to development, test, or pre-production environments, including environments for  
• Contingency, continuity, or disaster recovery 

Many other types of reports are available https://aus-sccm.austin.utexas.edu/reports/browse/ConfigMgr_AUS

ITS Standard Change Process:

ITS Change Standards and Guidelines

All standard changes are scheduled 2 weeks out to allow for testing and validation.