The Project Evaluation Toolkit

A Toolkit for Anticipating and Evaluating Transportation Project Impacts. 

PET Home

User's Guide

Toolkit Files

Papers & Slideshow


Contact Us



 Toolkit Files

 Project Evaluation Toolkit (PET) files for download are available as follows:

 PET 2.0 [No Network pre-loaded] (Excel, VB macros enabled)

 PET 2.0 for Austin [Austin Network pre-loaded] (Excel, VB macros enabled)

 PET 2.0 for DFW [Dallas-Ft Worth Network pre-loaded] (Excel, VB macros enabled)

 PET 2.0 for Houston [Houston Network pre-loaded] (Excel, VB macros enabled)

 Network Images [Austin, DFW, & Houston Networks mapped in PowerPoint slides)

 Trip Table Estimator File (compiled executable)

 Trip Table Estimator File (C++ source code)

 Network Flow Estimator (compiled executable)

 Network Flow Estimator (C++ source code)

 Toolkit Upload File (MS Excel, VB macros enabled)

 Budget Allocation Module (MS Excel)

Multi-Objective Decision-Making Module (MS Excel)

If you wish to conduct sensitivity testing you must also create two folders in the same directory as the Main Toolkit File named "STInputs" and "STOutputs".

Also note that analysts do not need to attempt to use all PET components simultaneously. The Main Toolkit File may be used in conjunction with the Trip Table Estimator and the Network Flow Estimator for most projects. The Toolkit Upload File can help users wishing to specify a new network to be uploaded to the Main Toolkit File. The Operational Strategies Toolkit Component may be used in conjunction with the Main Toolkit File once a base network is specified in the Main Toolkit File. Finally, the Budget Allocation Module may be used as a stand-alone tool or may be used to further assess budgeting after running PET for a number of potential project. For more information about the various toolkit components, please see the descriptions below.

Main Toolkit File

The Main Toolkit file contains a user-entered transportation network consisting of a series of nodes (intersections) and directional links (road segments). Additional information is required, such as traffic link volumes, roadway capacity, tolls, etc., though many inputs are optional and may be used for more detailed analysis. The user then enters into the Main Toolkit File the ways in which the transportation network will change then runs the Travel Demand Model (composed of the Trip Table Estimator and Network Flow Estimator). The Main Toolkit File will read in the Travel Demand Model's outputs and report how travel patterns and traffic impacts change in the base case and alternative scenarios.

Trip Table Estimator

Once the analyst has specified the transportation network, alternative network(s), current traffic volumes and parameters in the Main Toolkit File, the analyst may run the Trip Table Estimator. This component estimates current traffic flows between all origins and destinations for each time of day. It should be noted that every node is a potential origin and potential destination for all other nodes.

For more information, see Section 9.0 of the Toolkit Documentation/User's Guide.

Network Flow Estimator

After trip tables have been established, the Network Flow Estimator may be run from the Main Toolkit File. This will assign traffic volumes by link, time of day, user class, and mode for a given scenario (base-case, alternative 1, 2 or 3) and year (initial or design). Total scenario traveler welfare estimates are also generated using the Network Flow Estimator. The Network Flow Estimator is typically run multiple times to estimate traffic impacts in each scenario for both the initial and design years.

For more information, see Section 9.0 of the Toolkit Documentation/User's Guide.

Toolkit Upload File

There are two ways to enter data into PET, through the Main Toolkit File or through the Toolkit Upload File. Entering data into PET through the Main Toolkit File may be conducted by entering network, parameter, or other input information. This works fine for small edits and developing new scenarios, but can be laborious if a significant amount of input data is required (for example, developing a new network from scratch). The Main Toolkit File contains numerous formulas and there is a small processing delay each time a new value is entered.

In order to address this issue and provide a convenient location for all inputs, the analyst may opt to use the Toolkit Upload File. This file contains data entry locations for the vast majority of inputs, which may then be quickly uploaded to the Main Toolkit File once all inputs have been entered.

For more information, see Section 2.3 of the Toolkit Documentation/User's Guide.

Budget Allocation Module

Most components of the Project Evaluation Toolkit are designed as an alternative analysis tool which may be used to identify desirable project scenario alternatives. The budget allocation module may be used to identify a preferred mix of potential projects in order to achieve the maximum benefits. Analysts may specify budget limits and equity considerations, such as ensuring that various regions have minimum expenditure levels. Moreover, the budget allocation module requires the analyst to specify a pre-determined level of required investment for every candidate project, under the assumption that one project's costs will not impact another project's cost. In this regard, the budget allocation decision making process will choose mix of projects that will deliver the maximum benefits, within the limits of budget and other constraints.

For more information, see Section 12.0 of the Toolkit Documentation file/User's Guide.

Multi-Criteria/Multi-Objective Decision-Making Module

PET's multi-objective decision-making tool (MODMT) enables engineers, planners and others to select one or more optimal projects or scenarios from among competing alternatives, subject to multiple criteria that are not all monetized or otherwise directly comparable. The MODMT uses Data Envelopment Analysis and thus "efficiency" values to rank different scenarios. Scenarios whose efficiency is less than one are clearly dominated by other scenarios, and are not recommended. Scenarios with an efficiency greater than or equal to one are potentially optimal candidates, depending on one's relative valuation of the different criteria. The magnitude of the efficiency value reflects the degree to which these scenarios are dominated (or not) by the others. This method is not sensitive to units used for each criterion (e.g., fatalities versus minutes saved versus toll revenues versus tons of fine particular matter).

For more information, see Section 13.0 of the Toolkit Documentation file/User's Guide.


Visit Dr. Kockelman's Homepage

Last Updated: 1.17.14