DOT-RFI-26-5001-ADCS.pdf

RFI Shell07/2018

REQUEST FOR INFORMATION (RFI) from the Florida Dept. of Transportation

The Department of Transportation, District Five, Office of Intermodal Systems Development is requesting the following information from prospective vendors about the commodities and/or contractual services described below.

Description of Commodities/Contractual Services:

Florida Department of Transportation District 5 is interested in piloting an automated data collection system (ADCS) solutions to improve the safety of our workers and the accuracy and efficiency of roadway inventory activities along the State Highway System (SHS) and along localized off-system roadways. The first goal of an ADCS implementation is to improve worker safety by reducing the amount of time they are physically on the roadway. The second goal of an ADCS implementation is to reduce costs and improve efficiency associated with data collection.

The Department is seeking a Commercial Off-the-Shelf (COTS) solution and not a development project. An ADCS that is able to perform some of the functions currently performed by personnel is expected. A full replacement of all data gathering is not required. This RFI is intended to gauge the maturity of existing systems to guide the scoping of a pilot phase deployment, including assisting in understanding reasonable thresholds, identifying overly specific means and methods in our standards, or other constraints that the Department should take into account when developing a future procurement document.

The ADCS shall include all sensors, equipment, and software necessary to provide reliable, repeatable georeferenced datasets relating to the location, physical characteristics, condition, and geometry of a roadway, as well as the location, type, condition, and frequency of supplemental roadside infrastructure.

The ADCS will support the Department’s Roadway Characteristics Inventory (RCI) program, and must produce geospatial data compatible with the Linear Referencing System (LRS). The RCI program was established by FDOT to ensure compliance with federal reporting requirements of the Federal Highway Administration’s (FHWA) Highway Performance Monitoring System (HPMS). FDOT Districts carry out the RCI program on a five-year inventory cycle for all roadways. Additionally, FDOT conducts the HPMS Standard Sample inventory on a three-year cycle.

The FDOT District Five region includes 1,979 on-system centerline miles and 4,760 off-system centerline miles. The ADCS will be responsible for capturing data in accordance with HPMS and RCI required frequencies. The vendors may batch data collection, feature extraction, or otherwise optimize the process within the requirements of HPMS and RCI.

Functional Classification Length (in centerline miles) Rural Major Collector 503 Rural Minor Collector 388 Rural Minor Arterial 191 Rural Principal Arterial Expressway 16 Rural Principal Arterial Interstate 87 Rural Principal Arterial Other 402 Rural Local 201 Urban Major Collector 1,681

DOT-RFI-26-5001-ADCS

Urban Minor Arterial 806 Urban Minor Collector 845 Urban Principal Arterial Expressway 140 Urban Principal Arterial Interstate 193 Urban Principal Arterial Other 1,067 Urban Local 234 Total 6,739

The FDOT 2025 RCI Handbook1 provides a detailed description of all administrative- and field-related datasets collected in the RCI program, including how to manually collect them. The primary intent of this Request for Information (RFI) is to better understand available solutions for automated data collection, and their ability to deliver the various field elements of the FDOT RCI.

Minimum Technical Requirements The Minimum Technical Requirements for the District 5 technology-based ADCS are provided below. The MTR are not intended to be complete technical specifications but define the baseline functionality of the system(s). This RFI is meant to determine the cost feasibility of an ADCS deployment and to refine and create more specific requirements if the ADCS procurement moves forward. The proposed solution is not expected to capture all features described in the RCI Handbook; the proposed solution should generally be capable of capturing the Physical Features (Series 200) and Operational Features (Series 300) of the RCI Handbook that occur within the roadway right-of-way. Additionally, responses to this RFI will be used to determine the viability of capturing Maintenance Features (Series 400) using the ADCS deployment. Conversely, the proposed solution does not need to capture Administrative Features (Series 100), Non-Motorized Way Features (Series 800), and Rail Line Features (900). Appendix B identifies which RCI features are relevant to the scope of this RFI and which RCI features will be handled by FDOT and/or Consultant staff, separate from the focus of this RFI.

System shall deliver output data in shapefile format, with a projection in UTM 17N NAD83. At a minimum, accuracy should be sub-meter, except where stated otherwise in the accuracy standards provided in General Interest Roadway Data (GIRD) Procedure, RCI Handbook, and the Quality Assurance Monitoring Plan (QAMP). The output data shall be compatible with the Linear Referencing System (LRS) as described in the LRS Handbook. However, the Department will conduct the conversion process from the sub-meter shapefile to the LRS.

System shall be capable of identifying different roadway features derived from pavement markings, including but not limited to:

o General Purpose Through and Turn Lanes, Inside and Outside Shoulders, Two-Way Left Turn Lane, Bicycle Lane and Bicycle Keyhole Lane, Auxiliary Lane, Toll Lane / High-Occupancy Toll Lane, and Sharrow

System shall be capable of identifying and determining characteristics of supportive infrastructure as well as other features adjacent to the roadway, including but not limited to:

o Intersections, Structures, Railroad Crossings, Sidewalks and Shared-use Paths, Traffic Signals, Medians, Barriers, Lighting, Guardrails, Ditches, Turnouts, On-street Parking, and Fencing.

1 FDOT Transportation Data and Analytics Office. FDOT 2025 RCI Handbook. https://www.fdot.gov/statistics/rci/default.shtm

System shall be capable of applying logical segmentation termini for various RCI features, based on the requirements established in the FDOT RCI Handbook and the GIRD.

System shall adhere to following Florida Administrative Code (FAC) statutes related to cybersecurity:

o 60GG-1 Department of Management Services Project Management and Oversight o 60GG-2 Information Technology Security o 60GG-3 Data Center Operations o 60GG-4 Cloud Computing o 60GG-5 State of Florida Enterprise Architecture

Specific Information Requested:

1. Vendor Name

2. Description of Proposed Solution - Provide a brief write-up of the overall system – include a product name and overview of the system architecture; identification of subsystem or components; technology differentiators; and other pertinent information. Please provide an estimated number of centerline miles for which the proposed solution has been used.

3. Has the proposed solution been successfully deployed for other state DOTs?

4. If the answer to Question No. 3 is “Yes”, please identify the location (roadway, city, state), quantity, owner / agency, and Project Manager contact information (e-mail address, phone number) for each successful deployment project.

5. Please identify if the proposed solution meets the minimum technical requirements (Yes / No).

6. If the answer to Question No. 5 is “No”, please provide additional information relating to the technical requirement(s) that are not met by the proposed solution.

7. Has the proposed solution been previously evaluated, certified, or approved by a public agency or governing body?

8. If the answer to Question No. 7 is “Yes”, please identify which public agencies or governing bodies have provided certifications or approvals.

9. Please respond to Appendix A indicating the proposed solution’s capabilities relating to RCI features.

In Appendix A, please provide General Comments where further explanation of the proposed solution’s capabilities is needed. Please also provide the proposed solution’s Level of Accuracy related to each feature. Please be aware this information is important in judging the feasibility but is also assisting in determining requirements for a future contract.

a. Level of accuracy (in feet) for the feature captured

b. Level of accuracy relating to classification of the feature captured

i. False Positives – classifying something that is not an actual feature

ii. False Negatives – missing the classification of a feature

iii. Misclassification – incorrectly classifying a feature

10. Describe the proposed solution’s process for data collection verification and quality control.

11. Describe your approach to generating datasets that are compatible with the LRS.

12. Describe your approach to the HPMS schedule (all HPMS roadways every 3 years) and the larger RCI schedule (all RCI roadways every 5 years).

13. Are there best practices from other locations for data quality assurances that can be shared? The Department intends to perform data quality assurance, verifying across features for accuracy in location and classification. This program would ideally be staffed to take significantly longer than the ADCS to produce results. In some classes the verification may occur multiple years after initial interpretation by the vendor. This would be tied to financial consequences, and the goal is not to unnecessarily increase risks for either the Department or the ADCS. The Department wants to be a good partner and ensure accuracy in reported data. Please share information on successful programs or provide contact information for other agencies to coordinate with.

14. Provide the cost estimate range (low and high) for collecting data once every five years off-system and every three years on-system for the District Five Transportation System. The cost range should include data collection, data verification, final deliveries of georeferenced data, and risk.

15. Please provide a typical data collection schedule. Include milestones for planning, data collection, generating georeferenced datasets subdivided by feature or features to meet the minimum specifications of this project?

16. Can the proposed solution capture passing sight distance?

17. Can the proposed solution identify if there are obstacles nearby that would prevent roadway expansion up to 100 feet from the edge of through lanes?

o Can the proposed solution estimate potential number of expansion lanes based on identification of obstacles (or lack thereof) to expansion?

18. Does your solution incorporate aerial imagery into the analysis and outputs? If yes, please describe the process and outputs.

19. Can the proposed solution identify the type of signalization present at a signalized intersection? Types of signalization include:

o Uncoordinated Fixed Time, Uncoordinated Traffic Actuated, Coordinated Progressive, Coordinated Real-time Traffic Adaptive, No Signal System.

20. What is your data retention policy? What is the process for the Department to retrieve data files?

21. Is a cloud-hosted platform available for the Department to retrieve data collected from the ADCS, as needed? If so, what data would be available? Available imagery to allow navigation and data validation is a significant value add.

Please attach additional information for the proposed solution(s) along with the completed questionnaire – including but not limited to product data sheets, technical specifications, brochures, client testimonials, and other resource materials providing a complete overview of the system(s) to be evaluated.

TIMELINE

Action Date Local Time (Eastern)

Advertisement Posted February 24, 2026

Deadline for All Questions March 6, 2026 10:00 AM

Deadline for Posting Responses to Questions

March 13, 2026 10:00 AM

RFI Responses Due May 8, 2026 10:00 AM

Public Meeting to Open Responses

May 8, 2026 11:00 AM

Contact for Questions or clarification:

Please submit all questions in writing to the following email address D5.ProcurementQuestions@dot.state.fl.us

The requested information must be received by 10:00 AM (EST) on May 8, 2026 at the following E-mail address: D5.Purch@dot.state.fl.us

NOTE: Responses to this Request for Information (RFI) will be reviewed by the agency for informational purposes, and will not be considered as offers to be accepted by the agency to form a binding contract.

Advertisement of any subsequent competitive solicitation that may result from this RFI will be posted on the Florida Vendor Information Portal.

APPENDIX A – ADCS Proposed Solution Capabilities Please fill out the table below, indicating if the proposed ADCS solution can capture the data for each RCI feature (Yes / No / “See comment”) for each roadway type. If necessary, please clarify the capability of the proposed ADCS solution in the General Comments column. Please also provide the anticipated level of accuracy in an appropriate unit of measure.

APPENDIX A – ADCS Proposed Solution Capabilities

RCI Features Proposed Solution's Capabilities, Limitations, and Level of Accuracy

Related to RCI Handbook Features General Comments – Capabilities

Feature Number

Description Name HPMS Managed

Lane

01, 11 Interstate

PA

02, 12 Fwy/Exp

PA

04, 14 Other

PA

06, 16 Minor

Art

07, 17 Major Coll

08, 18 Minor Coll

09, 19 Local

Level of Accuracy

Number Example EXAMPLE X Yes Yes Yes Yes Yes Yes Yes No <1m N/A

212 Through Lanes

NOLANES X

SURWIDTH X

213 Auxiliary Lanes

AUXLNTYP X

AUXLNUM X

AUXLNWTH X

214 Outside Shoulders

MLTRFSEP X

SHLDTYPE X

SHLDTYPx X

SLDWIDTH X

SHLDWTHx X

215 Medians

MDBARTYP X

MEDWIDTH X

RDMEDIAN X

216 Bike Lanes & Sidewalk

BIKELNCD X

BIKLNBCD X

BIKSLTCD X

BIKSLTWD X

SEPBLNWD X

SDWLKBCD X

SHRDPTH X

SIDWLKWD X

217 Sidewalks SIDEWALK

219 Inside Shoulders (R/L only)

ISLDTYPE X

ISLDTYPx X

ISLDWDTH X

ISLDWTHx X

220 Non-Curve Intersection Point NCPTINT X

221 Horizontal Curve

BEARING X

HRZCANGL X

HRZDGCRV X

HRZPTINT X

232 Surface Layers

FRICTCSE X

SURFLAYx X

241 Crossdrains & Box Culverts

RCI Features Proposed Solution's Capabilities, Limitations, and Level of Accuracy

Related to RCI Handbook Features General Comments – Capabilities

Feature Number

Description Name HPMS Managed

Lane

01, 11 Interstate

PA

02, 12 Fwy/Exp

PA

04, 14 Other

PA

06, 16 Minor

Art

07, 17 Major Coll

08, 18 Minor Coll

09, 19 Local

Level of Accuracy

242 Storm Sewer 245 Roadside Ditches 248 Outfall Ditches

251 Intersections

BEGSECNM X

ENDSECNM X

INTSDIRx X INTSRTPx X

252 Interchanges

EXITNO X

INTERCHG X

253 Railroads

CHKDIGIT X

RRCROSNO X

256 Turnouts 257 Crossovers CROVERLG 271 Guardrail 272 Fencing

273 Cable Barriers

CABLBRTY

CABLWIRE

275 Misc. Concrete Structures

311 Speed Zone

DTESZAPP X

MINSPEED X

312 Turning Restrictions 313 Parking Restrictions 320 Milemarker Signs MILEMARK 322 Signals

323 School Zones

SCHLNAME

SCHLPED

326 Traffic Monitoring Sites TRSTANO 341 Lighting 360 Toll Plazas 361 Service Plazas 411 Roadside Mowing 412 Weed Control 413 Landscape Area 421 Roadside Ditch Cleaning 422 Median Ditch Cleaning 431 Parks & Rest Areas 443 Delineators 451 Striping 452 Symbols & Messages

RCI Features Proposed Solution's Capabilities, Limitations, and Level of Accuracy

Related to RCI Handbook Features General Comments – Capabilities

Feature Number

Description Name HPMS Managed

Lane

01, 11 Interstate

PA

02, 12 Fwy/Exp

PA

04, 14 Other

PA

06, 16 Minor

Art

07, 17 Major Coll

08, 18 Minor Coll

09, 19 Local

Level of Accuracy

453 Crosswalks 454 Stopbars 455 Raised Pavement Markers PAVTMARK 460 Attenuators 480 Highway Signs

APPENDIX B – Anticipated Scope Items (derived from RCI Handbook) This table is for informational purposes only. It is intended to show which RCI Handbook features are related to the RFI (“In Scope”) and which features will be handled by FDOT staff or their designee.

The table summarizes each RCI feature, including their number, description, series type, and measurement.

APPENDIX B – Overview of RCI Features

RFI Scope or FDOT RCI Features Feature Type (by Series) Feature Measurement

Feature Number

Description Administrative

Features Maintenance

Features Rail

Features Trail

Features Operational

Features Physical Features

Length Points Counts

FDOT / Consultant 111 State Road System X X FDOT / Consultant 112 Federal System X X FDOT / Consultant 113 AASHTO X FDOT / Consultant 114 Local Name Effective Date ( November 2022) X X FDOT / Consultant 115 Special Designation X X FDOT / Consultant 116 Freight Network X FDOT / Consultant 118 HPMS X X FDOT / Consultant 119 HPMS Universe X X FDOT / Consultant 120 Type Road X X FDOT / Consultant 121 Functional Classification X X FDOT / Consultant 122 Facility Classification X X FDOT / Consultant 124 Urban Classification X X FDOT / Consultant 126 Preliminary Context Classification X FDOT / Consultant 128 Target Speed X X FDOT / Consultant 137 Maintenance Area Boundary X X FDOT / Consultant 138 Roadway Realignment X X FDOT / Consultant 139 New Alignment X FDOT / Consultant 140 Section Status Exception X X FDOT / Consultant 141 Stationing Exception X X FDOT / Consultant 142 Managed Lanes X X FDOT / Consultant 143 Assoc. Station Exception X X FDOT / Consultant 144 FL Intra. Hwy System (inactive) X X FDOT / Consultant 145 Level of Service X X FDOT / Consultant 146 Access Management X X FDOT / Consultant 147 Strategic Intermodal System (SIS) X FDOT / Consultant 148 Memorial Designation X In Scope 212 Through Lanes X X In Scope 213 Auxiliary Lanes X X In Scope 214 Outside Shoulders X X In Scope 215 Medians X X In Scope 216 Bike Lanes & Sidewalk X In Scope 217 Sidewalks X X In Scope 219 Inside Shoulders (R/L only) X X FDOT / Consultant 220 Non-Curve Intersection Point X X

APPENDIX B – Overview of RCI Features

RFI Scope or FDOT RCI Features Feature Type (by Series) Feature Measurement

Feature Number

Description Administrative

Features Maintenance

Features Rail

Features Trail

Features Operational

Features Physical Features

Length Points Counts

FDOT / Consultant 221 Horizontal Curve X X In Scope 230 Surface Description X X FDOT / Consultant 232 Surface Layers X X FDOT / Consultant 233 Base X X In Scope 241 Crossdrains & Box Culverts X In Scope 242 Storm Sewer X X FDOT / Consultant 243 Off Roadway Areas X In Scope 245 Roadside Ditches X X X In Scope 248 Outfall Ditches X X In Scope 251 Intersections In Scope 252 Interchanges X X In Scope 253 Railroads X X In Scope 256 Turnouts X X X In Scope 257 Crossovers X X FDOT / Consultant 258 Structures X X In Scope 271 Guardrail X X In Scope 272 Fencing X X In Scope 273 Cable Barriers X In Scope 275 Misc. Concrete Structures X X In Scope 311 Speed Zone X X In Scope 312 Turning Restrictions X X In Scope 313 Parking Restrictions X X In Scope 320 Milemarker Signs X X In Scope 322 Signals X X In Scope 323 School Zones X X In Scope 326 Traffic Monitoring Sites X X FDOT / Consultant 330 Traffic Flow Break Station X X FDOT / Consultant 331 Traffic Flow Breaks X X In Scope 341 Lighting X X In Scope 360 Toll Plazas X X In Scope 361 Service Plazas X X In Scope 411 Roadside Mowing X X In Scope 412 Weed Control X X In Scope 413 Landscape Area X X In Scope 421 Roadside Ditch Cleaning X X In Scope 422 Median Ditch Cleaning X X In Scope 431 Parks & Rest Areas X X In Scope 443 Delineators X X In Scope 451 Striping X X

APPENDIX B – Overview of RCI Features

RFI Scope or FDOT RCI Features Feature Type (by Series) Feature Measurement

Feature Number

Description Administrative

Features Maintenance

Features Rail

Features Trail

Features Operational

Features Physical Features

Length Points Counts

In Scope 452 Symbols & Messages X X In Scope 453 Crosswalks X X In Scope 454 Stopbars X X In Scope 455 Raised Pavement Markers X X In Scope 460 Attenuators X X In Scope 480 Highway Signs X X FDOT / Consultant 481 Highway Maintenance Class X X FDOT / Consultant 801 Trails X X FDOT / Consultant 901 Rail Line Facility X X FDOT / Consultant 902 Passenger Rail X X FDOT / Consultant 903 Rail Passenger Station Name X X X

APPENDIX C – Crosswalk of RCI Feature Characteristics This table is for informational purposes only, providing a crosswalk of features from the RCI Handbook. For more detail, see the RCI Handbook Appendix A and RCI Handbook Chapter 7 – RCI Features & Characteristics.

Legend:

✓ Full Extent, required where characteristic exists CP Construction Plans (Greyed out) O Optional

APPENDIX C – Crosswalk of RCI Characteristics Feature Number Description

Name Manage

Lane 01, 11 Interstate PA 02, 12 Fwy/Exp PA

04, 14 Other

PA

06, 16 Minor Art

07, 17 Major Coll 08, 18 Minor Coll 09, 19 Local

212 Through Lanes NOLANES ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

SURWIDTH ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

213 Auxiliary Lanes

AUXLNTYP ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

AUXLNUM ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

AUXLNWTH ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

214 Outside Shoulders

MLTRFSEP ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

SHLDTYPE ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

SHLDTYPx ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

SLDWIDTH ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

SHLDWTHx ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

215 Medians

MDBARTYP ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

MEDWIDTH ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

RDMEDIAN ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

216 Bike Lanes & Sidewalk

BIKELNCD ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

BIKLNBCD ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

BIKSLTCD ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

BIKSLTWD ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

SEPBLNWD ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

SDWLKBCD ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

SHRDPTH ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

SIDWLKWD ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

217 Sidewalks

219 Inside Shoulders (R/L only)

ISLDTYPE ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

ISLDTYPx ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

ISLDWDTH ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

ISLDWTHx ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

220 Non-Curve Intersection Point NCPTINT CP CP CP CP CP CP CP CP

221 Horizontal Curve

BEARING CP CP CP CP CP CP CP CP

HRZCANGL CP CP CP CP CP CP CP CP

HRZDGCRV CP CP CP CP CP CP CP CP

HRZPTINT CP CP CP CP CP CP CP CP

230 Surface Description PAVECOND ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

SURFNUM ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

232 Surface Layers

FRICTCSE CP CP CP CP CP CP CP CP

SURFLAYx CP CP CP CP CP CP CP CP

233 Base

BASETHK CP CP CP CP CP CP CP CP

TYPEBASE CP CP CP CP CP CP CP CP

241 Crossdrains & Box Culverts ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ 242 Storm Sewer ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ 245 Roadside Ditches ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ 248 Outfall Ditches ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

251 Interchanges

BEGSECNM ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

ENDSECNM ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

INTSDIRx ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ INTSRTPx O O O O O O O O

252 Interchanges

EXITNO ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

INTERCHG ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

253 Railroads

CHKDIGIT ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

RRCROSNO ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

256 Turnouts 257 Crossovers 271 Guardrail 272 Fencing 273 Cable Barriers 275 Misc. Concrete Structures

311 Speed Zone

DTESZAPP ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

DTESZIMP ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

MAXSPEED ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

MINSPEED ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

312 Turning Restrictions 313 Parking Restrictions 320 Milemarker Signs 322 Signals 323 School Zones

326 Traffic Monitoring Sites

TRSTANO ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

TRSTATYP ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓

341 Lighting 360 Toll Plazas 361 Service Plazas 411 Roadside Mowing 412 Weed Control 413 Landscape Area 421 Roadside Ditch Cleaning 422 Median Ditch Cleaning 431 Parks & Rest Areas

443 Delineators 451 Striping 452 Symbols & Messages 453 Crosswalks 454 Stopbars 455 Raised Pavement Markers 460 Attenuators 480 Highway Signs