Back office HMI prototype

Transcription

1 EUROPEAN COMMISSION SEVENTH FRAMEWORK PROGRAMME GA No Cooperative dynamic formation of platoons for safe and energy-optimized goods transportation D5.3 Back office HMI prototype Deliverable No. COMPANION D5.3 Deliverable Title Back office HMI prototype Dissemination level Written By Thomas Friedrichs (OFFIS) 31/05/2016 Checked by Jonas Mårtensson (KTH) WP leader 14/06/2016 Approved by Magnus Adolfson (Scania) Coordinator 28/06/2016 Issue date 15/06/2016

2 History log Name Status Version Date Summary of actions made OFFIS Editor 1 31/05/2016 First draft Thomas Friedrichs Scania Reviewer /06/2016 Reviewed the document Magnus Adolfson OFFIS Thomas Friedrichs Editor /06/2016 Extended description of transport assignments, layout, and minor improvements Jonas Mårtensson KTH Reviewer /06/2016 Reviewed the document Thomas Friedrichs OFFIS Editor /06/2016 Included requirements, changed according to reviewer comments 2 / 20

3 Executive summary The off-board HMI is a website deployed in the Azure cloud together with the other services of COMPANION. It is a prototype of a system that would be used by dispatchers of transport companies to enter transport assignments which are being automatically coupled with a specific transport plan that includes platooning opportunities, a route and also estimated fuel savings. Further the interface can be used to manually confirm transport assignments which are then transferred to the designated truck. Another function is the live tracking of the position and status of a transport assignment. Dispatchers can use the HMI to get an overview of the current status of the whole fleet. Here, individual vehicles are being clustered on the map so that in case the fleet includes a large amount of trucks the monitoring of the fleet is still possible and straightforward. The update intervals of the live tracking capabilities can be set by the user to attribute to slower internet connections. Details on fuel savings and platooning benefit are provided to measure the effect of platooning. The development of the off-board HMI was conducted with the help of CEREZUELA who provided useful insight about the needed information and interaction metaphors. 3 / 20

4 Contents History log 2 Executive summary 3 Contents 4 1. Acronyms list 5 2. Introduction 6 3. Transport Assignments Details view Creation and Deletion Fleet State Details view Statistics On-board view Technical details 19 4 / 20

5 1. Acronyms list Acronym HMI KPI TA MVC ETA Meaning Human-machine interface Key performance indicator Transport assignment Model-view-controller Estimated time of arrival 5 / 20

6 2. Introduction This report constitutes the deliverable D5.3: Back office HMI prototype. It is the results of the work within the task T5.3: Development of off-board HMI and interaction paradigms. The overall objective of task T5.3 was to develop a human-machine interface (HMI) for the interaction between platoon operators and the platoon scheduling system. In our case, platoon operators are dispatchers of transport companies who use the HMI for all their administrative tasks in the whole platooning lifecycle. The platooning lifecycle for dispatchers consists of creation of a Transport Assignment (TA), management of TA s, and the monitoring of them. Requirements for the off-board HMI were collected and presented in D2.3 (Final user requirements) and D2.4 (Technical requirements). In Table 1, all requirements related to the functional development off-board HMI are listed including the sections of this document describing the implementation. Description Fulfilled an explained in section UR3 Dispatchers must be able to create transport Creation and Deletion assignments UR4 Dispatchers should be able to get an overview of 3 - Transport Assignments all assignments UR5 Dispatchers must be informed of an upcoming 3 - Transport Assignments assignment UR8 Before departure dispatchers must be able to get 3 - Transport Assignments information about the estimated effects of platooning UR27 Dispatchers must be informed about a delay and 4 - Fleet State the reason for it UR28 After completion, dispatchers must be able to get 5 - Statistics information about the estimated effects of platooning TR OFF 14 Create and delete transport assignments Creation and Deletion TR OFF 15 It should be possible to track the status of all 4 - Fleet State current, future and past assignments TR OFF 16 In a map overview, all relevant assignments should 4 - Fleet State be visualized according to their current location and status TR OFF 17 It should be possible to gather the detailed status Details view of an individual assignment, including position of the truck, deviations and estimated arrival time TR OFF 18 It should be possible to receive information about the platooning benefit of an individual assignment Details view Table 1 - User requirements and technical requirements related to the development of the off-board HMI 6 / 20

7 The HMI is deployed in the Microsoft Azure Cloud. The implementation facilitates a series of thirdparty libraries and services which are listed in this paper. In the following chapters we will present the HMI and explain how it is used. The creation, management, and monitoring of Transport Assignments is presented in Chapter 3. Concerning the monitoring of currently executed Transport Assignments, in Chapter 4 we will demonstrate the tracking of trucks and how they can be monitored in real-time. In the Statistics part in Chapter 5 we will demonstrate how the HMI reflects the benefits of platooning with numbers on fuel savings. An extension of the work is presented in Chapter 6 where we introduce the on-board version of the HMI which a driver can use to monitor the currently assigned Transport Assignment including a map and assignment data. 7 / 20

8 3. Transport Assignments There is a distinction between transport assignments and transport plans. Dispatchers create transport assignments where they enter the following information: Description Start location Destination location Arrival time Load in kg Driver Vehicle Every transport assignment is stored in a database and receives a unique identifier. In the next step, each transport assignment is automatically processed and several alternative transport plans are created for each assignment. Transport plans contain more specific information about the transport: Departure time Time of departure calculated depending on arrival time, route length, traffic and platooning opportunities Duration Duration of the transport in hours, minutes, and seconds Route length Length of the route in km Predicted and real fuel consumption Consumption values indicating possible and actual savings Route The planned route from start to destination. This is a list of Latitude/Longitude values This data is used in the off-board HMI. In other parts of the COMPANION back end system, transport plans contain more detailed information about a transport. In the current version of the off-board HMI, dispatchers can only confirm one transport plan, which is the most optimal one for a transport assignment. In the summary all existing transport assignments are listed (see Figure 1). On the highest level, the list integrates tabs to show all, planned, upcoming, and current transport assignments. This separation is based on the different status of transport assignments. Undefined Registered Transport assignment entered in the system Planned One or more transport plans are created WaitingToBeConfirmed A dispatcher has to confirm the assignment Confirmed The assignment was confirmed by a dispatcher ReadyForExecution The actual plan is confirmed and ready for execution Executing The plan for the assignment is currently executing Done The assignment is done Cancelled Assignments can be cancelled instead of deleted 8 / 20

9 The All tab lists all assignments. Planned only includes transport assignments that have the status Waiting to be confirmed, Planned, and Registered. With this separation dispatchers can confirm assignments quickly. Throughout all tabs in this view, the list of assignments includes the following information: Description (the name of an assignment), Arrival Time (the defined time of arrival at the destination), ID (continuous identification number), Estimated Departure Time (the calculated time of departure), Load, Status (the Transport Assignment status), Plan Status (status of the Transport Plan), and Benefit (the fuel benefit in liters with platooning). Further in each row on the very right side there are the action links Confirm, Details, and Delete to either confirm, request details, or delete a specific transport assignment. Figure 1 - Transport Assignments summary The Planned is vertically separated in two sections: Assignments that have to be confirmed by the dispatcher (status Waiting to be confirmed ) are listed in the upper half, while registered and planned assignments appear in the lower half of the view. Assignments that have to be confirmed are separated because here the dispatcher manually has to confirm each assignment so that it can be sent to the truck. Assignments with this status already have a platooning plan and need the approval by the dispatcher. Registered assignments with the plan status undefined don t have a platooning plan yet and will be listed as to be confirmed as soon as they have a platooning plan assigned. As an additional support for the dispatcher, in the tab title there is a numerical indicator showing the current number of assignments that have to be confirmed (see Figure 2). 9 / 20

10 Numerical indication for to be confirmed assignments Figure 2 - Planned Assignments including registered and waiting to be confirmed In the tab Upcoming transport assignments with the status Confirmed and ReadyForExecution are listed. Here the assignment status is set to confirmed which means that the dispatcher approved the plan and the transport plan is sent to the vehicle for execution (see Figure 3). Figure 3 - Upcoming and confirmed transport assignments The section Current includes all transport assignments that are being executed currently. 10 / 20

11 3.1 Details view The details view contains extended information about a transport assignment. Besides the initial dispatcher information this view includes a temporary route which is calculated using a Google service for illustration purposes, see Figure 4. Figure 4 - Details of a transport assignment including a temporary route 3.2 Creation and Deletion Dispatchers can create new transport assignments by clicking on Create New beneath the headline. By doing so the create view is being displayed and the details of the transport can be entered (see Figure 5). In the first step, the dispatcher has to enter a name for the Assignment. After this, in the Origin Location text field the starting point of the transport has to be defined. This can either be done by entering an address, a name of a destination (e.g. Scania Södertälje ), or by entering a Latitude/Longitude combination. While typing, a google search is being performed in the background to look up the location name. If the desired location is found (i.e. names of towns, street names, names of companies or points of interest), the corresponding entry can be selected by clicking on it. 11 / 20

12 Click Figure 5 - Create new assignment view After this, a marker is placed on the map indicating the starting location of the transport (see Figure 6). Further, the Latitude/Longitude value of the location is shown under the text box. Dispatchers can refine the starting location by dragging the marker to a more appropriate location: The marker can be relocated by dragging it to a new position Figure 6 - Specified starting location of a transport and marker indicating the exact location 12 / 20

13 After the starting location has been set, the destination location can be entered using the same approach as for the starting location. To demonstrate the possibility of entering Latitude/Longitude values, Figure 7 illustrates this approach exemplarily. Figure 7 - Destination location setting using Latitude/Longitude coordinates The next step of the creation process is the selection of the planned arrival time. In COMPANION the dispatchers set the arrival time first and the departure time is calculated backwards. This approach is based on the preferences of transportation companies and allows dispatchers to enter all assignment data without having to set a departure time manually. The arrival time can be specified with a date picker object as shown in Figure 8. Figure 8 - Demonstration of picking an arrival time with the date picker 13 / 20

14 The last step of the creation process is the definition of the load in KG, the assignment of a vehicle for the transport and a driver. After all information has been entered, the assignment can be saved in the database by clicking on Create at the bottom of the page as depicted in Figure 9. Figure 9 - All information has been entered. The assignment can be saved by clicking on "Create". Transport assignments can also be deleted by pressing the Delete link in the transport assignments overview page (see Figure 1). 14 / 20

15 4. Fleet State The Fleet State overview can be used to track the position of the own fleet as shown in Figure 10. The position information update interval can be specified by the dispatcher using the corresponding dropdown menu. The map supports clusters which are very useful for a large amount of trucks being visualized at the same time. By clicking on a cluster icon, the map zooms into the cluster details and shows individual markers, each representing one vehicle. By clicking on a marker, a label appears which includes a hyperlink to the assigned transport plan for further inspection. In the table list below the map all trucks are listed including information about the assigned plan (Description), the number of truck platooning (Platoon size), the current location in Latitude/Longitude values. Further the position is shown in a human readable format using the Google service to lookup an address based on Latitude/Longitude values. The current deviation time is also listed in minutes, which is also connected to the Deviated columns indicating if a vehicle is behind the plan. The column Last Updated Time show when the last update from the vehicle has been sent to the off-board system and indicates if the information shown is up-to-date. In the last column the Platooning benefit is shown, which is the fuel saved per truck for this transport in liters. On the very right side the Details button can be used to further inspect the status of the truck. Figure 10 - Fleet state overview. Individual trucks are represented with markers. The table list below shows current information about the individual trucks. 15 / 20

16 4.1 Details view The details view, see Figure 11 - Details view for a specific truck, includes extended information about a specific truck and also visualizes the calculated route from the Fleet Manager. The view presents details about the vehicle, the assignment ID and also the plan ID which can change due to automatic recalculations. Next to the assignment name there is the length of the route. It has to be noted that the presented route is exemplarily and is not detailed enough to be used in real transportation. The fuel consumption indicator at the bottom of the page shows the current and estimated fuel consumption for the transport using a horizontal bar chart. The map is being updated automatically every second so that the position of the truck (marker currently not visible) can be tracked in real time. Figure 11 - Details view for a specific truck 16 / 20

17 5. Statistics Statistical data is mainly shown in the Statistics section of the website, see Figure 12. An overall distribution of the status of all transport assignments can be found on the left. On the right side are the platooning benefits. These are from top to bottom: - Percentage of kilometers driven in platoons compared to the total number of kilometers driven. - The ETA variance, which is the difference between estimated times of arrivals compared to the actual time of arrival. - Fuel savings through platooning as a total number in liters. In the bottom of the view is a line chart visualizing the individual platooning benefit for each vehicle in the system. Figure 12 - Statistics section showing platooning benefits and transport assignment status 17 / 20

18 6. On-board view Drivers also need to have an overview of the current transport assignment and want to observe the parameters of an assignment during execution. For this, we implemented a specific view for truck drivers which is based on the information shown in the details section of the Fleet State. Basically, the same information is shown but in a way that is optimized for drivers and the small screen that is provided in the COMPANION trucks located in the middle of the cockpit. The screen only has a resolution of 800 x 400 pixels which required us to optimize the view to fit on the screen. In Figure 13 the assignment data is visualized for the driver. On the bottom right side of the screen, there is a link which leads to the map overview. If touched, the map appears in full screen as shown in Figure 14 Figure 13 - Truck view with details on the current transport assignment Figure 14 - Truck view with a map overview of the current route 18 / 20

19 7. Technical details The development of the off-board HMI includes a series of modern libraries which are listed in Table 2- List of all used third-party libraries. The application was designed using the Model-View-Controller (MVC) pattern based on.net The website is designed in a RESTful way which means that the server-client system is stateless, and URL's are well defined (controller/action/id). The off-board HMI itself does not hold any data itself. It is dependent on the other COMPANION services, especially the Fleet Manager. The APIs are well defined and are documented in a table. Name Description Usage Bootstrap CSS library All pages jquery Asynchronous calls with JS Asynchronous update of information in Fleet State Google Maps Map services Location translation Temporary route calculation Address search Map interaction Leaflet Map service Map provider Moment.js Date and Time conversion Date Time conversion and localization Mapbox Map and UI service UI theme for OpenStreetMap Chart.js Chart with JS Chart generation and visualization Datetime Picker Date and Time picker DateTime picker Leaflet Markercluster Cluster algorithm and UI Cluster generation in Fleet State OpenStreetMap Map service Map service Marker setting Marker manipulation Table 2- List of all used third-party libraries Table 3 - List of used APIs and their descriptionincludes all used APIs from other services of the COMPANION back end system. 19 / 20

20 D2.1 Potential scenarios for new platooning concepts COMPANYON Confidential API Description api/hmi/getvehicleetakpi KPI that indicates the variance of the ETA depending on total route length api/hmi/getplatooningratiokpi KPI representing the percentage of the total trip length of all platoons spent platooning api/hmi/gettotalfuelsavingbyplatooninginliterskpi KPI representing the total fuel savings in liters for all transports in the system api/hmi/findassignments List of all transport assignments in the system api/hmi/getassignment?assignmentid=" + id Returns a specific transport assignments api/hmi/addassignment Adds a transport assignment to the system api/hmi/findvehicles Returns all vehicles in the database api/hmi/finddrivers Returns all drivers in the database api/hmi/deleteassignment?assignmentid=" + id Removes a specific transport assignment api/hmi/confirmassignment?assignmentid=" + id Sets the status of a transport assignmen to Confirmed maps/api/geocode/json?latlng=" + loc + "&key= Returns the location of a Latitude/Longitude value in a human readable format api/hmi/getfleetstate Returns a list of all vehicles registered in the system, including the assigned transport assignments and plans Table 3 - List of used APIs and their description 20 / 20