F4.1.15 Provide PT Vehicle Driver Interface

Frame Repository / Frame Functional View / Functionality / Functional Area F4 - Manage Public Transport Operations / F4. Manage Public Transport Operations / F4.1 Monitor PT fleet / F4.1.15 Provide PT Vehicle Driver Interface

Project:

F4.1 Monitor PT fleet

F4.1.15 Provide PT Vehicle Driver Interface : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function

Created:	24.10.2019 12:44:31
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:	{61CB146E-2271-49ed-8085-40133EBA3E2E}
Appears In:	Functional Tree of Area F4 Manage Public Transport Operations, DFD F4.1 Monitor PT fleet

This Function shall be capable of providing the following facilities: (1) Support for both data and voice dialog between the PT Driver and the Collect PT Vehicle Data functionality through a suitable HMI for use in situations that are not included in updates provided by regularly transmitted data, e.g. emergencies, special messages to drivers, etc. (2) The output of other PT Vehicle data and alarm information to the PT Driver through a suitable HMI. (3) The ability of the PT Driver to use a suitable HMI to request information about the service (schedule and fares) on which the PT Vehicle is to be used and for that information to be displayed.

Associations To
Associations From
Requirements
Advanced

Element	Source Role	Target Role
«FRAME_Low_Level_Data_Flow» mpto_request_schedule_for_vehicle 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» td.ptd-messages FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_High_Level_Function» F4.1 Monitor PT fleet FRAME_High_Level_Function «componentof»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_request_fares_for_vehicle FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» td.ptd-data_and_alarm_outputs FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_message_from_driver FRAME_Low_Level_Data_Flow «IN»	Name:	Name:
Details:

Element	Source Role	Target Role
«FRAME_User_Need» 10.1.5.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_requested_fares_for_vehicle FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fd.ptd-assign_vehicle_to_service FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_User_Need» 10.2.4.1 FRAME_User_Need «Servedby»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_vehicle_data_and_alarms_for_driver FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» fd.ptd-messages FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_requested_schedule_for_vehicle FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:
«FRAME_Low_Level_Data_Flow» mpto_message_to_driver FRAME_Low_Level_Data_Flow «OUT»	Name:	Name:
Details:

Requirement	Type	Status	Difficulty	Priority	Stability
Functional	Functional	Proposed	Medium	Medium	Moderate
Details: (a) continuously monitor for the arrival of input data flows from PT Drivers;<br/>(b) send messages from the PT Driver to the Collect PT Data function in the message from driver data flows<br/>(c) continuously monitor for the arrival of the message to driver data flow;<br/>(d) when the data flow in (c) arrives immediately output its contents to the PT Driver;<br/>(e) continuously monitor for the receipt of the assign vehicle to service data flow from the PT Driver;<br/>(f) when the data flow in (e) arrives, put the identity of the service that it contains into the request schedule for vehicle and request fares for vehicle data flows and send them to the Plan New Service Schedule and Manage Fare Schemes Data Store functions;<br/>(g) as a result of (f) continuously monitor for the receipt of the requested service for vehicle and requested fares for vehicle data flows<br/>(h) when the data flows in (g) arrives, store the data locally within the function.<br/>

Property	Value
isReadOnly:	false
isFinalSpecialization:	0