CFG 328695 Buffaload C-EPOD Configuration - TEST
Buffaload
Buffaload C-EPOD Configuration - TEST
CALIDUS EPOD
30th July 2015 - 0.1
Reference: CFG 328695
Contents
Introduction
Configure the Buffaload CALIDUS ePOD system for the client's use use.
The intention of this document is to show the overview of the solution requirements for CALIDUS ePOD for the customer, and to document the configuration undertaken to achieve this.
This document refers to the configuration undertaken for the TEST system for the customer Buffaload.
Note: This will become a controlled document after implementation of the system described above. Any changes to configuration will be reflected in this document.
Solution Overview
There are several location types:
- RDC - the three Buffaload RDCs: Wigan, Ellington, Bristol.
- SUPPLIER - Collections from a supplier
- UNDEFINED - Unknown locations
- STORE - Deliveries to end customers.
The expected movements in this operation are:
- SUPPLIER - RDC - STORE - Collections from supplier into RDC, cross-docked onto delivery trips to the customer.
The following movements may also be a small part of the operation:
- SUPPLIER - STORE - Direct deliveries from a supplier to a customer
- STORE - STORE - Direct deliveries from one store to another store.
- RDC - RDC - Inter-depot transfers
The three RDCs each have a carrier associated to them, and a fourth carrier is also present, ASHWIG, that is a trusted third-party carrier. Jobs for all the carriers will be executed through CALIDUS ePOD.
All resources (drivers and vehicles) are available for all carriers in C-TMS.
All trips are planned centrally for the operation.
CALIDUS ePOD will execute all jobs sent to it under a central site BUF, that combines all the transport movements assigned to all carriers.
The following movements will be controlled through CALIDUS ePOD:
- RDC - STORE
- STORE - STORE
- SUPPLIER - STORE
RDCs will use WCS to scan unloading for the following movements:
- Any location - RDC
RDCs will use WCS to scan loading for the following movements:
- RDC - Any location
Loading and Unloading tasks for RDC locations are not required on CALIDUS ePOD.
Tasks sent to CALIDUS ePOD will be Deliveries at STORE only.
C-TMS will be configured in this way to send jobs to CALIDUS ePOD to execute.
Operational/System Process
CTMS trips are planned for the Delivery orders.
Trips set to ACCEPTED status sends trips to WCS for Loading.
Trips set to ACCEPTED status sends trips to EPOD.
Trips are loaded via WCS.
Trips are updated to EPOD during Loading with the items and orders that are actually to be delivered.
EPOD will have jobs sent to it for each delivery job - collections into RDCs are not part of this process.
The driver will log in to EPOD.
Upon logging in to EPOD, no Vehicle Defect checks will be completed - this is expected to be completed by a different application.
Upon starting a Load in EPOD, the driver will be prompted to enter odometer readings. This will set the Load to In Progress and set EN_ROUTE status against the trip in C-TMS. The odometer reading will be stored in C-TMS.
The jobs will appear on a job list on the EPOD Device, consolidated together per location i.e. there will be one job on the list per delivery location.
Clicking an item on the list will show the job details (the full address, contact information, any instructions to the driver). The jobs may not be cancelled here. All individual orders will be displayed on this screen and the driver may see the details against all the individual orders separately.
The Driver will click a Start Job button when they start this job i.e. when they depart the previous location.
The driver may then use navigation on the device to guide them to that location. The driver may SMS or phone the contact if a contact telephone number has been provided.
Once arrived at the location, the driver will click Arrive job.
The device will display a summary of total quantity of item types being delivered, per order. A list of all items being delivered on all orders will be shown on the Containers tab. A User Notes tab will also be present to enter any notes the driver likes.
The driver will not leave the cab to scan the items - this is completed by the store's staff. To complete the job on the device, the driver will select each item from the list and select Delivered from the pop-up menu.
Once all items are confirmed as delivered, the device will move to a Signature Capture process, where the driver will be asked to obtain the name and signature of the person signing for the goods.
Once complete, the Job List will be redisplayed, showing any remaining jobs on the list.
When there are no remaining jobs on the list, the driver will be prompted to return to base and enter the odometer reading again.
When this is complete, the device will search for any more work assigned to this driver or vehicle.
Scope
This is using the latest version (v3) of the CALIDUS ePOD application.
Set-up
Server Details
- Server name: SHARED-WEB-R
- OS: Windows 2012 Standard
- IP: 172.183.45.50
- RDC User: SHARED-WEB-R \<Own User>
- RDC Password: <Own Password>
- IIS: Version 8.0.9200.16384
Database
- Server name: SHARED-SQLSVR-R
- OS: Windows 2012 Standard
- IP: 172.184.45.200
- RDC User: SHARED-SQLSVR-R\<Own User>
- RDC Password: <Own Password>
- SQL server: Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
EPOD Installation
Install Files: E:\OBS_Logistics_Install_Files
- Application
- Admin: C:\Program Files (x86)\OBSLogistics.epod\EPOD_buftst.app
- Webservices: C:\Program Files (x86)\OBSLogistics.epod\EPOD_buftst.web
- EPOD Data/Logs: E:\EPOD_Data\EPOD_buftst
- SQL Server
- Data files: E:\SQLServer_Data\buftst
- Backup: None
URL
- Internal
- Admin: http://172.183.45.50:40458/
- Webservices: http://172.183.45.50:40459/
- External
- Admin: http://buffaload-test.CALIDUS-epod.com/
- Webservices: http://buffaload-webtest.CALIDUS-epod.com:40458/
Configuration
CALIDUS TMS
Carriers created:
- BUFELL
- BUFBRI
- BUFWIG
- ASHWIG
All assigned to carrier group "fleet".
Carrier group "fleet" given EPOD Site "BUF".
All drivers (RES_PERSON) set EPOD_USERNAME = ID, and sent to EPOD.
All vehicles (RES_TRACTOR) set as EPOD_ENABLED, and sent to EPOD.
All reason codes (SCH_REASON_CODE WHERE USAGE = 'ITEM_NON_CON') send to EPOD.
Job for sending tasks to EPOD are enabled and running every 5 minutes.
System Parameters Settings:
| Parameter Name | Value/Description |
|---|---|
| EPOD_ENROUTE_COLLECTIONS | Y (Set trips to En Route) |
| EPOD_JOB_GROUP_FORMAT | CI (Carrier ID) |
| EPOD_SET_ACTUAL_SIGNATORY_BLANK | N |
| EPOD_SITE_ID_FORMAT | CA (Carrier Group EPOD Site, or Carrier ID if Group Site not present) |
| EPOD_VIEW_POD_URL | (Unset - not relevant) |
| EPOD_WS_ADDRESS | http://172.163.45.50:40458/WebServices/DataService/ePOD_DataService2.asmx |
| EPOD_WS_MESSAGE_FORMAT | MODE1 |
| EPOD_WS_PASSWORD | TEST |
| EPOD_WS_USERNAME | ADM |
Location types (GEO_LOC_TYPE) configured as follows:
| LOAD | UNLOAD | |||||||
|---|---|---|---|---|---|---|---|---|
| LOC_TYPE | SEND_JOB | CONSOL_JOB | SEND_DETS | JOB_GROUP | SEND_JOB | CONSOL_JOB | SEND_DETS | JOB_GROUP |
| CROSSDOCK | Y | Y | Y | Y | Y | Y | ||
| RDC | Y | Y | Y | Y | Y | Y | ||
| BRANCH | Y | Y | Y | Y | Y | Y | ||
| SUPPLIER | N | N | N | Y | Y | Y | ||
| UNDEFINED | Y | Y | Y | Y | Y | Y | ||
| STORE | Y | Y | Y | Y | Y | Y | ||
| HOME | Y | Y | Y | Y | Y | Y | ||
Configuration against specific locations (GEO_LOCATION) removed (set to NULL)
CALIDUS EPOD
Site BUF created.
Job groups created for each carrier:
- BUFELL
- BUFBRI
- BUFWIG
- ASHWIG
All Reason Codes, Vehicles and Drivers sent across from CTMS and present.
Generic users created for:
| Username | Name | Password | Active | Type |
|---|---|---|---|---|
| ADM | OBS Administrator | TEST | Active | Administrator |
| pda | OBS PDA User | pda | Active | PDA Only |
| PDAADMIN | PDAADMIN | service | Active | For access to PDA settings on device |
| REMOTE | REMOTE | Mcug9BkLUDIeASUd5Rde | Active | Remote Access from other systems |
All Admin users provided access to all job groups, so they can see all jobs.
XF Configs created for all sites, including new site BUF
Site Settings:
| Column | Value |
|---|---|
| EPL_SITE_ID | BUF |
| EPL_DESCRIPTION | Buffaload Logistics Ellington |
| EPL_LOGO | (Assigned Logo) |
| EPL_SERVICE_POD_FORMAT | Unassigned |
| EPL_DELIVERY_POD_FORMAT | GenContnr |
| EPL_COLLECTION_POD_FORMAT | GenContnr |
| EPL_SERVICE_ACTIVITIES | N |
| EPL_SERVICE_PREWORK | N |
| EPL_SERVICE_INFO | N |
| EPL_SERVICE_PRODUCTS | N |
| EPL_SERVICE_MC_REF | N |
| EPL_SERVICE_DIAGNOSIS | N |
| EPL_SERVICE_POSTWORK | N |
| EPL_VEHICLE_CHECK_CONFIG | <VEHICLE_CHECK FREQ="1" REQUIRED="N" /> |
| EPL_LAST_CHANGED_DATE | 20150729 |
| EPL_LAST_CHANGED_TIME | 10544591 |
| EPL_AUTO_COMPLETE_EMAIL | N |
| EPL_AD_HOC_COLLECTION | N |
| EPL_DEL_DRIVER_SIGN | N |
| EPL_COL_DRIVER_SIGN | N |
| EPL_DELIVERY_PAYMENT | N |
| EPL_DOCUMENT_PHOTO | N |
| EPL_XF_CONFIG | BUF |
| EPL_CONTAINER_ONLY | N |
| EPL_PDF_DOCUMENT | Y |
| EPL_SITE_EMAIL | |
| EPL_PDA_DIS_JOB_CODE | EPL_JOB_CODE |
| EPL_LINKED_C_D | Y |
| EPL_METRICS_ENTRY | Y |
| EPL_NOTES | Y |
| EPL_FORCED_ENTRY | N |
| EPL_SYSTEM_TYPE | GENERIC |
| EPL_UPDATE_FUNCTIONS | N |
| EPL_JOB_LIST_CFG | <JOB_LIST_CONFIG><FIELD name="EPL_JOB_TYPE" label="T" width="10"/><FIELD name="EPL_CUSTOMER_NAME" label="Customer" width="70"/><FIELD name="EPL_POSTCODE" label="Postcode" width="20"/></JOB_LIST_CONFIG> |
| EPL_TTM_XREF | 1 |
| EPL_SCAN_ERROR_FLAG | Y |
| EPL_IMPORT_CREATE_SD_FLAG | Y |
| EPL_ARRIVAL_FLAG | Y |
| EPL_RESEQUENCE | N |
| EPL_CLAUSE_DELIVERY | N |
| EPL_JOB_STATUS | N |
| EPL_AUTO_GEN_LOAD | N |
| EPL_SERVICE_LEVEL_LISTS | N |
| EPL_ALTERNATE_JOB_DISPLAY | N |
| EPL_CONSOLIDATION | Y |
| EPL_VEHICLE_STOCK_FLAG | N |
| EPL_JOB_TRANSFER_IND | 0 |
| EPL_SCAN_AT_VEHICLE_IND | 0 |
| EPL_LOAD_PREFIX | |
| EPL_PDA_FULL_ADDRESS_IND | 1 |
| EPL_SYSTEM_LOADS_UNIQUE_IND | 0 |
| EPL_PROGRAM_ARGUMENT_FLAGS | |
| EPL_NEXT_JOB_FLAG | N |
| EPL_RETURNS_DEPOT_FLAG | N |
| EPL_SCANNING_FLAG | N |
| EPL_AUTOLOGIN_FLAG | Y |
| EPL_ADHOC_ANYTIME_CONFIG | |
| EPL_AUDIT_LOGIN_FLAG | N |
| EPL_VEHICLE_CHECKS_FORMAT | Unassigned |
| EPL_TRAILER_VEHICLE_FLAG | N |
| EPL_AD_HOC_DELIVERY | N |
| EPL_OWNER_OPERATOR | N |
Job Groups have been configured as follows:
| Column | Value1 | Value2 | Value3 | Value4 |
|---|---|---|---|---|
| EPL_SITE_ID | BUF | BUF | BUF | BUF |
| EPL_JOB_GROUP | ASHWIG | BUFBRI | BUFELL | BUFWIG |
| EPL_DESCRIPTION | ASHWIG | BUFBRI | BUFELL | BUFWIG |
| EPL_LOGO | ||||
| EPL_SERVICE_POD_FORMAT | ||||
| EPL_DELIVERY_POD_FORMAT | GenContnr | GenContnr | GenContnr | GenContnr |
| EPL_COLLECTION_POD_FORMAT | GenContnr | GenContnr | GenContnr | GenContnr |
| EPL_SERVICE_ACTIVITIES | N | N | N | N |
| EPL_SERVICE_PREWORK | N | N | N | N |
| EPL_SERVICE_INFO | N | N | N | N |
| EPL_SERVICE_PRODUCTS | N | N | N | N |
| EPL_SERVICE_MC_REF | N | N | N | N |
| EPL_SERVICE_DIAGNOSIS | N | N | N | N |
| EPL_SERVICE_POSTWORK | N | N | N | N |
| EPL_LAST_CHANGED_DATE | 20150729 | 20150729 | 20150729 | 20150729 |
| EPL_LAST_CHANGED_TIME | 11012462 | 11011857 | 11013268 | 11014115 |
| EPL_AUTO_COMPLETE_EMAIL | N | N | N | N |
| EPL_AD_HOC_COLLECTION | N | N | N | N |
| EPL_DEL_DRIVER_SIGN | N | N | N | N |
| EPL_COL_DRIVER_SIGN | N | N | N | N |
| EPL_DELIVERY_PAYMENT | N | N | N | N |
| EPL_DOCUMENT_PHOTO | N | N | N | N |
| EPL_XF_CONFIG | ASHWIG | BUFBRI | BUFELL | BUFWIG |
| EPL_CONTAINER_ONLY | N | N | N | N |
| EPL_METRICS_ENTRY | N | N | N | N |
| EPL_NOTES | Y | Y | Y | Y |
| EPL_TNCS | ||||
| EPL_DEL_CUST_SIGN | Y | Y | Y | Y |
| EPL_COL_CUST_SIGN | Y | Y | Y | Y |
| EPL_SIGN_CHECK_LBL | ||||
| EPL_TTM_XREF | ||||
| EPL_JOB_STATUS | N | N | N | N |
| EPL_CONSOLIDATION | N | N | N | N |
| EPL_FORCE_PROD_QTY | 0 | 0 | 0 | 0 |
| EPL_COMMENT_PRODUCTS | 0 | 0 | 0 | 0 |
| EPL_CANC_IMAGE_REQ | 0 | 0 | 0 | 0 |
| EPL_CLAUSE_DELIVERY | 0 | 0 | 0 | 0 |
| EPL_SCAN_AT_VEHICLE_IND | 0 | 0 | 0 | 0 |
| EPL_AD_HOC_DELIVERY | N | N | N | N |
| EPL_EXCLUSIVE_REASON_CODE | N | N | N | N |
| EPL_PRE_DEL_CUST_SIGN | N | N | N | N |
| EPL_PRE_COL_CUST_SIGN | N | N | N | N |
| EPL_PRE_JOB_TNC_ID | 0 | 0 | 0 | 0 |
| EPL_ALLW_DEL_INCOMP_SERVS_IND | 0 | 0 | 0 | 0 |
The system job for sending tasks to C-TMS is enabled and scheduled to run every 5 minutes.
Appendix A: Document References
A.1 References
| Ref No | Document Title & ID | Version | Date |
| 1 | UG 291094 EPOD Admin User Guide | 3.0 | 16/10/2014 |
| 2 | UG 291097 EPOD Client User Guide | 4.0 | 16/10/2014 |
A.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. |
A.3 Authorised By
Murray Middleton | OBSL Development Manager | _____________________________ |
Phil Harding | OBSL Project Manager | _____________________________ |
