APPENDIX A. OPERATIONAL PROCESS FLOW CHARTS

Transcription

1 APPENDIX A. OPERATIONAL PROCESS FLOW CHARTS The flow charts on the following pages illustrate the operational processes that could be carried out by the corridor management system envisioned in this requirements document. They show how the various actors in the system (the people and the technical components) could interact to execute a variety of tasks, including: Assessing corridor performance Detecting and verifying incidents Assessing the impact of incidents Creating, reviewing, and approving response plans Reviewing system operations Addressing asset failures 1

2 A.1. INCIDENT RESPONSE CONTROL LOOP NEW INCIDENT OCCURS Incident Management Sy stem updates list of activ e incidents within corridor waits for next incident to occurs NEXT INCIDENT Subsy stem updates model representing current network operations No Active Incident PERIODIC OPERATIONAL REVIEWS (current situation) Activ e Incidents Subsy stem ev aluates current network operations Weekly /monthly reviews of system activities by Corridor Operators Rev iew of operational issues by / Maintenace Staff determine needs for response plan Response Plan Needed Rules Engine identif ies av ailable detours and control alternativ es Response Planning Not Required No f easible alternativ e One or more possible alternativ es Rev iew of important system issues by Corridor Manager and Transportation Managers Rules Engine generates response plans for identified incident(s) Subsy stem ev aluates dev eloped response plans Implementation of recommended adjustments into system by Sy stem Manager Configuration Parameters (alternate scenarios) Rules Engine selects a recommended response plan for implementation sends the selected response plan for implementation Rev iew/approv al of recommended plan by Corridor Operators Recommended plan not approv ed Recommended plan approv ed Response Management Subsystem sends RMS control commands to v arious control dev ices af f ected by response plan Figure A-1 Envisioned Incident Response Control Loop 2

3 A.2. PERIODIC CORRIDOR PERFORMANCE ASSESSMENT Sensors Probe Vehicles Bluetooth Devices Road Closures Incidents Planned Events Continuous Corridor Model Update Elements with realtime data update Subsy stem continuously updates the status of corridor elements using received real-time data Elements without realtime data update Subsy stem uses stored historical data and def ault prof iles Historical Default Profiles & Values Modelers, Operators Modelers, Operators, Managers x min x min x min x min x min x min Configuration Parameters Sy stem Manager sets up the basic metrics reporting interv al (e.g., 5 min, 15 min) System Setup Subsy stem records perf ormance metrics that hav e been compiled over each reporting interval Subsy stem sends compiled metrics to the Analy sis Module retriev es f rom the, and possible other sources relev ant perf ormance statistics for the requested evaluation period Analy sis Module aggregates the retrieved statistics to produce the requested report System User requests through the S User Interface, a corridor-wide performance report for the past hour S User Interface sends a report generation request to the Analysis Module UI S User Interface display s the requested statistics on the terminal used by TMC Operator Analy sis Module summarizes the analy sis results in a PDF f ile Report Generation Figure A-2 Periodic Corridor Performance Evaluation Process 3

4 A.3. INCIDENT/EVENT DETECTION Police Dispatchers Drivers & Passengers Transit Dispatchers Drivers & Passengers Field Personnel First Responders CHP C AD Pasadena Record System County City App retrieves from inf ormation characterizing ty pical roadway conditions f or the current day of week and time of day retrieves from inf ormation characterizing the current operational status of corridor roadway s Sensors Bluetooth Devices Probe Vehicles Incident directly observ ed by TMC operator on CCTV v ideo f eed Agency Personnel receiv es incident inf ormation Incident Inf ormation is receiv ed by TMC Operator retriev es incident inf ormation f rom connected CAD systems v ia generates an Incident Warning message with the location of the incident retriev es Incident inf ormation f rom Crowdsourcing Application (Waze, other) via generates an Incident Warning message with the location of the incident assesses whether unusual congestion exists in the corridor by comparing real-time and historical data If unusual congestion exists, the generates a Congestion Warning message with the location of the problem display for review Incident Warning and Congestion Warning messages on terminal used by all TMC Operators TMC Operator assesses the v alidity of the incident inf ormation receiv ed by rev iewing operational status of corridor elements TMC Operator determines that Incident information is valid TMC Operator instructs to create a new incident record INCIDENT CHARACTERIZATION TMC Operator determines that the incident inf ormation is not valid INFORMATION DISCARDED Field Personnel If needed, TMC Operator uses the S User Interf ace to consult most recent performance evaluations Figure A-3 Incident Detection and Verification Process 4

5 EM ERGENCY LANE/ROAD CLOSURES Transit Dispatchers Field Maintenance Personnel First Responders PLANNED LANE/ROAD CLOSURES Caltrans LCS County Road Closures City A Road Closures City B Road Closures CONTROL DEVICE FAILURE Lane closure/ev ent directly observ ed by TMC operator on CCTV v ideo f eed Agency Personnel receiv es incident inf ormation Incident Inf ormation is receiv ed by TMC Operator retriev es f rom f ault data receiv ed f rom connected traffic control systems display f or rev iew receiv ed Lane Closure and Control Dev ice Fault messages on terminal used by all TMC Operators retriev es f rom f ault data receiv ed f rom connected traffic control systems TMC Operator assesses the v alidity of the incident inf ormation receiv ed by rev iewing operational status of corridor elements TMC Operator determines that Incident inf ormation is v alid TMC Operator instructs to create a new incident record TMC Operator determines that the incident inf ormation is not v alid Field Personnel If needed, TMC Operator uses the S User Interf ace to consult most recent perf ormance ev aluations INCIDENT CHARACTERIZATION INFORMATION DISCARDED Figure A-4 Event Detection and Verification Process 5

6 NEW VALID INCIDENT creates new incident record assigns incident ID to the identif ied incident pre-populates incident record with data supplied by connected inf ormation sy stems CAD system supplies basic incident inf ormation Location Lanes af f ected CAD Incident record is edited/completed by TMC Operator TMC Operator assess incident characteristics Expected duration Sev erity based on incident ty pe TMC Operator checks incident details CCTV camera Reports f rom f ield personnel CAD systems Corridor status f rom reports CAD Completed incident record is v alidated by TMC Operator adds the new incident record to a list of activ e incidents DETERM INATION OF RESPONSE PLANNING NEED Figure A-5 Incident Characterization Process 6

7 A.4. ONLINE CORRIDOR MODEL ADJUSTMENTS M ODEL UPDATE REQUEST (e.g., followingan incident) Subsy stem retriev es the corridor model representing current operations (Current Model) Subsy stem retriev es f rom a list of incidents that hav e been recently terminated Subsy stem remov es f rom Current Model all incidents that hav e been terminated Subsy stem retriev es f rom a list of activ e incidents Subsy stem compares list of activ e incidents f rom with ev ents def ined in Current Model Subsy stem retriev es f rom data characterizing the current status of control dev ices: - Current timing plan - Current metering rate - Current posted messages Subsy stem adjusts if necessary the status the f ollowing modeled control dev ices in Current Model: - Traf f ic signals - meters - Changeable message signs Subsy stem retriev es f rom real-time data characterizing the current status of roadway elements - Flow rates - Queue length - Density - Etc, CMS Sensors Bluetooth Devices Probe Vehicles incident list dif f er f rom list of incidents coded in Current Model Subsy stem remov es f rom Current Model all incidents no longer on the list Subsy stem adds in Current Model incidents on list not already coded in the model. Subsy stem adjusts in Current Model the characteristics of incidents already def ined in model to match incidents in list Incident in list identical to incidents coded in Current Model Subsy stem estimates traffic conditions on indiv idual roadway links within the modeled network area Subsy stem adjusts, if necessary, the f ollowing elements in Current Model: - Roadway characteristics - Trav el demand - Network f low pattern Subsy stem stores an updated v ersion of Current Model f or use in subsequent system activities Figure A-6 Corridor Model Online Adjustment Process 7

8 A.5. INCIDENT/EVENT IMPACT ASSESSMENT (RESPONSE NEED ASSESSMENT) NEW INCIDENT/EVENT requests f rom Subsy stem an ev aluation of corridor operations ov er next hour with and without the identif ied incidents requests f rom Incident Management System a list of activ e incidents within the corridor SS Sybsystem retrieves corridor model representing current operations No activ e incident is receiv ed Activ e incidents are receiv ed Subsy stem projects corridor operations Subsy stem projects corridor operations ov er next hour f or the f ollowing two scenarios: ov er next hour f or the f ollowing two scenarios: - Current Network without Incident - Current Network without Incident - Current Network with Incident - Current Network with Incident Subsy stem stores simulation results f or potential later use NO FURTHER ACTION IS CONSIDERED receiv es simulation results f rom the Subsy stem uses simulation results to quantif ies the impacts of activ e incidents on corridor operations Corridor Operators & Managers Configuration Parameters ev aluates whether the ev aluated impacts exceed user-def ined thresholds Impacts exceed userdef ined thresholds Impacts do not exceed user-def ined thresholds stores ev aluation results f or potential later use RESPONSE PLANNING INITIATED NO FURTHER ACTION CONSIDERED Figure A-7 Incident/Event Impact Assessment Process 8

9 A.6. RESPONSE PLAN CREATION POSITIVE RESPONSE PLANNING DECISION retriev es list of activ e incident f rom Incident Management Sy stem Rules Egine identif ies av ailable alternate route(s) around congested corridor elements considering: - Severity - Available roadway capacity - Asset av ailability - User-def ined operational constraints Operational Constraints Corridor Operators & Managers retriev es f rom storage simulation results f or the Current Network with Incident scenario ( Do nothing scenario ) assesses the ov erall operational sev erity of active incidents based on simulation results and produces an overall severity rating No f easible alternate route NO RESPONSE PLAN DEVELOPED One or more f easible alternate route(s) Rules Egine identif ies appropriate control strategies for each identified alternat route - Timing plan change - Change of ramp metering rate Rules Egine identif ies an approprioate information dissemination strategy Control Preferences CMS If required, TMC Operator rev iews and approves/modify the proposed severity rating retriev es real-time data characterizing the av ailability of traffic control devices within the corridor For each alternate route, requests a simulation ev aluation of corridor operations over next hour Subsy stem projects corridor operations Subsy stem projects corridor operations over next hour Subsy for each stemdeveloped projects corridor alternative operations over next hour for each developed alternative over next hour for each developed alternative Sensors Bluetooth Devices Probe retriev es f rom current status data for corridor roadway elements uses retriev ed real-time data to compute av ailable capacity along f reeway and arterial segments receiv es simulation results from Subsystem computes perf ormance metrics f or each alternativ e, including a do nothing scenario (Current Network with Incident scenario) uses computed perf ormance metrics to identify a recommended response plan. RESPONSE RECOMMENDATION stores simulation and recommendation details for later use logs summary of recent activ ities Memory Figure A-8 Response Plan Creation Envisioned Process 9

10 A.7. RESPONSE PLAN REVIEW/APPROVAL RESPONSE RECOMMENDATION sends the recommended response plan to the Response Management Sy stem (RMS) RMS identif ies the control dev ices that each agency is requested to change to implement the recommended response plan RMS = Incident Management System = Decision Support System IMPL = Implementation Module RMS checks whether plan approv al is required f rom each af f ected agencies RMS Agency staf f approv al required RMS sends control change requests to each agency af f ected by the recommended response plan RMS Sensors Bluetooth Devices Agency staf f approv al not required TMC Operator or Manager f rom TMC Operator/Manager of Agency TMC X Operator/Manager rev iews the control of Agency B rev iews the change Agency request(s) C rev iews the requested changes requested changes TMC Operator or Manager f rom Agency TMC Operator TMC X Operator approv or es/reject Manager f rom or Manager the f rom control Agency X approv es/reject the Agency change X approv request(s) es/reject the control change request(s) control change request(s) RMS compiles request changes approv als/rejections RMS If needed, TMC Operator uses User Interf ace to rev iew: - Response plan elements - Status of control dev ices - Current corridor perf ormance - project results All requested changes approv ed Some changes not approv ed CMS RECOMMENDED PLAN NOT IM PLEMNETED Probe Vehicles Implementation Subsystem sends control RMS commands to v arious control dev ices af fected by response plan RMS inf orms all corridor partners of the recommended changes RMS CMS 511 & Media Road Operators Transit Operators First Responders Operators allowed to suggest changes? Or system just wait for next decision interval?? logs summary of recent activ ities Figure A-9 Response Plan Review/Approval Envisioned Process 10

11 A.8. SYSTEM OPERATIONAL REVIEW Following and incident, TMC Operator decides to rev iew how the system responded to the event Corridor Manager rev iews the issue(s) brought to his attention, contracting if necessary Transportation Managers Transportation Managers S User Interface retriev es f rom the the activ ity log f or the day /time of interest UI TMC Operator uses the S User Interf ace to request a summary of system activities associated with a specif ic ev ent or specific day /time period If relev ant, Corridor Manager brings the issue(s) to the attention of the Sy stem Manager Sy stem Manager reviews submitted issue(s), consulting if needed with / Maintenance Staf f, TMC Operators, Transportation Managers, and Corridor Manager Maintenance Staff Maintenance Staff TMC Operators S User Interface retriev es f rom the the activ ity log f or the day /time of interest UI Following and incident, TMC Operator uses the S User Interf ace to rev iew the retrieved operational statistics Sy stem Manager determines, in consultation with Maintenance Staf f, TMC Operators and Corridor Manager changes to make to the system to correct the identified problems Problem related to Sy stem Component Problem related to local system Transportation Managers Corridor Manager Following the rev iew of the incident response rev iew, TMC Operator identif ies potential issue(s) with sy stem operations TMC Operator brings the identif ied issue(s) to the Corridor Manager Maintenance Staf f instructed to modif y the sy stem to address the identified issue(s) Repairs/adjustments Maintenance Staf f instructed to f ix the identif ied issue(s) with local system Repairs/adjustments RMS UI REP Sensors Probe Vehicles CMS Bluetooth Devices Figure A-10 System Operation Review Envisioned Process 11

12 A.9. RESPONDING TO ASSET FAILURES receiv es a f ault/error message from a traffic detector uses inf ormation receiv ed to assess the reported problem (if possible) Fault not af f ecting signal operations Fault af f ecting signal operations TMC Operator inf orms Maintenance Staff of faulty detector(s) Maintenance Staf f schedule repair work Maintenance Staf f enters any planned lane closures into local reporting sy stem marks the data receiv ed f rom f aulty detector(s) as potentially inaccurate Historical data not available returns no av ailable data for any data request Historical data available f ulf ills data requests using historical av erage prof iles f or the corresponding day and time Fault reported through local traf f ic control system Field Personnel archiv es the f ault message NO FURTHER ACTIONS sends a Control Dev ice Fault warning to the display a f ault message on computer terminal f or review by TMC Operators TMC Operator of agency responsible f or detector maintenance takes note of the f ault TMC Operator assesses the sev erity of the fault message received Faulty detector is f ixed Maintenance Staf f inf orms TMS Operator that faulty detector is fixed Maintenance Staf f terminates the road closure plan associated with the detector repair Road Closures Road Closures updates list of active incidents /ev ents updates list of activ e incidents/ev ents Subsy stem uses supplied data to characterize traf f ic conditions at the f aulty detector s location Rules Engine dev elop response plans based on supplied data SUBSEQUENT CONTROL INTERVAL If needed, TMC Operator uses the S User Interface to consult most recent perf ormance ev aluations Need f or correctiv e actions stops receiv ing error messages f rom traf f ic detector sets detector status to Normal starts to f ulf ill data requests using real-time data Subsy stem uses supplied data to characterize traf f ic conditions at detector`s location Rules Engine dev elop response plans based on supplied data Figure A-11 Envisioned Process for Addressing a Sensor Fault 12

13 Fault not af f ecting signal operations receiv es a f ault/error message from a traffic signal controller uses inf ormation receiv ed to assess the reported problem (if possible) Fault af f ecting signal controller operations TMC Operator inf orms Maintenance Staff of the f aulty controller adjust operating status of controller (f lashing mode, def ault timing plan, etc.) creates a new incident record updates list of activ e incidents/events in corridor Subsy stem updates traf f ic signal operational parameters in corridor models archiv es the f ault message sends a Control Device Fault warning to the Maintenance Staff schedule repair work sets controller as unav ailable f or response planning Rules Engine considers f aulty controller when developing new response plans Fault reported through local traf f ic control system NO FURTHER ACTIONS display a f ault message on computer terminal f or review by TMC Operators TMC Operator of agency responsible f or controller maintenance takes note of the f ault Signal controller is f ixed Maintenance Staff inf orms TMS Operator that controller is f ixed TMC Operator sets to Terminated the incident record associated with the faulty controller SUBSEQUENT CONTROL INTERVAL updates list of activ e incidents/ev ents Field Personnel If needed, TMC Operator uses the S User Interf ace to consult most recent performance evaluations TMC Operator assesses the v alidity /severity of the received fault message Need f or correctiv e actions stops receiv ing f ault messages sets controller s operating status to Normal sets controller as av ailable f or response planning Subsy stem updates traf f ic signal operational parameters in corridor models Rules Engine considers updated controller status when developing response plan Figure A-12 Envisioned Process for Addressing a Signal Controller Fault 13