Banner Implementation: A Focus on Community College Issues

1
Banner Implementation A Focus on Community
College Issues
Marie Fetzner November 3, 2005 WIZARD
Conference Syracuse, New York
2
Session Purpose

• Review general issues related to Community
  Colleges and Banner implementations
• Project Leadership
• Institutional Issues
• Functional and Technical Issues
• Facilitate participant discussion

3
Audience Poll

• Not yet committed to Banner as an ERP
• Implementation of Banner just about to begin
• Early stages of Banner implementation
• Mid-way through Banner implementation
• Finalizing the Banner implementation
• Currently utilizing Banner

4
MCC Banner Overview

• MCCs legacy system is SCT Plus
• MCC is implementing all five Banner modules
• Finance
• HR
• Advancement
• Student
• Financial Aid

5
MCC Banner Timeline

• Start-up phase March 1 August 31, 2003
  Implementation Dates
• Year 1 Finance (September, 2004)
• Year 2 Human Resources (January, 2005)
• Year 2 Advancement (September 2005)
• Year 3 Banner Student (October 2005-
  September 2006)
• Year 3 Banner Financial Aid (February 2006)

6
Reframing Leadership for Banner

• Commitment to a common vision
• Connect the Banner vision to the College mission
  and strategic plan
• Collaborative process
• Appreciate diverse ways of working
• Be resilient but confident of the outcome
• Executive level support for Banner is key

7
Vision and Leadership

• A vision is an open invitation and an
  inspiration for people to create ideas and
  events The Art of Possibility, Stone-Zender
  and Zender

8
MCC Banner Vision

• To advance College processes and systems by
  providing efficient, accessible, secure and
  dynamic information that supports the College.
•  

9
Institutional Readiness

• Banner system considerations
• System modules
• Finance and HR for CCs
• 3rd party applications and integration
• Implementation and maintenance issues
• Cultural change legacy system to Banner
• Communicate with all audiences
• Gather input from other CCs who have implemented
  Banner

10
Institutional Readiness

• Status of current IT system(s)
• Technology Plan
• Three to five year IT priorities
• Fiscal Assessment
• Institutional and IT budget projections
• CCBOA as a source for fiscal models
• Human Resource readiness
• IT staff and HR functional staff

11
Institutional Readiness

• Determine use of INB and/or Self Service
• Student considerations
• Faculty/Staff considerations
• All end user training issues
• Basic navigation
• Reporting
• Set the context for process changes i.e.,
• Electronic pay stub
• Web time entry

12
Functional and Technical Issues

• Develop the Banner organizational structure
• Identify timeline for implementation
• Identify IT staff assignments
• Identify functional team leads
• Develop budget for Banner
• Hardware, software, 3rd party apps, training
  rooms, service agreements, travel, misc. and etc.
• Utilize SICAS as a resource

13
Functional and Technical Issues

• Develop timeline for hardware and software
  installation
• Consider external hosting or internal support
• Develop schema for Banner instancesimportant for
  CCs that may be using all 5 modules
• Participate in SICAS and SCT listservs
• Participate in SICAS FAUGs
• CCs need to have input for FDR priorities
• Review existing CC-specific SICAS enhancements

14
Dialogueon Topics of Interest

• Strengthening the SUNY CC Banner network
• Sharing CC Banner module information i.e., COA,
  HR issues
• Maintaining and improving non-CC SUNY Banner
  school relationships
• portal review committee
• SICAS board meeting and FAUG participation
• Banner CC implementation issues

15

• Contact Information
• Marie Fetzner
• Monroe Community College
• mfetzner_at_monroecc.edu