Description:
Traffic Engineering Software (TES) is a suite of software analysis tools and data management tools that integrate three different types of information: collision data, traffic counts, and infrastructure data into one complete package that can be easily accessible in a tabular form and/or displayed automatically on a GIS map. It includes eight modules:
- Collision Module.
- Traffic Study Module.
- Safety Module.
- Sign Inventory Module.
- Signal Inventory Module.
- Infrastructure Module.
- GIS Module.
- Maintenance Module.
TES’ Safety Module provides safety analysis based on the Highway Safety Manual. This module can help determine the most high-risk intersections and road segments within the road network.
TES uses safety performance functions (SPF) to determine relationships between traffic volume, collisions, and road geometry for different types of locations within the municipality’s road network. Using this information, TES can evaluate all sites to determine their Potential for Safety Improvements (PSI) and overrepresentation of crash types
TES provides a flexible structure and users can update its databases using data available in other software packages. For example, it can interface with AASHTOWare Safety Analyst or IHSDM.
Tool Type:
Software
Owner Source:
private_company
Sponsor/Owner:
- Traffic Engineering Software (TES) Information Technology Ltd.
Published:
Availability:
This software is available for a fee at the following link:
Traffic Engineering Software (TES)
Disclaimer:
This information is disseminated under the sponsorship of the U.S. Department of Transportation in the interest of information exchange. The U.S. Government assumes no liability for the use of the information contained herein. This information does not constitute a standard, specification, or regulation. The U.S. Government does not endorse products or manufacturers. Trademarks or manufacturer's names appear in this information only because they are considered essential to the objective of this publication.
Any opinions, findings, and conclusions or recommendations, and translations thereof, expressed in this publication are those of the author(s) and do not necessarily reflect the views of the Federal Highway Administration.