F4.2.5 Prepare Fare Schemes

Header Image
Project:
F4.2.5 Prepare Fare Schemes : Public <<FRAME_Low_Level_Function>> FRAME_Low_Level_Function
Created: 24.10.2019 12:44:32
Modified: 08.09.2021 11:24:40
Project:
Advanced:
This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to prepare new fare schemes for the current and new PT Service Plans according to the current fare policy whenever the Plans are created and/or changed.<br/>(2) Once they have been created, the ability to provide details of the new fare schemes directly to other functionality in the Manage PT and Provide Traveller Journey Assistance Functional Areas.<br/>(3) Also once they have been created, the ability to provide details of the new fare schemes to the functionality that manages the fare scheme store of data and provides the PT Operator interface.<br/>
  • Associations To
  • Associations From
  • Requirements
  • Advanced
Element Source Role Target Role
«FRAME_High_Level_Function» F4.2 Plan PT Service
FRAME_High_Level_Function «componentof»
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.pepf_fare_schemes
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_fare_schemes_for_travellers
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.ptja_current_fares
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_PT_fares_for_demand_services
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_Functional_Area» F4. Manage Public Transport Operations
FRAME_Functional_Area «componentof»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_fare_schemes_for_stops
FRAME_Low_Level_Data_Flow «IN»
Name:  
 
Name:  
 
Details:
 
Element Source Role Target Role
«FRAME_Low_Level_Data_Flow» mpto_PT_services
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_current_fare_scheme
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 7.3.2.4
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_fare_scheme_planning_strategies
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
«FRAME_User_Need» 4.1.0.4
FRAME_User_Need «Servedby»
Name:  
 
Name:  
 
Details:
 
«FRAME_Low_Level_Data_Flow» mpto_fare_strategies
FRAME_Low_Level_Data_Flow «OUT»
Name:  
 
Name:  
 
Details:
 
Requirement Type Status Difficulty Priority Stability
Functional Functional Proposed Medium Medium Moderate
Details:
(a) when the PT services data flow is received, store the data objects it contains locally for later use;<br/>(b) when the fare strategies data flow arrives, extract the overall fare strategies that it contains (e.g. card products, seasonal tickets, sales policy, child fares, fares for elderly people, bicycles, guide dogs, etc.) and store internally;<br/>(c) following the receipt of the data flows in either (a) or (b), re-calculate the fares for the services using the fare strategies that they have provided, plus the service details obtained using the data flow in (c);<br/>(d) send the results of (c) to the Manage Fare Schemes Data Store function using the updated fare scheme data flow and to the Provide PT Operator Interface to PT Schedule Plans function using the revised fare scheme for operator data flow;<br/>(e) output the new fares produced as a result of (c) to the Provide Electronic Payment Facilities and Provide Traveller Journey Assistance Areas using the appropriate output data flows;<br/>(f) also send the new fares produced as a result of (c) to the Vehicle Sharing and other functionality.<br/>
Property Value
isReadOnly: false
isFinalSpecialization: 0