SunGuide SM Software Development Project Status Meeting July 8, 2005 CDRL 1-8.3.19

SunGuideSunGuideSMSM Software Development Project Software Development Project

Status MeetingStatus MeetingJuly 8, 2005July 8, 2005

CDRL 1-8.3.19CDRL 1-8.3.19

July 8, 2005SunGuide Status Meeting 2

AgendaAgenda

Time Item Lead

8:30 – 8:35 Introductions Liang Hsia

8:35 – 8:40 License Update Liang Hsia

8:40 – 8:55 TMC and Software Deployment Schedule Updates Districts / Other Agencies

8:55 – 9:15 Project Status Report Steve Dellenback

9:15 – 9:30 Results of SunGuide Installation at D4 Dellenback / Steve Corbin

9:30 – 9:35 Status of ECO #1.1 Liang Hsia

9:35 – 9:45 Break

9:45 – 11:15 ECO #2 Discussion and scheduleIM through C2C communicationsTravel Time Support and MaintenanceEnhancements requested during R1.1 FATRoad Ranger SubsystemIncident Management Through Wireless DevicePerformance MeasuresTraffic SignalTag ReadersHAR- wave files

John Bonds /Liang Hsia /Steve Dellenback

11:15 – 11:50 Update Plans for District 6 Milestone Demonstration:Scope of demonstrationDevices availablePlan the pretest of ramp metering, (schedule, availability and scope)

John Bonds / Dellenback /Jesus Martinez /Arturo Espinosa

11:50 - 12:00 Closing remarks and adjourn Liang Hsia


Introductions


AgendaAgenda

Time Item Lead







9:35 – 9:45 Break







License UpdatesLicense Updates

SwRI / FDOT Sublicense– License executed on August 29, 2003 before the contract started.– License updated on September 5, 2003 covering distribution

source code to other Florida governmental entities.– TxDOT informed SwRI on January 22, 2004 that TransGuide

software was on “hold”.– License amended on April 12, 2004 (to support District 2 and

name change)– SwRI provided FDOT with draft language on September 10, 2004 to include other Florida government entities


License UpdatesLicense Updates

For a FDOT / TxDOT partnership to occur two things are needed:

– MOU and License:• FDOT provided TxDOT with comments and legal opinion on

March 2, 2004• TxDOT provided FDOT with draft MOU and License on March

16, 2004 • FDOT forwarded draft MOU & License to TxDOT on October

18, 2004• FDOT corresponded with TxDOT & SwRI in January 2005

– TxDOT Software License (solves TransGuide license issue)• TxDOT provided FDOT with a license on June 30, 2004

(included previous FDOT requests for content).• FDOT signed license on August 10, 2004.• TxDOT acknowledged the receiving of the FDOT signed

license on August 23, 2004.• TxDOT signed license on August 30, 2004 and sent to FDOT

on September 20, 2003.• FDOT Requested TransGuide software on October 4, 2004.• FDOT Received TransGuide software on October 19, 2004.


License Updates - continuedLicense Updates - continued

FDOT / WsDOT Term of Use (TOU):– WsDOT provided FDOT with standard TOU on February 11, 2004.– FDOT provided recommendation on to WsDOT on March 13, 2004.– FDOT provided comments to the WsDOT’s Office of General

Counsel’s August 21, 2004.– WsDOT began working on FDOT’s comments on August 26, 2004.– FDOT requested status on September 14, 2004, October 7, 2004

and November 5, 2004.– FDOT & WsDOT attorneys and project managers had

teleconference on November 30, 2004.

– New Option:• WsDOT would license to “Southwest Patents”• “Southwest Patents” would license to FDOT• This resolves the indemnification issue



FDOT / MDX Joint Program Agreement (JPA)

– FDOT provided MDX with preliminary JPA on December 3, 2003.

– MDX provided FDOT with draft final JPA on June 23, 2004.

– FDOT worked on Locally Funded Agreement and MDX JPA.

– FDOT forwarded updated JPA and sublicense to MDX on October 26, 2004

– FDOT developed a draft Software General and On-Site Support Agreement to address MDX’s software support concerns on February 11, 2005.

– FDOT forwarded the updated JPA to MDX on June 7, 2005.



SwRI / FDOT / Lee County Sublicense– Lee County provided FDOT with official letter for participation on

July 27, 2004– FDOT and SwRI started documentation preparation on July 30, 2004– SwRI provided FDOT with draft language on September 10, 2004– FDOT forwarded sublicense to Lee County on October 26, 2004

FDOT issued iFlorida Data Collection Process (DCP) notice to proceed on September 8, 2004.

Dynamap License: – System Planning Office and Office of Information Systems are

finalizing the license agreement on September 14, 2004.– Kevin Thibault approved the $130,000 GDT Procurement on October

19, 2004.– Statewide license effective on March 31, 2005.


License Updates - License Updates - Oracle Oracle continuedcontinued

Transportation Management Center Date Required OIS Licensed Processor Current License Duration

District 1 Ft. Myers RTMC Sun 12/31/06 2

District 1 Sarasota RTMC Sat 12/31/11

District 2 Jacksonville RTMC Sun 12/31/06 2 10/3/03 to 10/3/08

District 3 Pensacola RTMC Mon 12/31/07

District 3 Tallahassee RTMC Wed 12/31/08

District 4 Ft. Lauderdale RTMC Mon 1/31/05 2 10/3/03 to 10/3/08

District 4 West Palm RTMC Mon 12/31/12

District 5 Orlando RTMC Mon 12/31/07 4

District 6 Miami RTMC Thu 6/30/05 2 10/3/03 to 10/3/08

District 7 Tampa RTMC Sun 4/30/06 2 10/3/03 to 10/3/08

Lee County RTMC Sat 12/31/05

Miami-Dade Expressway RTMC Thu 6/30/05 2

Statewide TMC & Testing Lab Tue 5/31/05 2 10/3/03 to 10/3/08

Turnpike Pompano RTMC Mon 12/31/12

Turnpike Turkey Lake RTMC Mon 12/31/12


License Updates – Support AgreementLicense Updates – Support Agreement

Software general and on-site support requirements were discussed on December 7, 2004

Draft final Software General and On-Site Support Agreement has been forwarded to SwRI on February 11, 2005

SwRI returned comments to FDOT on April 20, 2005

Summary and updated Support document were distributed on July 1, 2005


AgendaAgenda

Time Item Lead







9:35 – 9:45 Break







Reports by Deployment and Reports by Deployment and Possible Integration SchedulePossible Integration Schedule

District 4

District 6

MDX

District 7

District 1

Lee County

District 2

District 5

District 3

Turnpike Enterprise


SunGuideSunGuideSMSM Software Schedule Software Schedule

August 2005: Ramp Meter Test and Milestone Demonstration

TBD: Lee County Bridge Incident Management System Requirements Meeting

August 2005: Release 2 Acceptance Test

September 2005: Release 2 deployment depending on test results


District 4 ScheduleDistrict 4 Schedule

February 21, 2005: Video wall RFP, completion 120 days after NTP

April 22, 2005: 7 CCTV available

June 13-17, 2005: SunGuideSM software deployed at D4 TMC

August 12, 2005: 45 CCTV available

October 2005: Complete I/95/I595 Video Monitor System


District 6 RTMCDistrict 6 RTMC

August 2005: Ramp metering subsystem testing and SunGuideSM Software Milestone Demonstration planned

September 2005: SunGuideSM software deployment

November 9, 2005: I-95 Package B project completion

1st Quarter 2006: Ramp Meters operations


MDX ScheduleMDX Schedule

April 7, 2003 MDX sent letter to ITS Office aboutparticipating in SunGuideSM Project

April 25, 2003 FDOT Responded, Welcoming MDX’s

participation

December 3, 2003 FDOT provided MDX with a draft Joint Program Agreement

September 2005 SunGuideSM Software Release 2 deployment at MDX

October 2005 MDX TMC Operational



June 2006 Building Construction Finish3rd Quarter 2006 SunGuideSunGuideSM Software Deployment



FY 2004FY 2004 I-95 N ITS ImprovementI-95 N ITS ImprovementFY 2006FY 2006 SunGuideSunGuideSM Deployment (Tentative)Deployment (Tentative)



FY 2004FY 2004 Orlando RTMC retrofit and upgrade Orlando RTMC retrofit and upgradeSeptember 8, 2004 -September 8, 2004 - iFlorida Data Collection Process iFlorida Data Collection ProcessDecember 2005 December 2005 FY 2004-2005FY 2004-2005 iFlorida C2C between Districts 2 and 5 iFlorida C2C between Districts 2 and 5


Turnpike RTMCTurnpike RTMC

SunNavSM Development

April-December 2004: SunNav 1.2 Release • NTCIP Drivers for DMS• DMS GUI Field Sorting

November 2005 SunNav 2.0 (Final Completion)• Web-based XML Release• NTCIP Camera Driver• Replication of Data• Incident Management Dynamic Expansion• Response Plan Upgrades

August 2005 SunGuideSM - Statewide TMC Software• Center-to-Center Interface Module


District 1District 1

May 2005 I-75 Safety Barrier System upgrade December 2006 SunGuideSM Deployment at Ft. Myers RTMC

FY 2011 (2005) Sarasota RTMC


District 3District 3

FY 2007 Pensacola RTMC FY 2007 Pensacola RTMC FY 2008 Tallahassee RTMCFY 2008 Tallahassee RTMC


Lee County Bridge Incident Lee County Bridge Incident ManagementManagement

July 27, 2004 Lee County Public Works sent letter to FDOT

indicating Lee County’s participation in

SunGuide Software Project

TBD SunGuide Software deployment


C2C ScheduleC2C Schedule

February 16, 2004 SunGuideSM and C2C Project Team completed Interface Control

Document(ICD)

February 20, 2004 SunGuideSM and C2C Project Coordination Teleconference

March 9, 2004 SunGuideSM & C2C Project Coordination Meeting

October 2005 C2C deployment among Districts 4, 6,and Turnpike


AgendaAgenda

Time Item Lead







9:35 – 9:45 Break







Project Web SiteProject Web Site

http://sunguide.datasys.swri.edu


Release-Oriented Release-Oriented Development ApproachDevelopment Approach


Status of Release 1.1 Status of Release 1.1 Development ActivitiesDevelopment Activities

Development of Release 1.1 requirements complete

Integration testing complete

Factory Acceptance Testing (FAT) complete

Training material:– Classes prepared (and already presented):

• Operator/User Interface Training Course (twice)• System Administration/Deployment Training Course

– Future course:• Software Design and Maintenance Training Course


Status of Release 2 ActivitiesStatus of Release 2 Activities

Ramp Metering:– Development complete:

• Subsystem• Drivers:

– TSS driver complete– RM driver complete

• GUI

– Undergoing integration testing in San Antonio

– Issues identified June 28, 2005 by Les Jacobson (being addressed by SwRI developers)


Status of Release 2 Activities: Status of Release 2 Activities: continuedcontinued

Emergency Evacuation:

– Design initiated

– Development initiated

– SwRI has determined that a number of existing web sites provide what was asked for in the SunGuide requirements

– SwRI has been provided with “Evacuation Zone” shape files

– SwRI is progressing along developing a web site with links to available web site

– Question:

• The Emergency Evacuation requirements (as provided by FDOT) specify a number of areas within SunGuideSM that shall provide user input (SwRI has planned to do these with manual data entry screens) – would FDOT prefer to use the “available” web sites from other agencies and NOT implement the user entry screens? If the answer to this is yes, a requirements modification will need to be made.



Data Archive– Design Completed– Development Completed– Undergoing integration testing in San Antonio

Web Server– Development complete


Status of Release 2 Activities: continuedStatus of Release 2 Activities: continued

HAR– Design complete– Development in process– Note: SwRI has procured a

HAR system

Center-to-Center– Design complete– Development in process– Note: FDOT may be

providing an alternative ConOps which will impact the current development.



Trailblazer– Driver complete– Integrating with GUI– Simulator to aid testing

Safety Barrier– ICD Complete– Design initiated– Simulator to aid testing



RWIS– Design– Development complete

Inventory and Maintenance– Design initiated

Optional Service:– iFlorida Data Collection Process (DCP)


Deliverable StatusDeliverable Status

SwRI waiting for FDOT comments:– None critical

Future documents to be provided by SwRI:– Updated testing documents– Updated design documents

All documents delivered to FDOT

are available on the project web site.

http://SunGuide.datasys.swri.edu


Cost Status (as of 6/10/05)Cost Status (as of 6/10/05)

Release 1:– Allocated: $4,335,554 (includes ECO 1.1: $484,775)– Spent: $4,259,002

Release 2:– Allocated: $2,651,361– Spent: $1,505,321

Deployments:– Allocated: $397,292– Spent: $13,694 (as 7/5/05: $46,626)

Support - on-site support and FDOT directed support (thru 6/2012):– Allocated: $1,175,558– Spent: $75,656


Spending Curves Spending Curves (includes projected funds from ECO 1.1)(includes projected funds from ECO 1.1)

SunGuide Projected Spending

$0

$1,000,000

$2,000,000

$3,000,000

$4,000,000

$5,000,000

$6,000,000

$7,000,000

$8,000,000

Oct-0

3

Dec-0

3

Feb-0

4

Apr-0

4

Jun-

04

Aug-0

4

Oct-0

4

Dec-0

4

Feb-0

5

Apr-0

5

Jun-

05

Aug-0

5

Oct-0

5

Dec-0

5

Feb-0

6

Apr-0

6

Jun-

06

Projected

Actual


Schedule StatusSchedule Status

Current areas of concern:– Documents:

• None– Software:

• Ramp Meter is significantly over-budget– Contractual:

• ECO 1.1 is in the process of being finalized – Release 2.0:

• FAT• Deployment

To be scheduled:– Milestone Demonstration– Ramp Metering testing– District 6 deployment


Schedule Status - continuedSchedule Status - continuedCurrent Reporting PeriodCurrent Reporting Period


Events to Be ScheduledEvents to Be Scheduled

Future status meetings that need to be confirmed:– August 2005: SwRI proposes week of Aug 8th or Aug 22nd – September 2005: SwRI proposes week of Sep 19th

Testing:– Release 2 FAT

Milestone Demonstrations:– Milestone Demo #2 (choose one of the following):

• D6 Integrated DMS and CCTV operation to be demonstrated

• D6 Ramp Metering demonstration– Milestone Demo #3: D4, D6 and MDX Functionality of C2C,

CCTV and DMS to be demonstrated


AgendaAgenda

Time Item Lead







9:35 – 9:45 Break







District 4 DeploymentDistrict 4 Deployment

Occurred week of June 13, 2004 SunGuideSM products installed:

– Administrative Editor – Executive Handler – Status Logger – Data Bus – GUI / Map (GUI)– Closed Circuit Television (CCTV)– Dynamic Message Sign (DMS) – Video Switching (VS)– Video Wall (VW)– Transportation Sensor Subsystem (TSS)– Incident Management (IM)


District 4 Deployment: District 4 Deployment: SwRI’s PerspectiveSwRI’s Perspective

Deployment occurred Monday (1:00) through Friday (11:00) with the deployment team working days and evenings

Issues that arose (that were resolved but took a lot of time):– First time SunGuideSM had ever been installed tested

with Oracle Fail Safe and Microsoft Cluster– Configuration of Moxa devices caused data

transmission problems with TSS Detectors and DMS– Configuration of VBrick encoders being used as “port

servers”

At the end of the week, the installation was successful

All subsystems worked as designed and tested during the FAT in the SwRI labs

Operator and Administrator training conducted


District 4 Deployment: District 4 Deployment: FDOT’s PerspectiveFDOT’s Perspective

District 4 comments about deployment?


AgendaAgenda

Time Item Lead







9:35 – 9:45 Break







ECO 1.1 UpdateECO 1.1 Update

Jan 13 New requirements identified

Mar 15 CMB approved new requirements

Apr 27 ECO DRAFT sent to SwRI

Apr 28 SwRI returned ECP with comments


AgendaAgenda

Time Item Lead







9:35 – 9:45 Break







AgendaAgenda

Time Item Lead







9:35 – 9:45 Break







Possible Future EnhancementsPossible Future Enhancements

Recently Identified by FDOT:– IM through C2C communications– Travel Time – Support and Maintenance– Enhancements requested during R1.1 FAT– Road Ranger Subsystem– Incident Management Through Wireless Device– Performance Measures– Traffic Signal– Tag Readers– HAR- wave files– D4 Deployment issues

Purpose of today’s discussion (concept development):– Focus on desired functionality– SwRI to generate estimates based on what is discussed


IM Through C2C CommunicationsIM Through C2C Communications

FDOT Central Office has authored a C2C ConOps document that describes an approach to C2C between centers

Primary differences from current SunGuideSM include:– Current SunGuideSM places a message on the MAS

queues if the user has appropriate credentials to make a DMS request

– SunGuideSM provides no coordination of incidents across SunGuideSM deployments

FDOT thoughts on Central Office C2C concept?


Travel TimeTravel Time

SunGuideSM has a module that computes and publishes Travel Times, it does this by:– Configuring “travel time links” in the SunGuideSM Admin

Editor– TvT Subsystem computes and published travel time– Only current “user” of the Travel Time data is the Web

Server application

SwRI recommends:– Develop a “Travel Time Message Template” that is editable

by the SunGuideSM Administrator– Create a graphical editor to specify Travel Time links– Create a “DMS TvT Subsystem” to display tavel times– Messages will be queued through MAS (i.e. priority based)

FDOT thoughts?


Support and MaintenanceSupport and Maintenance

Anecdotal support costs:– Lifecycle costs: 20% of software lifecycle cost is development; the

other 80% is deployment, debugging, enhancements, general support, etc.

– Maintenance Contracts: support contracts for commercial software typically in the 10% to 20% of the purchase cost per year for support; this typically only provides telephone support and product updates (that are made on the vendor’s timeframe)

“Best Guess” as to what will happen with the “support funds”:– Deployment – 5%– Troubleshooting operational issues – 15%– Bug fixing – 20%– Enhancement activity – 55%– Education – 5%


Support and Maintenance: Support and Maintenance: continuedcontinued

During the ITN negotiations, to meet the established budget (while minimizing requirements changes) the support funds were reduced:

SwRI has been asked to provide– 24x7 coverage– Response times vary based on severity

SwRI provided FDOT with a document (proposal) in April 2005


Support and Maintenance: Support and Maintenance: continuedcontinued

The following are the proposed costs:

Would require an additional $1,585,413 through June 2012


Enhancements requested Enhancements requested during R1.1 FATduring R1.1 FAT

“Find on Map” button needs to have a flashing indicator or notification for assigned operator (D6)

Limit DMS messages to 2 phases and a specific character count (D6)

“Date Picker” rather than drop down lists for date fields (D6) Prefer to use “mile marker” rather than “cross street” in

recommended response plans (D6) Add “close” button to windows (rather than the Windows “x”)

(MDX) Highlight an individual sign from a response plan on the map

(MDX) Restrict field lengths in the editor (MDX)

Other items were listed as “enhancements” but they were actually SunGuideSM configuration activities


Road Ranger SubsystemRoad Ranger Subsystem

SwRI questions:

– Is this a “Road Ranger” activity tracking piece of software?

– Is this to interact with SunGuideSM :

• Dynamically (via wireless)?

• End of shift (via a dock)?

FDOT thoughts?


Incident Management Incident Management Through Wireless DeviceThrough Wireless Device

SwRI recommendations:– Browser-based client for maximum flexibility:

• Accessed from wireless device or any other external browser• Security managed by IIS and Windows permissions• Server located in DMZ with small hole for SG access

– Web Application connects to Data Bus and/or database:• Special portal for wireless (small display) clients• List-based incident display• Optional map-based incident display (like SG Web Server)

– Incident data entry forms optimized for wireless (small display) clients:

• Minimum number of fields• Use combo boxes and other controls to minimize typing• Provide Lat/Lon data entry• Optional response plan generation

FDOT thoughts?


Performance MeasuresPerformance Measures

SunGuideSM has a variety of data to determine performance measures

SwRI recommendation:– FDOT provide example reports or documents of

performance measures– SwRI will evaluate what SunGuideSM currently can

support– Estimate as to effort to modify SunGuideSM can be

generated

FDOT thoughts?


Traffic SignalsTraffic Signals

FDOT has expressed the desire to control Traffic Signals from SunGuideSM

SwRI questions:

– Is the TxDOT C2C capability sufficient (i.e. the ability to query pre-existing plans and change to one of these pre-existing)

– Will any upcoming SunGuideSM implementation have access to traffic signals (for control)

FDOT thoughts?


Tag ReadersTag Readers

FDOT has expressed the interest in utilizing “toll tags” to capture measured travel times as opposed to the current “computed” travel times generated by SunGuideSM

SwRI questions:– What penetration of toll tags exist in the metro

areas?– Does FDOT have access to toll tag data:

• Directly from readers• Via C2C (e.g. OOCEA in Orlando)

FDOT thoughts?


HAR- Wav FilesHAR- Wav Files

FDOT has expressed the desire to generate Spanish HAR messages

SwRI questions:

– Are Spanish messages a functional requirement?

FDOT thoughts?


D4 Deployment IssuesD4 Deployment Issues

Limit operator creation of messages :

– Issue: Limit operator's ability to edit/create DMS messages (i.e. only allow them to pull from a library or use IM recommended messages

– SwRI Proposed Requirements:• GUI: The system shall have a permission field (per user) for typing

a manual message for a DMS.• GUI: The system shall have a permission field (per user) for typing

a manual message for a HAR.• GUI: The system shall have a permission field (per user) for

editing the message in a device queue.• GUI: The system shall have a permission field (per user) for

editing a generated incident message.

– Estimated cost: $3,598

FDOT thoughts?


D4 Deployment Issues: continuedD4 Deployment Issues: continued

Single phase DMS messages only:

– Issue: Limit IM recommended messages to fit on a single phase.

Note: this involves using abbreviations and SwRI can think of some situations (although unlikely) where there will be no way to create a single phase message - in this case someone with DMS edit/create capability would need to hand edit

– SwRI Proposed Requirements:• IM: The system shall have a configuration setting that specifies

only one phase messages will be generated.• IM: The system shall have a prioritized list of words and

replacements. • Admin: The system shall have an editor to add, modify and delete

words and their replacement words.

– Estimated cost: $17,514

FDOT thoughts?


AgendaAgenda

Time Item Lead







9:35 – 9:45 Break







D6 Capabilities July/AugustD6 Capabilities July/August

August I-95 Package B completion January 2006 – March 2006 Ramp Meters installed (?) Equipment available

– DMS – • Dambach Vantage : Vario F 318 (12 cpl 2 rows)• Vultron Digi DOT (3 cpl 3 rows)

– CCTV• Cohu Model 3525-1000-Pend• Pelco Model DD53CBW• Vicon Model VFT-23 and Model VC2600-DSP• Hitachi Model KP-D581• Sanyo Model VDC2974

– Barco/Argus Video Wall with Apollo software– Traffic Detectors

• Belden loops• VIDS Odetics

HAR? RWIS?


Advantages of a MD at D6Advantages of a MD at D6

Variety of different devicesVariety of different devices– 5 CCTV types

– 3 DMS types

– 2 types of traffic sensors

– Possible ramp meter device field test New devices available not tested in D4 Connectivity with MDX and D4

– Preliminary to C2C MD


Time FrameTime Frame

Ideal : August 2005Ideal : August 2005

Combine C2C with D5 MD?

Too ambitious?

Too soon before R2 delivery (October)?

DiscussionDiscussion

Action itemsAction items


AgendaAgenda

Time Item Lead







9:35 – 9:45 Break




