Transit Enterprise Architecture and Planning Framework (2011)

Below is the uncorrected machine-read text of this chapter, intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text of each book. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

7Project Objectives The Transit Enterprise Architecture and Planning (TEAP) Framework project sought to provide transit agencies with a roadmap to successfully implement Information Technology (IT) and Intelligent Transportation System (ITS) technologies that meet their business needs. The systems management areas that compose the Framework include the following disciplines: • Enterprise Architecture and Enterprise Architecture Process (EA/EAP) • Business Case Methodology (BCM) • Funding Implementation (FI) • Project Systems Engineering (SE) • Post-Implementation Analysis (PIA) Using methods and techniques promoted by these five dis- ciplines, a transit agency will have a roadmap for planning, assessing, developing, and evaluating their IT/ITS projects. To that end, the TEAP Framework project’s objectives include: • Understanding the state of the practice with respect to the transit industry’s application of five major IT/ITS system management disciplines (including enterprise architecture, business case methodology, funding implementation, project systems engineering, and post-implementation analysis); • Developing an approach to integrate the five IT/ITS system management disciplines into a coherent Framework; • Providing guidance to transit professionals with different levels of technical background about the Framework, its elements, and their relationships; • Developing guidance and tools to help agencies implement the Framework elements, particularly the Enterprise Archi- tecture Planning element; and • Validating the approach with transit agencies. The result of the project is a set of tools and guidance on the five disciplines, collected into a one-stop website that allows collaboration among peers and industry-driven updates as the approach evolves over time. The portal is implemented as a wiki website at http://tcrp-teap.pbworks.com. Transit Enterprise Architecture and Planning (TEAP) Framework Objectives The roadmap incorporates five system management devel- opment methods into a coherent Framework. Each of the methods is complex and requires different skills to accomplish. Understanding how to implement each element of the Frame- work and then to connect the different sections required that the project be divided into two phases. The Phase I objective included identifying the best practices of the wider IT indus- try and the state of the practice for transit, then synthesizing and proposing a Framework to bring these disciplines together. Near the end of Phase I, the Project Team identified critical components of the Framework that were missing from the transit industry and could not be substituted with IT best practices. To that end, in Phase I, the tasks consisted of under- standing the current state of the practice in order to develop the preliminary Framework, guidance, and tools that compose the roadmap to developing successful IT/ITS projects. Specif- ically, the Framework helps: • Guide an agency’s planning process and investment criteria, • Improve its understanding of risks and risk management, • Verify and validate compliance with its needs and stake- holder requirements, • Better manage system project implementation, and • Enhance the measurement of results and benefits. The Phase II objectives focused on developing building blocks for the industry so that they could realistically and more quickly create the foundation of the Framework, the Enterprise Architecture. This was accomplished by adapting an existing C H A P T E R 1 Introduction

enterprise architecture developed by the Washington Metro- politan Area Transit Authority (WMATA) as a reference for transit. This reference is the cornerstone of the TEAP Frame- work and was applied by one or more agencies to validate the guidance for its application. Final Report Scope TCRP Report 84 Volume 9 provides a summary of the out- puts of the project. This report is composed of an executive summary and six chapters with the following scope and objectives: • Executive Summary: This section provides a short overview of the project and its results. The section is most appro- priate for transit managers to obtain an overview of the TEAP. • Chapter 1, Introduction: This chapter provides the objec- tives of the project and the scope of the final report. • Chapter 2, Research Approach—Methodology: This chap- ter provides a summary of the methodology used by the research team for the development of the project outputs. • Chapter 3, State of the Practice: This chapter summarizes the first output of the project—a review by the transit com- munity of the state of the practice in the use of the five sys- tems management areas that compose the Framework. The chapter provides context for the development of a TEAP that is specific to transit. • Chapter 4, Development of the TEAP Framework: This chapter describes the TEAP Framework that was developed and presents resources and tools to support application of the Framework. The chapter presents the Framework roadmap, including its benefits and how to implement it. • Chapter 5, Reference Enterprise Architecture for Transit: This chapter goes into greater detail regarding the refer- ence enterprise architecture and the different solutions for applying fare management application models. The exam- ple and templates contained in this chapter describe how a transit agency can adapt the reference TEAP to represent their business processes, information, application, and tech- nology investments. • Chapter 6, Evaluation and Next Steps: This chapter presents lessons learned from independent transit agencies that either used the TEAP or reviewed the wiki site and its content. 8