F3.1.1.5.24 Implement Urban Traffic Strategies

Frame Repository / Frame Functional View / Functionality / Functional Area F3 - Manage Traffic / F3. Manage Traffic / F3.1 Provide Traffic Control / F3.1.1 Provide Urban Traffic Management / F3.1.1.5 Provide Urban Traffic Management Facilities / F3.1.1.5.24 Implement Urban Traffic Strategies

Project:

F3.1.1.5 Provide Urban Traffic Management Facilities

F3.1.1.5.24 Implement Urban Traffic Strategies : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	24.10.2019 12:44:25
Modified:	08.09.2021 11:24:29

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{66076FF8-17FB-4246-84B3-C09F2345458B}
Appears In:	DFD F3.1.1.5 Provide Urban Traffic Management Facilities, Functional Tree of F3.1.1 Provide Traffic Control

This Function shall be capable of providing the following facilities: (1) The provision of traffic management that enable Vehicles to make the most efficient use of the urban road network. (2) The automatic implementation of strategies for traffic management in a planned sequence according to the time of day and day of week. (3) The ability to output data for "stop&go" and/or "commands & information" messages directly to Vehicles so that their contents can be output to Drivers by an In-vehicle display mechanism. (4) The ability of the Road Network Operator to override the automatic implementation of one or more strategies using inputs made through the HMI provided by the Provide Urban Traffic Operator Interface Function. (5) The ability for the automatic strategy implementation to be temporarily overridden by inputs requiring green wave routes to be implemented for selected Vehicles. (6) The ability for the automatic strategy implementation to be overridden by requests for changes to the way that traffic is managed that are received from functionality in the Manage Incidents and Manage Demand High-level Functions in the Manage Traffic Functional Area. (7) The ability for the Road Network Operator to define the order of priority for the various inputs that can override the automatic strategy implementation. (8) The ability to adapt the traffic management strategies to suit the current and predicted traffic conditions using real-time data to identify the need for and content of the adaptations (adaptive traffic control). (9) The ability to apply traffic management strategies to some or the entire urban road network managed by the System. (10) The ability to monitor the results from the implementation of strategies so that if necessary corrective action can be taken if the content of strategies are not followed. (11) The provision of details of the current and previously implemented strategies on some or all parts of the urban road network to the Road Network Operator through the Provide Urban Traffic Operator Interface Function.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mt.pshvs_c&i_outputs_for_driver_display FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_response_fault FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_strategies_in_use FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_traffic_management_c&i_request FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_zone_access_vehicle_list FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.pshvs_s&g_outputs_for_driver_display FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_speed_value FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_operator_urban_traffic_management_response FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tors.utms-urban_traffic_management_strategies FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_traffic_management_s&g_requests FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_lane_management FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F3.1.1.5 Provide Urban Traffic Management Facilities FRAME_High_Level_Function «Componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_bridge_inputs FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.ptja_urban_recommended_routes FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_speed_and_headway_settings FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tmms.mmc-urban_crossing_inhibit FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_to_inter-urban_traffic_commands FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.pscs_green_wave_result FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_tunnel_inputs FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_User_Need» 7.1.12.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_traffic_flow_management_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_planned_urban_traffic_management_request FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.2.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» pscs.mt_green_wave_request FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psef.mt_urban_emergency_route_request FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.5.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.9.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.8.7 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.3.1.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_bridge_urban_inputs FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.3.7 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 2.1.3.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_current_urban_traffic_conditions FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.9.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.10 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.5.9 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.12.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.5.7 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.0.13 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.5.8 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_inter-urban_to_urban_traffic_commands FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 5.2.0.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_operator_urban_traffic_management_request FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_traffic_management_s&g_response FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.3.1.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.0.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_static_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.mt_request_demand_vehicle_priority FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.4.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.9.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fors.utms-urban_traffic_management_strategies FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.mt_vehicle_priority_request FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_zoning_strategy FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.5.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.3.8 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_network_long-term_prediction_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.5.6 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_incident_strategy_request FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.0.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.9.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_tunnel_urban_inputs FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 5.2.0.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.0.6 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_traffic_management_l&s_response FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.0.10 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_environmental_inputs FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.0.12 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.26 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» psef.mt_urban_virtual_coned_area_request FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_traffic_management_c&i_response FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.0.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.1.25 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.8.8 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.4.8.9 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.5.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.5.2.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.4.9 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 2.1.2.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_demand_management_strategy FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.4.8 FRAME_User_Need «Servedby»	Name:	Name:
Details:

Requirement	Type	Status	Difficulty	Priority	Stability
Functional	Functional	Proposed	High	Medium	Moderate
Details: (a) continuously monitor for receipt of the operator urban traffic management request, planned urban traffic management request, urban environmental inputs, urban demand management strategy and urban incident strategy request data flows;<br/>(b) when any of the data flows in (a) is received, implement the traffic management commands that they contain using the contents of the data flow containing urban static data to determine which are the appropriate section(s) of the urban road network to which the commands apply;<br/>(c) the commands in (b) shall be implemented using some or all of the urban bridge inputs, urban tunnel inputs, urban lane management, urban speed setting, urban traffic management s&g request, urban traffic management msg requests and urban recommended routes data flows, plus data sent to the Traffic Simulation functionality in the urban strategies in use data flow and data sent directly to In-vehicle functionality using the s&g outputs for driver display and c&i outputs for driver display data flows;<br/>(d) the commands being implemented in (b) shall be filtered for applicability and sent to any other adjacent urban traffic management systems in the urban traffic management strategies data flow and to any relevant inter-urban traffic management systems in the urban to inter-urban traffic commands data flow;<br/>(e) if the urban zoning strategy data flow is received, whichever is necessary of the data flows in (c) shall be sent plus the urban zone access vehicle list data flow;<br/>(f) it shall be possible for the data flows containing current urban traffic conditions, urban traffic flow management data, predicted urban network data, bridge urban inputs and tunnel urban inputs to be continuously monitored and for their contents to be used to revise the detail of the commands being implemented in (b) thus providing adaptive traffic control;<br/>(g) if the operator urban traffic management request was received in (a) and had led to the implementation of (b) and (c) then the operator urban traffic management response data flow shall be sent to the Provide Operator Interface function;<br/>(h) as a result of (c) the receipt of the urban traffic management s&g response, urban traffic management l&s response and urban traffic management c&i response data flows shall be monitored;<br/>(i) when any of the data flows in (h) is received their contents shall be checked to see if the commands in (c) are being followed;<br/>(j) if the result of (i) is that the commands are not being followed, this shall be communicated to the Provide Operator Interface function in the operator urban management response data flow and to the Maintenance Management functionality in the urban response fault data flow;<br/>(k) if the requirement is included in the contents of the data flows in (b) the contents of the data flows in (i) shall be used to revise the commands being sent in (c);<br/>(l) if either the inter-urban to urban traffic commands or urban traffic management strategy data flows is received, their contents shall be analysed if necessary new commands implemented as in (c) with the addition that requests may be sent to any relevant multi-modal management systems in the urban crossing inhibit data flow;<br/>(m) if any of the urban emergency route request, green wave request, vehicle priority request and request demand vehicle priority data flows is received, its contents shall be implemented as in (b) and (c) above and shall take priority over any of the other inputs received in (a), (l) and (m);;<br/>(n) of the data flows in (m) the contents of the urban emergency route request shall take priority over all the others, with the contents of the vehicle priority request data flow being the next highest in priority, followed by the contents of the demand vehicle priority data flow;<br/>(o) if the inter-urban virtual coned area request data flow is received, implement the necessary lane closures and speed restrictions as in (b) and (c) above in order to prevent vehicles from entering the area around an accident;<br/>(p) the commands in the operator urban traffic management request data flow received in (a) shall take precedence over all the inputs in (a) and (l) but not the inputs in (m) and (o);<br/>(q) the commands in the planned urban traffic management request data flow received in (a) shall take the lowest priority after all the other inputs in (a), (l), (m) and (o);<br/>(r) implementation of all the outputs in (c) shall be checked to ensure that the comments being implemented are consistent and coherent and do not contradict each other.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0