Skip to main content

Transit Enterprise Architecture and Planning Framework (2011) / Chapter Skim
Currently Skimming:


Pages 24-29

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 24...
... Methodology Used to Develop the Reference Enterprise Architecture for Transit The Reference Enterprise Architecture for Transit was developed from a comprehensive, albeit high-level, existing EA model developed by WMATA. The WMATA EA, which includes several modes and references to other transit management systems, presented a starting point that details some of the complexities of large transit agencies, yet may be scaled down to smaller organizations.
Read the entire page →
From page 25...
... The reference architecture is composed of several sets of entities, including the following: • Metamodel -- Model that shows the organization of the Reference Enterprise Architecture for Transit • Reference Enterprise Architecture for Transit -- Model that shows the reference architecture, including all the entities and relationships – Diagram of the model – Templates and tools that explicitly define the four EA layers, and the institutional and technical drivers of a Transit Enterprise Architecture • Fare Management Solutions -- Four different configurations/ solutions for implementing the fare management segment of the Reference Enterprise Architecture for Transit • Streamlined EA Process -- Streamlined approach for collecting information to customize the reference architecture to meet a transit agency's enterprise These topics are overviewed in the sections that follow. The wiki contains the details and in-depth descriptions of the models, tools, and process.
Read the entire page →
From page 26...
... TEAP metamodel. (Source: Adapted from WMATA Enterprise Architecture, June 2009.
Read the entire page →
From page 27...
... The reference architecture summarizes the enterprise to the business process level; however, many agencies create flow charts that describe business processes to more detailed levels, down to specific operating procedures, subprocesses, decision points, and events (triggers)
Read the entire page →
From page 28...
... Additionally, an application may exchange information with another application. Because there are many off-the-shelf and custom tools that transit agencies use, the Reference TEAP designates a set of categories and types of tools in lieu of commercial or open software products.
Read the entire page →
From page 29...
... Streamlined processes for developing an "as-is" transit enterprise architecture.
Read the entire page →

Key Terms

  • enterprise architecture
  • king county
  • business processes
  • transit agencies
  • transit management

  • county metro
  • corporate goals
  • reference model
  • reference architecture
  • transit industry

  • transit enterprise
  • prise architecture
  • customer information
  • data model
  • maintenance management

  • sit agencies
  • sit agency
  • customer relations


    • 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.