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

2. 2 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 2 Agenda TimeItemLead 8:00 – 8:15 Introductions and Opening Remarks Tillander 8:15 – 8:30High Level Overview – meeting objectives Heller 8:30 – 9:45 Various topics: C2C XML Schemas Weather Alerts External Events Data To Be Fused Data Fusion and FL-ATIS Event Management Changes Heller / Brisco 9:45 – 10:00 Break 10:00 – 10:45Various topics: Location Codes SAE Codes Floodgate Messages Reports Heller / Brisco 10:45 – 11:00Action Item Review Heller / Brisco 11:00 – 11:15 Deployments / Schedule Heller / Brisco 11:15 – 11:30 Open Discussion All

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

4. 4 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 4 Agenda TimeItemLead 8:00 – 8:15 Introductions and Opening Remarks Tillander 8:15 – 8:30High Level Overview – meeting objectives Heller 8:30 – 9:45 Various topics: C2C XML Schemas Weather Alerts External Events Data To Be Fused Data Fusion and FL-ATIS Event Management Changes Heller / Brisco 9:45 – 10:00 Break 10:00 – 10:45Various topics: Location Codes SAE Codes Floodgate Messages Reports Heller / Brisco 10:45 – 11:00Action Item Review Heller / Brisco 11:00 – 11:15 Deployments / Schedule Heller / Brisco 11:15 – 11:30 Open Discussion All

5. 5 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 5 Meeting Objectives Requirements and Design: –Review high level design –Provide clarification to SwRIs initial design interpretation –Present revised prototype screens / reports Not an objective: –Revise requirements

6. 6 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 6 Release 4.0 Development Activities

7. 7 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 7 Agenda TimeItemLead 8:00 – 8:15 Introductions and Opening Remarks Tillander 8:15 – 8:30High Level Overview – meeting objectives Heller 8:30 – 9:45 Various topics: C2C XML Schemas Weather Alerts External Events Data To Be Fused Data Fusion and FL-ATIS Event Management Changes Heller / Brisco 9:45 – 10:00 Break 10:00 – 10:45Various topics: Location Codes SAE Codes Floodgate Messages Reports Heller / Brisco 10:45 – 11:00Action Item Review Heller / Brisco 11:00 – 11:15 Deployments / Schedule Heller / Brisco 11:15 – 11:30 Open Discussion All

8. 8 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 8 C2C 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

9. 9 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 9 Weather 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

10. 10 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 10 External 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

11. 11 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 11 Data 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

12. 12 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 12 Data 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

13. 13 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 13 Event 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

14. 14 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 14 EM Changes (contd)

15. 15 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 15 EM Changes (contd)

16. 16 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 16 Agenda TimeItemLead 8:00 – 8:15 Introductions and Opening Remarks Tillander 8:15 – 8:30High Level Overview – meeting objectives Heller 8:30 – 9:45 Various topics: C2C XML Schemas Weather Alerts External Events Data To Be Fused Data Fusion and FL-ATIS Event Management Changes Heller / Brisco 9:45 – 10:00 Break 10:00 – 10:45Various topics: Location Codes SAE Codes Floodgate Messages Reports Heller / Brisco 10:45 – 11:00Action Item Review Heller / Brisco 11:00 – 11:15 Deployments / Schedule Heller / Brisco 11:15 – 11:30 Open Discussion All

17. 17 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 17 Agenda TimeItemLead 8:00 – 8:15 Introductions and Opening Remarks Tillander 8:15 – 8:30High Level Overview – meeting objectives Heller 8:30 – 9:45 Various topics: C2C XML Schemas Weather Alerts External Events Data To Be Fused Data Fusion and FL-ATIS Event Management Changes Heller / Brisco 9:45 – 10:00 Break 10:00 – 10:45Various topics: Location Codes SAE Codes Floodgate Messages Reports Heller / Brisco 10:45 – 11:00Action Item Review Heller / Brisco 11:00 – 11:15 Deployments / Schedule Heller / Brisco 11:15 – 11:30 Open Discussion All

18. 18 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 18 Location 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. 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

20. 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. 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? Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review

22. 22 EM Event Codes: Location and Lane Blockage Issue: some actual (real) lane configurations may not be captured above Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review

23. 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. Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review

24. 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): Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review

25. 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. Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review

26. 26 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 26 Floodgate Messages Add 2 nd 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

27. 27 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 27 Floodgate Messages (contd) Alternate language selection scheme

28. 28 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 28 Reports Adding Crystal Reports 11 run-time to installer is in progress…

29. 29 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 29 Agenda TimeItemLead 8:00 – 8:15 Introductions and Opening Remarks Tillander 8:15 – 8:30High Level Overview – meeting objectives Heller 8:30 – 9:45 Various topics: C2C XML Schemas Weather Alerts External Events Data To Be Fused Data Fusion and FL-ATIS Event Management Changes Heller / Brisco 9:45 – 10:00 Break 10:00 – 10:45Various topics: Location Codes SAE Codes Floodgate Messages Reports Heller / Brisco 10:45 – 11:00Action Item Review Heller / Brisco 11:00 – 11:15 Deployments / Schedule Heller / Brisco 11:15 – 11:30 Open Discussion All

30. 30 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 30 Action Item Summary NumberResponsible Text Resolution 190SwRI SwRI to provide the C2C XML schema. Closed: Provided on 12/12/07 191SwRI 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 192SwRI SwRI to provide justification of $6,700 line item in cost estimate if not to implement FHP interface. Closed: Provided on 11/14/07 193SwRI SwRI to provide analysis and impact of adding the FHP CAD feed to SunGuide. Closed: Has been provided to FDOT 194SwRI Determine an approach to providing Floodgate information to Logictree/IBI. Closed: FDOT has provided requirements to SwRI 195FDOT (PBS&J) John Bonds to distribute the SAE list to the districts. In progress: Proposed solution is being reviewed 196SwRI 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

31. 31 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 31 Action Item Summary - continued NumberResponsible Text Resolution 197FDOT (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 198FDOT (PBS&J) PBS&J took action to pare down the SAE code table with help from districts. Closed: Provided to SwRI 199SwRI SwRI to coordinate with Logic Tree / IBI Group regarding floodgate messages. Closed: Requirements provided and implementation in process 200SwRI Add other deployments: MDX, Palm Beach County, Turnpike Closed: Added to schedule 201SwRI SwRI will provide some options to relieve operator work load for selecting SAE codes. Closed: Current approach is to automatically select

32. 32 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 32 Agenda TimeItemLead 8:00 – 8:15 Introductions and Opening Remarks Tillander 8:15 – 8:30High Level Overview – meeting objectives Heller 8:30 – 9:45 Various topics: C2C XML Schemas Weather Alerts External Events Data To Be Fused Data Fusion and FL-ATIS Event Management Changes Heller / Brisco 9:45 – 10:00 Break 10:00 – 10:45Various topics: Location Codes SAE Codes Floodgate Messages Reports Heller / Brisco 10:45 – 11:00Action Item Review Heller / Brisco 11:00 – 11:15 Deployments / Schedule Heller / Brisco 11:15 – 11:30 Open Discussion All

33. 33 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 33 Deployments / 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

34. 34 Jan 8, 2008R4.0 Data Fusion Design Follow-up Design Review 34 Agenda TimeItemLead 8:00 – 8:15 Introductions and Opening Remarks Tillander 8:15 – 8:30High Level Overview – meeting objectives Heller 8:30 – 9:45 Various topics: C2C XML Schemas Weather Alerts External Events Data To Be Fused Data Fusion and FL-ATIS Event Management Changes Heller / Brisco 9:45 – 10:00 Break 10:00 – 10:45Various topics: Location Codes SAE Codes Floodgate Messages Reports Heller / Brisco 10:45 – 11:00Action Item Review Heller / Brisco 11:00 – 11:15 Deployments / Schedule Heller / Brisco 11:15 – 11:30 Open Discussion All

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