Student Systems
The Student Systems group is dedicated to the development and maintenance of systems and software supporting all student-related activities at the University of Texas at Dallas. Student Systems strives to provide the most accurate, efficient and secure systems and services to all groups that support our student population. We are also committed to ensuring our services are in compliance with all governing laws, statutes, and policies in support of advancing excellent educational and research programs at the University of Texas at Dallas.
Supported Systems
Campus Solutions (PeopleSoft/Orion)
We provide maintenance, development and support for enterprise systems that sustain the administrative functions of student-related activities. The primary responsibility of the Student Systems group is the maintenance, development and support of Orion, the Campus Solutions application of the PeopleSoft Enterprise Application. The Campus Solutions application is the backbone of almost all areas dealing with students and student information, including:
- Academic Advisement – gives students and faculty timely access to academic records and reports
- Campus Community – provides a common source of campus data, coordinating all forms of communication to help you manage your administrative services
- Campus Self Service – allows students and faculty members to engage in self-service activities such as requesting transcripts, viewing grades, or accessing course calendars
- Financial Aid – automates federal and institutional financial aid processing
- Admissions – helps students and staff plan, manage, and track admissions activities
- Student Financials – provides tools for managing and calculating all student financial information, including tuition, fees, refunds, and other financial information
- Student Records – manages all aspects of enrollment, from catalog and class schedule maintenance, credit transfers, requisite restrictions, and more
eLearning
eLearning is the University of Texas at Dallas eLearning and course management system.
Auxiliary System Data Feeds
In addition to supporting the above systems, we also provide Data Feeds (information sent from one system to another) from the Campus Solutions system to several auxiliary systems.
Request Services
Work Request Procedures
Service Requests should be made via the appropriate JIRA Project, using the steps as outlined on the Requesting Service page.
Most requests for enhancements or modifications to the Campus Solutions application should be accompanied by a functional specifications document:
- Shared Services Modification requests require the use of the TexSIS Functional Specifications Document.
- Local Modification requests require the use of the Orion Functional Specifications Document.
For more information about the differences between Shared Services and Local modification requests, refer to the document, Orion Modification Request Process. Also, this entire process is documented in the Orion Work Request Process document.
Forms
JIRA Project Sites for Campus Solutions
- PMPS
- PeopleSoft Campus Solutions (Orion) – Modifications or changes to existing processes, enhancements and new processes should be entered in the PMPS project. PMPS requests are monitored by the technical manager for the Campus Solutions System. The approval process for PMPS requests includes review and prioritization by the Orion Users Group.
- CSOC
- Campus Solutions On Call – All production failures and problems which require an immediate fix should be entered in the CSOC project. These requests are monitored by the Orion on-call person as well as the technical manager. All CSOC requests will be addressed as soon as possible.
- EA
- Enterprise Applications (OnBase access, eLearning, and other systems)
Additional Forms
In addition to using the JIRA system described above, the following forms are required when the Campus Solutions (Orion) system is involved.
- Shared Services Modification requests require the use of the TexSIS Functional Specifications Document.
- Local Modification requests require the use of the Orion Functional Specifications Document.
