Skip to main content

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


Pages 30-36

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 30...
... Pilot Approach A multi-faceted approach was used to obtain transit input to further refine and add resources to the wiki site, and in particular, create a Reference Enterprise Architecture for Transit based on transit agency input. Although two agencies were specified at the panel meeting to participate in the pilot activities, the team chose a multi-faceted approach because of early concerns about the availability of transit agencies with the capability to take on the additional workload of implementing an enterprise architecture planning (EAP)
Read the entire page →
From page 31...
... The focus of the peer review discussion was on the following three areas: • WMATA's taxonomy for a Transit Reference Enterprise Architecture Business Process Model. • WMATA's taxonomy for a Transit Reference Enterprise Architecture Data and Application Model.
Read the entire page →
From page 32...
... Moreover, they saw the benefit in creating a community of enterprise architecture experts in the transit industry to move the industry forward. As new technologies, applications, and business needs change and evolve, new solutions need to be developed, and consequently, models that represent these business needs will be developed and incorporated into the next generation "to-be" architecture models.
Read the entire page →
From page 33...
... • Seeing ABACUS® outputs that were in the transit domain. (For more information, see the section of this report titled "Testing within EA Modeling Software -- ABACUS Enterprise Architecture Software")
Read the entire page →
From page 34...
... Testing within EA Modeling Software -- ABACUS Enterprise Architecture Software In addition to the transit agencies that helped pilot test and comment on the TEAP wiki and EAP materials, one vendor heard of the project and volunteered time and software tools to help with a different type of pilot testing. The vendor worked in conjunction with WMATA staff and the research team to see if the TEAP Transit Reference EA model could successfully be input into general EAP industry modeling software.
Read the entire page →
From page 35...
... • Created a generalization of a transit reference enterprise architecture, with tools and templates, and published it on the wiki. • Developed an approach for transit agencies (large and small)
Read the entire page →
From page 36...
... Conclusion and Final Comments The state of the practice survey and the pilot results demonstrated the transit industry's overall difficulty in finding the needed resources and time to fully develop all the elements of the TEAP Framework within most transit agencies. Return on investment (ROI)
Read the entire page →

Key Terms

  • enterprise architecture
  • technology investments
  • architecture models
  • business architecture
  • king county

  • architecture planning
  • technology investment
  • business processes
  • transit agencies
  • county metro

  • obtain feedback
  • front page
  • project management
  • washington metropolitan
  • reference model

  • process model
  • reference architecture
  • tecture planning
  • transit business
  • transit managers

  • project team
  • transit industry
  • work plan
  • project plan
  • project schedule

  • management office
  • prise architecture
  • architecture plan
  • sit agencies
  • sit agency


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