F4.2.8 Plan New PT Service Schedule

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

Project:

F4.2 Plan PT Service

F4.2.8 Plan New PT Service Schedule : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

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

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{6646E43B-CB56-4531-A39F-0D4D27299BFC}
Appears In:	Functional Tree of Area F4 Manage Public Transport Operations, DFD F4.2 Plan PT Service

This Function shall be capable of providing the following facilities: (1) The ability to prepare new PT Service Plans at the request of the PT Operator, taking account of constraints such as, the geographic area to be served, quality of service parameters (e.g. frequency of Vehicles, required routes), timetables, synchronisation, PT Driver duty scheduling, co-ordination with other modes of transport, etc. (2) The ability to also prepare new PT Service Plans that are variations in the normal service provision when input is received about such things as special events, unusual traffic conditions, changes in the services provided by other PT operations, the occurrence of incidents that affect the flow of traffic in the road network and requests resulting from the implementation of a demand management strategy. (3) The ability to send the newly prepared PT Service Plans to the Manage PT Service Plan Data function for use by other PT functionality and to other Functional Areas, such Provide Traveller Journey Assistance, where it will be used to plan Travellers' trips. (4) The ability to also send newly prepared PT Service Plans to other instances of this functionality such as different PT service providers and the operators of other transport modes.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mpto_updated_scheduling FRAME_Low_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_revised_services_and_schedules FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_fare_strategies 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_Low_Level_Data_Flow» mpto_PT_schdeules_for_demand_services 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» mpto.mt_current_services FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_PT_schedules_for_vehicle_sharing FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F4.2 Plan PT Service FRAME_High_Level_Function «componentof»	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» tmms.mms-plannings FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_requested_schedule_for_vehicle FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.ptja_available_pt_services FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mpto_route_data_for_planning FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_request_schedule_for_vehicle FRAME_Low_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_Low_Level_Data_Flow» mt.mpto_request_incident_service_change FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 2.1.0.1 FRAME_User_Need «Servedby»	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_typical_travel_times FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.mpto_road_network_traffic_predictions FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.mpto_traffic_management_strategies FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_PT_scheduling FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.0.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_maintenance_plans FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.0.4 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.mpto_request_demand_service_change FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.0.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.1.3 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fors.ptms-pt_planning FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.1.1.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_service_planning_strategies FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:

Requirement	Type	Status	Difficulty	Priority	Stability
Functional	Functional	Proposed	Medium	Medium	Moderate
Details: (a) collect planning strategies, plans for road works, other (Multi-Modal and similar, i.e. Road Related) services planning, plans for special events, predicted traffic conditions, historic journey times and specific service requests using the relevant input data flows;<br/>(b) obtain the details of the existing PT Service Plans from the Manage PT Service Plan Data Store using the updated scheduling data flow to request and the PT scheduling data flow to provide the details;<br/>(c) enable the PT Operator to combine the above information and requirements and initiate the definition of a new PT Service Plans including fares strategies, using the service planning strategies data flow;<br/>(d) make the selected the new PT Service Plans available to other functions in the Manage PT and Manage Traffic Functional Areas using the relevant output data flows;<br/>(e) also make the new PT Service Plans available to other (Multi-Modal and similar, i.e. Road Related) systems using the planning output data flows<br/>(f) send the new PT Service Plans to the Manage PT Service Plan Data Store function for loading into that Data Store the updated scheduling data flow;<br/>(g) send the new PT Service Plans to the Provide PT Operator Interface to PT Schedule Plans function using the revised services and schedules data flow.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0