FS 299880 EuLoS EPOD Modifications - Revision history

Milesl: /* PDA Changes */

2012-06-20T10:54:03Z

PDA Changes

← Older revision		Revision as of 12:54, 20 June 2012
Line 257:		Line 257:

	If the Load has the same reference being delivered later, both the PDA and the Server will update the Delivery associated to the Collection with the Vehicle information (i.e. the Container records) but not the Damages information (i.e. the Products).		If the Load has the same reference being delivered later, both the PDA and the Server will update the Delivery associated to the Collection with the Vehicle information (i.e. the Container records) but not the Damages information (i.e. the Products).

			== Ad Hoc Vehicle (Container) Collection ==
			As part of the collection a Ad Hoc collection at container level will be required. This will function in a similar way to existing product level ad hoc collection, with the PDA creating the records.
			As part of the vehicle system configuration a addtional item on the context menu will be added to the containers grid labelled as new.
			Clicking this will create a new container and enter the user in the vehicle damages screen, prompting to populate the Reg, desc, cmr. From here they can add any damages on this vehicle.

			Clicking confirm will create the container. This will then be processed the same as all other containers.

	=== Sequence Image messages After All Normal Messages ===		=== Sequence Image messages After All Normal Messages ===

Anw: v0.4 - Final draft

2012-06-11T14:11:48Z

v0.4 - Final draft

← Older revision		Revision as of 16:11, 11 June 2012
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' EPOD}}		{{#vardefine:System\|''CALIDUS'' EPOD}}
	{{#vardefine:Doc_Title\|EuLoS EPOD Modifications}}		{{#vardefine:Doc_Title\|EuLoS EPOD Modifications}}
	{{#vardefine:Version\|0.3}}		{{#vardefine:Version\|0.4}}
	{{#vardefine:Date\|11th June 2012}}		{{#vardefine:Date\|11th June 2012}}
	{{#vardefine:Reference\|299880}}		{{#vardefine:Reference\|299880}}
Line 99:		Line 99:

	<!-- NEW PAGE -->		<!-- NEW PAGE -->

	= Set-up =		= Set-up =
	== Pre-requisites ==		== Pre-requisites ==
Line 260:		Line 259:

	=== Sequence Image messages After All Normal Messages ===		=== Sequence Image messages After All Normal Messages ===
	The PDA Sending process will be modified to ensure that all images are sequenced for sending after any other pending messages, via a sort order on the pending message.		The PDA Sending process will be modified to ensure that all images are sequenced for sending after any other pending messages, via a sort order on the pending message. To achieve this, a Priority and auto-generating ID will be added to the index on the Pending table, sorting in Ascending sequence. All Image messages will be written with priority -1. All other messages will be written with priority 1.

	A Priority and ID will be added to the index on the Pending table, sorting in Ascending sequence.

	All Image messages will be written with priority -1. All other messages will be written with priority 1.

	When writing Images, the Image Size parameter will be checked. If the Image exceeds the Image Size parameter, the message will be broken down into multiple messages, each message payload being equal to the Image Size parameter, with the remainder of the image being sent in the final message.		When writing Images, the Image Size parameter will be checked. If the Image exceeds the Image Size parameter, the message will be broken down into multiple messages, each message payload being equal to the Image Size parameter, with the remainder of the image being sent in the final message.
Line 332:		Line 327:
	* Reference Number: EPL_CUST_REF of the EPOD_JOB record for the Collection Job.		* Reference Number: EPL_CUST_REF of the EPOD_JOB record for the Collection Job.

	=== Format "EULOS POC 2"		=== Format "EULOS POC 2" ===
	This format will print one page per container, rather than one page per job.		This format will print one page per container, rather than one page per job.

Line 475:		Line 470:
	\|Result=A new Delivery Job should be created.		\|Result=A new Delivery Job should be created.
	}}		}}


	{{TestPlan_Test		{{TestPlan_Test
	\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}		\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
	\|Action=~~{{warning}} Update Delivery from Collection~~		\|Action=Find the collection Job again, and delete a Vehicle, add a new Vehicle and change an existing one.
	\|Result=		\|Result=The Delivery associated should be updated with the new details.
	}}		}}


	{{TestPlan_CycleFooter}}		{{TestPlan_CycleFooter}}

Line 659:		Line 650:
	\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}		\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
	\|Action=Find a completed Job, either through the Load or Jobs screens.		\|Action=Find a completed Job, either through the Load or Jobs screens.
	\|Result=The ~~jobs~~ are displayed.		\|Result=The vehicles are displayed.
			}}
			{{TestPlan_Test
			\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
			\|Action=Select a vehicle and choose to display the damages.
			\|Result=The damages should be displayed in a grid.
			}}
			{{TestPlan_Test
			\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
			\|Action=Select a vehicle.
			\|Result=A popup should show all the vehicle details. All fields should appear and be labelled as specified.
			}}
			{{TestPlan_Test
			\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
			\|Action=Select a Damage line
			\|Result=A popup should show all the damage details. All fields should appear and be labelled as specified.
	}}		}}


	{{TestPlan_Test		{{TestPlan_Test
	\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}		\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
	\|Action=~~{{warning}}~~ Show ~~the Damages Codes~~		\|Action=Show an image against a damage line.
	\|Result=		\|Result=The image should be displayed.
	}}		}}
	{{TestPlan_Test		{{TestPlan_Test
	\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}		\|Test={{ #vardefineecho: SubCycle \| {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
	\|Action=~~{{warning}} Display~~ the ~~POD/POC in various formats~~.		\|Action=From the Jobs screen, choose to display the completion report for the job for each type (Collection and Delivery), for each Job Group (GEFCO, EULOS and BARCA).
	\|Result=		\|Result=The correct report (POD or POC) should be displayed, depending on the Job type and the Job Group configuration.
	}}		}}

	{{TestPlan_CycleFooter}}		{{TestPlan_CycleFooter}}



	<!-- MEDIA LANDSCAPE NO -->		<!-- MEDIA LANDSCAPE NO -->

Anw: v0.3 - Added Image Breakdown; added Job Vehicle Updates for linked jobs; continued test plan

2012-06-11T10:04:19Z

v0.3 - Added Image Breakdown; added Job Vehicle Updates for linked jobs; continued test plan

Show changes

Anw: Edited Test plan

2012-06-08T15:36:41Z

Edited Test plan

Show changes

Anw: v0.2 - Completed setup and data sections

2012-06-08T14:36:00Z

v0.2 - Completed setup and data sections

← Older revision		Revision as of 16:36, 8 June 2012
Line 5:		Line 5:
	{{#vardefine:Doc_Title\|EuLoS EPOD Modifications}}		{{#vardefine:Doc_Title\|EuLoS EPOD Modifications}}
	{{#vardefine:Version\|0.1}}		{{#vardefine:Version\|0.1}}
	{{#vardefine:Date\|~~6th~~ June 2012}}		{{#vardefine:Date\|8th June 2012}}
	{{#vardefine:Reference\|299880}}		{{#vardefine:Reference\|299880}}
	{{#vardefine:Year\|2012}}		{{#vardefine:Year\|2012}}
Line 97:		Line 97:

	== Scope ==		== Scope ==
	~~{{warning}}~~ The developments will take place against the latest version of the EPOD system (1.32.X)		The developments will take place against the latest version of the EPOD system (1.31.X)

	<!-- NEW PAGE -->		<!-- NEW PAGE -->

	= Set-up =		= Set-up =
	~~{{warning}}~~
	== Pre-requisites ==		== Pre-requisites ==
	For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server. Additionally, each customer must have an Email address assigned to them for automatic emails to be sent.		For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server. Additionally, each customer must have an Email address assigned to them for automatic emails to be sent.

	== Menu Structure ==		== Menu Structure ==

	== Data ==		== Data ==
	A Site will be generated. This will be agreed in advance, but is expected to be "EULOS". This is generated and maintained through the Site Admin screen.		A Site will be generated. This will be agreed in advance, but is expected to be "EULOS". This is generated and maintained through the Site Admin screen.
	*PDF Production will be enabled from this screen.		* PDF Production will be enabled from this screen, by setting the "POD's PDF" check box.
	* ~~{{warning}}~~ Notes		* Notes will be enabled against the Job by setting the "User Notes" check box.
			* Collections and Deliveries with the same reference (Job Code) will be linked for updating, by setting the "Link C & D on Job Code" check box.

	A Job Group will be set up for the depots using the system, through the Job Group Admin screen.		A Job Group will be set up for the depots using the system, through the Job Group Admin screen.
	*The format for collections will be set to "EULOS POC" and deliveries set to "EULOS POD" against each Job Group, from the Job Groups screen. For Barcelona, the format for collections will be set to "EULOS POC 2"		*The format for collections will be set to "EULOS POC" and deliveries set to "EULOS POD" against each Job Group, from the Job Groups screen. For Barcelona, the format for collections will be set to "EULOS POC 2"
	* ~~{{warning}} Notes~~		* Collections and Deliveries with the same reference (Job Code) will be linked for updating, by setting the "Link C & D on Job Code" check box.
	* {{warning}}

	A Customer record will be set up for each of the Job Groups, with the same ID as the Job Groups. This address of these customer records will be used to identify the Depot Address on the documentation.		A Customer record will be set up for each of the Job Groups, with the same ID as the Job Groups. This address of these customer records will be used to identify the Depot Address on the documentation.
Line 122:		Line 120:
	Reason Codes will be set up as agreed between any host system and ''CALIDUS'' EPOD. These are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system.		Reason Codes will be set up as agreed between any host system and ''CALIDUS'' EPOD. These are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system.

	Reason Codes for the Vehicle Defect Location, Type and Severity will be set up as required by the operation. {{Note}} Type codes that have multiple sub-values will be encoded separately i.e. CD-Cut and CD-Torn will be stored as two separate codes.		Reason Codes for the Vehicle Defect Location, Type and Severity will be set up as required by the operation.

			{{Note}} Type codes that have multiple sub-values will be encoded separately i.e. CD-Cut and CD-Torn will be stored as two separate codes.

	= Functional Description =		= Functional Description =
	~~{{warning}}~~
	The following areas will require modification:		The following areas will require modification:
	* Database Changes		* Database Changes
Line 146:		Line 145:

	==Database Fields==		==Database Fields==
	~~{{warning}}~~ EPOD_CONTAINER		Table EPOD_CONTAINER will be modified as follows:
	* Three new fields, EPL_CODE_1/2/3, will be added to the table, to allow for several new fields. These fields will be 20 character nvarchar fields.		* Three new fields, EPL_CODE_1/2/3, will be added to the table, to allow for several new fields. These fields will be 20 character nvarchar fields.

	~~{{warning}}~~ "System Type" flag, with options "Vehicle Delivery" and "Generic" ~~(SITE)~~		Table EPOD_SITE will be modified as follows:
			* A new "System Type" flag will be added, called EPL_SYSTEM_TYPE, with options "Vehicle Delivery" and "Generic"
	~~EPOD_REASON_CODES~~
	~~EPL_DESCRIPTION will be changed to a MAX length nvarchar field.~~

			Table EPOD_REASON_CODES will be modified as follows:
			* EPL_DESCRIPTION will be changed to a MAX length nvarchar field.
			* EPL_REASON_CODE will be changed to allow up to 20 characters.

	==Import/Export Data==		==Import/Export Data==
Line 334:		Line 334:
	\|Glossary=EPOD		\|Glossary=EPOD
	\|Ref1=UG 291094 EPOD Admin User Guide		\|Ref1=UG 291094 EPOD Admin User Guide
	\|RefV1=1.0		\|RefV1=2.0
	\|RefDate1=6/10/~~2011~~		\|RefDate1=4/4/2012
	\|Ref2=UG 291097 EPOD Client User Guide		\|Ref2=UG 291097 EPOD Client User Guide
	\|RefV2=1.0		\|RefV2=2.0
	\|RefDate2=6/10/~~2011~~		\|RefDate2=4/4/2012
	\|REQ=0		\|REQ=0
	\|EST=0		\|EST=0

Anw: /* PDA Changes */

2012-06-08T13:30:04Z

PDA Changes

← Older revision		Revision as of 15:30, 8 June 2012
Line 232:		Line 232:

	The suggested screen layouts are as follows:		The suggested screen layouts are as follows:
			* The Vehicle Details screen
	[[file:299880-PDA-Details1.PNG]]		[[file:299880-PDA-Details1.PNG]]
	* The ~~Vehicle Details~~ screen		* The pop-up Damage Entry screen
	[[file:299880-PDA-Details2.PNG]]		[[file:299880-PDA-Details2.PNG]]
	* The pop-up ~~Damage Entry screen~~		* The pop-up menu, from long-pressing the grid.
	[[file:299880-PDA-Details3.PNG]]		[[file:299880-PDA-Details3.PNG]]
	* The pop-up menu, from long-pressing the grid.

	Each defect will be stored as an entry against EPOD_PRODUCT.		Each defect will be stored as an entry against EPOD_PRODUCT.

Anw: /* Appendix A: POD Formats */

2012-06-08T13:28:38Z

Appendix A: POD Formats

← Older revision		Revision as of 15:28, 8 June 2012
Line 310:		Line 310:
	<!-- NEW PAGE -->		<!-- NEW PAGE -->
	= Appendix A: POD Formats =		= Appendix A: POD Formats =
	~~[[File:299880-ColNote.jpg\|700px\|border]]~~
	~~<!-- NEW PAGE -->~~
	[[File:299880-DeliveryNote.jpg\|700px\|border]]		[[File:299880-DeliveryNote.jpg\|700px\|border]]
	<!-- NEW PAGE -->		<!-- NEW PAGE -->
	[[File:299880-BarcaNote.jpg\|700px\|border]]		[[File:299880-BarcaNote.jpg\|700px\|border]]

	<!-- MEDIA LANDSCAPE YES -->		<!-- MEDIA LANDSCAPE YES -->

	= Appendix B: Test Plan =		= Appendix B: Test Plan =
	{{TestPlan_Header		{{TestPlan_Header

Anw: v0.1 - Initial Document Creation

2012-06-08T13:22:35Z

v0.1 - Initial Document Creation

New page

<div class="noprint">
{{#vardefine:Client|EUL}}
{{#vardefine:ClientName|EuLoS}}
{{#vardefine:System|''CALIDUS'' EPOD}}
{{#vardefine:Doc_Title|EuLoS EPOD Modifications}}
{{#vardefine:Version|0.1}}
{{#vardefine:Date|6th June 2012}}
{{#vardefine:Reference|299880}}
{{#vardefine:Year|2012}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==
=== Admin Functionality ===
Jobs are created within the Admin screens or sent to the system through the standard Web Services (to be slightly modified to accept some new fields).

A method will be added to the Admin Job Creation screen to copy a collection to a delivery once created (if linked collections/deliveries are being used) – this will ease data creation for the Admin users.

The Admin User will enter the vehicles to be collected/delivered as containers against the job – user enters code as the vehicle registration, description is the make/model. The screen will be modified so that the labels are more descriptive of a Vehicle Delivery process (i.e. Vehicle Reg, Make/Model, etc)

Each vehicle and registration will be added as a separate line - if the operation is not aware of the car registration at the time of entering the job, the registration can be entered as a generic line (i.e. CAR1, CAR2, etc) or left blank.

The jobs will be assigned to loads, and the loads assigned to users through the Admin screens as per the existing functionality.

=== PDA Functionality ===
On the PDA, the User will log on with a provided User ID and Vehicle ID.

A vehicle labelled "CAR COLLECT" will be available for those drivers picking up a single car. All other vehicles are trailer plates and will be selectable by registration from the drop-down list provided. If the vehicle has not been checked that day, the PDA will force the user to perform the vehicle checks required. {{Note}} For "CAR COLLECT", these checks will be skipped by the user.

The user will then be provided the Load they have been allocated.

The Job List will display, showing the collection and delivery assigned to the load.

The User selects the Job from the list and is provided contact details and address information, as normal, along with the Job reference.

When the user starts the job, the PDA will display a list of vehicles to be collected. The user clicks a line (there should be one per vehicle registration). Note that the screen labels will be modified to show Vehicle/Reg, etc.

The User will be prompted to enter
* Model/Make (defaulted to that entered on the Job)
* Registration/Chassis (defaulted to that entered on the Job)
* Spare (check box entry)
* Radio (check box entry)
* The user will also be able to enter Defects, if any are found:
** The PDA will allow selection of the Location/Type/Severity required, through drop-down lists. A Button will be provided to add the defect to a list below. A Button will be provided to capture an image associated to the defect, if required.
** A Grid of all entered defects will be shown below, showing the coded entry (i.e. 37 CE-Punctured 1). – Click the grid line to edit the entry above and see the detail. If editing, there will be a button to remove the defect. OK to save again.
* When complete, the User clicks OK, and is returned to the container (vehicle) list.

Completion of collection or delivery is after all container (vehicle) items are confirmed collected or delivered.

There will be a facility for the User to enter notes against the collection or delivery.

The User is then prompted for the customer signature.

Assuming 1 collection and delivery on a load, the User is returned to the job list, with only the delivery portion remaining. The vehicles will have been copied to the Delivery, but not the defect codes.

Click the delivery, and the user will be shown the Delivery with the same job code but the delivery address.

The Delivery process works identically to the Collection process. Vehicle Details and Condition codes will not be pre-entered.

On completion of all jobs, all messages are sent back to the EPOD database. All Images are sent separately. Images will be sent after normal messages, but normal messages may be queued after an image already in the process of being sent.

=== Completion Reports ===

The Admin Products screen will be modified to show the labels of Vehicles/Condition in all places if the new configuration flag 'Vehicle Delivery System' is set. The Job Details screen will display the condition location/type/severity codes entered by the PDA user. Images taken by the PDA users can be seen from here.

The POD/POC reports will show the logo of the company to whom the job belongs (configured within the EPOD system). The POC will not display the data relating to the delivery.

The Terms and Conditions will be added to the second page of the POD/POC.

All POD and POC values can be emailed directly to the customer/client as required.

ERP systems (if any) can be updated at this time.

== Barcelona System ==
This system will be used here only to examine cars in the lot associated to the office.

Cars will be added onto a load and the load assigned to a user.

The users will use the PDA to inspect each car in turn, the device is being used as inspection data entry, and the system used to print off an inspection form (the POC document).

This operation will be under a different site and/or job group, so that it can have its own configuration.

The POC format produced will be different to the normal operation. It will be multi-page document, the second page showing all the defect codes.

== Scope ==
{{warning}} The developments will take place against the latest version of the EPOD system (1.32.X)



= Set-up =
{{warning}}
== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server. Additionally, each customer must have an Email address assigned to them for automatic emails to be sent.

== Menu Structure ==

== Data ==
A Site will be generated. This will be agreed in advance, but is expected to be "EULOS". This is generated and maintained through the Site Admin screen.
*PDF Production will be enabled from this screen.
* {{warning}} Notes

A Job Group will be set up for the depots using the system, through the Job Group Admin screen.
*The format for collections will be set to "EULOS POC" and deliveries set to "EULOS POD" against each Job Group, from the Job Groups screen. For Barcelona, the format for collections will be set to "EULOS POC 2"
* {{warning}} Notes
* {{warning}}

A Customer record will be set up for each of the Job Groups, with the same ID as the Job Groups. This address of these customer records will be used to identify the Depot Address on the documentation.

Reason Codes will be set up as agreed between any host system and ''CALIDUS'' EPOD. These are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system.

Reason Codes for the Vehicle Defect Location, Type and Severity will be set up as required by the operation. {{Note}} Type codes that have multiple sub-values will be encoded separately i.e. CD-Cut and CD-Torn will be stored as two separate codes.

= Functional Description =
{{warning}}
The following areas will require modification:
* Database Changes
* Import/Export
** Add new fields
** Add Generation of EPL_CONTAINER_ID to Import.
* Admin Changes
** Copy Collection to Delivery button
** Job/Job Details Screens Label Changes
** Job Products to translate Vehicle Damage Codes
** Reason Codes screen
*** Vehicle Damage Codes
*** MAX Length Description field
* PDA Changes
** Collection/Delivery Label Changes
** Vehicle Details Tab
** Copy Vehicle Details to Linked Delivery
** Sequence Image messages After All Normal Messages
* POD/POC Formats

==Database Fields==
{{warning}} EPOD_CONTAINER
* Three new fields, EPL_CODE_1/2/3, will be added to the table, to allow for several new fields. These fields will be 20 character nvarchar fields.

{{warning}} "System Type" flag, with options "Vehicle Delivery" and "Generic" (SITE)

EPOD_REASON_CODES
EPL_DESCRIPTION will be changed to a MAX length nvarchar field.

==Import/Export Data==
Import and Export of Jobs and Loads will be through the existing standard Web Services.

These will be modified to add the new fields listed in the previous section.

Additionally, the Import processes will be modified to auto-generate the Container ID if it is not provided.

== Admin Changes ==
=== Job Screen ===
A new button (Copy Collection to Delivery) will be available if the Job Group or Site is configured for Linked Collections and Deliveries. Clicking this button will create a linked Collection or Delivery and copy all the data from the original job.

The user will be given a extra tab on the job screen popup. If a link is present the update function will copy any data below the job level to the linked job. The code to complete this will exist within the DAL.

=== Reason Codes Screen ===
This screen will be modified to allow the user to enter 3 additional different types of codes:
* VLOC - Vehicle Damage Location
* VTYPE - Vehicle Damage Type
* VSEV - Vehicle Damage Severity
These code types should be
* visible (with the human-readable text) within the grid when showing saved codes
* selectable (with the human-readable text) through the filter.
* able to be added against a new code
* able to be changed against an existing code being edited
A Drop-down List should be provided of all the types.

Additionally, this screen should be modified to allow the user to display and enter an unlimited number of characters in the description.

=== Job Details Screen ===
If the new System Type flag is set to "Vehicle Delivery", the function of this screen will change slightly.

* The "New Container" button will become New Vehicle.
* "Containers for Job" will become "Vehicles for Job"
* The "New Loose Product" button will be removed.
* The Containers grid will not display the "Container ID" field
* The "Products" button will become the "Damages" button.
* "Package Code" will become "Vehicle Reg"
* "Description" will become "Model/Make"
* "Products for Container" will become "Damages for Vehicle".
* The "New Product" button will become the "New Damages" button.
* The Products grid will be replaced with a Damages grid showing:
** Damage Code (comprising Location, Type and Severity)
** Damage Description (comprising the description looked up from each Location, Type and Severity in the Damage code above)

On pressing Select against a grid line (or adding a new Container/Vehicle), the following changes will be made to the pop-up:
* The pop-up will be titled "Vehicle Details"
* "Container ID" will be removed and automatically generated
* "Package Code" will become "Vehicle Reg"
* "Description" will become "Model/Make"
* "Long Description" will be removed.
* "Gross Weight" will be removed.
* Three new fields will be added (EPL_CODE_1, EPL_CODE_2 and EPL_CODE_3) only when this flag is set. The first two shall be labelled as Spare and Radio. Both will be Drop-down lists, allowing the values "Yes" and "No" only (actual values "Y" and "N" stored). The last shall be labelled CMR No.

In addition, any pop-up messages or validation messages will change to reflect the following:
* A "Container" is a "Vehicle"
* "Description" is "Model/Make"
* "Product" is "Damage"

== PDA Changes ==
If the new "System Type" flag is set to "Vehicle Delivery", the function of the Collection and Delivery screens will change.
* The "Containers" tab will be labelled as "Vehicles".
* A new tab will be created, labelled as "Details".
* The scanned item will be EPL_PACKAGE_DESC rather than EPL_CONTAINER_ID.

When a vehicle has been entered/scanned and marked as collected or delivered (through the appropriate button), the system will move on to the new Details tab.

The User will be prompted to enter:
* Model/Make (defaulted to EPL_PACKAGE_DESC)
* Registration/Chassis (defaulted to EPL_DESCRIPTION)
* CMR # (defaulted to EPL_CODE3)
* Spare (check box entry of EPL_CODE1)
* Radio (check box entry of EPL_CODE2)
* The user will also be able to enter Defects, if any are found, using the button provided:
** The PDA will allow selection of the Location/Type/Severity required, through a pop-up screen, selecting values from drop-down lists. A Button will be provided to add the defect to a list below. A Button will be provided to capture an image associated to the defect, if required.
** A Grid of all entered defects will be shown below, showing the coded entry (i.e. 37 CE-Punctured 1). The user will be able to long-hold against a grid-line to delete or edit the entry.

The suggested screen layouts are as follows:
[[file:299880-PDA-Details1.PNG]]
* The Vehicle Details screen
[[file:299880-PDA-Details2.PNG]]
* The pop-up Damage Entry screen
[[file:299880-PDA-Details3.PNG]]
* The pop-up menu, from long-pressing the grid.

Each defect will be stored as an entry against EPOD_PRODUCT.
Any images taken against a defect will be saved against the EPOD_PRODUCT record.

If no codes are entered when OK is pressed, a popup confirmation will be displayed ("No Damage?").

Completion of collection or delivery is after all container (vehicle) items are confirmed collected or delivered.

There will be a facility for the User to enter notes against the collection or delivery, through the standard Notes tab.

When complete, the User will click OK and is returned to the container (vehicle) list. The messages will be sent back to the EPOD server for confirmation.

If the Load has the same reference being delivered later, both the PDA and the Server will update the Delivery associated to the Collection with the Vehicle information (i.e. the Container records) but not the Damages information (i.e. the Products).

=== Sequence Image messages After All Normal Messages ===
The PDA Sending process will be modified to ensure that all images are sequenced for sending after any other pending messages, via a sort order on the pending message.

== POD/POC Formats ==

The POD/POC reports will show the logo of the company to whom the job belongs (configured within the EPOD system). The POC will not display the data relating to the delivery.

=== Format "EULOS POD" ===
* Collect From: Name and Address information from the Customer or Job Address associated to the Collection Job of that Job Code. The Date is the Date the Collection job was completed.
* Deliver To: Name and Address information from the Customer or Job Address associated to the Delivery Job of that Job Code. The Date is the Date the Delivery job was completed.
* Model/Make: EPL_DESCRIPTION of EPOD_CONTAINER
* Registration/Chassis: EPL_PACKAGE_DESC of EPOD_CONTAINER
* Spare: EPL_CODE1 of EPOD_CONTAINER
* Radio: EPL_CODE2 of EPOD_CONTAINER
* Collection Condition: This is the consolidated values of EPL_PRODUCT_DESCRIPTION of EPOD_PRODUCT, comma delimited, from the Collection job of this Job Code.
* Delivery Condition: This is the consolidated values of EPL_PRODUCT_DESCRIPTION of EPOD_PRODUCT, comma delimited, from the Delivery job of this Job Code.
* Driver Name: EPL_NAME of EPOD_USER, of the PDA User who completed the Delivery job (EPL_USER_ID of EPL_JOB)
* Truck Registration: EPL_VEHICLE_REG of EPOD_VEHICLE, of the Vehicle driven by the user who completed the Delivery job (EPL_VEHICLE_ID of EPOD_JOB).
* Reference Number: EPL_CUST_REF of the EPOD_JOB record for the Delivery Job.
* Collection Name: EPL_SIGNATORY of the EPOD_JOB record for the Collection Job.
* Collection Signature: EPL_SIGNATURE of the EPOD_JOB record for the Collection Job.
* Delivery Name: EPL_SIGNATORY of the EPOD_JOB record for the Delivery Job.
* Delivery Signature: EPL_SIGNATURE of the EPOD_JOB record for the Delivery Job.

A second page will be produced showing all the terms and conditions.

=== Format "EULOS POC" ===
This is the same as the POD document above, but with the following changes:
* The Deliver To box is not displayed.
* The Delivery Collection column is not displayed.
* The Delivery Name/Signature box is not displayed.
* Driver Name: EPL_NAME of EPOD_USER, of the PDA User who completed the Collectionjob (EPL_USER_ID of EPL_JOB)
* Truck Registration: EPL_VEHICLE_REG of EPOD_VEHICLE, of the Vehicle driven by the user who completed the Collection job (EPL_VEHICLE_ID of EPOD_JOB).
* Reference Number: EPL_CUST_REF of the EPOD_JOB record for the Collection Job.

=== Format "EULOS POC 2"
This format will print one page per container, rather than one page per job.

* Model: EPL_DESCRIPTION of EPOD_CONTAINER
* Load No: EPL_JOB_CODE of EPOD_JOB
* REF No: EPL_CUST_REF of EPOD_JOB
* Chassis/Reg No: EPL_PACKAGE_DESC of EPOD_CONTAINER
* CMR No: EPL_CODE3 of EPOD_CONTAINER
* Purchase Order No: EPL_SO_NUMBER of EPOD_JOB
* Collection Point Area, Damage and Severity Codes: This is the consolidated values of EPL_PRODUCT_DESCRIPTION of EPOD_PRODUCT, comma delimited, from the Collection job of this Job Code.
* Truck No/Ship: EPL_VEHICLE_REG of EPOD_VEHICLE, of the Vehicle driven by the user who completed the Collection job (EPL_VEHICLE_ID of EPOD_JOB).
* Driver Name: EPL_NAME of EPOD_USER, of the PDA User who completed the Collection job (EPL_USER_ID of EPL_JOB)
* Driver Signature: EPL_SIGNATURE of the EPOD_JOB record for the Collection Job.
* Date: The Date is the Date the Collection job was completed (EPL_ACTUAL_END_DATE of EPOD_JOB).

{{note}} All other parts of the format not mentioned above will be printed but are not filled in with any data compiled from the job completion.

{{warning}} The diagram of the car will be supplied by the client.

A second page will be produced showing all the damage location, type and severity codes.


= Appendix A: POD Formats =
[[File:299880-ColNote.jpg|700px|border]]

[[File:299880-DeliveryNote.jpg|700px|border]]

[[File:299880-BarcaNote.jpg|700px|border]]


= Appendix B: Test Plan =
{{TestPlan_Header
|Title=EuLoS EPOD Test Plan
|Log=299880
|Description=Test the functionality required by the EuLoS operation
|MenuAccess=Various
|Prerequisites=Ensure that site EULOS is created, with Users ADM and PDA pre-created.
|Objective=To ensure that the Import, Admin, PDA and Export functionality of the ''CALIDUS'' EPOD system operate as expected
}}{{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}

{{warning}} Complete test plan


{{Doc_Appendix
|Appendix=C
|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=2
|TS=0
|DEV=16
|ST=5
|IMP=0
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=N
|Rev1={{warning}} Client Rep
|Rev1Title=Client Representative
|Rev2=Matt Turner
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]