Office of the Chief Information Officer

United States Department of Agriculture

Enterprise Architecture

Introduction

The USDA Enterprise Architecture (EA) helps make sure information technology investments align with the mission and goals of the Department. It defines how information and technology should support USDA’s strategic goals and benefit the business.


Purpose

The intent of the USDA Enterprise Architecture is to help make the information technology (IT) expenditures more effectively serve the mission and goals of the organization. Enterprise architecture defines how information and technology support USDA’s strategic planning to benefit our business. There are many ways to organize the information and diagrams that make up the architecture.


Enterprise Architecture Contacts

Will Williams
Enterprise Architecture Director
Will.Wlliams@ocio.usda.gov

Bob Sile
Business & Performance Architect
Robert.Sile@usda.gov

Brian Brotsos
Data Architect
Brian.Brotsos@usda.gov

David Waddell
Technology Architect
David.Wadell@usda.gov

Sean May
Standards/Application Architect
Sean.May@usda.gov

Virginia Davis
Portfolio Architect
Virginia.Davis@usda.gov

EA emailenterprise.architecture@ocio.usda.gov


Enterprise Architecture Links

The Federal Information Technology (IT) Shared Services Strategy (published May 2, 2012) provides Federal Agencies with policy guidance on the full range and lifecycle of intra- and inter-agency information technology (IT) shared services. These enable mission, administrative, and infrastructure-related IT functions. This strategy is part of the "Shared First" strategy which seeks to increase return on investment, eliminate waste and duplication, and improve the effectiveness of IT solutions.

The OMB document The Common Approach To Federal Enterprise Architecture published on May 2, 2012, which directly addresses shared services guidance as an Enterprise Architecture General Principle on page 13: "Shared Services. Agencies should select reusable and sharable services and products to obtain mission or support functionality. Increasingly, the Federal Government is becoming a coordinator and consumer as opposed to the producer of products and services. Standardization on common functions and customers will help Federal Agencies implement change in a timely manner."

Important Enterprise Architecture links:

USDA 2015 Enterprise Roadmap

USDA EA Diagram 2015

USDA 2014 Enterprise Roadmap

OMB Federal EA (FEA)

Federal IT Dashboard

Data.gov

Forest Service EA Program