Overview

Systems just a part of operations

Process
Service
System

Data

Organisation Cost

Resources / Infrastructure

Governance (KPIs) Flexibility (ST) /

Scaleability (LT)
Policies
Key Features of Delivery Module

• Separate system that communicates through the shipment API with OMS
(or any other tool)
• Main element is tracking number of package
• Ability to manage forward logistics (deliveries)
• Ability to manage return logistics (pick ups)
• Integrated solution with no need of redundant manual data entry
• Streamlined operational processes
• Real time package status view for customer service
• Integrated data set for dash boarding and reporting
• Dedicated development resources; solution is improved continuously
• Dedicated support organisation and 24/7 emergency line
Delivery module – high level delivery process

• 1) warehouse ships packages to distribution hubs

• 2) hubs receive packages
• 3) hubs allocate packages to riders and produce run sheets
• 4) rider delivers packages and collects cash from customer
• 5) customer signs proof of delivery
• 6) rider returns to the hub with packages and cash
• 7) rider and admin reconcile cash and packages (either cash or package
must return)
• 8) undelivered packages are either put aside for redelivery (start at step 3
the next day) or returned to the warehouse
• 9) total cash for delivered packages during a given day for a given hub is
deposited at a bank account
• 10) finance reconciles bank account with delivery reports per hub (not in
delivery module)
Key Features of Delivery Module
Inbound key features

• Setting up of hubs (shipment provider) in order mgt tool through shipping provider
• API with order mgt tool synchronizes every 5min and pulls packages
• List of inbound packages
• Ability to receive packages at hub by scanning, simple and multiple selection
• Ability to schedule packages from all queues (can be printed on run sheets)
• Ability to see packages history from all queues
• Ability to add notes (can be printed on run sheets)
• Ability to export queue content
At the hub key features

• At the hub
– See packages at the hub
– Create a delivery run sheet by scanning, simple or multiple selection of packages
– Assign riders and dates to run shets
– Print delivery run sheets based on defined html template
– Ability to return
• See picked up return parcels and send them back to the warehouse
• Package overview:
– See all packages
– Add notes or define delivery date
– See package history
• Ability to change shipment provider (hub)
• Assign zones to packages based on geofencing on googlemaps
Delivery Android app (in development)

• See deliveries and pickups assigned to drivers

• View deliveries and pickups on maps
• Contact customers via SMS and phone
• Confirm collected amount and payment method
• Collect signature for proof of delivery
• Assign delivery / pick up attempt failure reason
• Take picture of location
• Backend:
– Verify location of riders
– Assign packages / pickups on the fly
– Message riders
Outbound key features

• Manage delivery runs:

– See all open delivery runs
– Reconcile payment (cash and other payment types) by scanning, simple or multiple
selection
– Assign delivery attempt failures at packages level
– Enter reconciliation comments
– Close delivery runs
– (n progress) Packages level reconciliation of amount and payment method
• View all packages in transit from hub (back to warehouse) and receive them at the
warehouse or re-received them at the hub
• View delivery run history and reconciliation differences
Reports key features

• Package overview: see backlog of packages by configurable time interval

• Global overview: see key indicators on hub level at one glance
• Advanced reporting needs: access to mirror database for ad hoc / automated reporting
Administration key features

• Management:
– Set up and manage riders
– Set up zones and geofence them
– Set up time slots for package scheduling
– Set up alternative payment methods
– Set up delivery failure reasons (reason codes can be imported from OMS or ERP as well)
– Set up clients (if delivery done for multiple accounts)
• Set up roles
• Set up users and assign / manage roles
– Login is email based
– Password reset every two weeks
• Set up delivery run templates (html or pdf based on configurable html templates)
• Ability to import packages (if not done through API) for re-deliveries, ad-hoc deliveries or
other clients
Support and escalation

Level / Issue Contact Person

User creation (local contacts)
(login, access denied)

Support Level 1 Quick reference guides

(functionalities / bugs) (local contacts)

Support Level 2 Support Email: ohms@[Link]

(functionalities / bugs) Support Skype: [Link]

OMS / WMS down Portugal development team standby number, +351 924470097
BOB connection down Jose Santos, che_manel, jdossantos@[Link]

Implementation team XXXX

Templates (invoice, (local contacts)

purchase order, AWB)
 OMS / DM Governance

Ventures Central Support

Regional Regional
Regional
Operations Regional
Lead

CTO
Regional
Operations Regional
CTO Global
COO CTO
Regional
Operations Regional
CTO Operations
Operations CTO - Manage developers
- Implement and hypercare - Ensure overall
system architecture

Features
Manage

Regional Jose Joao

Regional - Funnel requirements Jose Santos
OMS PMs - Manage deployments Santos Granja
OMSRegional
PMs - Connect with BOB and
OMS PMs other systems - Business connection
- Ensure process
- Final new feature review
- Connect with BOB

New Features
Luis Carneiro
Rui Ruarte
Bug Fixing
Venture Regional

Testing
OMSVenture
POCs Normal
Support Bug Fixing
Execute

OMSVenture
POCs
OMSVenture
POCs
OMS POCs Emergency call and/or Jira (blocking)
- First level support - Second level support
- Request new features - End user materials
- Ensure ticket consistency

Weekly Satus and Bi –Weekly Feature

Deployment Calls and Arbitrage Calls

Identify Filter / Report Fix / Develop