Click for next page ( 5

The National Academies of Sciences, Engineering, and Medicine
500 Fifth St. N.W. | Washington, D.C. 20001

Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement

Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 4
4 EAP Enterprise Architecture INPUTS Performance Potential P o Vision / Mission / Goals Business P r Projects Internal Data External / Regional Applications BUSINESS CASE Technology METHODOLOGY IT/ITS Strategic Plan FUNDING Budget Process Operating & Capital :: Programs POST- IMPLEMENTATION SYSTEMS Approved A ANALYSIS ENGINEERING P Projects KEY Project Flow Supporting Information Flow Figure 1. Five components of TEAP. Guidance for Transit Managers A short executive report was developed for executive and senior managers (see Guidance for Transit Managers in Appendix A), which included a high-level summary of the Frame- work and a checklist for managers to assist them with their management oversight of tech- nology projects. Targeted for transit professionals who desire only a short synopsis of the con- tent of the Framework, the report includes a brief description of each of the five disciplines, their benefits, and the synergistic relationships between them. In addition, a general set of roles for transit managers is included, as well as checklists that are specific to each of the TEAP Framework elements. The checklists are designed to assist transit managers in enabling their staff and the transit organization to effectively assess, acquire, and enhance IT/ITS systems. The Guidance for Transit Managers report is available on the wiki and in Appendix A. Phase II Results: Reference Enterprise Architecture for Transit Phase II focused on generating a Reference Enterprise Architecture for Transit, and val- idating this architecture with transit agencies of different sizes, modes, and organizational structures.

OCR for page 4
5 Table 1. TEAP Framework Wiki. TEAP Framework Wiki Description Audience Guidance for Transit A high-level description of the TEAP Transit executive and Managers Framework, including the purpose and senior managers. benefits associated with each Framework element and the interrelationships. In addition, the guidance includes a checklist that enumerates the roles and responsibilities of transit managers with respect to each of the elements. This section includes a self- contained, downloadable version that can be printed and read in hard copy. TEAP Framework A detailed description of each TEAP Program managers and Guidance: Framework element, including: information transit professionals Executive Summary on the what, why and benefits of the who want to learn EA/EAP element; best practices and streamlined more about the topics. BCM approaches; and additional resources, Funding including references, tools, and examples Project SE from the Information Technology (IT) and Post- transit industries. Implementation Transit EAP Guidebook The Transit EAP Guidebook details step-by- Program managers and step how to develop a transit enterprise transit practitioners architecture (as-is and to-be). The who are tasked with Guidebook shows how to customize the implementing an EAP Reference Enterprise Architecture for and maintaining the as- Transit to represent the drivers, business is and to-be enterprise processes, information, applications, and architectures. technologies in your organization. The Guidebook is an interactive and extendable "space" on the wiki to describe a Reference Enterprise Architecture for Transit, and to include related terms and techniques for implementing a transit enterprise architecture. It includes models, templates, examples, and benefits associated with each step. State of the Practice A summary of the State of the Practice All Synthesis Results Synthesis related to the five elements of the TEAP Framework. Other Resources How-To Guides All Glossary and Acronym List FAQs About the Project and the Wiki Site Map Improvement Page The general purpose of an enterprise architecture is to understand the connections between your organization's business processes and stakeholders (users, upstream providers, and downstream recipients); this information is used to measure performance and make decisions, as well as to develop applications and technology that enable the services and generate the information. Most transit agencies support similar business processes, information views, applications and technologies. The models that represent each layer do not differ greatly either. This provides an opportunity for the industry to describe a generic reference that may be customized based on the particular agency, rather than having each transit agency start from scratch. A reference architecture defines the common elements found in each of the four enterprise architecture levels and their typical relationships to each other. The Reference Enterprise Architecture for Transit was developed from a comprehensive, albeit high-level, existing enterprise architecture (EA) developed by the Washington Met- ropolitan Area Transit Authority (WMATA). The WMATA EA presented a starting point that detailed some of the complexities of large transit agencies (with several modes), yet may

OCR for page 4
6 be scaled down to smaller organizations. To ensure that the WMATA EA represented the diverse transit industry, a team of transit IT experts from more than a dozen transit agencies representing small, medium, and large agencies; covering urban/suburban/rural transit; and supporting different modes were brought together to review and walkthrough the architec- ture. In addition, several EA experts from other sectors were included in the expert-peer review group. As other agencies heard about the Reference TEAP, they too asked to partic- ipate in reviewing, piloting, or commenting on elements of the architecture. Three workshops were conducted for the participants to review, recommend, and agree to changes regarding the proposed Reference TEAP. The first workshop highlighted a pre- sentation from the Chief of Architecture from WMATA, Jamey Harvey, on the WMATA EA. Mr. Harvey described the EA organization (metamodel), content, and general principles he used at WMATA. The second workshop focused on how to make the architecture more generic and what segment to select for review and refinement (development of one or more "solu- tions"). The result of this second workshop was the selection of the fare management area for review. Prior to the final workshop, research team members interviewed different agencies that were developing typical and new solutions for fare management. The models included closed systems that most agencies currently implement, an open payment system, and the emerging mobile/branded card payment system. Several transit agencies reviewed the resulting artifacts; some agencies applied their exist- ing systems to the model or solutions to validate them. The results of these pilots are described in Chapter 6. The final reference architecture, the four fare management solutions, stream- lined implementation guidance (with tools and templates), and approach for incorporating solutions were included in the Phase I wiki site.