EST 318572 PART Job Group Level Clausing: Difference between revisions

From Calidus HUB
VisualWikitext
No edit summary
No edit summary
Line 5: Line 5:
|Supimix_Client_Reference= 
|Supimix_Client_Reference= 
|Supimix_Number=318572
|Supimix_Number=318572
|The_version_of_the_document=1.0
|The_version_of_the_document=0.1
|Your_Name=A N Walker
|Your_Name=A N Walker
|Supimix_PO_Reference= 
|Supimix_PO_Reference= 
Line 25: Line 25:


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.
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.
A new flag against each reason code will indicate whether this reason code is partner-specific or generic.


A new optional text item will also be added to allow the users to maintain an Export Reason Code, used when exporting completed jobs back to external systems.
{{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.}}
 
{{Note|Reason codes themselves must still be unique to the system - a reason code must not exist for one job group (for example a pallet network partner) and also for the Partners job group or Partnerlink global reason codes. If the same reason code is required across multiple job groups, the Export Reason code can be used to achieve this in the export file.}}




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 configured to be enabled for Partnerlink's system.
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 Pallet Network (for example 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.
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.




Line 43: Line 40:


When prompting for Clause Reason Codes at job confirmation, the device will check the settings to decide which clause reason codes to display:
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 Pallet Network job (e.g. in the Palletforce Job Group), the device will show only clause reason codes for this pallet network.
* 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 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.
* If this job is being operated on behalf of a different partner, the device will show only the generic Partnerlink clause reason codes.




All Export processes will be modified to check reason codes when exporting completed or cancelled jobs to the external systems - the processes will look up the reason code used on the job and substitute it for the Export Reason Code is one exists.
{{Note|All other reason codes (e.g. cancellation reason codes) will be unaffected by this change.}}
 
 
{{Note|All other reason codes (e.g. cancellation reason codes) are expected to be unaffected by this change, as the data for these reason codes will not be modified. However, if it is decided that this functionality is applicable across all reason codes, these may be configured to act in the same way as the clause reason codes.}}
{{Note|Although this modification will support multiple pallet network job codes, currently only Palletforce is in use within Partnerlink. If other pallet networks are added into this implementation, there may be more work required when importing jobs from JobShare, and exporting completed jobs out to the external pallet network systems.}}




Line 58: Line 51:


|Requirements_Days=0
|Requirements_Days=0
|Estimation_Days=1.25
|Estimation_Days=1
|Functional_Specification_Days=1.75
|Functional_Specification_Days=1.25
|Technical_Specification_Days=1.25
|Technical_Specification_Days=1
|Development_Days=5.75
|Development_Days=4.25
|Testing_and_Release_Days=1.75
|Testing_and_Release_Days=1.25
|Implementation_Days=.25
|Implementation_Days=.25
|Project_Management_Days=1.25
|Project_Management_Days=1
|Year=2015
|Year=2015
|Free_Of_Charge=N
|Free_Of_Charge=N
|Supimix_Client_Code=PART}}
|Supimix_Client_Code=PART}}

Revision as of 18:50, 29 January 2015

Aptean Logo.png
STATEMENT OF WORK
CHANGE REQUEST ESTIMATE
ClientPARTProjectDEVSitePART
Client Reference Aptean Reference318572Estimate Version0.1
Prepared ByA N WalkerEstimate Date16/01/15
Invoice Reference Priority3
Customer System Version1.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 or other Pallet Network 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 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 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 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.

Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=EST_318572_PART_Job_Group_Level_Clausing&oldid=1698’