Overview Enterprise Architecture is focused on the alignment of people, process, technology, and information across an organization.
Enterprise Architecture (EA) operates across the entire technology lifecycle, starting in pre-procurement activities within the IT strategic plan process, through RFP considerations, technology selection, and ongoing governance activities such as exception handling, vendor management, and architectural reviews.
EA also produces standards which specify required behavior and controls for the application of technology in the Commonwealth. In addition, EA develops technology roadmaps that identify current, upcoming, and outdated software to support effective infrastructure management and planning.
The authority of the enterprise architecture practice is established in the Code of Virginia § 2.2-2007 and § 2.2-2011.
Enterprise Architecture Standard and Policy
To support the CIO’s mission of delivering a unified IT approach across state government, Enterprise Architecture (EA) develops standards that define required behaviors and controls for technology use within the Commonwealth. These standards are designed with measurable, enforceable requirements to ensure consistent application and compliance. By standardizing approaches, EA reduces redundancy, minimizes security risks, and streamlines training and skill development.
The Enterprise Architecture Policy (EA200) lays the foundation for EA standards and forms part of the Commonwealth’s technology governance framework. It sets direction and outlines technical requirements governing the acquisition, use, and management of IT resources by executive branch agencies.
The Enterprise Architecture Standard (EA225) establishes a structured framework for developing, maintaining, and leveraging EA as a decision-making tool for IT investments and changes across the enterprise.
EA Roadmaps and Requirements
View the following roadmaps and resources published under EA-225.
- Application Domain Report
- Cloud Based Hosting Topic Report
- Enterprise Systems Management
- EA Solution Computer-based Signature Standard
- EA Solution Data Availability Requirements
- EA Solutions Web Systems Standard
- ETA Integration Domain Report
- Legacy Information Technology
- EA Smart Device Use
- SOA Integration Domain Topic Report
Roadmaps, as published by the COV EA team, provide for guidance around planning technology investment, changes, and updates. They specify, for foundational technology categories, which product versions should be used, when they should be updated by, and when they should be no longer used.
The intent for governance of technology versions is simply to prevent last minute version updates and their consequent negative impact on delivering quality information technology that supports the Commonwealth business architecture. In fact, updating to current versions should be a recurring task for agencies and suppliers of Commonwealth information technology services, because this will result in increased staff productivity, maintaining reliable security and reducing the costs of legacy maintenance.
The following roadmaps enable agencies and suppliers to plan more predictable and scheduled updates. Because assessments are "forecasted" with best available information at the time of a decision, they are subject to change to maintain resilience with those subsequent changes occurring outside the Commonwealth's control.
Review the current EA technology roadmap updates.
Roadmaps are available for the following:
- Application Hosting Platform Roadmap
- COV Artificial Intelligence Technology Roadmap
- COTS Applications Technology Roadmap
- Data Management Technology Roadmap
- End User Computing Operating Systems Technologies Roadmap
- End User Computing Productivity Software Technologies Roadmap
- End User Computing Web Browsers Technologies Roadmap
- Programming Languages and Data Access Methods
- COV Search Engine Technologies
- Server OS and Hypervisor Technologies Roadmap
- Web and Application Servers Technologies Roadmap
Visit COV IT Glossary for EA Roadmap Definitions.
How to Engage with the EA Team
Enterprise Architecture at VITA is engaged through a variety of mechanisms, which vary depending on the need. Learn how to engage with the EA team for each process listed below.
If your agency or operation is unable to comply with approved EA standards or roadmaps, an Archer exception should be registered for your agency.
Some examples of exceptions are:
- Your agency uses a software product version that is 2 or more versions behind the current release.
- Your agency has out-of-support hardware that the agency is dependent on, or has a hardware product that is over 5 years old that is still in service.
- You can't meet an enterprise requirement, such as compliance with logging or data availability.
Register your exceptions in Archer, the COV risk management system.
Executive Order 30 directs that VITA develop and publish an AI policy and AI technology standard that is adhered to by the executive branch agencies.
As part of the developed standard, all agencies and suppliers shall register their intended utilization of artificial intelligence in their operational functions for review by VITA and the secretariat.
To find out more about this process, visit our Artificial Intelligence section. Use Archer to start or access your AI records.
As part of its governance role, Enterprise Architecture (EA) reviews architectural designs to ensure coherence and alignment with VITA rules, verifying that all applicable service requirements are met. EA also reviews referenced exceptions for validity and relevance and provides input on technical design details when necessary.
IT Strategic Plans (ITSPs) are required by the Code of Virginia. Every two years, agencies must attest to the IT initiatives they plan to undertake over the next two-year period. As part of the approval process, Enterprise Architecture reviews each plan for standards compliance, opportunities for reuse, remediation of outstanding exceptions, and clarity of intent.
Following review, EA enters approval recommendations into Planview and, if needed, coordinates with the CAM and other teams for follow-up or clarification.
Investment Business Cases (IBCs) authorize agencies to develop project charters, issue RFPs, and allocate funds. As part of the review process, Enterprise Architecture (EA) assesses each IBC for alignment with the agency’s IT Strategic Plan (ITSP) and evaluates the proposed solution against current standards and IT strategy.
For example, agencies generally should be using cloud-friendly approaches that don’t unnecessarily create roadblocks for compliance or other challenges during implementation or in the future. Enterprise Architecture, as one of the reviewers, will approve the IBC if there are no identified issues. If clarifications or conditions are needed, EA may include them with the approval or return the IBC for additional information before proceeding.
A Project Governance Request (PGR) follows an approved Investment Business Case (IBC), once the agency is ready to fund the proposed solution. Similar to the IBC review, Enterprise Architecture (EA) evaluates the PGR for compliance with EA standards and alignment with the Commonwealth’s IT strategy.
Following the review, the enterprise architect will either approve the PGR or request additional information before approval. EA may also contact agency representatives for clarification as needed during this process.