eworkflow: course approval routing - aacrao-web.s3 ... · eworkflow: course approval routing aacrao...
TRANSCRIPT
eWorkflow: Course Approval Routing
AACRAOTuesday, March 25, 2008
1:30pm - 2:30 p.m.Session ID 192
PresentersVirginia Johns, Registrar, UC Santa Barbara
Kathleen Copenhaver, Associate Registrar, UCLA
2
Campus Profile
College of Letters & Science11 Professional SchoolsFaculty
4,000 Teaching FacultyEnrollment: 37,500
26,000 Undergraduates11,500 Graduate
Degree Programs125 Undergrad Majors75 Undergrad Minors121 Graduate Majors
Classrooms200 General Assignment50 Department Classrooms40 Department Laboratories
RankTop 10 Research Universities(National Research Council)
Top 4 “New Ivies”(Kaplan/Newsweek)
Nobel Laureates 5 UCLA Faculty 4 UCLA Graduates
Library8 million volumesTop 10 in the nation
Buildings325 Buildings419 Acres
100 NCAA Championships
3
eWorkflow: Course Approval
GoalGet courses processed and scheduled by quarterly deadlines so students can enroll in classes and complete their degree.
Basic StepsComplete the course form (data input)Submit for approval (routing)Upload or input when finalized (process)
How can we do this most efficiently?
4
Analyze and Streamline
Analyze current processes - eliminate unnecessary stepsWork with administrators, faculty, and senate committees to simplify processesScope: Don’t load too many processes and functions on a course form that could/should be done elsewhere.
5
Old Paper Course Form
Challenge: How to rationalize the approval, routing, and storage?
1. Signatures (Designees ?)
2. Routing
3. Record of Approvals —7 carbon copies
6
Delegation of Authority
In 1998, the Undergraduate Council delegated authority to approve most course actions to the College and School Faculty Executive Committees.
In addition, the Undergraduate Council reaffirmed direct routing of Variable Topics to the Registrar’s Office.
The Graduate Council retained their course review and approval processes.
The delegation streamlined routing and helped determine the workflow for the new electronic course approval process.
7
Course Approval Workflow
Department(Department Chair or Designee)
College/SchoolFaculty Executive Committee
(Coordinates internal approval with Deans )
Registrar’s Office
Or
Graduate Division Ugrad Council
Or
Registrar’s Office Registrar’s Office
Registrar’s Office
√
√
8
Roles and Routing Issues
There are 4 divisions in the College, and there are 11 Professional schools. Each has their own committees, subcommittees, deans, and approval processes.
Would have needed 1/2 FTE just to keep a database updated with all the routing roles, offices, and staff changes.
Could have decentralized updates, but there were still too many variables for efficient workflow.
Decision Point
9
Open Routing Workflow
DepartmentChair or DesigneeCurriculum CmtesDept Faculty
College/SchoolFaculty Exec CommitteeDeansSubcommittees
Graduate DivisionAssociate Dean
Ugrad CouncilCurriculum Cmte Chair
Registrar
Registrar
Registrar
Registrar(Titles & descriptions for established Variable Topics courses)
Basic PrincipleEach unit is responsible for routing within their level.
10
Basic Critical Features
Secure Login (Authentication & Authorization)
Automated WorkflowApproval TrackingNotificationCustomized Course FormsError CheckingItemized HelpMinimal TrainingPrinter-friendly OptionsArchival Record of Forms and SyllabiReports
**Be easy to fill out and understand**
√
13
Staff Authorization
1. Must have a mainframe Student Records logon ID and password
2. Must be setup in the mainframe security module specific for CIMS access
3. Must be listed in the Campus Directory withan e-mail address
14
Faculty Authorization
1. Must have a UCLA e-mail account and password
2. Must be active in the payroll
3. Must have a senate-approved faculty title (e.g.,Professor, Adjunct Prof, TA)
4. Must be listed in the Campus Directory with an e-mail address
15
Data Sources
Database FunctionEnterprise Directory Authentication
Logon ID & PasswordPayroll Authorization
Confirms faculty titles(Prof, Adjunct Prof, TA)
Mainframe Security Module AuthorizationConfirms staff eligibility
Campus Directory AuthorizationRouting & e-mail notifications
Registrar’s Databases Replicated mainframe course dataLocal tables for pull-downs & roles
16
CIMS Statistics
14,000 Courses Active in InventoryCIMS Forms Monthly
AverageYearly
Average
New Courses 35 424
Revised Courses 67 801
Deleted Courses 13 162
Subtotal 116 1,387
Specialized Term Courses
Variable Topics 65 774
Fiat Lux Seminars 18 213
Honors Seminars 11 131
Subtotal 93 1,118
Total CIMS Forms 209 2,505
CIMS Routing Transactions 1,369 16,424
CIMS Unique Users 28 340
Average Routing per CIMS Form 6.56
17
CIMS Main Menu Sections
1. Courses Waiting for My Approval
2. Status of Pending ApprovalsPrinter-friendly
3. Course FormsNew, Revised, Delete, Customized
4. Course ReportsArchived Approvals, Syllabi
√
24
Courses Waiting for Approval
Pending Action L&S FEC Coordinator
Courses Requiring My Approval
Pending Action L&S FEC Coordinator
Pending Action L&S FEC Coordinator
Pending Action L&S FEC Coordinator
Pending Action L&S FEC Coordinator
Pending Action L&S FEC Coordinator
Pending Action L&S FEC Coordinator
Pending Action L&S FEC Coordinator
Pending Action L&S FEC Coordinator
26
Review Approvals to Date
Dept Staff
Dept Chair
FEC Staff
College Dean
FEC Chair
Record of who approved it, when it was approved,what changes were made, and what comments were recorded.
28
RO Scheduling Processing
New course data input manually in mainframe screen,then from routed to publications for description editing.
29
RO Publication Processing
• Web Interface
• Cut, paste, edit description
• Web Service: Upload directly to mainframe
• Data is stored locally as a backup
31
Intervention Capability
Only the Registrar’s Office or the Initiator can withdraw a course.
Only the Registrar Office can re-route a course from another’s queue.
33
Pros and Cons
ProsFastSecureEasy to UseCustomized FormsAutomated RoutingError CheckingRouting RecordArchival RecordSyllabus ArchiveNo more paper
Routing routine reusable for other applications!!
ConsStill manual input of course data to mainframe screensNo interface to print catalogTrainingKeeping up with Browser issues
35
Future Plans
Rewrite to new Student Records Data ModelDevelop Curriculum module for submission of new programs and program changesDevelop GE module for submission of courses for GE approval
37
eWorkflow: Course Approval Routing
AACRAO 2008 Orlando
Ginny Johns, RegistrarUniv of Calif, Santa Barbara
38
Old Issues
Typewriter required!“Shadow” systems AmbiguityEnforcementTracking Constantly changing leadershipInformed decisions
39
Project Team
Academic Senate leadershipmarketingsystem developmentongoing operation
Office of Registrar partnersinterface developmenthelp text maintenancetraining
40
FeaturesWeb interfaceWorkflow processingInterfaces with the Master Course DBDetailed formatted dataError checkingHelp text management systemReal-time tracking Escalation capability
If no action has been performed on a course request in X days, send reminder email to the reviewing agency
Queries for a specific field Dated, IDd comments
42
Course Approval Process
Initiated by faculty memberApproved by department chairEdited by Office of the RegistrarApproved by Executive Committee of applicable collegeApproved by Committee on Undergrad Academic Programs and PolicyRecorded by Office of the Registrar
43
Senate Committee Workflow
College Executive Committeeto appropriate college advisorbrings to committee for discussionadvisor records decision
Academic Policy and Procedure Commsequentially to committee memberschair can specifically assignmembers can hand-offtwo approvals required
The following field(s) have changed since the originaldepartment analyst submission: Prerequisite Text, Advisory Enrollment Information, Former Course Name, Repeats.They have been marked with a red arrow to the left of their title.
Update Review: Highlights changes (blue oval on previous slide)
71
New Opportunities
Growing wishlistGeneral Education course approvalsEnforced coordination of cross-listed coursesCross-notification of pre-requisite coursesDegree program proposals
Use as a change agentElectronic approval processes (oversight)
Which generate “Catalog Copy”Facilitating an online (only) Catalog
73
Contact Information
Virginia (ginny) JohnsRegistrarUniversity of CaliforniaSanta Barbara, Ca 93106-2015(805) [email protected]