F7.1.3 Get Vehicle Information

Header Image
Project:
F7.1.3 Get Vehicle Information : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 24.10.2019 12:44:37
Modified: 08.09.2021 14:47:43
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to collect inputs from which data objects can be created to provide details about a Vehicle to check that it is complying with the rules enacted for the road network.<br/>(2) The ability to process the information if it has been collected by functionality in other Functional Areas, or by sensors connected to the Function.<br/>(3) The ability to process the information provided to the Function even if it has not been systematically checked.<br/>(4) The ability to collect inputs provided by "Weigh-In-Motion"sensors and creating data objects from them to record the weight per axle and gross weight for Freight Vehicles.<br/>(5) The ability to request the Vehicle's Driver to provide records, of route, speed, hours until the next rest stop, etc.<br/>(5) The ability to receive guidelines from functionality in the Manage Traffic Functional Area about the way that rules should be applied and compliance checked.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_High_Level_Function» F7.1 Detect Violation
FRAME_High_Level_Function «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Functional_Area» F7 Provide Support for Law Enforcement
FRAME_Functional_Area «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psle.pshvs_vehicle_ID_request
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» td-psle_record_request
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» psle_measure
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» fd-psle_record
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt.psle_urban_enforcement_guidelines
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 3.1.0.1
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fv-psle_vehicle_image
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» fv-psle_characteristics
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 3.1.0.3
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 3.1.1.4
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 3.1.0.2
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 3.1.0.4
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» pshvs.psle_vehicle_ID
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 3.1.1.3
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mt.psle_inter-urban_enforcement_guidelines_PF
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
Requirement Type Status Difficulty Priority Stability
Functional Functional Proposed Medium Medium Moderate
Details:
(a) if the second trigger input data flow is received, carry out the measure of the parameter to be checked based on its contents;<br/>(b) if the third or fourth trigger input data flows are received, collect the measure from the Manage Traffic Area;<br/>(c) ask the Driver for the delivery of the record to be controlled using the third trigger output data flow;<br/>(d) receive the record to be controlled from the Driver using the first other input data flow;<br/>(e) ask the vehicle for its identification using the first trigger output data flow and wait for a response;<br/>(f) receive the identification from the vehicle, if available using the second other input data flow;<br/>(g) extract the useful information from the measure so that it can be analysed;<br/>(h) send the measure to the Check Compliance Function using the second trigger output data flow.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0