F3.1.2.13.7 Manage Planned Inter-urban Traffic Strategy Change

Header Image
Project:
F3.1.2.13.7 Manage Planned Inter-urban Traffic Strategy Change : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 24.10.2019 12:44:26
Modified: 08.09.2021 11:24:30
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to provide facilities that enable inter-urban traffic management strategies to be implemented automatically in a timed sequence.<br/>(2) The ability for the sequence mechanism to permit the implementation to be by any combination of time of day, day of week, day of month, or day of year.<br/>(3) The ability for the content and detail of the sequences of management comments that are to be implemented by time of day, to be received from the functionality that provides the Road Network Operator interface.<br/>(4) The ability to provide on request a response to the functionality that provides the Road Network Operator interface details of the time of day sequences that are currently available for use.<br/>(5) The ability to send requests for implementation of traffic control strategies to the inter-urban traffic management and access control functionality.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mt_planned_inter-urban_data_output
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_planned_inter-urban_traffic_management_request
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_High_Level_Function» F3.1.2.13 Manage Inter-urban Traffic Strategies
FRAME_High_Level_Function «Componentof»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_User_Need» 7.1.3.7
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_planned_inter-urban_data_update
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.3.6
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.1.0.11
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt_inter-urban_strategies_for_long-term
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
Requirement Type Status Difficulty Priority Stability
Functional Functional Proposed Medium Medium Moderate
Details:
(a) when the first trigger input data flow is received the command that it contains shall be checked;<br/>(b) if the result of (a) is that the current available sequences are to be changed, then this shall be implemented;<br/>(c) completion of (b) shall be confirmed using the second trigger output data flow;<br/>(d) if the result of (a) is that details of the current sequences are to be output, this shall be sent to the inter-urban traffic and access control Functions using the first and third trigger output data flows;<br/>(e) periodically, the sequences shall be scanned and the next one to be implemented for the current day and time shall be determined;<br/>(f) when the day and time determined in (e) arrives, the control strategy(ies) requested in the sequence shall be sent to the inter-urban traffic and access control Functions using the first and third trigger output data flows;<br/>(g) when the second trigger input data flow is received the data for the new or revised inter-urban traffic management strategy shall be checked for format and consistency;<br/>(h) if the result of (g) is acceptable, the strategy shall be made available for selection when required;<br/>(i) if the result of (g) is not acceptable, then details shall be output using the first trigger output data flow;<br/>(j) the actions in (e) and (f) shall take priority over all other actions carried out by this Function.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0