To create a change or to review existing changes, see ITS Change Management.
...
| Note |
|---|
To follow the workflow of a change request, click Raise a request.  |
Change Types
The sections below describe different types of change management requests.
Request Types | Description |
|---|---|
Expedited Change | Used to address a Break/Fix, an unplanned change based on a customer's request, vendor availability, or degradation of service. |
Standard Change | Change that is low risk, has little to no impact, and is of routine nature. |
Non-Standard Change | Often non-trivial changes to systems, services, and infrastructure. Require communication to end-users or the campus community and may require internal and external planning, assessment, authorization, CAB review, and scheduling before implementation. |
Firewall Change | Firewall Changes are a subset of Standard changes used for routine firewall alterations. This change type follows the Standard Change workflow, automatically sets fields related to impact, and includes additional prompts for Firewall specific information. Firewall Changes require team lead approval but do not require CAB approval. Changes to the firewall that will have significant impacts on major services should be planned and completed as Non-Standard Changes. |
Standard
Standard changes have a very low risk and a predictable outcome. They are relatively common, follow a procedure or work instruction, and require minimal communication.
...
Complete the form. All RFCs that alter production configurations or programs need to have been tested in a non-production environment and include documented procedures to regress the change via a set of well-understood back-out procedures.
If this is not possible, the Functional Approver must indicate the reason why such practices are bypassed.
The Approvers field is for your Team Lead. While approval is not required for Expedite Changes, adding your Team Lead will allow them to receive notifications for the ticket. To enter the Team Lead, enter their email address or lastname, firstname.
Additional technicians are any technicians who will be working on or must remain updated about the change order. To enter the additional technicians enter their email address or lastname, firstname. They will be added as Watchers to the ticket.
At the bottom of the form, you can choose to publish a notice on the IT Status page.
Choose Yes from the dropdown for Post to IT Status.
Enter a brief description of the change. This description will be displayed when a site visitor clicks on the link for the change.
When you are writing a message for the IT Status page,
Keep it concise and focused.
Identify the issue, who it impacts, and how it affects them.
For the Services Impacted field, select the appropriate service. If multiple services are affected, you can select each affected service. To do so,
Hit Ctrl + click (for Windows) or Command + click (for macOS).
If the service is not listed, choose Other.
Enter the service in the Service Impacted (Other) field below.
Click Create to complete the request.
...
Joshua Bartlett
Chris BernardKevin Brown
Josh Boggis
Andre Corsini
Griffin Freiberg
Steve Fletcher
Matt Grimm
Haleh Ghaemolsabahi
Jason Hamley
Jessica Henderson
Dhanoop Jose
John Khairallah
Les Martin
Noel McAvoy
Gil Milone
Rob Morrell
Ann Nunes
Mike Oatley
Keith Parks
Brett Paulson
David Plamondon
Catherine Rhodes
Rich Ritchie
Zach Robert
Mitch Saba
Chris Tarricone
Hengameh Vosough
Michael Williams
John Wrynn
Yi Zhang
...
Emergency CAB (eCAB) is composed of these Directors:
Haleh Ghaemolsabahi
Jila Kazerounian
Mike Williams
Josh Boggis
Christopher BernardDirector of Campus TechnologyServices
Director of Enterprise Applications
Director of Telecommunications
Director of Enterprise Systems
Chief Information Security Officer
Roles and Responsibilities
...