Download
statewide transportation management center software library system status meeting february 17 2004 n.
Skip this Video
Loading SlideShow in 5 Seconds..
Agenda PowerPoint Presentation

Agenda

211 Views Download Presentation
Download Presentation

Agenda

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Statewide Transportation Management Center Software Library SystemStatus Meeting February 17, 2004

  2. Agenda STMCSLS Status Meeting

  3. Agenda STMCSLS Status Meeting

  4. And The Name Is… _______________________ STMCSLS Status Meeting

  5. Agenda STMCSLS Status Meeting

  6. Software 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 STMCSLS Status Meeting

  7. Agenda STMCSLS Status Meeting

  8. Agenda STMCSLS Status Meeting

  9. Agenda STMCSLS Status Meeting

  10. History of Computer Sizing Estimates • 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. STMCSLS Status Meeting

  11. Computer Sizing Estimates: Conceptual Deployment STMCSLS Status Meeting

  12. Computer 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 STMCSLS Status Meeting

  13. SizingTable • 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 STMCSLS Status Meeting

  14. Agenda STMCSLS Status Meeting

  15. Agenda STMCSLS Status Meeting

  16. Project Web Site http://stmcsls.datasys.swri.edu STMCSLS Status Meeting

  17. Release-Oriented Development Approach Release 1Release 2aRelease 2b not in scope STMCSLS Status Meeting

  18. 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 Scope of STMCSLS Effort STMCSLS Status Meeting

  19. 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 1 Activities STMCSLS Status Meeting

  20. CCTV subsystem, drivers for: SunGuide camera support Status of Release 2a Activities STMCSLS Status Meeting

  21. Deliverable 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. STMCSLS Status Meeting

  22. Cost 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 STMCSLS Status Meeting

  23. Schedule 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 STMCSLS Status Meeting

  24. Schedule 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) STMCSLS Status Meeting

  25. Schedule Status - continued STMCSLS Status Meeting

  26. Schedule Status - continued • 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. STMCSLS Status Meeting

  27. Action Items STMCSLS Status Meeting

  28. Action Items - continued STMCSLS Status Meeting

  29. Action Items - continued STMCSLS Status Meeting

  30. Action Items - continued STMCSLS Status Meeting

  31. SwRI Development Labs STMCSLS Status Meeting

  32. General Comments / Feedback on Project Status STMCSLS Status Meeting

  33. Agenda STMCSLS Status Meeting

  34. Draft Contract Amendment List:Sent by Central ITS Office on 2/9/04 STMCSLS Status Meeting

  35. STMCSLS 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 STMCSLS Status Meeting

  36. 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 Device Drivers In BAFO That Were Approved For Implementation STMCSLS Status Meeting

  37. SwRI Asked To Evaluate Adding New 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 STMCSLS Status Meeting

  38. IP 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. STMCSLS Status Meeting

  39. EIS 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. STMCSLS Status Meeting

  40. Wavetronix RTMS TSS Device Driver • Scope: • A device driver for a Wavetronix SmartSensor 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 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. STMCSLS Status Meeting

  41. 3M (Canonga) Microloop TSS Device 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 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 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. STMCSLS Status Meeting

  42. Trailblazer Device Driver and GUI Support • 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) STMCSLS Status Meeting

  43. Intelligent Devices Incorporated (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 STMCSLS Status Meeting

  44. DTS 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. STMCSLS Status Meeting

  45. Barco / 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 STMCSLS Status Meeting

  46. Barco / 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. STMCSLS Status Meeting

  47. Device 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 STMCSLS Status Meeting

  48. Device 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 STMCSLS Status Meeting

  49. Device 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 STMCSLS Status Meeting

  50. Tentative Schedule STMCSLS Status Meeting