Intelligent Transportation Systems

When is this applicable for your project?

All projects must complete the Technology/SEA Assessment to determine and document if a SEA is required. 

A SEA is required if technology (electronics, communications, or information processing used singly or in combination to improve the efficiency or safety of a surface transportation system) is included in the scope. The SEA is required per 23 CFR 940 and is a project delivery process for technology. It will help walk the project manager (PM), step by step, through designing technology consistently across CDOT through the use of templates. For additional details, use the link on the right to the ITS & Network Services website. The SEA deliverables are housed in OnTrack or available on the ITS & Network Services Branch website.  


Note: If a project has to go through the SEA process, the ITS & Network Services Branch should be involved in the Scoping, FIR, FOR, and final plan set review meetings 

What are the roles and responsibilities in this arena?

Currently, the project-specific SEA documents are determined in the Operations Evaluation (TSMO) process by CDOT Intelligent Transportation Systems (ITS). The project managers are then required to prepare the documents. These processes are currently under development.

Project Managers: 

  • The Technology/SEA Assessment will be completed by the PM which includes completing the initial assessment on if the SEA is required 
  • If the SEA is required, the PM is responsible for completing the remaining SEA documents 

ITS & Network Services:  

  • Verifying the need of the SEA was done correctly in the Technology/SEA Assessment
  • Collaborating with the PM and reviewing all submitted SEA documents 
  • Supporting PMs as a technology specialty resource

Red flags:

  • The Technology/SEA Assessment is done after scoping - this results in the entire SEA and technology design starting too late 
  • Not involving all stakeholders which includes end users of the system 
  • Submitting documents out of order or all at once - The SEA documents build on each other and are set up to be submitted sequentially 
  • Large maintenance costs, life cycle costs, or increase in man hours without a clear understanding of how address them 
  • Creating stand alone or one off systems 
  • Rewriting documents from scratch - previously prepared documents should be leveraged and reused with slight modification to be project specific
  • Not having a clear understanding of what the specific problem the project is supposed to solve and why the technology is being installed