Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The University's faculty and staff can perform their job responsibilities effectively in Banner or other ancillary software according to the Project Timeline.
  • The University has retired the AIMS system at the conclusion of the project. 
  • The need for duplicate data entry and shadow databases has been greatly reduced or eliminated.
  • Ad hoc reporting capabilities are made available to and are utilized for report generation in departments.
  • Students, faculty and staff are provided direct access to a single integrated view of personalized information from the Luminis portal and other web applications.
  • The University is able to communicate effectively with current students, prospective students, and applicants.
  • Use of manual or paper-based administrative processes has been significantly reduced.
  • Modern standards-based methods are utilized to integrate and utilize Banner data with other University IT systems, including Moodle, Identity Management, Campus Cards, and Facilities management.

Project Scope

Banner modules and other Sungard Higher Education software purchased are:

...

  • 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, which will include replacement functionality and other enhancements specifically indicated; Other approved initiatives will be included in not-phase-one planning. Given the necessity of meeting the implementation time-line, replacement functionality will receive the highest priority.
  • Replacement functionality refers to the ability to achieve required business objectives, but not necessarily 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.
  • Given the necessity of meeting implementation goals to support the University's mission, the ERP project and its associated components will be University Technology's highest priority.  New projects that compromise the resources of the ERP project, or major upgrades to enterprise applications supported by University Technology and not identified in the project scope, with the exception of security patches or upgrades mandated by vendor support policies, will not be undertaken. 
  • 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.
  • Training will be conducted using a "train the trainer" model. Functional consulting will include training for the project teams. End-user training will be conducted by University staff in functional offices with the assistance of ETC training resources.
  • The Data Standards team will be responsible for establishing policies and relevant standards for data entry, including the use of shared codes.
  • Project documents will be posted on U-KNOW.

Project Risks

Project constraints and challenges ("boundary conditions") include:

...