| |
|
| [an error occurred while processing this directive]
|
|
| |
|
 |
| |
|
July 2007
Issue 2
|
Photo by Steve Jones |
Kicking off Banner
Pam Horne, assistant vice president for enrollment management and dean of admissions, addresses the OnePurdue Enrollment and Student Affairs team, representatives from SunGard Higher Education and others at a kickoff for implementation of the Banner applications. Horne is the “process owner” of ESA. |
|
| Scheduling functions move to Enrollment Management |
In a plan approved June 6 by Provost Sally Mason, the responsibility for student registration, class schedule preparation and classroom assignments will transition to the Office of Enrollment Management and assigned to the Office of the Registrar.
An integral part of the 2008 release of OnePurdue’s student applications, Banner, the move is expected to be completed by this September.
“This transition is in line with OnePurdue’s overall vision and plan to integrate two other applications with Banner: Ad Astra’s Astra Schedule and Platinum Analytics,” said University Registrar Bob Kubat. Astra Schedule is a space scheduling tool and Platinum Analytics will perform course demand analysis and help Purdue plan course offerings.
|
 Kubat |
(Banner is SunGard Higher Education’s academic and administrative software package that will comprise the bulk of OnePurdue’s Enrollment and Student Affairs (ESA) implementation. Read more about SunGard Higher Education and the individual Banner modules included in OnePurdue here.)
Training for key staff members will start in July, beginning with courses in registration and fee assessment, among others.
“We are strategically aligning both processes and people with the future of Purdue’s student systems,” Kubat said.
To assist in implementing Banner, Astra Schedule and Platinum Analytics, a work group has been formed to address registration processes and procedures, in addition to other related activities. Currently comprised of 16 members, this group includes representatives from every school and college, OnePurdue staff and the Office of the Registrar. Kubat said that others will be added at appropriate times as the Banner implementation progresses. These will include students, representatives from the Bursar’s Office and other administrative offices (e.g., Continuing Education).
Student input also will be sought regarding priorities for the timing of registration for student cohorts, scheduling of drop/add periods, wait lists and other issues.
“Using Banner, we will manage the opening and closing of sections and seats, in addition to handling prerequisites and reservations, throughout a registration period,” Kubat said. “This will help ensure that all students will have classes available to them.” Policies and priorities for these processes will be determined by the work group.
Submitted by Bob Kubat
Return to Contents
|
|
| Purdue legacy applications: what stays and what goes |
|
The OnePurdue Vision is to transform the University’s way of doing business into a flexible and user-centric portfolio of applications that will integrate all Purdue data, information and processes. As new OnePurdue Enrollment and Student Affairs applications are introduced, some “legacy” applications will retire. The table below lists which ones will and will not be affected by OnePurdue.
Submitted by Lee Gordon
Return to Contents
|
| Tentative “go-live” dates set for Banner implementation |
|
Purdue will continue using student legacy systems until summer 2008. Here are two other significant milestones. (Note: These are projected and tentative dates — and subject to change.)
Date |
Milestone |
| February 2008 |
Banner Financial Aid goes into production to support the fall semester. |
Fall 2008 |
First Banner Registration (for Spring 2009 semester) |
Submitted by Lori Shipley
Return to Contents
|
| Purdue to get inside view of Banner from August workshops |
|
To help Purdue get ready for Banner, two days of workshops, led by representatives from Wichita State University (WSU), will be held Aug. 6-7 on the West Lafayette campus.
“Wichita State had a successful Banner implementation, and we would like to learn from their experiences,” said University Registrar Bob Kubat. “This will be a good opportunity for Purdue leaders to get an inside view of what’s involved and the challenges ahead.”
WSU’s Assistant Vice President Dianne Coleman and Becky North, WIN user support and training coordinator, will help lead the workshops; both will speak about their experiences implementing Banner.
WIN (WSU Information Network) is the name of the ERP (Enterprise Resource Planning) system at WSU, as OnePurdue is the name of Purdue’s ERP.
These workshops will cover three primary topics: departmental preparedness, training and user support. They also will include workshops on strategies for leaders.
“This will help us prepare for our own Banner implementation,” Kubat said.
Invitations to the workshops soon will be sent to associate deans, directors and department heads.
Submitted by Bob Kubat
Return to Contents
|
| Legacy and Banner systems: a comparison |
|
SunGard Higher Education's Banner will include new ways for students, faculty and staff to access information. The chart below compares how some things will be done with Banner, how they are being done now, and how they are being done in the new OnePurdue (SAP) human resources and financial systems.
Function |
How it's being done now — or will be done in the future — with ... |
Current Student Systems |
OnePurdue/ Banner |
SAP (for new financial and HR systems) |
| Login |
ACID or Career Account |
Career Account |
Career Account |
| Operational ID |
Student ID (SID) |
PUID |
PUID and PERNR (primary identifier for HR master data) |
| Access Connection |
Some connect to mainframe; some through Web |
Web |
Some Web and some SAP GUI client |
| Portal |
SSINFO (students); SIS on Web (staff) |
Banner Luminus |
SAP Portal |
| Reporting Tool |
Brio for most; SAS for a few |
Cognos for most; SAS for a few |
BeX and SAP Query for most; SAS for a few |
| Post-Go-Live Data Environments |
Legacy transactional systems, DSS, Registrar ECHO system |
Operational Data Store for most data; Enterprise Data Warehouse for summary- level data |
SAP ERP and SAP Business Warehouse |
| Historical Data Environments |
Legacy transactional systems, DSS |
DSS (Additional student historical data will be extracted from legacy systems, moved and archived to DSS.) |
DSS |
| Electronic Report Distribution |
PageCenter |
e~Print Reports |
To be determined |
| Document Imaging |
none |
Banner XtenderSolutions |
To be determined |
| Workflow |
none |
Banner Workflow |
SAP Workflow |
Submitted by Lee Gordon
Return to Contents
|
|
|
|
