1 / 100

Statewide Transportation Management Center Software Library System Kick-Off Meeting November 13, 2003

November 13, 2003. STMCSLS Kickoff Meeting. 2. Agenda. November 13, 2003. STMCSLS Kickoff Meeting. 3. Project Team Structure. November 13, 2003. STMCSLS Kickoff Meeting. 4. Team Organization. November 13, 2003. STMCSLS Kickoff Meeting. 5. License Discussion / Software Baseline. November 13, 2003. STMCSLS Kickoff Meeting.

omar
Download Presentation

Statewide Transportation Management Center Software Library System Kick-Off Meeting November 13, 2003

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Statewide Transportation Management Center Software Library System Kick-Off Meeting November 13, 2003

    2. November 13, 2003 STMCSLS Kickoff Meeting 2 Agenda

    3. November 13, 2003 STMCSLS Kickoff Meeting 3 Project Team Structure

    4. November 13, 2003 STMCSLS Kickoff Meeting 4 Team Organization

    5. November 13, 2003 STMCSLS Kickoff Meeting 5 License Discussion / Software Baseline

    6. November 13, 2003 STMCSLS Kickoff Meeting 6 Software Ownership TxDOT Software: Requires license with TxDOT (or through SwRI) TxDOT requests updates to be provided Maryland Software: Freely available by requesting from CHART No formal licensing required MIST® Device Drivers: PBF will provide driver (source code) to FDOT No restrictions on drivers delivered Vendor Protocols: No cost agreement with vendors

    7. November 13, 2003 STMCSLS Kickoff Meeting 7 SwRI / TxDOT License TxDOT proprietary notices within software and documentation will be maintained SwRI will return or certify destruction of all materials upon termination of agreement SwRI will maintain a coordinated issues database SwRI agrees to provide TxDOT, at no cost, the source and documentation for any modification and enhancements made to TxDOT software TxDOT has no claim on new software developed

    8. November 13, 2003 STMCSLS Kickoff Meeting 8 SwRI / FDOT Sublicense – con’t Limited to use for internal purposes in the geographical limits of FDOT, FDOT may distribute binaries within Florida Requires SwRI provide TxDOT copies of all modifications, enhancements, and documentation updates made to the TxDOT software FDOT may make additional changes themselves or through another contractor. changes must be provided back to SwRI with documentation updates FDOT may not issue sub-licenses

    9. November 13, 2003 STMCSLS Kickoff Meeting 9 DRAFT: Proposed FDOT / TxDOT Memo of Understanding TxDOT and FDOT are parties to the MOU; however, others may be invited to join if they are willing to accept the terms of the MOU TxDOT will provide the TxDOT software to FDOT FDOT will be allowed to take ownership of the TxDOT software source code within Florida FDOT may provide the TxDOT software executables to any Florida public sector transportation agency TxDOT and FDOT will share all changes, modifications, and enhancements to the TxDOT software This ITS-related software partnership will be for an indefinite term. Either TxDOT or FDOT may unilaterally terminate the partnership with sufficient notice Correspondence and/or documentation relating to the partnership will be posted to respective web sites of TxDOT and FDOT

    10. November 13, 2003 STMCSLS Kickoff Meeting 10 Ramp Meter Software Ramp Meter Firmware: Owned by Washington State DOT Runs in 170 controllers Controls ramp meter signals based on strategy from ramp meter module Ramp Meter Module: Owned by University of Washington Fuzzy logic based on VAX Issues commands to ramp meter controllers

    11. November 13, 2003 STMCSLS Kickoff Meeting 11 Ramp Meter Firmware License FDOT desires to use WSDOT’s firmware: Multiple queue detectors Satisfies FDOT’s ramp metering control philosophy (e.g., works with fuzzy logic) License to be created between WSDOT and FDOT (PBF to assist in license language). License to cover Florida (others may have to deal with WSDOT): To be finally determined by FDOT/WSDOT This is ancillary to the STMCSLS The two detectors are a “normal” one (normally 500 ft upstream) and a critical one (intersection block). These are dealt with differently in the fuzzy logic.The two detectors are a “normal” one (normally 500 ft upstream) and a critical one (intersection block). These are dealt with differently in the fuzzy logic.

    12. November 13, 2003 STMCSLS Kickoff Meeting 12 Ramp Metering Module License Fuzzy logic code review 11/4/03 concluded code was not particularly useful Coupled with proposed University of Washington license requirements were too restrictive for FDOT’s objectives - no further distribution rights without separate license Conclusion: SwRI / PBF will develop the ramp metering module entirely as priced

    13. November 13, 2003 STMCSLS Kickoff Meeting 13 Software Baseline Information: Significant Reuse Of Existing Software

    14. November 13, 2003 STMCSLS Kickoff Meeting 14 Software Baseline Information: Ownership

    15. November 13, 2003 STMCSLS Kickoff Meeting 15 Budget / Work Plan

    16. November 13, 2003 STMCSLS Kickoff Meeting 16 Project Web Site http://stmcsls.datasys.swri.edu

    17. November 13, 2003 STMCSLS Kickoff Meeting 17 Scope 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

    18. November 13, 2003 STMCSLS Kickoff Meeting 18 Proposed STMCSLS Architecture Robust Extensible Flexible Scalable Configurable Proven

    19. November 13, 2003 STMCSLS Kickoff Meeting 19 Release-Oriented Development Approach Release 1 Release 2a Release 2b not in scope

    20. November 13, 2003 STMCSLS Kickoff Meeting 20 High-Level Design Concepts FDOT provided high-level requirements Scope of work desired maximal reuse Short development period Reuse existing software: Texas Maryland MIST device drivers GUIs: New user interfaces will be developed: Browser Windows Final design will be performance based

    21. November 13, 2003 STMCSLS Kickoff Meeting 21 Overall Features of Architecture Abstraction Layer Executive Handler Data Distribution Security Software Configurability Database Logging

    22. November 13, 2003 STMCSLS Kickoff Meeting 22 Budget for STMCSLS Effort: Release 1

    23. November 13, 2003 STMCSLS Kickoff Meeting 23 Budget for STMCSLS Effort: Release 2a

    24. November 13, 2003 STMCSLS Kickoff Meeting 24 Budget for STMCSLS Effort: Release 2b

    25. November 13, 2003 STMCSLS Kickoff Meeting 25 Budget for STMCSLS Effort: Deployment and Support

    26. November 13, 2003 STMCSLS Kickoff Meeting 26 Detailed Work Plan Comments Received From FDOT Comments received from FDOT on 11/5/2003 Significant comments and SwRI/PBF response: Document format: FDOT provided “standard” format after delivery of document – all future documents will utilize formats provided Additional detail on bulleted tasks: will be added Discussion on potential scope of work modifications needs to occur (will be done during the general discussion portion of this presentation): 360 Surveillance System Center-to-Center

    27. November 13, 2003 STMCSLS Kickoff Meeting 27 Agenda

    28. November 13, 2003 STMCSLS Kickoff Meeting 28 Staffing Plan

    29. November 13, 2003 STMCSLS Kickoff Meeting 29 Team Organization

    30. November 13, 2003 STMCSLS Kickoff Meeting 30 Project Management Project Management Team: PM: Steve Dellenback SPM: Robert Heller DPM: Charles Wallace SPM (PBF): John Schumitz Meetings: FDOT Internal Status Report Implement Software Process

    31. November 13, 2003 STMCSLS Kickoff Meeting 31 Project Management: Monthly Status Reports Activities: Performed previous period To be performed (over next 2 periods) Schedule status Documentation schedule and upcoming deliverables Risks Action item database

    32. November 13, 2003 STMCSLS Kickoff Meeting 32 Project Management: Subcontract Management SwRI generated statement of work PBF response with cost and schedule Performance monitoring Commitments Status (cost and schedule) Planning: upcoming milestones, deliverables, meetings, demonstrations Risk management (evaluate, assess, monitor) Communicate, communicate, communicate: Weekly teleconferences every Monday morning

    33. November 13, 2003 STMCSLS Kickoff Meeting 33 Staffing Plan Comments Received From FDOT Comments received from FDOT on 11/5/2003. Key staff designation: Altered designation for several “key staff” members Significant comments and SwRI/PBF response: Staff changes: When qualifications were submitted (original staff proposed) the ITN award was to be by April 2, 2003 Project was October 7, 2003 Staffing changes are inevitable with a delay of 6 months Resumes are being provided on all new staff (as part of Staffing Plan). Staff changes: New staff: resumes added to staff plan Thompson/Vick: added to table to reflect technical consulting role

    34. November 13, 2003 STMCSLS Kickoff Meeting 34 Staff Assigned

    35. November 13, 2003 STMCSLS Kickoff Meeting 35 Release 1 Staffing Assignments

    36. November 13, 2003 STMCSLS Kickoff Meeting 36 Release 1 Staffing Assignments - continued

    37. November 13, 2003 STMCSLS Kickoff Meeting 37 FDOT Schedule Critical Milestones

    38. Statewide Transportation Management Center Software Library System (STMCSLS) Welcoming remarks Self-introduction of speakerWelcoming remarks Self-introduction of speaker

    39. November 13, 2003 STMCSLS Kickoff Meeting 39 STMCSLS SwRI / FDOT Sublicense Budget / Work Plan FDOT Schedule Critical Milestones Center to Center Communications A Statewide ITS Architecture has already been developed for the state of Florida. Some general information about this project that will be discussed in following slides include: A Statewide ITS Architecture has already been developed for the state of Florida. Some general information about this project that will be discussed in following slides include:

    40. November 13, 2003 STMCSLS Kickoff Meeting 40 Sublicense 09/02/2003 SwRI / FDOT sublicense signed Software ownership & distribution Geographical restriction Statewide versus Department-wide No license fee A Statewide ITS Architecture has already been developed for the state of Florida. Some general information about this project that will be discussed in following slides include: A Statewide ITS Architecture has already been developed for the state of Florida. Some general information about this project that will be discussed in following slides include:

    41. November 13, 2003 STMCSLS Kickoff Meeting 41 District 4 Broward County RTMC

    42. November 13, 2003 STMCSLS Kickoff Meeting 42 District 6 RTMC

    43. November 13, 2003 STMCSLS Kickoff Meeting 43 District 7 RTMC

    44. November 13, 2003 STMCSLS Kickoff Meeting 44 Miami-Dade Expressway (MDX) Authority’s Participation

    45. November 13, 2003 STMCSLS Kickoff Meeting 45 Center to Center (C2C) Communications The National ITS Architecture development process is based on a structured approach that starts with the end user Once the user needs are established, specific system requirements are developed in order to design a system that will satisfy those needsThe National ITS Architecture development process is based on a structured approach that starts with the end user Once the user needs are established, specific system requirements are developed in order to design a system that will satisfy those needs

    46. November 13, 2003 STMCSLS Kickoff Meeting 46 Center to Center (C2C) Communications The National ITS Architecture development process is based on a structured approach that starts with the end user Once the user needs are established, specific system requirements are developed in order to design a system that will satisfy those needsThe National ITS Architecture development process is based on a structured approach that starts with the end user Once the user needs are established, specific system requirements are developed in order to design a system that will satisfy those needs

    47. November 13, 2003 STMCSLS Kickoff Meeting 47 Michigan DOT’s Participation

    48. November 13, 2003 STMCSLS Kickoff Meeting 48 STMCSLS Budget in Ten-Year ITS Cost Feasible Plan (Programmed Dollars in Millions) Funding Source FY 03-04 FY 04-05 FY 05-06 FY06-07 FY07-08   1. STMCSLS* 5.01 0.75 0.75 0.17 0.17 2. District 6 0.50 (Ramp Metering)   3. MDX   *Note: On February 13, 2002, the Michigan DOT affirmed its commitment to co-sponsor this activity. In addition to FDOT's monies, MDOT has committed $500,000 in each of these five fiscal years and beyond. A Statewide ITS Architecture has already been developed for the state of Florida. Some general information about this project that will be discussed in following slides include: A Statewide ITS Architecture has already been developed for the state of Florida. Some general information about this project that will be discussed in following slides include:

    49. November 13, 2003 STMCSLS Kickoff Meeting 49 STMCSLS Budget in Ten-Year ITS Cost Feasible Plan (Programmed Dollars in Millions) Funding Source FY 08-09 FY 09-10 FY 10-11 FY11-12   1. STMCSLS* 0.18 0.18 0.19 0.19 2. District 6 (Ramp Metering)   3. MDX   *Note: Total $8.09 Million A Statewide ITS Architecture has already been developed for the state of Florida. Some general information about this project that will be discussed in following slides include: A Statewide ITS Architecture has already been developed for the state of Florida. Some general information about this project that will be discussed in following slides include:

    50. November 13, 2003 STMCSLS Kickoff Meeting 50 SwRI Schedule

    51. November 13, 2003 STMCSLS Kickoff Meeting 51 Schedule Philosophy Precedence Relationships taken from Scope of Services Modified by detailed work plan Document deliveries integrated Release 1, 2a, 2b arranged to take advantage of staff availability from one release to next, non-overlap of testing Critical paths computed by Microsoft Project Includes all tasks with no successor tasks Critical path hidden by task rollup Only Release 1 was resource loaded Software “reuse” efforts begin before design review

    52. November 13, 2003 STMCSLS Kickoff Meeting 52 Project Management Schedule

    53. November 13, 2003 STMCSLS Kickoff Meeting 53 Release 1 Schedule

    54. November 13, 2003 STMCSLS Kickoff Meeting 54 Release 2a Schedule

    55. November 13, 2003 STMCSLS Kickoff Meeting 55 Release 2b Schedule

    56. November 13, 2003 STMCSLS Kickoff Meeting 56 Deployment and Support

    57. November 13, 2003 STMCSLS Kickoff Meeting 57 Schedule Summary STMCSLS development team: Release 1: September 2004 Release 2a: August 2005 Release 2b: November 2005 Milestone demo: anytime after March 1, 2004 Broward County and Miami: Broward: No access to center until contractor is done CCTV / video switch solution to be selected later this year, early next year Miami: move in March 2004, 90 day “burn-in”

    58. November 13, 2003 STMCSLS Kickoff Meeting 58 General Schedule Discussions … Comments from Everyone …

    59. November 13, 2003 STMCSLS Kickoff Meeting 59 Agenda

    60. November 13, 2003 STMCSLS Kickoff Meeting 60 Project Risks

    61. November 13, 2003 STMCSLS Kickoff Meeting 61 Risk Management Process SwRI PM (Dellenback) is Risk Manager Risk Management Cycle Depicted is Continuous: Risk Identification Risk Analysis Risk Prioritization Risk Planning Risk Monitoring Risk Manager Identifies: Owner: PM, SPM, DPM, PB SPM, FDOT Identifier: Technical, Operational, Schedule, Organizational, Legal or Contractual Likelihood: High, Medium, Low Impact: High, Medium, Low Ranking: Product of Likelihood and Impact Controls: Methods of Risk Mitigation Status: Open, Closed

    62. November 13, 2003 STMCSLS Kickoff Meeting 62 Technical Risks

    63. November 13, 2003 STMCSLS Kickoff Meeting 63 Technical Risks - continued

    64. November 13, 2003 STMCSLS Kickoff Meeting 64 Technical Risks - continued

    65. November 13, 2003 STMCSLS Kickoff Meeting 65 Operational Risks

    66. November 13, 2003 STMCSLS Kickoff Meeting 66 Schedule Risks

    67. November 13, 2003 STMCSLS Kickoff Meeting 67 Legal and Contractual Risks

    68. November 13, 2003 STMCSLS Kickoff Meeting 68 Organizational Risks

    69. November 13, 2003 STMCSLS Kickoff Meeting 69 Concept of Operations (or High Level Design)

    70. November 13, 2003 STMCSLS Kickoff Meeting 70 General Concept User interfaces: Separate from the core system Local thin clients or remote clients via C2C Subsystems: Data passed through Data Bus Use well defined interfaces Data Bus Standard interface Extensible with no code changes

    71. November 13, 2003 STMCSLS Kickoff Meeting 71 Data Bus Concept

    72. November 13, 2003 STMCSLS Kickoff Meeting 72 Data Flow Through the Data Bus

    73. November 13, 2003 STMCSLS Kickoff Meeting 73 Agenda

    74. November 13, 2003 STMCSLS Kickoff Meeting 74 Preliminary Requirements Review

    75. November 13, 2003 STMCSLS Kickoff Meeting 75 Requirements Process Organizing original requirements All original STMCSLS requirements are converted into FEAT (feature) requirements Reorganized the structure of the requirements into subsystems Retained traceability back to the STMCSLS requirement numbers Updated status of requirements appropriately (Approved, FDOT, and Future) Creating System Level Requirements Created new category of requirements (SUB) for subsystems Adds additional functional requirements for the various subsystems SUB requirements are structured in a hierarchical format Each new SUB requirement has traceability to a FEAT requirement

    76. November 13, 2003 STMCSLS Kickoff Meeting 76 Requirements View - continued

    77. November 13, 2003 STMCSLS Kickoff Meeting 77 Requirements View

    78. November 13, 2003 STMCSLS Kickoff Meeting 78 Requirements View - continued

    79. November 13, 2003 STMCSLS Kickoff Meeting 79 Requirements View - continued

    80. November 13, 2003 STMCSLS Kickoff Meeting 80 Requirements Status Completed Requirements DMS CCTV HAR Data Distribution Need to be completed IM (Incident Management) IMS (Inventory and Maintenance) EH (Executive Handler) SL (Status Logger) TSS (Traffic Sensor Subsystem) RWIS (Weather) C2C (Center-to-Center) GUI (Graphical User Interface) DA (Data Archiving) EE (Emergency Evacuation) Proposed Requirements Review: December 11, 2003

    81. November 13, 2003 STMCSLS Kickoff Meeting 81 User Interface Prototype Demonstration

    82. November 13, 2003 STMCSLS Kickoff Meeting 82 GUI Design Issues Implementation approaches: Windows application Browser based application Maintenance (upgrades): Windows application: custom installation Browser: utilizes web services Map data: Windows application: user workstation Browser: web server based

    83. November 13, 2003 STMCSLS Kickoff Meeting 83 Maintenance issues with GUI(s) Windows based application: Configuration management Change management Web based application: Web server maintenance Map data maintenance

    84. November 13, 2003 STMCSLS Kickoff Meeting 84 User Interface Prototype: Software Architecture

    85. November 13, 2003 STMCSLS Kickoff Meeting 85 User Interface Prototype Today’s demo: Local execution 1.8 GHz Laptop Optimal workstation environment is 2.8 GHz to 3.06 GHz with 1 GB RAM Request feedback from FDOT on “look and feel”

    86. November 13, 2003 STMCSLS Kickoff Meeting 86 User Interface Prototype Two options for “thin clients”: Browser based Windows application SwRI recommends: browser based Performance issues: CCTV control possible in “real time” Map complexity can increase refresh time (but an issue no matter the client “type” – more data creates a longer redraw time)

    87. November 13, 2003 STMCSLS Kickoff Meeting 87 User Interface: Maps

    88. November 13, 2003 STMCSLS Kickoff Meeting 88 User Interface: Device View

    89. November 13, 2003 STMCSLS Kickoff Meeting 89 User Interface: DMS Control

    90. November 13, 2003 STMCSLS Kickoff Meeting 90 User Interface: CCTV Control

    91. November 13, 2003 STMCSLS Kickoff Meeting 91 Agenda

    92. November 13, 2003 STMCSLS Kickoff Meeting 92 Proposed Dates to Discuss Software Requirements Review: December 11, 2004 Software Design Review: February 3, 2004 Status Meetings: Dec 11, 2003 Jan 6, 2004 Feb 3, 2004 Mar 3, 2004 – POTENTIAL CONFLICT Apr 6, 2004 ITSA Apr 26 - 29 May 8, 2004 Jun 3, 2004

    93. November 13, 2003 STMCSLS Kickoff Meeting 93 Issues to Discuss CCTV: 360 Surveillance System: Software ownership / distribution Device support Use as a controller / switch Lack of integrated environment IDI (Intelligent Devices Inc.): General concept Device support Center-to-Center (see diagram on next page): Communications (hardware) infrastructure Software infrastructure Oracle licenses (section 3.2.2.6 of Scope of Services) MDX participation

    94. November 13, 2003 STMCSLS Kickoff Meeting 94 Center-to-Center Conceptual View

    95. November 13, 2003 STMCSLS Kickoff Meeting 95 Open Discussion

    96. November 13, 2003 STMCSLS Kickoff Meeting 96 STMCSLS Project Team Contact Information

    97. November 13, 2003 STMCSLS Kickoff Meeting 97 ??? Small Group Meetings December 10 Morning – Miami / Tampa / MDX Afternoon – Broward County December 11 Morning – Orlando / Jacksonville Afternoon - Turnpike Is a formal SRR required? Useful?

    98. November 13, 2003 STMCSLS Kickoff Meeting 98 Action Item Recap

    99. November 13, 2003 STMCSLS Kickoff Meeting 99 Action Item Recap

    100. November 13, 2003 STMCSLS Kickoff Meeting 100 360 Surveillance Concept

    101. November 13, 2003 STMCSLS Kickoff Meeting 101 IDI Device Driver Alternatives

More Related