Customer-linked Investments: UVMÕs investments will be driven by clearly defined objectives that reflect the priorities and needs of its customers and the extent to which they enable Òmore and betterÓ University capabilities. Large investments will consider the total cost of ownership, including acquisition, maintenance, support and de-acquisition costs.
IT Policy and Oversight: UVM will establish policy and oversight bodies responsible for putting in place consistent management practices to address UVM-wide issues such as enterprise architecture, security, data access, business continuity, connectivity, outsourcing, quality standards and funding.
Metrics: CIT will establish an ongoing program to measure system quality and the service levels provided to CITÕs customers to ensure effective ongoing management of its investments and continuous improvement.
Buy vs. Build Solutions: UVM will purchase packages rather than build unless business requirements can only be met, or competitive advantage gained, by developing them internally.
Local IT: Colleges and departments will only provide IT services when this best meets user needs and where economies of scale are not possible and the initiative will not enhance University-wide capabilities.
Self-service: UVM will encourage the use of the Internet to reduce service costs, to create opportunities for customers to take over traditional UVM administrative functions and to improve user productivity.
Reusability: In order to deliver services as efficiently as possible, existing solutions that meet user needs will be reused and extended to a broader customer base. Common, dispersed IT solutions will be developed, delivered, and maintained by only one organization and should not support multiple images of the same solution.
UVM Branding: A consistent UVM-wide web portal will be developed to improve access to UVMÕs services, reduce the learning curve, and decrease transaction costs.
Methodology: UVMÕs IT organizations will use a consistent development methodology that incorporates both developers and customers in the process. Individual tasks and deliverables will vary based on project size and risk.
Data Sharing: All data should be managed to enable appropriate levels of sharing across the enterprise and will be accessed using standard data base and file management facilities.
Standard Protocols: To facilitate the electronic exchange of data between applications and external entities, a standard set of protocols will be used that are based, when available, on industry standards.
Common Environments: By broad user community, a common work environment will be supported, including approved workstations, connectivity, applicationsÕ help desks and access to UVM-wide data.
Data Capture: All unique representations of data should be captured once and stored in a manner that reduces data duplication and redundancy.
Access to Legacy Systems: Seamless access to existing data and applications will utilize messaging or connector technology.
Data Independence: Data will be designed and maintained independently of application, technology and organization to provide better sharing, reduce cost of change, and minimize impact on the environment.
Network: There will be a single logical production network that provides transparent access to applications and data to allow applications and data to be accessed without regard to location.
User Interface: By broad customer base, common user interfaces will be defined. Different communities may have a different look and feel.
Information: Users will be able to view or process any piece of information they need, based on profiles and security requirements.
Access and Outreach: IT services will be accessible to all members of UVM, extending beyond the traditional boundaries of time and distance to create a global learning community.
Connectivity/Interoperability: The architecture must allow many disparate hardware and software subsystems to connect with each other and exchange requests and data as needed to perform the desired business transactions.
Security: Security must be comprehensive and enable UVM to protect its assets from deliberate or accidental misuse.
Flexibility: The solution will allow for changes in the technical and business environments in order to insure the longevity of the investment.
Layers: A layered architecture (application, data, information and technology) will best enable UVM to adapt to changes in both user requirements and technology innovations with minimum disruption and cost. Layered design is used to transparently manage interfaces among data, applications, communications, and technology over time.
Functional Isolation: Functional isolation will lower the cost of system deployment and maintenance by minimizing duplication, confirming the effects of a change, and reducing the complexity of implementing changes.
Modularity: Each component will be able to be removed and changed, reducing the complexity of implementing changes.
Portability: Portable applications can allow sites to upgrade their platforms as technological improvements occur, with minimal impact on operations.
Integration: Integrated packages which meet functional and nonfunctional requirements, will be favored over separate, best-of-breed packages, which require custom-built interfacing mechanisms.