statewide transportation management center software library system status meeting february 17, 2004

Statewide Transportation Management Center Statewide Transportation Management Center Software Library SystemSoftware Library System

Status Meeting Status Meeting February 17, 2004February 17, 2004

February 17, 2004STMCSLS Status Meeting 2

AgendaAgenda

Time Item Lead

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

8:35 – 8:40 New Software Name Announcement Hsia

8:40 – 8:50 MOU between FDOT and TxDOT, Software License Updates: TransGuide, and TxSoftware Sublicense Modification for D2

Hsia / Dellenback

8:50 – 9:00 Ramp Metering Module Status, License and Terms of Use (TOU) update

Martinez

9:00 – 9:30 Districts’ TMC and Software Deployment Schedule Updates

Faquir / Martinez / Campo /Bitting / Birosak

9:30 – 10:00 Computer Size Estimates for TMC Dellenback

10:00 – 10:15 Break

10:15 – 10:45 Project Status Report/ URR, SRR Meetings Action Items Follow Up

Dellenback

10:45 – 11:15 Summary of Final List for Contract Amendment: Deletion/Addition of new Modules, Associated Cost, and Schedule

Dellenback

11:15 – 11:20 Announcement of March Project Status Review Meeting with ITS Working Group Meeting

Hsia / Dellenback

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


AgendaAgenda

Time Item Lead




Hsia / Dellenback


Martinez




10:00 – 10:15 Break


Dellenback


Dellenback


Hsia / Dellenback



And The Name Is…And The Name Is…

_______________________


AgendaAgenda

Time Item Lead




Hsia / Dellenback


Martinez




10:00 – 10:15 Break


Dellenback


Dellenback


Hsia / Dellenback



Software License IssuesSoftware License Issues

SwRI / FDOT License– License executed before the STMCSLS contract

started.– TxDOT informed SwRI on January 22, 2004 that

TransGuide software was on “hold”.

TxDOT / FDOT MOU

FDOT / TransGuide License

SwRI / FDOT Sublicense for District 2

FDOT / WsDOT MOU


AgendaAgenda

Time Item Lead




Hsia / Dellenback


Martinez




10:00 – 10:15 Break


Dellenback


Dellenback


Hsia / Dellenback



History of Computer Sizing History of Computer Sizing EstimatesEstimates

SwRI asked during Kick-off meeting to provide sizing estimates (Action Item #9).

SwRI has performed initial sizing analysis and provided a sizing report to FDOT on February 5, 2004.

Provides a technique to “estimate” computer needs.

Contents are preliminary and conservative: document will be updated as software testing continues.


Computer Sizing Estimates: Computer Sizing Estimates: Conceptual DeploymentConceptual Deployment


Computer ConfigurationsComputer Configurations

Workstations:– Microsoft Windows XP, Internet Explorer 6.01 or greater– SVG Viewer 3.0 or greater– 2.4 to 3.0 GHz processor– 512 MB RAM– 20 GB disk

STMCSLS Database Server (these requirements will vary widely based on how much data the STMCSLS implementation chooses to log and the backup policies implemented by the STMCSLS implementation computer staff):

– Microsoft Server 2000– Oracle 9i– > 2.4 GHz processor– > 2 GB RAM (Oracle likes RAM – the more the better)– 70 GB of disk using RAID architecture (this disk space will vary based on

the amount of historical information logged to the database) STMCSLS Application Servers (STMCSLS processes):

– Microsoft Server 2000– STMCSLS Executive Handler – > 2.4 GHz processor– 1 GB RAM– 36 GB of disk


SizingSizingTableTable

Used to estimate computing resources

Process can be “mixed and matched”

Impacts:– Number of users– Number of devices– Multi processors

District specific evaluations will be made during initial stages of implementation


AgendaAgenda

Time Item Lead




Hsia / Dellenback


Martinez




10:00 – 10:15 Break


Dellenback


Dellenback


Hsia / Dellenback



Project Web SiteProject Web Site

http://stmcsls.datasys.swri.edu


Release-Oriented Release-Oriented Development ApproachDevelopment Approach

Release 1 Release 2a Release 2b not in scope


Scope of STMCSLS EffortScope of STMCSLS Effort

Release 1:– Core software framework:

• Database• Process viewer• Status logger• User interface• Map

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

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

– Traffic Detection, driver for:• Bitrans 238I-95

– Incident management subsystem

Release 2a:

– Core software framework upgrade

– Center-to-Center

– FDOT Central office configuration

– Ramp metering

– CCTV subsystem, drivers:

• SunGuide protocol

– 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– Process viewer– Status logger– User interface– Map

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

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

Traffic Detection, driver for:– Bitrans 238I-95

Incident management subsystem


Status of Release 2a ActivitiesStatus of Release 2a Activities

CCTV subsystem, drivers for:– SunGuide camera support


Deliverable StatusDeliverable Status

Pending:– Concept of Operations (in final stages now that

requirements are complete)– Software Security Plan (in final review)– Two complete but not delivered (waiting for Oracle

licenses from FDOT)

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 2/11/04, ~$815,000 has been expended

Release 2a:

– Budget amount: $2,074,276

– As of 1/2/04, $32,000 has been expended

Release 2b:

– Budget amount: $245,311

– As of 1/2/04, $0 has been expended


Schedule StatusSchedule Status

Current schedule is posted to project web site

Overall project status:– Ahead in many places– STMCSLS is operational in the lab:

• Support processes (executive, logging)• Data Bus• DMS (Mark IV and NTCIP)• CCTV:

– Master process– NTCIP driver

• TSS: talking to “simulators”• Incident management


Schedule Status - continuedSchedule Status - continued

Current areas of concern:– Lack of Oracle Designer license

– Device drivers:• BiTrans TSS driver

– Documents:• Concept of Operations• Security Plan

– Lack of final device drivers

– Baseline software (TransGuide component)



SwRI would encourage a project status meeting after ITS America (April 26 – 28 in San Antonio)

SwRI would recommend April 29th

Agenda:– Project status– See STMCSLS operating in a multi-server, multi-

workstation environment with REAL EQUIPMENT– Meet the development team

Note:– The project status meeting in San Antonio on April 29th

will depend on Committee Member’s travel plans.


Action ItemsAction Items


Action Items - continuedAction Items - continued


SwRI Development LabsSwRI Development Labs


General Comments / Feedback on Project Status


AgendaAgenda

Time Item Lead




Hsia / Dellenback


Martinez




10:00 – 10:15 Break


Dellenback


Dellenback


Hsia / Dellenback



Draft Contract Amendment List:Draft Contract Amendment List:Sent by Central ITS Office on 2/9/04Sent by Central ITS Office on 2/9/04


STMCSLS and Device DriversSTMCSLS and Device Drivers

Device functionality isolated by “ICDs” (Interface Control Documents)

Subsystems are “generic” and not specific to device functionality

Device drivers easy to add once base subsystem is complete and operational


Device Drivers In BAFO That Were Device Drivers In BAFO That Were Approved For ImplementationApproved For Implementation

DMS:

– NTCIP

– Mark IV (v 2.5)

CCTV (Cameras):

– NTCIP

– SunGuide

Video Switch:

– American Dynamics 2050 (Stopped development)

Traffic Detectors:– BiTrans 238I-95

Ramp Metering:– WsDOT (firmware)

RWIS:– NTCIP

HAR


SwRI Asked To Evaluate Adding SwRI Asked To Evaluate Adding New Devices to STMCSLS EffortNew Devices to STMCSLS Effort

IP-Video Device Driver

EIS RTMS TSS Device Driver

Wavetronix RTMS TSS Device Driver

3M (Canonga) Microloop TSS Device Driver

Trailblazer Device Driver and GUI Support

Intelligent Devices Incorporated (IDI) Support

Barco / Argus:

– Video Switch Device Driver

– Wall Configuration Software

DTS Video Switch


IP VideoIP Video

Scope:– SwRI will develop an IP-Video video switch device driver that will

instruct “decoders” to listen to “encoders”.– The device driver shall be compliant with the STMCSLS CCTV Video

Switch Interface Control Document (ICD) interface– The device driver will issue SNMP commands to the following

decoders:• CorTec• Teleste• VBrick• iMpath

– Update STMCSLS video switch configuration software to provide a field to identify the manufacturer of the encoders and decoders configured in the STMCSLS.

Assumptions:– SwRI will provide VBrick, Teleste and Cortec TCP/IP encoders and

decoders.– FDOT will provide iMpath TCP/IP encoders and decoders.– SwRI will not be performing inter-operability testing between different

brands of encoders and decoders.


EIS RTMS TSS Device DriverEIS RTMS TSS Device Driver

Scope:– A device driver for a Electronic Integrated System (EIS) RTMS device

will be developed.– The device driver compliant with the STMCSLS TSS device driver

Interface Control Document (ICD) interface shall be developed.– Efforts will include:

• Design• Peer Review• Implementation• Testing• Integration with the STMCSLS TSS subsystem

Assumptions:– The serial port of the EIS RTMS device shall be connected to a terminal

(port) server so that a TCP/IP interface can be used to retrieve data.– SwRI will supply test hardware in the SwRI development laboratories.


Wavetronix RTMS TSS Device Wavetronix RTMS TSS Device DriverDriver

Scope:– A device driver for a Wavetronix SmartSensor device will be

developed.– The device driver compliant with the STMCSLS TSS device driver



Assumptions:– The TCP/IP interface from the device will be used to retrieve data.– SwRI will supply test hardware in the SwRI development laboratories.

Note: if both FDOT approves both the Wavetronix and EIS RTMS device drivers cost savings will likely occur because of software reuse.


3M (Canonga) Microloop TSS 3M (Canonga) Microloop TSS Device DriverDevice Driver

Scope:– A device driver for a 3M Canoga, model C400/C800/C990E device will

be developed.– The device driver compliant with the STMCSLS TSS device driver



Assumptions:– The serial port of the 3M device shall be connected to a terminal (port)

server so that a TCP/IP interface can be used to retrieve data.– SwRI will supply test hardware in the SwRI development laboratories.

Note: if both FDOT approves both the Wavetronix and EIS RTMS device drivers cost savings will likely occur because of software reuse.


Trailblazer Device Driver and GUI Trailblazer Device Driver and GUI SupportSupport

Scope:– Develop a device driver (to be included in the DMS subsystem) to

support Trailblazer devices, SunGuide protocol will be used to communicate to the devices.

– Develop a GUI that will provide the operator with the capability to request display modifications on a Trailblazer.

– Development staff will travel to Miami for two on-site test periods (up to four days each).

– Efforts will include:• Design• Peer Review• Implementation• Testing• Integration with the STMCSLS DMS subsystem

Assumptions:– FDOT will provide access to a Trailblazer sign for testing (timeframes

for access will be prearranged)


Intelligent Devices Incorporated Intelligent Devices Incorporated (IDI) Support(IDI) Support

Scope:– Work with FDOT staff to identify candidate devices– Observe NTCIP testing with FDOT staff– Once devices accepted by FDOT, perform integration testing with

STMCSLS software framework

Assumptions:– FDOT will procure all devices– All NTCIP compliance testing to be performed by FDOT (TERL)– No software development effort by SwRI


DTS Video SwitchDTS Video Switch

Scope:– SwRI will develop video switch driver that will instruct the DTS video

system to connect video inputs to video outputs.– The device driver shall be compliant with the STMCSLS CCTV Video

Switch Interface Control Document (ICD) interface

Assumptions:– SwRI assumes that camera control and video switching both need to

be supported by this driver.– SwRI needs protocol documents from DTS before we can initiate and

design or development.– SwRI needs access a FDOT provided DTSS unit for testing and

development. SwRI has included funds to travel to FDOT specified locations.

Note: the estimated cost SwRI has provided is an conservative costs; SwRI has been given limited access to technical information about how to communicate to the DTS switch from an external source. Once complete technical information on the interface is received, SwRI will evaluate adjusting the cost estimate based on the details of the interface.


Barco / ArgusBarco / Argus

Scope:– SwRI is proposing two applications:

• Video switch device driver:– SwRI will develop a video switch driver that will instruct the video

wall to change displays in the “Barco Windows”.– The device driver shall be compliant with the STMCSLS CCTV Video

Switch Interface Control Document (ICD) interface• Video wall configuration software:

– SwRI will extend the STMCSLS GUI to allow the Barco video wall to be reconfigured using STMCSLS software.

– The software will allow virtual windows to be defined and input streams associated with each of these windows.

– Note: this software would replace the Barco provided software for configuring the video wall.

– Efforts for both proposed application include:• Design• Peer Review• Implementation• Testing• Integration with the STMCSLS CCTV subsystem


Barco / Argus - continuedBarco / Argus - continued

Assumptions:– SwRI requires access to a Barco unit for fact finding. – SwRI requires a Barco software development environment at SwRI.– SwRI requires access to DTS development staff for questions / answers.– SwRI assumes FDOT will provide the necessary Barco hardware and

software.


Device Driver CostsDevice Driver Costs

SwRI was asked to evaluate the current device driver costs

Current device drivers were included in the BAFO approved by FDOT

New drivers can be added:– SwRI based cost estimates on some assumptions (see

previous slides)– SwRI has developed cost estimates– Schedule impact may vary based on timing and number

of new drivers added


Device Driver Costs - continuedDevice Driver Costs - continued

IP-Video Device Driver: $134,322

EIS RTMS TSS Device Driver: $103,684

Wavetronix RTMS TSS Device Driver: $103,684

3M (Canonga) Microloop TSS Device Driver: $129,074

Trailblazer Device Driver and GUI Support: $56,381

Intelligent Devices Incorporated (IDI) Support: $89,910

Barco / Argus:

• Video Switch Device Driver: $184,788

• Wall Configuration Software: $178,471

DTS Video Switch: $202,003


Device Driver Costs - continuedDevice Driver Costs - continued

Cost reductions:

– CCTV American Dynamics Driver: ~$69,000

– CCTV SunGuide Driver: ~$54,000

Net cost impact to project:

– Additions: $1,182,317

– Reductions: $123,000

– NET: $1,059,317


Tentative ScheduleTentative Schedule

ID Task Name

1 Release 1

4 American Dynamics Video Switch

5 NTCIP CCTV Camera Driver

6 BiTrans B238-I95 TSS Driver

7 DMS NTCIP Driver

8 DMS Mark IV Driver

9

10 Release 2a

13 SunGuide CCTV Camera Driver

14

15 Release 2b

18

19 IP-Video Device Driver

20 DTS Video Switch Driver

21 DTS Camera Driver

22 Barco / Argus Video Switch

23 Barco / Argus Screen Configuration

24 EIS RTMS TSS Device Driver

25 Wavetronix RTMS TSS Driver

26 3M (Canoga) Microloop TSS Driver

27 Trailblazer Driver / GUI Support

28 IDI Support

10/7 10/6

11/17 Stopped by FDOT

11/17 5/3

11/17 4/5

12/1 1/6

12/1 2/10

1/19 8/11

1/19 6/1

12/27 11/18

3/15 7/30

8/2 1/28

8/2 1/28

9/6 2/4

11/1 4/15

3/15 7/15

5/3 9/1

9/6 2/4

4/5 7/23

3/15 8/11

Qtr 4 Qtr 1 Qtr 2 Qtr 3 Qtr 4 Qtr 1 Qtr 2 Qtr 3 Qtr 4 Qtr 1 Qtr 22003 2004 2005 2006


AgendaAgenda

Time Item Lead




Hsia / Dellenback


Martinez




10:00 – 10:15 Break


Dellenback


Dellenback


Hsia / Dellenback



Future MeetingsFuture Meetings

Next Status Meeting:– March 9th (~2:00 to 5:00) in conjunction with the FDOT

beginning of the year ITS meeting, will include:• Status Report• Significant software demonstration

Outreach Meeting: March 10th (1:45 to 2:00)

Need to schedule:– Software Design Review

Need to confirm:– Status meeting at SwRI on April 29th (ITS America)– Meet 8:30 to 12:00


March DemonstrationMarch Demonstration


AgendaAgenda

Time Item Lead




Hsia / Dellenback


Martinez




10:00 – 10:15 Break


Dellenback


Dellenback


Hsia / Dellenback



Questions / Comments


Action Item RecapAction Item Recap

Number Person Action

1

2

3

4

5

6

7

statewide transportation management center software library system status meeting february 17, 2004

Documents

stmcsls status meeting

project status review

schedule dellenback

software license updates

new software

d2 hsia dellenback

project status report

ramp metering module