VISUM Add-on modules

Using the Calendar module, you can show and edit a weekly or an annual timetable in a VISUM version file. Thereby the service days are shown that define whether a certain PuT line will be operated or not. It is also possible to show a specific service on weekdays, for example, or to define special regulations for holidays. Additionally, when importing data from timetable and service programs, you can transfer complete timetables.

The Calendar module basically provides two options for service day modelling:

• Weekly calendar:
  The network model allows you to describe the travel demand and public transport services for each day of the week (Mon - Sun). You can determine the weekday schedule for each PuT line. Additionally, you can enter a projection factor (e.g. for projection to annual values) for each day.

• Annual timetable:
  In the network model, you are able to specify a period (e.g. operates "daily" or "Sat. 5/18/10") for the service days.

You only need the Calendar module for PrT, if you want to calculate and analyse dynamic assignments for a period of several days.

The Junction editor allows you to model all junction details in a single view, from the node and turn attributes to the complete junction.

There are different views available showing the different aspects of the junction:

• Nodes: shows the basic node attributes and the major flow
• Links: shows the attributes of all approach links of a node, e.g. the number of lanes or their geographic orientation
• Turns: shows the macroscopic attributes of all turns
• Geometry: the node model for node geometry, including lanes and lane turns
• Signal times: shows the signal times for signal group-based and stage-based signal controls

The Nodes, Links and Turns views are standard views in VISUM and replace the former dialogues "Edit node" and "Edit turn". The Geometry and Signal times views are only available with the Junction editor add-on.

The VISSIM interface module allows PTV Vision to combine macroscopic analyses in VISUM with microscopic traffic simulation in VISSIM.

An abstract network model (ANM) is created from a VISUM network and can then be imported into and edited in VISSIM.

For more convenient and detailed node editing with the VISSIM interface, we recommend that you use the Junction editor (module).

TFlowFuzzy is deployed to correct PuT and PrT trip matrices using current count data and reference values.

The new matrix data is calculated with the aid of an iterative method that is based on routes computed from individual OD pairs.

This can be useful in the following cases:

• A demand matrix based on empirical survey data is outdated and you want to update it without having to conduct a new (origin-destination) survey. The update shall be based on census data only.
• You want to calibrate a matrix generated from the transport network model using count volume data.
• You want to improve a matrix generated from incomplete or unreliable data using current and more complete/reliable count volume data.
• A survey contains the journey distance distribution, but the model does not reflect the data at the level of accuracy required.

TFlowFuzzy will solve this problem for PuT as well as for PrT. The update only affects the demand matrix and always refers to total volumes.

You can use the following count and survey data or combine them if you want to:

• Link volumes
• Origin/destination travel demand per zone
• Volumes of turns at nodes or main turns at main nodes (as long as they are defined)
• Volume screenlines
• PuT passenger trips
• Boarding/alighting passengers at stop areas
• Skim data distribution, e.g. journey distance distribution

The calculation result is an updated demand matrix.

EWS calculation allows you to perform cost-benefit analyses for investments in road construction based on EWS-97.

The EWS-97 (recommendations on economic efficiency analyses of roads) were established by the working committee "Economic efficiency" of the FGSV (German Road and Transportation Research Association).

These recommendations form the basis for an economic assessment of investments in road construction carried out according to uniform standards. The results from economic efficiency analyses support decision-making regarding the measures to be taken. Furthermore, the decisions made shall be as objective and transparent as possible.

Economic efficiency analyses according to EWS-97 are based on the costs and benefits of a road construction measure (planned case) compared to the costs saved, if it is not implemented (comparison case).

The EWS add-on module integrates EWS 1997 as seamlessly as possible into the VISUM environment. Minor corrections of the EWS guidelines have been discussed and agreed with the responsible member of the FGSV working committee.

The volumes required for EWS can either be entered as count data or calculated through assignment. This allows the use of "real" count data and the simulation of various variants based on the assignment methods integrated into VISUM. The speed data required for the analyses is calculated according to EWS-97 (tables 11-13).

The TRIBUT module contains a special PrT assignment method that accounts for road toll.

"Conventional" approaches use a constant value of time to calculate road toll. Basically costs (toll fees) are then converted into time and standard mono-criteria assignment methods can be directly applied.

Unlike the conventional approach, TRIBUT applies a random time value. Therefore, TRIBUT calculates the route search and choice based on two separate sets of criteria: time and costs (bi-criteria).

During the last few years, this method has been applied to evaluate privately funded toll motorways in France. In contrast to the conventional approach, it is characterised by a more realistic price elasticity concerning the use of toll roads.

The Graphical timetable editor complements the tabular one since its display options provide an optimum overview of the current planning status and trip-related information:

• Display and editing of all or selected timetable trips in time-distance or distance-time diagrams
• Display of one or several lines, selection of stops for display, control of order of stops
• Trip-differentiated display according to certain attributes (e.g. day, line, vehicle type, operator, etc.)
• Intelligent combination of tabular and graphical display for selection, insertion, editing and deleting of trips
• Visualisation of additional service trip details, e.g. number of passengers per route section per trip (based on assignments), automatic passenger count results or the deviations between actual and scheduled departure times.
• In the time-distance diagram you can also show the assignment of individual trips to blocks
• The blocks can be displayed in bar diagrams (Gantt diagrams) for interactive editing

This module enables you to analyse the efficiency and cost recovery level of a PuT system, its service units and service lines. The results can be separated by operators and service areas.

The costs are calculated based on vehicle deployment, the use of stops and routes as well as on general, operator-specific attributes and the respective rates.

• Driver/vehicle units: rates for operating distance and time as well as depreciation charges per vehicle unit or train type
• Stops, routes: use-dependent rates and cost types
• Operators: rates and cost types that cover the general infrastructure, e.g. for depots and overhead costs

Revenues are estimated based on passenger distribution (calculated with the aid of the assignment function) and on simple revenue ratios or a specified tariff model.

Estimation of the number of required vehicles forms the major basis of cost calculation. This module provides the basic automatic line blocking function based on a selected timetable and user-defined rules, as for example:

• Depots and their capacities are explicitly accounted for
• Interlining trips are determined based on the network
• Trip-specific preparation and completion times as well as block-specific tasks (e.g. fuelling, cleaning and vehicle preparation) are considered
• Rules for selecting and combining trips

Note:

By combining the LLE and Calendar modules you can perform a more efficient profitability analysis, whilst accounting for several valid days and service days.

The Detailed line blocking module extends the basic line blocking functionality provided by the LEE module.

• Vehicle deployment can be further optimised by accounting for a number of vehicle combinations.
• Forced chainings can be modelled as previous or successive relations.
• Secondary criteria can be used for a systematic selection among equally good solutions.

Instead of one specific vehicle type, you can assign a number of possible vehicle types to a trip. During the optimisation procedure the vehicle type is chosen that allows for a minimum deployment of vehicles. For vehicle selection, the software can also take passenger volumes calculated during assignment or based on survey data as well as the vehicle's capacity into account in order to ensure demand-optimised vehicle deployment.

The optimization procedure might result in several equally good solutions in terms of the total costs. By applying several additional criteria, e.g. block duration, number of different vehicle types per line or number of lines per block, you can find a solution that meets additional requirements. In addition, you can have operation constraints taken into account, as e.g. deployment of a fixed vehicle type for a certain trip.

Note:

The modules Graphical timetable editor and LLE are required for line blocking and represent the basis for use of the Detailed line blocking module.

Normally passenger surveys do not include the passengers' complete trip within the PuT network. This is especially true for passengers who transfer several times or who walk from one stop to another to transfer. In general, passengers are counted when they board the vehicle on the so-called survey line and are asked about the following details of their trip:

• Boarding stop on the survey line (the line on which they are interviewed)
• Alighting stop on the survey line,
• Initial boarding stop of the trip,
• Final stop of the trip and
• other trip details (e.g. type of ticket, purpose of the journey)

The PuT passenger survey module is used to check and complement trip-based passenger information. Checking and completing the survey data is primarily based on computer-aided modelling of the survey-relevant PuT supply and on parameters for reconstructing incomplete or correcting wrong trip data.

From route information (that might have to undergo several plausibility checks) and by means of so-called direct assignment, a VISUM version file is created. It allows you to perform all common procedures, e.g. route evaluation according to the number of traversed zones, the generation of demand matrices and visualisation of passenger volumes per links, stops, and lines.