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.
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.
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.
These forms are for Information Services staff only. If you need to report an unexpected service interruption, please contact the OSU Computer Helpdesk.
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.
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.
The following planned changes will impact customer access to IT services. Links provide details of the nature and extent of the service interruption. Service-affecting changes are not permitted on blackout days. Planned changes that will likely not impact access to IT services are listed at the standard change blog.
Banner, the Data Warehouse, ODS/EDW and most administrative or Banner-related applications will be unavailable Thursday and Friday (28 and 29).
The affected Banner-related applications include: AppWorx, Banner INB, Banner SS, BRM, Cleanaddr, Data Warehouse, DegreeWorks (MyDegrees), EDW, EvalS, myOSU, Nolij, OSCAR, ODS, Multiple Assignments, FormFusion, Scholarship Management System, MyVendor, R25 and Banner Workflow.
This is our annual Oracle database, operating system and hardware maintenance activity. Banner and related applications will be brought down at 11:59PM on Wednesday night and brought back no later than 11:59PM Friday night.
Blackboard will be taken offline Dec. 20-22 (Friday through Sunday) to perform an upgrade to Service Pack 13. To discover what's new in the upgrade, see all the details here. [PDF]
At a glance: Top 5 features in the Blackboard upgrade
How can I find out more? Check out the short videos of some of the new features in Service Pack 13.
Blackboard will be unavailable during the maintenance window of 6:00 am to 9:00 am on Saturday, January 25, 2014.
Blackboard will be unavailable from 6AM to 6PM on Thursday November 28 for regular monthly maintenance.
Blackboard will be taken offline September 13-15 (Friday through Sunday) to perform a planned upgrade to Service Pack 9.
Beginning 12:01 am Friday through Sunday 11:59 pm, Blackboard will be unavailable while the upgrade is completed and the system is tested. Blackboard will be back online Monday 12:01 am September 16.
More information about the upgrade is available at http://oregonstate.edu/tac/how-to-use/blackboard/blackboard-servicepack-9-upgrade
Upgrades to IS systems and services shall not be scheduled between December 28 and January 1 so as not to impact criticial business use, including fundraising activities, annual reports, and administrative tasks.
On Thursday November 14th, from 6:00 to 6:30am, Network Services will perform a code upgrade on the enterprise VPN. This code upgrade will most likely cause a service interruption during the maintenance window. Users needing to use the VPN at this time should use the test VPN to avoid any interruption.
The test VPN can be accessed via a web interface at https://sapp4public.nws.oregonstate.edu/ or by adding a new profile in the Cisco AnyConnect for sapp4public.nws.oregonstate.edu. The test VPN will be available until a few days after the upgrade, after which users should not expect production level service and uptime from this test VPN. The test VPN option will not be available for Site to Site VPN connections, these connection will most likely go down during the maintenance, but will be up and available after it is completed.
Upgrades to IS systems and services shall not be scheduled between December 14 and December 19 so as not to impact criticial academic use, including grade submission and posting.
The following message was sent from the TouchNet service owner, Business Affairs
The TouchNet eCommerce data storage and maintenance will be migrated from local OSU servers to a hosted solution with data stored and managed at the TouchNet data center. This project will also upgrade TouchNet applications (Payment Gateway, Marketplace uStores and uPay (including T-Link) sites, Bill & Payment, and Cashiering) from version 5 to version 6. The targeted go-live date is Wednesday, November 6, 2013.
Moving to a hosted solution has several benefits including:
During production migration, all TouchNet eCommerce applications in the production instance will be taken off-line for 2 full days, Monday, November 4 and Tuesday, November 5, 2013. We anticipate you will be online again by the start of business November 6, 2013.
Payment Gateway, Marketplace uStores and uPay (including T-Link) sites, Bill & Payment, and Cashiering will be taken off-line during the outage. Please plan accordingly by notifying your customers and placing a message on your website. If you have a third party maintaining your website, please ensure they are aware of the outage.
We apologize for any inconvenience and appreciate your assistance.