Transit input files are stored in the SERPM8\Inputs\Transit folder. Files with a scenario key are specified in the Cube Scenario Manager.

The following table shows the key transit input files. Attributes of the network definitions (transit lines) are described in more detail below.

Transit Network Details

Mode and Operator Codes

The selected transit mode and operator codes has implications for:

• [mode code] the availability of the transit service in mode choice alternatives (with-local or no-local).
• [mode code] the application of travel time discounts and other time bonuses that represent the unobserved reliability, enhanced station amenities, and higher quality ride of "premium" modes.
• [operator code] the fare system utilized
• [mode and operator code] how the transit assignment results are summarized.

The next two tables summarize the mode numbers and operator numbers.

Transit Line Definitions

Each transit line has required (first table) and optional (second table) attributes. These attributes are set in the Transit Line File.

Transit Dwell Time Determination

SERPM 8 includes a process that updates the dwell time defined in each transit line file according to the time-period (AM, OP, PM) specific dwell times defined in the TSPEED.DBF file. The dwell times are indexed by the USERA4 attribute, which is set to the same as the OPERATOR value.

Both the DWELL_C and USERA4 attributes must be set for the update process to function. They need not be on the same line, but the following convention must be followed:

• DWELL_C defined after USERA4 is specified
• DWELL_C should be defined following the first node definition (e.g. N=11111, DWELL_C=0.5, N=11112,...)
• DWELL_C defined only once per line

If USERA4 and/or DWELL_C are not defined, the transit line will operate without a dwell time delay by stop. This may be appropriate if transit speeds are defined on the highway link (representing a dedicated right-of-way) that factor in dwell time.