Overview

This Function shall be capable of providing the following facilities:

(1) The ability for the Parking Operator to manage the booking of parking spaces in rest areas that form part of service areas using a HMI provided by other functionality.
(2) Upon receiving a booking request the ability to estimate the availability of parking spaces at the Estimated Time of Arrival (ETA) of the Freight Vehicle provided in the request and the information about any hazardous goods that it may be carrying that is included in the request.
(3) If a space will be available, the ability to seek confirmation from the Parking Operator (through the HMI provided by other functionality) before accepting the booking.
(4) If no parking space is available, the ability to respond to the request with alternative times when a suitable space will be available.
(5) The ability to update the confirmed booking as updates of the Estimated Time of Arrival (ETA) are received and ability to provide information about the services that are available to the Freight Vehicle Driver in the rest area in response to these updates.
(6) The ability to provide the Fleet Management Operator with details of all rest area bookings that have been made.  
(7) If the newly updated ETA is found to cause a clash with another booking, the ability to recommend an alternative time slot for the parking space booking and when confirmation is received from the Freight Vehicle, use this as the parking space booking.
(8) When data is received to indicate that the Freight Vehicle has arrived at the entrance to the rest area, the ability to provide guidance to enable the Freight Vehicle Driver to find the booked parking space.

Functional Requirements

(a) continuously monitor for receipt of the rest area parking request data flow
(b) when the data flow in (a) is received, internally store its contents and output them in the confirm rest area request data flow to the Provide Operator Interface to manage Service Areas function
(c) as a result of (b) continuously monitor for receipt of the rest area request confirmation response data flow from the Provide Operator Interface to manage Service Areas function
(d) when the data flow in (c) is received, check its contents and if it contains a confirmation then output this in the rest area parking response data flow to the Manage Freight Vehicle Rest Area Use function
(e) if the contents of the data flow in (d) contain a rejection, delete the data stored in (b), output the rejection in the rest area parking response data flow to the Manage Freight Vehicle Rest Area Use function and then return to (a)
(f) as a result of (d) continuously monitor for the receipt of the rest area parking confirmation data flow from the Manage Freight Vehicle Rest Area Use function
(g) if the data flow in (f) is not received within a specific time, implement (e)
(h) when the data flow in (f) is received, update the data in (b) to confirmed and continuously monitor for receipt of the rest area eta data flow from the Monitor Vehicle Trip Plan Implementation function
(i) when the data flow in (h) is received, check that the ETA is the same as provided in (b) and if so, send the request data for service area data flow to the Manage Inter-urban Service Area Data Store function
(j) as a result of (i) continuously monitor for receipt of the requested data for service area data flow from the Manage Inter-urban Service Area Data Store function
(k) when the data flow in (j) is received, send its contents and confirmation of the booking to the Manage Freight Vehicle Rest Area Use function in the rest area booking confirmation & information data flow
(l) if the check in (i) shows that the ETA is different check the internal store of data from (b) and updated in (h) to see if there is a parking space free for the vehicle at the new ETA
(m) if the result of (l) is that there is no space available, find a time when one will be available and send it with a rejection of the space availability for the new ETA to the Manage Freight Vehicle Rest Area Use function in the rest area unavailable for new eta data flow and continuously monitor for receipt of the data flow in (a)
(n) when the data flow in (m) is received, repeat (b) to (m)
(o) as a result of (k) continuously monitor for receipt of the freight vehicle identity for rest zone data flow from the Detect Vehicle Approaching Rest Area function
(p) when the data flow in (o) is received, sent the rest area parking details data flow to the Manage Freight Vehicle Rest Area Use function
(q) as a result of (p) continuously monitor for receipt of the freight vehicle left rest area data flow from the Monitor Vehicle Trip Plan Implementation function
(r) when the data flow in (q) is received, delete the data store in (b) and updated in (h), before returning to (a)
(s) provide details of all rest area bookings to the fleet operator in the rest area booking details data flow.

Diagrams

Parent Higher Level Function

• 3.1.5 Provide Management of Service Areas

Input logical dataflows

• mt_freight_vehicle_identity_for_rest_area
• mt_requested_data_for_service_area
• mt_rest_area_request_confirmation_response
• pshvs.mt_freight_vehicle_left_rest_areae
• pshvs.mt_rest_area_eta
• pshvs.mt_rest_area_parking_confirmation
• pshvs.mt_rest_area_parking_request

Output logical dataflows

• mt.pshvs_rest_area_booking_confirmed_&_information
• mt.pshvs_rest_area_parking_details
• mt.pshvs_rest_area_parking_response
• mt.pshvs_rest_area_unavailable_for_new_eta
• mt_confirm_rest_area_request
• mt_request_data_for_service_area
• mt_rest_area_booking_for_fleet_operator

User needs