From Enabling Citizen-Centered Electronic Government, 2005 - 2006 Federal Enterprise Architecture Program Management Office Action Plan,
Executive Office of the President of the United States, Office of Management and Budget, March 2005
From Enabling Citizen-Centered Electronic
Government, 2005 - 2006 Federal Enterprise Architecture Program Management
Office Action Plan,
Executive Office of the President of the United States, Office of Management
and Budget, March 2005
From TRB's Transit Cooperative Research Program (TCRP) Report 84:
e-Transit:
Electronic Business Strategies for Public Transportation, Volume 5 - Concept for
an e-Transit Reference Enterprise Architecture
"What Is an Enterprise Architecture? In simplest terms, an enterprise is any purposeful activity, and an architecture is the structural description of an activity. Building on this, we can view enterprise architectures as systematically derived and captured structural descriptions—in useful models, diagrams, and narrative—of the mode of operation for a given enterprise, which can be either a single organization or a functional or mission area that transcends more than one organizational boundary (e.g., financial management, homeland security).
The architecture can also be viewed as a blueprint that links an enterprise’s strategic plan to the programs and supporting systems that it intends to implement to accomplish the mission goals and objectives laid out in the strategic plan. As such, the architecture describes the enterprise’s operations in both logical terms (such as interrelated business processes and business rules, information needs and flows, and work locations and users) and technical terms (such as hardware, software, data, communications, and security attributes and performance standards). Moreover, it provides these perspectives both for the enterprise’s current (or “as-is”) environment and for its targeted future (or “to-be”) environment, as well as for the transition plan for moving from the “as-is” to the “to be” environment.
The importance of enterprise architectures is a basic tenet of IT management, and their effective use is a recognized hallmark of successful public and private organizations."
--Randolph C. Hite, Director, Information Technology Architecture and Systems Issues, Government Accountability Office, from May 19, 2004 testimony before the Subcommittee on Technology, Information Policy, Intergovernmental Relations and the Census, Committee on Government Reform, House of Representatives,"
Concept for an e-Transit Reference Enterprise Architecture--TRB's Transit Cooperative Research Program (TCRP) Report 84: e-Transit: Electronic Business Strategies for Public Transportation, Volume 5 - Concept for an e-Transit Reference Enterprise Architecture examines the need for and uses of a reference enterprise architecture; the process for its development based on using systems engineering concepts and practices; the basic concepts behind systems engineering and enterprise architecture; and the transit-specific tasks associated with creating an e-transit reference enterprise architecture.
http://trb.org/news/blurb_detail.asp?id=4296
The Federal Enterprise Architecture (FEA)
Planning effort was launched in 2002
http://www.whitehouse.gov/omb/egov/a-1-fea.html
The FEA is poised to move into strategic initiatives stage in 2005 and 2006
http://www.whitehouse.gov/omb/egov/documents/2005_FEA_PMO_Action_Plan_FINAL.pdf
"Government Enterprise Architectures Face Numerous Risks"
https://www.gartner.com/0_admin/QuickRegInfo.jsp
"Seven Architecture Actions for Shared Government Services -
http://www.gartner.com/DisplayDocument?ref=g_search&id=449212
"Findings From the Enterprise Architecture Research Meeting: Externalize Your Enterprise Architecture" Dec 05, Anne Lapkin
http://www.gartner.com/DisplayDocument?doc_cd=136918
"EAP Architectures Provide Business Benefits Only When They're Used" Oct 04 Matthew Hotle, Anne Lapkin
http://www.gartner.com/DisplayDocument?doc_cd=131249
"Now what? Four years into the enterprise
architecture initiative, agencies have blueprints in place. It’s time to put
those EAs to work," article by Joab Jackson Government Computer News
Staff, February 6, 2006
http://www.gcn.com/25_3/tech-report/38142-1.html
The FEA Library serves as the central repository for all FEA PMO related documents. The files and information resources contained explain the purpose, usage, and definition of the Federal Enterprise Architecture and associated reference models.
http://www.whitehouse.gov/omb/egov/a-2-EALibraryNEW2.html#Pres
Enterprise Architecture Planning for Transit: Bridging the ITS Deployment Gap. Presentation to FTA, May 31, 2005 , Hwang and Lerner-Lam.
http://www.tsconsortium.org/EAP/EnterpriseArchitecturePlanningVersion2.3.ppt
Main Website for the Federal Enterprise Architecture (FEA)
http://www.whitehouse.gov/omb/egov/a-1-fea.html
Originally established by Executive Order 13011 (Federal Information Technology) and later codified by the E-Government Act of 2002, the Chief Information Officers Council (the CIO Council) is the principal interagency forum to improve agency practices for the management of information technology.
http://www.whitehouse.gov/omb/egov/d-1-cio.html
The ITRB is a group of senior IT,
acquisition, and program managers with significant experience developing,
acquiring, and managing information systems in the Federal Government.
http://www.itrb.gov/
Washington Metropolitan Area Transit Authority
Contact: Edward Thomas, Vice President, Strategic Planning
Email: elthomas@wmata.com
Tel: 202-962-2100
Miami - Dade Transit
Contact: Rosie Perez, Sr. Chief, Information Technology & Support Services
Tel: 305-375-3651
This Resource Center is maintained by the Transit Standards Consortium, Inc. for public use. Send additional references to TransitEAP@tsconsorium.org.