...
- 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, 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.With the exception of security patches and/or upgrades mandated by vendor support policies, no major upgrades will be performed on other New projects that compromise the resources of the ERP project, or major upgrades to enterprise applications supported by University Technology except those and not identified in the project scope.No new projects will be undertaken which intersect with resources required by the ERP project., 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.
- 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.
...