SECTION I – INTRODUCTION
CONTEXT
The purpose of enterprise architecture is to optimize across the enterprise the often fragmented legacy of processes technology into an integrated environment that is responsive to change and supportive of the delivery of the business strategy.
An enterprise architecture standard addresses this need, by providing a strategic context for the expanded use of technology in response to the constantly changing needs of the business environment.
PURPOSE
UMW has adopted the Commonwealth of Virginia (CoVA) IT Resource Management (ITRM) Enterprise Architecture Standard 225-09. UMW’s Enterprise Architecture standard is a strategic asset used to manage and align business processes and technology infrastructure with the University’s overall strategic plan.
The Enterprise Architecture standard is also a comprehensive framework which assists with defining and describing the University’s current (“as-is”) technology platforms, as well as its target (“to-be”) technology direction.
SCOPE
The scope of this standard coverall all information technology used by the University of Mary Washington.
SECTION 2 – STANDARDS
STANDARD
UMW’s EA standard is used by the Information Technologies Department to manage the University’s technology portfolio with a focus on the following goals:
- Alignment of IT resources to strategic university goals and the academic mission of the institution
- Reduction of ongoing operating costs
- Optimization of university technology assets
- Maximization of service
- Improvements in IT risk management and mitigation
- Improvements in technology capabilities and capacity
- Integration of emerging technologies
UMW’s technology assets are assessed and categorized into the following technology domains.
- Applications Domain – Systems Design, Application Acquisition, Development and Software Languages and Platforms, Software Engineering
- Database Domain – Databases and other data access methods
- Information Domain – Reporting, Data Management, Business Intelligence
- Integration Domain – Database integration, message integration, middleware, etc.
- Networking and Telecommunications Domain – Facilities infrastructure, etc.
- Platform Domain – Personal computing, servers, desktop productivity tools
- Security Domain – Information security and risk management
- Enterprise Systems Management Domain – Service Delivery, Service Support, and Operations Management
Each domain contains its own definitions and requirements for technology within its area.
The Enterprise Architecture standard also defines categories for architecture direction, that the University uses when planning or making changes or additions to its technology portfolio:
Strategic:
This technology is considered a strategic component of the University’s Enterprise Architecture. Strategic technologies define the desired, “to be”, state of the University. Before any updated or new Strategic technology can be deployed, appropriate operational and performance reviews must take place, to include the following:
- Perform the appropriate testing
- Establish the needed technical support
- Follow a formal Change Management process
- Develop any required images
- Obtain the appropriate operational reviews and approvals
- Assess impact on business processes
- Assess training needs
Emerging:
This technology requires additional evaluation. This technology may be used for evaluative or pilot testing deployments or in a higher education research environment. Any use, deployment or procurement of this technology beyond higher education research environments requires an approved Commonwealth Enterprise Architecture Exception. The results of an evaluation or pilot test deployment should be submitted to VITA‘s Policy, Practice and Architecture Division for consideration in the next review of the Enterprise Architecture for that technology.
Transitional/Contained:
This technology is not consistent with the Commonwealth‘s Enterprise Architecture strategic direction. Agencies may use this technology only as a transitional strategy for moving to a strategic technology. Agencies currently using this technology should migrate to a strategic technology as soon as practical. A migration or replacement plan should be included as part of the Agency‘s IT Strategic Plan. New deployments or procurements of this technology require an approved Commonwealth Enterprise Architecture Exception.
Obsolescent/Rejected:
This technology may be waning in use and support and is not consistent with the Commonwealth’s Enterprise Architecture strategic direction. The university may use this technology only as a transitional strategy for moving to a strategic technology. Any such in-use technology should migrate to a strategic technology as soon as practical. A migration or replacement plan should be included as part of the university’s IT Strategic Plan. New deployments or procurements of this technology require an approved Commonwealth Enterprise Architecture Exception.
SECTION 3 – REFERENCE and SUPPORTING INFORMATION
REFERENCES
UMW uses the CoVA ITRM Standard EA225-09 as its standard for Enterprise Architecture. The standard can be found at: http://www.vita.virginia.gov/uploadedFiles/Library/EAStandard225-09.pdf
SUPPORTING INFORMATION
N/A
SECTION 4 – GOVERNANCE
RESPONSIBILITY
| Responsible manager(s) | Executive Director of IT Infrastructure |
| Procedure administrator | Executive Director of IT Infrastructure |
| Approving body | Office of the CIO |
SECTION 5 – STANDARDS REVIEW AND MAINTENANCE
This standard is reviewed annually by 1 July of each succeeding year. The Director of EAS of assigned designee will review the standards for accuracy and relevancy and make any necessary revisions or adjustments.
Document footer will be updated to include the date of the most recent revision.
The Change History matrix will be updated accordingly.
APPROVAL AND REVISIONS
Approved March 2, 2011 v 1.1 by Vice President for Information Technologies & CIO
February 4,2015 v1.2 Tightened up language. No significant changes made to the standard
May 25, 2016 v1.3 updated per IT template