Anw: v1.1 - Removed reference to Barcode scanning

2015-09-02T08:25:27Z

v1.1 - Removed reference to Barcode scanning

Anw: v1.0 - Released to customer

2015-08-05T11:29:41Z

v1.0 - Released to customer

← Older revision		Revision as of 13:29, 5 August 2015
Line 4:		Line 4:
	{{#vardefine:System\|''CALIDUS'' ePOD}}		{{#vardefine:System\|''CALIDUS'' ePOD}}
	{{#vardefine:Doc_Title\|Pall-Ex Interface}}		{{#vardefine:Doc_Title\|Pall-Ex Interface}}
	{{#vardefine:Version\|0.4}}		{{#vardefine:Version\|1.0}}
	{{#vardefine:Date\|~~14th July~~ 2015}}		{{#vardefine:Date\|3rd August 2015}}
	{{#vardefine:Reference\|324096}}		{{#vardefine:Reference\|324096}}
	{{#vardefine:Year\|2015}}		{{#vardefine:Year\|2015}}

Anw: Added fixed cost

2015-08-04T10:17:17Z

Added fixed cost

← Older revision		Revision as of 12:17, 4 August 2015
Line 862:		Line 862:
	\|Year={{#var:Year}}		\|Year={{#var:Year}}
	\|FSEST=Y		\|FSEST=Y
			\|FOC=Y
			\|FIXEDCOST=6000
	\|Rev1=Matt Turner		\|Rev1=Matt Turner
	\|Rev1Title=OBSL Account Manager		\|Rev1Title=OBSL Account Manager

Anw: v0.4 - Normalised version with internal documentation; Added pallet-level functionality at the request of the customer

2015-07-14T15:21:42Z

v0.4 - Normalised version with internal documentation; Added pallet-level functionality at the request of the customer

Show changes

Anw: Minor formatting changes

2015-06-18T14:33:10Z

Minor formatting changes

← Older revision		Revision as of 16:33, 18 June 2015
Line 1:		Line 1:
	<div class="noprint">		<div class="noprint">
	{{#vardefine:Client\|PART}}		{{#vardefine:Client\|PART}}
	{{#vardefine:ClientName\|~~The Client Name~~}}		{{#vardefine:ClientName\|Partnerlink}}
	{{#vardefine:System\|''CALIDUS'' ePOD}}		{{#vardefine:System\|''CALIDUS'' ePOD}}
	{{#vardefine:Doc_Title\|Pall-Ex Interface}}		{{#vardefine:Doc_Title\|Pall-Ex Interface}}
Line 165:		Line 165:


	== Database ===		== Database ==
	The database package used to retrieve the job transfer configurations must be modified.		The database package used to retrieve the job transfer configurations must be modified.

Line 258:		Line 258:
	The resulting message should be in this format:		The resulting message should be in this format:

	:addEpodConsignment		;addEpodConsignment
	<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"		<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
	xmlns:tem="http://tempuri.org/">		xmlns:tem="http://tempuri.org/">
Line 279:		Line 279:


	:addMPodImage		;addMPodImage
	<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"		<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
	xmlns:tem="http://tempuri.org/">		xmlns:tem="http://tempuri.org/">
Line 296:		Line 296:

	This function will check the response and, if this is a failure, will mark the job as having failed export (exactly as it does in the existing SOAP code). The responses, if successful will follow the format of:		This function will check the response and, if this is a failure, will mark the job as having failed export (exactly as it does in the existing SOAP code). The responses, if successful will follow the format of:
	Tag "whatevermethodResponse" containing tag "whatevermethodResult", containing at least the text "Success", as below for example:		:Tag "whatevermethodResponse" containing tag "whatevermethodResult"
			containing at least the text "Success", as below for example:

	<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"		<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"

Anw: v0.2 - Completed details. Note that this is draft until it is confirmed how the data will be received from the TMSs

2015-06-18T14:26:11Z

v0.2 - Completed details. Note that this is draft until it is confirmed how the data will be received from the TMSs

Show changes

Anw: v0.1 - Initial draft.

2015-05-29T16:02:49Z

v0.1 - Initial draft.

New page

<div class="noprint">
{{#vardefine:Client|PART}}
{{#vardefine:ClientName|The Client Name}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Pall-Ex Interface}}
{{#vardefine:Version|0.1}}
{{#vardefine:Date|26th May 2013}}
{{#vardefine:Reference|324096}}
{{#vardefine:Year|2015}}
</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 ==
AE Parker will be rolling out CALIDUS ePOD to their fleet and will need to send ePOD information/confirmation on deliver completion through to Pall-Ex systems.

== Solution Overview ==
Process:
* The new partner A.E.Parker will be set up with a new partner code within {{#var:System}}, will be configured for their use following the standard configuration. This partner will be configured for export to the TMS system in use.
* Pall-Ex specific reason codes will be set up as required by the Pall-Ex TWINE system.
* New Pall-Ex Jobs will be sent to Partnerlink through the existing JobShare format, or directly to the back-end TMSs.
* When planned, these jobs will be sent to {{#var:System}} through the existing interface in use for the existing partners, and will be identified with a new Job Group e.g. PALLEX. Note: This will require change to the sending process from the TMS system to accommodate this new job group.
* The jobs will be completed like any other normal delivery.
* When jobs are completed, the existing AutoExport functionality will update the Partners (identified through their Partner Codes) using a flat-file export of the job details in OBS Logistics' XML format, as it does with each existing partner.
* The AutoExport process will also export the files to Pall-Ex TWINE system, identified through the Job's Group and the configuration attached to it.
* The AutoExport functionality will store the success or failure of the export, along with any of the returned reasons from the export.

The Admin Export Configuration screen will be changed to allow the parameters for the new Pall-Ex extract to be specified against it.

The Partnerlink Import process will be modified to add a field to the import process to identify the Pallet System in use (for example, Palletforce, Pall-Ex, Fortec).

The new Pall-Ex Export process will work as follows:

At least 2 messages will be sent to update the Pall-Ex TWINE system, by connecting through three methods of their existing webservice:
* AddEpodPallet – One message sent per pallet on the consignment, to update a pallet and consignment with delivery and signatory information.
* AddEpodConsignment – One message sent per cancelled consignment, to update the consignment as cancelled delivery, with an appropriate reason code. {{Warning}} It is possible that the TMS systems may not be able to accurately identify the actual Pall-Ex pallet identity for the individual pallets. In this case (decided at functional specification stage), the process may be amended to always use this webservice to confirm the consignment as delivered rather than the above AddEpodPallet webservice.
* AddMPodImage – to upload the signature image from the delivery to the consignment.
The process will check the responses of sending these messages to the webservice, and will store the results in the Audit tables within {{#var:System}}. Messages that process in error will be marked as such, so that they may be identified and reprocessed manually if required.

== Scope ==
Assumptions:
* Jobs will be sent to Partnerlink and through to {{#var:System}} using the existing JobShare interfaces.
* Pallets for these Pallet Networks will be labelled with their own network's pallet labels, and not Partnerlink labels, like PalletForce. It is expected that pallets will be created by {{#var:System}} in the normal way, identifying the individual pallets by assigning each pallet a unique ID, counting from the 1 to the total number of pallets.
* The new partners will accept updates into their Transport systems from {{#var:System}} in the standard OBS format - the pallet network system will be updated separately. This will require a modification to identify consignments as being completed for Pall-Ex.
* The Consignment will already exist within the Pall-Ex TWINE system, ready for updating with POD information from {{#var:System}}.
* AE Parker will be assigned a Partner Code by Partnerlink, which will be provided to OBS Logistics prior to implementation of this change.

Changes will be made to latest version of {{#var:System}} only, and will require an update to all application components and full system and user acceptance testing.

This process is dependent on multiple reason codes for pallet networks change, specified in EST 318572 PART Job Group Level Clausing - No Duplicates. The work for this change must be completed before or as part of this change.

The reason codes used by Pall-Ex are not currently used in the Partnerlink system (2 character numeric values from 01 to 19), so these will not cause any contention in the system. It has been confirmed that

This process is dependent on jobs being received into {{#var:System}} through the standard Partnerlink interface, changes to which have been specified in FS 326965 Partnerlink EPOD Interface. This change to the inbound interface may require changes to the Partner TMS systems to allow the new fields to be specified. The changes for this have been specified here for completeness. Note that no changes will be necessary to Partner TMS systems if those systems are used solely by partners that do not complete Pall-Ex jobs or have no requirement to specify linked (consolidated) jobs.

Additionally, jobs will be exported through the standard interface (also specified in the same document). As the latest version of the system is being used for the basis of this change, this may require changes to the partner TMS systems to extract the information in the new format. Note that only new fields have been added - fields have not been changed for purpose or function.

{{Note}} This change requires integration with another system, so up to 1 day has been added to the specification and testing time to allow for this. If the specification time increases beyond this time allowed due to additional work required during this stage, the estimate will be increased to cover the actual time taken.



= Set-up =

== Pre-requisites ==

== Menu Structure ==

== Data ==
{{Warning}}
* New Partner Codes - New Site Configurations
* New Pall-Ex job group configuration
* New Export configuration



= Functional Description =

== Admin ==

== Auto-Import ==

== Auto-Export ==
{{Warning}} Generic changes to autoexport

=== New Pall-Ex Auto-Export Process ===
{{Warning}} Assuming we will have to do consignment level debriefing, as the pallet level webservice may not be working, and we may not have the Pall-Ex pallet IDs or know the format, and we may not get the information from Mandata anyway.



= Appendix A: TEST PLAN =

{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=description of what is to be achieved
|MenuAccess=Where on the menus the item can be found
|Prerequisites=The prerequisites of the test
|Objective=The details of what each group of tests is to achieve
}}
{{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Area being tested in this cycle
|Notes=Any notes or prerequisites for the tests following.
}}  {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=The actions to follow
|Result=The expected result
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=The actions to follow
|Result=The expected result
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=The actions to follow
|Result=The expected result
|Remarks=
|PassFail=
}} {{TestPlan_CycleFooter}}


{{Doc_Appendix
|Appendix=B
|Estimate=Y
|Glossary=EPOD
|Ref1=[[EST 324096 Pall-Ex Interface]]
|RefV1=1.0
|RefDate1=30/03/2015
|Ref2=[[FS 318572 PART Job Group Level Clausing]]
|RefV2=1.0
|RefDate2=08/04/2015
|Ref2=[[FS 326965 Partnerlink EPOD Interface]]
|RefV2=1.0
|RefDate2=22/05/2015
|REQ=0
|EST=1.25
|FS=2.0
|TS=1.5
|DEV=7.75
|ST=1.5
|IMP=1
|PM=1
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=Y
|Rev1=Matt Turner
|Rev1Title=OBSL Account Manager
|Rev2=John Davidson
|Rev2Title=Partnerlink Director
}}</div>
[[Category:{{#var:Client}} FS]]