sunguide sm software development project status meeting april 29, 2004

SunGuideSunGuideSMSM Software Development Project Software Development Project

Status Meeting Status Meeting April 29, 2004April 29, 2004

April 29, 2004SunGuide Status Meeting 2

AgendaAgenda

Time Item Lead

8:30 – 8:35 Introductions Hsia and all participants

8:35 – 8:45 Software MOU, Licenses, and Contract Amendment for Release 1 Updates

Hsia

8:45 – 9:15 Districts’ TMC and Software Deployment Schedule Updates (Sorted by scheduled and planned deployment Dates)

District 4 District 6 MDX District 7District 1 District 2 District 5 Turnpike District 3

9:15 – 9:45 Project Status Report Dellenback

9:45 – 10:00 Open Discussion / Action Item Summary Dellenback

10:00 – 10:20 Break

10:20 – 10:30 Demonstration of American Dynamics Keyboard / Joystick

Dellenback / Regner

10:30 – 12:00 Demonstration of SunGuide software:Executive HandlerStatus LoggerMapGUI (with Logitech joystick)Data BusCCTV SubsystemTSS SubsystemIM Subsystem (tentative)

Robert HellerLynne RandolphJohn BriscoRoger StrainMeredith MoczygembaJennifer SpulerMark SmithBret SadlerJames HalbertCharlie Wallace


Introductions


AgendaAgenda

Time Item Lead



Hsia





10:00 – 10:20 Break


Dellenback / Regner




Software License IssuesSoftware License Issues

SwRI / FDOT License– 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 draft license on March 16, 2004.• FDOT provided recommendation to TxDOT on April 12, 2004.• Al Kosik of TxDOT to address license the week of April 19, 2004

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 / MDX Joint Program Agreement (JPA)– FDOT provided MDX with preliminary JPA on December 3, 2003.


FDOT Contract Amendment ProcessFDOT Contract Amendment Process

FDOT receives complete information from SwRI; FDOT ITS Office distributes the complete information to Committee members

and gets members’ confirmation of Districts’ decision in five working days.3. FDOT Procurement Office receives information from FDOT ITS Office;4. FDOT Procurement Office prepares the amendment and detailed processes;5. FDOT Procurement Office forwards the contract document to FDOT Office of

General Counsel for legal review and signature;6. FDOT Office of General Counsel returns the approved document to the FDOT

Procurement Office;7. FDOT Procurement Office sends to SwRI for review and signature;8. SwRI returns the signed document to FDOT Procurement Office, for

processing (at this stage, the Procurement Office must have the encumbrance completed and then can issue the Notice to Proceed);

9. FDOT Procurement Office forwards the contract document to the FDOT State Highway Engineer’s Office for review and signature.

10. FDOT State Highway Engineer’s Office returns the signed Contract Document to the FDOT Procurement Office for final processing.

11. FDOT issues the Contract Change Order


AgendaAgenda

Time Item Lead



Hsia





10:00 – 10:20 Break


Dellenback / Regner




ReportsReports

District 4

District 6

MDX

District 7

District 1

District 2

District 5

District 3

Turnpike


AgendaAgenda

Time Item Lead



Hsia





10:00 – 10:20 Break


Dellenback / Regner




Project Web SiteProject Web Site

http://sunguide.datasys.swri.edu


Release-Oriented Release-Oriented Development ApproachDevelopment Approach

Release 1 Release 2a Release 2b not in scope


Scope of SunGuideScope of SunGuideSMSM Effort Effort

Release 1:– Core software framework:

• Database• Executive handler• Status logger• User interface• Map• Data Bus

– DMS subsystem, drivers for:• NTCIP Florida MIB• Mark IV version 2.5

– CCTV subsystem, drivers for:• NTCIP camera support• American Dynamics 2050 switch

(stopped)– Traffic Detection, driver for:

• Bitrans 238-I95– Incident management subsystem

Release 2a:– Core software framework upgrade– Center-to-Center – FDOT Central office configuration– Ramp metering – CCTV subsystem, drivers:

• SunGuideSM protocol (stopped)– RWIS – Archive data – HAR– Web server – Emergency evacuation

Release 2b:– Inventory and maintenance


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 subsystem, drivers for:– NTCIP Florida MIB– Mark IV version 2.5

CCTV subsystem, drivers for:– NTCIP camera support– American Dynamics 2050 switch (stopped)

Traffic Detection, driver for:– Bitrans 238-I95 (changing to B238-I4)

Incident management subsystem


Status of Release 2a ActivitiesStatus of Release 2a Activities

CCTV subsystem, drivers for:– SunGuideSM protocol camera support – stopped per FDOT

request

Ramp Metering:– Requirements provided to FDOT for review– Plan to perform a site visit to WSDOT operations facility

Emergency Evacuation:– Refining requirements


Deliverable StatusDeliverable Status

Pending:

– Revised Concept of Operations (ConOps) document

Future documents:

– Software Acceptance Test Plan

– Software Integration Plan

All available on project web site.


Cost StatusCost Status

Release 1:

– Budget amount: $3,208,052

– As of 4/16/04, ~$1,384,000 has been expended

Release 2a:

– Budget amount: $2,074,276

– As of 4/16/04, ~$52,000 has been expended

Release 2b:

– Budget amount: $245,311

– As of 4/16/04, $0 has been expended


Schedule StatusSchedule Status

Current schedule is provided with each status report Release 1 software operational in the lab:

• Core software framework:– Database– User administration– Status Logger– Executive Handler– User Interface– Map– Data Bus

• DMS:– Subsystem– Mark IV driver– NTCIP driver

• CCTV:– Subsystem– NTCIP driver– “Pelco” driver (for testing purposes only)

• TSS:– Subsystem– Simulator process (up to 1000’s of detectors)

• Incident management– GUI (partially)


Schedule Status - continuedSchedule Status - continued

Current areas of concern:– Documents:

• None

– Timing of the ECO being approved

– 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

Concept of Operations Review and Software Design Review:– To be held in Orlando– Date TBD (tentatively May 12th)

Future status meetings need to be scheduled:– May 12, 2004 (tentatively)– June 11, 2004 (tentatively)– July 9, 2004 (tentatively)– August 13, 2004 (tentatively)


Messages LoggedMessages Logged

Status Logger:– Centralized logging– Custom applications implement messages– Viewer exists

Five logging levels:– Informational– Detailed– Warning– Error– Debug

List of messages provided to FDOT on 3/31/04


Status Logger ViewerStatus Logger Viewer


Sample Status Logger MessagesSample Status Logger Messages


Status Logger ConclusionsStatus Logger Conclusions

SwRI needs any feedback on the messages being logged by 5/14/04.


Action ItemsAction Items


Action Items - continuedAction Items - continued


Project Scope Changes in Process


Items to be added…Items to be added…

Release 1:– IP Video Switch driver– NTCIP 1208 Video Switch driver– DTS testing:

• 1205 Driver• 1208 Driver

– IDI:• Purchase of CCTV controllers• Purchase of DMS (Dambach) controllers:• Testing:

– CCTV Controllers– DMS Controllers

– Concept of Operations (ConOps) enhancement


Items to be added - continuedItems to be added - continued

Release 2a:– WSDOT 170 driver for Ramp Metering– Milestone demonstration #2– Canoga Microloop device driver– RTMS device driver:

• EIS• Wavetronix

– Barco / Argus video wall driver– SunGuide Trailblazer support

Release 2b:– Milestone Demonstration #3


Architecture with ECP #1Architecture with ECP #1


AgendaAgenda

Time Item Lead



Hsia





10:00 – 10:20 Break


Dellenback / Regner




Discussion / Future MeetingsDiscussion / Future Meetings

Open Discussion

Need to schedule:– Concept of Operations Review– Software Design Review

Need to establish:– May Status Meeting– June Status Meeting– July Status Meeting– August Status Meeting


Action Item RecapAction Item Recap

Number Person Action

41

42

43

44

45

46

47


AgendaAgenda

Time Item Lead



Hsia





10:00 – 10:20 Break


Dellenback / Regner




SwRI Development LabsSwRI Development Labs


Lab DemonstrationsLab Demonstrations

sunguide sm software development project status meeting april 29, 2004

Documents

fdot txdot partnership

proceedfdot procurement

txdot software license

fdot wsdot term of use

signed contract document

signed document

transguide software

draft license