sunguide tm 4.0 functionality data fusion: how data is managed june 24, 2008

SunGuideSunGuideTMTM 4.0 Functionality 4.0 FunctionalityData Fusion: How Data is ManagedData Fusion: How Data is Managed

June 24, 2008June 24, 2008

Purpose of this presentation…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

June 24, 2008SunGuide 4.0 Functionality 2


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


Florida Statewide 511 System ConceptFlorida Statewide 511 System ConceptFrom FDOT Data Fusion Requirements DocumentFrom FDOT Data Fusion Requirements Document


FLATIS Functional SubsystemsFLATIS Functional SubsystemsFrom FDOT Data Fusion Requirements DocumentFrom FDOT Data Fusion Requirements Document

DFS provides data to IDS via C2C

SunGuide data and other local and district sources


Release 4.0 and FL-ATIS Release 4.0 and FL-ATIS ResponsibilitiesResponsibilities

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


C2C Infrastructure Concept:C2C Infrastructure Concept:Deploying a C2C “Cloud”Deploying a C2C “Cloud”


TMDD Network ModelTMDD Network Model(TMDD = Traffic Management Data Dictionary)(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

How SunGuide Data gets to How SunGuide Data gets to FL-ATIS…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


R4.0 Conceptual Data FlowR4.0 Conceptual Data Flow


Providing Data to Other Providing Data to Other “Consumers” (3“Consumers” (3rdrd Parties) 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.


FL-ATIS Database:FL-ATIS Database:Event, SAE Code and Location TablesEvent, SAE Code and Location Tables


SAE Code Table

Location Table

Event Table

FL-ATIS C2C Plugin Tables

Data types to be discussed…Data types to be discussed…

Event

– “Classic” event

– Weather

– 3rd Party Floodgates DMS CCTV Travel time / traffic conditions (TSS data)


SunGuide Event ProcessingSunGuide Event Processing


Weather ProcessingWeather Processing


External EventsExternal Events


Note: “nearby” distance is configurable

Restricting Publishing of EventsRestricting Publishing of Events

Operator can determine if an event is published to FL-ATIS:


Floodgate ProcessingFloodgate 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

Floodgate - continuedFloodgate - continued

Each floodgate: two audio recordings, two text entries Each banner: two text entries


Floodgate - continuedFloodgate - 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


DMS ProcessingDMS Processing


CCTV ProcessingCCTV Processing


Travel Time / Traffic ConditionsTravel 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)


Test Data SourcesTest Data Sources

Two sources of data:– SwRI Test Data feed (FULL feed available since May 16)

– XML Tester (a ‘controlled’ tool)


Scenarios / Use CasesScenarios / Use Cases(will be presented with the detailed FL-ATIS design)(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)



Questions?

sunguide tm 4.0 functionality data fusion: how data is managed june 24, 2008

Documents

functionalityhow sunguide

sunguide updates data

sunguide center

method sunguide

data feed

c2csunguide data

functionalityproviding

underlying data model