FS 369101 UAT-67 Cage Confirmation Scans

From Calidus HUB






Aptean Logo.png







DHL

Cage Confirmation Scans

Functional Specification

5th February 2020 - 1.0
Reference: FS 369101 UAT-67















FUNCTIONAL OVERVIEW

Client Requirement

When pallet building at C3 consolidation centre users need to have an additional check to make sure the items are physically loaded to the correct pallet by scanning and confirming pallet ID. OBS advised this will be a change to add a validation making each item scanned require a positive scan on the cage/pallet label.


Solution Overview

The MCS pallet building process will be made configurable by location (i.e. RDC) to force confirmation of the pallet after every scan.

This is expected to be enabled for Cherwell 3 (the consolidation centre) but not for the warehouses (i.e. Cherwell 1), which will continue with the process as now.


Scope

This change will be applied to system version 2 of C-MCS linking to system version 11.35 on HCRTST and once approved will be promoted to HCRPRD.

This change to the functionality will be controlled by a new location parameter. This will default to disabled, to retain current system functionality. DHL operational and project staff are responsible for configuring the location to the new pallet building process.

This change mentions the label printing process, which is undergoing a slight change (under SCR 369080 MCS Scan Printer). This functionality is not being developed as part of this change and will be developed separately.


Impact

As decided by the customer. At locations where the customer chooses to enable this functionality, the users will be required to scan a package and a pallet in combination for every package that is palletised through MCS Pallet Building.


CONFIGURATION SET-UP

Pre-requisites

C-MCS must be configured and connected to a configured C-TMS system.


Menu Structure

N/A


Data

At each location that requires it, the MCS Configuration must be changed so that the flag "Pallet Building Process" is set to "Single" (the new process) from the default "Continuous" value.

FS 369101 Location.PNG

Figure 1: Locations maintenance - MCS tab


It is expected that this will be configured only at the DHLCHER3 location. However, the operation or project team could enable this at any location if they desire.


Implementation Advice

None


FUNCTIONAL DESCRIPTION

Locations Maintenance

The C-TMS Locations Maintenance form will be modified to add a new drop-down list, labelled as "Pallet Building Process". This will default to the value "Continuous".

FS 369101 Location.PNG

Figure 2: Locations maintenance - MCS tab


MCS Pallet Building

The Cherwell 1 Pallet Building process is expected to continue with the normal process, as follows:

  • The user will select the Pallet Building option.
  • The user will scan a package.
  • MCS will display the package details and suggest any pallets.
  • If an open pallet is suitable, the user can scan the pallet label in the Pallet text box, and MCS will confirm that the package is on this pallet.
  • If no open pallets are available and suggested, the user can create a new pallet with the New Pallet button.
  • When pressed, MCS will prompt them to scan a new pre-printed pallet label. When confirmed, MCS will confirm that the package is on this pallet.
  • MCS will stick to this pallet.
  • MCS will prompt to scan a package again.
  • When scanned, the package will be automatically added to the current pallet.
  • To change pallets, the user will be able to click the Change Pallet button.


  • Pallet Building - start

    Pallet Building - start

  • Package scanned, pallets suggested

    Package scanned, pallets suggested

  • Pallet confirmed, stuck to pallet

    Pallet confirmed, stuck to pallet

Figure 3: Cherwell 1 Pallet Building process


The Cherwell 3 Pallet Building process will be configured to use the new process, as follows:

  • The user will select the Pallet Building option.
  • The user will scan a package.
  • MCS will display the package details and suggest any pallets.
  • If an open pallet is suitable, the user can scan the pallet label in the Pallet text box, and MCS will confirm that the package is on this pallet.
  • If no open pallets are available and suggested, the user can create a new pallet with the New Pallet button.
  • When pressed, MCS will prompt them to select a printer. Note Note: This printer selection process is being changed under SCR 369080. When selected and confirmed, MCS will print the pallet label to the printer and will confirm that the package is on this pallet.
  • MCS will not stick to this pallet - it will be blanked.
  • MCS will prompt to scan a package again.
  • From this point, the user will work through the same process each time, as from the second step above.
  • Pallet Building - start

    Pallet Building - start

  • Package scanned, pallets suggested

    Package scanned, pallets suggested

  • Pallet confirmed, not stuck to pallet

    Pallet confirmed, not stuck to pallet

Figure 4: Cherwell 3 Pallet Building process


TECHNICAL NOTES

Modules Changed

Module Name Module Type Notes
LOCATION.fmb C-TMS Form  
DP_MCS C-TMS Package  
V_MCS_SITE C-TMS View  
(As required) SQL Database modification script.
VMcsSiteDAL1.cs MCS Server code  
VMcsSiteDAL1_Gen.cs MCS Server code  
VMcsSite1_Gen.cs MCS Server code  
McsDatabase.js MCS Device code  
m004a01t_uc_pallets.js MCS Device code  


Table Updates

Table GEO_LOCATION will change to add the following field:

Name Type Nullable Default Storage Comments
MCS_PALLET_BUILD_PROCESS VARCHAR2(1) N N    


Developer Notes

To achieve this, we must make the following changes:

  • New Location configuration required (i.e. applicable for C3, not C1). "Pallet Building Process", values "Continuous" (default) or "Single" (new process).
    • Modify C-TMS Location form MCS tab.
    • Modify DB table
    • Modify V_MCS_SITE
    • Modify MCS to add the new flag.
  • In MCS Pallet Building:
    • After palletising a package, check the new location flag is "Single". If so, blank the package information and selected pallet and return to the package prompt.


C-TMS Database Changes

The existing view V_MCS_SITE will be modified to return new MCS location flag, as follows: 

CREATE OR REPLACE VIEW V_MCS_SITE AS
SELECT DEPOT SIT_DEPOT, LOCATION_ID SIT_LOCATION_ID, LOCATION_NAME SIT_LOCATION_NAME,
MCS_PRINT_PALLET_LABEL SIT_PALLET_LABEL, 
MCS_PALLET_CLOSURE SIT_PALLET_CLOSURE,
MCS_PALLET_SEAL_REQD SIT_PALLET_SEAL_REQD, 
MCS_TRANS_SHIP SIT_TRANS_SHIP,
MCS_PALLET_BUILD_PROCESS SIT_PALLET_BUILD_PROCESS,
NVL(UPDATED_DATE,CREATED_DATE) SIT_UPDATED_DATE
FROM GEO_LOCATION
WHERE DEPOT = 'RDC'
AND NVL(MCS_ACTIVE,'N') = 'Y'
ORDER BY LOCATION_ID

This change and the database table change will be added to a database modification script, to be used during implementation.


C-TMS Locations Form Changes

The C-TMS Locations Maintenance form will be modified to add a new drop-down list, labelled as "Pallet Building Process". This will default in the database to a value of "C".

The field will be added under the existing "Pallet Building Validation" field.

The drop-down list will be populated with the descriptions of the field values below:

  • "C" - Continuous (the default value).
  • "S" - Single.

The following existing fields will be moved to the right in a new column:

  • Set Trip Status at Receipt.
  • Set Trip Status at Despatch.


FS 369101 Location.PNG

Figure 5: Locations maintenance - MCS tab changes


MCS DAL Changes

At login, MCS must receive the location (depot) configuration flags from C-TMS.

  • SIT_PALLET_BUILD_PROCESS - this flag controls whether pallets built through C-MCS at this location will stick to a pallet (C), or will require pallet confirmation after each scan (S).

These will be received as part of the logon procedure.

The location configuration flags will be received on the list of depots received when calling V_MCS_SITE and will be stored on the local database in new fields. The new flag will be accessible under the MCS.App object directly i.e. MCS.App.SIT_PALLET_BUILD_PROCESS.


Affected code modules:

  • VMcsSiteDAL1.cs - add the new fields as XML tags.
  • VMcsSiteDAL1_Gen.cs - add the new flags to the read data.
  • VMcsSite1_Gen.cs - add the new fields.
  • McsDatabase.js - add the new flag.


MCS Pallet Building Screen

Pallet building package information to be changed to:

  • when package palletised, return to initial prompt, only if configured to do so.

The process will check MCS.App.SIT_PALLET_BUILD_PROCESS. If set to "C", it will work as now. If set to "S", it will:

  • Reset the selected pallet ID.
  • Reset the pallet ID field.
  • Clear the package display.
  • Return to the package prompt.

This will occur at the end of the following events:

  • On entering a valid pallet for a new package scan.
  • On creating a new pallet.

Function funAddItemToPalletCallback is usually called in response to adding packages to pallets, and currently resets the displayed items. Modifying this process should cover all eventualities.


Affected code modules:

  • m004a01t_uc_pallets.js


TEST PLAN

Test Script / Scenario ReferenceCage Confirmation ScansCall Number(s): 369101 UAT-67
Test Script / Scenario DescriptionConfirm pallet after each package in pallet building.PASS / ISSUES / FAIL
Menu AccessPallet Building 
Pre-requisitesA configured C-TMS and MCS.Tested By:
 
Test ObjectiveTest that; locations can be configured to confirm pallet after each package and; pallet building confirms the pallet after each package at configured locations only.Date:
 


Step Action Result Remarks P/F
1 C-TMS Location Form      
         
1.01 Check existing MCS-enabled locations, that the Pallet Building Process is set to "Continuous". All existing MCS-enabled locations have the value set to "Continuous" on the screen and "C" in the database.    
1.02 Change a location to Pallet Building Process "Single". Save and re-find. The location value should be saved as "S" and shown as "Single" in the Locations form.    


Step Action Result Remarks P/F
2 MCS Pallet Building      
  Ensure that there are two locations configured, one with Continuous process and one with Single process. Ensure that there are multiple packages on an order, planned through both locations.      
2.01 On a site configured to Single process, start pallet building and scan a package. The package details are displayed. Any suitable pallets are shown.    
2.02 Create a new pallet and confirm. The device shows a message that the package is on the pallet. The package details are blanked, the pallet is removed and the device is prompting for package again.    
2.03 Scan another package. The package details are displayed. Any suitable pallets are shown, including the new pallet.    
2.04 Enter the new pallet and confirm. The device shows a message that the package is on the pallet. The package details are blanked, the pallet is removed and the device is prompting for package again.    
2.05 On a site configured to Continuous process, start pallet building and scan a package. The package details are displayed. Any suitable pallets are shown.    
2.06 Create a new pallet and confirm. The device shows a message that the package is on the pallet. The package details are blanked, but the pallet remains. The device is prompting for package again.    
2.07 Scan another package. The device shows a message that the package is on the pallet. The package details are blanked, but the pallet remains. The device is prompting for package again.    


APPENDIX A: QUOTE & DOCUMENT HISTORY

Cost Details
Activity Estimate
No. of Days		 No. of Days Rate per Day (£) Cost (£ Exc. VAT)
Requirements 0.00 0.00 820 £0.00
Change Request Evaluation 0.25 0.25 0 £0.00
Functional Specification 1.00 1.00 820 £820.00
Technical Specification 0.00 0.00 820 £0.00
Development 4.25 4.25 790 £3,357.50
Testing and Release 2.00 2.00 790 £1,580.00
Implementation 0.50 0.50 820 £410.00
Project Management 0.50 0.50 830 £415.00
 
TOTAL 8.50 8.50   £6,582.50
Estimate excludes training, release to live and go live support.

References

Ref NoDocument Title & IDVersionDate
1SCR 369080 MCS Scan Printer1.024/01/2020


Glossary

Term or Acronym Meaning
AWB Airway Bill; a receipt of goods required by airline carriers. It also serves as the carriage contract between the carrier and the shipper.
C-MCS CALIDUS MCS, OBS Logistics Mobile Control System. See also MCS.
Carrier The carrier completing the trip. Can comprise any carrier configured in the system, but normally Home Fleet (usually a carrier per depot), 3rd-party carriers, supplier-/customer-own transport, own collection, etc.
Consolidating Centre A depot that takes delivery of goods from several origins and consolidates them for trunking to outbases (q.v.) or final delivery to destinations. See also Consolidation.
Consolidation In execution terms, this is the act of taking several jobs and combining them into a single execution job. This can be by several criteria but is broadly defined as: Same Location consolidation, where the delivery/collection points are identical; Linked Location, where the deliver/collection points have been configured to be seen as the same point within C-TMS and; Manual (Ad Hoc) Consolidation, where the driver decides that two jobs should be delivered/collected at the same time.

In general transport terms, this is the act of taking like product from several sources (originating depots, warehouses, orders) going to the same destination or on the same vehicle and placing them on a transportable media. See also containerisation.

Containerisation The action of taking items and placing them inside another item for tracking purposes. See also Asset.
Cost Centre A part of an organisation to which costs may be charged for accounting purposes. For C-TMS, this is used for accounting purposes, and also to generally configure the system.
C-TMS CALIDUS TMS, OBS Logistics' Transport Management System.
Cross-Dock Also a specific location at which product is exchanged.
Customer In 3PL terms, the customer on behalf of which the transport is being operated.
DDL Drop-down list - a series of pre-designated answers to a particular question on a device, rather than requiring the user to key the answer in in full.
Debrief Comprises 2 parts: Stop debrief, where actual arrival and departure times against a trip are entered; Order debrief, where actual product and item quantities are entered; Driver/Trip debrief, where additional information is captured from the driver relating to the trip.
Depot Any location that schedules and controls transport.
Despatch In transport terms, the process of loading and despatching items out of a depot. In this implementation, the process of loading and despatching is predominantly controlled by C-MCS (q.v.). See also Loading.
Driver Comprising drivers and crew assigned to a trip.
DU Distribution/Deliverable Unit - Pallet, Package, etc.; Also Asset, Asset Type.
Fixed Route In transport terms, a fixed route is a trip comprised of a series of fixed stops that are typically always visited. A C-TMS fixed route template (q.v.) can be used to create these.
Item A single item for delivery/collection. A general terms, distinct from the DU of the deliverable item e.g. Pallet, Package, etc.
Loading In transport terms, the process of loading and despatching items out of a depot. In this implementation, the process of loading and despatching is predominantly controlled by C-MCS (q.v.). See also Despatch.
Location In C-TMS terms, a trip comprises visits or drops to many locations. A location can be of many different types.
Location Types Usually one of: Depot, Customer, Delivery/Collection Location, Store, etc.
MCS Mobile Control System, an application to execute mobile tasks, as opposed to transport management tasks from a console. For OBS Logistics, transport depot mobile tasks are handles by CALIDUS MCS.
OMS Ref A unique transport movement ID, referring to a single transport movement request.
Optimisation Route building and optimisation of stops on a trip.
Order Equiv: OMS Ref; a transport movement.
Order Status The lifecycle of an order.
Outbase A depot whose purpose is to deliver to final delivery destination within a geographically-restricted subsection of the whole catchment area; also ROC.
Reason Codes Of many types: Adjustment, Non-conformance, Order.
Receipt In transport terms, the process of receiving and uploading items into a depot. In this implementation, the process of receipt and unloading is predominantly controlled by C-MCS (q.v.). See also Unloading.
Region; Postal Region Geographical Region.
Resources Drivers, Crew, Tractors, Vehicles, Trailers (q.v.).
Route A route is a fixed route that is repeated. A Trip is a unique trip, which may be created from a route.
ROC Regional Operating Centre; a depot whose purpose is to deliver to final delivery destination within a geographically-restricted subsection of the whole catchment area; also Outbase.
RPE Roll-pallet Equivalent - This is used to estimate volume and therefore capacity of vehicles within C-TMS.
Schedule A day's plan, usually consisting of 24 hours, not necessarily from midnight to midnight.
Shunt A trunk (q.v.) movement between depots using the trunk network, typically of a much shorter length than a trunk movement.
TLM Transport Logistics Manager
Tractor The driver cab, pulling the trailer.
Trailer The trailer carrying the goods. Can be several types.
Trans-Ship The process of receiving, cross-docking and despatching items within a depot, usually within a single transaction. In this implementation, this is the process at the ROC (q.v.).
Transport Transport operations.
Trip C-TMS: A selection of work to be completed, specifically a workload that lasts for an entire shift for a driver.
Trip Status The lifecycle of a trip.
Trunk A route between depots, transporting goods usually to be delivered from the destination depot, but any transfer of goods from the original receiving or originating depot in the network to the final delivery depot (the outbase).
Unloading The process of receiving and uploading items into a depot. In this implementation, the process of receipt and unloading is predominantly controlled by C-MCS (q.v.). See also Receiving.
Vehicle A generic term for the resource assigned to a trip. Can be tractor (q.v.), tractor plus trailer (q.v.), fixed vehicle (e.g. van). In C-TMS terms, the tractor ID is considered the vehicle ID, usually the registration.
Warehouse This is a depot in C-TMS that is seen to be a warehouse, or origin and storage point for product for delivery.


Authorised By


Julie Scott
OBS Project Manager
_____________________________

Paul Kurze
Customer Representative
_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=FS_369101_UAT-67_Cage_Confirmation_Scans&oldid=8394’