FS 294229 Whiteline EPOD Modifications
Whiteline Group Ltd
Whiteline ePOD Modifications
CALIDUS ePOD
23th November 2011 - 0.1
Reference: FS 294229
Contents
Functional Overview
Client Requirement
The customer requires an ePOD system.
The functionality required is:
- Deliveries of loose products
- Collections of loose products
- Automatic Import of data from host system (Cold Fusion)
- Export of data
- Admin functions (for creation of Collections)
- Facility to confirm receipt of payment
- Integrated Navigation
The customer will have 5 users of the system.
Solution Overview
The following developments will be required:
- Data Interfacing
- Import
- Export
- Customer Reference
- Payment Received
- Integrated Navigation
- New POD format
Scope
- Modifications will be made to the latest version (1.1) of the CALIDUS ePOD system.
- The software delivery is by end of January (TBC).
- The software will be hosted on one of the customer's servers - minimum requirements have been notified.
Set-up
Pre-requisites
- For emailing POC/POD documents, Email must be configured on the CALIDUS ePOD server.
Menu Structure
None
Data
None
Functional Description
Configuration
New Site/Job Group rule to control Payment Received on PDA—User:Anw, 3/10/2011 12:7:59
Database Modifications
A new field will be added to the EPOD_PRODUCTS table, called EPL_CUST_REF. This will be a 30-character field.
Data Interfacing
Data interfacing has been discussed with the Whiteline technical resource (Ian Finch of IFCon). The interfacing will be through a modified version of the standard Web Service XML structures.
All import data will be sent from the host system to the ePOD Web Service.
All export data will re requested by the host system from the ePOD Web Service. This will be requested based on a single day to be updated.
Import
The import XML will be modified to include a new tag EPL_CUST_REF within the EPOD_PRODUCT container tag, as follows:
<xsd:element name="EPL_CUST_REF" nillable="true"> <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:maxLength value="30" /> </xsd:restriction> </xsd:simpleType> </xsd:element>
When received within an EPOD_LOADS or EPOD_JOBS tag, this will be saved to the new field against the EPOD_PRODUCTS table.
Export
The export XML will be modified to include a new tag EPL_CUST_REF within the EPOD_PRODUCT container tag, as follows:
<xsd:element name="EPL_CUST_REF" nillable="true"> <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:maxLength value="30" /> </xsd:restriction> </xsd:simpleType> </xsd:element>
Requests for data through the Web Service (ePOD_DataService.asmx) will require an XML message structure to define what data is being extracted. The structures follow:
- Load by Load ID
<?xml version="1.0" encoding="utf-16"?> <xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:element name="EPOD_EXPORT_LOAD"> <xsd:complexType> <xsd:sequence> <xsd:element name="EPL_LOAD_ID" type="xsd:string" /> </xsd:sequence> <xsd:attribute name="EPL_USER_ID" type="xsd:string" /> <xsd:attribute name="EPL_USER_PASSWORD" type="xsd:string" /> <xsd:attribute name="EPL_SITE_ID" type="xsd:string" /> </xsd:complexType> </xsd:element> </xsd:schema>
Only the specified Load will be returned.
- Load by Date
<?xml version="1.0" encoding="utf-16"?> <xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:element name="EPOD_EXPORT_LOAD_DATE"> <xsd:complexType> <xsd:sequence> <xsd:element name="EPL_LOAD_END_ACTUAL_DATE" type="xsd:string" /> </xsd:sequence> <xsd:attribute name="EPL_USER_ID" type="xsd:string" /> <xsd:attribute name="EPL_USER_PASSWORD" type="xsd:string" /> <xsd:attribute name="EPL_SITE_ID" type="xsd:string" /> </xsd:complexType> </xsd:element> </xsd:schema>
Only Loads that have been completed or cancelled on that date will be returned.
- Job by Job ID
<?xml version="1.0" encoding="utf-16"?> <xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:element name="EPOD_EXPORT_JOB"> <xsd:complexType> <xsd:sequence> <xsd:element name="EPL_JOB_ID" type="xsd:string" /> </xsd:sequence> <xsd:attribute name="EPL_USER_ID" type="xsd:string" /> <xsd:attribute name="EPL_USER_PASSWORD" type="xsd:string" /> <xsd:attribute name="EPL_SITE_ID" type="xsd:string" /> </xsd:complexType> </xsd:element> </xsd:schema>
Only the specified job will be returned.
- Job by Date
<?xml version="1.0" encoding="utf-16"?> <xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:element name="EPOD_EXPORT_JOB"> <xsd:complexType> <xsd:sequence> <xsd:element name="EPL_END_ACTUAL_DATE" type="xsd:string" /> </xsd:sequence> <xsd:attribute name="EPL_USER_ID" type="xsd:string" /> <xsd:attribute name="EPL_USER_PASSWORD" type="xsd:string" /> <xsd:attribute name="EPL_SITE_ID" type="xsd:string" /> </xsd:complexType> </xsd:element> </xsd:schema>
Only Jobs that have been completed or cancelled on that date will be returned.
{Note} It is expected that this implementation will use the Job By Date export.
Customer Reference
Payment Received
Integrated Navigation
Bespoke POD Document
Appendix A: POD Document Formats
Appendix B: Quote & Document References
![]() | Unknown costs for client/year (WHI/2011) |
Cost Details | ||||
Activity | Estimate No. of Days |
No. of Days | Rate per Day (£) | Cost (£ Exc. VAT) |
Requirements | 0.00 | 0.00 | 0 | £0.00 |
Change Request Evaluation | 0.00 | 0.00 | 0 | £0.00 |
Functional Specification | 2.00 | 2.00 | 0 | £0.00 |
Technical Specification | 0.00 | 0.00 | 0 | £0.00 |
Development | 6.50 | 6.50 | 0 | £0.00 |
Testing and Release | 2.00 | 2.00 | 0 | £0.00 |
Implementation | 0.00 | 0.00 | 0 | £0.00 |
Project Management | First argument to "number_format" must be a number. | First argument to "number_format" must be a number. | 0 | £First argument to "number_format" must be a number. |
TOTAL | First argument to "number_format" must be a number. | First argument to "number_format" must be a number. | £First argument to "number_format" must be a number. |
Estimate excludes training, release to live and go live support. |
B.1 References
Ref No | Document Title & ID | Version | Date |
1 |
B.2 Glossary
Term or Acronym | Meaning |
---|---|
Ad Hoc | A task instigated on the device (spec. Ad Hoc Pallet Move), rather than a task instigated from the WMS and Stock Control. |
Advice Note Number | An external reference linked to a Goods Receipt. |
Aisle | A component of a location; usually a space through rows of racking or storage locations; a collection of locations; |
Anchor Point | A starting location for a search for a suitable storage location; auto-putaway location suggestion start point. |
Area | A collection of aisles; an area in the warehouse for a particular purpose. |
Batch | A production batch of a product; a quantity of product that is considered to have the same characteristics; |
Bay (Warehouse) | A physical loading or unloading point for the warehouse. |
Bay | A component of a location; usually a space between uprights in racking, comprising several levels (horizontal beams). |
Block Stack | A stable stack of pallets. |
Bulk | Bulk storage; Usually full-pallet storage areas, racked or stacked. |
Cancellation | The facility to cancel a task due to some problem, identified by the user when performing the task. |
Check Digit | A short code, usually randomly generated and stored against a location, used to help identify that a user is at the right location before they proceed with a warehouse task. |
CSV | Character-separated values; a text file with multiple rows and values, usually separated with commas. |
C-WCS | CALIDUS WCS, the name of the OBS Logistics Warehouse Control system |
C-WMS | CALIDUS WMS, the name of the OBS Logistics Warehouse Management system |
Dead Leg | A movement of a truck without a pallet; wasted resource. |
Despatch | The final physical stage of an order; handover of goods to the haulier. |
Drive-In | A drive-in location, typically multi-level, multi-deep location. |
Dual Cycling | Processes utilizing P&D locations for interleaving tasks in and out of specific areas, reducing dead leg movements. |
Exchange | Specifically Pick Exchange or Task Exchange. The process of allowing a user to select a different pallet in a multi-pallet location and exchanging the expected pallet for this one. If the pallet is planned for another task, task exchange will complete this task instead of the expected one first. If the pallet is not planned, pallet exchange will swap the pallet (if suitable). |
GR; GRN | Goods Receipt; Goods Receipt Number or Note |
High Bay | Typically tall (greater than 5 level) racking, usually full pallet storage, usually Narrow Aisle. |
JIT | Just In Time; processes designed to trigger at the last instant. |
KPI | Key Performance Indicator. |
Level | A component of a location; usually the vertical compartments of an area, delineated by horizontal beams. |
Loading | The act of loading pallets onto a vehicle. |
Location | A uniquely identified space in the warehouse for storage of product. There are many types, most commonly Floor locations (for example, Marshalling, Inbound), Racking or Bulk Storage Locations and Pick faces. |
Manifest | The contents of a vehicle or container. |
Marshalling | The act of bringing pallets for an order or load together; an area to do so. |
Multi-deep | A location with 2 or more pallets stored sequentially i.e. only one can be accessed at a time. |
NA | Narrow Aisle; usually any area in the warehouse that is restricted access due to space limitations, Narrow Aisles have associate P&D locations. |
P&D | Pick-up and Drop-off locations; locations used to control the handover of pallets between distinct areas, for example between chambers and the wider area of the warehouse. |
PI; Perpetual Inventory | The act of continuously checking locations in a warehouse, identifying and correcting product quantity issues. Usually used in Bulk environments rather than Pick Faces. In pick faces, this process is called is called Residual Stock Balance and usually takes place after picking from a pick face. |
Pick Face | A location designed for picking part of a pallet of stock. Usually a low- or ground-level location. |
Pick List (order) | The instructions to pick pallets or cases from locations; the paper report associated to this; the stage of preparing these instructions; the sending of these instructions to WCS. |
PO | Purchase Order. |
Pre-advice; Goods Receipt Pre-advice | An advanced notification of what is being received. Part of a manifest. Pre-advices can be stock and quantity, or individual pallet level. |
Putaway | The physical move of a pallet to a storage location as a result of receiving it into the warehouse. |
RAG | Acronym for Red/Amber/Green, a traffic light colouration system depicting (in sequence) Errors, Warnings or Informational messages. Usually used in operational monitoring to effectively display when certain processes are not working as expected. |
RDT | Radio Data Terminal. |
Replen; Replenishment | The act of moving product (usually a pallet) from bulk storage to a pick face. |
Reposition | The facility to change the location of a movement or putaway when at the final destination, sue to some issue discovered when performing the task. |
RF | Radio Frequency; An RF device is an RDT, typically used by CALIDUS WCS for executing warehouse tasks. |
SCR; CR | Software Change Request. |
Short Pick | The process of not fulfilling an order due to failure to identify sufficient product when picking. May also be used as a term to indicate Short Allocation. |
SO | Sales Order. |
Truck Types | Plants, Mechanical Handling Equipment. For example, Reach trucks, Counter-balance trucks, pallet riders, etc. |
UOM | Unit of Measure. |
WA | Wide Area; usually any area in the warehouse that is not restricted access due to space limitations, for example, floor areas, not Narrow Aisle. |
WCS | Warehouse Control System |
WMS | Warehouse Management System |
B.3 Authorised By
Steve McCartney | OBS Representative | _____________________________ |
Matt Turner | OBS Representative | _____________________________ |