This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to provide facilities that enable the Driver of a Freight Vehicle to book parking places at loading or unloading zones along the route they are about to follow in a Vehicle Trip Plan.<br/>(2) The ability to enable such a Driver to book a parking place in a loading or unloading zone, based on the Expected Time of Arrival (ETA) according to the Vehicle Trip Plan.<br/>(3) If the booking for a parking space at a loading or unloading zone is rejected, or the ETA changes as the Vehicle Trip Plan is implemented, the ability to enable the Freight Vehicle Driver to revise the parking space booking to match the new ETA.<br/>(4) When a suitable parking space is not available a loading or unloading zone, the Function shall enable the Driver to book a parking place in a holding zone, which will be used until such time as the requested parking space in a loading or unloading zone becomes available.<br/>(5) When the Vehicle approaches the destination loading or unloading zone, or a holding zone, the ability for the Driver to be provided with details guidance about how to find the zone and how to manoeuvre the Freight Vehicle into the booked parking space.<br/>
(a) continuously monitor for receipt of the vehicle trip plan with no parking needs data flow or the trip plan with un/loading needed data flow from the Manage Use of Rest Areas function;<br/>(b) when either of the data flow in (a) is received, check to see if the vehicle trip plan shows it is necessary to book parking places in loading or unloading zones;<br/>(c) if the answer to (b) is "no", send the vehicle trip plan to the Prepare and Revise Trip Plans function in the trip plan with un/loading bookings data flow;<br/>(d) if the answer to (b) is "yes", send a list of the required parking in loading or unloading zones and a request for their confirmation to the Freight Vehicle Driver in the confirm un/loading zone parking needs data flow;<br/>(e) as a result of (d) continuously monitor for receipt of the un/loading zone use request data flow;<br/>(f) when the data flow in (e) is received, extract all of the parking requirements from the vehicle trip plan and send them to the Manage Loading or Unloading Zone Bookings function in the un/loading zone use request data flow;<br/>(g) as a result of (f) continuously monitor for receipt of the un/loading zone use response data flow from the Manage Loading or Unloading Zone Bookings function;<br/>(h) when the data flow in (g) is received, output its contents to the Freight Vehicle Driver in the un/loading zone use response data flow;<br/>(i) if the contents of the data flow in (h) was acceptance, continuously monitor for receipt of the un/loading zone use request response data flow;<br/>(j) when the data flow in (i) is received, send the confirmation of the booking acceptance to the Manage Loading or Unloading Zone Bookings function in the un/loading zone use confirmation data flow, add the details of the booked parking to the vehicle trip plan and send it to the Prepare and Revise Trip Plans function in the trip plan with un/loading bookings data flow;<br/>(k) if the content of the data flow in (h) was rejection, continuously monitor for receipt of the revised in/loading zone use request data flow from the freight vehicle driver;<br/>(l) when the data flow in (k) is received, send the new loading or unloading zone use request to the Manage Loading or Unloading Zone Bookings function in the un/loading zone use request data flow and as a result, repeat (g) to (i) and (k) until it is possible to complete (j);<br/>(m) continuously monitor for receipt of either the un/loading zone routing information, holding zone routing information, un/loading zone unavailable for new ETA, or holding zone unavailable for new eta data flows from the Manage Loading or Unloading Zone Bookings function;<br/>(n) when either of the first two data flows in (m) is received, output its contents to the Freight Vehicle Driver in either the un/loading zone routing information or holding zone routing information data flows and continue with (m), but if after a suitable time period it is not received, return to (a);<br/>(o) when either of the second two data flows in (m) is received, output its contents to the Freight Vehicle Driver in either the un/loading zone unavailable for new eta or the holding zone unavailable for new eta data flows and continuously monitor for receipt of the revised in/loading zone use request data flow from the Freight Vehicle Driver;<br/>(p) when the data flow in (o) is received, send the revised loading or unloading zone use or holding zone use request to the Manage Loading or Unloading Zone Bookings function in the un/loading zone use request data flow and continuously monitor for receipt of the un/loading zone use response data flow from the Manage Loading or Unloading Zone Bookings function;<br/>(q) repeat (g) and (h);<br/>(r) if the contents of the un/loading zone use response data flow output to the Freight Vehicle Driver in (h) was acceptance, continuously monitor for receipt of the un/loading zone use request response data flow;<br/>(s) when the data flow in (r) is received, send the confirmation of the booking acceptance to the Manage Loading or Unloading Zone Bookings function in the un/loading zone use confirmation data flow, add the details of the booked parking to the vehicle trip plan and send it to the Prepare and Revise Trip Plans function in the trip plan with un/loading bookings data flow;<br/>(t) continue with (m), but if after a suitable time period it is not received, return to (a).<br/>
