 |
INFORMATION SYSTEMS - Legacy Systems Support
System Owners
Student information is contained in a number of systems. Some of the
larger, enterprise systems containing student data are the Bursar
system, the Financial Aid system, the SI Admissions system,
the SI Registrar system, SIS, SIS on the Web, SSINFO, and Decision
Support System. The system owner and application administrator
depends on the content. A system owner is the individual who
has been assigned ultimate responsibility for a system. An application
administrator is one who acts on behalf of the system owner
to keep the system operating effectively. A system is defined
as a single computer program or a group of programs, owned by
Purdue University, that perform(s) a single task or multiple
tasks, on a server, mini-computer, or mainframe.
If the content
is related to: |
The System Owner is: |
The Application Administrator is: |
|
Student Accounts, Fees, Payments |
John Higgins, Bursar |
Kerry Kleiber, Manager of Systems and Operations |
| Student Loans |
Sherry Ziobro, Manager Loan Programs |
Kerry Kleiber, Manager of Systems and Operations |
|
Student Financial Aid, Student Employment |
Joyce Hall, Director of Financial Aid |
Terri Davis, Associate Director of Financial Aid |
|
Student Admissions |
Pam Horne,
Asst. Vice President for Enrollment Management and Dean of Admissions |
Jeannie Sanson, Assistant Director of Admissions/Operations and Rebekkah Porter, Assistant Director of Admissions/Operations |
|
Prospective Student Information |
Pam Horne,
Asst. Vice President for Enrollment Management and Dean of Admissions |
Sarah Bauer, Associate Director of Enrollment Management |
| Student Courses, Schedules, Enrollment, Encumbrance, Academic
Record, Demographic and Biographic Information |
Robert A. Kubat, Registrar |
Lesa Beals, Associate Registrar for Records, Registration and Graduation |
The system owner (or his/her delegate) has the following responsibilities:
- Learn and understand the overall purpose of the system.
- Learn and understand sufficient details of the system to be
able to manage the day-to-day operations of the system.
Provide final approval to proceed with daily processing.
- Manage the development and continued maintenance of desk procedures
for the staff who operate the system on a day-to-day basis.
- Make final decisions in situations where system information
is inaccurate after appraising the customer impact as
well as the resources and time available.
- In conjunction with the ITaP Business Continuation Plan,
develop and maintain a system level business continuation plan.
- Coordinate all changes to the system when it is not working. Provide
final approval for implementation for all changes to the system.
- Conduct periodic review of the system operation to insure that
it is working as intended.
- Coordinate with ITaP (and other departments as needed) acceptable
levels of documentation and procedures for operating and
maintaining the system.
- Manage training development and presentation for all staff who
will be updating or using the information in the system.
- Recommend improvements to the system to maintain an efficient and
accurate process providing customer oriented information.
- Communicate changes, improvements and other important information
about the system as needed.
- Represent the university in all actions resulting from the use of
the system, its data or information provided by the system.
- Ensure appropriate problem resolution has occurred and that system
issues are addressed and communicated accordingly.
- Conduct periodic review of the system operations to insure that
it is working as intended.
- Responsible for establishing and maintaining business processes especially
those required by University policies.
- Responsible for specifications on what the system will and will not
do (including reporting).
- Responsible for ensuring that there is a policy (who should get access)
and process for granting access to the system and a process
for periodic review of the access.
|
 |
