D3.12 Incident Strategies Data

Header Image
Project:
D3.12 Incident Strategies Data : Public <<FRAME_Datastore>> FRAME_Datastore
Created: 24.10.2019 12:47:06
Modified: 10.09.2021 10:38:52
Project:
Advanced:
This Data Store shall be used in the Manage Traffic Functional Area.  It shall contain information objects that provide details of incident strategies that have been created and used previously.<br/><br/>Each information object in the Store shall contain the following data objects:<br/>(1) Strategy identity (characters)<br/>(2) Reason for implementing the strategy (characters)<br/>(3) How the strategy was implemented, e.g. Operator, Automatically - (character);<br/>(4) Implementation date (date string)<br/>(5) Implementation time (numbers defining hours, minutes and seconds)<br/>(6) Removal date (date string)<br/>(7) Removal time (numbers defining hours, minutes and seconds)<br/>(8) Part(s) of the road network covered by the strategy (data for a digital roadmap using a standard format, e.g. GDF)<br/>(9) Set of actions for the urban road network traffic management functionality - optional (characters);<br/>(10) Set of actions for the inter-urban road network traffic management functionality - optional (characters);<br/>(11) Set of other actions - optional (characters);<br/>(12) Set of text messages to be displayed to Travellers and/or Drivers, with the identities of the equipment through which the displays shall be shown (characters).<br/><br/>The above shall represent the "minimum" set of information about each strategy.  It shall be possible for it to be supplemented by other sets of information such as comments from the Road Network Operator.  Some of the data items shall only be populated when the strategy is used, e.g. how the strategy was implemented, date/time of implementation/removal.<br/><br/>It shall be possible for the actions to be a series of commands that can be sent directly to other Functions, such as those concerned with traffic management.  Other actions shall be able to be requests for the Road Network Operator to call one or more Emergency Services, or take other action that cannot be implemented by a specific Function.<br/><br/><br/>
  • Associations To
  • Associations From
  • Tagged Values
  • Advanced
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mt_read_incident_strategies
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mt_load_incident_strategies
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
Tag Value
DataStore_SecurityLevel None
Details:
Default: None
isUnlimited false
Details:
Values: true,false
Default: false
itemKind Information
Details:
Values: Physical,Information
Default: Information
Maximum acceptable request times per application and/or service 1000
Details:
Default: 1000
Number of Users supported 1
Details:
Default: 1
Physical Capacity 1 Byte
Details:
Default: 1 Byte
Planned data storage duration over time 1 Year
Details:
Default: 1 Year
Planned Service level per application and partner None
Details:
Default: None
transaction numbers over time 10
Details:
Default: 10
Property Value
isControlType: false
ordering: FIFO