SunGuide TM Software Development Project Release 4.0 Data Fusion Follow-Up DR Jan. 8, 2008 Updated: Jan 4, 2008, 11:00 am

SunGuideSunGuideTMTM Software Development Project Software Development Project

Release 4.0 Data Fusion Follow-Up DR Release 4.0 Data Fusion Follow-Up DR Jan. 8, 2008Jan. 8, 2008

Updated: Jan 4, 2008, 11:00 am

2Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 2

AgendaAgenda

Time Item Lead

8:00 – 8:15 Introductions and Opening Remarks Tillander

8:15 – 8:30 High Level Overview – meeting objectives Heller

8:30 – 9:45 Various topics:C2C XML SchemasWeather AlertsExternal EventsData To Be FusedData Fusion and FL-ATISEvent Management Changes

Heller / Brisco

9:45 – 10:00 Break

10:00 – 10:45 Various topics:Location CodesSAE CodesFloodgate MessagesReports

Heller / Brisco

10:45 – 11:00 Action Item Review Heller / Brisco

11:00 – 11:15 Deployments / Schedule Heller / Brisco

11:15 – 11:30 Open Discussion All


Introductions


AgendaAgenda

Time Item Lead




Heller / Brisco

9:45 – 10:00 Break


Heller / Brisco





Meeting ObjectivesMeeting Objectives

Requirements and Design:

– Review high level design

– Provide clarification to SwRI’s initial design interpretation

– Present revised prototype screens / reports

Not an objective:

– Revise requirements


Release 4.0 Development Release 4.0 Development ActivitiesActivities


AgendaAgenda

Time Item Lead




Heller / Brisco

9:45 – 10:00 Break


Heller / Brisco





C2C XML SchemaC2C XML Schema

Draft schema delivered in December New Travel Time data type w/ Link inventory New Floodgate data type

– Second language support being added New Traveler Event data type

– Location and Roadway inventory data being added

– Actual Lat/Lon instead of/in addition to Location ID

– Note: Traveler Event needs to be a new event type because DF005G requires a unique icon for Traveler Events on the map.

Add Offset in miles to Incident, Closure, and Traveler Event data types


Weather AlertsWeather Alerts

SwRI ready to evaluate Meteorlogix alert data

Issues:

– SwRI needs active web service to obtain sample data

– Meteorlogix needs coverage instructions and geodata for covered roads and areas


External EventsExternal Events

SwRI ready to accept external event data from C2C feed

SwRI can develop new “plug-in” to publish FHP data, or

SwRI can develop new SunGuide module to retrieve FHP data from FHP web service


Data To Be FusedData To Be Fused

Weather Alerts

– Fused to EM Location Code

– Location Code checked against existing Events

– New Traveler Event presented to operator

External Event Data (e.g. FHP CAD)

– Fused to EM Location Code

– Location Code checked against existing Events

– Event conflict resolution dialog presented to operator


Data Fusion & FL-ATISData Fusion & FL-ATIS

Extended telecon and e-mail interaction

Resolved:

– EM subsystem, GUI, and Admin changes

– Location code usage

– SAE code usage

– Floodgate messages and GUI changes

Unresolved:

– Weather alerts


Event Management ChangesEvent Management Changes

Add new Alternate Route Admin dialog Add City and Metro Area selections to EM Location

Admin dialog Update EM to include original lat/lon values in

schema Update EM to use configurable “snap-to” radius for

Location code selection Add Traveler Info event type Add “Publish to ATIS” control Populate existing Alternate Route ID dropdowns

with values from new Alternate Route Admin dialog

Note: Prototype EM GUI and Alternate Route dialog on following slides


EM Changes (cont’d)EM Changes (cont’d)


EM Changes (cont’d)EM Changes (cont’d)


AgendaAgenda

Time Item Lead




Heller / Brisco

9:45 – 10:00 Break


Heller / Brisco





AgendaAgenda

Time Item Lead




Heller / Brisco

9:45 – 10:00 Break


Heller / Brisco





Location CodesLocation Codes

SunGuide C2C will publish Location and Roadway inventory data based on EM Location and Roadway data

Data Fusion will use EM Location code if available, and newly available original lat/lon values

19

SAE Code Proposed Solution

Requirements directed a GUI based solution where “drop down” were going to be provided to allow operators to select SAE codes.

During design discussions:– It was concluded that this was requesting too much of an

operator (they have enough to do)– FDOT wanted a “standard” approach to which SAE codes were

selected

Resolution:– SunGuide will use “EM Event Codes” (a combination of SAE

codes and FDOT codes) and not claim to adhere to a standard– A EM Event Code “translation” table will be built and event

“attributes” will be automatically mapped– SunGuide will distribute EM Event Codes codes via C2C– EM Event Codes will be “transparent” to SunGuide operators

Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review

Implementation of EM Event Codes

A list of “requested” codes was generated by PBS&J (and distributed to the Districts)

District 4 provided additional requests The following slides show the results, the column

“SunGuide Support” is important to review because this could impact cost and schedule (the original approach of “drop downs” was very simple):– Easy translation: can be derived from SG data– EM Event type: data available in SG– Event attribute: data available in SG– Hard translation: algorithm to derive from SG data will

need to be created– Set Event type and lane flags: data available in SG– Not found: no data available to support

21

EM Event Codes:Translation Table for “Event Type”

Issue: “event type” can be edited by the System Administrator – should this edit screen be removed so FDOT can have the SAME event types across all SunGuide deployments?


22

EM Event Codes:Location and Lane Blockage

Issue: some “actual” (real) lane configurations may not be captured above


23

EM Event Codes:Various fields

Note: “weather conditions” can be edited by the System Administrator – this edit screen be removed by FDOT direction so FDOT can have the SAME weather conditions across all SunGuide deployments.


24

EM Event Codes:Proposed Additions (beyond the SAE standards)

Theses codes are were requested by District 4

Codes that will not be included (no “travel time” related codes will be provided):


25

SAE Codes: Issues to Resolve

Does FDOT wish to “rename”?

Codes will only be included if a “mapping” can be identified between SunGuide and the codes. Some “compaction” of codes may be implemented by using “qualifiers” (e.g. “three” “center lanes blocked”)

Are the lists provided by PBS&J acceptable?– Final tables needed by end of January– Should Admin editor screens be removed?

Should the D4 proposed additions be included?

Once all of the above issues are resolved SwRI will determine the impact to the project.



Floodgate MessagesFloodgate Messages

Add 2nd language support to GUI and subsystem

Add new GUI fields in support of FL-ATIS

Add Floodgate support to SunGuide plug-in and C2C

SunGuide interaction with 511 remains unchanged


Floodgate Messages (cont’d)Floodgate Messages (cont’d)

Alternate language selection scheme


ReportsReports

Adding Crystal Reports 11 run-time to installer is in progress…


AgendaAgenda

Time Item Lead




Heller / Brisco

9:45 – 10:00 Break


Heller / Brisco





Action Item SummaryAction Item Summary

Number Responsible Text Resolution

190 SwRISwRI to provide the C2C XML schema. Closed:

Provided on 12/12/07

191 SwRI

SwRI will provide analysis of impact to implement a Meteorlogix interface instead of a NWS interface.

Open: waiting on data from IBI/DTN

before the impact can be completed

192 SwRISwRI to provide justification of $6,700 line item in cost estimate if not to

implement FHP interface.Closed:

Provided on 11/14/07

193 SwRISwRI to provide analysis and impact of adding the FHP CAD feed to

SunGuide.Closed:

Has been provided to FDOT

194 SwRI

Determine an approach to providing Floodgate information to Logictree/IBI.

Closed:FDOT has provided

requirements to SwRI

195 FDOT (PBS&J)John Bonds to distribute the SAE list to the districts. In progress:

Proposed solution is being reviewed

196 SwRI

SwRI needs to provide a draft GUI layout for review by FDOT operations personnel with explanation of what fields are and how they will work. Needs to include: SAE coding, publishing to IDS, alternate routing, etc.

Included in Follow-up Design Review


Action Item Summary - continuedAction Item Summary - continued

Number Responsible Text Resolution

197 FDOT (PBS&J)Erik Gaarder and Gene Glotzbach to ask Logic Tree / IBI Group of impact

switching to J2540-2.Closed:

Change will not be made

198 FDOT (PBS&J)PBS&J took action to pare down the SAE code table with help from

districts.Closed:

Provided to SwRI

199 SwRI

SwRI to coordinate with Logic Tree / IBI Group regarding floodgate messages.

Closed:Requirements provided

and implementation in

process

200 SwRIAdd other deployments: MDX, Palm Beach County, Turnpike Closed:

Added to schedule

201 SwRI

SwRI will provide some options to relieve operator work load for selecting SAE codes.

Closed:Current approach is to

automatically select


AgendaAgenda

Time Item Lead




Heller / Brisco

9:45 – 10:00 Break


Heller / Brisco





Deployments / ScheduleDeployments / Schedule

Current high-level schedule:– Development to complete late March 2008– Integration complete by April 4, 2008– FAT the week of April 7, 2008– IV&V the week of May 5, 2008– Deployments starting week of May 12, 2008 (specific order will need to

be verified by FDOT – 3 day installations might cover 2 deployments, assume that SunGuide is already installed)• D2 (2 days)• D3 (2 days)• D4 (3 days)• D5 (3 days)• D6 (2 days)• D7 (2 days)• TERL (3 days)

Based on the urgency of Release 3.1 (I-95 Express Lanes) the overall development schedule will be pushed 6 to 8 weeks


AgendaAgenda

Time Item Lead




Heller / Brisco

9:45 – 10:00 Break


Heller / Brisco





Discussion ?

Documents

SunGuide TM Software Development Project Release 4.0 Data Fusion Follow-Up DR Jan. 8, 2008 Updated: Jan 4, 2008, 11:00 am