SunGuide SM Software Development Project Status Meeting May 10, 2005 CDRL 1-8.3.18

SunGuideSunGuideSMSM Software Development Project Software Development Project

Status MeetingStatus MeetingMay 10, 2005May 10, 2005

CDRL 1-8.3.18CDRL 1-8.3.18

May 10, 2005SunGuide Status Meeting 2

AgendaAgenda

Time Item Lead

9:00 – 9:05 Introductions Liang Hsia

9:05 – 9:10 License Update Liang Hsia

9:10 – 9:25 TMC and Software Deployment Schedule Updates Districts / Other Agencies

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

9:45 – 10:00 Status of ECO# 1.1 Liang Hsia

10:00 – 10:15 Results of Demonstration of Release 1.1 in San Antonio Steve Dellenback

10:15 – 10:30 Break

10:30 – 10:45 Revised Plan for Release 1.1 Delivery Steve Dellenback

10:45 – 11:00 IV&V Acceptance Test Plan John Bonds

11:00 – 11:45 Concept for MDX / D6 / D4 C2C Demonstration John Bonds / SwRIMDX / D4 / D6 / FDOT Staff

11:45 – 1:00 Lunch

1:00 – 2:00

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

Bonds /Dellenback / Martinez Espinoza

2:00 – 3:00 District 6 equipment inventory review and site inspection Martinez / Heller

3:00 - 3:15 Closing remarks and adjourn Liang Hsia


Introductions


AgendaAgenda

Time Item Lead







10:15 – 10:30 Break




11:45 – 1:00 Lunch

1:00 – 2:00






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.



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.

GDT 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


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


AgendaAgenda

Time Item Lead







10:15 – 10:30 Break




11:45 – 1:00 Lunch

1:00 – 2:00






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

May 16, 2005 to May 30, 2005: stress testing and ad hoc testing at SwRI

June 1, 2005: Release 1.1 Acceptance Test at SwRI

June 13, 2005: Release 1.1 deployment in District 4depending on test results

June – August, 2005: Ramp Meter Test and Milestone Demonstration

May 2005: 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

August 12, 2005: 45 CCTV available

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


District 6 RTMCDistrict 6 RTMC

April 2005: Ramp metering subsystem testing and SunGuide Software Milestone Demonstration planned

August 28 2005: I-95 Package B project completion

August 2005: SunGuideSM software deployment

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

August 2005 SunGuideSM Software Release 2 deployment at MDX

October 2005 MDX TMC Operational



March 2006 Building Construction FinishApril 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

August 2005 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

August, 2005 C2C deployment among Districts 4, 6, and MDX


AgendaAgenda

Time Item Lead







10:15 – 10:30 Break




11:45 – 1:00 Lunch

1:00 – 2:00






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 initial Release 1 requirements complete

Development of Release 1.1 requirements complete

Efforts remaining:– Integration testing– Factory acceptance testing– Document updates (more later)– Training material:

• Classes were added (R2 classes were moved up to R1)

• Material will be ready prior to a deployment


Status of Release 2 ActivitiesStatus of Release 2 Activities

Ramp Metering:– Subsystem:

• Design complete• Development complete

– Drivers:• TSS driver complete• RM driver complete

– GUI• Design complete• Development in process

– Undergoing integration testing in San Antonio

Emergency Evacuation:– Design initiated– Development initiated

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

Antonio

Web Server– Design complete– Development in process

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

system

Center-to-Center– Design initiated– Development in process

RWIS– Design complete– Development in process

Safety Barrier– ICD Complete– Design initiated

Inventory and Maintenance– Will be initiated soon

Optional Service:– iFlorida Data Collection Process (DCP)


Deliverable StatusDeliverable Status

SwRI waiting for FDOT comments:– None

Future documents to be provided by SwRI:– Updated Training Plan– Training Material

All documents delivered to FDOT

are available on the project web site.

http://SunGuide.datasys.swri.edu


Cost Status (as of 4/15/05)Cost Status (as of 4/15/05)

Release 1:– Allocated: $4,335,554 (includes ECO 1.1)– Spent: $4,004,264

Release 2:– Allocated: $2,651,361– Spent: $1,247,679

Deployments:– Allocated: $397,292– Spent: $8,598

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


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


Schedule StatusSchedule Status

Current areas of concern:– Documents:

• None– Software:

• Ramp Meter is significantly over-budget– Contractual:

• ECO 1.1 is not processed so the project is currently over budget

– Release 1.1 Software will be ready for testing / deployment by May 16, 2005

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


Schedule Status – continuedSchedule Status – continuedLast Reporting PeriodLast Reporting Period


Schedule Status - continuedSchedule Status - continuedCurrent Reporting PeriodCurrent Reporting Period


Events to Be ScheduledEvents to Be Scheduled

Future status meetings that need to be confirmed:– June 7, 2005 (will this be necessary?)– July 2005: SwRI proposes the week of July 18th – August 2005: SwRI proposes week of Aug 8th or Aug 22nd

Future reviews that need to be scheduled:– Release 2 Software Design Review

Milestone Demonstrations:– Milestone Demo #2: D6 Integrated DMS and CCTV operation

to be demonstrated

– Milestone Demo #3: D4, D6 and MDX Functionality of C2C, CCTV and DMS to be demonstrated


Release 2 Software Insight


HAR – Speech ConversionHAR – Speech Conversion

FDOT has funded a “HIS DR2000 Driver” for HAR MDX implementation of HIS HAR system:

– Central software for HAR control– SIM (Software Interface Module) that SwRI is using for the driver

– this allows “files” to be exchanged to control the HAR units

Issue – text to speech conversion:– MDX did not purchase the Text to Speech module (cost $6,500 –

more if installed separately)– SwRI has investigated using Visual Studio .NET text/speech

conversion tool– Test conversion (sample):

• This is the voice of the Florida Department of Transportation. 2 left lanes closed on interstate four ten. 3 miles ahead. Please merge right.

– Highest quality would be from the HIS module (SwRI needs decision by May 30, 2005).


Web ServerWeb Server

Original plan was to use SVG and client application

– Problems:

• Performance (loading statewide data)

• Required SVG to be loaded on all clients

• Did not meet FDOT Web Guidelines Solution:

– Create “static” maps with a server application

– Graphics images are sent to clients Notes:

– All map views are configurable by installation

– Data is supplied by C2C interface


Web Server - continuedWeb Server - continued








Web Server – continued:Web Server – continued:Configuring Map ViewsConfiguring Map Views

<mapViews> <view id="Statewide">

<imageSize width="450" height="450"/><boundingRect top="30.818830" left="-84.734330" bottom="24.837500" right="-78.747670"/><imgPath>Statewide.jpg</imgPath>

</view> <view id="District 4">

<imageSize width="450" height="450"/><boundingRect top="26.270830" left="-80.475000" bottom="25.860170" right="-80.061670"/><imgPath>District 4.jpg</imgPath>

</view> <view id="North Detail">

<imageSize width="450" height="450"/><boundingRect top="26.206830" left="-80.199670" bottom="26.120830" right="-80.113000"/><imgPath>North Detail.jpg</imgPath>

</view> <view id="East Detail">

<imageSize width="450" height="450"/><boundingRect top="26.177830" left="-80.218150" bottom="26.060170" right="-80.101670"/><imgPath>East Detail.jpg</imgPath>

</view> <view id="South Detail">

<imageSize width="450" height="450"/><boundingRect top="26.098170" left="-80.1998300" bottom="26.04500" right="-80.147000"/><imgPath>South Detail.jpg</imgPath>

</view><view id="West Detail"><imageSize width="450" height="450"/><boundingRect top="26.283830" left="-80.416000" bottom="26.125170" right="-80.256970"/><imgPath>West Detail.jpg</imgPath>

</view></mapViews>

Web Site Demo


Ramp MeterRamp Meter

Integration testing currently being performed GUI development almost complete


Ramp Meter - continuedRamp Meter - continued


AgendaAgenda

Time Item Lead







10:15 – 10:30 Break




11:45 – 1:00 Lunch

1:00 – 2:00






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







10:15 – 10:30 Break




11:45 – 1:00 Lunch

1:00 – 2:00






New FunctionalityNew Functionality

Windows broken out:– TSS– CCTV control– Video switching– Video wall– DMS status / send message (other DMS not yet broken out)

New/Enhanced Editors:– DMS associations (supports IM response plan creation)– TSS virtual links (for not yet instrumented highways)

Message Arbitration System (MAS) – SEE NEXT PAGE– Levels: 1 to 255 (1 is the highest priority), defaults– Highest priority message displayed– Message routed to MAS– DMS routes sequences to MAS– MAS queues: view queues and Manage content (not yet

complete)


MAS: Conceptual DesignMAS: Conceptual Design


New Functionality – con’tNew Functionality – con’t

Incident Management:– IM broken into multiple windows– Alerts use visual/aural alerts notification for non-addressed

alerts– Pre-filling of fields– Three levels of severity– Owner concept:

• Add support for owner• Release ownership• Take ownership• Visual/aural alerts for un-owned

– Response plans:• Uses DMS associations to select devices• Multiple severity levels• Generation now in the 1 to 3 second range

– Added mileposts


New Functionality – con’tNew Functionality – con’t

MCP (Manual Control Panel)

– American Dynamics Model 2088 supported

– Features:

• Control: PTZ, focus, iris

• Presets: set and call

• Switching: monitor and video wall

Various:

– Added logoff

– Second logon forces first off

– CCTV locks automatically assigned (if available)


AgendaAgenda

Time Item Lead







10:15 – 10:30 Break




11:45 – 1:00 Lunch

1:00 – 2:00






AgendaAgenda

Time Item Lead







10:15 – 10:30 Break




11:45 – 1:00 Lunch

1:00 – 2:00






Tentative Release 1.1 Testing and Tentative Release 1.1 Testing and Deployment ScheduleDeployment Schedule


Documents for Release 1.1 Documents for Release 1.1 DeliveryDelivery

SwRI is providing updates to the following documents:– Software Requirements Specification (SRS): done– Software Integration Plan (SIP): done– Software Acceptance Test Procedures (SATP): done– Software Integration Case Procedures (SICP): draft

complete, final by May 16, 2005– Software Users Manual (SUM): by June 1, 2005– Version Description Document (VDD): by June 1, 2005

New documents/material:– Training Material (by June 8, 2005)


Testing ProcessTesting Process

“Factory Acceptance Test” (FAT) to be run in the SwRI development labs

Planned dates:– Early preview: May 30th

– Testing: June 1st and June 2nd – Ad hoc testing: June 3rd

Process:– Tests from SICP will be executed– FDOT and SwRI witness– Results captured


Post TestingPost Testing

SwRI to produce:– Software Test Report

Installation in District 4 targeted for the week of June 13th

Training:– Training is “slide” and “hands-on” based– Dates for District 4 training needs to be established– Classes (not all have to be scheduled):

• Operator (3 to 4 hour class)• Administrator (3 to 4 hour class)• Developer (4 to 8 hour class)


AgendaAgenda

Time Item Lead







10:15 – 10:30 Break




11:45 – 1:00 Lunch

1:00 – 2:00






IV&VIV&V

Independent Verification and ValidationIndependent Verification and Validation TWO 12 Amendment 5 PBS&J Tasks 5.22 through 5.32TWO 12 Amendment 5 PBS&J Tasks 5.22 through 5.32

– IV&V Test Plan for Release 1.1 Software

– IV&V Test Procedures for Release 1.1 Software.

– Dry run the IV&V Test Procedures at least 3 times on the SunGuide Software correcting the procedures as necessary

– Test Readiness Review at D4 RTMC

– Conduct the IV&V Acceptance Test on the SunGuide Software System that has been installed in D4 RTMC.

– Hot Wash-up meeting immediately after the conclusion of IV&V testing in D4 RTMC

– Issue Minutes of the meeting.

– Draft IV&V Test Report

– Final IV&V Test Report

May 10, 2005SunGuide Status Meeting IV&V Plan 63

IV&V Test PhilosophyIV&V Test Philosophy

Verify System functional and performance requirements met.

Baseline ECO#1.1 to the extent D4 has the hardware to support.

Operational test scenarios Test at the highest level possible Any requirements not able to be tested will be

tested in Release 2. Basis for FDOT Acceptance of Release 1.1


Waivers, Deviations and FailuresWaivers, Deviations and Failures

If a requirement is not satisfied FDOT has three If a requirement is not satisfied FDOT has three optionsoptions**::

Issue a WaiverIssue a Waiver – a requirement that is not met due to a design or implementation

error – accept the system as-is if a work around is available– the problem will be fixed in accordance with the Contract Vendor-

furnished, the Department-approved corrective action plan within the approved schedule

Issue a deviationIssue a deviation– Vendor may request a deviation from a stated requirement if the

SunGuide can be shown to provide an equivalent functionality.– Department can accept or reject a deviation request.– Problem never fixed.

Fail the Acceptance and require rework.Fail the Acceptance and require rework.

* Scope of Services, Task 6, Pg 33* Scope of Services, Task 6, Pg 33


Expected D4 ConfigurationExpected D4 Configuration

Barco Video Wall with Argus controller and Apollo

Software version 1.6

CCTV: Vicon SVFT-PR23 (Number to be determined)

DMS: Mark IV I-95

– (A316111-102 Rev.A8 June 26, 2001)

CCTV Joystick AD 2088 (need to discuss AD 300)

Traffic sensors (?) - assumed yes for the plan.

No RWIS

No HAR


Release 1.1Release 1.1

249 Functional requirements249 Functional requirements– 20 User requirements

– 25 System requirements

– 80 Subsystem requirements

– 103 Component requirements

– 21 Unit requirements

13 requirements verified during the Functional Configuration Audit held January 10, 2005


Operational Test CasesOperational Test Cases

OTC-1 Hazmat Incident– Verifies 89 requirements

OTC-2 CCTV Details– Verifies 13 requirements

OTC-3 SunGuide Operation– Verifies 24 requirements

OTC-4 System reliability, monitoring and reporting– Verifies 8 requirements

OTC-5 Database operations– Verifies 12 requirements

OTC-6 Fail safe and security– Verifies 9 requirements

OTC-7 Operator controls/DMS details– Verifies 34 requirements

OTC-8 Traffic Detection – Verifies 23 requirements

FCA verified 13 requirements (already verified FAT 1)

212 of 236 operational requirements are testable at D4212 of 236 operational requirements are testable at D4


IV&V Tentative PlanIV&V Tentative Plan

Run after SunGuide is installed at D4 and is certified Run after SunGuide is installed at D4 and is certified

by SwRI to be operationalby SwRI to be operational

Run at the convenience of D4Run at the convenience of D4

DMS operations will adhere to the D4 rules used DMS operations will adhere to the D4 rules used

during the Milestone Demonstration (October 2004)during the Milestone Demonstration (October 2004)

Expected to take 2 days (10 hours)Expected to take 2 days (10 hours)

Tentative datesTentative dates

– Early date: July 6 and 7Early date: July 6 and 7– Latest date: August 19 and 20Latest date: August 19 and 20


AgendaAgenda

Time Item Lead







10:15 – 10:30 Break




11:45 – 1:00 Lunch

1:00 – 2:00






PurposePurpose

Demonstration of technical progress towards Demonstration of technical progress towards

meeting one or more functional threads before meeting one or more functional threads before

final integration and installationfinal integration and installation

Early look at how requirements were interpreted Early look at how requirements were interpreted

and implemented in enough time to influence the and implemented in enough time to influence the

final productfinal product

Gain on-site experience with installation and Gain on-site experience with installation and

operation requirementsoperation requirements


C2C Milestone DemoC2C Milestone Demo

Is it needed?Is it needed?

NoNo C2C code is almost completeC2C code is almost complete Requires a full install at both sitesRequires a full install at both sites Requires site-to-site TCP/IP connectivityRequires site-to-site TCP/IP connectivity

Yes

Early install at D6 will surface any Early install at D6 will surface any infrastructure incompatibilitiesinfrastructure incompatibilities

Early demonstration may help FDOT evolve Early demonstration may help FDOT evolve C2C standards for operation.C2C standards for operation.

Timing of demo is crucial to its effectiveness


C2C Demo ConceptC2C Demo Concept

From D4From D4

– view and control D6 CCTV

– put a message on a D6 DMS

From D6From D6– view and control D4 CCTV

– put a message on a D4 DMS

What else needs to be demonstrated?

Add D6 functions like ramp metering demo?

Traffic sensor detection?

Safety barrier interface?


C2C Milestone DemonstrationC2C Milestone Demonstration

Requires Release 2 softwareRequires Release 2 software R2 tentative install at D6 R2 tentative install at D6

– Between September 8 and October 21

D4 Upgrade to R2 D4 Upgrade to R2 – Between September 27 and October 31

C2C Milestone DemoC2C Milestone Demo– anytime between September 28 and November 8

R2 tentative install at MDXR2 tentative install at MDX– August/September time frame

Test Bed in Tallahassee?Test Bed in Tallahassee?


Optimum time for C2C MDOptimum time for C2C MD

August 2005August 2005

D4 will have experience with R1.1

D6 will be ready for ramp metering interface

Still 30 days before install of R2 at D6

MDX will be ready for R2 software


Discussion / ConclusionsDiscussion / Conclusions

Go forward with MD#2?Go forward with MD#2?

What will be demonstrated?What will be demonstrated?

Who will be connected physically?Who will be connected physically?

Action Items?Action Items?


AgendaAgenda

Time Item Lead







10:15 – 10:30 Break




11:45 – 1:00 Lunch

1:00 – 2:00






AgendaAgenda

Time Item Lead







10:15 – 10:30 Break




11:45 – 1:00 Lunch

1:00 – 2:00






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







10:15 – 10:30 Break




11:45 – 1:00 Lunch

1:00 – 2:00






Informal Discussion and TMC Walk Through


AgendaAgenda

Time Item Lead







10:15 – 10:30 Break




11:45 – 1:00 Lunch

1:00 – 2:00