1. SunGuide SM Software Development Project Status Meeting March 9, 2004

2. March 9, 2004SunGuide Status Meeting 2 Agenda TimeItemLead 2:00 – 2:05IntroductionsHsia and all participants 2:05 – 2:25Configuration Management:  CM during development  CM during / after deployment Dellenback / Heller 2:25 – 2:50Districts’ TMC and Software Deployment Schedule Updates (Sorted by scheduled or planned deployment date) Faquir - District 4 Bitting - District 7 Martinez - District 6 Campo - MDX Birosak - District 1 Vega - District 2 Rivera - District 5 McCrary - District 3 Birenbaum - Turnpike Enterprise 2:50 – 2:55MOU between FDOT and TxDOT, Software License Updates: TransGuide, and TxSoftware Sublicense Modification for D2 Hsia / Dellenback 2:55 – 3:15Computer Size Estimates for TMC Dellenback 3:15 – 3:30Break 3:30 – 4:00 Project Status Report:  Development status  GUI / Map Screen Snapshots  Cost and schedule status  Action item follow-up Dellenback 4:00 – 4:15New device drivers:  Driver details  Cost and schedule Dellenback 4:15 – 4:30Open Discussion / Action Item Summary Dellenback

3. March 9, 2004SunGuide Status Meeting 3 Agenda TimeItemLead 2:00 – 2:05IntroductionsHsia and all participants 2:05 – 2:25Configuration Management:  CM during development  CM during / after deployment Dellenback / Heller 2:25 – 2:50Districts’ TMC and Software Deployment Schedule Updates (Sorted by scheduled or planned deployment date) Faquir - District 4 Bitting - District 7 Martinez - District 6 Campo - MDX Birosak - District 1 Vega - District 2 Rivera - District 5 McCrary - District 3 Birenbaum - Turnpike Enterprise 2:50 – 2:55MOU between FDOT and TxDOT, Software License Updates: TransGuide, and TxSoftware Sublicense Modification for D2 Hsia / Dellenback 2:55 – 3:15Computer Size Estimates for TMC Dellenback 3:15 – 3:30Break 3:30 – 4:00 Project Status Report:  Development status  GUI / Map Screen Snapshots  Cost and schedule status  Action item follow-up Dellenback 4:00 – 4:15New device drivers:  Driver details  Cost and schedule Dellenback 4:15 – 4:30Open Discussion / Action Item Summary Dellenback

4. March 9, 2004SunGuide Status Meeting 4 Configuration Management Definition: The process of selecting items whose configuration and change status will be controlled (baseline items), defining the process by which those items will be controlled, and then implementing that process. Following slides: –Project view of CM –Statewide view of CM

5. March 9, 2004SunGuide Status Meeting 5 Project View of CM

6. March 9, 2004SunGuide Status Meeting 6 SunGuide SM Software CM Requirement Scope of Services Requires –Use of Rational© ClearCase© for Configuration Management (CM) –Initial delivery of CM baseline corresponding to software before modifications –Delivery of CM repositories with each release

7. March 9, 2004SunGuide Status Meeting 7 CM Repositories Active Repositories –ClearCase repository utilized for baselines –Microsoft© Visual Source Safe© (VSS) for daily development –Department repository per SwRI Software Engineering Process (SEI CMM-Level 3) –Project web-site for delivered documents Backed up daily through Division IT services

8. March 9, 2004SunGuide Status Meeting 8 Daily CM Process Visual Source Safe is tightly integrated with Microsoft Visual Studio Developers responsible for check-in and check-out cycles: –Encourage daily check-in / check-out –Facilitates coordinated builds –Multiple projects under VSS are active MS Windows share backed up by Division IT group

9. March 9, 2004SunGuide Status Meeting 9 Department Process Repository All artifact deliveries to FDOT placed in department CM repository: –Maintained by administrative support staff –Part of SEI CMM approved process –Backed up by Division IT group

10. March 9, 2004SunGuide Status Meeting 10 SunGuide.datasys.swri.edu Project Web Site Contains copies of all deliverables Maintained by project staff Updated as deliveries made via email Source backed up by division IT group

11. March 9, 2004SunGuide Status Meeting 11 ClearCase Repository Initial Baseline (delivered) consists of source code and documents from –Chart II Incident Management –TxDOT Traffic Operations Division Deferred baselined source code: –TransGuide Three More baselines anticipated –Release 1 –Release 2a –Release 2b Resides on Microsoft Windows share Backed up by Division IT group

12. March 9, 2004SunGuide Status Meeting 12 Baseline Release Preparation Prior to release of baseline perform –Functional Configuration Audit Formal test Report is written –Physical Configuration Audit Delivery media prepared Delivery media all “parts” to build baseline Report is written Copy to Department Repository

13. March 9, 2004SunGuide Status Meeting 13 Statewide View of CM

14. March 9, 2004SunGuide Status Meeting 14 CM Common Terms Baseline Item: A product of an effort which is to be maintained under configuration management. Typical baseline items include plans, ITS Architectures, Standards, specifications, and software source code. Engineering Change Requests (ECRs): A formal request for a change to requirements. Configuration Management Board (CMB): A group of people responsible for evaluating and approving or disapproving proposed changes to baseline items, and for ensuring implementation of approved changes. Configuration Manager: Person selected by the CMB to manage the configuration management activities; including the oversight of the CMB.

15. March 9, 2004SunGuide Status Meeting 15 Statewide Perspective Centralized Baseline Issue submission CMB composition and purpose Configuration Management Process

16. March 9, 2004SunGuide Status Meeting 16 CM Centralized Baseline Master SunGuide SM products are stored in a central location: –Documents –Source code –Installation scripts For each active development project: –Code copied to a project repository –Development occurs against the local repository –After acceptance testing, moved back to statewide location

17. March 9, 2004SunGuide Status Meeting 17 CM Issue Submission ECR is submitted Reviewed by CMB If approved: –ECP (Engineering Change Proposal) that contains cost and schedule –If ECP is approved: ECO (Engineering Change Order) issued

18. March 9, 2004SunGuide Status Meeting 18 CM CMB Purpose –Select Configuration Manager –Evaluate proposed changes (ECRs) –Approve/Disapprove ECRs –Interact with Other Organizations

19. March 9, 2004SunGuide Status Meeting 19 CMB Composition

20. March 9, 2004SunGuide Status Meeting 20 CM Process - Summary Identify Issue Review Locally and Resolve (if possible) Develop and Submit ECR to Statewide System Review ECR with CMB If ECR approved, software developer generates a ECP that contains cost and schedule FDOT reviews and approves ECP and provides a ECO to the software developer Software developer implements ECO Release product Install product

21. March 9, 2004SunGuide Status Meeting 21 CM Questions / Comments

22. March 9, 2004SunGuide Status Meeting 22 Agenda TimeItemLead 2:00 – 2:05IntroductionsHsia and all participants 2:05 – 2:25Configuration Management:  CM during development  CM during / after deployment Dellenback / Heller 2:25 – 2:50Districts’ TMC and Software Deployment Schedule Updates (Sorted by scheduled or planned deployment date) Faquir - District 4 Bitting - District 7 Martinez - District 6 Campo - MDX Birosak - District 1 Vega - District 2 Rivera - District 5 McCrary - District 3 Birenbaum - Turnpike Enterprise 2:50 – 2:55MOU between FDOT and TxDOT, Software License Updates: TransGuide, and TxSoftware Sublicense Modification for D2 Hsia / Dellenback 2:55 – 3:15Computer Size Estimates for TMC Dellenback 3:15 – 3:30Break 3:30 – 4:00 Project Status Report:  Development status  GUI / Map Screen Snapshots  Cost and schedule status  Action item follow-up Dellenback 4:00 – 4:15New device drivers:  Driver details  Cost and schedule Dellenback 4:15 – 4:30Open Discussion / Action Item Summary Dellenback

23. March 9, 2004SunGuide Status Meeting 23 Discussion Topics Status of current ITS construction projects Planned ITS deployments Deployment specific questions: –Server operating system: Microsoft Server 2000 Microsoft Server 2003 –Workstation operating system: Microsoft Server XP

24. March 9, 2004SunGuide Status Meeting 24 Agenda TimeItemLead 2:00 – 2:05IntroductionsHsia and all participants 2:05 – 2:25Configuration Management:  CM during development  CM during / after deployment Dellenback / Heller 2:25 – 2:50Districts’ TMC and Software Deployment Schedule Updates (Sorted by scheduled or planned deployment date) Faquir - District 4 Bitting - District 7 Martinez - District 6 Campo - MDX Birosak - District 1 Vega - District 2 Rivera - District 5 McCrary - District 3 Birenbaum - Turnpike Enterprise 2:50 – 2:55MOU between FDOT and TxDOT, Software License Updates: TransGuide, and TxSoftware Sublicense Modification for D2 Hsia / Dellenback 2:55 – 3:15Computer Size Estimates for TMC Dellenback 3:15 – 3:30Break 3:30 – 4:00 Project Status Report:  Development status  GUI / Map Screen Snapshots  Cost and schedule status  Action item follow-up Dellenback 4:00 – 4:15New device drivers:  Driver details  Cost and schedule Dellenback 4:15 – 4:30Open Discussion / Action Item Summary Dellenback

25. March 9, 2004SunGuide Status Meeting 25 Software License Issues SwRI / FDOT License –License executed before the contract started. –TxDOT informed SwRI on January 22, 2004 that TransGuide software was on “hold”. TxDOT / FDOT MOU –FDOT provided TxDOT with comments and legal opinion on March 2, 2004 FDOT / TransGuide License –FDOT provided TxDOT with customized License Agreement on February 19, 2004 SwRI / FDOT Sublicense for District 2 FDOT / WsDOT Term of Use FDOT / MDX Joint Program Agreement (JPA)

26. March 9, 2004SunGuide Status Meeting 26 Agenda TimeItemLead 2:00 – 2:05IntroductionsHsia and all participants 2:05 – 2:25Configuration Management:  CM during development  CM during / after deployment Dellenback / Heller 2:25 – 2:50Districts’ TMC and Software Deployment Schedule Updates (Sorted by scheduled or planned deployment date) Faquir - District 4 Bitting - District 7 Martinez - District 6 Campo - MDX Birosak - District 1 Vega - District 2 Rivera - District 5 McCrary - District 3 Birenbaum - Turnpike Enterprise 2:50 – 2:55MOU between FDOT and TxDOT, Software License Updates: TransGuide, and TxSoftware Sublicense Modification for D2 Hsia / Dellenback 2:55 – 3:15Computer Size Estimates for TMC Dellenback 3:15 – 3:30Break 3:30 – 4:00 Project Status Report:  Development status  GUI / Map Screen Snapshots  Cost and schedule status  Action item follow-up Dellenback 4:00 – 4:15New device drivers:  Driver details  Cost and schedule Dellenback 4:15 – 4:30Open Discussion / Action Item Summary Dellenback

27. March 9, 2004SunGuide Status Meeting 27 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.

28. March 9, 2004SunGuide Status Meeting 28 Computer Sizing Estimates: Conceptual Deployment

29. March 9, 2004SunGuide Status Meeting 29 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 SunGuide SM Database Server (these requirements will vary widely based on how much data the SunGuide SM implementation chooses to log and the backup policies implemented by the SunGuide SM 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) SunGuide SM Application Servers (SunGuide SM processes): –Microsoft Server 2000 –Executive Handler –> 2.4 GHz processor –1 GB RAM –36 GB of disk

30. March 9, 2004SunGuide Status Meeting 30 Sizing Table 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

31. March 9, 2004SunGuide Status Meeting 31 Sample Exercise Assumed: –100 DMSs –200 Detectors –10 simultaneous uses Summary: –Need a database server –3 dual processor application servers (provides growth capacity) Note: –Size estimates will be re- evaluated after integration (and probably go down) Application Servers Only

32. March 9, 2004SunGuide Status Meeting 32 Agenda TimeItemLead 2:00 – 2:05IntroductionsHsia and all participants 2:05 – 2:25Configuration Management:  CM during development  CM during / after deployment Dellenback / Heller 2:25 – 2:50Districts’ TMC and Software Deployment Schedule Updates (Sorted by scheduled or planned deployment date) Faquir - District 4 Bitting - District 7 Martinez - District 6 Campo - MDX Birosak - District 1 Vega - District 2 Rivera - District 5 McCrary - District 3 Birenbaum - Turnpike Enterprise 2:50 – 2:55MOU between FDOT and TxDOT, Software License Updates: TransGuide, and TxSoftware Sublicense Modification for D2 Hsia / Dellenback 2:55 – 3:15Computer Size Estimates for TMC Dellenback 3:15 – 3:30Break 3:30 – 4:00 Project Status Report:  Development status  GUI / Map Screen Snapshots  Cost and schedule status  Action item follow-up Dellenback 4:00 – 4:15New device drivers:  Driver details  Cost and schedule Dellenback 4:15 – 4:30Open Discussion / Action Item Summary Dellenback

33. March 9, 2004SunGuide Status Meeting 33 Agenda TimeItemLead 2:00 – 2:05IntroductionsHsia and all participants 2:05 – 2:25Configuration Management:  CM during development  CM during / after deployment Dellenback / Heller 2:25 – 2:50Districts’ TMC and Software Deployment Schedule Updates (Sorted by scheduled or planned deployment date) Faquir - District 4 Bitting - District 7 Martinez - District 6 Campo - MDX Birosak - District 1 Vega - District 2 Rivera - District 5 McCrary - District 3 Birenbaum - Turnpike Enterprise 2:50 – 2:55MOU between FDOT and TxDOT, Software License Updates: TransGuide, and TxSoftware Sublicense Modification for D2 Hsia / Dellenback 2:55 – 3:15Computer Size Estimates for TMC Dellenback 3:15 – 3:30Break 3:30 – 4:00 Project Status Report:  Development status  GUI / Map Screen Snapshots  Cost and schedule status  Action item follow-up Dellenback 4:00 – 4:15New device drivers:  Driver details  Cost and schedule Dellenback 4:15 – 4:30Open Discussion / Action Item Summary Dellenback

34. March 9, 2004SunGuide Status Meeting 34 Project Web Site http://sunguide.datasys.swri.edu

35. March 9, 2004SunGuide Status Meeting 35 Release-Oriented Development Approach Release 1 Release 2a Release 2b not in scope

36. March 9, 2004SunGuide Status Meeting 36 Scope of SunGuide SM 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 SM protocol –RWIS –Archive data –HAR –Web server –Emergency evacuation Release 2b: –Inventory and maintenance

37. March 9, 2004SunGuide Status Meeting 37 Status 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

38. March 9, 2004SunGuide Status Meeting 38 Status of Release 2a Activities CCTV subsystem, drivers for: –SunGuide SM protocol camera support – stopped per FDOT request Ramp Metering: –Developing requirements –Plan to perform a site visit to WashDOT operations facility

39. March 9, 2004SunGuide Status Meeting 39 Screens: Executive Handler

40. March 9, 2004SunGuide Status Meeting 40 Screens: Executive Handler - continued

41. March 9, 2004SunGuide Status Meeting 41 Screens: Maps

42. March 9, 2004SunGuide Status Meeting 42 Screens: Maps - continued

43. March 9, 2004SunGuide Status Meeting 43 Screens: XML Client Tester

44. March 9, 2004SunGuide Status Meeting 44 Deliverable Status Pending: –Final version of Software Requirements Specification Future documents: –Software Design Document: HTML based See next page –Software Acceptance Test Plan –Software Integration Plan All available on project web site.

45. March 9, 2004SunGuide Status Meeting 45 SDD Snapshots

46. March 9, 2004SunGuide Status Meeting 46 Cost Status Release 1: –Budget amount: $3,208,052 –As of 2/11/04, ~$997,000 has been expended Release 2a: –Budget amount: $2,074,276 –As of 1/2/04, $34,631 has been expended Release 2b: –Budget amount: $245,311 –As of 1/2/04, $0 has been expended

47. March 9, 2004SunGuide Status Meeting 47 Schedule Status Current schedule is posted to project web site Overall project status: –Ahead in many places –SunGuide SM is operational in the lab: Support processes (executive, logging) GUI Map Data Bus DMS: –Mark IV –NTCIP CCTV: –Master process –NTCIP driver –“Pelco” driver (for testing purposes only) TSS: –Master process –Simulator process (up to 1000’s of detectors) Incident management

48. March 9, 2004SunGuide Status Meeting 48 Schedule Status - continued Current areas of concern: –Documents: None –Lack of final device drivers –Baseline software (TransGuide component)

49. March 9, 2004SunGuide Status Meeting 49 Schedule Status - continued

50. March 9, 2004SunGuide Status Meeting 50 DMS Functional Thread: GUI - Data Bus – DMS Subsystem - Device

51. March 9, 2004SunGuide Status Meeting 51 CCTV Functional Thread: XML Simulator - Data Bus – CCTV Subsystem - Device

52. March 9, 2004SunGuide Status Meeting 52 TSS Functional Thread: Device Simulator - TSS Subsystem - Data Bus – XML Simulator

53. March 9, 2004SunGuide Status Meeting 53 Schedule Status - continued Project status meeting after ITS America (April 26 – 28 in San Antonio) on April 29th –Agenda: Project status See SunGuide SM operating in a multi-server, multi- workstation environment with REAL EQUIPMENT Meet the development team DMS Milestone Demo: –District 4: Schedule still being evaluated

54. March 9, 2004SunGuide Status Meeting 54 SwRI Development Labs

55. March 9, 2004SunGuide Status Meeting 55 Action Items

56. March 9, 2004SunGuide Status Meeting 56 Action Items - continued

57. March 9, 2004SunGuide Status Meeting 57 Action Items - continued

58. March 9, 2004SunGuide Status Meeting 58 General Comments / Feedback on Project Status

59. March 9, 2004SunGuide Status Meeting 59 Agenda TimeItemLead 2:00 – 2:05IntroductionsHsia and all participants 2:05 – 2:25Configuration Management:  CM during development  CM during / after deployment Dellenback / Heller 2:25 – 2:50Districts’ TMC and Software Deployment Schedule Updates (Sorted by scheduled or planned deployment date) Faquir - District 4 Bitting - District 7 Martinez - District 6 Campo - MDX Birosak - District 1 Vega - District 2 Rivera - District 5 McCrary - District 3 Birenbaum - Turnpike Enterprise 2:50 – 2:55MOU between FDOT and TxDOT, Software License Updates: TransGuide, and TxSoftware Sublicense Modification for D2 Hsia / Dellenback 2:55 – 3:15Computer Size Estimates for TMC Dellenback 3:15 – 3:30Break 3:30 – 4:00 Project Status Report:  Development status  GUI / Map Screen Snapshots  Cost and schedule status  Action item follow-up Dellenback 4:00 – 4:15New device drivers:  Driver details  Cost and schedule Dellenback 4:15 – 4:30Open Discussion / Action Item Summary Dellenback

60. March 9, 2004SunGuide Status Meeting 60 Draft Contract Amendment List: Sent by Central ITS Office on 2/9/04

61. March 9, 2004SunGuide Status Meeting 61 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

62. March 9, 2004SunGuide Status Meeting 62 Device Drivers In BAFO That Were Approved For Implementation DMS: –NTCIP –Mark IV (v 2.5) CCTV (Cameras): –NTCIP –SunGuide SM (Stopped development) Video Switch: –American Dynamics 2050 (Stopped development) Traffic Detectors: –BiTrans 238I-95 Ramp Metering: –WsDOT (firmware) RWIS: –NTCIP HAR

63. March 9, 2004SunGuide Status Meeting 63 SwRI Asked To Evaluate Adding New Devices to Development 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

64. March 9, 2004SunGuide Status Meeting 64 All Development Efforts Include… The device driver compliant with the appropriate SunGuide SM device driver Interface Control Document (ICD). Development efforts will include: –Design –Peer Review –Implementation –Testing –Integration

65. March 9, 2004SunGuide Status Meeting 65 IP Video Scope: –SwRI will develop an IP-Video video switch device driver that will instruct “decoders” to listen to “encoders”. –The device driver will issue SNMP commands to the following decoders: CorTec Teleste VBrick iMpath Assumptions: –SwRI will not be performing inter-operability testing between different brands of encoders and decoders.

66. March 9, 2004SunGuide Status Meeting 66 RTMS TSS Device Driver(s) Scope: –A device driver for a Electronic Integrated System (EIS) RTMS device will be developed. –A device driver for a Wavetronix SmartSensor device will be developed. –A device driver for a 3M Canoga, model C400/C800/C990E device will be developed. 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. –TCP/IP interface of the Wavetronix RTMS device shall be used to retrieve data. –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. Notes: –Concurrent development of these drivers will results in a cost savings.

67. March 9, 2004SunGuide Status Meeting 67 Trailblazer Device Driver and GUI Support Scope: –Develop a device driver (to be included in the DMS subsystem) to support Trailblazer devices, SunGuide SM 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).

68. March 9, 2004SunGuide Status Meeting 68 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 SunGuide SM software framework Assumptions: –FDOT will procure all devices –All NTCIP compliance testing to be performed by FDOT (TERL) –No software development effort by SwRI

69. March 9, 2004SunGuide Status Meeting 69 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 SunGuide SM 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. –Non-disclosure has been put in place – waiting for technical detail.

70. March 9, 2004SunGuide Status Meeting 70 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 SunGuide SM CCTV Video Switch Interface Control Document (ICD) interface Video wall configuration software: –SwRI will extend the SunGuide SM GUI to allow the Barco video wall to be reconfigured using SunGuide SM 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. 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.

71. March 9, 2004SunGuide Status Meeting 71 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

72. March 9, 2004SunGuide Status Meeting 72 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

73. March 9, 2004SunGuide Status Meeting 73 Device Driver Costs - continued Cost reductions: –CCTV American Dynamics Driver:~$69,000 –CCTV SunGuide SM Driver:~$52,000 Net cost impact to project: –Additions:$1,182,317 –Reductions: $123,000 –NET:$1,061,317

74. March 9, 2004SunGuide Status Meeting 74 Tentative Schedule

75. March 9, 2004SunGuide Status Meeting 75 Agenda TimeItemLead 2:00 – 2:05IntroductionsHsia and all participants 2:05 – 2:25Configuration Management:  CM during development  CM during / after deployment Dellenback / Heller 2:25 – 2:50Districts’ TMC and Software Deployment Schedule Updates (Sorted by scheduled or planned deployment date) Faquir - District 4 Bitting - District 7 Martinez - District 6 Campo - MDX Birosak - District 1 Vega - District 2 Rivera - District 5 McCrary - District 3 Birenbaum - Turnpike Enterprise 2:50 – 2:55MOU between FDOT and TxDOT, Software License Updates: TransGuide, and TxSoftware Sublicense Modification for D2 Hsia / Dellenback 2:55 – 3:15Computer Size Estimates for TMC Dellenback 3:15 – 3:30Break 3:30 – 4:00 Project Status Report:  Development status  GUI / Map Screen Snapshots  Cost and schedule status  Action item follow-up Dellenback 4:00 – 4:15New device drivers:  Driver details  Cost and schedule Dellenback 4:15 – 4:30Open Discussion / Action Item Summary Dellenback

76. March 9, 2004SunGuide Status Meeting 76 Future Meetings Outreach Meeting: March 10 th (1:45 to 2:00) Next Status Meeting: –April 29 th (in conjunction with ITS America): Status Report Significant software demonstration Need to schedule: –Software Design Review Need to confirm: –May Status Meeting –June Status Meeting

77. March 9, 2004SunGuide Status Meeting 77 Questions / Comments

78. March 9, 2004SunGuide Status Meeting 78 Action Item Recap NumberPersonAction 39 40 41 42 43 44 45