There are multiple methods for coding, reviewing, and evaluating MOEs) or performance measures in a microsimulation model. The guidance outlined in this section is based on best practices and covers the most common performance measures for reporting existing and future conditions. For detailed explanations on the use of MOEs, see

Chapter 4

of this manual. While there could be general principles that apply to reporting results and MOEs for microsimulation, this section outlines the reporting results specific to Vissim. For

examples

of reporting MOEs, see

Chapter 17

of this manual.

One of the main purposes for conducting an alternatives analysis is to test future build conditions that cannot be tested in the field. For this reason, it is important to extract speeds, throughputs, travel times, and other data outputs from various models, including Vissim, in the same way they are collected in the field. Animations of Vissim model runs are often used to supplement tabular presentation of results. For information on recording animations (including visualization, camera positions, and 3D elements), refer to the Vissim user guide.

When reporting results and MOE’s, it is important to distinguish between segment wide results and network level results. Networkwide MOEs such as network delay are used to determine the impacts of a model change to the overall network, while segment wide MOEs such as travel time are used to determine the impacts of a model change to a segment.