https://di.no/doc

DI Plan & Go - Setup of Company

Owned by Svein Are GrΓΈnsund (Deactivated)
Last updated: Jul 22, 2022
3 min read

Definitions

  • Plan - A collection of orders that will be distributed as a batch (i.e. a shift for a given date)

  • Route - A collection of stops to be assigned to a driver

  • Stop - A location on a route where there are customers

  • Customer - An order/customer (customer name/phone presented to the driver) that has one/many deliveries

  • Delivery - An item (name presented to the driver) to be delivered to a customer (or picked up)

  • Driver - The courier that is performing the distribution - using the mobile app. Drivers are created within a company.

  • User - Personell that plans the distribution and assigns routes to drivers. Users might have access to multiple Companies. Two main-types os users:

    • Users connected to one/multiple distribution-companies

    • Users connected to one/multiple CustomerSystems. A supplier that has outsourced distribution to multiple distribution-companies, but still has insight and customer-service

Core Configuration

  • Company Required
    The local distribution-company that has drivers to dispatch.
    Input needed: CompanyName + Country (NO, SE)

    • DeliveryTime Rules Optional
      How long time does it take to service a customer in the given zip-interval? Can be rules for a Company or combination Company + CustomerSystem. Default is 3 minutes per customer.

  • CustomerSystem Required
    Each product-type can have a configuration. Normally a company has one CustomerSystem defined, but it can have multiple. And a CustomerSystem CAN be shared with multiple Companies.
    Input needed: CustomerSystemName + Country (NO, SE)
    Rules a CustomerSystem can have:

    • Acknowledgement Rules
      Defining what actions/policies you want for the drivers.

      • Quick-Actions Required
        This is the button(s) where the driver indicates a successful delivery/pickup for a customer.

        • Available types (choose at least one): CUSTOMER, DOOR, DELIVERED, PICKED_UP

        • Proof of Delivery (picture)

          • Choose (for each type) if driver has to take a picture when acknowledging. Will be visible in the dashboard

      • Deviations Optional

        • Available types: CANT_FIND(customer), MISSING, NOT_HOME, DAMAGED, NOT_ACCEPTING, OTHER

        • Choose context (for each type): Customer or Delivery/Product

        • Choose (for each type) if you want the driver to always add a comment when registering a deviation

    • Scanning (if items has PARCEL_NUMBER and a label with barcode/QR-code) Optional

      • Choose if you want the driver to Scan items when loading the truck

      • Choose if you want the driver to Scan items before delivering to customer

    • Notification Rules Addon feature
      SMS can be triggered for certain events (with custom SMS-message). This feature needs additional setup/agreements. Available events:

      • β€œSoon there” - Driver on his/her way and is estimated to be there within X minutes.

      • β€œSuccessful delivery/pickup” - When driver selects a QuickAction (successful delivery/pickup)

Example Configuration

Suzy Shoes has activity in two cities and wants to use Plan & Go. Since operation in each city is very autonomous we create two companies, but they share the same CustomerSystem. See an example-setup below:

  • Companies:

    • β€œSuzy Shoes - Oslo” (with local drivers defined)

    • β€œSuzy Shoes - Stockholm” (with local drivers defined)

  • CustomerSystem:

    • β€œSuzy Shoes”

    • Acknowledgement Rules:

      • Quick-Actions (two buttons for the driver):

        • CUSTOMER - indicates that you delivered is personally to the customer

        • DOOR (chose POD-picture) - indicates that you could meet the customer, but left it as a safe spot, documenting the spot by taking a picture)

      • Deviations:

        • CANT_FIND, NOT_HOME and OTHER (all with required comments) for customer-context. Also OTHER for delivery-context, to be able to handle a partially successful delivery.

    • Scanning:

      • Activating scan on both loading and delivery since the boxes has a label with QR-code and you want to maximize control (right item to right customer)

    • Notification Rules:

      • SMS is important for customer-experience and you decide to go the this add-on. After setting up an SMS-agreement you decide this rule:

        • Sender-name: SuzyShoes

        • Message (when driver is 30 minutes away):
          <custom message - soon there - keep it short>

        • Message (when driver uses DOOR-action):
          <custom message - left parcel by door - keep it short>

  • Delivery Time Rules:

    • Parking is easier in Oslo and you experience that 4 minutes is right for zip-interval AAAA-BBBB, and 2 minutes for zip-interval CCCC-DDDD.

    • For Stockholm the default 3 minutes are perfect.