• Mission
• Objectives
• Project Principles
• Project Timeline
• Communications Plan
• Faculty and Staff Training
• Meet the Project B.O.B. Team
• Project Team Resources

PROJECT PRINCIPLES

1. We will adopt and leverage the vendor-delivered best practices, even if that means changing our current processes.
2. We will be willing to reexamine existing policies and procedures to allow us to implement best practices and to best serve the needs of our constituencies.
3. Changes to, or rejection of, best practices or deviation from the project principles will occur only when they directly support the institution's mission. All such changes require approval from the Executive Steering Committee.
4. The needs of our constituencies will drive design and implementation of our processes.
5. We will deliver tools and data access to empower functional users to make better decisions and to serve their constituencies.
6. Stakeholders will have access to self-service capabilities whenever feasible.
7. Our processes will assume trust with auditability within State guidelines.
8. We will streamline processes by eliminating non-value added steps. This includes the elimination of paper, authorizations, etc.
9. The institution as a whole owns its data; custodianship falls to functional areas, which are responsible for sharing data access with appropriate institutional users.
10. Custodians must understand the scope of their data and the impacts of their data management on other custodians and the overall institution. Data will be processed without delay, available to all applications that need it, and secure from loss. Its quality and integrity must be preserved.
11. Data should be collected only once and as close to the source as possible.
12. The established and accepted administrative system will be the official repository for shared, official, institutional data. This will eliminate need for separate maintenance and reducing potential for inaccuracy. This data will be available for downloading and integration for "appropriate" application development and other solutions.
13. Other College systems that should interact with the central administrative system will do so via the established data infrastructure in areas such as authentication and directory services, user interface, and application and services deployment.