Anw: v1.1 - Updated to latest functionality

2013-11-07T09:38:10Z

v1.1 - Updated to latest functionality

Show changes

Anw: v1.0 - Added System Overview section, updated the references and issued.

2012-04-19T10:44:41Z

v1.0 - Added System Overview section, updated the references and issued.

Show changes

Anw at 16:57, 9 February 2012

2012-02-09T16:57:17Z

← Older revision		Revision as of 18:57, 9 February 2012
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' ePOD}}		{{#vardefine:System\|''CALIDUS'' ePOD}}
	{{#vardefine:Doc_Title\|ePOD Requirements Guide}}		{{#vardefine:Doc_Title\|ePOD Requirements Guide}}
	{{#vardefine:Version\|0.2}}		{{#vardefine:Version\|0.1}}
	{{#vardefine:Date\|9th February 2012}}		{{#vardefine:Date\|9th February 2012}}
	{{#vardefine:Reference\|292887}}		{{#vardefine:Reference\|292887}}

Anw: v0.1 - Initial draft version

2012-02-09T16:54:27Z

v0.1 - Initial draft version

New page

<div class="noprint">
{{#vardefine:Client|PROD}}
{{#vardefine:ClientName|OBS Logistics Ltd}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|ePOD Requirements Guide}}
{{#vardefine:Version|0.2}}
{{#vardefine:Date|9th February 2012}}
{{#vardefine:Reference|292887}}
{{#vardefine:Year|2012}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=REQ {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}}


<div class="noprint">
=Introduction=
This document is intended to drive the collection of information required to implement an new ''CALIDUS'' EPOD system.

Each section is designed as a reminder of existing functionality within the system, targeting specific areas for more information.

Ample space has been left for comments within the printed document.

=Overview=
What is the total number of users?

What is the total number of Loads per day?

What is the total number of Jobs (Separate Collection, Delivery and Service) per Load?

What is the total number of Containers per Job?

What is the total number of Products per Container?

'''Add any other pertinent information here.'''

=General=
The system allows for multiple Sites to be served completely separately within the system. You cannot plan Jobs for 2 different sites onto the same Load.

Jobs can be Grouped together - this allows the system to apply different settings to Jobs being processed in Group 1 as opposed to jobs in group 2. For example, group 1 may require a different Completion document (i.e. POD) format to group 2.

How many sites will there be?

How many Job Groups will there be?

==Customers==
Will the jobs require defined Customer Codes (i.e. re-used)?

Will the jobs require only Free Entry Addresses (not reused)?

Will the system need to support both (i.e. a customer address and a different delivery address)?

==Products==
Are Product Weights required to be held?
*Per Unit?
*Total?

Are product Prices required?
*Per Unit?
*Total?

Is there a pre-defined product list?

Are product quantities to be stored and monitored?
*Vehicle Product Quantities?
*Site Product Quantities?

What are the number and size of the descriptive product fields?
* Description 1
* Long Description
* UOM


=Loads=
A Load consists of a collection of jobs assigned to a driver to complete.

Is there a need to have several Loads assigned to one driver? The system allows this - each load is sent to the user as the previous load is complete.

There are 3 types of Jobs. Which are required?
*Collection
*Delivery
*Service

When starting a Load on a vehicle, the system will check and display a number of vehicle checks required before the user can begin.

Are vehicle checks required?

Information is displayed about each job when it is started:
*Job Address
*Contact information
*Job Instructions
Is any other information required?

The user can make a call the customer.

The user can Navigate to the customer's address.

'''Add any other pertinent information here.'''

==Collections==
There are several types of collection. Which are in use?
*Containers only (i.e. identifying Pallets only)
*Containers and Products (i.e. identifying containers, then identifying the product within, and confirming the quantity)
*Products Only
*Ad Hoc collection of Products

What details must be visible against the Container? The system currently displays the ID and Description. A long press can be used to view any container weight.

What details must be visible against the Product? The system currently displays the Product, Description and Quantity. A long press can be used to view references and product type.

'''Add any other pertinent information here.'''

==Deliveries==
There are several types of collection. Which are in use?
*Containers
*Containers and Products
*Products Only

What details must be visible against the Container? The system currently displays the ID and Description. A long press can be used to view any container weight.

What details must be visible against the Product? The system currently displays the Product, Description and Quantity. A long press can be used to view references and product type.

'''Add any other pertinent information here.'''

==Services==
What steps are required as part of the Service?
*Pre-work Checks
*Vehicle Info
*Installed Products
*Returned Products
*MC References
*Diagnosis
*Post-work Checks

'''Add any other pertinent information here.'''

==Confirmation of a Job==
When a job is completed:
*Is the Driver Signature required?
*Is the Customer Signature required?
*Is a different contact to that advised required?
*Is Document Image Capture required?
*Is COD required? (Captures only whether the cash was collected, not the amount)
*Is a receipt required? (New development)

'''Add any other pertinent information here.'''

==Exceptions==
What exceptions are captured?
*Job Cancellation
*Container not delivered
*Product Quantity Change

Are specific reason codes used?

Are images required?

'''Add any other pertinent information here.'''

=Data Transfer=
==Import==
How will jobs be interfaced?
*OBS Web Service
*Other Web Service
*File Upload (CSV, XLS, etc)

What data needs importing?
*Customers
*Products
*Jobs
*Loads
*Other

==Export==
How will jobs be interfaced back to you?
*OBS Web Service (ERP Pull)
*Web Service (Push)
*Other Web Service (Bespoke Format)
*Email

What data needs exporting?
*Jobs
*Loads
*Completion Documents

'''Add any other pertinent information here.'''

=Completion Documents=
There are several types of Completion documents that can be crea5ted by the system. Which are required?
*Delivery (POD)
*Collection (POC)
*Service (Work Report)

Are there different formats per Job Group?

Do the documents go over a single page?

Are any of the subsequent pages in a different format?

Please provide examples for each format, annotated with requirements. Any required images should be provided.

What format should they be produced in?
*HTML
*PDF

Should these documents be automatically emailed to the customers?

'''This space should be used to list all new fields required for the Completion documents.'''


=Admin Features=
Is the Admin system going to be used?

What for?
*Entering Jobs
*Entering Containers
*Entering Products
*Changing quantities
*Entering Customers
*Assigning Jobs to Loads
*Assigning Loads to Users
*Maintaining Product Quantities
*Maintaining Users
*Viewing Loads
*Viewing Jobs
*Viewing Containers
*Viewing Products
*Viewing/Printing/Emailing Completion Documents

If new fields are required on Completion documents, must they be viewable/editable?

'''Indicate these below.'''


=Technical Details=
Is the system hosted by the Client or by OBSL?

Windows Server:
*Memory
*HD
*O/S

In order to effectively support the system, OBSL must connectivity to the system.
*Remote connectivity to the server [ RDC ] [ VPN ] [ VNC ] [ Other ] ____________
*File Transfer details

The server requires Microsoft IIS to be installed for the application to function.

For emails, an email server must be set up and the details provided.

For importing from Microsoft Excel, this program must be installed on the server.

==Hosting==
The data passed to and from the PDA units is open and unencrypted. This contains details of the delivery address and product information. If this is to be encrypted, the whole message must be encrypted through Secure Socket Layering.

[ SSL ] or [ Open ]

Minimum Database Requirements
*SQL Server 2005/2008 Compact Edition

PDA unit requirements
*Windows Mobile 6+
*Screen size required?


{{Doc_Appendix
|Appendix=A
|Estimate=N
|Glossary=EPOD
|Ref1=UG 291094 EPOD Admin User Guide
|RefV1=1.0
|RefDate1=6/10/2011
|Ref2=UG 291097 EPOD Client User Guide
|RefV2=1.0
|RefDate2=6/10/2011
|REQ=0
|EST=0
|FS=0
|TS=0
|DEV=0
|ST=0
|IMP=0
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=N
|Rev1=Tony Walker
|Rev1Title=OBS Consultant
}}</div>

REQ 292887 ePOD Requirements - Revision history

Anw: v1.1 - Updated to latest functionality

Anw: v1.0 - Added System Overview section, updated the references and issued.

Anw at 16:57, 9 February 2012

Anw: v0.1 - Initial draft version