APPENDIX A. OPERATIONAL PROCESS FLOW CHARTS
Transcript of APPENDIX A. OPERATIONAL PROCESS FLOW CHARTS
I-210 Pilot: System Requirements
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 ICM system operations • Addressing asset failures
I-210 Pilot: System Requirements
2
A.1. INCIDENT RESPONSE CONTROL LOOP
Figure A-1 – Envisioned Incident Response Control Loop
Simulation Subsy stem updates model representing current network operations
Incident Management Sy stem updates list of activ e incidents within corridor
Activ e Incidents
No Activ e Incident
DSS determine needs f or response plan
Response Plan Needed
Response Planning Not
Required
DSS Rules Engine identif ies av ailable detours and control alternativ es
DSS Rules Engine generates response plans f or identif ied incident(s)
One or more possible alternativ es
No f easible alternativ e
NEW INCIDENT OCCURS
DSS Rules Engine selects a recommended response plan f or implementation
Rev iew/approv al of recommended plan by Corridor Operators
DSS waits f or next incident to occurs
NEXT INCIDENT
Recommended plan not
approv ed
Rev iew of important sy stem issues by Corridor Manager and Local Transportation Managers
PERIODIC OPERATIONAL REVIEWS
Response Management Subsy stem sends control commands to v arious control dev icesaf f ected by response plan
RMS
Weekly /monthly reviews of sy stem activities by Local Corridor Operators
RUL
RUL
DSS
SIM
IMS
Rev iew of operational issues by ICM/Local Maintenace Staf f
ICM
Implementation of recommended adjustments into ICM sy stem by ICM Sy stem Manager
ICM Configuration Parameters
Simulation Subsy stem ev aluates dev eloped response plans
SIM
DSS Activity Log
Simulation Subsy stem ev aluates current network operations
SIM
Simulation Data
(alternate scenarios)
Simulation Data
(current situation)
DSS sends the selected response plan f or implementation
DSS
RUL
Recommended plan approv ed
I-210 Pilot: System Requirements
3
A.2. PERIODIC CORRIDOR PERFORMANCE ASSESSMENT
Figure A-2 – Periodic Corridor Performance Evaluation Process
Simulation Subsy stem continuously updates the status of corridor elements using receiv ed real-time data
SIM
Traffic Signals
Ramp Meters
Data Hub
Traffic Sensors
Bluetooth Devices
Probe Vehicles Incidents
Planned Events
Road Closures
Simulation Subsy stem records perf ormance metrics that hav e been compiled ov er each reporting interv al
SIMSy stem User requests through the ICMS User Interf ace, a corridor-wide perf ormance report f or the past hour
ICMS User Interf ace sends a report generation request to the Analy sis Module
Analy sis Module aggregates the retriev ed statistics to produce the requested report
ICMS User Interf acedisplay s the requested statistics on the terminal used by TMC Operator
ICMData Hub
Historical Data
Default Profiles & Values
Simulation Subsy stem uses stored historical data and def ault prof iles
Data Hub
SIM
Elements with real-time data update
Elements without real-time data update
Continuous Corridor Model Update
Report Generation
Modelers,Operators
Analy sis Module retriev es f rom the Data Hub, DSS and possible other sources relev ant perf ormance statistics f or the requested ev aluation period
x min x min x min x min x min x min
Modelers,Operators,Managers
Configuration Parameters
ICM Sy stem Manager sets up the basic metrics reporting interv al (e.g., 5 min, 15 min)
System Setup
ICM
Simulation Subsy stem sends compiled metrics to the Data Hub
SIM
Analy sis Module summarizes the analy sis results in a PDF f ile
UI
DSS Data
I-210 Pilot: System Requirements
4
A.3. INCIDENT/EVENT DETECTION
Figure A-3 – Incident Detection and Verification Process
Drivers &Passengers
IMS retriev es f rom Data Hubinf ormation characterizing the current operational status of corridor roadway s
If unusual congestion exists, the IMS generates a Congestion Warning message with the location of the problem
Local TMC Operator determines that Incident inf ormation is v alid
Local TMC Operator determines that the
incident inf ormation is not v alid
INFORMATION DISCARDED
Local TMC Operator assesses the v alidity of the incident inf ormation receiv ed by rev iewing operational status of corridor elements
IMS assesses whether unusual congestion exists in the corridor by comparing real-time and historical data
INCIDENT CHARACTERIZATION
CHPCAD
Pasadena Traffic Record System
IMS retriev es incident inf ormation f rom connected CAD sy stems v ia Data Hub
IMS
Incident directly observ ed by Local TMC operator on CCTV v ideo f eed
Incident Inf ormation is receiv ed by Local TMC Operator
Drivers &Passengers
Simulation Data
Data Hub
IMS retriev es f rom Data Hubinf ormation characterizing ty pical roadway conditions f or the current day of week and time of day
IMS
IMS
IMS
IMS
If needed, TMC Operator uses the ICMS User Interf ace to consult most recent DSS perf ormance ev aluations
Data Hub
Local TMC Operator instructs IMS to create a new incident record
Traffic Sensors
Bluetooth Devices
Probe Vehicles
IMS retriev es Incident inf ormation f rom Crowdsourcing Application (Waze, other) v ia Data Hub
Data Hub
App
IMS
IMS display f or rev iew Incident Warningand Congestion Warning messages on terminal used by all TMC Operators
ICM
IMS
IMS generates an Incident Warningmessage with the location of the incident
IMS generates an Incident Warningmessage with the location of the incident
IMS IMS
County Data
Police Dispatchers
Transit Dispatchers
Local Agency Personnelreceiv es incident inf ormation
First Responders
Field Personnel
Field Personnel
City Data
I-210 Pilot: System Requirements
5
Figure A-4 – Event Detection and Verification Process
Lane closure/ev ent directly observ ed by Local TMC operator on CCTV v ideo f eed
Traffic Signals
Ramp Meters
Data Hub
IMS retriev es f rom Data Hub f ault data receiv ed f rom connected traf f ic control sy stems
IMS
Caltrans LCS
County Road
Closures
Data Hub
IMS retriev es f rom Data Hub f ault data receiv ed f rom connected traf f ic control sy stems
City A Road
Closures
CONTROL DEVICE FAILUREPLANNED LANE/ROAD CLOSURESEM ERGENCY LANE/ROAD CLOSURES
Incident Inf ormation is receiv ed by Local TMC Operator
Field Maintenance Personnel
Transit Dispatchers
Local Agency Personnelreceiv es incident inf ormation
First Responders
Local TMC Operator determines that Incident inf ormation is v alid
Local TMC Operator
determines that the incident inf ormation
is not v alid
INFORMATION DISCARDED
Local TMC Operator assesses the v alidity of the incident inf ormation receiv ed by rev iewing operational status of corridor elements
INCIDENT CHARACTERIZATION
Local TMC Operator instructs IMS to create a new incident record
IMS display f or rev iew receiv ed Lane Closureand Control Dev ice Fault messages on terminal used by all TMC Operators
IMS
City B Road
Closures
IMS
Simulation Data
If needed, TMC Operatoruses the ICMS User Interf ace to consult most recent DSS perf ormance ev aluations
ICM
Field Personnel
I-210 Pilot: System Requirements
6
Figure A-5 – Incident Characterization Process
TMC Operator assess incident characteristics• Expected duration• Sev erity based on incident
ty pe
NEW VALID INCIDENT
IMS adds the new incident record to a list of activ e incidents
IMS creates new incident record
IMS assigns incident ID to the identif ied incident
IMS pre-populates incident record with data supplied by connected inf ormation sy stems
Incident record is edited/completed by TMC Operator
Completed incident record is v alidated by TMC Operator
CAD sy stem supplies basic incident inf ormation• Location• Lanes af f ected
TMC Operator checks incident details• CCTV camera• Reports f rom f ield personnel• CAD sy stems• Corridor status f rom DSS reports
DETERM INATION OF RESPONSE PLANNING NEED
CAD
CAD
ICM
IMS
IMS
IMS
IMS
I-210 Pilot: System Requirements
7
A.4. ONLINE CORRIDOR MODEL ADJUSTMENTS
Figure A-6 – Corridor Model Online Adjustment Process
M ODEL UPDATE REQUEST (e.g., following an incident)
Simulation Subsy stem retriev es f rom IMS a list of activ e incidents
SIM
Simulation Subsy stem compares list of activ e incidents f rom IMS with ev ents def ined in Current Simulation Model
SIM
IMS
Simulation Subsy stem retriev es the corridor model representing current operations (Current Simulation Model)
SIM
Incident in ICM list identical to incidents coded in Current Simulation Model
IMS incident list dif f er f rom list of incidents coded in Current Simulation Model
Simulation Subsy stem remov es f rom Current Simulation Model all incidents no longer on the IMS list
Simulation Subsy stem adds in Current Simulation Modelincidents on IMS list not already coded in the model.
Simulation Subsy stem retriev es f rom IMS a list of incidents that hav e been recently terminated
SIMIMS
Simulation Subsy stem remov es f rom Current Simulation Model all incidents that hav e been terminated
SIM
Simulation Subsy stem retriev es f rom Data Hubreal-time data characterizing the current status of roadway elements- Flow rates - Queue length- Density - Etc,
Traffic Sensors
Bluetooth Devices
Probe Vehicles
Data Hub
Simulation Subsy stem adjusts, if necessary, the f ollowing elements in Current Simulation Model:
- Roadway characteristics- Trav el demand- Network f low pattern
Simulation Subsy stem retriev es f rom Data Hub data characterizing the current status of control dev ices:- Current timing plan- Current metering rate- Current posted messages
Traffic Signals
Ramp Meters
CMSData Hub
Simulation Subsy stem adjusts if necessary the status the f ollowing modeled control dev ices in Current Simulation Model:- Traf f ic signals- Ramp meters- Changeable message signs
Simulation Subsy stem stores an updated v ersion of Current Simulation Model f or use in subsequent ICM sy stem activities
Simulation Data
Simulation Data
SIM
SIM
SIM
SIM
SIM
SIM
Simulation Subsy stem estimates traf fic conditions on indiv idual roadway links within the modeled network area
SIM
SIM
Simulation Subsy stem adjusts in Current Simulation Model the characteristics of incidents already def ined in model to match incidents in ICM list
SIM
I-210 Pilot: System Requirements
8
A.5. INCIDENT/EVENT IMPACT ASSESSMENT (RESPONSE NEED ASSESSMENT)
Figure A-7 – Incident/Event Impact Assessment Process
NEW INCIDENT/EVENTDSS requests f rom Simulation Subsy stem an ev aluation of corridor operations ov er next hour with and without the identif ied incidents
IMSDSS requests f rom Incident Management Sy stem a list of activ e incidents within the corridor
No activ e incident is receiv ed
DSSSS
Activ e incidents are receiv ed
DSS
DSS uses simulation results to quantif ies the impacts of activ e incidents on corridor operations
DSS
DSS ev aluates whether the ev aluated impacts exceed user-def ined thresholds
NO FURTHER ACTION IS CONSIDERED
DSS receiv es simulation results f rom the Simulation Subsy stem
ICM Configuration Parameters
Impacts exceed user-def ined thresholds
Impacts do not exceed user-def ined thresholds
RESPONSE PLANNING INITIATED
NO FURTHER ACTION CONSIDERED
DSS Data
Corridor Operators & Managers
Simulation Sy bsy stem retrieves corridor model representing current operations
SIM
Simulation Subsy stem projects corridor operations ov er next hour f or the f ollowing two scenarios:- Current Network without Incident- Current Network with Incident
Simulation Subsy stem projects corridor operations ov er next hour f or the f ollowing two scenarios:- Current Network without Incident- Current Network with Incident
DSS stores ev aluation results f or potential later use
DSS
DSS
DSS
Simulation Data
Simulation Subsy stemstores simulation results f or potential later use
SIMSIM
Simulation Data
I-210 Pilot: System Requirements
9
A.6. RESPONSE PLAN CREATION
Figure A-8 – Response Plan Creation Envisioned Process
POSITIVE RESPONSE PLANNING DECISION
DSS Data
DSS retriev es f rom storage simulation results f or the Current Network with Incident scenario (“Do nothing scenario”)
DSS
DSS assesses the ov erall operational sev erity of active incidents based on simulation results and produces an ov erall sev erity rating
DSS retriev es list of activ e incident f rom Incident Management Sy stem
DSSIMS
If required, TMC Operator rev iews and approv es/modif y the proposed sev erity rating
Data Hub
DSS retriev es real-time data characterizing the av ailability of traffic control dev ices within the corridor
DSS
Traffic Signals
Ramp Meters
CMS
DSS
DSS Rules Egine identif ies av ailable alternate route(s) around congested corridor elements considering:- Sev erity - Av ailable roadway capacity- Asset av ailability - User-def ined operational constraints
For each alternate route, DSSrequests a simulation ev aluation of corridor operations ov er next hour
DSS computes perf ormance metrics f or each alternativ e, including a “do nothing” scenario (Current Network with Incident scenario)
DSS
DSS receiv es simulation results f rom Simulation Subsy stem
DSS uses computed perf ormance metrics to identif y a recommended response plan.
DSS
DSS uses retriev ed real-time data to compute av ailable capacity along f reeway and arterial segments
Operational Constraints
Corridor Operators & Managers
DSS retriev es f rom Data Hub current status data f or corridor roadway elements
Data Hub
Traffic Sensors
Probe Data
DSS
No f easible alternate route
One or more f easible alternate route(s)
NO RESPONSE PLAN DEVELOPED
DSS
Simulation Subsy stem projects corridor operations ov er next hour f or each dev eloped alternativ e
Simulation Subsy stem projects corridor operations ov er next hour f or each dev eloped alternativ e
Simulation Subsy stem projects corridor operations ov er next hour f or each dev eloped alternativ e
SIM
RESPONSE RECOMMENDATION
DSS
Bluetooth Devices
RUL
DSS stores simulation and recommendation details f or later use
DSS Memory
DSS
DSS Activity Log
DSS logs summary of recent activ ities
DSS
DSS
DSS Rules Egine identif ies appropriate control strategies f or each identif ied alternat route- Timing plan change- Change of ramp metering rate
RUL
DSS Rules Egine identif ies an approprioateinf ormation dissemination strategy
RUL
Control Preferences
DSS Activity Log
I-210 Pilot: System Requirements
10
A.7. RESPONSE PLAN REVIEW/APPROVAL
Figure A-9 – Response Plan Review/Approval Envisioned Process
RESPONSE RECOMMENDATION
RMS identif ies the control dev ices that each agency is requested to change to implement the recommended response plan
RMS sends control change requests to each agency af f ected by the recommended response plan
TMC Operator/Manager of Agency C rev iews the requested changes
TMC Operator/Manager of Agency B rev iews the requested changes
TMC Operator or Manager f rom Agency X rev iews the control change request(s)
Simulation Data
If needed, TMC Operator uses ICM User Interf ace to rev iew:- Response plan elements- Status of control dev ices- Current corridor perf ormance- Simulation project resultsTMC Operator or Manager f rom
Agency X approv es/reject the control change request(s)
TMC Operator or Manager f rom Agency X approv es/reject the control change request(s)
TMC Operator or Manager f rom Agency X approv es/reject the control change request(s)
RMS compiles request changes approv als/rejections
All requested changes approv ed
Some changes not approv ed
RECOMMENDED PLAN NOT
IM PLEMNETED
ICM Implementation Subsy stem sends control commands to v ariouscontrol dev ices af fected by response plan
RMS checks whether plan approv al is required f rom each af f ected agencies
Agency staf f approv al not
required
Agency staf f approv al required
IMS = Incident Management SystemDSS = Decision Support SystemIMPL = Implementation Module
Data Hub
Traffic Sensors
Bluetooth Devices
Probe Vehicles
Traffic Signals
Ramp Meters
CMS
Traffic Signals
Ramp Meters
CMS
511 & Media
RMS inf orms all corridor partners of the recommended changes
Road OperatorsTransit OperatorsFirst Responders
?Operators allowed to suggest changes? Or
system just wait for next decision interval?
DSS Activity Log
DSS logs summary of recent activ ities
DSS sends the recommended response plan to the ICM Response Management Sy stem (RMS)
DSS
RMS
RMS
RMS
RMS
RMS
RMS
DSS
ICM
I-210 Pilot: System Requirements
11
A.8. ICM SYSTEM OPERATIONAL REVIEW
Figure A-10 – ICM System Operation Review Envisioned Process
DSS Activity
Log
Following and incident, Local TMC Operator decides to rev iew how the ICM sy stem responded to the ev ent
TMC Operator uses the ICMS User Interf ace to request a summary of sy stem activities associated with a specif ic ev ent or specif ic day /time period
ICM
Simulation Data
ICMS User Interf ace retriev es f rom the Data Hub the DSS activ ity log f or the day /time of interest
ICMS User Interf ace retriev es f rom the Data Hub the DSS activ ity log f or the day /time of interestData
Hub
Data Hub
Following and incident, Local TMC Operator uses the ICMS User Interf ace to rev iew the retriev ed operational statistics
ICM
Following the rev iew of the incident response rev iew, Local TMC Operator identif ies potential issue(s) with sy stem operations
UI
UI
Local TMC Operator brings the identif ied issue(s) to the ICM Corridor Manager
ICM Corridor Manager rev iews the issue(s) brought to his attention, contracting if necessary Local Transportation Managers
Local Transportation Managers
If relev ant, Corridor Manager brings the issue(s) to the attention of the ICM Sy stem Manager
ICM Sy stem Manager rev iews submitted issue(s), consulting if needed with ICM/Local Maintenance Staf f, Local TMC Operators, Local Transportation Managers, and ICM Corridor Manager
ICM Sy stem Manager determines, in consultation with Local Maintenance Staf f , Local TMC Operators and ICM Corridor Manager changes to make to the ICM sy stem to correct the identif ied problems
Local TMC Operators
ICM Corridor Manager
Local Transportation Managers
Problem related to ICM Sy stem Component
Problem related to local sy stem
ICM Maintenance Staf f instructed to modif y the sy stem to address the identif ied issue(s)
Local Maintenance Staf f instructed to f ix the identif ied issue(s) with local sy stem
UI
SIM
RUL
RMS
DSS
REP
IMS
Local TCS
Traffic Signals
Ramp Meters
Traffic Sensors
Bluetooth Devices
Probe Vehicles
CMS
Local Maintenance Staff
ICM Maintenance Staff
DSS Activity
Log
DSS Activity
Log
Repairs/adjustments Repairs/adjustments
I-210 Pilot: System Requirements
12
A.9. RESPONDING TO ASSET FAILURES
Figure A-11 – Envisioned Process for Addressing a Traffic Sensor Fault
Data Hub receiv es a f ault/error message f rom a traf f ic detector
Data Hub
Data Hub uses inf ormation receiv ed to assess the reported problem (if possible)
Data Hub
Fault af f ecting signal operations
Data Hub sends a Control Dev ice Fault warning to the IMS
Data Hub
Fault not af f ecting signal operations
Data Hub archiv es the f ault message
Data Hub
NO FURTHER ACTIONS
Need f or correctiv e
actions
Local TMC Operatorassesses the sev erity of the f ault message receiv ed
IMS display a f ault message on computer terminal f or rev iew by TMC Operators
IMS
If needed, TMC Operator uses the ICMS User Interf ace to consult most recent DSS perf ormance ev aluations
Field Personnel
Simulation Data
ICM
Local TMC Operator inf orms Local Maintenance Staf f of faulty detector(s)
Local Maintenance Staf f schedule repair work
Local Road
Closures
Local TMC Operator of agency responsible f or detector maintenance takes note of the f ault
Faulty detector is f ixed
Local Maintenance Staf f inf orms Local TMS Operator that f aulty detector is f ixed
Local Road
Closures
DSS Rules Enginedev elop response plans based on supplied data
Simulation Subsy stem uses supplied data to characterize traf f ic conditions at detector`s location
SIM
RUL
Fault reported through local traf f ic control sy stem
Local TCS
Data Hub marks the data receiv ed f rom f aulty detector(s) as potentially inaccurate
Data Hub
SUBSEQUENT CONTROL INTERVAL
Data Hub stops receiv ing error messages f rom traf f ic detector
Data Hub
Local Maintenance Staf f terminates the road closure plan associated with the detector repair
Data Hub
Data Hub f ulf ills data requests using historical av erage prof iles f or the corresponding day and time
Data Hub returns “no av ailable data” f or any data request
Historical data av ailableHistorical data not av ailable
DSS Rules Engine dev elop response plans based on supplied data
RUL
Simulation Subsy stem uses supplied data to characterize traf f ic conditions at the f aulty detector’s location
SIMData Hub
Data Hub
Data Hub
IMS updates list of activ e incidents /ev ents
IMS
Local TCS
Local TCS
Data Hub starts to f ulf ill data requests using real-time data
Data Hub
Data Hub sets detector status to “Normal”
Data Hub
IMS updates list of activ e incidents/ev ents
IMS
Local Maintenance Staf f enters any planned lane closures into local reporting sy stem
I-210 Pilot: System Requirements
13
Figure A-12 – Envisioned Process for Addressing a Traffic Signal Controller Fault
Data Hub receiv es a f ault/error message f rom a traf f ic signal controller
Data Hub
Data Hub uses inf ormation receiv ed to assess the reported problem (if possible)
Data Hub
Fault af f ecting signal controller operations
Data Hub sends a Control Dev ice Fault warning to the IMS
Fault not af f ecting signal operations
Data Hub archiv es the f ault message
Data Hub
NO FURTHER ACTIONS
Need f or correctiv e
actions
Local TMC Operator assesses the v alidity /severity of the receiv ed f ault message
IMS creates a new incident record
IMS display a f ault message on computer terminal f or rev iew by TMC Operators
IMS
If needed, TMC Operator uses the ICMS User Interf ace to consult most recent DSS perf ormance ev aluations
Field Personnel
Simulation Data
ICM
DSS Rules Engine considers f aulty controller when dev eloping new response plans
Simulation Subsy stem updates traf f ic signal operational parameters in corridor models
IMS updates list of activ e incidents/ev ents in corridor
IMS
Local TMC Operator inf orms Local Maintenance Staf f of the f aulty controller
Local Maintenance Staf f schedule repair work
Local TMC Operator of agency responsible f or controller maintenance takes note of the f ault
Signal controller is f ixed
Local Maintenance Staf f inf orms Local TMS Operator that controller is f ixed
DSS Rules Engine considers updated controller status when dev eloping response plan
Simulation Subsy stemupdates traf f ic signal operational parameters in corridor models
IMS updates list of activ e incidents/ev ents
IMS
Fault reported through local traf f ic control sy stem
Local TCS
IMS
Data Hub sets controller as unav ailable f or response planning
Data Hub
Data Hub adjust operating status of controller (f lashing mode, def ault timing plan, etc.)
Data Hub
SUBSEQUENT CONTROL INTERVAL
Data Hub sets controller’s operating status to “Normal”
Data Hub
Local TMC Operator sets to “Terminated” the incident record associated with the f aulty controller
Data Hub sets controller as av ailable f or response planning
SIM
RUL
RUL
SIMData Hub stops receiv ing f ault messages
Local TCS
Local TCS
Data Hub
Data Hub
Data Hub