Unit Costs (Unadjusted) - View by Subsystem

We want your Feedback

PLEASE EXPLORE THE NEW ITS UNIT COST SAMPLE ENTRIES:

We would appreciate you taking a few moments to provide your feedback: ITS Unit Costs Sample Entry Feature. Thank you for your thoughts and comments.

Subsystems
Unit costs are organized by Subsystems, based roughly on where an ITS element physically resides (e.g., video cameras deployed along the roadside, signal preemption devices installed in a transit bus, and video wall monitors located in a transportation management center).  The list of Subsystems comes from the National ITS Architecture.  In some cases, the subsystems were further divided to better reflect unit costs and better represent actual ITS deployments.  Refer to http://www.iteris.com/itsarch/html/glossary/glossary.htm for additional information on subsystems.

Unit Cost Elements
The Unit Cost Element refers to the equipment that would be included within the selected subsystem.  The unit cost element would be used to make the equipment package list for a subsystem within the architecture.  The Unit Cost Element Description refers to the assumptions made to determine the element’s unit price.  Unit Cost Elements reflect the equipment that is used in ITS project deployments.

Unit Cost Components
The Unit Cost Component refers to the specific equipment name given by the cost provider as shown within a specific unit cost entry.  Unit Cost Components have been collected from numerous sources including bid tabs, project estimates, actual project costs, and system cost reports.  The Unit Cost Component description refers to the component description developed by the cost provider.

Sample Unit Cost Entries
To enhance the Unit Cost Database, example entries of unit cost components have been compiled from available sources and provided in table format.  Excel spreadsheets of these tables are downloadable for the user to further analyze data if so desired.  Cost data have been provided from numerous sources.  The data are not intended to be all inclusive, nor is it intended that all unit cost components will map directly to the Unit Cost Element as currently provided in the database.  The purpose is to provide additional cost data for users to develop their own ITS cost estimates.