|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The IT Strategy Administrative Systems Task Force found that, in addition to
having systems that are fast becoming outdated, most UNC campuses have very limited
capacity for training staff and faculty on administrative systems. This lack of training
limits their effectiveness. Many campuses also have inadequate staffs for software
implementation, support and maintenance.
|
|
|
|
|
|
|
|
Recommendations
|
|
|
|
|
|
|
|
|
|
The IT Strategy calls for campuses to collaborate in providing shared software
support. A proposed support center (the Alliance) would provide campuses with fee-for-
service support for common administrative systems work. The Alliance would be
governed by its member campuses, and all UNC campuses could join.
The expected benefits of this proposed collaboration are:
• Reduced cost of software procurement and support
• More consistent and timely software upgrades for all campuses
• Greater influence over vendors’ software development decisions.
The IT Strategy also proposes that UNC implement automated data sharing to
streamline data collection and processing. This would result in improved data quality,
easier access to data, and significant savings of staff time.
|
|
|
|
|
|
“A data warehousing system would automatically gather data from relevant campus
systems and make it accessible in a variety of formats to approved users. Access to
various types of data could be restricted based on the level of user privilege.”
|
|
|
|
|
|
|
|
|
 |
|
|
|
|
|
|
|
|
|
Members of the Logistical Needs Task Force reviewed the support requirements
of the initiatives recommended by the other four IT Strategy task forces. They identified
three major logistical challenges:
• Supporting the new multi-million-dollar campus network infrastructure being
implemented as part of Phase I of the IT Strategy project.
• Meeting the support and training needs of ever-increasing numbers of faculty, staff
and student users.
• Paying for IT hardware, software and support services while trying to contain costs.
|
|
|
|
|
Recommendations
|
|
|
|
|
|
|
|
|
|
 |
|
|
|
|
|
|
|
|
•
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Provide campuses with additional network support to meet growing demands for
service. Increase the capability of every campus to ensure reliable and accessible
network services.
Create a network electronics renewal process to upgrade or replace network
components on a regular basis.
|
|
|
|
|
|
|
|
|
•
|
|
|
|
|
|
|
|
|
|
October 1999
|
|
|
|
|
8
|
|