Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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. Hubs or Areas of operation (within states)

  3. Destinations Serviced for each hub

  4. Destinations Serviced

    1. Hubs are a grouping of destinations

  5. Areas serviced for the destinations

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

  6. Services offered

    1. Shuttle or Private Vehicle

  7. Online customer booking portal including CC Payment

  8. Planning Ad-Hoc Bus Runs from bookings

  9. Driver Portal marking onboard / missed

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

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

...

An example booking screen

The fields can be arranged in any order or as a simpler stepped wizard easily

...

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

...

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

Here is a business flow of

...

a shuttle booking

The system include full financials (GL/AP/AR etc)

Gliffy
imageAttachmentIdatt821329925
macroIdf0da9f56-7c90-4a7c-bb89-a5b2160d26dc
baseUrlhttps://saasplications.atlassian.net/wiki
nameShuttle Bus Booking Flows
diagramAttachmentIdatt821035013
containerId821428227
timestamp1644216483288

Here is pricing logic used by the shuttle system

Each customer may use a different pricing logic - below is an example

Gliffy
imageAttachmentIdatt821493762
macroId2e0a4801-25ce-456f-805f-3bfff19de760
baseUrlhttps://saasplications.atlassian.net/wiki
nameShuttle Pricing Flow
diagramAttachmentIdatt821428234
containerId821428227
timestamp1644216547353

...