Skip to main content

Currently Skimming:


Pages 1-6

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 1...
... Transit enterprise architecture templates and tools were created by adapting an existing transit enterprise architecture developed by the Washington Metropolitan Area Transit Authority (WMATA) Transit Enterprise Architecture and Planning Framework 1
From page 2...
... The most difficult of the five disciplines for agencies to implement is the enterprise architecture, and very few agencies have the resources or time to implement even part of an enterprise architecture. TEAP Framework Overview The Framework helps transit professionals understand the financial, operational, and management impacts of technologies, to help them better meet their enterprise business process needs and corporate objectives.
From page 3...
... , which is used to model the organization's policies, structure, locations, business processes, information, applications, and technologies, and their relationship to each other (i.e., the organization's blueprint) ; • Business Case Methodology (BCM)
From page 4...
... Phase II Results: Reference Enterprise Architecture for Transit Phase II focused on generating a Reference Enterprise Architecture for Transit, and validating this architecture with transit agencies of different sizes, modes, and organizational structures. POSTIMPLEMENTATION ANALYSIS BUSINESS CASE METHODOLOGY Potential Projects Approved Projects Project Flow Supporting Information Flow KEY EAP Enterprise Architecture IT/ITS Strategic Plan • Performance • Business • Data • Applications • Technology SYSTEMS ENGINEERING • Budget Process • Operating & Capital :: Programs FUNDING INPUTS • Vision / Mission / Goals • Internal • External / Regional Figure 1.
From page 5...
... 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.
From page 6...
... Several transit agencies reviewed the resulting artifacts; some agencies applied their existing systems to the model or solutions to validate them. The results of these pilots are described in Chapter 6.


This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.