FS 297001 Prolog EPOD Modifications - Revision history

Anw: v1.2 - Added test plan

2012-05-03T14:55:13Z

v1.2 - Added test plan

Show changes

Anw: Updated Import XML samples to the correct format.

2012-05-03T14:38:42Z

Updated Import XML samples to the correct format.

Show changes

Anw: v1.1 - New version with clarified XML Export layouts

2012-04-11T07:07:28Z

v1.1 - New version with clarified XML Export layouts

Show changes

Anw: v1.0 - Issued after confirmation from Rob Ellis

2012-03-28T15:03:30Z

v1.0 - Issued after confirmation from Rob Ellis

← Older revision		Revision as of 17:03, 28 March 2012
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' EPOD}}		{{#vardefine:System\|''CALIDUS'' EPOD}}
	{{#vardefine:Doc_Title\|Prolog EPOD Modifications}}		{{#vardefine:Doc_Title\|Prolog EPOD Modifications}}
	{{#vardefine:Version\|0.6}}		{{#vardefine:Version\|1.0}}
	{{#vardefine:Date\|~~15th~~ March 2012}}		{{#vardefine:Date\|28th March 2012}}
	{{#vardefine:Reference\|297001}}		{{#vardefine:Reference\|297001}}
	{{#vardefine:Year\|2012}}		{{#vardefine:Year\|2012}}

Anw at 16:29, 15 March 2012

2012-03-15T16:29:10Z

← Older revision		Revision as of 18:29, 15 March 2012
Line 618:		Line 618:
	These users will be able to view (and create) loads and jobs within the system, as well as view the completion documents for completed jobs, or view images of exceptions on cancelled jobs.		These users will be able to view (and create) loads and jobs within the system, as well as view the completion documents for completed jobs, or view images of exceptions on cancelled jobs.

	The Job Group screen will require modification, to add the new configuration flags (detailed in section [[#Database Fields\|Database Fields]]		The Job Group screen will require modification, to add the new configuration flags (detailed in section [[#Database Fields\|Database Fields]])

	The Load screen will be modified to add a mouse-over tool-tip, displaying the start and end vehicle mileage.		The Load screen will be modified to add a mouse-over tool-tip, displaying the start and end vehicle mileage.

Anw: v0.6 - Amended after feedback from Rob Ellis

2012-03-15T16:27:48Z

v0.6 - Amended after feedback from Rob Ellis

← Older revision		Revision as of 18:27, 15 March 2012
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' EPOD}}		{{#vardefine:System\|''CALIDUS'' EPOD}}
	{{#vardefine:Doc_Title\|Prolog EPOD Modifications}}		{{#vardefine:Doc_Title\|Prolog EPOD Modifications}}
	{{#vardefine:Version\|0.5}}		{{#vardefine:Version\|0.6}}
	{{#vardefine:Date\|~~7st~~ March 2012}}		{{#vardefine:Date\|15th March 2012}}
	{{#vardefine:Reference\|297001}}		{{#vardefine:Reference\|297001}}
	{{#vardefine:Year\|2012}}		{{#vardefine:Year\|2012}}
Line 49:		Line 49:
	Collection jobs will have no product or container details, just job instructions detailing the products and quantities to be collected.		Collection jobs will have no product or container details, just job instructions detailing the products and quantities to be collected.

	Linked Collections and Deliveries (i.e. collecting from a supplier and delivering directly to a customer on the same trip) will be required. In this instance, the jobs will be linked by having the same Job Code on each job.		Collections and Deliveries will be identified by the Job Code - this will be the Order Reference.

			Linked Collections and Deliveries (i.e. collecting from a supplier and delivering directly to a customer on the same trip) will be required. In this instance, the jobs will be linked by having the same Job Code on each job. The Job Code on both the Collection and Delivery will the the same.

	The Load import includes the Driver assigned to the Load.		The Load import includes the Driver assigned to the Load.
Line 196:		Line 198:
	**Load		**Load
	*Pass new configuration to PDA		*Pass new configuration to PDA
	*Job Assignation by Vehicle
	*Metric Entry		*Metric Entry
	*Load Update from PDA to Server		*Load Update from PDA to Server
Line 235:		Line 236:

	===Job===		===Job===
	An Owner field added to the Job import, to allow the client system to specify ~~the Depot~~ (e.g. Britvic).		The Job Group field will identify the depot from which the Job originates.

			An Owner field added to the Job import, to allow the client system to specify Prolog's Client (e.g. Britvic).

	The Customer information (i.e. customer code, name address and contact details) will be sent as part of Job, so that this information can be placed on the resulting completion document (POD or POC).		The Customer information (i.e. customer code, name address and contact details) will be sent as part of Job, so that this information can be placed on the resulting completion document (POD or POC).
Line 259:		Line 262:
	<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>		<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
	<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>		<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
	<EPL_JOB_CODE>~~JOB_CODE_001~~</EPL_JOB_CODE>		<EPL_JOB_CODE>00067527</EPL_JOB_CODE>
	<EPL_CUST_REF>~~00067527~~</EPL_CUST_REF>		<EPL_CUST_REF></EPL_CUST_REF>
	<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>		<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
	<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>		<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
Line 285:		Line 288:
	<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>		<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
	<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>		<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
	<EPL_JOB_CODE>~~JOB_CODE_001~~</EPL_JOB_CODE>		<EPL_JOB_CODE>00067527</EPL_JOB_CODE>
	<EPL_CUST_REF>~~00067527~~</EPL_CUST_REF>		<EPL_CUST_REF></EPL_CUST_REF>
	<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>		<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
	<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>		<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
Line 311:		Line 314:
	<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>		<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
	<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>		<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
	<EPL_JOB_CODE>~~JOB_CODE_002~~</EPL_JOB_CODE>		<EPL_JOB_CODE>00067523</EPL_JOB_CODE>
	<EPL_CUST_REF>~~00067523~~</EPL_CUST_REF>		<EPL_CUST_REF></EPL_CUST_REF>
	<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>		<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
	<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>		<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
Line 363:		Line 366:
	*EPL_JOB_GROUP will be the originating Depot ID (e.g. "SHEFFIELD"). These will be pre-set and agreed in advance.		*EPL_JOB_GROUP will be the originating Depot ID (e.g. "SHEFFIELD"). These will be pre-set and agreed in advance.
	*EPL_JOB_ID (10 characters) is a unique reference for the individual job (collection or delivery). For linked collections and deliveries, each job should have a unique EPL_JOB_ID, but the same EPL_JOB_CODE. If left blank, this will be generated by the system. This will be mapped to the unique value of the currently used barcode.		*EPL_JOB_ID (10 characters) is a unique reference for the individual job (collection or delivery). For linked collections and deliveries, each job should have a unique EPL_JOB_ID, but the same EPL_JOB_CODE. If left blank, this will be generated by the system. This will be mapped to the unique value of the currently used barcode.
	*EPL_JOB_CODE (20 characters) will be any reference that ties linked jobs together.		*EPL_JOB_CODE (20 characters) will be any reference that ties linked jobs together, or a unique reference for the job.
	*An additional reference can be mapped to EPL_CUST_REF (30 characters)~~. This will map to the consignment number~~.		*An additional reference can be mapped to EPL_CUST_REF (30 characters).
	*The customer code, name, contact and address information will be mapped to the appropriate fields.		*The customer code, name, contact and address information will be mapped to the appropriate fields.
	*EPL_CONTAINER_ID (15 characters) will be the Order Reference.		*EPL_CONTAINER_ID (15 characters) will be the Order Reference.
Line 373:		Line 376:
	Loads can be imported separately or the jobs can be included within the EPOD_JOBS tag.		Loads can be imported separately or the jobs can be included within the EPOD_JOBS tag.

	The Load import includes the Driver ~~and Vehicle~~ assigned to the Load.		The Load import includes the Driver assigned to the Load.

	{{warning}} Currently the client system allocates jobs to a Vehicle, not a Driver, whilst ''CALIDUS'' EPOD assigns by the User ID (the Driver). In the requirements meeting, did we decide which will be changed, EPOD or Transport system?

	<EPOD_IMPORT EPL_SITE_ID="PROLOG" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">		<EPOD_IMPORT EPL_SITE_ID="PROLOG" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
Line 388:		Line 389:
	<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>		<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
	<EPL_USER_ID>MATT</EPL_USER_ID>		<EPL_USER_ID>MATT</EPL_USER_ID>
	~~<EPL_VEHICLE_ID>AB12XYZ</EPL_VEHICLE_ID>~~
	<EPOD_JOBS>		<EPOD_JOBS>
	...		...
Line 499:		Line 499:
	<EPL_INVOICED/>		<EPL_INVOICED/>
	<EPL_CUST_SIGNATORY/>		<EPL_CUST_SIGNATORY/>
	<EPL_JOB_CODE></EPL_JOB_CODE>		<EPL_JOB_CODE>00067523</EPL_JOB_CODE>
	<EPL_CUST_REF>~~00067523~~</EPL_CUST_REF>		<EPL_CUST_REF></EPL_CUST_REF>
	<EPL_OFFICE_INSTRUCTION/>		<EPL_OFFICE_INSTRUCTION/>
	<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>		<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
Line 589:		Line 589:
	*'''Customer''': The Code will be EPL_CUSTOMER_CODE of EPOD_JOB. The address will be taken from this customer's EPOD_CUSTOMER record.		*'''Customer''': The Code will be EPL_CUSTOMER_CODE of EPOD_JOB. The address will be taken from this customer's EPOD_CUSTOMER record.
	*'''"2 Pallets / 162 Kg"''': EPL_CONTAINER_PACKAGE_DESC of EPOD_CONTAINER		*'''"2 Pallets / 162 Kg"''': EPL_CONTAINER_PACKAGE_DESC of EPOD_CONTAINER
	*'''Order Reference''': ~~EPL_CONTAINER_ID~~ of ~~EPOD_CONTAINER~~		*'''Order Reference''': EPL_JOB_CODE of EPOD_JOB
	*'''Order Processed''': EPL_START_ACTUAL_DATE of EPOD_JOB		*'''Order Processed''': EPL_START_ACTUAL_DATE of EPOD_JOB
	*'''Reference''': EPL_PRODUCT_CODE of EPOD_PRODUCT		*'''Reference''': EPL_PRODUCT_CODE of EPOD_PRODUCT
Line 599:		Line 599:
	*'''Time''': EPL_END_ACTUAL_TIME of EPOD_JOB		*'''Time''': EPL_END_ACTUAL_TIME of EPOD_JOB
	*'''Notes''': EPL_NOTES of EPOD_JOB {{Note}} New Field		*'''Notes''': EPL_NOTES of EPOD_JOB {{Note}} New Field
	*'''Consignment Barcode''': ~~{{Warning}} is this~~ required~~? If so, from what data?~~		*'''Consignment Barcode''': Not required
	*'''"SM0425 00000 00113306"''': ~~{{Warning}} is this~~ required~~? If so, from what data?~~		*'''"SM0425 00000 00113306"''': Not required
	~~{{warning}} The data contained in the barcode is not the number above - what is this?~~

	==Data Clear-down==		==Data Clear-down==
Line 656:		Line 655:
	\|Year={{#var:Year}}		\|Year={{#var:Year}}
	\|FSEST=N		\|FSEST=N
	\|Rev1=~~Tony Walker~~		\|Rev1=Rob Ellis
	\|Rev1Title=~~Consultant~~		\|Rev1Title=Client Representative
	\|Rev2=Matt Turner		\|Rev2=Matt Turner
	\|Rev2Title=OBS Representative		\|Rev2Title=OBS Representative
	}}</div>		}}</div>
	[[Category:{{#var:Client}} FS]]		[[Category:{{#var:Client}} FS]]

Milesl: v0.5 Version updated

2012-03-07T11:24:16Z

v0.5 Version updated

← Older revision		Revision as of 13:24, 7 March 2012
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' EPOD}}		{{#vardefine:System\|''CALIDUS'' EPOD}}
	{{#vardefine:Doc_Title\|Prolog EPOD Modifications}}		{{#vardefine:Doc_Title\|Prolog EPOD Modifications}}
	{{#vardefine:Version\|0.4}}		{{#vardefine:Version\|0.5}}
	{{#vardefine:Date\|~~1st~~ March 2012}}		{{#vardefine:Date\|7st March 2012}}
	{{#vardefine:Reference\|297001}}		{{#vardefine:Reference\|297001}}
	{{#vardefine:Year\|2012}}		{{#vardefine:Year\|2012}}

Milesl: Added Address line 5

2012-03-07T11:19:09Z

Added Address line 5

← Older revision		Revision as of 13:19, 7 March 2012
Line 227:		Line 227:
	*JOB - A configuration set for JOB updates		*JOB - A configuration set for JOB updates
	*LOAD - A configuration set for LOAD updates		*LOAD - A configuration set for LOAD updates

			New Fields to both EPOD_CUSTOMER and EPOD_JOB_ADDRESS
			*EPL_ADDRESS_5

	==Import Data==		==Import Data==

Milesl: v0.4 Version updated

2012-03-01T14:36:27Z

v0.4 Version updated

← Older revision		Revision as of 16:36, 1 March 2012
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' EPOD}}		{{#vardefine:System\|''CALIDUS'' EPOD}}
	{{#vardefine:Doc_Title\|Prolog EPOD Modifications}}		{{#vardefine:Doc_Title\|Prolog EPOD Modifications}}
	{{#vardefine:Version\|0.3}}		{{#vardefine:Version\|0.4}}
	{{#vardefine:Date\|1st March 2012}}		{{#vardefine:Date\|1st March 2012}}
	{{#vardefine:Reference\|297001}}		{{#vardefine:Reference\|297001}}

Milesl: Removed Job assignment by vehicle

2012-03-01T14:35:55Z

Removed Job assignment by vehicle

← Older revision		Revision as of 16:35, 1 March 2012
Line 401:		Line 401:
	The server responds with a Logon Response, passing all the configuration and standing data to the device. The configuration will be modified to include the new configuration elements against the Site and Job Group. The PDA will store this configuration.		The server responds with a Logon Response, passing all the configuration and standing data to the device. The configuration will be modified to include the new configuration elements against the Site and Job Group. The PDA will store this configuration.

	~~==Job Assignation by Vehicle==~~

	The EPOD server will first attempt to find any incomplete loads assigned to that user. In the event that this does not return a load, the server will be modified to check for any incomplete loads assigned to that vehicle. If found, the Load will be assigned to that user and sent to the device as is does now for loads assigned to users.

	==Metric Entry==		==Metric Entry==
	Once a load has been downloaded, the unit will check whether the system requires Current Mileage entry against the load. If so, the unit will request the user to enter the mileage at this point. This will be though a form to enter the mileage in numeric form.		Once a load has been downloaded, the unit will check whether the system requires Current Mileage entry against the load. If so, the unit will request the user to enter the mileage at this point. This will be though a form to enter the mileage in numeric form.

← Older revision		Revision as of 17:03, 28 March 2012
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' EPOD}}		{{#vardefine:System\|''CALIDUS'' EPOD}}
	{{#vardefine:Doc_Title\|Prolog EPOD Modifications}}		{{#vardefine:Doc_Title\|Prolog EPOD Modifications}}
	{{#vardefine:Version\|0.6}}		{{#vardefine:Version\|1.0}}
	{{#vardefine:Date\|~~15th~~ March 2012}}		{{#vardefine:Date\|28th March 2012}}
	{{#vardefine:Reference\|297001}}		{{#vardefine:Reference\|297001}}
	{{#vardefine:Year\|2012}}		{{#vardefine:Year\|2012}}

← Older revision		Revision as of 13:24, 7 March 2012
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' EPOD}}		{{#vardefine:System\|''CALIDUS'' EPOD}}
	{{#vardefine:Doc_Title\|Prolog EPOD Modifications}}		{{#vardefine:Doc_Title\|Prolog EPOD Modifications}}
	{{#vardefine:Version\|0.4}}		{{#vardefine:Version\|0.5}}
	{{#vardefine:Date\|~~1st~~ March 2012}}		{{#vardefine:Date\|7st March 2012}}
	{{#vardefine:Reference\|297001}}		{{#vardefine:Reference\|297001}}
	{{#vardefine:Year\|2012}}		{{#vardefine:Year\|2012}}

← Older revision		Revision as of 16:36, 1 March 2012
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' EPOD}}		{{#vardefine:System\|''CALIDUS'' EPOD}}
	{{#vardefine:Doc_Title\|Prolog EPOD Modifications}}		{{#vardefine:Doc_Title\|Prolog EPOD Modifications}}
	{{#vardefine:Version\|0.3}}		{{#vardefine:Version\|0.4}}
	{{#vardefine:Date\|1st March 2012}}		{{#vardefine:Date\|1st March 2012}}
	{{#vardefine:Reference\|297001}}		{{#vardefine:Reference\|297001}}