Fusing Data Across the State of Florida to Support ATIS Services

Transcription

1 Session 5A: Center-to to-center Fusing Data Across the State of Florida to Support ATIS Services Steven W. Dellenback,, Ph.D., PMP Southwest Research Institute San Antonio, Texas

2 Objectives FDOT Objectives: Improve transportation safety Reduce congestion and delays Establish a software standard at TMCs throughout the State of Florida Develop standardized performance measure reporting to include: Staff performance Event response performance TMC performance And more SunGuide TM software goals: Flexible and expandable to match individual TMC needs Respond to traffic incidents in a rapid, accurate, and effective manner 2

3 Releases Release 1 (2004): Core infrastructure Basic device control (CCTV, DMS, TSS) Release 2 (2005): Advanced Incident Management Travel Times C2C added (Web Site and Emergency Evacuation support) Release 3 (2007): Revised event management and performance measurement AVL/RR (courtesy patrols) used for incident management Express (HOT) Lanes Release 4 (2008): Note: Data Fusion (for ATIS support) FHP CAD (state highway patrol data) FDOT utilizes TxDOT s Status Logger, Executive Handler, DMS Subsystem/driver and C2C 3

4 Why ATIS Development Efforts State has a very high number of tourists trips (511 is VERY popular) Seen FDOT Districts: 5 separate contracts to provide 511 services Web sites are District specific Objective: Recognize a cost savings by combining 511 services across the state Single entry point for Web Services Common look and feel 4

5 Florida Statewide 511 System Concept From FDOT Data Fusion Requirements Document 5

6 FLATIS Functional Subsystems From FDOT Data Fusion Requirements Document DFS provides data to IDS FL- ATIS) via C2C SunGuide data and other local and district sources 6

7 Software Architecture 7

8 Event Data To Be Fused SunGuide Events: Manually created Automatically created: Detectors (microwave, loops) Video Weather data: From DTN (similar to National Weather Service feed) Wide variety of weather events FHP CAD (state police) Third Party 8

9 Why Utilize a C2C Standard? Allows data to be collected across TMCs Allows assets to be used across TMCs Provides TMC software independence TMCs are not equal : Different equipment Different data from different TMCs (all do not provide the same) A tool to collect regional or statewide data Facilitates performance measurement reporting 9

10 C2C Infrastructure: Support both status and command/control Roadway network: Layout (GIS based) EM Locations (Event Management Locations): Geographic Roadway / Cross Street Current conditions: Link Speeds Travel Times (including delays) Events (detailed data), 23 different event types supported Field Devices: DMS: Messages Message queues (from remote centers) CCTV HAR Environmental Sensors 10

11 TMDD Network Model (TMDD = Traffic Management Data Dictionary) The network model is the underlying data model for C2C Travel times / traffic conditions are published as link data Each SunGuide deployment is its own network FL-ATIS (511) utilizes data from multiple networks 11

12 C2C Infrastructure Concept: Conceptual View 12

13 C2C Infrastructure Concept: Deploying a C2C Cloud 13

14 FL-ATIS Software Architecture SunGuide C2C is the transport mechanism Other agencies can dump data to the cloud to be added to the 511 system 14

15 FDOT C2C Conceptual Deployment 15

16 How SunGuide Data gets to FL- ATIS Data: In general, as SunGuide updates data it is immediately transmitted to the C2C C2C pushes data to a receiver s plugin, from there, the processing of the data is the burden of the receiver Data Format: Specified in the SunGuide Center-to-Center Interface Control Document (ICD), last published on Feb 8,

17 R4.0 / FL-ATIS Data Flow 17

18 Event Management Events created: Manually From alarms: Loops Microwave Video Weather 3 rd Parties Each event must be: Confirmed False alarm Road Rangers (assist vehicles) are critical to the event handling process 18

19 Event Response Plans: Can Cross District Boundaries When an event occurs, signs along any possible routes (for the specified distance) are included in the recommended response plan Relationships between DMS and HAR devices are established one-time 19

20 Event Response Plans con t System generates a recommended set of DMS and HAR devices to include as well as s to appropriate responders (Devices can added from LOCAL system or from REMOTE systems via C2C) Number included based on severity of event 20

21 Response Plans: Generating Recommended Plans Response plans include recommended signs: operators have complete control Operator may tune the parameters to alter the number of devices in the plan Devices from other centers can be added 21

22 SAE Codes: Standard Codes Provide a numeric way to describe conditions Allows any receiving application to unambiguously interpret Bandwidth efficient Very useful for IVR applications 22

23 SAE Code Interpretation SAE Description is updated whenever Event is Saved. 23

24 SunGuide Event Processing 24

25 DMS Processing 25

26 CCTV Processing 26

27 Web Site: C2C Powered 27

28 Summary C2C can be effectively used to combine information from multiple centers (running different versions of software) Using C2C to allow operational staff to utilize asset ACROSS deployment boundaries provides a significant improvement to operations C2C allows data to be fused and provided in a seamless (appearance of a single source to end users) TxDOT C2C is quite capable! 28

29 Questions? Contact Information: Steve Dellenback, Ph.D., PMP Southwest Research Institute PO Drawer Culebra Road San Antonio, Tx