SunGuide SM Software Development Project Status Meeting October 13, 2004

SunGuideSunGuideSMSM Software Development Project Software Development Project

Status Meeting Status Meeting October 13, 2004October 13, 2004

October 13, 2004SunGuide Status Meeting 2

AgendaAgenda

Time Item Lead

8:30 – 8:35 Introductions Liang Hsia

8:35 – 8:45 License Updates:

- TxDOT and FDOT - MDX JPA

- TransGuide - GDT

- WSDOT TOU - SwRI/FDOT Modification

Liang Hsia

8:45 – 9:00 TMC and Software Deployment Schedule Updates D1 D2 D3 D4 D5 D6 D7 MDXTurnpike Enterprise

9:00 – 9:45 Project Status Report Steve Dellenback

9:45 – 10:00 SunGuideSM Milestone Demonstration “Process and Results” John Bonds

10:00 – 10:20 Break

10:20 – 11:20 SunGuideSM Software (Milestone Demonstration) Robert Heller

11:20 – 11:30 Open Discussion / Action Item Summary All


Introductions


AgendaAgenda

Time Item Lead




- TransGuide - GDT


Liang Hsia




10:00 – 10:20 Break




License UpdatesLicense Updates

SwRI / FDOT Sublicense– License executed before the contract started.– 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)

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

– MOU:• FDOT provided TxDOT with comments and legal opinion on March 2,

2004

– 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.


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 and October 7, 2004.

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.


License Updates - continuedLicense Updates - continued

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 issued iFlorida Data Collection Process (DCP) notice to proceed on September 8, 2004.

GDT License: System Planning Office and Office of Information Systems are finalizing the license agreement on September 14, 2004.


AgendaAgenda

Time Item Lead




- TransGuide - GDT


Liang Hsia




10:00 – 10:20 Break




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

District 4

District 6

MDX

District 7

District 1

District 2

District 5

District 3

Turnpike Enterprise


AgendaAgenda

Time Item Lead




- TransGuide - GDT


Liang Hsia




10:00 – 10:20 Break




Project Web SiteProject Web Site

http://sunguide.datasys.swri.edu


Release-Oriented Release-Oriented Development ApproachDevelopment Approach


Status of Release 1 ActivitiesStatus of Release 1 Activities

Project Management:– PM / Meetings / Reviews– Process documents– Interface Control Documents

(ICDs)

Core software framework:– Database– User administration– Executive handler– Status logger– User interface– Map– Data Bus

DMS:– General Subsystem– NTCIP Florida MIB driver– Mark IV version 2.5 driver


Status of Release 1 Activities - Status of Release 1 Activities - continuedcontinued

CCTV Control:

– General Subsystem

– NTCIP 1205 driver

Video Switching


– IP Video switching driver

Video Wall


– Barco/Argus video wall driver

Traffic Detection, driver for:


– Bitrans B238-I4 driver

– RTMS (EIS and Wavetronix) driver


Status of Release 1 Activities - Status of Release 1 Activities - continuedcontinued

Incident Management:– GUI– Subsystem– TIM coordination

Training:– Training Plan– Classes being adjusted– Material being developed

Testing– Integration testing – Document development

Documents:– Software User’s Manual (SUM– Version Description Document (VDD)– Software Design Document (SDD)


Status of Release 2 ActivitiesStatus of Release 2 Activities

Ramp Metering:– Design activities initiated– Initial GUI design completed– High level design completed

Emergency Evacuation:– Requirements refined and

provided to FDOT– Design initiated

Data Archive– Requirements refined– Design initiated

Web Server– Requirements refined– Design initiated

HAR– Requirements refined– Design initiated

Center-to-Center– Requirements refined– Design initiated

RWIS– Requirements refined– Design initiated

Inventory and Maintenance– Requirements to be refined

Optional Service:– iFlorida Data Collection

Process (DCP)


Development ActivityDevelopment Activity

Current major development efforts are focused on:

– RTMS Driver (EIS and Wavetronix support)

– Map link editor (more later)

– User preference editor (more later)

– Barco / Argus Video Wall Interface (more later)

– IP Video Switching and Snapshots

Other project activities:

– Integration

– Testing

– Documentation (lots of effort here)


Map Link EditorMap Link Editor

Objective:– Provide an interactive tool to create links to display

real-time traffic conditions (from TSS)

Approach:– A “restricted” GUI to edit the links– Background map can be displayed– Tool creates a XML file of the “speed layer” of the

map– User specifies:

• Points along a line to draw the link• Add highway symbols (e.g. Interstate shield) –

shields are “dynamic” (not bit maps)


Map Link Editor: Example ScreenMap Link Editor: Example Screen


User Preference EditorUser Preference Editor

Objective:– Provide the user with a mechanism to change the

“look and feel” of the GUI

Approach:– Allow a user to set and save preferences– Preferences are saved to database– User preferences are loaded when user logs in


User Preference Editor:User Preference Editor:Example ScreensExample Screens


User Preference Editor:User Preference Editor:Example ScreensExample Screens


Barco / Argus Video WallBarco / Argus Video Wall

Initial switching being performed using:– Apollo API: 1.6 Beta Service Release 2– “Official” release of Service Release 2 by mid-

October (per Barco)

Current issues:

1. Cannot determine what video is on a viewer: on startup or when the geometry is refreshed, the video wall GUI will display no sources showing as connected (supposed to be fixed by Barco)

2. When a layout is activated, takes 3 seconds to respond: GUI has a built in delay to “wait”


Barco / Argus Video Wall: Barco / Argus Video Wall: Example ScreensExample Screens


Deployment Challenges / IssuesDeployment Challenges / Issues

Vicon Camera:– Protocol issue:

• Vicon is using NTCIP 1205 V01.07, July 12 1999 • SunGuideSM uses NTCIP 1205 V01.08 Amendment

1 v08, August 2004

– Vicon commitment to update:• Letter to FDOT (James Bitting) dated

September30, 2004• Signed by Vice President of Sales: John

Whiteman, Jr.

– Existing cameras will need to be updated:• District 4• SwRI


Functional ThreadsFunctional Threads


Deliverable StatusDeliverable Status

SwRI waiting for FDOT comments:– Software Integration Case Procedures

Future documents to be provided by SwRI:– SwRI will update the ConOps document and resend to FDOT – Software User’s Manual– Version Description Document– Software Design Document

All documents delivered to FDOT

are available on the project web site.


Cost StatusCost Status

Release 1:– Budget amount: $3,863,374– As of 9/24/04, ~$3,040,000 has been expended

Release 2:– Budget amount: $2,568,339– As of 9/24/04, ~$199,000 has been expended

Cost reductions (funds back to FDOT):– Eliminating DTS Efforts: $75,009.71– Combining 2a and 2b: $61,676.09 (this includes a

“training adjustment” to add classes)


Spending CurveSpending Curve


Schedule StatusSchedule Status

Current areas of concern:– Documents:

• None

– Software:• None

– Baseline software (TransGuide component)


Schedule Status – continuedSchedule Status – continuedLast Reporting PeriodLast Reporting Period


Schedule Status - continuedSchedule Status - continuedCurrent Reporting PeriodCurrent Reporting Period


Schedule Status - continuedSchedule Status - continued

Integration:

– Proceeding well

– Continuing long term “endurance” testing

“Factory” Acceptance Testing:

– Tentatively November 17-19 in San Antonio

Future status meetings that need to be scheduled:

– November 9, 2004

– December 8, 2004 (“short” meeting in Jacksonville)

Future reviews that need to be scheduled:

– Release 2 Software Design Review: needs to occur before December 10, 2004 (might be conducted with NetMeeting or WebEx).


Action ItemsAction Items


Action Items - continuedAction Items - continued


AgendaAgenda

Time Item Lead




- TransGuide - GDT


Liang Hsia




10:00 – 10:20 Break




John Bonds Presentation


AgendaAgenda

Time Item Lead




- TransGuide - GDT


Liang Hsia




10:00 – 10:20 Break




AgendaAgenda

Time Item Lead




- TransGuide - GDT


Liang Hsia




10:00 – 10:20 Break




Milestone Demonstration


AgendaAgenda

Time Item Lead




- TransGuide - GDT


Liang Hsia




10:00 – 10:20 Break




Action Item RecapAction Item Recap

Number Person Action

53

54

55

56

57

58

59

Date post:	01-Jan-2016
Category:	Documents
Upload:	jaime-britt
View:	37 times
Download:	0 times