SAFETEA-LU Section 1201 Real-Time System Management Information 23 CFR Part 511 AASHTO SSOM Task Force on Systems Operations Performance Measures 9 April 2013 Bob Rupert, FHWA,

2 U.S. Department of Transportation Background – Legislation SAFETEA-LU, Subtitle B, §1201 □ Real-Time System Management Information Program  Establish a real-time system management information program in all States  Monitor traffic & travel conditions of the major highways  Share information to address congestion problems and facilitate traveler information.  Codified by Final Rule as Part 511 of Title 23 of United States Code of Federal Regulations □ 23 CFR Part 511

3 U.S. Department of Transportation Provisions of 23 CFR Part 511 (1 of 2)  Two-stage implementation □ All Interstates within 4 years (November 2014) □ Other metropolitan “Routes of Significance” as identified by States in collaboration with local agencies within 6 years (November 2016)  Information to be made available □ Construction lane and road closures □ Road- or lane-blocking traffic incidents □ Hazardous conditions & road or lane closures due to adverse weather □ Travel times (in Metropolitan areas)  “Metropolitan” = greater than 1 million MSA □ New additions with 2010 Census: Salt Lake City, Raleigh

4 U.S. Department of Transportation Provisions of 23 CFR Part 511 (2 of 2)  Regional ITS Architecture Update □ Regional architectures to be reviewed & updated as appropriate to ensure addressing RTSMIP provisions  Timeliness (age) of information □ Construction & Incident information within 20 minutes / within 10 minutes in Metro areas □ Adverse weather conditions within 20 minutes □ Travel times within 10 minutes  Quality measures □ Accuracy of 85% □ Availability of 90%

5 U.S. Department of Transportation Metro Areas Over 1 Million D.C. 52 metro areas as of 2010 Census

6 U.S. Department of Transportation Clarifications / Expansion of Information  Not Required by the Regulations □ No requirement for dissemination to general public, or the use of specific technologies or specific applications □ No method identified or discussed for measuring accuracy or other quality metrics ▪Flexibility to use methods appropriate to systems & processes used to acquire information & data □ No specific (i.e., new) enforcement actions ▪Usual Federal oversight, stewardship actions

7 U.S. Department of Transportation Data Exchange Formats  Not included in 23 CFR 511 regulations  Section 1201(b) provides that: □ USDOT to establish data exchange formats to ensure that the data provided by highway & transit monitoring systems can readily be exchanged across jurisdictional boundaries, facilitating nationwide availability of information.  Further, 1201(c)(2) notes that Regional ITS Architectures: □ Shall incorporate the data exchange formats to ensure that the data provided by highway and transit monitoring systems may readily be exchanged with State & local governments and may be made available to the traveling public.

8 U.S. Department of Transportation Data Exchange Formats  Initial list of potential standards published in 2007  Effort underway, using a system engineering approach to develop a Data Exchange Format Specification (DXFS) and companion Guidance document □ Walk-throughs with stakeholders  Center-to-Center communications □ Traffic Management Data Dictionary (TMDD), v3  Completed to date: □ Concept of Operations □ System Requirements Specification □ System Design Description

9 U.S. Department of Transportation Data Exchange Formats  The User Needs are organized around the four areas described in 23 CFR 511, with an additional area to address transit related information that is not directly covered by the Rule: □ Travel Time □ Incident Information □ Construction Information □ Weather Information □ Transit information  Guidance will include traceability among needs, architecture flows, requirements, standards, etc. □ Audience is system designer / developer

10 U.S. Department of Transportation Data Exchange Formats  Guidance and Data Exchange Format Specification will be completed by fall 2013 □ Dependent on completion of TMDD v3.03  Concept of Operations, System Requirements Specification, and System Design Description can be provided □ In final Draft

11 U.S. Department of Transportation Real-Time System Information Management Program Web site: Bob Rupert