FS 318572 PART Job Group Level Clausing
Partnerlink
Job Group Level Clausing
CALIDUS EPOD
8th April 2015 - 0.3
Reference: FS 318572
Contents
Functional Overview
Client Requirement
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".
Solution Overview
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 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.
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.
Scope
- This change will be made to the latest version of the CALIDUS EPOD system only.
- This change does not have provision for duplicate reason codes for Job Groups (i.e. Pallet Network Clause Codes) and/or Sites (i.e. Partner Clause codes). If this is required, further development will be required.
- This change does not affect any other reason codes other than Clause codes. If this is required, further development will be required.
Set-up
Pre-requisites
A working implementation of the CALIDUS EPOD system.
Menu Structure
None
Data
The new flag "Owner/Operator" should be enabled for all existing Partnerlink sites.
The new flag "Exclusive Reason Codes" should be enabled for all existing job groups.
All Job, Detail and Clause codes should be set up for all partners and job groups.
Examples of how the data may be configured:
| Site | Reason | Group | Specific | Notes |
|---|---|---|---|---|
| L01 | R1 | L01 | Y | Specific codes for partners |
| L01 | R3 | L01 | Y | " |
| L03 | R2 | L03 | Y | " |
| L03 | R3 | L03 | Y | " |
| L01 | G1 | N | Partnerlink/Generic codes | |
| L01 | G2 | N | " | |
| L03 | G1 | N | " | |
| L03 | G2 | N | " | |
| L01 | P1 | PALLET | Y | Pallet Group specific codes |
| L01 | P2 | PALLET | Y | |
| L01 | P3 | PALLET | Y | |
| L03 | P1 | PALLET | Y | |
| L03 | P2 | PALLET | Y | |
| L03 | P3 | PALLET | Y |
Functional Description
Server Modifications
The CALIDUS EPOD server will be modified to hold some additional flags and values against existing records:
Reason Codes:
The Reason Codes table will be modified to include the following:
- Job Group - optional data, to identify that the reason code is present specifically for the Job Group identified.
- Owner-Specific - A Y/N flag to indicate whether the reason code is specific to this owner or generic for every owner (the default value)
Site:
The Site-level configuration will be modified to add an "Owner Operator" flag to indicate whether the system as a whole operates as a shared network. The allowed values will be "Y" or "N" and will default to "N".
Job Group:
The Job Group configuration will be modified to add an "Exclusive Reason Codes" flag, to indicate whether this Job Group must only use its own Reason Codes (i.e. those reason codes explicitly indicated as belonging to this job group) rather than also allowing generic codes as well (i.e. where the reason code is marked as not Owner-specific).
These new values added to the data above will be sent to the CALIDUS EPOD Mobile Device application when the driver logs on to the system and will be used to ensure only the correct reason codes are displayed to the driver when completing jobs.
Admin Modifications
The CALIDUS EPOD Admin system will be modified to maintain the new fields above, as follows:
Site Maintenance
The Site Maintenance screen will be modified to add the new field "Owner Operator" to the Admin tab of the screen in the position indicated:
Site Maintenance Screen
This will be a check-box entry, defaulting to unchecked.
Job Group Maintenance
The Job Group Maintenance screen will be modified to add the new field "Exclusive Reason Codes" to the Admin tab of the screen in the position indicated:
Job Group Maintenance Screen
This will be a check-box entry, defaulting to unchecked.
Codes Maintenance
The Codes Maintenance screen will be modified to add the new fields below to the table when finding data:
- Job Group, titled as "Job Group"
- Owner-Specific, titled as "Specific"
Codes Maintenance Screen
No new functionality will be added to the search criteria.
When adding new codes (through the Add button) or amending existing codes (through the Select button against an existing row in the table), the pop-up entry screen will be modified to add the new fields on the screen for entry in the position identified below:
Codes Maintenance Screen - adding/amending
The fields will be added as below:
- "Job Group" - optional data, allowing the user to select any job group for the site in a drop-down list.
- "Owner-Specific" - A check box, defaulting to unchecked.
Mobile Device Modifications
The CALIDUS EPOD Mobile Device application will be modified to accept and store the new configuration and standing data maintained in the server, namely:
- Codes
- Site
- Job Group
This will be stored when the data is sent to the device at driver login.
The process that selects reason codes for display in the application will be modified to:
- Check the Site flag "Owner Operator". If enabled, the process will only select generic codes (i.e. Owner-specific is "N" against the codes) if the job owner does not match the partner operating the job (the site). If the owner is the same as the operator, all codes for the site will be selected, regardless of the owner-specific code flag.
- Check the Job Group flag "Exclusive Reason Codes". If enabled, the process will only select codes that match the Job Group for the job. Additionally, no generic codes will be allowed.
Examples of codes selected, referencing the examples in section Data above:
If L01 and doing a job owned by L01, the following reasons would be available to the driver:
- R1
- R3
- G1
- G2
If L01 is doing a job on behalf of another partner (e.g. L03) the following reason codes are available to the driver:
- G1
- G2
If L03 and doing a job owned by L03:
- R2
- R3
- G1
- G2
If L01 is doing a job on behalf of Palletforce or other pallet network:
- P1
- P2
- P3
Note that the generic codes will not be available to the Pallet Network jobs, as the PALLET job group will be defined as using only Exclusive (i.e. job group-specific) codes.
The Cancellation screen will be modified to pass in the Job and Job Group, so that the screen displays the correct reason codes for the job and job group when cancelling Jobs, Containers (Pallets) or Products.
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.
The Signature screen will also be modified so that, when Clausing pallets (by selecting from the list of pallets displayed from the newly-named "Clause" tab on this screen), the screen displays the correct Clause reason codes for the job and the job group for this pallet.
No other codes entry will be changed, so none are affected by this change.
Appendix A: Quote & Document References
| Cost Details | ||||
| Activity | Estimate No. of Days |
No. of Days | Rate per Day (£) | Cost (£ Exc. VAT) |
| Requirements | 0.00 | 0.00 | 650 | £0.00 |
| Change Request Evaluation | 1.25 | 1.25 | 650 | £812.50 |
| Functional Specification | 1.25 | 1.25 | 650 | £812.50 |
| Technical Specification | 1.00 | 1.00 | 650 | £650.00 |
| Development | 4.25 | 4.25 | 650 | £2,762.50 |
| Testing and Release | 1.25 | 1.25 | 650 | £812.50 |
| Implementation | 0.25 | 0.25 | 650 | £162.50 |
| Project Management | 1.00 | 1.00 | 650 | £650.00 |
| TOTAL | 10.25 | 10.25 | £6,662.50 | |
| Estimate excludes training, release to live and go live support. |
A.1 References
| Ref No | Document Title & ID | Version | Date |
| 1 | EST 318572 PART Job Group Level Clausing | 1.0 | 16/01/2015 |
A.2 Glossary
| Term | Definition |
|---|---|
| EPOD | Electronic Proof of Delivery. The OBS EPOD system is CALIDUS ePOD. |
| CALIDUS eSERV | The OBS mobile system to complete Service functionality in the field. This is part of the CALIDUS ePOD system. |
| PDA | The mobile device on which the C-ePOD system will run in the field. This can be a Phone, EDA or industrial PDA, running Android. |
| DAL | Data Access Layer. A mechanism for accessing data by the system that is removed from the application, allowing for simplified access and providing protection to the data, as only approved DAL methods can be used to modify it. |
| GPS | Global Positioning System. A mechanism of retrieving accurate positioning information in the form of Latitude and Longitude (Lat-Long) co-ordinates from a device. |
| GPRS, 3G, HSDPA, Data Service | All terms referring to mobile device network connectivity, and the speed at which the device connects to the internet. |
A.3 Authorised By
John Davidson | Partnerlink Representative | _____________________________ |
Murray Middleton | OBS Logistics Representative | _____________________________ |
