Overview

This Function shall be capable of providing the following facilities:

(1) The ability to manage the operation of a PT stop used by PT Vehicles using real-time, static and fare information that it has received from other PT management functionality and from other PT stops.
(2) The ability to collate, filter and fuse all the received data and to present it at the PT Stop using a suitable HMI to Static Travellers, i.e. Travellers who have commenced their trips but are not actually moving because they are waiting for a PT service to arrive at the stop.
(3) The data filtering process shall remove all information that is not relevant to PT Services that use the PT stop and because its location is known, any information that is not geographically relevant.
(4) The ability to detect any unexpected activity in the area surrounding its location and provide an emergency call facility for use by Static Travellers at the PT stop.
(5) When an emergency notification is received, the ability to forward it to the Provide Safety and Emergency Facilities functionality and output the acknowledgement that is received.
(6) The ability to send all the data it has collected to any adjacent PT stops for them to similarly process and where relevant output to Travellers.
(7) The ability to output information to those with disabilities, e.g. deafness and blindness.
(8) The ability to continuously monitor its operation and when a problem is detected, send a message to the Monitor PT infrastructure functionality.

Functional Requirements

(a) continuously monitor for the arrival of the data flows containing service information for stops, service change information for stops and arrival prediction data
(b) when any of the data flows in (a) is received, process and filter their contents to remove information that is not relevant to and static travellers at the stop service by the function
(c) output the results of (b) to the static traveller in the service information from stop or arrival prediction data flows
(d) if the route static data for stops or fare schemes for stops data flows are received, store their data locally so that it can be used to determine which are the next and previous stops for each PT service
(e) if the service information for stops is received in (a) send its contents to other stops in the data flow containing arrival prediction data
(f) continuously monitor the traveller presence at stop data flow and for every change, send the passenger numbers at stop data flow to the Optimise PT Fleet Control function
(g) continuously monitor for the receipt of the traveller emergency at stop data flow
(h) when the data flow in (g) is received, send the PT stop alarm notification data flow to the functionality in the Provide Safety Emergency Facilities Functional Area
(i) when as a result of (h) the PT stop alarm acknowledgement data flow is received, output its contents to the static traveller using the alarm acknowledgement data flow
(j) if any problems occur with (a) to (i), send a report of the problem to the Monitor PT Infrastructure function in the faulty PT stop data flow.

Diagrams

Parent Higher Level Function

• 4.1 Monitor PT fleet

Input logical dataflows

• fors.pts-arrival_prediction_data
• ft.st-traveller_emergency_at_stop
• ft.st-traveller_presence_at_stop
• mpto_fare_schemes_for_stops
• mpto_route_static_data_for_stops
• mpto_service_change_information_for_stops
• mpto_service_information_for_stops
• psef.mpto_PT_stop_alarm_acknowledgement

Output logical dataflows

• mpto.psef_PT_stop_alarm_notification
• mpto_alarm_at_stop
• mpto_faulty_PT_stop
• mpto_passenger_numbers_at_stop
• tors.pts-arrival_prediction_data
• tt.st-alarm_acknowledgement
• tt.st-service_information_from_stop

User needs