-
Notifications
You must be signed in to change notification settings - Fork 5
Costs
The various costs input into the model are summarized in below. All costs are for year 2010; model users can use a CPI adjustment for translating costs from other years to 2010 values for consistency.
Cost (Year 2010) | File | Current Settings |
---|---|---|
Value-of-time for assignment | Assignment and skimming procedure file + General Procedure Settings + PrT Settings + Impedance + Impedance function by demand segment | 25 dollars per hour 144 seconds per dollar = 3600 / 25 |
Transit fare matrix | VISUM Python script SOABM.py createTapFareMatrix() | 100, 200 cents (GP, RV) |
Parking costs | VISUM master version file SOABM.ver MAZ attributes HPARKCOST, DPARKCOST, MPARKCOST | 0 dollars |
Link toll | VISUM master version file SOABM.ver link attributes Toll_PrTSys(Dseg) | 0 dollars |
Auto operating cost | Orramp.properties file for reference in the OR-RAMP UECs | aoc.fuel =13.5 aoc.maintenance =6.3 |
Value of Time for Tour/Trip Making | Orramp.properties file for reference in the OR-RAMP UECs | Mean Values of Time: 0-30k = $6.01/hr; 30-60k = $8.81/hr, 60-100k = $10.44/hr, >100k = $12.86/hr |
For future year scenarios ODOT has attempted to build consistency around future cost assumptions across the several transportation model tools that ODOT operates. For several reasons it is critical that all cost information be brought to a common year, one of those reasons is that costs amounts assumptions can come from many different sources. As an example, the cost comparison work below comes from a model who's costs are in 2005 dollars, a factor of 1.15 different than 2010 dollars according to CPI inflation adjustment. For future years, tolls, taxes, or fuel costs might be provided in those future year amount, say 2030 dollars for example. 2010 to 2030 would be a much larger inflation adjustment factor than 1.15. Therefore, it is critical to the model operation that all cost information be brought to a common year. The same way all cost information must be brought to a common unit of currency (in the case of ODOT model, currency is in US dollars).
For all work related to the ABM the Bureau of Land Managment's (BLM) Consumer Price Index (CPI) Inflation Calculator should be used for adjusting costs to the proper year - currently 2010. https://data.bls.gov/cgi-bin/cpicalc.pl
ODOT has several transportation modeling tools, however the one with the most price / cost testing is GreenSTEP / RSPM, which has recently been re-established as VisionEval (VE). The following is a table of some of the cost information contained in VisionEval for both current years and for future years. It's important to note that all of VisionEval cost assumptions are in 2005 dollars, so a factor of 1.15 is needed to make them comparable to the ABM.
Cost | Description | Model Year 2005 (2005 Dollars) | Model Year 2050 (2005 Dollars) |
---|---|---|---|
Fuel (Auto Operating Costs - AOC) | Fuel / Energy (Electricity); for 2005, $1.91 per gallon (excluding tax) at 21.4 mpg on average. | $0.09 | $0.04 - $0.06 |
Taxes (AOC) | Road User Fees - Gas Tax, Registration Fees, VMT Tax; for 2005, fuel taxes are 0.424 at 21.4 mpg. Registration fees are below $0.005/mile. | $0.02 | $0.01 - $0.03 |
Other (AOC) | Vehicle O&M Costs and future per mile costs, like PAYD insurance. | $0.03 | $0.03 - $0.05 |
Potential Carbon Tax | Some additional per mile costs related to carbon taxes or pricing are likely by 2050. | NA | ~$0.03 |
- Getting Started
- RunModel bat file
- Networks and Zone Data
- Auto Network Coding
- VDF Definition
- Transit Network Coding
- Non-motorized Network Coding
- Editing Land Use Data
- Running the Population Synthesizer
- Input Checker
- Analyzing Model Outputs
- Commercial Vehicle Model
- External Model
- Model Cost Inputs
- Value of Time
- Person Type Coding Logic
- MSA Feedback
- VMT Computation
- Shadow Pricing Mechanism
- Methodology for Developing TAZ Boundaries
- Methodology for Developing MAZ Boundaries
- Methodology for Developing TAPS
- Source of Land-Use Inputs
- Major University Model (Optional)
- Running Transit Everywhere Scenario
- Building the ABM Java Program
- Debugging ABM Python Code
- ABM Cleaning Protocol
- Updating to New Visum
- Troubleshooting and Debugging