This Function shall be capable of providing the following facilities:<br/><br/>(1) The ability for Vehicle Sharers to create travel plans only in response to a request for a new travel plan from a Vehicle Sharer. <br/>(2) The details of the travel plan must show the requesting Vehicle Sharer showing how they will travel from their origin place to their desired destination using either their own Vehicle (with other Vehicle Sharers) or as passengers in Vehicles belonging to one or more other Vehicle Sharers.<br/>(3) It shall be possible for the implementation of a new travel plan to be conditional on its acceptance by any Vehicle Sharers that will be affected, because their existing travel plans will be changed.<br/>(4) It shall also be possible for a travel plan to use of the current PT Services, travel services provided by other modes and meeting points in car parks<br/>(5) The ability for the criteria used to create travel plans to be made available to the PT Operator through a HMI provided by a separate function.<br/>(6) It must not be possible for the PT Operator to obtain information about individual Vehicle Sharers.<br/>(7) The ability to obtain data about existing travel plans and Vehicle Sharers through the functionality that manages the store of Vehicle Sharer Data.<br/>(8) The ability to exchange travel plan data with the functionality providing the HMI for Vehicle Sharers, so that new travel plans can be displayed, modified and approved, at which point they will be sent to the functionality that manages the store of Vehicle Sharer Data for future use.<br/>(9) The ability to modify created travel plans in response to requests from Vehicle Sharers.<br/>
(a) continuously monitor for receipt of the Vehicle Sharer travel needs, travel plan criteria request and travel plan criteria update data flows;<br/>(b) when as a result of (a) the vehicle sharer travel needs data flow is received, send the request existing travel plans data flow to the Manage Vehicle Sharing Information function;<br/>(c) also send the service details request to the Other Modes plus the request service area details and request car park details data flows to functionality in the Manage Traffic Functional Area;<br/>(d) when as a result of (b) and (c) the requested data flows are received create a travel plan based on the travel needs, using the criteria provided by the PT Service provider, the data that has just been obtained and any other data that is stored internally about the inter-urban and urban road networks, plus PT Service schedules and fares;<br/>(e) when as a result of (d) a new travel plan has been created, send its details to the Provide Vehicle Sharer Interface function in the proposed travel plan data flow;<br/>(f) as a result of (e) monitor for the arrival of either the travel plan rejected or travel plan accepted data flows;<br/>(g) if the travel plan rejected data flow is received in (f) then repeat (d) and (e) revising the travel plan according to the reasons for rejection provided by the Vehicle Sharer;<br/>(h) if the travel plan accepted data flow is received in (f) send it to the Manage Vehicle Sharing Information function using the accepted travel plan data flow;<br/>(i) continuously monitor for the receipt of the inter-urban road network details, urban road network details, PT schedules for vehicle sharing and PT fares for vehicle sharing, internally storing the data that they contain whenever they are received;<br/>(j) when the travel plan criteria request data flow in (a) is received send the current criteria to the Provide Operator Interface for Vehicle Sharing function in the requested travel plan criteria data flow;<br/>(l) when the travel plan criteria update data flow is received in (a) update the internal store with the new criteria and use them in all future travel plan creations as described in (d).<br/>
