Guiding Principles

Student Information System Implementation Guiding Principles

The Purpose of the Guiding Principles:

  1. Provide direction and guidance for the implementation of student systems;
  2. Define the approach for delivering student information systems;
  3. Establish the standards of organizational behavior to support the strategic goals for student information systems.

Guiding Principles:

  1. Decisions regarding Information systems to support student administration will be strategic business decisions, not technology driven projects.  The need for technology driven projects remain and will be prioritized and supported.  (e.g. upgrade to an operating system)
  2. All projects will be prioritized with enterprise direction and operational needs established by the governing bodies.
  3. Project will leverage current University investment before considering an alternative vendor or custom development.
  4. No modifications will be made to vendor provided base code without approval by the Executive Sponsors.
  5. The use of standard business processes will be implemented across campus (where possible, when fit, etc) 
  6. When utilizing vendor solutions, the vendor provided best practices will be implemented unless the process identified provides the University a competitive advantage.
  7. Data will:
    1. be considered an asset;
    2. be standardized and commonly defined;
    3. maintain integrity across interfaces (field sizes, code values, etc)
    4. be captured once and quality validated at the source;
    5. be accessible to University staff as appropriate;
    6. be protected from external intrusion or unauthorized internal use.
  8. All ‘bolt-on’ solutions must have a cost benefit analysis completed and be evaluated by the governing bodies for implication to all project plans currently in progress or under consideration.
  9. The project will eliminate shadow systems when the core student system can be utilized.
  10. Information systems will focus on service to our customers and will maximize self-service functionality.
  11. Testing is a critical step in system implementations and will not be overlooked.  
  12. Work to implement information system strategic goals will be done in a ‘silo free’ environment.
  13. Issues will be resolved quickly and roadblocks escalated and removed.
  14. Appropriate resources will be committed.
  15. Non participation or no response to information presented in team meetings implies agreement.
  16. E-mail requests to team members will include a reasonable response time (e.g. 2 working days) in the text of the email.  No response implies agreement.
  17. All project decisions will be documented and distributed to all team members.
  18. Upgrades & maintenance to system modules will be completed as necessary.
  19. Project schedules must be met.