Shuttle buses run between

1. Destinations

2. Addresses

The price of the fare depends on the area travelling from to the destination

Broadly there are two types of shuttle runs

1. Ad-Hoc - built as bookings are received - common with:

   1. Areas with sporadic bookings

   2. Private addresses

2. Route - scheduled runs

   1. Some stops are made even if no booking exists

   2. Strict schedule adherence

   3. Bookings can auto-attach easily

There are a number of key items

1. States of Operation - a shuttle run will normally only travel in a single state

2. Destinations Serviced

   1. Hubs are a grouping of destinations

3. Areas serviced for the destinations

   1. ie Areas that do have a travel time to the destination chosen

4. Services offered

   1. Shuttle or Private Vehicle

5. Online customer booking portal including CC Payment

6. Planning Ad-Hoc Bus Runs from bookings

7. Driver Portal marking onboard / missed

8. Delegations to others (A need to Pay others)

9. Delegations from others (A need to Collect payment from others)

Customer online bookings

1. Customers are individuals making bookings using an online website after authentication

2. The URL that customers access may have a variable used to link to a referring organisation and show the referring organisations logo

3. The booking screen may be a single page - or setup as a stepped wizard

4. The customer may make a return booking at the same time

5. The payment is online and the booking if not paid is not retained by the system

An example booking screen

The customer will then receive a booking confirmation email with the booking information and also an attached invoice PDF.

• Email Template fo the booking confirmation

  • Usage context = Booking

  • System Usage = Order/Booking Payment Receipt

  • Recipients Role = Customer

The booking will then be ready for adding to a Bus Run

Planning Ad-Hoc Bus Runs

Ad-Hoc runs do not follow a schedule and bookings are commonly manually planned. A view of the day and bookings shows

1. Planned Bus runs (a combination of a driver and a vehicle with a from and to time on a date)

2. Bus Run Legs

   1. Ad-Hoc runs = a group of bookings in a direction to or from a destination

      1. Eg a group of bookings to the airport will be a leg

      2. At the end of the leg the driver will indicate starting the next leg

      3. The following bookings from the airport will be the next leg

   2. Route runs = a route from start to finish

      1. Eg a route may start at a destination (eg the airport) full of people - expecting to later end at a destination (eg the airport) full of people.

      2. Travel around a series of stops

      3. Drop off and pickup during the route

3. Allocated bookings (bookings already assigned to a Run Leg)

4. UnAllocated bookings (bookings that need to be assigned to a run

   1. Bookings can be assigned or moved runs anytime

The Drivers Day

The driver uses the drivers portal to:

1. View their runs today and in the future

2. Confirm they have done a vehicle check

3. Start their run

4. Be shown the next address to go to

5. Mark passengers on-board / missed / or end of leg

6. Back to 4 until day is finished

Here is a business flow of a shuttle booking

Here is pricing logic used by the shuttle system