| 1 | | Work with Regional Traffic Engineers (RTEs) to obtain resolutions from municipalities, MPOs, and RPOs (as appropriate and as required) regarding the proposed route change. Once obtained, an electronic copy of these should be sent to the State Traffic Engineer or designee (carbon copy TMSD’s Mobility and Safety Information Engineer and TMSD’s Ordinance Program Coordinator) |
| 2 | | If a project, obtain project break down maps and send an electronic copy to TMSD’s Mobility and Safety Information Engineer (carbon copy TMSD’s Ordinance Program Coordinator and appropriate RTEs). Project breakdown maps, or a statement that they do not exist, are due thirty (30) business days after receipt of the NTP unless otherwise specified. |
| 3 | | If a project, obtain construction progress reports and send an electronic copy to TMSD’s Mobility and Safety Information Engineer (carbon copy TMSD’s Ordinance Program Coordinator and appropriate RTEs). Construction progress reports are due thirty (30) business days after receipt of the NTP unless otherwise specified. |
| 4 | | If a project, obtain copies of let plans separated into three groups: (a) title sheet, (b) roadway profile sheets (sheets 4+, horizontal profiles only), and (c) structure sheets (only for numbered structures, and only the general drawing sheets for bridges or the location sketch sheets for pipes/culverts). These plan sheets are needed for mileposting (station numbers to calculate mileposts, Y-lines for intersecting features, new service roads or “cut” secondary roads that may need new SR numbers, bridge numbers to add as features, etc.). An electronic copy of these plan sheets should be sent to TMSD’s Mobility and Safety Information Engineer (carbon copy TMSD’s Ordinance Program Coordinator and appropriate RTEs). Let plan sheets are due thirty (30) business days after receipt of the NTP unless otherwise specified. |
| 5 | | Complete route change worksheets. Note that some items on the worksheets generally necessitate an on-site field investigation. Once completed, an electronic copy of these worksheets should be sent to TMSD’s Mobility and Safety Information Engineer (carbon copy TMSD’s Ordinance Program Coordinator and appropriate RTEs). Worksheets are due thirty (30) business days after receipt of the NTP unless otherwise specified. |
| 6 | | Perform Interstate scans for any project being opened as an Interstate or any route being elevated to Interstate status. Scans generally include a review of traffic volume, access control, right-of-way, speed, sight distance, roadway geometry, lane and shoulder widths, slopes, medians, clearances, structures, and crashes. Deadlines for completion of scans shall be provided by the State Traffic Engineer (or designee), and field visits may need to be coordinated with RTEs, FHWA personnel, and others. Submittals shall be sent to the State Traffic Engineer or designee (carbon copy TMSD’s Mobility and Safety Information Engineer, TMSD’s Ordinance Program Coordinator, and appropriate RTEs). |
| 7 | | Create a formal map for each route being changed with segment breaks at municipal limits, major interchanges, and state lines in accordance with AASHTO standards. Maps shall include a title, legend, segment lengths (in tenths of miles), “north” designation, creation date, and appropriate notes. Maps are due thirty (30) business days after receipt of the NTP (unless otherwise specified). Once created, an electronic copy of these should be sent to the State Traffic Engineer or designee (carbon copy TMSD’s Mobility and Safety Information Engineer, TMSD’s Ordinance Program Coordinator, and appropriate RTEs). |
| 8 | | [Skip this step for NC routes and routes being designated as “Truck” or “Connector”] Create preliminary AASHTO application(s) for each route being changed and shall include proposed changes to AASHTO’s U.S. Route Number Database. Once created, an electronic copy of these should be sent to the State Traffic Engineer or designee (carbon copy TMSD’s Mobility and Safety Information Engineer, TMSD’s Ordinance Program Coordinator, and appropriate RTEs). Preliminary applications are due no later than ten (10) business days prior to the US/Interstate Subcommittee meeting. |
| 9 | | Attend US/Interstate Subcommittee meetings and take minutes. An electronic copy of the minutes should be sent to the State Traffic Engineer or designee (carbon copy TMSD’s Mobility and Safety Information Engineer, TMSD’s Ordinance Program Coordinator, appropriate RTEs, and all other attendees). Minutes are due no later than five (5) business days following the meeting. |
| 10 | | Revise formal maps and preliminary AASHTO applications as needed based on comments received at the US/Interstate Subcommittee meeting. Once revised, an electronic copy of these should be sent to the State Traffic Engineer or designee (carbon copy TMSD’s Mobility and Safety Information Engineer, TMSD’s Ordinance Program Coordinator, and appropriate RTEs). Revisions are due no later than ten (10) business days prior to the US/Interstate Committee meeting. |
| 11 | | Check construction progress reports for updates and, if any, send an electronic copy to the State Traffic Engineer or designee (carbon copy TMSD’s Mobility and Safety Information Engineer, TMSD’s Ordinance Program Coordinator, and appropriate RTEs). Updates, if any, are due no later than ten (10) business days prior to the US/Interstate Committee meeting |
| 12 | | Attend US/Interstate Committee meetings and take minutes. An electronic copy of the minutes should be sent to the State Traffic Engineer or designee (carbon copy TMSD’s Mobility and Safety Information Engineer, TMSD’s Ordinance Program Coordinator, appropriate RTEs, and all other attendees). Minutes are due no later than five (5) business days following the meeting |
| 13 | | Revise formal maps and preliminary AASHTO applications as needed based on comments received at the US/Interstate Committee meeting. Once revised, an electronic copy of these should be sent to the State Traffic Engineer or designee (carbon copy TMSD’s Mobility and Safety Information Engineer, TMSD’s Ordinance Program Coordinator, and appropriate RTEs). Revisions are due no later than ten (10) business days prior to the AASHTO submittal date. |
| 14 | | [Skip this step for NC routes and routes being designated as “Truck” or “Connector”] Review AASHTO’s Special Committee on U.S. Route Numbering web site for route change approvals/denials (usually available around 2-4 weeks following AASHTO’s semiannual meeting) and send an electronic copy to the State Traffic Engineer or designee (carbon copy TMSD’s Mobility and Safety Information Engineer, TMSD’s Ordinance Program Coordinator, and appropriate RTEs). |
| 15 | | Request new secondary road (SR) numbers from DOT’s GIS Unit’s Data Conversion Group and send an electronic copy to TMSD’s Mobility and Safety Information Engineer (carbon copy TMSD’s Ordinance Program Coordinator and appropriate RTEs). Requests are due no later than ten (10) business days following formal approval of the number change (US/Interstate Committee approval for NC routes, AASHTO approval for US routes, and AASHTO and/or FHWA approval for Interstate routes). |
| 16 | | Update the mileposting of all mainlines and intersecting routes and submit changes to TMSD’s Mobility and Safety Information Engineer for review. Use appropriate TEAAS features reports and/or the mileposting “Short Form” (along with extra pages as needed), and appropriate TEAAS high order reports and/or the “High Order Routes Sheet” as needed. Mileposting recommendations are due no later than ten (10) business days following formal approval of the number change (US/Interstate Committee approval for NC routes, AASHTO approval for US routes, and AASHTO and/or FHWA approval for Interstate routes). |
| 17 | | Once the mileposting change recommendations have been reviewed and approved by TMSD’s Mobility and Safety Information Engineer (or designee), update all mileposting in TEAAS. Once updated, notify TMSD’s Mobility and Safety Information Engineer (or designee from previous step) for review. Mileposting updates are due no later than ten (10) business days following approval of mileposting change recommendations. |
| 18 | | Once the updated mileposting information has been approved, ensure that all routes with number or length changes be added to DOT’s “Exclusion List” by TMSD’s Mobility and Safety Information Engineer. |
| 19 | | Create new Route Change ordinances (ordinance type 22) in TEAAS and send the ordinance numbers to TMSD’s Mobility and Safety Information Engineer and TMSD’s Ordinance Program Coordinator for review and input of temporary effective dates. Route change ordinances are due no later than five (5) business days following approval of mileposting updates. NOTE – only create route change ordinances for secondary roads if the secondary road is being upgraded to a primary or if a primary is being downgraded to a secondary road. |
| 20 | | Create new National Network (NN), STAA Designation, and STAA Reasonable Access ordinances (ordinance types 40-46) in TEAAS and send the ordinance numbers to TMSD’s Mobility and Safety Information Engineer and TMSD’s Ordinance Program Coordinator for review and input of temporary effective dates. Also include in the correspondence the ordinance number for any ordinance being repealed by the route change or replaced by the new ordinances so TMSD’s Ordinance Program Coordinator can input temporary repeal dates. NN and STAA ordinances are due no later than five (5) business days following approval of mileposting updates. |
| 21 | | Create other new ordinances (speed limits, no parking, etc.) in TEAAS as needed and send the ordinance numbers to appropriate RTEs for review, approval, and municipal concurrence (as needed). Also include in the correspondence the ordinance number for any ordinance being repealed by the route change or replaced by the new ordinances. Be sure to copy TMSD’s Mobility and Safety Information Engineer and TMSD’s Ordinance Program Coordinator for input of temporary effective and/or repeal dates. Other ordinances are due no later than five (5) business days following approval of mileposting updates. |
| 22 | | Perform additional items as requested by the State Traffic Engineer (or designee), TMSD’s Mobility and Safety Information Engineer, TMSD’s Ordinance Program Coordinator, or Contract Manager that may be outside the normal route change process for the specific route being worked on. |
| 23 | | Pending description |
| 24 | | |
| 25 | | |
