...
- July 1, 2011 – Finance
- July 1, 2011 – reporting tool and ODS
- August, 2011 – Admissions (and Relationship Management)
- October, 2011 – Luminis (prospects, applicants)
- January 1, 2012 – HR/Payroll
- January, 2012 – Financial Aid
- March, 2012 – Student (registration, accounts receivable, catalog/schedule)
- October, 2012 or February 2013 – DegreeWorks
A detailed schedule of project activities can always be found in the Project Calendar on U-KNOW.
Project Assumptions
- The Banner implementation will be 'vanilla' – no modifications of the program source code will be made.
- The project will be limited in scope as described under Project Scope; Except where otherwise noted, implementation will be limited to replacement functionality. Other approved initiatives will be included in not-phase-one planning.
- Replacement functionality refers to the ability to achieve required business objectives, rather than to replicate current procedures. Assessment and improvement of practices and policies is expected.
- No development, modification, or report development will be done on AIMS unless it is mandated by a government body or the Board of Trustees.
- Given the necessity of meeting implementation goals to support the University's mission, Banner and its associated components will be the number one priority for University Technology. All other projects will be deferred or assigned a lower priority.
- Interfaces will be written as needed to achieve continuity and maintain functionality through the implementation cycle.
- Printing of reports and forms will be done locally in user offices using a laser printing strategy.
- Ad hoc reporting capabilities will be available to end-users.
- End-user training will be conducted by University staff.
- Shared codes will be determined by the Data Standards team.
- Project documents will be posted on U-KNOW.
...