Hire firms of any size can use this application. Other related applications cover the Booking, Return and Billing processes.

Transcription

1 Story Segmentation At any given airport there are many car hire firms to cater for the customer who has onward travel needs. This Hire Car Handover application is designed to support the process that starts when a customer, who has pre-booked, arrives at the reception desk and finishes when they leave in the car. Hire firms of any size can use this application. Other related applications cover the Booking, Return and Billing processes. Targeting The Hire Car Handover application is targeted at the car hire firm representative who needs to have all the relevant information available in order to give a smooth and efficient service to the customer. The handover process covers the following steps: Validate customer identity using driver s license, passport or ID card. Confirm the vehicle and offer upgrade if authorized. Go over any optional extras. Confirm the insurance details and level of cover. Confirm the credit card details to be used for payment. Locate the keys and show the customer to the correct car in the car park. Inspect the car with the customer and inform them of key features: seat and mirror adjustment, location and operation of fuel filler cap, opening the hood and trunk, rescue service details. Get the rental agreement signed and leave a copy with the customer. Positioning The Hire Car Handover application adheres to the Fiori design principles. It makes use of the data previously entered in the Booking application. The Hire Car Handover application is primarily designed to work on a tablet so that it can be taken from the reception desk to the car as needed during the handover process. Being a responsive app it also works on desktop and mobile. On launching the application, the master screen will be defaulted to a list of customers for the current day; it is possible to search within this list by name. On selecting the customer the detail screen gives the required information through a sequence of tabs. Persona

2 Matthew Get the job done well. 23 Years old. Single. 2 years experience in this role. Service Give a smooth and efficient customer service. Daily jobs: Booking hire cars for customers. Handover of hire cars (supported by this application). Return of hire cars. All relevant information to hand. Fast, simple and effective applications. s and managers. Checking the customer s identity. Finding the car keys. Finding where the car is parked. Knowing the key features of many different types of car.

3 User Experience Journey Current User Experience Journey Dura5on of the Journey: 15 to 30 min Mindset What is on the Persona s mind while taking the ac5ons of their journey? How do they feel each step of the journey? arrives Need to confirm their iden7ty They want an upgrade Can I find the correct keys and the car Need to remember the features for this car looks pleased with the car Job well done Ac5ons What ac5ons and ac5vi5es does the Persona take while going thru the journey to achieve their goal? Ask for customers name Get customer paperwork and confirm iden7ty and payment details Check with management Check key locker Find car Find the car details and inspec7on sheet Review with customer Get signed rental agreement Wave goodbye Touch points What touch points does the Persona have? (Tools, channels, devices, conversa5ons, and so on.) Filing cabinet Manager Key locker Car Park Paperwork Car Rental Agreement

4 Mock-up (from Splash) This mock-up shows the screens as they would appear on a tablet. The first screen after the launch pad is the list of customers for the current day. On selecting the customer the first tab of the details screen shows the customer identification information while the next tab shows the vehicle details, including any pre-approved upgrade. Note that the application title bar will be provided from the Launchpad and is not shown here. As the screens do not render well at this size in this pdf document here is a link to the prototype where the screens can be viewed on-line: - / _S0

5 Tab 3 shows the optional extras, this tab was added following the feedback from the design challenges. Thanks to those who suggested it. Tab 4 shows the insurance details Tab 5 shows the payment details. Note the link to the Booking application is available in the footer. This is to enable changes and corrections to be made.

6 Tab 6 shows the location of the keys and the car. The final tab screen covers the inspection details and the key features of the vehicle. There is also a reminder to get the signed rental agreement and to wish the customer a safe onward journey. Study Link to study:

7 SAP Web IDE App Prototype This is the development in SAP Web IDE. This app has been build using a Master screen and a Detail Screen (with many tabs). The formatter has been used to show the dates without the time stamp part. Note. For this prototype, a special pair of date formats have been used so that the collection date and return date are calculated starting from the current date. This is to stop the mock data looking out-of-date as time passes.

8 Here are the first few screens from the SAP Web IDE, again as they would appear on a tablet. You can see the customer list, customer identification and vehicle details. There are some small differences with colours and alignment of fields but other than that these screens are very close to the mock up screens created in Splash. As there is a You Tube video to go with this submission, this document is limited to 8 pages so there is no room to show screen shots of the rest. Please view the You Tube video to see all of the screens and some (hopefully amusing) mock data. You Tube Link to You Tube video: