Overview

This Function shall be capable of providing the following facilities:

(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.
(2) The ability to check the received data for consistency before being sent to another part of the System functionality for storage.

Functional Requirements

(a) when any of the trigger flows is received, the data shall be collected and checked for consistency
(b) the time and date stamps shall be added if found to be missing
(c) similarly the source identity shall be added if it is not found in the data, using the origin Function of the data flow
(d) if the location is not included in the data, it shall be marked as "unknown"
(e) when (b) through to (d) are complete the data shall be sent for storage using the trigger output data flow.

Diagrams

Parent Higher Level Function

• 3.3 Manage Demand

Input logical dataflows

• fmms.mms-ferry_service_information
• fmms.mms-rail_service_information
• fws-weather_information
• mpto.mt_current_fares
• mpto.mt_current_services
• mpto.mt_PT_service_variations
• mt_carpark_occupancy_for_demand_management
• mt_demand_management_environmental_data
• mt_inter-urban_current_traffic_data_for_demand
• mt_inter-urban_traffic_data_for_demand
• mt_service_area_occupancies_for_demand_management
• mt_urban_current_traffic_data_for_demand
• mt_urban_traffic_data_for_demand
• pepf.mt_infra_usage_info

Output logical dataflows

• mt_updated_demand_data

User needs