EST 318572 PART Job Group Level Clausing

STATEMENT OF WORK CHANGE REQUEST ESTIMATE

Client	PART	Project	DEV	Site	PART
Client Reference		Aptean Reference	318572	Estimate Version	0.1
Prepared By	A N Walker			Estimate Date	16/01/15
Invoice Reference				Priority	3
Customer				System Version	1.4

Client Request

New Clausing Requirement: 1. Clausing Reason Codes to be used on all job groups (applicable only to Palletforce currently as per log 314964) 2. Separate Reason codes will apply for 3 different Job Groups a Palletforce (Palletforce codes only) b Partnerlink (Delivery for a different Partner - Partnerlink agreed codes to be used only) c Partner (Owned and executed jobs to use own set of codes that link back to the Partner TMS). 3. Import change, need to split Partnerlink and Owned&executed jobs. 4. Can the TAB on the signature capture screen be changed from "Pallets" to "Clause".

Aptean Solution

The CALIDUS ePOD system will be modified as follows: The Reason Codes Maintenance screen will be modified to allow the users to maintain the Group for which the code entered is valid - this may be left blank to indicate codes that may be used for all jobs. A new flag against each reason code will indicate whether this reason code is partner-specific or generic. Note: Reason codes themselves must still be unique to the system - a reason code must not exist for the Palletforce job group and also for the Partners job group or Partnerlink reason codes. The Site maintenance screen will be modified to add a new configuration flag to control whether the system should check if there are different reason codes for owners and operators. This will be set up enabled for Partnerlink's system. The Job Group maintenance screen will be modified to add a new configuration flag to control whether reason codes for this Job Group are exclusive i.e. no generic Partnerlink codes may be used for jobs of this Job Group, only ones that have been specifically assigned to the Job Group. It is expected that the Palletforce job group will have this set. It is also possible that other Partner job groups will have this enabled, in case it is decided that the generic Partnerlink codes may not be used for jobs that are owned and operated by the same partner. In the examples contained in this estimate, I have assumed that the Partner Job Codes will allow the use of the generic codes as well as specific codes, although this configuration may be changed at any time. These new flags and Reason codes fields will be sent to the Android PDA application. When prompting for Clause Reason Codes at job confirmation, the device will check the settings to decide which clause reason codes to display: If this is a Palletforce job (i.e. in the Palletforce Job Group), the device will show only Palletforce clause reason codes. If this is a job owned and operated by the same partner, the device will show all generic Partnerlink clause reason codes, and also all clause reason codes specific to that partner. If this job is being operated on behalf of a different partner, the device will show only the generic Partnerlink clause reason codes. Note: All other reason codes (e.g. cancellation reason codes) will be unaffected by this change. The signature screen will be modified so that the title of the current Pallets tab will be displayed as "Clause" instead, only for the Partnerlink style.

Warning:

Unknown costs for client/year (PART/2015)

Cost Details
Activity	Hours	Rate per hour (£)	Cost (£ Exc. VAT)
Requirements	0.00	0.00	£0.00
Change Request Evaluation	1.00	0.00	£0.00
Functional Specification	1.25	0.00	£0.00
Technical Specification	1.00	0.00	£0.00
Development	4.25	0.00	£0.00
Testing and Release	1.25	0.00	£0.00
Implementation	0.25	0.00	£0.00
Project Management	1.00	0.00	£0.00
TOTAL	10.00		£0.00

Estimate excludes training, release to live and go live support.

Copyright © Aptean 2015. This estimate has an expiry date of 30 days from the specified Estimate Date. The information contained herein is supplied without liability for errors or omissions.