Mt. SAC Important Message

New Numbers, Same Classes! Some of our most important general education classes have new course numbers and names effective this Fall. Don't miss your GE requirements and read your Mountie email for more information!

LEARN MORE
Menu
Change management plan written out with affected parts. Information Technology Change Management
A lit lightbulb indicating a new idea for change. A new idea for innovationInformation Technology Change Management
Different lines and ideas being organized into a straight flow through change management. Creating an efficient flow for changeInformation Technology Change Management

Information Technology Change Management

Mt. SACs Change Management practices are designed to uphold the stability and integrity of our college systems, applications, and data. Through our Change Management process, we seek to communicate and facilitate a seamless and efficient way to manage, maintain, and upgrade systems managed by IT. Our goal is to minimize negative impact to services and our customers.

Our approach relies on a standardized set of procedures to address every change request. Change Management ensures that each change is documented, thoroughly evaluated, properly sanctioned, prioritized, and deployed, aligning with our business objectives and upholding the stability and dependability of our vital IT services.

What Qualifies as a Change? A change encompasses the introduction, alteration, or removal of any element that might impact IT services. Typically, changes lead to adjustments within a particular facet of the IT infrastructure or one of our critical business applications.

      • Routine/Standard Change
        • These are usually pre-authorized, pre-defined, repeatable changes
        • Low risk, low known impact
        • Documented and well-known procedures
      • Minor/Normal Change
        • Low risk, low impact
        • Low to medium amount of preparation/planning
        • Scheduled or routine changes
        • Requires Change Approval Panel (CAP) authorization
      • Major/Emergency Change

        Major

        • Medium to high risk
        • Significant amount of preparation and planning required
        • Requires CAP Authorization 

         

        Emergency

        • High risk of failure 
        • Urgent change (must be changed as soon as possible)
        • Little to no viable alternatives or work-around
        • Requires CAP Authorization
      • Routine/Standard Change Examples
        • Website modifications and updates
        • Software patches and updates
        • Virus signature files updates
      • Minor/Normal Change Examples
        • Corrective changes to problems in running systems
        • Updates of SSL certificates
        • Computer Configuration Update (changing group policy, adding access to software applications)
      • Major/Emergency Change Examples

        Major

        • Banner upgrades, year-end closing
        • Firewall upgrades, patches, and ACL updates
        • Implementing new application requiring SSO, SFTP, or other integration

         

        Emergency

        • Registration issues preventing students from adding/dropping classes requiring Banner patch
        • Security breach resulting in serious risk to a critical service

Change Submission Deadline

The Change Approval Panel meets weekly on Tuesday at 1:30pm to review upcoming changes. To facilitate the process, all submissions must be pre-approved by management prior to the Change Review (CR) meeting. Submissions that have not received approval at least one day before the scheduled meeting will not be considered for review. 

Emergency changes are the only changes that can be approved outside of regularly scheduled meetings and only require the approval of the Change Review Group (CRG).

Change Management Request Form

Contact Us

Do you have any questions, comments, or concerns regarding IT Change Management?  Email: mcantuchan@mtsac.edu