FS 281363 New CTMS Execution Screen: Difference between revisions

From Calidus HUB
VisualWikitext
No edit summary
 
(9 intermediate revisions by the same user not shown)
Line 4: Line 4:
{{#vardefine:System|''CALIDUS'' C-TMS}}
{{#vardefine:System|''CALIDUS'' C-TMS}}
{{#vardefine:Doc_Title|New C-TMS Execution Screen}}
{{#vardefine:Doc_Title|New C-TMS Execution Screen}}
{{#vardefine:Version|0.1}}
{{#vardefine:Version|0.2}}
{{#vardefine:Date|25th October 2011}}
{{#vardefine:Date|26th October 2011}}
{{#vardefine:Reference|281363}}
{{#vardefine:Reference|281363}}
</div>
</div>
Line 22: Line 22:


== Client Requirement  ==
== Client Requirement  ==
A new UI for a new Drivers Execution screen. Functionality required has been agreed between Tony Walker and Pete Crane, working from the One Network requirements document.


== Solution Overview  ==
== Solution Overview  ==
A new Execution screen will be created.
The screen will allow all of the functionality of the existing Trip Debrief screen, plus modifications to allow for:
*Extended ODO entry
*Driver Briefing
*Driver Exception Handling
The screen will be optimised for each trip status, showing the user the necessary data entries for each step, depending on the status of the order.
Extensive use of popups will be used to ensure that the entry of the data is a seamless as possible, directing the user to enter the data in as close a way to the operational requirement as possible.
An increased auditing level will be added, as well as Load ID visibility, to allow users to see how the new functionality would integrate into the existing process.
The styling of the product will approach DHL standards and colour schemes, to show the styling capability of the new product UI.


== Scope  ==
== Scope  ==
This is a prototype, showing the capability. There is a simplified database in use in the back-end, with demonstration data. It is unlikely that updating data will be required but, where possible, the prototype will incorporate this.


<!-- NEW PAGE -->  
<!-- NEW PAGE -->


= Set-up  =
= Set-up  =
Line 53: Line 69:
==Planned==
==Planned==
Entry button to show status of trip, allowing change to next status only.
Entry button to show status of trip, allowing change to next status only.
Re-plan and Add Stop links will be available from this point, to call additional screens (not part of prototype).


If change to next status, check that the General information has been entered – if not, popup validation forcing entry as below.
If change to next status, check that the General information has been entered – if not, popup validation forcing entry as below.
In all tabs, when changing to next status, write Audit log entry and link to appropriate levels. See auditing later for details.
At this stage, write an audit entry and link to Trip, Tractor, Driver.


Accordion panel, general is displayed.
Accordion panel, general is displayed.
Line 60: Line 82:
Accordion Panel contains tab panel with General information:
Accordion Panel contains tab panel with General information:
*Line 1
*Line 1
**Trip Ref – display
**Trip Ref - display
**Carrier – display only
**Carrier - display only
**Del Type – display only
**Del Type - display only
**Owning Depot – display only
**Owning Depot - display only
*Line 2
*Line 2
**Vehicle – entry with DDL
**Vehicle - entry with DDL
**Driver – entry with DDL
**Driver - entry with DDL
**Button to enter crew if desired. If crew entered, display immediately.
**Button to enter crew if desired. If crew entered, display immediately.
**Crew 1 – entry with DDL
**Crew 1 - entry with DDL
**Crew 2 – ditto
**Crew 2 - ditto
*Line 3
*Line 3
**Button to enter instructions. If instructions entered, display immediately.
**Button to enter instructions. If instructions entered, display immediately.
Line 85: Line 107:
*Cust Ref
*Cust Ref
*Planned qty, weight and Volume
*Planned qty, weight and Volume
*Load Number
*Load Number (a link to a Load screen - see later)
All display only
All display only


Line 91: Line 113:
*Stop #
*Stop #
*Planned arrival and depart date and time,
*Planned arrival and depart date and time,
*Actual arrival and depart date and time.
*Type (Collection or Delivery)
*Type (Collection or Delivery)
*Location
*Location
*Distance - cumulative
*Distance - cumulative
*Drive Mins - cumulative
*Drive Mins - cumulative
*Trailer Type – Same for all stops
*Trailer Type - Same for all stops
*Trailer ID  – Same for all stops
*Trailer ID  - Same for all stops
*Activities – blank  
*Activities - blank  


All display only
All display only


==Accepted==
==Accepted==
Re-plan and Add Stop links will be available from this point, to call additional screens (not part of prototype).
Entry button to show status of trip, allowing change to next status only.
Entry button to show status of trip, allowing change to next status only.
At this stage, write an audit entry and link to Trip, Driver.


If change to next status, check that the Driver Brief information has been entered – if not, popup validation forcing entry as below.
If change to next status, check that the Driver Brief and Despatched Quantities information has been entered - if not, popup validation forcing entry as below (automatically switching between tabs/accordions as necessary.


Accordion display
Accordion display
Line 128: Line 152:
Saving this will prompt the user to change the status to En Route.
Saving this will prompt the user to change the status to En Route.


Accordion Panel (closed) with ability to see order details grid as above, plus Despatched quantities:
*Stop
*Load Location
*Stop
*Unload location
*Cust Ref
*Planned and despatched qty, weight and Volume, UOMs together
*Load Number
Despatched quantities must be entered.
Button under despatched quantities to allow all to be set to planned quantities (if not already entered).
Save button.
Panel (not part of accordion) with Grid of Stops under tab panel as above.


==En Route==
Re-plan and Add Stop links will be available from this point, to call additional screens (not part of prototype).


Entry button to show status of trip, allowing change to next status only.
History link will be available from this point, to call a separate screen with the Trip ID as a parameter.
If change to next status, check that the Order Quantities and Trip Times have all been been entered - if not, popup validation forcing entry as below. Also needs to check that at least a Start and End ODO have been entered.
At this stage, write an audit entry and link to Trip, Tractor, Driver.
Accordion display
First accordion panel (closed), three tabs, General, Driver Brief (from above) then:
Driver ODO:
*Grid showing
*Date
*Time
*Type (Start/End/Fuel)
*Mileage
*Fuel Drawn
Save button
Can add records at any time for any type.
At this stage, write an audit entry and link to Trip, Tractor, Driver.
Second accordion panel (open) with ability to see order details grid as above, plus Delivered quantities:
*Stop
*Load Location
*Stop
*Unload location
*Cust Ref
*Planned, despatched and Delivered qty, weight and Volume, UOMs together
*Reason Code
*Load Number
Delivered quantities must be entered.
If the delivered quantity entered does not match the Despatched quantities, a Reason code must be entered. Do this through a Popup, allowing entry of reason code and displaying description. A comment box should also be allowed.
A Trip audit should be written if this is the case.
Button under delivered quantities to allow all to be set to despatched quantities (if not already entered).
Panel (not part of accordion) with Grid of Stops under tab panel as above.
Also add:
*Actual arrival and depart date and time.
*ETA arrival date and time.
*Actual Distance - entered
*Actual Time - calculated
Actual arrival and depart date and time and actual distance for each stop can be entered.
Only the first row's data can be entered initially.
On entry of first stop's actual arrival/depart date and time, check whether delivered quantities entered for all orders to that stop. If not, pop open an entry grid for the orders only, forcing entry of quantities and reason code as above. When entered and saved, update the orders panel above.
Also at this stage, check the arrival time against the delivery window against the orders associated to the stop. If the arrival time is outside the window associated to the order(s), pop up a window showing the orders affected and prompt to enter a reason code as before. This reason should be applied to all affected orders. A Trip Audit should be written if this is the case.
Once first entered, can save - that's OK.
At this stage, write an audit entry and link to Trip, Tractor, Driver.
The user can then continue entering against the following stops one by one.
ETA dates and times will be forecast from outside the system. If they are available, the system needs to RAG-colour the ETA fields:
*If the ETA against a stop is later than the delivery window of any orders associated to that stop, the background should be coloured red.
*Otherwise, the background should be coloured green.
Furthermore, the following stops should then be checked based on the new calculated ETA depart and planned drive time against the stop, to predict an ETA against these lines. The same check should be performed against these following trips. If any of these further calculated ETAs are outside the delivery window of any orders associated to the stop, the ETA fields should be coloured Amber.
Clicking on a Red-coloured ETA field should pop up a window allowing the user to email all affected customers with their new ETA.
Button under Actual Dates/Times to set to Planned (if not already set)
When all quantities and dates entered, prompt user whether they want to change status to Completed.
==Completed==
Entry button to show status of trip, allowing change to next status only.
History link will be available from this point, to call a separate screen with the Trip ID as a parameter.
If change to next status, check that the Driver Debrief information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs/accordions/popups as necessary.
At this stage, write an audit entry and link to Trip, Driver.
Accordion display
First accordion panel (open), four tabs, General, Driver Brief, Driver ODO (from above) then:
Driver Debrief tab:
Checklist of items:
*Ops 13 Carried out
*Defect Found
*Tick Vosa Checked Vehicle
*Update Fleet Compliance Check List
*Button to show Driver Discrepancies
*Checkbox to show discrepancies dealt with
*Shift End Time entry
Save button
Driver Discrepancies pops up a window showing:
All numbered discrepancies (late arrivals, departures, delivered quantity changes) in a grid.
A comment should be allowed to be added per discrepancy.
Save button
When all data entered, ask user whether they want the status to go to Debriefed.
==Debriefed==
Entry button to show status of trip, allowing change to next status only.
History link will be available from this point, to call a separate screen with the Trip ID as a parameter.
If change to next status, check that the POD information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs/accordions/popups as necessary.
At this stage, write an audit entry and link to Trip.
Accordion display
As above, with Orders panel (shown) allowing entry of POD at end of grid - all other items display only.
The POD entry will consist of a series of check boxes against the grid, with a button under to set all as received. If the POD is set, provide a button/icon to view the POD through a popup.
Trips panel can now be closed as part of the accordion.
==Confirmed==
History link will be available from this point, to call a separate screen with the Trip ID as a parameter.
Accordion display
As above, but with Finance tab (part of general accordion) shown:
Show grand total of payments and button to add new payments.
Trips panel closed as part of the accordion.
=Audit Screen=
Audit records are written at one of three levels (Trip, Tractor, Driver) at various stages in the process above.
This screen reports on them.
Screen accepts parameters of Trip, Trailer or Driver.
For Trip - display all records found.
Any others, limit to 20 to a page.
For Trip, get Audit Type records of Trip for the supplied Trip ID.
For Tractor, get Audit Type records of Tractor for the supplied Tractor ID
For Driver, get Audit Type records of Trip for the supplied Driver.
The page should display the information in the audit record, plus links for whatever other levels this audit record links to.
So, we have the following:
Audit 1, with information "Driver Briefed" is linked to the Trip ID and the Driver ID
Audit 2, with information "Trip En-Route" is linked to the Trip ID, Tractor ID and Trailer ID.
etc.
If we search for the Trip ID, we will return both audit records.
If we search for the Tractor ID, we will get only audit 2.
If the user clicks a link against an audit, call the same screen with the new parameter.
There should be a capability to click an audit record and see all the details, showing comments entered against the audit, and an ability to add more comments.
=Load Screen=
This screen shows all orders associated to the load ID passed in.


<!-- NEW PAGE -->  
<!-- NEW PAGE -->  
{{Doc_Appendix
{{Doc_Appendix
|Appendix=A
|Appendix=A

Latest revision as of 12:07, 26 October 2011




Aptean Logo.png







OBS Logistics Ltd

New C-TMS Execution Screen

CALIDUS C-TMS

26th October 2011 - 0.2
Reference: FS 281363











































Functional Overview

Client Requirement

A new UI for a new Drivers Execution screen. Functionality required has been agreed between Tony Walker and Pete Crane, working from the One Network requirements document.

Solution Overview

A new Execution screen will be created.

The screen will allow all of the functionality of the existing Trip Debrief screen, plus modifications to allow for:

  • Extended ODO entry
  • Driver Briefing
  • Driver Exception Handling

The screen will be optimised for each trip status, showing the user the necessary data entries for each step, depending on the status of the order.

Extensive use of popups will be used to ensure that the entry of the data is a seamless as possible, directing the user to enter the data in as close a way to the operational requirement as possible.

An increased auditing level will be added, as well as Load ID visibility, to allow users to see how the new functionality would integrate into the existing process.

The styling of the product will approach DHL standards and colour schemes, to show the styling capability of the new product UI.

Scope

This is a prototype, showing the capability. There is a simplified database in use in the back-end, with demonstration data. It is unlikely that updating data will be required but, where possible, the prototype will incorporate this.


Set-up

Pre-requisites

Menu Structure

Data

C-TMS Execution Screen

Screen requests Schedule and Trip as it does now. Trip should be allowed entry through autocomplete if no schedule has been selected (fuzzy match on trip ID).

Selecting a trip displays panels based on the status of the trip:

  • Planned
  • Accepted
  • En Route
  • Complete
  • Debriefed
  • Confirmed

Planned

Entry button to show status of trip, allowing change to next status only.

Re-plan and Add Stop links will be available from this point, to call additional screens (not part of prototype).

If change to next status, check that the General information has been entered – if not, popup validation forcing entry as below.

In all tabs, when changing to next status, write Audit log entry and link to appropriate levels. See auditing later for details.

At this stage, write an audit entry and link to Trip, Tractor, Driver.

Accordion panel, general is displayed.

Accordion Panel contains tab panel with General information:

  • Line 1
    • Trip Ref - display
    • Carrier - display only
    • Del Type - display only
    • Owning Depot - display only
  • Line 2
    • Vehicle - entry with DDL
    • Driver - entry with DDL
    • Button to enter crew if desired. If crew entered, display immediately.
    • Crew 1 - entry with DDL
    • Crew 2 - ditto
  • Line 3
    • Button to enter instructions. If instructions entered, display immediately.
  • Save button.

User must enter Vehicle and Driver (faint colour on entry box background). Crew and instructions are optional.

Saving this will prompt the user to change status to Accepted.

Accordion Panel (closed) with ability to see order details grid:

  • Stop
  • Load Location
  • Stop
  • Unload location
  • Cust Ref
  • Planned qty, weight and Volume
  • Load Number (a link to a Load screen - see later)

All display only

Panel (not part of accordion) with Grid of Stops under tab panel, showing:

  • Stop #
  • Planned arrival and depart date and time,
  • Type (Collection or Delivery)
  • Location
  • Distance - cumulative
  • Drive Mins - cumulative
  • Trailer Type - Same for all stops
  • Trailer ID - Same for all stops
  • Activities - blank

All display only

Accepted

Re-plan and Add Stop links will be available from this point, to call additional screens (not part of prototype).

Entry button to show status of trip, allowing change to next status only. At this stage, write an audit entry and link to Trip, Driver.

If change to next status, check that the Driver Brief and Despatched Quantities information has been entered - if not, popup validation forcing entry as below (automatically switching between tabs/accordions as necessary.

Accordion display First accordion panel, two tabs, general (from above) then

Driver Brief panel (open)

Some questions with tick box and entry:

  • Keys given to driver
  • Advise of route and vehicle
  • Advise of TLC drops of Traffic Issues
  • Check Driving License
  • Enter shift start time - time entry only.
  • Ops 13 checks carried out

All are required.

Save button.

User must enter all values. Validation popups if not entered.

Saving this will prompt the user to change the status to En Route.

Accordion Panel (closed) with ability to see order details grid as above, plus Despatched quantities:

  • Stop
  • Load Location
  • Stop
  • Unload location
  • Cust Ref
  • Planned and despatched qty, weight and Volume, UOMs together
  • Load Number

Despatched quantities must be entered.

Button under despatched quantities to allow all to be set to planned quantities (if not already entered).

Save button.

Panel (not part of accordion) with Grid of Stops under tab panel as above.

En Route

Re-plan and Add Stop links will be available from this point, to call additional screens (not part of prototype).

Entry button to show status of trip, allowing change to next status only.

History link will be available from this point, to call a separate screen with the Trip ID as a parameter.

If change to next status, check that the Order Quantities and Trip Times have all been been entered - if not, popup validation forcing entry as below. Also needs to check that at least a Start and End ODO have been entered.

At this stage, write an audit entry and link to Trip, Tractor, Driver.

Accordion display First accordion panel (closed), three tabs, General, Driver Brief (from above) then: Driver ODO:

  • Grid showing
  • Date
  • Time
  • Type (Start/End/Fuel)
  • Mileage
  • Fuel Drawn

Save button

Can add records at any time for any type. At this stage, write an audit entry and link to Trip, Tractor, Driver.

Second accordion panel (open) with ability to see order details grid as above, plus Delivered quantities:

  • Stop
  • Load Location
  • Stop
  • Unload location
  • Cust Ref
  • Planned, despatched and Delivered qty, weight and Volume, UOMs together
  • Reason Code
  • Load Number

Delivered quantities must be entered. If the delivered quantity entered does not match the Despatched quantities, a Reason code must be entered. Do this through a Popup, allowing entry of reason code and displaying description. A comment box should also be allowed. A Trip audit should be written if this is the case.

Button under delivered quantities to allow all to be set to despatched quantities (if not already entered).

Panel (not part of accordion) with Grid of Stops under tab panel as above. Also add:

  • Actual arrival and depart date and time.
  • ETA arrival date and time.
  • Actual Distance - entered
  • Actual Time - calculated

Actual arrival and depart date and time and actual distance for each stop can be entered. Only the first row's data can be entered initially.

On entry of first stop's actual arrival/depart date and time, check whether delivered quantities entered for all orders to that stop. If not, pop open an entry grid for the orders only, forcing entry of quantities and reason code as above. When entered and saved, update the orders panel above.

Also at this stage, check the arrival time against the delivery window against the orders associated to the stop. If the arrival time is outside the window associated to the order(s), pop up a window showing the orders affected and prompt to enter a reason code as before. This reason should be applied to all affected orders. A Trip Audit should be written if this is the case.

Once first entered, can save - that's OK. At this stage, write an audit entry and link to Trip, Tractor, Driver.

The user can then continue entering against the following stops one by one.

ETA dates and times will be forecast from outside the system. If they are available, the system needs to RAG-colour the ETA fields:

  • If the ETA against a stop is later than the delivery window of any orders associated to that stop, the background should be coloured red.
  • Otherwise, the background should be coloured green.

Furthermore, the following stops should then be checked based on the new calculated ETA depart and planned drive time against the stop, to predict an ETA against these lines. The same check should be performed against these following trips. If any of these further calculated ETAs are outside the delivery window of any orders associated to the stop, the ETA fields should be coloured Amber.

Clicking on a Red-coloured ETA field should pop up a window allowing the user to email all affected customers with their new ETA.

Button under Actual Dates/Times to set to Planned (if not already set)

When all quantities and dates entered, prompt user whether they want to change status to Completed.

Completed

Entry button to show status of trip, allowing change to next status only.

History link will be available from this point, to call a separate screen with the Trip ID as a parameter.

If change to next status, check that the Driver Debrief information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs/accordions/popups as necessary. At this stage, write an audit entry and link to Trip, Driver.

Accordion display First accordion panel (open), four tabs, General, Driver Brief, Driver ODO (from above) then:

Driver Debrief tab: Checklist of items:

  • Ops 13 Carried out
  • Defect Found
  • Tick Vosa Checked Vehicle
  • Update Fleet Compliance Check List
  • Button to show Driver Discrepancies
  • Checkbox to show discrepancies dealt with
  • Shift End Time entry

Save button

Driver Discrepancies pops up a window showing:

All numbered discrepancies (late arrivals, departures, delivered quantity changes) in a grid.

A comment should be allowed to be added per discrepancy.

Save button

When all data entered, ask user whether they want the status to go to Debriefed.

Debriefed

Entry button to show status of trip, allowing change to next status only.

History link will be available from this point, to call a separate screen with the Trip ID as a parameter.

If change to next status, check that the POD information has been entered – if not, popup validation forcing entry as below (automatically switching between tabs/accordions/popups as necessary. At this stage, write an audit entry and link to Trip.

Accordion display

As above, with Orders panel (shown) allowing entry of POD at end of grid - all other items display only.

The POD entry will consist of a series of check boxes against the grid, with a button under to set all as received. If the POD is set, provide a button/icon to view the POD through a popup.


Trips panel can now be closed as part of the accordion.

Confirmed

History link will be available from this point, to call a separate screen with the Trip ID as a parameter.

Accordion display

As above, but with Finance tab (part of general accordion) shown: Show grand total of payments and button to add new payments.

Trips panel closed as part of the accordion.

Audit Screen

Audit records are written at one of three levels (Trip, Tractor, Driver) at various stages in the process above. This screen reports on them.

Screen accepts parameters of Trip, Trailer or Driver.

For Trip - display all records found. Any others, limit to 20 to a page.

For Trip, get Audit Type records of Trip for the supplied Trip ID. For Tractor, get Audit Type records of Tractor for the supplied Tractor ID For Driver, get Audit Type records of Trip for the supplied Driver.

The page should display the information in the audit record, plus links for whatever other levels this audit record links to.

So, we have the following:

Audit 1, with information "Driver Briefed" is linked to the Trip ID and the Driver ID

Audit 2, with information "Trip En-Route" is linked to the Trip ID, Tractor ID and Trailer ID.

etc.

If we search for the Trip ID, we will return both audit records.

If we search for the Tractor ID, we will get only audit 2.

If the user clicks a link against an audit, call the same screen with the new parameter.

There should be a capability to click an audit record and see all the details, showing comments entered against the audit, and an ability to add more comments.

Load Screen

This screen shows all orders associated to the load ID passed in.


Appendix A: Document References

A.1 References

Ref NoDocument Title & IDVersionDate
1Reference10.101/01/2011


A.2 Glossary

Term or Acronym Meaning
Ad Hoc A task instigated on the device (spec. Ad Hoc Pallet Move), rather than a task instigated from the WMS and Stock Control.
Advice Note Number An external reference linked to a Goods Receipt.
Aisle A component of a location; usually a space through rows of racking or storage locations; a collection of locations;
Anchor Point A starting location for a search for a suitable storage location; auto-putaway location suggestion start point.
Area A collection of aisles; an area in the warehouse for a particular purpose.
Batch A production batch of a product; a quantity of product that is considered to have the same characteristics;
Bay (Warehouse) A physical loading or unloading point for the warehouse.
Bay A component of a location; usually a space between uprights in racking, comprising several levels (horizontal beams).
Block Stack A stable stack of pallets.
Bulk Bulk storage; Usually full-pallet storage areas, racked or stacked.
Cancellation The facility to cancel a task due to some problem, identified by the user when performing the task.
Check Digit A short code, usually randomly generated and stored against a location, used to help identify that a user is at the right location before they proceed with a warehouse task.
CSV Character-separated values; a text file with multiple rows and values, usually separated with commas.
C-WCS CALIDUS WCS, the name of the OBS Logistics Warehouse Control system
C-WMS CALIDUS WMS, the name of the OBS Logistics Warehouse Management system
Dead Leg A movement of a truck without a pallet; wasted resource.
Despatch The final physical stage of an order; handover of goods to the haulier.
Drive-In A drive-in location, typically multi-level, multi-deep location.
Dual Cycling Processes utilizing P&D locations for interleaving tasks in and out of specific areas, reducing dead leg movements.
Exchange Specifically Pick Exchange or Task Exchange. The process of allowing a user to select a different pallet in a multi-pallet location and exchanging the expected pallet for this one. If the pallet is planned for another task, task exchange will complete this task instead of the expected one first. If the pallet is not planned, pallet exchange will swap the pallet (if suitable).
GR; GRN Goods Receipt; Goods Receipt Number or Note
High Bay Typically tall (greater than 5 level) racking, usually full pallet storage, usually Narrow Aisle.
JIT Just In Time; processes designed to trigger at the last instant.
KPI Key Performance Indicator.
Level A component of a location; usually the vertical compartments of an area, delineated by horizontal beams.
Loading The act of loading pallets onto a vehicle.
Location A uniquely identified space in the warehouse for storage of product. There are many types, most commonly Floor locations (for example, Marshalling, Inbound), Racking or Bulk Storage Locations and Pick faces.
Manifest The contents of a vehicle or container.
Marshalling The act of bringing pallets for an order or load together; an area to do so.
Multi-deep A location with 2 or more pallets stored sequentially i.e. only one can be accessed at a time.
NA Narrow Aisle; usually any area in the warehouse that is restricted access due to space limitations, Narrow Aisles have associate P&D locations.
P&D Pick-up and Drop-off locations; locations used to control the handover of pallets between distinct areas, for example between chambers and the wider area of the warehouse.
PI; Perpetual Inventory The act of continuously checking locations in a warehouse, identifying and correcting product quantity issues. Usually used in Bulk environments rather than Pick Faces. In pick faces, this process is called is called Residual Stock Balance and usually takes place after picking from a pick face.
Pick Face A location designed for picking part of a pallet of stock. Usually a low- or ground-level location.
Pick List (order) The instructions to pick pallets or cases from locations; the paper report associated to this; the stage of preparing these instructions; the sending of these instructions to WCS.
PO Purchase Order.
Pre-advice; Goods Receipt Pre-advice An advanced notification of what is being received. Part of a manifest. Pre-advices can be stock and quantity, or individual pallet level.
Putaway The physical move of a pallet to a storage location as a result of receiving it into the warehouse.
RAG Acronym for Red/Amber/Green, a traffic light colouration system depicting (in sequence) Errors, Warnings or Informational messages. Usually used in operational monitoring to effectively display when certain processes are not working as expected.
RDT Radio Data Terminal.
Replen; Replenishment The act of moving product (usually a pallet) from bulk storage to a pick face.
Reposition The facility to change the location of a movement or putaway when at the final destination, sue to some issue discovered when performing the task.
RF Radio Frequency; An RF device is an RDT, typically used by CALIDUS WCS for executing warehouse tasks.
SCR; CR Software Change Request.
Short Pick The process of not fulfilling an order due to failure to identify sufficient product when picking. May also be used as a term to indicate Short Allocation.
SO Sales Order.
Truck Types Plants, Mechanical Handling Equipment. For example, Reach trucks, Counter-balance trucks, pallet riders, etc.
UOM Unit of Measure.
WA Wide Area; usually any area in the warehouse that is not restricted access due to space limitations, for example, floor areas, not Narrow Aisle.
WCS Warehouse Control System
WMS Warehouse Management System


A.3 Authorised By


Rev1
Rev1 Title		_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=FS_281363_New_CTMS_Execution_Screen&oldid=284’