REQ 312018 Bag It Up EPOD Requirements

From Calidus HUB
Revision as of 17:35, 16 September 2013 by Anw (talk | contribs) (v0.1 - Initial Creation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)





Aptean Logo.png







Bag It Up

Bag It Up ePOD Requirements

CALIDUS ePOD

16th September 2013 - 0.1
Reference: REQ 312018











































Introduction

This document is the Bag It Up ePOD Requirements document.

Objective

The primary purpose of this document is to document the requirements gathered from Bag It Up during the sales process, and to present an overview of the process that will be followed in and the work required to the CALIDUS ePOD system.

This document has been written in a manner such that it can be approved by non-technical representatives of Bag It Up whilst also being of sufficient detail to allow the Functional or Technical Specification phase for this area to begin.

Scope and Limitations

This document is based on the documentation provided by the OBS Logistics Sales team.

  • The changes will be made in the latest version of the CALIDUS ePOD system.
  • The changes have been specified with the Android PDA client in mind.

Client Requirements

Overview

Website: http://biugroup.co.uk/

Bag It Up recycle clothes from banks left at Supermarkets.

They require an ePOD solution to record the bags collected from the bins and the weights etc.

They will be using an existing back office solution to send jobs into ePOD and receive job information back.

There are approximately 15 vehicles, of which some (around 2) are Loader Cranes.


Log in:

Username as standard

Password will be 4 digit Numeric


Vehicle Checks

The client wants to do a vehicle check at the start of a load and at the finish of a load. Some of the information on the load will have to come from load metrics.

There are two examples of a daily vehicle check configured at vehicle level. Please attached form (Trip Sheet) and Loader crane.

Signatures will be required at the end of a vehicle check. Signatures are a VOSA requirement. Anything marked 'Office' on the form will be on the report but not be populated by ePOD.

Bank Defects will come from a variety of container cancellations and clausing through the standard process. Obviously, these forms will only be available at the end of a load.


Load and Job Processes

There are four main Job types that apply to each collection, delivery and require different pieces of data to be collected. The BIU system will indicate which job group should be applied to each job.


Job Type 1 – Standard Planned Collection of Recycled clothing from Supermarket banks

  • Choose collection job
  • Review job as normal and confirm arrival. Co-Pilot has not been purchased yet but is on the table.
  • Containers will represent banks. Client will click on or scan each container to confirm how many bags have been collected. If container is so damaged that no bags will be collected,the container can be cancelled using the existing cancellation process. If the bank is damaged but bags can still be collected then the container should be claused. A claused container will still need a picture.
  • Default qty for product in container is 0. User must choose change qty to indicate how many bags have been collected. No reason code should be entered at this stage.
  • No signature is required
  • At the end of a load that contains these collections, the user must enter weighbridge ticket no (up to five numeric digits) and weight (up to five numeric digits)
  • No paperwork created for these deliveries. But all completed information must be exported to BIU systems

Example load – 20 collections and 1 delivery to drop off bags at weighbridge/recycling point


Job Type 2 – Planned Collection then enter weighbridge ticket information from on-board weigh system

  • As above, job type 1, but at the end of collection before signature, the user must enter weighbridge ticket no and weight.
  • No signatures are required
  • No paperwork created for these deliveries.

Example load – 20 Collections or a mixed load with Job type 1


Job Type 3 – Ad – Hoc collection – Bank collection

  • As above but no containers or products. User must answer the following:
    • No of banks (up to 3 digit numeric)
    • Weighbridge Ticket No
    • Weight
    • Driver and customer signature
    • Creation of collection note (Attached) for auto email to customer


Job Type 4 - Ad – Hoc collection – Bag only collection

  • As job type 3. User must answer the following:
    • Material – Free text entry
    • No of bags
    • Weighbridge Ticket No
    • Weight
    • Driver and customer signature
    • Creation of collection note (Attached) for auto email to customer

Data Import

Loads and Jobs received from existing back-end system, including any standing data.

PDA Login

When an engineer logs on to a device (using their provided user name, password and vehicle), the assigned work-list will be downloaded onto the device, showing all the jobs in sequence on a Job List.

Login - username and numeric password, Vehicle


Vehicle Checks

  • Vehicle Checks Sample

    Vehicle Checks Sample


Vehicle Checks (pre) - collecting all Daily driver checks (required) and Loader Checks (optional). Vehicle checks must be completed.

Obtain Workload

When an engineer logs on to a device (using their provided user name, password and vehicle), the assigned work-list will be downloaded onto the device, showing all the jobs in sequence on a Job List.

Download Load

Load Metrics (Pre) - ODO reading only

  • Load Metrics

    Load Metrics


Job List

Selecting a job from the Job List will show the user the job report and customer contact details, allowing the user to contact the customer (through text or phone), or navigate to the customer's address.

Job Details

Job Start

Job Arrive

The engineer can then choose to start the job, and when they arrive at the site, can begin entering the details.

Note Note: All process up to and including the engineer starting and arriving at the job are generic and described in detail in the user guides, as referenced in the appendices.

Collection Process

  • Job Details Tab

    Job Details Tab

  • Products Tab

    Products Tab

  • Pop-up Actions

    Pop-up Actions


For each Collections - configured by Job Group (Type)

  • Type 1
  • Type 2
  • Type 3
  • Type 4

Job Completion

  • On job completion, Driver and Customer signatures (for Type 3 and 4 only)
  • Job Metrics - ODO, Weighbridge Number, Weight, Fuel Drawn
  • Signature

    Signature

  • New: Job Metrics (similar to Load Metrics)

    New: Job Metrics (similar to Load Metrics)



Delivery Process

Final delivery (optional)

Post-Load

  • Load Metrics - Post

    Load Metrics - Post


Load Metrics (Post) - ODO, Weighbridge Number, Weight

Vehicle Checks (post) - same details as entered in Pre-checks

Possible change: Driver's Declaration and Signature


POC Format

On job completion, POC format (for Type 3 and 4 only)

See #Appendix A: Client Documents for the layout of the form.

Warning Warning: Map elements here

Data Export

Once Vehicle Checks are complete, export of vehicle checks including: Driver; Vehicle; checks complete.

Once Jobs are complete, export of jobs to back-end system including: Job Metrics; signature. Export of POC to customer's email.

Once Load complete, export of load including: Load Metrics; Driver's Declaration and Signature.

Appendix A: Client Documents

Loader Crane

REQ 312018 Loader.jpg

Trip Sheet

REQ 312018 Trip.jpg

POC - Job Types 3 and 4

REQ 312018 POC.jpg

Appendix B: Table of SCRs

SCR#SystemAreaDescriptionEstimate (Days)Notes
1 ePOD PDA/Admin Customer Style (including logo, specific labels and numeric-only password).  1.75 
2 ePOD PDA/Server Job Details UDF fields against Job Group/Collection (for job types 3/4), plus Done button.  3.50 
3 ePOD PDA Vehicle Checks at start and end of load.  1.40 
4 ePOD PDA/Server Job Metrics with Weight/Weighbridge entry (UDF).  3.50 
5 ePOD PDA/Server Add Weight/Weighbridge against Load Metrics at end only (UDF).  3.50 
6 ePOD All Clausing (for Bank Defect) from Product screen, not signature screen, with images.  4.20 
7 ePOD PDA Product Quantity Entry if required quantity is 0.  1.40 
8 ePOD Export Vehicle Checks Auto-Export.  2.10 
9 ePOD Admin POC Report format.  1.40 
10 ePOD PDA Customer Signature not required.  2.80  2
11 ePOD Admin Remove Container/Product tabs if there aren't any.  2.10  2

Notes:

  1. All ballpark costs in this document are provided as-is, are legally non-binding and subject to raising a formal change request with OBS Logistics.
  2. These are product modifications

Note Note: During the analysis process the following changes were discussed but marked as not-required:

SCR#SystemAreaDescriptionEstimate (Days)Notes
12 ePOD All Driver Declaration - Signature against Load when complete (for Vehicle Checks) or against Vehicle Checks  0.00 
13 ePOD PDA/Server Vehicle Checks linked to Loads  4.20 
14 ePOD All Refuel ad-hoc action from Job List  7.00 
15 ePOD Admin Vehicle Checks Report  1.40 
16 ePOD Admin Trip Report from Load Admin screen  2.80 
17 ePOD Export Trip Export (including new items from Trip Report).  1.40 
18 ePOD Export Configurable POD Export - add email export  2.10 
19 ePOD All Vehicle Types  2.80 
20 ePOD All Vehicle Checks associated to Vehicle Types  7.00 
21 ePOD Import/Export Interface Import and Export changes  4.20 


Appendix C: Document References

C.1 References

Ref NoDocument Title & IDVersionDate
1UG 291094 EPOD Admin User Guide2.04/4/2012
2UG 291097 EPOD Client User Guide3.023/4/2013


C.2 Glossary

Term Definition
EPOD Electronic Proof of Delivery. The OBS EPOD system is CALIDUS ePOD.
CALIDUS eSERV The OBS mobile system to complete Service functionality in the field. This is part of the CALIDUS ePOD system.
PDA The mobile device on which the C-ePOD system will run in the field. This can be a Phone, EDA or industrial PDA, running Android.
DAL Data Access Layer. A mechanism for accessing data by the system that is removed from the application, allowing for simplified access and providing protection to the data, as only approved DAL methods can be used to modify it.
GPS Global Positioning System. A mechanism of retrieving accurate positioning information in the form of Latitude and Longitude (Lat-Long) co-ordinates from a device.
GPRS, 3G, HSDPA, Data Service All terms referring to mobile device network connectivity, and the speed at which the device connects to the internet.


C.3 Authorised By


Matt Turner
OBS Account Manager		_____________________________


Client Representative		_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=REQ_312018_Bag_It_Up_EPOD_Requirements&oldid=1224’