SunGuide TM 4.0 Functionality Data Fusion: How Data is Managed June 24, 2008

1. SunGuideTM 4.0 FunctionalityData Fusion: How Data is ManagedJune 24, 2008

2. Purpose of this presentation… • Purpose: • Informational presentation (not a design review) • Provide data flows from SunGuide to FL-ATIS • Provide insight into data being provided to FL-ATIS • Objectives: • Establish a baseline understanding of how SunGuide will be used to “create” data for FL-ATIS • No intent: • To revisit R4.0 design decisions SunGuide 4.0 Functionality

3. Release 4.x Development Activities:Releases: 4.0-Data Fusion, 4.1-Travel Time SunGuide 4.0 Functionality

4. Florida Statewide 511 System ConceptFrom FDOT Data Fusion Requirements Document SunGuide 4.0 Functionality

5. FLATIS Functional SubsystemsFrom FDOT Data Fusion Requirements Document • DFS provides data to IDS via C2C • SunGuide data and other local and district sources SunGuide 4.0 Functionality

6. Release 4.0 and FL-ATIS Responsibilities • SunGuide C2C is the “transport mechanism” • If other agencies (e.g. OOCEA) wish to provide data it MUST comply with the SunGuide C2C interface requirements SunGuide 4.0 Functionality

7. C2C Infrastructure Concept:Deploying a C2C “Cloud” SunGuide 4.0 Functionality

8. 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 • SunGuide web site (511 web site in D5) utilizes data from multiple networks SunGuide 4.0 Functionality

9. 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, 2008 SunGuide 4.0 Functionality

10. R4.0 Conceptual Data Flow SunGuide 4.0 Functionality

11. Providing Data to Other “Consumers” (3rd Parties) • C2C: • Is the “method” SunGuide uses to transmit data outside the “domain” of a SunGuide deployment. • Was built using the available ITS Standards produced by NEMA, AASHTO, and ITE. • The 3rd party feed identified in FDOT DFS document will be a “C2C feed”. • C2C ICD: • Has been published (this describes how to access the data). • To access the data feed a program has to be developed that access the web service that provides data in XML format (see the C2C ICD). • Suggestion to develop an application that simply deposits the data every ‘x’ minutes onto a FTP server has been made. • Note: the www.fl511.com developed for Release 3.0 used C2C as the source for data. SunGuide 4.0 Functionality

12. FL-ATIS Database:Event, SAE Code and Location Tables Location Table FL-ATIS C2C Plugin Tables Event Table SAE Code Table SunGuide 4.0 Functionality

13. Data types to be discussed… • Event • “Classic” event • Weather • 3rd Party • Floodgates • DMS • CCTV • Travel time / traffic conditions (TSS data) SunGuide 4.0 Functionality

14. SunGuide Event Processing SunGuide 4.0 Functionality

15. Weather Processing SunGuide 4.0 Functionality

16. External Events Note: “nearby” distance is configurable SunGuide 4.0 Functionality

17. Restricting Publishing of Events • Operator can determine if an event is published to FL-ATIS: SunGuide 4.0 Functionality

18. Floodgate Processing • FDOT provided an Excel spreadsheet with all possible Floodgate combinations • Converted to XML file by FDOT • SunGuide uses XML file which allows a “soft” configuration – any changes to the file need to be SIMULTANEOUSLY coordinated across SG deployments and FL-ATIS SunGuide 4.0 Functionality

19. Floodgate - continued • Each floodgate: two audio recordings, two text entries • Each banner: two text entries SunGuide 4.0 Functionality

20. Floodgate - continued • Status: • Retrieved from the FL-ATIS C2C plugin database • Sent to C2C for distribution • Transmitted to each deployment “subscribed” for Floodgate status data • Selecting banner/message takes operator back to “entry” screen so edits can easily performed SunGuide 4.0 Functionality

21. DMS Processing SunGuide 4.0 Functionality

22. CCTV Processing SunGuide 4.0 Functionality

23. Travel Time / Traffic Conditions • TSS generated “link” data published as available (e.g. a lot of detectors implies a lot of C2C data) • TvT (Travel Time) data published at the rate of a “tunable” TvT parameter (e.g. C2C publishes as it arrives) SunGuide 4.0 Functionality

24. Test Data Sources • Two sources of data: • SwRI Test Data feed (FULL feed available since May 16) • XML Tester (a ‘controlled’ tool) SunGuide 4.0 Functionality

25. Scenarios / Use Cases(will be presented with the detailed FL-ATIS design) • Goal for use cases: • Follow data from “SunGuide” to “FL-ATIS” • Allow the flow of data to be visualized through the entire system (SG and FL-ATIS) • For each use case: • Rewritten to be consistent with SG operational paradigm • Provided with each (note each is available on SwRI’s test server – useful for end-to-end integration testing): • Use case (stimulus) • Appropriate SunGuide GUI (this can be expanded to see the details) • XML transmitted via C2C (as appropriate) • SAE codes and “SunGuide interpretation” (only used within SunGuide) SunGuide 4.0 Functionality

26. Questions? SunGuide 4.0 Functionality