This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability to respond to the receipt of data objects containing a comment to implement a particular Freight Transport Execution Plan by requesting the content of the Plan from other functionality and proceeding to implement the Plan.<br/>(2) The ability to send instructions to functionality that provides an interface for the Freight Vehicle Driver(s) that will enable them to follow the road-based part(s) of the itinerary included in the Freight Transport Execution Plan.<br/>(3) If the Plan shows that the Freight Transport Load Item(s) constitute an abnormal load, the ability to declare this as an incident to the Manage Traffic functionality in the system so that the appropriate mitigation action can be taken.<br/>(4) If the Plan includes the use of other modes of transport, the ability to inform systems for the specified mode(s) of the expected time of arrival (eta) of the Freight Vehicle(s) carrying the Freight Transport Load Item(s).<br/>(5) If the other mode of transport in (4) above is unable to accommodate the Freight Transport Load Item(s) the ability to direct the Freight Vehicle Driver(s) to park up somewhere until the other mode becomes available.<br/>(6) Where (5) above applies the ability to report the status of the other mode of transport to the functionality that provides an interface for the Freight Transport Operations Manager. <br/>(7) The ability to recognise that an incident has occurred with the implementation of the Freight Transport Execution Plan through data objects received from other functionality and to (a) request an incident response from other functionality, and (b) to declare an incident to the Manage Traffic functionality in the system.<br/>(8) For (7)(a) the ability to implement the incident response if one is provided.<br/>(9) The ability to provide the expected location of the Freight Transport Load Item(s) to other functionality that will monitor the progress of the implementation of the Freight Transport Execution Plan.<br/>(10) The ability to send records of the Freight Transport Plan implementation status to other functionality that will compare it with the actual status for reporting to the Freight Transport Operations Manager.<br/>(11) The ability to send records of progress with the implementation of the Freight Transport Execution Plan to other functionality that will use it to analyse the way the Plan has been implemented.<br/><br/>
(a) continuously monitor for receipt of the implement FTEP data flow from the Provide FTU Interface function;<br/>(b) when the data flow in (a) is received, use its content in the request FTEP details data flow and send it to the Manage FTEP store function;<br/>(c) as a result of (b) continuously monitor for the receipt on the requested FTEP details data flow from the Manage FTEP store function;<br/>(d) commence implementation of the FTEP by sending the following:<br/> - instructions to the Freight Vehicle Driver for the Freight Vehicle identified in the FTEP to the Provide Freight Vehicle Driver Interface function in the Freight Vehicle Driver Instructions data flow,<br/> - the expected location to the Monitor FTEP implementation function in the FTLI expected location FTEP data flow, and<br/> - details of both of these data flows to the Calculate FTEP Implementation Status in the expected FTEP implementation status data flow;<br/>(e) if the FTEP requires the use of another non-road based mode of transport, send the current eta to the Provide Interface to Other Transport Modes function in the FV eta for other mode data flow;<br/>(f) as a result of (d) and (e), continuously monitor for receipt of the other mode service status data flow from the Provide Interface to Other Transport Modes function;<br/>(g) if the data flow in (f) indicates that the other transport mode will not be ready to receive the FTLI from the Freight Vehicle, then send revised instructions to the Freight Vehicle Driver in the in the Freight Vehicle Driver Instructions data flow and also send details of the change to the Provide FTOM Interface for FTEP Monitoring function in the other mode service issues data flow;<br/>(h) also as a result of (d) and (e), continuously monitor for receipt of the vehicle incident found data flow from the Calculate FTEP Implementation Status function;<br/>(i) if and when the data flow in (h) is received, send the request incident response data flow to the Manage Incident Response Data Store function and continuously monitor for receipt of the requested incident response data flow;<br/>(j) when the data flow in (i) is received, carry out the instructions that it contains, which may include sending to functionality in the Manage Traffic Functional Area (F3) either of the following:<br/> - the declare FTEP implementation incident data flow, or<br/> - if the FTLI has been classed as an abnormal load (in the FTEP data), the FTEP abnormal load incident data flow;<br/>(k) in addition to the actions in (j) repeat the last action in (d) and (e);<br/>(l) as a result of (j) continuously monitor for receipt of the incident response data flow from functionality in the Manage Traffic Functional Area (F3) and repeat (k) but with revised data flow content depending on the incident response.<br/>
