SEA and the ITS Architecture Plan

The SEA and the CDOT ITS Architecture are both required per 23 CFR 940. As mentioned on the SEA summary page, the SEA process is a project delivery process that focuses on the technology elements of a project. The CDOT ITS Architecture Plan will be like a technology vision plan and document the minimum requirements for each service package a project must fulfill. Projects should only be implementing the service packages that were selected in the CDOT ITS Architecture Plan. Keep in mind the CDOT ITS Architecture Plan is in the early drafting stages so PM's are being directed to use the National ITS Architecture Plan.  

Which ITS Architecture Plan should be used - National or CDOT? 

Since the CDOT ITS Architecture Plan is still in the early development phases, PM's are being directed to use the National ITS Architecture Plan. Using an Architecture Plan is critical for creating consistencies by always having the same minimum elements, functional requirements, and interfaces. Using an Architecture Plan that is not customized to CDOT though will create challenges and at some times frustrations. We are working quickly to get the CDOT ITS Architecture created, but it will take time to do a thorough job. Frustrations with the National ITS Architecture Plan stem from different terminology and references items that do not occur at CDOT. If there is any confusion while completing the SEA documentation in regards to the service package content, please reach out to the ITS & Network Services Branch for help. 

Why is the ITS Architecture Plan incorporated with the SEA documents? 

The CDOT ITS Architecture Plan is intended to keep CDOT consistent with technology projects and also ensure CDOT stays focused on achieving our technology vision. Projects that do not fall under the CDOT ITS Architecture Plan require further discussion if they should even be implemented at CDOT. New technology that does not help CDOT reach our vision state takes time and valuable resources away from the projects that fall within the CDOT ITS Architecture Plan. 

Should a project be modifying a service package or implementing a brand new technology (with executive approval), the SEA process is structured to document and create discussions around the modifications. 

What is the relationship between the SEA and the ITS Architecture documents? 

The majority of the SEA documents are sequential. The beginning SEA documents rely on the ITS Architecture Plan to make sure the project scope falls within a selected CDOT ITS Architecture Plan service package. As the SEA documents dive into more detail, content will be pulled directly from the selected CDOT ITS Architecture Plan service package requiring documentation on how the project intends to fulfill the minimum established elements, functional requirements, and interfaces. Using this strong, consistent foundation, the PM can then dig into the more project specific details for the later SEA documents.