IT Changes

Information Services seeks to communicate with the OSU community about the changes we make to the IT systems that we manage. Our goal is to manage, maintain, and upgrade systems in a thoughtful way so that we minimize negative impact to services and customers.

Achieving this goal requires that we plan changes carefully, consult with members of the community regarding planned changes, and respond to unplanned changes systematically to ensure minimal downtime.

Change Management is the formal term for defining our policies and processes. Please read about the Change Management & Incident Response Project page for additional background about this initiative.

Change Advisory Board

The Change Advisory Board (CAB) convened in December, 2012 and began drafting appropriate processes for changes and incidents. As basic processes are defined, the CAB will begin performing its function as a change review body even as it continues to define and refine change processes.

CAB membership currently consists of:

Raul Burriel - Chair / primary representative, Academic Technology

Mike Akey - Co-chair / primary representative, IT Infrastructure and Identity Services

Max Cohen - Chair emeritus / primary representative, Client Services

Michael McDonald - primary representative, Web and Mobile Services

Moustafa ElBadry Shaker - primary representative, Office of Information Security

Reed Byers - primary representative, Enterprise Computing Services

Francisco Orozco, Jr. - primary representative, Networking and Telecommunications

Edward Ostrander - secondary representative, Academic Technology

vacant - secondary representative, IT Infrastructure and Identity Services

vacant - secondary representative, Client Services

vacant - secondary representative, Web and Mobile Services

vacant - secondary representative, Enterprise Computing Services

vacant - secondary representative, Networking and Telecommunications

Change Policies

These policies apply only to services and systems owned by OSU Information Services.

The Incident Response policy does not apply to Security Incidents, which are covered by the Information Security Manual section 502: Incident Response and Escalation.

Communicate Changes & Incidents

These forms are for Information Services staff only. If you need to report an unexpected service interruption, please contact the OSU Computer Helpdesk.

Incident UNPLANNED OUTAGE
  • Communicate ongoing or recent Incidents
  • World-readable on IS website, RSS, Twitter, Facebook
  • Email sent to Outages list
SIGNIFICANT or EMERGENCY
  • Submit change plan before making a change
  • Will be reviewed by CAB and your Director
  • Communication will be developed after review
STANDARD CHANGES
  • Optional form to communicate Standard changes
  • Posts to Maintenance blog only – no email is sent
  • Not a replacement for your Change Log

Communicate an Incident (Unplanned Outage)

Please avoid overly technical jargon, as your message will not only be sent to the Outages email list but will also show up at the following locations.

Communicate a Significant or Emergency Change Plan

In most cases (excepting Emergency changes), you will develop a technical plan and a communications plan for your change prior to filling out this form. Please upload this documentation when submitting this form if you are able.

After you submit this form, the Change Advisory Board (CAB) and Unit Director can help shape the communications plan before any message is received by any customer.

This form is for significant or emergency changes. For other changes, please use one of the links in the IT Changes menu box to the side or below the form.

 

Communicate a Standard Change

This optional communication will post your message to the Maintenance blog.