1. Banner Project Student Team Update
Set Up:
Computer with PowerPoint or recent version of IE and network.
Projector
Objective: Clear, informative, Consistent message across the institution. From Registrar’s office, university relations, controller’s office, safety and security, to School of Law, graduate programs, . Audience intention is for anyone. Presentation to be give by any leader of the institution. Same message. This is a vechicle for communicating and transfer of knowledge.
February 16, 2005

2. Today’s Agenda Project activities defined Review schedule
Upcoming student team activities
Open Discussion (Q/A)
Reminders
This is just one of six strategic directions.

3. Quote worth remembering…
“If we knew what it was we are doing, it would not be called a project, would it ?
This is just one of six strategic directions.

4. An example of what we thought we knew in October 2004 !

5. Banner Project Timeline
MyVU
Finance HR
Financial Aid
Student
Alumni
July
2004
Today
July
2005
Jan
2006
July
2006
Jan
2007

6. Student Module Build/Testing Timeline
Catalog
Schedule
General Person
Faculty Load
Location Mgmt
Recruitment
Admissions
General Student
Registration
Student Billing (AR)
Academic History
Advising & Program Planning
Dry Run Testing
July
2004
Today
July
2005
Jan
2006
July
2006
Jan
2007

7. Definition of Build ?
In essence, the building of a prototype for testing purposes. This includes the entering of rules, codes and validation forms. Only data necessary to test this configuration is needed during this time. Data may or may not be moved over from Plus to Banner. However, this will be both decided and done during the Data Migration stage.

8. How dates arrived at:
Go Live – SCT provided timeframes based on experiences and support capabilities and VU adopted them during the planning phase and documented them in our PDD.
End-User Training – In general, each process team has 2 weeks allocated for training of the staff and users within their respective area. Working backwards from Go Live dates, keeping them within 2 weeks of Go Live and offering multiple sessions for users.
Testing w/ Data – In general, the duration was estimated based on the amount of testing required coupled with the complexity. Working backwards from Go Live dates, and ensuring we have completed this at least 30 days prior to Go live, thus allocating time for unplanned activities.
Data Migration – Working backwards from integration testing period and extending it all the way from when we receive our first data mapping consulting visit from SCT.
Testing – Same as above.
Builds – Same as finish date as the data migration period for the particular area and starting with the first functional workshop for this module.
Workshops – Process Team Leads identified “black out” dates and VU PM negotiated with SCT on availability of consultants.

9. Banner Student Basic Sub-Modules in Banner Student General Person
General Student
Curriculum, Catalog & Schedule
Faculty Load
Admissions
Registration
Academic History
Accounts Receivable
Housing
CAPP (degree audit)

10. The Banner Systems Financial Student Aid Human Alumni Resources
Recruiting
Admissions
Catalog
Schedule
Faculty Load
Academic History
Location Mgt.
Registration
Accounts Receivable
CAPP
The Banner Systems
Student
Human
Resources
Finance
Alumni
Financial
Aid

11. Plus to Banner from a Functional perspective
Attend
Workshops
Configuration
(Build forms)
Data Mapping
(Crosswalks)
Testing
Testing
End-User
Training

12. Banner Module Milestones:
Workshops (System Education)
Builds (Configuration of forms, rules, codes, etc.)
Review old codes and establish new ones, if necessary
Enter into the database
Testing
Plans (Develop and document)
Standalone Testing (Validate configuration)
Data Migration
Data mapping (Establishing Crosswalks)
Testing w/ data
Module-Integration Testing (Validate configuration, converted data, interfaces, if needed)
System-wide-Integration Testing (Confirm compatibility with existing production Banner modules)
Training (End-User Education)
GoLive

13. Steps for each Module: Train end-users on Banner
Create and train a work team of users/decision makers
Build Banner validations and rules
Test, refine and perfect the business process as it will exist in Banner
Develop security profile for the process
Build reporting infrastructure to support the process
Convert data and test for accuracy
Build any necessary interfaces or data bridges
Create end-user documentation
Train end-users on Banner

14. Banner Database Overview
Name Instance Purpose Access Data
Seed SEED Test Oracle and Banner MIC SCT-delivered data.
Banner upgrades.
Training TRNG Provide Banner system MIC and Functional SCT-delivered data.
education to VU by SCT Implementation Team
Consultants. using train01…train10.
Test TEST Development of MIC and Functional Initially will be a clone
configuration data Implementation Team of Seed database, and
(forms and tables) using individual account later populated with VU
by each functional ids. configuration data.
business area and
functional (business)
unit testing.
Conversion CONV Development of MIC and Functional Initially will be a clone
actual data to be Implementation Team of Test database, and
converted and using individual account later populated with VU
functional (business) ids. converted data.
Pre-Production PPRD Integration Testing MIC and Functional Clone of Conversion
of all configurations and users using individuaPro database, but revised in
actual data for all account ids with preparation of Go Live,
modules and end-user restricted update if necessary.
training. privileges.
Production PROD Production Database MIC and Functional Clone of Pre-Production
users using individual database.
account ids.

15. Who is Involved and when ?
Faculty
Staff
Students
Functional Team
Process Team
Steering Team
Application Core Team: 20 hrs/wk
Extended Application Team: hrs/wk
Outer most group of users: 2-3 months prior to “go live”
Working sessions: Monday & Wednesday 1-4pm on various topics. Check Web Site to see topics covered.
See Steering Committee Matrix to validate who each application core team lead is to refer associates.
Planning, Organizing, Setup, Testing, Training, Go-Live

16. What Can I Do?
Attend and come prepared to participate in system education workshops
Complete workbooks as time permits after system education workshops
Configure system by building rules, codes and validation tables as assigned
Continually review project web site for updates
This is just one of six strategic directions.

17. Resources to assist you:
VU Banner Project Web Site
(accessed from MYVU)
SCTListservs (Discussion Groups)
ActionWeb (SCT Support)
Other University’s using Banner (USI, ISU…)

18. Reminders……
This is just one of six strategic directions.

19. Questions