F3.1.1.10 Collect Urban Traffic Data

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.10 Collect Urban Traffic Data

Project:

F3.1.1 Provide Urban Traffic Management

F3.1.1.10 Collect Urban Traffic Data : 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:	{26B5879E-F71D-4909-858C-63BC4C2D4F7F}
Appears In:	DFD F3.1.1 Provide Urban Traffic Management, Functional Tree of F3.1.1 Provide Traffic Control

This Function shall be capable of providing the following facilities: (1) The collection of traffic flow data from sensors that are located within the urban road network managed by the System. (2) The sensors shall be capable of detecting the presence of all types of road Vehicle, from Bicycles to Heavy Goods Vehicles. (3) The processing of the raw input data provided by the sensors into actual traffic flow data, i.e. vehicle flow rates, vehicle speeds, etc. (4) The supply of the processed raw input data to other functionality in the Manage Traffic Functional Area for collation and use. Note that this Function shall not collect any data directly from Vehicles. It shall assume that all Vehicles are passive and not capable of providing data themselves.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mt_collected_urban_traffic_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_current_traffic_data_for_demand FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_traffic_flow_management_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_traffic_data_for_incident_detection FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F3.1.1 Provide Urban Traffic Management FRAME_High_Level_Function «componentof»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_User_Need» 7.1.1.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 2.1.1.3 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.1.5 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.11.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.1.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 7.1.1.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ftrfc-urban_traffic_flow_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:

Requirement	Type	Status	Difficulty	Priority	Stability
Functional	Functional	Proposed	Medium	Medium	Moderate
Details: (a) the presence of the trigger input data flow shall be continuously monitored;<br/>(b) the analogue data representing raw traffic flow data obtained in (a) shall be processed into digital data such as, but not limited to, flow, speed, occupancy, headway, vehicle classification, and queue;<br/>(c) the data for each point in the urban road network at which it was produced shall be kept separate;<br/>(d) the trigger output data flows, shall be used to send the data in (c) to the urban road network traffic control and data management Functions.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0