Notes
Slide Show
Outline
1
PeopleSoft Student Information System
Schedule of Classes
Module Demonstration
October 12, 2007
2
Goals of this information session:
    • Brief overview and update on the Student Information System (SIS) project
    • Provide an overview of the Schedule of Classes (SOC) module
    • Demonstrate the basic actions taken to maintain the schedule of classes within a department
    • Introduce topics to be covered in training
3
SIS Background: Why a new student system?
4
Student Information System Modules
  • Academic Structure
  •  Foundation Tables
  •  Similar to Chart of Accounts in Financials
  •  Represents Case’s Academic Structure
  • Campus Community
  •  Bio/Demo Data: Names, Addresses, Phone Numbers, Email, Citizenship, etc.
  • Student Records
  •  Course Catalog
  •  Schedule of Classes
  •  Class Requisites
  •  Class Permissions
  •  Enrollment / Add/Drop
  •  Status Changes  Leaves, Withdrawals, etc
  •  Academic Standing
  •  Transfer / Test Credit
  •  Rosters, Advisee Lists, Grading
  •  Transcripts
  •  Degree Posting
  •  Holds



  • Academic Advisement
  •  Advisor Assignment
  •  Advisement/Degree Audit Reports
  •  What-ifs
  • Student Financials
  •  Charge Posting
  •  Tuition Calculation
  •  Late Fees
  •  Optional Fees
  •  Financial Aid Disbursements
  •  Billing
  •  Cashiering
  •  Payment Allocation
  •  Payment Plans
  •  Refunds
  •  Holds
  • Admissions*
  •  Application Processing, deferrals, etc
  •  Test Scores


  • * Limited functionality due to budget/scope


5
The Schedule of Classes
6
Schedule of Classes (SOC) Timeline
7
Process Timeline Comparison
8
The Schedule of Classes
9
Who can do what?
  • Departments
  • update offerings within their organization
  • chairs can request that others have access to their organization


  • CAS and CSE Deans’ Offices
  • modify offerings within their school
  • set approval “print flag”
  • flag freezes changes to meeting times, instructors


10
Basic Class Schedule Maintenance:
  • Modify/create/delete sections of a class
  • Confirm/assign/request a classroom for each section
  • Confirm/modify meeting days and times for each section
  • Confirm/assign an instructor for each section
  • Confirm/modify an enrollment limit
  • Save the changes
11
Additional business processes:
    • Section numbering protocol for courses with multiple components (lab, lecture, etc.)
    • Using the Associated Class field for multiple-component courses
    • Using the Auto-Enroll field for multiple-component courses
    • Scheduling a class that is new to the term
    • Creating in-term exams outside of a class’s standard meeting pattern
    • Creating sections for cross-listed courses
    • Processing and using reports to check for errors.

12
Training for Schedule of Classes
  • Email:
  • erptraining@case.edu



  • How training list was formed
  • Flexibility within/across depts


13
Questions?
  • Website:
  • www.case.edu/projects/erp/sis


  • Email:
  • erpsis@case.edu