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 10
10
In addition to the high-level summary, the wiki was divided Phase II: Reference Transit
into sections that highlighted the five planning areas and other Enterprise Architecture Process
pages that contained the synthesis results or provided help for
technical and non-technical wiki readers and editors. A site map The Phase II effort focused on refining the guidance, specif-
is also included. Each planning area includes discussions on: ically the enterprise architecture components. The state of the
practice revealed that though many organizations wanted to
· What, why, and benefits; develop enterprise architecture models, they did not want to
· Best practices; and expend the huge effort it required. Other industries, particu-
· Resources about the topic related to transit and other IT larly public sector organizations, deal with this obstacle by
communities. developing reference models that may be used as a template.
WMATA offered their existing enterprise architecture planning
Several interviews and webinars were conducted to evalu- (EAP) model as a starting point for the reference model. So the
ate different aspects of the guidance and wiki site. The research Phase II effort focused on adapting the WMATA EAP for use
validation effort focused on obtaining stakeholder feedback as a generic reference enterprise architecture for transit.
on multiple facets of the Framework, guidance, and tool con- Part of the development and validation process of the ref-
cept. Much of the feedback is reflected in the organization erence TEAP involved convening a peer review panel, com-
and material included in the current site. posed of experts in enterprise architecture and transit IT
domains. Through a series of workshops and interviews, the
panel selected a segment of the transit enterprise for which to
develop detailed solutions (see sidebar). The expert panel
A Solution (or solution architecture) in enterprise
selected the fare management architecture segment and four
architecture is a cross-cutting segment of an
solutions architectures. In addition, the WMATA EAP was
architecture that allocates functions, information,
updated to reflect a "generic" transit agency. Additional guid-
applications, and technology in different configu-
ance was developed for transit staff that explained how to use
rations to solve specific problems and develop
and customize the reference TEAP and fare management
requirements, usually through the design of
solution architecture models. Detailed examples were also
specific information systems or applications.
included in the guidance materials. These are described in
For example, there are different commercial
Chapter 5.
tools to implement different approaches to fare
One or more transit agencies were solicited for piloting the
management, such as (regional vs. agency)
reference TEAP and addressing how the solution architectures
smart cards, mobile devices, and open payment
could help them develop "as-is" and "to-be" architecture mod-
systems. Typically, there will be different types
els. Guidance was developed for most of the agencies, and
of solutions (approaches for implementing
several of them used the templates to validate the approach.
applications and technologies) for every major
Results from these pilots were solicited and documented in
system in the transit enterprise. Each solution
Chapter 6. In addition, several of the expert panel members
may affect relationships among the business
who attended the workshops and reviewed the reference TEAP
processes and information views.
and wiki were interviewed about enhancing the wiki. Results of
these interviews are also included in Chapter 6.
