F4.2 Plan PT Service

Frame Repository / Frame Functional View / Functionality / Functional Area F4 - Manage Public Transport Operations / F4. Manage Public Transport Operations / F4.2 Plan PT Service

Project:

F4.2 Plan PT Service : Public <<FRAME_High_Level_Function>> FRAME_High_Level_Function

Created:	24.10.2019 12:44:32
Modified:	12.11.2021 13:03:00

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{11256DFE-FADE-493f-803F-220E79388CDC}
Appears In:	Functional Tree of Area F4 Manage Public Transport Operations, DFD F4 Manage Public Transport Operations

This High-level Function shall perform the strategic planning of all the Public Transport services on the basis of all available information about the availability of resources and a record of historical data. The scheduling of all the Public Transport services shall mainly be performed off-line according to parameters such as analysis of demand, revenue, fleet and personnel resources, etc. It shall take into account the configuration of the road network so that the routes that are used by the services will be accessible to Public Transport vehicles. Specific functionality dealing with the planning of car-pooling services, according to the demand and availability of travellers and drivers, shall also be provided. Availability of on-demand services shall also be defined by this Function as well as all definition and management of tariff schemes.<br/>

Associations To
Associations From
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mpto.ptja_available_pt_services FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_service_planning_strategies FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» mpto_PT_data_for_vehicle_sharing FRAME_High_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.pepf_fare_schemes FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» to.pto-requested_route_static_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» mpto_service_information FRAME_High_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_route_static_data_for_reports FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_PT_services_in_operation FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_read_fare_scheme FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_updated_fare_scheme FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_current_fare_scheme FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_load_fare_scheme FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Functional_Area» F4. Manage Public Transport Operations FRAME_Functional_Area «componentof»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» mpto.mt_services_and_fares FRAME_High_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fo.pto-route_static_data_update FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_fare_scheme_planning_strategies FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tors.ptms-pt_planning FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» to.pto-revised_services FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» to.pto-pt_planning_outputs FRAME_High_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.ptja_pt_services_for_trip_monitoring FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_request_current_static_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» to.pto-revised_fare_schemes FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_load_static_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tmms.mms-plannings FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.ptja_current_fares FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» mpto_PT_data_for_demand_services FRAME_High_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.pscs_PT_services_and_schedules FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_revised_services_and_schedules FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_revised_fare_schemes_for_operators FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_route_static_data_updates FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fo.pto-request_route_static_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mpto_fare_scheme_for_PT_driver FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» mt.mpto_PT_service_planning_inputs FRAME_High_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.mpto_request_incident_service_change FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Function» F4.2.7 Manage PT Route Data Store FRAME_Low_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Function» F4.2.5 Prepare Fare Schemes FRAME_Low_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» mpto_service_&_scheduling_data FRAME_High_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» mt.mpto_request_changes FRAME_High_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» fo.pto-pt_planning_inputs FRAME_High_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fesp.peo-planned_events FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» mpto_request_service_data FRAME_High_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Function» F4.2.9 Provide PT Operator Interface for PT Service Plans FRAME_Low_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_PT_driver_request_for_fare_scheme FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Function» F4.2.6 Manage Fare Schemes Data Store FRAME_Low_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fmms.mms-plannings FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_fare_scheme_for_service FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Function» F4.2.8 Plan New PT Service Schedule FRAME_Low_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» mpto_route_data_for_planning_&_reports FRAME_High_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fors.ptms-pt_planning FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_maintenance_plans FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Function» F4.2.10 Manage PT Service Plan Data Store FRAME_Low_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_typical_travel_times FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:

Property	Value
isReadOnly:	false
isFinalSpecialization:	0