* Updated August 19, 2014




Will end-users and business leadership have a place at the table in ensuring that the student administration system meets their requirements?

All UT groups who have a stake in student systems will be engaged in the process in the coming months; this includes analysts and programmers who work on and integrate with current systems. There will be a separate planning effort that will provide more opportunities for involvement and input. 

How will historical data be accessed?

This has not been determined and will depend upon the outcome of the solution selection process, implementation planning, and solution design.

Our current systems are integrated and real-time. Can we expect the new system to have the same real-time functionality?

Our goal is to have a fully integrated administrative system. During the transition process when we are working between the new and legacy solutions, there may be a change in the level of integration. However, our goal will be to maintain current integrations throughout the process and that most functions will be real-time, at least where that is important in the requirements. We do not expect to lose real-time capabilities where they currently exist. We currently make decisions about whether a process should be real-time, semi-real time or overnight and will continue to make these determinations based on the business problem at hand.

How does the ASMP affect individual departmental shadow systems?

Where possible, we would like to pull the requirements associated with departmental shadow systems into the core administrative systems. However, inevitably some functions will remain outside of the core systems and will need to be integrated during the transition.


Will training resources will be available for developers on the campus?

We plan to offer appropriate training in the new system to the developer and user communities, so the university staff can perform their duties using the new systems.

Will new employees be hired with the skillsets required for the new system? If so, will these new hires replace current mainframe programmers?

There will likely be some new hires needed, though this does not mean they are replacing existing developers. Existing developers will have opportunities for training in any new systems.

Should I just stop writing against the mainframe? If so, what should I write against? What language should I use?

The transition will take several years. At some point, the IT Governance process will determine when mainframe development will stop, and all new development will occur in the new systems. That date has not been set at this time. Functional management and development teams should jointly determine whether an enhancement or maintenance change in a current system is needed and whether the mainframe is the right place to develop until such time that all mainframe development is ended.