IT Architecture and Infrastructure Committee
9:00 – 10:30 a.m., October 10, 2014, FAC 228D
I. 9:00 – 9:30 Mainframe Decommissioning – Endorse (Rich Janes)
II. 9:30- 9:50 Wi-Fi Cert-pocolypse (William Green, Jason Wang)
III. 9:50 – 10:20 Finalize Committee Priorities for 2014-2015 Academic Year – Discussion
IV. 10:20 – 10:30 Committee Chair – Election
Shannon Strank has been nominated to serve as Chair of AIC
Mainframe Decommissioning
10/7/2014
v2
E n d o r s e : G u i d i n g p r i n ci p l e s f o r U T A u s t i n m a i n f r a m e - d e co m m i s s i o n i n g
Current efforts underway:
Allow UT business and IT leadership to make informed decisions related to the decommissioning of the
mainframe and disposition of all applications that currently reside on the mainframe.
Leadership may opt to change any assumption in this plan including the timeline based on facts revealed
through the process.
All reasonable efforts will be made to decommission the mainframe by the end of fiscal year 2020.
Any unit or external agency that integrates with or runs applications or processes on the mainframe should
take deliberate actions to ensure their successful transition off the mainframe before the end of 2020.
Roadmaps are now part of a master road map that will be used to coordinate non-ERP ASMP 2.0 related
transitions. These include an inventory of administrative applications with the planned addition of non-student
administrative applications in February 2015.
Campus units should begin or continue to transition mainframe-based administrative applications to other
technologies in accordance with their roadmaps. This includes needs assessment, requirements and other
tasks leading to a solution. It should also include appropriate decommissioning of existing code, related
objects and retention of data.
Where there are units with similar needs, we will seek to identify common IT systems, applications and
business process solutions.
As with all other ASMP 2.0 initiatives, IT governance will guide the overall decommissioning plan and
process.
Additional effort starting in 2017 and 2018:
Prior to 2017, we will publish a list of orphaned applications in an attempt to identify owners. In October 2017,
applications remaining orphaned will be subject to a usage review and based on usage, a plan for their
decommissioning will be developed to include shutting down the application as soon as users can be notified
of its decommissioning.
In 2018, any unit without a reasonable plan to transition off the mainframe will work with the ASMP
Application Modernization team to decide on a replacement approach so that their applications can be
accounted for in the decommissioning plan. There are difficulties, risks and significant costs inherent in these
approaches so units should seek to develop their own replacement plans prior to 2018. Dispositions include,
but not limited to:
o (1) Replacement by a cloud or commercial off-the-shelf package,
o (2) Automated code conversion (i.e. “lift and shift”) of mainframe code and data to another platform,
o (3) Application retirement.
Costs associated with a unit’s application transition during the decommissioning of the mainframe will be
borne by the unit who owns the application. The option to stay on the mainframe will not be available.
The projected cost for mainframe support and operations beyond 2020 are expected to exceed $2,500,000
annually. At the end of fiscal year 2020 mainframe support and operation costs will no longer be a common
good service and will discontinue. This will allow resources to be redirected to services for the Common
Good. By May 2020, if one or more campus units or external agencies have not transitioned off the
mainframe and would cause a delay in the decommissioning of the mainframe, the University Budget Council
will determine to retire the application or consider if the entire mainframe support and operation costs should
be borne by the unit(s) proportionality based on CPU usage calculated quarterly.
1|P a g e
W i F i C h a n g e ( 7 / 2 0 1 5 ) – C a l l f o r Pa r
ticipation
Overview
Over 185,000 wireless devices are going to require user intervention to continue to function on
UT’s wireless network this summer. This is because the certificate (and its root authority) for
restricted.utexas.edu expires July 3, 2015. [a.k.a. the cert-pocolypse]
Notes
1) Research: We are forming a group to investigate various platforms and their reaction to
required certificate change. Who else would like to commit time now (as opposed to
later when devices are not working in the summer?
2) Example alternatives being studied:
a. Self-signed long expiration versus commercial certificate moving forward.
b. Big bang versus incremental change
i. Roll new certificate on July 3. Most devices will need minor attention
most end users can handle.
ii. Create a new SSID in spring to enable devices (especially embedded
devices) to move gradually and prepare ahead of time.
c. Taking the opportunity for the return of “utexas” for the SSID.
3) Recommendation: expected back to AIC by February
AIC
V 1.0
Octobe7, 2014