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 35
35 · Validated the logical consistency of the Reference TEAP · Developed an approach for transit agencies (large and small) (relationships). to apply the reference EA as a building block to expedite the · Provided for demonstration of "what if" scenarios and EAP. visualizations that were not possible for the project team to · Enhanced many parts of the wiki, including the front page. present (due to limited project resources). · Revised and improved the Guidance for Transit Managers. · Received the transit reference EA model information in The TEAP wiki provides several outputs from ABACUS, ABACUS EA software for review via a donation by a ven- including its native file format and hyperlinked report of the dor of time, effort, and access to their software tool. model. In addition, the TEAP MS Excel files are consistent · Gathered many suggestions and other ideas for potential with the ABACUS TEAP content and serve as templates that improvements to the wiki that can be incorporated in the provide round-trip editing tools for any EA tool vendor that future. may wish to enter the transit market. The transit participants in the pilot phase felt that the wiki was very valuable and helped with a wide range of transit Summary and Key Findings issues. Some of the benefits they mentioned are summarized The evaluation phase was successful in achieving the pri- as follows: mary goal of obtaining transit agency involvement in review- · The TEAP wiki can help transit agencies with a number of ing, using, and helping to improve the TEAP Framework issues, such as content on the TEAP wiki. Transit staff participated in the developing effective strategic plans and three EA workshops, provided documents, updated and tai- understanding the importance of knowing their business lored materials for the workshops and the wiki, began the needs before proceeding with technology investments. process of testing and customizing EA materials provided via · The wiki templates can help you identify critical items as the wiki for their own agencies, participated in follow-up inter- you are planning, implementing, or maintaining systems. views, and contributed ideas and materials for improving the · The EAP models and templates on the wiki can be used to TEAP wiki content. create more effective Disaster Recovery Plans. No single agency was able to do an in-depth pilot and test of the EA materials during the TCRP TEAP project time period. In addition, the transit participants gave many suggestions Unfortunately, the current economic troubles in the United and ideas for potential improvements to the wiki that can be States have added even greater stresses on transit agencies, incorporated in the future, such as: including those that wanted to pilot test the materials and tools. All the transit agencies that agreed to participate in the · Develop generic briefing materials for executive managers pilot had less time than they desired to work on it or had to and board members that help them understand the value withdraw. Ironically, at times like these, documentation of of EAP and the need to support EAP efforts. "as-is" and "to-be," such as EAP provides, is most helpful and · Develop information on how to build a business case for valuable in helping maintain, enhance, and develop technolo- EAP, including some examples and key indicators. gies efficiently. Nonetheless, the time that the transit staff was · Reinforce the point that the transit business areas have to able to contribute was highly valuable. be involved. The TEAP project's multi-faceted approach that was · Include national contact information (agency names, staff developed for the pilot, given early concerns about transit names, and phone numbers) for transit agencies that are agency time availability, worked well in obtaining much doing, or are considering doing, EAP or ITS applications. valuable transit feedback and developing new tools and Have it organized by categories. reference materials. The pilot feedback was more diverse, · Consider having a place for vendors and consultants to list coming from many agencies, rather than from one in-depth services, tools, and other related products. study. In the evaluation phase, the research team accomplished · Have some generic project architecture examples on the the following: wiki for things like Wireless Architectures and some ITS applications. · Conducted EA/EAP training workshops. · Investigate the possibility of online chats. · Obtained feedback and documents from transit staff. · Ensure that the wiki contains information on the benefits · Created a generalization of a transit reference enterprise of forming an IT Steering Committee, including benefits architecture, with tools and templates, and published it on to the organization as well as to the participants on the the wiki. committee.