F3.3.1 Receive Information on Travel Factors

Frame Repository / Frame Functional View / Functionality / Functional Area F3 - Manage Traffic / F3. Manage Traffic / F3.3 Manage Demand / F3.3.1 Receive Information on Travel Factors

Project:

F3.3 Manage Demand

F3.3.1 Receive Information on Travel Factors : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

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

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{01E4D2F5-D6A8-4237-8467-FC7D0544A4D4}
Appears In:	DFD F3.3 Manage Demand, Functional Tree of F3.3 Manage Demand

This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to receive data about the use of transport modes by Travellers in the geographic area served by the System from other functionality in the System, and/or external entities such as the Weather Service and Multi-Modal Systems.<br/>(2) The ability to check the received data for consistency before being sent to another part of the System functionality for storage.<br/>

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mt_updated_demand_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F3.3 Manage Demand FRAME_High_Level_Function «componentof»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» pepf.mt_infra_usage_info FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fmms.mms-ferry_service_information FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_inter-urban_current_traffic_data_for_demand FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_service_area_occupancies_for_demand_management FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_current_traffic_data_for_demand FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_inter-urban_traffic_data_for_demand FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.mt_PT_service_variations FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fmms.mms-rail_service_information FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.mt_current_services FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_carpark_occupancy_for_demand_management FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fws-weather_information FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.mt_current_fares FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 7.3.0.2 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_demand_management_environmental_data FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt_urban_traffic_data_for_demand FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:

Requirement	Type	Status	Difficulty	Priority	Stability
Functional	Functional	Proposed	Medium	Medium	Moderate
Details: (a) when any of the trigger flows is received, the data shall be collected and checked for consistency;<br/>(b) the time and date stamps shall be added if found to be missing;<br/>(c) similarly the source identity shall be added if it is not found in the data, using the origin Function of the data flow;<br/>(d) if the location is not included in the data, it shall be marked as "unknown";<br/>(e) when (b) through to (d) are complete the data shall be sent for storage using the trigger output data flow.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0