F4.6 Provide Facilities for Vehicle Sharing

Frame Repository / Frame Functional View / Functionality / Functional Area F4 - Manage Public Transport Operations / F4. Manage Public Transport Operations / F4.6 Provide Facilities for Vehicle Sharing

Project:

F4.6 Provide Facilities for Vehicle Sharing : Public <<FRAME_High_Level_Function>> FRAME_High_Level_Function

Created:	24.10.2019 12:44:31
Modified:	12.11.2021 13:03:12

Project:
Author:	Update after transfer
Version:	5.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{A8C5BEF7-4F95-43ce-9B22-C4329AFFB177}
Appears In:	Functional Tree of Area F4 Manage Public Transport Operations, DFD F4 Manage Public Transport Operations

This High-level Function provides facilities that support the sharing of Vehicles by Travellers making a journey. These Travellers are identified by the Car Pooler Terminator and are able to set up travel plans for a journey in which they combine with other Car Poolers to share the use of their Vehicles. A travel plan may link up to the current PT services, or the services provided by other transport modes and may involve the use of car parks or service areas as places to start/finish particular segments of the journey. Once all the car poolers in a travel plan have accepted it, the implementation is up to them. Thus a travel plan may be for a single journey or for multiple repeats of the same journey, depending on the needs of the Car Poolers who are involved. For security reasons, a car pooler can only find out about the travel plan(s) in which they are personally involved and can only contact other car poolers in that travel plan through the communications mechanism that each provides. Payment for the Vehicle sharing is not included in the functionality.<br/>

Associations To
Associations From
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» to.pto-current_travel_plan_criteria FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_requested_travel_plan_criteria FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_accepted_travel_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_travel_plan_accepted FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_proposed_travel_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_PT_fares_for_vehicle_sharing FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_read_vehicle_sharing_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_travel_plan_criteria_request FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_travel_plan_criteria_update FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.vs-deregistration FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_load_vehicle_sharing_data FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_travel_plan_rejected FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fo.pto-request_travel_plan_criteria 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_Low_Level_Data_Flow» mt.mpto_requested_car_park_details FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_request_existing_travel_plans FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fo.pto-updated_travel_plan_criteria FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_requested_current_travel_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» tt.vs-vehicle_sharing_outputs FRAME_High_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.mt_request_service_area_details FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.mpto_inter-urban_road_network_details FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tt.vs-current_travel_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.vs-travel_needs FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.vs-request_current_travel_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tt.vs-proposed_travel_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» tmms.mms-service_details_request FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.mt-vehicle_sharing_requests FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.vs-personal_details 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_request_current_travel_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_requested_travel_plans FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.mpto_urban_road_network_details FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» ft.vs-accept_travel_plan FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mt.mpto_requested_service_area_details FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto.mt_request_car_park_details FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_Low_Level_Function» F4.6.2 Create Travel Plans for Vehicle Sharing FRAME_Low_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» mpto_PT_data_for_vehicle_sharing FRAME_High_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» mt.mpto_requested_parking_details FRAME_High_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Function» F4.6.4 Provide Operator Interface for Vehicle Sharing FRAME_Low_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» ft.vs-vehicle_sharing_inputs FRAME_High_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» mt.mpto_road_network_details FRAME_High_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_High_Level_Data_Flow» fo.pto-vehicle_sharing_inputs FRAME_High_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fmms.mms-service_details_response FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Function» F4.6.3 Manage Vehicle Sharing Information FRAME_Low_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» flds-vehicle_sharer_location FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Function» F4.6.1 Provide Vehicle Sharer Interface FRAME_Low_Level_Function «componentof»	Name:	Name:
Details:

Property	Value
isReadOnly:	false
isFinalSpecialization:	0