**Contract No.**

**Task Order No.**

**Title:** HOV Facility Performance Monitoring, Evaluation & Reporting
Handbook

**COTM:** Jon Obenberger, HOTM, (202) 366-2221

**IQC Tasking:** Task E - Compete between Battelle (Attention Katie
Turnbull, TTI) and Cambridge Systematic (Attention Chuck Fuhs, PB
Farradyne)

**Proposed Cost:** \$ 300,000

**Period of Performance:** 20 months from WOA

# 1. SCOPE OF WORK: {#scope-of-work .unnumbered}

> Task Order Objectives:
>
> The purpose of this project is to develop a handbook that will serve
> as a technical reference that provides guidance and recommended
> practices on the need for, how to initiate, sustain, and use
> information generated from monitoring, evaluating, and reporting on
> the performance of HOV facilities. This document is intended to be a
> comprehensive technical reference providing guidance on how to
> develop, implement, improve, and sustain a continuous performance
> monitoring, data management, evaluation and reporting program or
> initiative for an HOV system. The use or application of these
> recommended practices will also in time, serve to enhance the
> planning, management, design, operation, and performance of HOV
> facilities.

In addition to developing this handbook, the project will also involve
the development of a technical presentation of the subject, tri-fold
brochure, primer, and other related tools to assist with the outreach
and awareness related to this project. This project also includes a task
to provide technical and administrative support to the FHWA Office of
Travel Management (HOTM) related to HOV facility related issues.

The intended audience of the handbook and these products includes
representative state DOTs, Metropolitan Planning Organizations, transit
agencies, enforcement agencies and others having a role in the planning,
development, management, operation, monitoring, evaluation, and
reporting on the performance of HOV facilities. Targeted end users of
the handbook are first level supervisors and technical staff (planners
and operators) involved in the collection, dissemination and warehousing
of data, and monitoring, evaluation and reporting of data to various
audiences.

> Background:

The need for greater emphasis in performance monitoring is growing as a
reflection of the large number of projects now in operation. Public and
policy makers want to know if an investment in HOV lanes has been
worthwhile, and know if they are performing according to expectations. A
prior FTA sponsored report addressing performance monitoring and
evaluation and chapter on HOV Performance Evaluations helped pave the
way for an understanding of the important role that these activities
serve for HOV lanes. Various guidelines and methods were illustrated for
addressing typical HOV measures. Although many areas conduct some form
of HOV performance monitoring based on these measures, evaluation and
reporting efforts vary greatly between regions. Performance monitoring
provides information for a number of people to make sound planning and
operational decisions for the individual projects or the system as a
whole.

> Without appropriate performance monitoring data, there is little basis
> for assessing how HOV lanes are operating in terms of cumulative
> benefits toward accomplishing regional transportation goals, and for
> defending HOV operation performance and policies from public scrutiny
> and legislative efforts to modify or overturn policy. Where monitoring
> is currently performed, there is often a disconnect between HOV goals
> and monitoring efforts, a lack of consistency in the data collected
> and analyzed, and a lack of information sharing which is particularly
> useful to help validate HOV performance between areas. As such, the
> profession is not able to adequately take advantage of "lessons
> learned" in planning, designing and operating HOV facilities.
>
> Currently, the only data collection guidance for performance
> monitoring provided nationally is in the HOV Systems Manual. The
> ability to monitor performance is inhibited by the availability and
> accuracy of necessary data. Manual data gathering may not be feasible
> due to a number of constraints. As data gathering techniques continue
> to become more automated, the potential to use this data increases.
>
> However, the evidence to date suggests that much of the automated data
> currently being collected is not easily retrievable, "clean" to
> readily use for performance evaluation purposes, and cannot be easily
> or effectively warehoused and accessed for historical purposes. These
> shortcomings have limited the effectiveness of this data to track
> trends and compare findings. Without developing an adequate and
> accurate means of collecting and archiving data, performance
> monitoring cannot be performed. HOV performance data management
> techniques need to be defined and confirmed, including use of the
> latest technologies, so that ITS architectural standards can be
> responsive to this need.
>
> Data collection and management activities include:

-   Set a framework for data management activities, define functional
    ways of collecting, analyzing and compiling data for each key
    measure responding to project goals and objectives, and identify
    various means of reporting outputs to various audiences.

-   Justifying the data collection process: for HOV projects and system
    level needs, promote an understanding of the data collection
    function by identifying HOV performance monitoring applications for
    data that is collected, such as mobility, accessibility, air
    quality, fuel consumption, safety, accidents and cost effectiveness.

-   Performance measures and data considerations: evaluate types and
    methods of HOV data collection, new technologies for measuring
    occupancy, travel speeds, and commute times.

-   Data quality and requirements: Determine appropriate performance
    measure thresholds to trigger HOV lane operational changes and/or
    lane enhancements.

-   Data fusion and archiving: Recommend data collection, refinement,
    dissemination and archiving best practices for the purposes of
    performance monitoring and evaluation.

-   Database and data management techniques: Explain techniques for how
    data will be processed and the functional requirements associated
    with a data management plan that can be automated to meet day-to-day
    needs.

-   Reporting and sharing of reporting: Examine what is needed to
    support ongoing reporting for performance monitoring, marketing and
    education, improved planning and design, and better project
    accounting. Reporting will examine the overall roles of agencies and
    staff including budget, staff, traffic management interface and
    in-kind agency contributions. Recommend ways for reporting data in
    public friendly ways to a variety of diverse stakeholders
    encompassing environmental, traffic, transit, and public policy
    interests.

> Performance monitoring, evaluation and reporting activities include:

-   Review Prior References: Examine guidance contained in the HOV
    Systems Manual, FTA Performance Monitoring Guidelines report, the
    FHWA "State of the Practice in HOV System Performance Monitoring"
    White Paper and recent available monitoring documentation. As
    background, confirm the usefulness of this information, data
    collection and evaluation techniques presented, issues presented and
    addressed, typical issues confronted now, identified gaps and
    research needs as outlined in these references and identification of
    potential planning, operation and design needs at the region,
    corridor and/or project level. Define unique needs associated with
    each HOV mode.

-   Links to Goals and Objectives: Examine a set of typical goals and
    objectives for the HOV system and identify appropriate performance
    measure links and measures of effectiveness applicable to each.
    Examine alternative means of addressing performance measures and
    trade-offs to each. Note validity of measures appropriate at the
    corridor or regional level of evaluation. Examine goals and
    objectives appropriate to existing projects and future extensions or
    improvements to HOV lane systems.

-   Data Collection: Identify and develop best practices for HOV data
    collection, issues currently confronted including available
    resources and experience, site selection and surveying techniques,
    optional data retrieval systems, data management and warehousing and
    data management planning. Best practices will include lessons
    learned from recent data collection efforts in case study locations
    where HOV system monitoring as been practiced for a number of years.
    Develop techniques that address a means for information management
    and dissemination, including prototypical systems for data storage,
    analysis and reporting of measures such as traffic volume,
    occupancy, travel times and violation rates. Examine ways to make
    data user-friendlier in the form of GIS maps and charts, and in
    formats appropriate for publication on-line.

-   Evaluation Techniques: Determine the appropriateness of specific
    techniques for addressing defined performance measures. Describe
    trade-offs in techniques, and the level of ease/difficulty,
    anticipated accuracy and cost associated with each. Develop a
    prototype evaluation plan for a project, corridor and system at
    varying levels of investment (system wide annual assessment and "the
    basics" for isolated projects), and link these to specific goals and
    objectives. Develop evaluation techniques specific to each HOV mode,
    such as bus transit, carpools and vanpools, motorcycles, ILEVs and
    mixed use express traffic in managed lanes. Use case studies from
    current projects to provide best practice experience.

-   Developing Consistency: Examine the basics for improving monitoring
    consistency between projects and systems. Look at the most commonly
    applied goals and objectives and define a limited level program that
    can offer comparable data collection, evaluation and reporting on
    key parameters found among HOV projects performing monitoring today.

-   Improved Data Reporting: Examine the different audiences and
    functional activities (planning, design, operation, enforcement)
    needing performance monitoring output and develop example reporting
    guidelines and formats to meet typical needs of each. Link these
    needs to the identified goals and objectives affecting
    project/corridor and regional level needs. Provide case studies,
    methods for comparing information, and questions reporting should
    address.

> The definition of a successful HOV lane operation needs to be clearly
> understood for each setting, with the monitoring program reflecting
> these goals and objectives for the respective projects or systems. The
> clear definition of realistic HOV goals helps define the appropriate
> evaluation procedure to determine whether the project or system is a
> success, and if it does not meet the goals, what happens. A
> comprehensive consideration of best practices is missing in current
> HOV guidance. Best practices need to be identified and developed to
> address how to best monitor, evaluate and report performance of HOV
> lanes. Specific issues commonly raised in assessing or defending
> specific operation policies are not covered in current guidelines, nor
> do the current guidelines offer a comprehensive assessment and link
> between performance functions and planning, design and operation
> needs. Case studies from recent performance work, missing from these
> reports, could offer examples of best practice.

An updated to the existing FTA technical reference on HOV facility
evaluation is needed to provide additional direction, guidance, and best
practices associated with the state-of-the-practice and needs of
agencies associated with monitoring, evaluating and reporting on the
performance of HOV facilities. The handbook to be developed by this
project will focus on influencing the development, use, and
implementation of performance measures, data collection and management,
monitoring, evaluation of effectiveness, and reporting on the
performance of HOV facilities. Additional guidance is needed on the
supporting management systems, processes, and methods agencies can use
to manage, assess, and track the performance of HOV facilities and
influence of various support services. This project will build off of
previously completed or current initiatives that provide insight and
examples on some of the key topics and related issues that will be
covered in this document. These documents include:

-   HOV Systems Manual; NCHRP Report 414; February 1998;

-   HOV Lane Performance Monitoring: 2000 Report, Washington DOT,
    February 2002;

```{=html}
<!-- -->
```
-   Performance Measures of Operational Effectiveness for Highway
    Segments and Systems; NCHRP Synthesis 311; 2003;

-   Travel Time Data Collection Handbook; Report No. FHWA-PL-98-035;
    March 1998;

```{=html}
<!-- -->
```
-   Performance Measures (e.g., FHWA publications, NCHRP Reports);

-   Transportation Planning (e.g., FHWA publications, NCHRP Reports);

-   Data Collection, Archiving, and Management (e.g., FHWA publications,
    NCHRP Reports);

-   HOT Lane Development Guide (FHWA);

-   Decision Support Methodology for Selecting Traffic Analysis Tool;

-   Guidelines for Applying Traffic Simulation Modeling Software; and

-   FTA Performance Monitoring Guideline Report.

> An initial list of key topics and technical issues have been
> identified in Section 6 of this task order to provide an initial
> organization of this handbook for the Contractor. This handbook will
> be similar in focus, detail, and scope to the existing Freeway
> Management Handbook that can be accessed at:
> http://ops.fhwa.dot.gov/Travel/traffic/handbook.htm.
>
> The Contractor will be responsible for addressing all of the feedback
> that is received from various interests with each of the deliverables
> to be produced in this task order. The HOV Pooled Fund Study (PFS)
> members, or their designated representatives, will serve as the key
> group that will be involved with and for providing feedback throughout
> this task order. Other practitioners will be added to this team based
> on their level of interest. On behalf of FHWA and the HOV PFS, the
> Contractor will be responsible for sending electronic requests to
> practitioners asking to review and provide comments on the draft
> products to be produced at key milestones in this project.
>
> The Contract Officers Task Order Manager (COTM) will provide an
> initial list of these practitioners to the Contractor. This list will
> include, but not be limited to, the ITE TMC Committee, ITE Transit
> Council, TRB Freeway Operations Committee, TRB HOV Systems Committee,
> and TRB Pricing Sub-Committee. The outreach and interaction with these
> different groups is assumed to occur electronically either through
> e-mail correspondence or teleconferences. Monthly status report
> meetings with the HOV Pooled Fund Study project review team and the
> COTM will occur monthly.

**Technical Approach:**

## Annotated Outline, References, and Detailed Work Plan

> The annotated outline (as described in subtask A.3) is central to the
> development of an approach as it will provide a framework for the
> final technical document and will identify key topics and issues to be
> addressed. The products of this task will include the kickoff meeting,
> list of technical references, work plan, and annotated outline.

### Kickoff Meeting

> Within 21 calendar days of contract initiation, attend a kickoff
> meeting with the Contract Office Task Manager (COTM), Jon Obenberger.
> At the kickoff meeting, the Contractor shall be prepared to present
> and discuss the proposed approach to performing the activities
> identified and produce the products identified in this task order. The
> Contractors presentation (PowerPoint format) at the kick-off meeting
> shall also cover include work plan, project fact sheet, key issues and
> critical path for each deliverable identified in the task order (e.g.,
> key milestones, schedule, stakeholder involvement, outreach). This
> shall include but not be limited to the approach for completing the
> literature review, assessment of current practice, annotated outline,
> development of the guidance document, communications plan and outreach
> material, and white paper identifying research needs.
>
> An initial draft two-page project fact sheet shall be submitted prior
> to the kick-off meeting. This fact sheet should be updated at key
> milestones during the project. The information on this fact sheet
> shall include, but not be limited to, the purpose of the project, need
> for the document, expected influence it is expected to have on
> practice, key technical topics and cross-cutting issues to be covered
> in the document, key milestones, project deliverables, and contact
> information. Subtask C.1 contains additional information on the
> project fact sheet.
>
> Based on comments received, a revised version of this project fact
> sheet may need to be resubmitted following the kick-off meeting.
>
> The kickoff meeting will take place at either the FHWA Headquarters
> Office or Turner-Fairbank Research Center. The Contractors Task Order
> Leader (TOL) should attend the kickoff meeting. The COTM may determine
> that the TOL could participate in this meeting via teleconference.
> Other key personnel shall participate via teleconference.

### References and Detailed Work Plan

> This deliverable shall include references to all literature that the
> Contractor may use in producing the technical document, or references
> related to HOV facility performance monitoring, evaluation and
> reporting that go above and beyond current state-of-the-practice. Each
> reference shall be accompanied by a brief description (three to four
> sentences) of the contents of the reference, assessment of the
> applicability, and usefulness to this project.
>
> The Contractor shall also prepare a detailed work plan illustrating
> the means and strategies for collecting and compiling additional
> information that is required for the project that may not be
> documented in literature. The Contractor shall submit the rationale,
> description, identify the technical topics and issues, potential case
> studies or examples, and estimated level of effort, schedule,
> itinerary, and receive COTM approval prior to initiating any work to
> collect this information. Within the work plan, the Contractor shall
> recommend means and strategies for collecting specific techniques,
> lessons learned, or obtaining examples related to HOV facility
> performance, monitoring, evaluating and reporting. The work plan shall
> also include an approach for developing an understanding of the
> institutional, technical, and procedural issues to consider,
> challenges, and other factors that may influence local practices with
> developing, sustaining, or using methods for data collection, data
> management, and performance monitoring and evaluation on HOV
> facilities.
>
> Within 21 calendar days of contract initiation, the Contractor shall
> submit to the COTM an initial list of references and work plan. The
> COTM will review the list of references and work plan and provide
> feedback within 14 calendar days of receipt from the Contractor.
> Within 45 calendar days of contract initiation, a conference call may
> be held with the Contractor to discuss the comments that are submitted
> by the COTM for both the list of references and work plan. If
> requested, the Contractor shall submit a revised work plan and list of
> references within 14 calendar days of receipt of written feedback from
> the COTM.

### Annotated Outline 

> The Contractor shall prepare an annotated outline that will serve as
> the basis from which the technical document will be developed in Task
> B. This annotated outline is intended to provide the foundation,
> context and framework for the subject matter, key technical topics and
> associated issues, and major concepts that will be included of the
> document. The annotated outline shall clearly describe and indicate
> the intended structure, key topics, and supporting issues to be
> presented in each chapter (e.g., objectives; section topics,
> description, key issues and information to be covered,
> state-of-practice summary, trends, profile of successful practices),
> figures (e.g., charts, photos, diagrams) and other items to be
> included in the draft document (e.g., appendix).
>
> The preparation of this annotated outline will evolve through the
> development and submittal of three versions of this outline that will
> vary in detail and information provided. These three versions will
> allow the Contractor and the COTM to focus and agree on the key
> messages themes, organization, content, and how to format or present
> the subject matter prior to initiating the development of the draft
> document. These annotated outlines are intended to serve as working
> documents and they are not intended for publication as a separate
> report.
>
> *Initial Annotated Outline*. This outline shall focus on the
> high-level issues, key components, themes, messages, chapters,
> sections and subsections, and supporting issues to be covered in the
> document. This outline should also present in the appropriate
> locations the justification and focus for the document (e.g., purpose,
> objective, summary of current practices and gaps being addressed,
> intended audience, expected influence it will have on practice) and
> each chapter (e.g., purpose, objectives, context for subject matter,
> relationship and relevance to other chapters). The ITE Traffic
> Management Center Operations Manual annotated outline is an example of
> the minimum acceptable level of detail that should be provided in this
> deliverable for the annotated outline. Note that this example does not
> contain all of the information that the Contractor will be required to
> provide for this document. This example can be accessed from the
> Institute of Transportation Engineers web site at
> [http://www.ite.org](http://www.ite.org/).

The Contractor shall submit this initial annotated outline to the COTM
within 60 calendar days of contract. The COTM will provide comments on
the Initial Annotated Outline within 14 calendar days of receipt. A
special meeting may be held via teleconference to discuss the comments
that are submitted by the COTM.

> *Draft Annotated Outline.* At a minimum, this outline shall address
> all of the issues and detail for the final annotated outline that have
> been previously identified in this subtask. Within 95 calendar days of
> contract initiation, the Contractor shall submit to the COTM the draft
> annotated outline that is responsive to the COTM comments that were
> submitted on the initial annotated outline. The COTM will provide
> comments on the draft outline within 21 calendar days of receipt of
> the draft. A special meeting may be held via teleconference to discuss
> the comments that are submitted by the COTM.
>
> *Annotated Outline.* Within 135 calendar days of contract initiation,
> the Contractor shall submit to the COTM a revised annotated outline
> that is responsive to the COTM's comments that were submitted on the
> draft annotated outline. The COTM will provide comments on the revised
> outline within 21 calendar days of receipt of the document. The
> Contractor shall incorporate the comments received from the COTM into
> the development of the Draft Technical Document specific in Task B. A
> special meeting may be held via teleconference to discuss the comments
> that are submitted by the COTM. The Contractor cannot proceed with any
> work toward producing the Technical Reference Document specified in
> Task B of this task order without the approval from the COTM.

## Produce Technical Document

### Technical Document Mockups

> The purpose of developing these mockups are to identify and
> demonstrate alternative methods of presenting the information that
> will be contained in this reference for use by the target audience.
> These alternative formats may include, but not be limited to,
> addressing different page layout, reference and cross-reference
> methods and styles, indexing, use of color, presentation of key
> information (e.g., check lists, highlight successful or recommended
> practices, emphasize key points), layout and access issues appropriate
> for both printed and electronic versions of the technical document.
> This subtask and mockups are expected to be a very minor activity and
> is not expected to require a significant effort by the Contractor.
>
> The Contractor shall submit to the COTM at least two mockups of a
> sample of the proposed format and layout that will be used for a
> typical chapter to be included in the technical document within 210
> calendar days of the initiation of this task order. The COTM will
> provide comments on the proposed mockups of the technical document
> within 21 calendar days of their receipt. The Contractor shall
> incorporate the comments received from the COTM into the development
> of the draft technical document that is submitted in Task B.2.

### Draft Technical Document

> The technical document to be developed for this task order shall be
> responsive to the task order objectives, key technical topics and
> issues that are presented in Section 6, annotated outline developed in
> Task A, and additional direction provided by the COTM. The Contractor
> is strongly encouraged to submit chapters of the initial draft
> technical document incrementally for the COTM's review. The Contractor
> should indicate in the work plan the proposed schedule for submitting
> both the initial and revised draft chapters if incremental delivery of
> the draft technical document is desired. The incremental submittal and
> review of the initial and draft chapters will allow the COTM to
> provide the Contractor with comments earlier in the process of
> developing the draft technical document.
>
> The Contractor shall complete the incremental submittal of the initial
> draft chapters of the technical document within 280 calendar days of
> the initiation of this task order. The COTM will provide comments
> within 28 calendar days of the receipt of the initial and revised
> drafts that are submitted for each chapter. The Contractor shall
> submit the revised draft of each chapter in the technical document
> that is responsive to the COTM's comments within 60 calendar days of
> receipt of those comments.
>
> The Contractor shall complete the incremental submittal of the revised
> draft chapters of the technical document within 380 calendar days of
> the initiation of this task order. The Contractor shall receive
> approval from the COTM prior to initiating any work on the Final
> Technical Document (subtask B.3).
>
> One meeting will be held with the Contractors TOL to discuss the
> review comments that are submitted by the COTM for both the initial
> and the revised draft of this technical reference document. Only one
> of these two meetings may take place in the greater District of
> Columbia metropolitan region with the other being a teleconference.
> Only the Contractors TOL would be required to attend this in-person
> meeting if it is held, with other key personnel on the Contract
> participating as needed via teleconference.

### Final Technical Document

> Within 465 days of contract initiation, the Contractor shall submit
> the final version of the *High Occupancy Vehicle (HOV) Systems
> Performance Monitoring, Evaluation and Reporting* handbook. The COTM
> will provide comments within 21 days of receipt of this final
> document. The Contractor shall submit the final technical document
> that is responsive to the COTM's comments within 21 calendar days of
> receipt of these comments. The Contractor may be required to perform
> minor editorial and technical revisions on issues not addressed in the
> final handbook that is submitted to the COTM.
>
> The Contractor's TOL shall attend the HOV PFS Annual Meeting that is
> anticipated to be held in the winter of 2003 or 2004 (spring or
> summer) to report on the progress of this project, provide an overview
> of this document, and key findings. The Contractor's TOL shall also
> participate in a national videoconference and/or webcast to present
> the findings and recommendations identified in this document. The COTM
> will make all of the arrangements, perform the necessary outreach, and
> facilitate this videoconference or webcast. The final project and/or
> subject presentation for this document should provide the basis for
> the Contractor's presentation.
>
> The final technical document shall conform to the FHWA publication
> guidelines and the requirement specified in Section 4 for deliverables
> to be developed and submitted in this task order. FHWA will be
> responsible for publication and distribution of the final document.

## Outreach Material, Tri-fold Brochure, and Distribution Plan

> This task will include the development and update of different
> outreach material throughout the project. The Contractor will submit
> to the COTM for review and approval a project fact sheet, presentation
> on subject matter, tri-fold brochure, and distribution plan.

### Project Fact Sheet, Presentation, and Outreach Material

> The Contractor shall develop, submit, and maintain different outreach
> related items to support the needs of the COTM and HOV PFS members
> throughout the project. The following is a list of items the
> Contractor will submit to the COTM for review and approval:
>
> \-*Project fact sheet.* The purpose of the project fact sheet is to
> identify the purpose, benefit or value, key aspects, and identify
> successful practices with developing measures and methods for HOV
> performance monitoring, evaluation and reporting. The information
> contained in the project fact sheet shall highlight the key aspects
> identified in the final handbook. The intended audience of this fact
> sheet is any individual that is engaged with or responsible for the
> planning, design, operation or maintenance of HOV systems and
> transportation management systems.
>
> Similar fact sheets that are considered acceptable examples of what
> the Contractor will develop for this work task order include the Work
> Zone Safety Awareness or Customer Driven Satisfaction in Illinois that
> are accessible at: <http://ops.fhwa.dot.gov/wz/factshet.htm>. The
> final version of this fact sheet to be developed shall conform to the
> FHWA publication guidelines and the requirements specified in Section
> 4 of this task order. FHWA will be responsible for publication and
> distribution of this fact sheet.
>
> The Contractor shall submit an initial draft copy of this two-page
> project fact sheet prior to the kick-off meeting and updated when
> appropriate at key milestones during the project. The Contractor shall
> submit a revised draft copy of this project fact sheet within 430
> calendar days of initiating this task order. The COTM will provide
> comments to the Contractor within 28 calendar days. The Contractor
> shall submit a final presentation that is responsive to the COTM's
> comments within 28 calendar days of receipt of these comments. The
> Contractor may be required to perform minor editorial revisions to the
> final fact sheet submitted to the COTM.
>
> \-*Project presentation.* This presentation will provide an overview
> of the project (e.g., issues/challenges in current practice, purpose
> of project, key findings, products to be developed, intended
> audiences, schedule, etc.) and similar issues identified for the
> project fact sheet. The presentation will include speaker notes and
> will be periodically updated by the Contractor at key milestones
> during the project. The format of this presentation shall be in
> Microsoft PowerPoint. This presentation shall be submitted following
> the kick-off meeting and updated when appropriate at key milestones
> during the project.
>
> *-Subject Presentation.* This product will involve the development of
> a presentation that will provide an overview of the subject matter
> that is contained in the technical document (e.g., issues/challenges
> in current practice, overview of subject, key issues, state of
> practice, gaps in practice, trends, recommended practices, lessons
> learned, resources available (e.g., technical guidance, training,
> technical support), brief overview of handbook (including purpose,
> intended audience, outcome and findings, list of chapter, products
> developed, where to access copy, etc.). Note this is intended to be a
> presentation on the subject matter and not a summary or overview of
> the handbook being developed. The intended audience of this
> presentation is executives, senior, mid-level managers, and technical
> staff that may be involved in or responsible for setting policies,
> allocating resources, transportation planning, providing transit
> services, establishing direction for programs, creating policies and
> procedures, or training related to transportation management systems
> and traffic operations programs.
>
> This presentation is assumed to be 30-40 minutes in length. The final
> version of the presentation that is developed shall conform to the
> FHWA publication guidelines and requirements specified in Section 4.
> The format of this presentation will be in Microsoft PowerPoint and
> will include the detailed speaker's notes to accompany the
> presentation.

FHWA will be responsible for publication and distribution of this
presentation. The Contractor shall submit a draft copy of the
presentation within 430 calendar days of initiating this task order. The
COTM will provide comments to the Contractor within 28 calendar days.
The Contractor shall submit a final presentation that is responsive to
the COTM's comments within 28 calendar days of receipt of these
comments. The Contractor may be required to perform minor editorial
revisions to the final presentation that is submitted to the COTM.

### Tri-Fold Brochure

> The purpose of this brochure is to identify key aspects, profile
> successful practices, identify the benefits or value, and describe why
> agencies should develop performance measures and evaluation practices
> on HOV facilities. The information contained in the brochure shall
> highlight the same concepts and result identified in the technical
> presentation and fact sheet. The intended audience of this brochure
> will be directed at community leaders, executive managers, and other
> key interests that have the potential to allocate resources or
> influence local practices or participation of their agency or staff on
> traffic management or HOV system related issues. This will require the
> Contractor to work with the HOV Pooled Fund Study members to obtain
> the necessary testimonials determined to include in the brochure.
>
> Similar examples of the type of brochure to be developed for this work
> include the "Using ITS in Work Zones" and "It's About Time: Traffic
> Signal Management" brochures. This Work Zone brochure can be accessed
> as Document #13584 through the ITS Electronic Document Library at:
> [www.its.dot.gov/welcome](http://www.its.dot.gov/welcome).
>
> Within 430 calendar days of the task order initiation, the Contractor
> shall submit to the COTM a draft of a Tri-Fold brochure that is
> defined in this sub-task. The COTM will provide feedback within 28
> calendar days of the receipt on this draft brochure. The Contractor
> shall submit a revised brochure that is responsive to the COTM's
> comments within 28 calendar days of the receipt of these comments. The
> Contractor may be required to perform minor editorial revisions to the
> final brochure that is submitted to the COTM.
>
> The final brochure shall conform to the FHWA publication guidelines
> and the requirements specified in Section 4 for deliverables to be
> developed and submitted in this task order. FHWA will be responsible
> for publication and distribution of this document.

### Primer

The purpose of this primer is to identify for a non-technical audience
the key aspects, identify key issues for their agencies to consider,
identify the benefits and/or value, recommended practices and lessons
learned, profile successful practices. The information contained in the
primer shall highlight the same concepts, lessons learned, and
recommended best practices identified in the technical document,
presentation, fact sheet, and brochure. The intended audience of this
primer will be directed at community leaders, executive managers, and
other key interests that have the potential to allocate resources,
change local practices, and make decisions or manage programs that will
directly or indirectly influence TMCs.

> The length of this primer is assumed to be 16-24 pages in length. A
> similar example of the type of document to be developed for this task
> order is the "Incident Management Successful Practices: A
> Cross-Cutting Study" that can be accessed through the electronic
> document library on the USDOT ITS Program web site at
> <http://www.its.dot.gov/welcome> as document #11484. The final version
> of the primer that is developed shall conform to the FHWA publication
> guidelines and the requirements specified in Section 2 of this task
> order. FHWA will be responsible for publication and distribution of
> this primer.
>
> Within 375 calendar days of contract initiation, the Contractor shall
> submit to the COTM a detailed annotated outline for this primer. The
> COTM will provide comments within 21 calendar days of receipt of this
> annotated outline. The Contractor shall submit a draft Primer that is
> responsive to the COTM's comments on the annotated outline within 430
> days of contract initiation. The COTM will provide feedback within 28
> calendar days of receiving the draft primer. The Contractor shall
> submit the final primer that is responsive to the COTM's comments
> within 28 calendar days of receiving these comments. The Contractor
> may be required to perform minor editorial revisions to the final
> primer submitted to COTM.

### Questions and Answers

The purpose of this material is to provide the general background
information and answer the questions commonly asked by a non-technical
audience (e.g., public, media, community leaders, etc.) related to the
subject matter. The Questions and Answers shall include 20 key issues on
the importance and issues to be considered with HOV performance
monitoring, evaluation and reporting. Examples of acceptable
deliverables that the Contractor can use in developing this product
include the Washington DOT HOV System Program on HOV Lanes
(<http://www.wsdot.wa.gov/hov/>) and Value Pricing Facts and Frequently
Asked Questions
(<http://www.hhh.umn.edu/centers/slp/projects/conpric/index.htm>). *The
level of effort for this subtask is considered to be very minor.*

> Within 430 calendar days of the task order initiation, the Contractor
> shall submit to the COTM a draft questions and answers sheet. The COTM
> will provide feedback within 28 calendar days of receipt. The
> Contractor shall submit a final questions and answers sheet that is
> responsive to the COTM's comments within 28 calendar days of the
> receipt of these comments. The Contractor may be required to perform
> minor editorial revisions to the final version of the item that is
> submitted to the COTM.

### Distribution Plan

> The purpose of this plan is to raise the awareness of the availability
> of this document, identify the audiences that should receive copies,
> and items to support their distribution. Detailed examples of a
> Distribution Plan, Distribution Letter, and Electronic Notice of the
> availability of the products produced by this task order can be
> accessed on the HOV PFS web site (<http://hovpfs.ops.fhwa.dot.gov/>)
> and will be provided to the Contractor. The focus of the Contractors'
> effort with this subtask will be to modify the examples that are
> provided to accommodate the subject and audience for the products
> produced. *The level of effort for this subtask is considered to be
> very minor.* The following is a description of these items:
>
> -Distribution letter to FHWA Resource Centers and Division Offices;
>
> -Electronic notice identifying the availability of document and where
> to obtain a copy;
>
> -Distribution list of agencies, organizations, web sites, listserv,
> and other interests should be notified of the availability of the
> products produced by this task order; and
>
> Within 430 calendar days of the task order initiation, the Contractor
> shall submit to the COTM a draft Distribution Plan, distribution
> letter, and electronic notice. The COTM will provide feedback within
> 28 calendar days of receipt. The Contractor shall submit a final
> Distribution Plan, distribution letter, and electronic notice that are
> responsive to the COTM's comments within 28 calendar days of the
> receipt of these comments. The Contractor may be required to perform
> minor editorial revisions to the final versions that are submitted to
> the COTM.

**Task D. Technical and Administrative Support** *(Estimated to be
\~\$40,000)*

The objective of this activity is to provide the technical and
administrative support necessary for different activities that may be
initiated or address key issues that public agencies are facing
associated with various HOV facility issues. The activities that may be
pursued will be aimed at increasing the awareness, advancing the
state-of-the-practice of public agencies, and identify the research and
technology transfer needs necessary to consider and use various proven
and innovative lane management strategies. The focus of these activities
may consider policies, planning, design, implementation, management,
operation, enforcement, marketing, performance monitoring, and
evaluation of managed lane facilities and various operational
strategies.

These activities may also involve performing literature reviews,
conducting surveys, or interviews to compile, document, analyze, and
summarize this information. These tasks will include but not be limited
to preparing presentations, briefing material, position or technical
white papers, developing content for presentation on web page related to
various topics or issues, updating the inventory of existing or planned
future HOV facilities, facilitating the interaction and review of
various products developed with the appropriate stakeholder groups, and
other related activities. The compilation of this information may
involve the preparation of tables, graphs, databases, brochures,
reports, white papers, or other related items. These activities also may
involve developing case studies on innovative applications identified in
the process of developing the HOV Facility Performance Monitoring,
Evaluation, and Reporting Handbook.

Prior to initiating any specific activity the administrative support,
services, and technical expertise necessary for each activity will be
identified in greater detail with the TTI manager. This will also
involve defining the scope, issues to address, technical expertise
required, format and final products to be developed, estimate of hours,
schedule, and cost.

# 2. Level of Effort and Period of Performance {#level-of-effort-and-period-of-performance .unnumbered}

> The total budget available for the work to be performed for this task
> order is \$ 250,000. The proposal to be submitted by the Contractor
> shall be based on this total estimated cost, including the direct
> costs and fixed fee for performing all of the tasks and related
> activities identified and associated with this task order. It is
> expected that the Contractor will begin this task order within 14
> calendar days of receiving the official start notice for the
> Contractor and/or subcontractors to initiate work on this task order.
> All work and services required hereunder shall be completed on or
> before 16 months after the effective date of the contract.

# 3. Staffing and Cost Proposal {#staffing-and-cost-proposal .unnumbered}

> The Contractor shall propose a team of individuals with experience in
> planning, designing, managing, and operating HOV facilities and
> systems. The team that is proposed should include the staff from the
> appropriate subcontractors that are a part of the firm's present
> indefinite quantities contract team. These individuals should have
> first hand knowledge, experience, and ability with the following key
> areas of the project: (No priority or importance implied with order)

-   Planning, design, management, and operation of HOV facilities and
    systems.

-   Development of technical references, recommended practices, or
    resource guides for public agencies related to the management and
    control of traffic or operation of HOV systems.

```{=html}
<!-- -->
```
-   Experience with analyzing the state-of-the-practice, developing
    recommended procedures, and practices related to the planning,
    design, and operation of HOV systems. This requires an understanding
    of the role, relationship, and how technical references, recommended
    practices and lessons learned, industry standards, agency policies,
    procedures, regulations, training, and other technology transfer
    initiatives can collectively influence the state-of-the-practice.

-   Understanding and experience with developing procedures and
    requirements for performance measures, monitoring, evaluation, data
    collection, and reporting on HOV facility performance.

-   Experience with using performance measures in planning, design,
    procurement, implementation, or operation and maintenance of HOV
    facilities.

-   Planning, coordinating the activities, and facilitating the
    interaction of public agencies related to the development of the
    policies, operational strategies and procedures, and integrating HOV
    facilities and other ITS service functions (e.g., TMCs, traveler
    information service providers, transit management systems, emergency
    management, etc.) in support of a proactive transportation
    management system in a region.

> It is possible for Contractor, Subcontractor, or specific individuals
> to have acquired relevant experience, expertise, and qualifications
> related to managing, leading, supporting, and performing various HOV
> studies, developing performance measures and evaluation procedures,
> developing or directing various management processes, transportation
> programs, or freeway management initiatives for public agencies in
> several ways, including:

-   Work performed directly by the firm. Please do not include work
    performed by individuals in the firm that are not expected to
    contribute in a meaningfully way or perform specific activities in
    this task order. With each reference, indicate if the firm was
    serving as a subcontractor to another firm or organization (and if
    so, provide the name of the organization and contact information),
    identify the specific role, and tasks that were performed. Do not
    include work for which the firm was a prime contractor but the
    project actual tasks were performed by a subcontractor.

-   Work performed by individuals of the firm, before the firm employed
    them, i.e. "John Doe of our firm, led the development of the XXXXXX
    for the Northern Virginia Region." Please indicate the specific
    role, responsibilities, and tasks that were performed, under the
    direct management, or supervision of the individual. For each
    activity identified please provide the title of the project, agency
    name, point of contact, and contact information.

> The proposal that is submitted in response to this task order should
> include the relevant experience, expertise, and qualifications that
> the Contractor, Subcontractor, and key individuals have related to the
> planning, design, management, operation, and maintenance of HOV
> lanes/systems. The information that is provided for the key technical
> personnel identified in this proposal should include: a brief summary
> of their relevant HOV experiences and qualifications in planning,
> managing, and specifically with developing procedures for performance
> monitoring and evaluation of HOV facilities; identification of current
> and planned work commitments for the length of this task order; level
> of effort (% FTE) for each of these commitments and telephone number
> associated with each commitment; and time available for new work
> commitments.
>
> The Contractor shall provide a nationally recognized expert to serve
> as the Task Order Lead (TOL) to manage, provide technical direction,
> and successfully complete the requirements of this task order. The TOL
> should have the knowledge and a minimum of 15 years of managing HOV
> related projects and studies, traffic management, ITS, and
> transportation management systems. The TOL should also have direct
> experience and a background that involves HOV facilities and traffic
> management. First hand experience in working for public agencies in
> the development of technical references, recommended practices and
> lessons learned, industry standards, agency policies and procedures is
> also desirable.
>
> It is not a requirement that the TOL, or any technical staff
> identified to perform the work identified in this task order, must be
> from the prime contractor on the current indefinite quantities
> contract. It is acceptable for the TOL and key technical staff
> identified in the proposal to be submitted, to consist of only
> individuals from the subcontractors that may be associated with the
> prime contractor on the current indefinite quantities contract. It is
> expected that the TOL identified in the proposal will be directly
> involved with all of the activities of the task order, intimately
> involved developing the required products, and writing of the
> handbook. The TOL is expected to represent a sizable portion of the
> work that is to be completed on this project.
>
> The individuals identified in the proposal that is submitted must be
> available to complete the identified tasks and activities within
> associated time periods that are identified in the task order. This
> portion of the proposal also needs to include a statement that
> indicates the Contractor and subcontractor's commitment that they will
> not switch the TOL or key technical staff identified in the proposal
> for the duration of the task order. Changes in the TOL or technical
> staff on the project at the request of the Contractor or due to
> inability to maintain the established schedule, must be approved by
> the COTM, and require the Contractor to accommodate for the loss in
> productivity due to such a change.
>
> The Contractor's proposal shall contain an estimate of the number of
> hours, rate or loaded rate, and cost for all individuals, grouped by
> the prime and each subcontractor, involved with each task. The total
> estimate of hours and cost should also be provided for each sub-task,
> task, and all of the work to be performed on the contract. The
> proposal should also contain a summary of the total estimate of the
> hours to be completed by sub-task and task for each month of the
> contract.

# 4. Deliverables {#deliverables .unnumbered}

The expected dates for the completion of the milestones and deliverables
identified in this task order are identified in Table 1. These
identified dates are keyed to the date that the official start notice is
issued for the Contractor to begin work on this task order. It is
expected that the Contractor will begin work within ten days of
receiving the start notice to initiate work. Upon initiation of this
start notice the Contractor shall submit a deliverable schedule that
reflects the actual calendar days corresponding to the required delivery
dates.

> All documents (e.g., white papers, draft reports, final reports) that
> will be developed in this report shall be submitted to the U.S. DOT in
> both a hard copies (as a reproducible) and electronic versions using
> Microsoft Word 2000 format and Adobe Acrobat pdf format. The final
> deliverables produced by this task order must also meet the
> requirements and comply with Section 508 of the Americans with
> Disabilities Act. The final electronic versions of the report
> submitted must be in Microsoft Word 2000, HTML, and pdf formats, and
> the appropriate software required by the Government Printing Office to
> print documents.
>
> Table 1. Deliverables Schedule.

+-------------------------------------------------------+--------------+
| *Deliverable*                                         | *Due\**      |
+-------------------------------------------------------+--------------+
| ## Task A. Annot                                      |              |
| ated Outline {#task-a.-annotated-outline .unnumbered} |              |
+-------------------------------------------------------+--------------+
| A.1. Kickoff Meeting                                  | 21 days      |
|                                                       |              |
| > -Initial Draft Project Fact Sheet                   | 21 days      |
| >                                                     |              |
| > -Initial Project Presentation                       | 21 days      |
+-------------------------------------------------------+--------------+
| A.2. List of References and Work Plan                 | 21 days      |
|                                                       |              |
| > -List of References                                 | 21 days      |
| >                                                     |              |
| > -Work Plan (Draft)                                  |              |
+-------------------------------------------------------+--------------+
| A.3. Annotated Outline                                | 60 days      |
|                                                       |              |
| > -Initial Annotated Outline                          | 95 days      |
| >                                                     |              |
| > -Draft Annotated Outline                            | 135 days     |
| >                                                     |              |
| > -Final Annotated Outline                            |              |
+-------------------------------------------------------+--------------+
| Task B. Produce Technical Document                    |              |
+-------------------------------------------------------+--------------+
| B.1. Technical Document Mockups                       | 210 days     |
+-------------------------------------------------------+--------------+
| > B.2. Draft (Initial/Revised)                        | 280/380 days |
+-------------------------------------------------------+--------------+
| B.3. -Final Draft                                     | 465 days     |
+-------------------------------------------------------+--------------+
| > -Final Document for Printing                        | 510 days     |
+-------------------------------------------------------+--------------+
| Task C. Distribution Plan, Outreach Material, and     |              |
| Tri-fold Brochure                                     |              |
+-------------------------------------------------------+--------------+
| C.1. -Project Fact Sheet (Draft/Final)                | 430/490 days |
+-------------------------------------------------------+--------------+
| > -Project Presentation (Draft/Final)                 | 430/490 days |
+-------------------------------------------------------+--------------+
| > -Subject Presentation (Draft/Final)                 | 430/490 days |
+-------------------------------------------------------+--------------+
| C.2. Tri-Fold Brochure (Draft/Final)                  | 430/490 days |
+-------------------------------------------------------+--------------+
| C.3. Primer (Annotated Outline/Draft/Final)           | 375/430/490  |
|                                                       | days         |
+-------------------------------------------------------+--------------+
| C.4. Questions and Answers (Draft/Final)              | 430/490 days |
+-------------------------------------------------------+--------------+
| C.5. Distribution Plan, Letter & Notice (Draft/Final) | 430/490 days |
+-------------------------------------------------------+--------------+
|                                                       |              |
+-------------------------------------------------------+--------------+
| \*Number of calendar days since contract initiation.  |              |
+-------------------------------------------------------+--------------+

> Products that are delivered must follow the publications guidelines
> that are available at <http://www.tfhrc.gov/qkref/qrgmain.htm> unless
> otherwise indicate in this task order. Additional details and
> requirements associated with the format, layout, number of copies to
> submit, obtaining publication numbers, obtaining government forms to
> include in the document, and other factors for the Contractor to
> consider with producing and submitting products will be provided by
> the COTM once the task order has been initiated.
>
> ***Section 508 Rehabilitation Act Compliance:*** \"All electronic and
> information technology deliverables rendered under this task order
> must comply with Section 508 of the Rehabilitation Act and the Access
> Board Standards available for viewing at
> [http://www.section508.gov.]{.underline} Unless otherwise indicated,
> the Contractor represents by signature of this contract that all
> deliverables comply with the Access Board Standards.\"

#### *Web Posting:* Web site publishing is FHWA's principal means of publishing reports. All of the products to be developed and ultimately distributed in this task order shall be created in both HTML and Microsoft Word. PDF documents created with the newest version of Adobe Acrobat can be substantially Section 508 compliant, if the documents are created and formatted to be 508-compliant. Visit [**http://access.adobe.com/acrobatmain.html**](http://access.adobe.com/acrobatmain.html) to learn more about the Adobe Acrobat accessibility features. {#web-posting-web-site-publishing-is-fhwas-principal-means-of-publishing-reports.-all-of-the-products-to-be-developed-and-ultimately-distributed-in-this-task-order-shall-be-created-in-both-html-and-microsoft-word.-pdf-documents-created-with-the-newest-version-of-adobe-acrobat-can-be-substantially-section-508-compliant-if-the-documents-are-created-and-formatted-to-be-508-compliant.-visit-httpaccess.adobe.comacrobatmain.html-to-learn-more-about-the-adobe-acrobat-accessibility-features. .unnumbered}

If the document is draft in Word, it will need to be converted to HTML
for viewing on the Internet. Conversion complications arise in documents
with double-column pages, complex tables, and multiple graphics. HTML
ready format of the Microsoft Word document should only contain free
flowing text. If graphics are added to a document, then a brief
description of those images should accompany the document. All images,
charts, and graphs must have a description to be Section 508 compliant.

***Documents for Printing:*** Documents developed for this task order
shall be prepared in electronic GPO-required format for printing. The
following programs are used to create a majority of the print publishing
work received by GPO:

-   Page layout: QuarkXPress, Adobe PageMaker, Adobe FrameMaker, Adobe
    In-Design, Corel Ventura, and Microsoft Publisher 2000.

-   Drawings/Illustrations: Adobe Illustrator, Macromedia FreeHand, and
    Corel Draw.

-   Image Manipulation: Adobe Photoshop and Corel PhotoPaint.

These are also the preferred programs of the commercial printing
industry. The most recent versions of these software programs should be
used. Avoid using any software that is more than one major revision old,
due in part to most vendors' only support recent or near recent
applications. The Contractor should check the software vendors' web site
for current versions and upgrade patches.

Files created using these software programs outputs have fewer problems
than files created in programs not designed for print publishing. Other
programs may be used, but unless they support prepress functions (e.g.,
PANTONE colors. Trapping, bleeds, crop marks and color separation)
problems will likely occur. Contractor who uses programs other than
those listed below should consider supplying high-resolution PDF files
instead of native files. For more information on creating appropriate
PDF files reference The GPO E-Pub's web site at:
<http://www.gpo.gov/procurement/ditsg>.

# 5. Reporting Requirements {#reporting-requirements .unnumbered}

The HOV Pooled Fund Study members have considerable interest in the
progress of this study, which they are funding. Therefore, the TOL shall
be available for a one-hour teleconference and briefing that may be
arranged by the COTM on a monthly basis. At this briefing the
Contractors COTM shall be prepared to discuss technical progress,
problems, and products. In addition, the Contractor's TOL shall attend
the HOV Pooled Fund Committee Annual Meeting will be held in the winter
of 2003 or 2004 (spring or summer) and report on the findings of the
study.

The Contractor's TOL shall also participate in a national
videoconference and/or webcast to present the findings and
recommendations identified in this document. The COTM will make all of
the arrangements, perform the necessary outreach, and facilitate this
videoconference or webcast. The final project and/or subject
presentation for this document will provide the basis for the
Contractor's presentation. This videoconference or webcast will occur
after the final document has been submitted and approved by the COTM.

# 6. HOV Performance Monitoring, Evaluation and Reporting: Key Technical Topics and Supporting Issues to be Addressed in the Handbook {#hov-performance-monitoring-evaluation-and-reporting-key-technical-topics-and-supporting-issues-to-be-addressed-in-the-handbook .unnumbered}

The following is an initial list of issues and topics that have been
identified to be addressed in the technical document developed for this
project:

1.  *Introduction*

```{=html}
<!-- -->
```
A.  Identify purpose, goals, and vision of the document;

B.  Identify intended audience of the document (primary and secondary);

C.  Provide a high-level discussion of the importance, benefits, and
    challenges that agencies face with operating, managing, and
    maintaining HOV facilities. Also address the importance of planning,
    designing, managing and maintaining a system and how changes
    throughout its life cycle impact performance, reliability and cost;

D.  Define and provide a brief overview of the role and value of
    performance monitoring, evaluation and reporting to HOV facilities
    and stakeholders, and how performance monitoring, evaluation and
    reporting could be used throughout the life cycle of HOV facilities;

E.  Provide the context of performance monitoring, evaluation and
    reporting for HOV facilities and how it may related to freeway
    management programs, traffic operations programs, transportation
    corridor application, and planning at agency, metropolitan area, and
    regional levels;

F.  Briefly describe the current state-of-the-practice, trends, and gaps
    with agencies developing and using performance measures for HOV
    systems. Indicate also other national initiatives and technical
    documents that have been developed or initiated that agencies can
    use to support in activities involve performance monitoring,
    evaluation and reporting for HOV facilities. Identify what has or
    hasn't been done related to providing guidance and recommended
    practices for HOV performance monitoring, evaluation and reporting;

G.  Describe how this document will meet the needs of agencies, can be
    used by practitioners, and expected influence it would have on the
    practice;

H.  Provide an overview and description of how the document was
    developed;

I.  Describe how key typical users (different groups of intended
    audience) may consider using this document based on their varying
    levels of experience and expertise; and

J.  Describe the organization of the document. Identify and provide
    brief overview of each chapter and key topics covered.

```{=html}
<!-- -->
```
2.  *The initial section of each chapter following the initial first
    chapter should address or present similar information. This
    introductory section should address or cover:*

```{=html}
<!-- -->
```
A.  The purpose and objective of the chapter;

B.  The key issues and context of material to be presented related to
    the overall subject matter of the entire document and this specific
    chapter;

C.  How does this particular chapter relate to and build off the
    previous chapter;

D.  How information contained in this chapter will help the reader to
    progress and build toward other subjects in subsequent chapters in
    the document; and

E.  The titles of remaining sections in this chapter.

```{=html}
<!-- -->
```
3.  *HOV Lane Monitoring, Evaluation and Reporting: Overview*

```{=html}
<!-- -->
```
A.  Provide a high-level overview of performance monitoring, evaluation
    and reporting, how it relates to HOV facilities. This chapter will
    provide an option to the reader with limited or no experience with
    the subject of this document to read one chapter to get a very
    high-level overview of the topics allowing them to use the rest of
    the document. This chapter should provide the reader with a basic
    understanding of the key topics to be covered in the document, why
    and how they apply and influence HOV systems; and

B.  Address additional issues and in greater depth than was appropriate
    in only several pages in the Introduction chapter. The information
    will allow the reader to understand these concepts and issues as
    they relate to the application of this subject matter, and decide
    what additional chapters to read and sequence, based on their
    individual experience and expertise, job responsibilities, or
    activities.

> C. Highlight successful practices and programs that reinforce
> recommended guidance and best practices identified in this section.

*4. HOV System Performance and Agency Strategic Plans and Goals*

> A. Review appendix B of NCHRP Report 446 to assist with identifying
> how HOV system performance may influence typical goals and measures of
> public agencies, service providers, and other stakeholders.
>
> B. Identify typical goals and measures within various strategic plans
> within a region. This should include at a minimum: transit, MPO plans,
> state DOTs, enforcement, traffic management, other key public agencies
> in a region. Identify and discuss the processes, opportunities, and
> techniques for integrating the consideration and influence of HOV
> systems goals, measures, and be integrated into these plans and
> processes.
>
> C. Identify and discuss techniques and strategies for reporting on the
> influence of HOV systems and various components on various strategic
> goals, measures, agency or service provide operations.
>
> D. Identify and describe continuous process improvement process
> framework around which HOV system performance monitoring, evaluation
> and reporting should fit within a region, key public agencies,
> regional processes and/or programs, and day-to-day operations and
> provision of services.
>
> E. Identify, discuss, state importance, and provide examples of how
> the HOV system, program, and multi-year plan around which HOV
> performance monitoring, evaluation and reporting should fit within an
> agency or region.
>
> F. Highlight successful practices and programs that reinforce
> recommended guidance and best practices identified in this section.

*5. Use of HOV System Performance Measures*

> A. Identify stakeholders who are possible users of data, concerned
> with, or impacted by the performance of an HOV system. Also include an
> assessment of their requirements, use, data needs, and other related
> factors that may influence their need for data being collected,
> processed, evaluated or reports on performance.
>
> B. Identify various programs, projects, decision-making processes, and
> various support services where subject data is used in making
> decisions or allocating resources.
>
> C. Identify and provide appropriate supporting material in the form of
> a matrix or chart identifying the various stakeholders, data needs,
> requirements, and other issues agencies should be aware of related to
> HOV system data or performance reports.
>
> D. Indicate and discuss how these requirements and needs may influence
> the planning and focus of HOV system monitoring, evaluation and
> reporting. Also indicate how this would influence the vision, mission,
> goals, objectives, concept of operations, services provided, program
> components and resources required.
>
> E. Develop goals and objectives for HOV system performance

-   Ensure key goals are consistent across regions

-   Allow for flexibility, as different regions may have different needs
    and purposes for their respective HOV systems

F.  Align performance measures with goals and objectives

-   Develop performance measures that report progress towards meeting
    objectives

```{=html}
<!-- -->
```
-   Examine typical goals and objectives for HOV systems

-   Identify appropriate performance measures applicable to the goals
    and objectives.

-   Note validity of measures appropriate at the corridor or regional
    level of evaluation

-   Examine goals and objectives appropriate to existing projects and
    future extensions or improvements to the HOV systems

> G. Highlight successful practices and programs that reinforce
> recommended guidance and best practices identified in this section.
>
> *6. Performance Measures and Data Requirements*
>
> A. The intent of this chapter is to present the recommended measures
> based on the users of performance measures and data for HOV facilities
> identified in previous chapters. This chapter will also address the
> requirements, issues to consider, and other factors associated with
> the data to support HOV system performance measures.
>
> B. Develop a matrix of typical or recommended performance measures for
> HOV systems. Included range of facility types (e.g., freeway,
> expressway, highway, surface street), users (e.g., general public,
> commuters, transit), and other factors.
>
> C. Describe role, need for, importance, provide justification,
> resources required, support services needed, and other key issues
> related to data collection function.
>
> D. Identify typical range of requirements and key issues to consider
> for data to support various users, uses and their needs identified in
> previous chapters.
>
> E. Identify, describe, present issues to consider, and other
> influencing factors associated with the approaches to collecting,
> processing, storing, archiving, and other related issues.
>
> F. Identify range of issue to consider, how to address, describe
> potential impacts on performance monitoring system and other factors.
> Issues should include: reliability, quality, variability, level of
> aggregation, quality, control techniques, processing, techniques,
> processing techniques, formatting, storage, and archiving.
>
> G. Discuss how various congestion causing events may influence data
> requirements, collection and other related factors.
>
> H. Address measures of performance for support services for an HOV
> system and program.
>
> I. Discuss how area of coverage and other data collection techniques
> are influenced by data needs, requirements, cost, and influence area
> of coverage will have on ability to perform monitoring, evaluation and
> reporting of performance.
>
> J. Highlight successful practices and programs that reinforce
> recommended guidance and best practices identified in this section.

*7. Performance Monitoring*

> A. Identify recommended practices with reporting on HOV system
> performance. Identify how reporting may vary based on various
> stakeholders. Indicate what techniques, formats, data, frequency, and
> other factors are used to get information out to these groups based on
> their needs and/or desires.
>
> B. Highlight successful practices and programs that reinforce
> recommended guidance and best practices identified in this section.
>
> C. This short list does not represent all of the issues, indicate
> level of detail, or amount of information that will be required for
> this section. Significant information will need to be summarized,
> context provided, and referring reader to other resources for
> additional information. Some of these resources could include traffic
> management, monitoring, and evaluation report and documents that
> NCHRP, FTA, and FHWA have already produced.

# 8. Data Collection and Management {#data-collection-and-management .unnumbered}

A.  Identify and develop best practices for HOV data collection

-   Issues currently confronted include the following

```{=html}
<!-- -->
```
-   Available resources and experience

-   Site selection and surveying techniques

-   Optional data retrieval systems

-   Data management and warehousing

-   Data management planning

```{=html}
<!-- -->
```
-   Include lessons learned from recent data collection efforts in case
    study locations where HOV system monitoring has been in place for a
    number of years

-   Develop best practice techniques that address a means for
    information management and dissemination, including prototypical
    systems for data storage, analysis, and reporting of performance
    measures such as traffic volume, occupancy, travel times, and
    violation rates

-   Examine ways to make data more user friendly through the use of GIS
    maps and charts, as well as other formats appropriate for on-line
    publication

B.  Determine an overarching framework for data management activities

-   Define functional ways of collecting, analyzing and compiling data
    for each key measure responding to project goals and objectives

-   Identify various means of reporting outputs to various stakeholders

C.  Justify the data collection process by promoting an understanding of
    the data collection function by identifying potential HOV
    performance monitoring applications for collected data, with regard
    to the following:

-   Mobility

-   Accessibility

-   Air quality

-   Fuel consumption

-   Safety

-   Cost effectiveness

D.  Evaluate types and methods of HOV data collection, including new
    technologies for measuring occupancies, travel speeds, and commute
    times

E.  Recommend data collection, refinement, dissemination and archiving
    practices for the purposes of performance monitoring and evaluation

F.  Explain techniques for how data will be possessed and the functional
    requirements associated with a data management plan that can be
    automated to meet day to day needs

G.  Examine the necessary resources to support ongoing reporting for
    performance monitoring, marketing, education, planning and design,
    and project accounting:

-   Reporting will examine the overall roles of agencies and staff,
    including budget, staff, traffic management interface, and in-kind
    agency contributions

-   Recommend strategies for reporting data in a public friendly format
    to meet the needs of stakeholders that include environmental,
    traffic, transit and public policy interests

> H. Describe the range, types, issues, sources of existing data
> collected from other interests, ability to access and use existing
> data, and influencing factors associated with methods to access,
> collect, process, store, archive, and make information available to
> others.
>
> I. Discuss database and data management strategies, techniques, plans,
> issues to consider, and other influencing factors.
>
> J. Discuss the importance, need for, and components of a data
> management plan, need for, and components of data management plan,
> relationship to an HOV system or program plan, and strategies to
> automate to collection, processing, and archiving of data.
>
> K. Highlight successful practices and programs that reinforce
> recommended guidance and best practices identified in this section.

# 9. Performance Evaluation Methodologies and Techniques {#performance-evaluation-methodologies-and-techniques .unnumbered}

A.  Identify recommended methodologies and processes to evaluate the
    performance of HOV systems to evaluate the performance of an HOV
    systems, facilities within a corridor, a specific facility, transit
    services, specific user groups, HOV system program components, or
    various support services.

B.  Include the analysis performed, tools utilized, stakeholders to
    include, where decisions are made in process, data required, format,
    and other considerations.

C.  Identify the importance, describe the need for, identify components,
    detail, and other issues to consider associated with an evaluation
    plan. Identify and discuss how the evaluation plan may vary for
    evaluating an HOV systems, facilities within a corridor, a specific
    facility, transit services, specific user groups, HOV system program
    components, or various support services. Identify and discuss how an
    evaluation plan may vary for a system, corridor, facility, or other
    related applications.

D.  Identify and discuss various evaluation techniques that considers at
    a minimum:

-   Determine appropriateness of specific techniques for addressing
    performance measures

```{=html}
<!-- -->
```
-   Describe trade-offs in techniques

-   Evaluate the ease of use of each technique

-   Describe the anticipated accuracy and estimate cost of each
    technique

```{=html}
<!-- -->
```
-   Develop a prototype evaluation plan at the project, corridor, and
    system levels

```{=html}
<!-- -->
```
-   Annual system-wide assessment

-   Basic evaluation techniques for isolated projects

-   Ensure prototype evaluation plan is linked to the previously
    described goals and objectives

-   Develop evaluation techniques specific to each mode that utilizes
    the HOV system, i.e. bus transit, vanpools, motorcycles, ILEVs, and
    mixed use express traffic in HOT lanes

-   Use case studies from current HOV evaluation projects to develop
    best practice experience

> E. Highlight successful practices and programs that reinforce
> recommended guidance and best practices identified in this section.

*10. Evaluating HOV System Performance*

> A. Identify the importance, challenges, issues, process, techniques,
> and other factors to consider associated with establishing a baseline
> of performance for an HOV system, facilities within a corridor, a
> specific facility, transit services, specific user groups, HOV system
> program components (e.g., public outreach/awareness), or various
> support services (e.g., enforcement, traffic management, traffic
> incident management).
>
> B. Address how various types of congestion causing events will
> influence performance, baseline of performance, and probability and
> impact may be on travel and HOV system.
>
> C. Identify and discuss methods, processes, techniques, users, uses
> and need, and other issues associated "near" real-time evaluation of
> performance. Also identify same issues for "off-line" more systematic
> evaluation of performance with longer time horizons.
>
> D. Identify, discuss, and represent issues associated with traffic
> managements need for evaluating and reporting on performance and how
> this impacts evaluation plans, systems established, resources and
> other needs.
>
> E. Highlight successful practices and programs that reinforce
> recommended guidance and best practices identified in this section.

*11. Performance Reporting*

> A. Identify recommended practices related to reporting on HOV system
> performance. Identify how the reporting may vary based on various
> stakeholders. Indicate what techniques, formats, data, frequency, and
> other factors are used to get information out to these groups based on
> their needs and/or desires.
>
> B. Describe and discuss issues associated with real-time users of data
> and how it impacts the reporting on performance.
>
> C. Identify and discuss all of the issues associated with planning,
> developing, and sustaining real-time and systematic reporting of data.
>
> D. Describe issues to consider and impacts on resources, reliability,
> types of information, and other issues associated with providing
> public real-time HOV system performance data.
>
> E. Examine different stakeholders and functional activities, i.e.
> planning, design, operation, and enforcement that need performance
> monitoring output
>
> F. Develop example reporting output and develop example reporting
> guidelines and formats to meet the needs of each stakeholder group
>
> G. Ensure the reporting needs of stakeholder groups are linked to
> previously established goals and objectives
>
> H. Provide case studies of typical reports, methods for comparing
> information, typical queries reporting should address, and lessons
> learned
>
> I. Highlight successful practices and programs that reinforce
> recommended guidance and best practices identified in this section.

*12. HOV System Performance Measurement*

> A. Identify the purpose, need and importance for an HOV system
> performance measurements system. Identify, describe, and discuss
> recommended components of system, functions, process, decisions that
> are made, support services and required resources.
>
> B. Identify potential components, policies, procedures, support
> services, technologies, agency and staff capabilities, agency
> commitments and funding needs, and other key issues to support the
> continuous performance monitoring, evaluation and reporting on HOV
> systems and support services.
>
> C. Examine the most commonly applied goals and objectives and define a
> limited level program that can offer comparable data collection,
> evaluation and reporting on key parameters found among HOV systems
> that are performing monitoring today.
>
> D. Highlight successful practices and programs that reinforce
> recommended guidance and best practices identified in this section.
>
> *13.* *Case Study Chapters (4-5)*

A. Each of the remaining chapters (4-5) of this technical document will
highlight a successful practice as an example that reinforces key
recommendations and practices identified in the previous chapters. The
intent of these chapters are to provide examples or case studies that
build off of and demonstrate how the concepts, techniques, and guidance
that are identified in the earlier chapters of this document can be
applied within an agency or program associated with an HOV system
performance monitoring, evaluation, and reporting system of program. If
actual case studies do not exist related to these, or other topics that
the Contractor and COTM identify, practices related to specific topics
or issues from individual agencies should be combined and presented as
one example or case study.

B. For each of the examples of case studies that are presented, detailed
information will be prepared to identify the breadth and depth of the
issues that should be considered associated with a particular
application. Where possible this information should be presented in the
form of lists, flow charts, graphs, diagrams, and other formats to
easily depict the key issues to be considered.

> C. Sample chapters highlighting similar examples or case studies can
> be obtained from the TMC PFS web page for the "Traffic Management for
> Planned Special Events" handbook located at:
> <http://tmcpfs.ops.fhwa.dot.gov/cfprojects/new_detail.cfm?id=32&new=0>.
>
> D. Possible topics for these chapters may include: 1) regional HOV
> system performance monitoring, evaluation, reporting; 2) HOV facility
> within a corridor; 3) HOV facility; and 4) HOV performance monitoring,
> evaluation and reporting system and/or program.

*14. Appendix.* The Contractor shall utilize appendices as needed to
present additional details, information, and examples that are not
appropriate for each chapter. The appendix shall contain a glossary of
terms to eliminate redundancy and misinterpretation on topics and terms
that are used throughout the document.