Vision - User contributions [en-gb]

Demo Script

2011-06-28T14:48:47Z

Pjh:

=Introduction=
Calidus Vision is a Visibility and Productivity tool, designed to represent data from diverse systems in a single system, displaying important information in small, meaningful, obvious screens designed to highlight performance and enhance visibility of issues in the host systems.
{{comment|text=data from diverse systems in a single view, displaying important information in meaningful screens designed to highlight performance and enhance visibility of issues in the host systems.
|sign=[[User:Pjh]]|date=2/5/2011 15:42:21}}

=Logon=
You are prompted to enter a username and password.

Security: At the moment Calidus Vision is expected to be installed within a secure network, so no secure URL is provided, although this has been done through the Portal for added security and can be added on your local installation. The username and password are secured through the database logon parameters - if the username is not valid on that system, you will not be able to log in. Further, if the session expires (through inactivity), the user will be required to log in again.

=Main Screen=
The main screen shows the menu options and systems that are you are allowed to access.
This is achieved through a user-definable menu structure and a security level against each configured user.

==Systems==
You can filer the menu quickly by System by using the system popup. This will remove all items that have no meaning to the system being accessed. For a generic implementation linking to a WMS and WCS, these (and potentially the Admin functions) will be the only available options on this Systems popup.
{{comment|text=You can filter the menu quickly by each System by using the system view dropdown.
|sign=[[User:Pjh]]|date=2/5/2011 15:42:21}}

Further systems that have been included are the Calidus TMS system.

==Quick Menu==
The quick menu will be open upon starting the system. This is a set of screens chosen by the user (from any of their available screens) that they use every day.

==Single Screens==
Single screens are screens designed to show a single aspect of a data for a specific purpose.

For example:
*Orders Summary - this shows the total amount of picks available to be picked at the moment through the RF system.
*Daily Part Pick Productivity - this shows the actual performance of pickers on the current day, versus the target productivity rates.

==Summary Screens==
Summary screens combine single screens to bring information together in logical groups. Additionally they summarise figures across a group (warehouse, shift, owner) is order to provide an overview of progress within the operations.

For example:
*System and Warehouse Overview - This shows a panel of the current outstanding tasks available for users to complete, and a panel showing the tasks already completed by users on the current day.
*Current Productivity - This shows panels of 4 general tasks in the warehouse, showing the performance of employees in this area, versus the target productivity rates.

==Extended Extracts==
Calidus Vision extracts and analyses all common task types (for example Picking, Receipt, Stock Take, Putaway, Replen). Some operations require that these task types be broken down further (for example, low and high part picking, picking from chill areas only). Extended Extractions are screens that show this detailed information in the way that the operation wants.

{{Note}}Due to the bespoke nature of the breakdown (i.e. very site specific), this is not something that can be demonstrated and is not configured within the generic system.

==Analysis & Enquiries==
These screens allow you to view and extract detailed information over a time period.

For Example:
*Detail Enquiry - this shows all the historical productivity data.

You can query data through the fields offered.

You can Filter data once found.

You can sort the data.

You can Export the data to CSV or formatted output.

*Orders - Time To Completion - This shows the estimated amount of time required to complete the currently-available part picks in the operation.

==Finding Screens Quickly==
Note that this screen is one of the ones configured on this user's Quick Menu.

This can be configured through the User Settings screen.

Click on the User Quick Screens button and change the screens to be displayed (through the filter), the sequence, and save.

This methodology of sequencing screens is used throughout the system.

You can also access screens through a Search function on a popup toolbar.

Click the '>' button in the top left to show the popup toolbar options. Click Search and enter 'Status'. Click on Order Status 2.

==Graphs==
Graphs plot the data from the screens we have already seen (mostly the Summary screens) to provide a quick visible comparison of data. {{warning}} Your Browser must have Flash installed to display the Graphs.

For example:
*Shift Summary screen - this shows a comparison of the average productivity of all shifts in the operation, over all task types. Note that you can click on the data bars and you will be shown the data used to calculate the information shown.

==Monitor==
The Monitor screens show views of system-specific activities that require regular monitoring.

For example:
*Order Status/Order Status 2 - This provides a view of the orders being processed in the operation, from some days in the past to future requirements. The detail can be further enquired by clicking on a figure - you will then be shown the detailed information relating to orders at that status.

==Settings==
In these screens you will be able to configure the way that the system operates:
*Web - Here you can change the Look and Feel. For example, change the style to DHL, then reload the application using the button provided. There are many styles available, and more can be created (perhaps for a customer view).
*Productivity - Here you can maintain the Minimum and Target productivity levels, which directly affects the RAG colouration in the screens and extracts. {{note}} the system is multi-warehouse and multi-owner, allowing for a central installation.
*Run - Here you can maintain the screens for a simple Dashboard. Screens can be added and removed, and the dashboards can be set to run on this terminal through the Actions/Timed Display menu option.
*There are also a range of System specific settings.

==Admin==
The Admin screens allow changes of settings that affect how Vision runs. These are very restricted options (with a high security level) and should only be given to a select few supervisors.
Examples:
*User Maintenance
*Groups & Menu Maintenance
*Rules Maintenance

FS 288575 DH-8GXFKZ Picker to select correct carton

2011-06-20T09:42:00Z

Pjh: minor edit to correct the date

<div class="noprint">
{{#vardefine:Client|DHL}}
{{#vardefine:System|Calidus Mobile}}
{{#vardefine:Doc_Title|Picker to select correct carton}}
{{#vardefine:Version|1.0}}
{{#vardefine:Date|20th June 2011}}
{{#vardefine:Reference|288575 DH-8GXFKZ}}
</div>
{{Doc_Title
|Client={{#var:Client}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==
Request for functionality to display on the RDT terminal, prior to start of Picking Task, to enable Picker to select correct size carton for Pick based on the size of the order - an initiative to reduce packaging.

== Solution Overview ==
The existing Stock Drip Feed message will be modified to include the dimensions (depth, width, height) of the stock codes.

The Pallet Types Drip Feed message will be modified to include the dimensions of the cartons (i.e. the Pallet Types).

When the RDT process assigns a pick to an RF user (for Actavis, this is a single order), the RF unit displays an optional summary screen, showing the total quantity of stock to be picked. ''Calidus'' Mobile will also calculate the total volume of picks on this order and display a number of suggested Carton Types (Pallet Type) capable of holding the contents of the order.
The screen will display the carton plus the number of this type required. Each carton type suggested will have its own line.

{{note}} '''The smallest number of smallest carton types capable of holding the entire contents of the order will be suggested'''.

Examples:

There are 3 carton types:
*Small - can hold up to 30cc
*Medium - can hold up to 50cc
*Large - can hold up to 100cc

#If the order volume is 30cc, the system will suggest 1 small carton.
#If the order volume is 40cc, the system will suggest 1 medium carton.
#If the order volume is 60cc, the system will suggest 1 large carton.
#If the order volume is 100cc, the system will suggest 1 large carton.
#If the order volume is 110cc, the system will suggest 1 large carton and 1 small carton.

{{Note}} '''In the final example, it may be more efficient in space utilisation within the carton to suggest 2*small cartons and 1*large cartons. This mechanism is, however, more efficient on the number of cartons and, therefore, more efficient for the picker.'''

The display of these suggested carton sizes will be rule-controlled in ''Calidus'' Mobile.

== Scope ==
*The changes will be made to version 3.4 of the ''Calidus'' Mobile system and version 4.14 of the ''Calidus'' WMS only.



= Set-up =
== Pre-requisites ==
A valid ''Calidus'' Mobile system must be connected to a valid ''Calidus'' WMS.

== Menu Structure ==
None

== Data ==
'''WMS'''

Enter the pallet type dimensions '''ONLY''' for those pallet types you wish to use as carton storage using the Pallet Types Maintenance screen WHS0045. If the WCS interface is enabled, this information will be automatically sent to the WCS. If not, enable the interface and type 'SEND' at the Action prompt.

Ensure that the Owner rule STDF is created and enabled for those owners requiring it.

Enter the stock case dimensions using the Stock Maintenance screen STKSTOC01B, Further Options (99), then Physical Attributes (06). If the WCS interface is enabled, this information will be automatically sent to the WCS. If not, enable the interface and type 'SEND' at the Action prompt of the top Stock Maintenance screen (STKSTOC01B).

'''WCS'''

Enable the new Picking rule 'Calculate Packs' for either the Owners requiring it, or against the Warehouse if no Owner values exist.



= Functional Description =
== WCS Database Changes ==
A new Owner and Warehouse rule will be created in the ''Calidus'' Mobile database, called 'Calculate Packs'. This rule will be on the 'Picking and Post-Picking Activities' group and will have the description 'If enabled, the Pick Information screen displayed initially in the Part Picking module will display the required cartons for the volume of picks'.

The rule will have values 'Y' and 'N', with the default value being 'N'.

The existing 'Pallet Types' table will be modified to store the width, depth and height of the pallet types. The fields will all be of large numeric type.

The existing 'Stock' table will be modified to store the width, depth and height of the stock unit, as above.

== WHS0909 - Stock Drip Feed ==
The existing Stock Drip Feed message will be modified to include the dimensions (depth, width, height) of the stock codes.

The following fields will be added to the MBX_EXWMS_PALDET message already sent to the WCS:
{| class="wikitable"
|-
! Field
! Type
! Size
! Offset
! Value
|-
|MBX_RECORD_TYPE
|ZONED UNSIGNED
|3
|0
|162
|-
|MBX_DATE_TIME_STAMP
|CHARACTER
|14
|3
|DTS
|-
|MBX_PALLET_NO
|CHARACTER
|8
|17
|0
|-
|MBX_PALLET_LOC
|CHARACTER
|10
|25
|Pick Location
|-
|MBX_OWNER_CODE
|CHARACTER
|3
|35
|Stockist Code
|-
|MBX_PRODUCT_CODE
|CHARACTER
|35
|38
|Stock Code
|-
|MBX_DESCRIPTION
|CHARACTER
|30
|73
|Description of Stock
|-
|MBX_QUANTITY
|ZONED UNSIGNED
|5
|103
|Factor 2/3
|-
|MBX_CUST_BATCH
|CHARACTER
|25
|108
|UOM
|-
|MBX_WMS_ROT
|CHARACTER
|14
|133
|HAZ+CHILL+MANU+SELLBY+BATCH<br />+SEALS Required (1 character, Oracle Only)<br />+Trace Code Required (1 character, 414 only)
|-
|MBX_RDT_ID
|CHARACTER
|2
|147
|Blank
|-
|MBX_LAST_PICK_FLAG
|CHARACTER
|1
|149
|Blank
|-
|MBX_STATUS_FLAG
|CHARACTER
|1
|150
|A/D/X
|-
|MBX_MANU_DATE
|ZONED UNSIGNED
|8
|151
|Factor 1/2
|-
|MBX_PRODUCT_SELLBY_DATE
|ZONED UNSIGNED
|8
|159
|STD Pallet Qty
|-
|MBX_COMPANY_CODE
|CHARACTER
|3
|167
|Blank
|-
|MBX_WAREHOUSE_ID
|CHARACTER
|3
|170
|Blank
|-
|MBX_CUST_PALLET_NO
|CHARACTER
|25
|173
|BARCODE of STOCK_UOMS
|-
|FILLER/LONG_DESCRIPTION
|CHARACTER
|40
|198
|Blank
|-
|FILLER/LONG_DESCRIPTION_2
|ZONED UNSIGNED
|10
|238
|DESCRIPTION_2 of STOCK
|-
|FILLER/PACK_SIZE
|CHARACTER
|10
|248
|SIZE_PACK of STOCK
|-
|FILLER/MEASURE_TYPE
|ZONED UNSIGNED
|11
|258
|MEASURE_TYPE of STOCK
|-
|FILLER/GOODS_RECEIPT_INFO_MSG
|ZONED UNSIGNED
|8
|269
|TEXT_LINE_1/2/3 of CUST_PRODUCT_TEXT
|-
|'''FILLER/CASE_DEPTH'''
|ZONED UNSIGNED
|4
|277
|CASE_LENGTH of STOCK
|-
|'''FILLER/CASE_WIDTH'''
|ZONED UNSIGNED
|4
|281
|CASE_WIDTH of STOCK
|-
|'''FILLER/CASE_HEIGHT'''
|ZONED UNSIGNED
|4
|285
|CASE_DEPTH of STOCK
|-
|FILLER/TERMINATOR
|CHARACTER
|1
|289
|"X"
|}

== WHS0045 - Pallet Types Drip Feed ==
The Pallet Types Drip Feed message will be modified to include the dimensions of the cartons (i.e. the Pallet Types).

The following fields will be added to the MBX_EXWMS_PALTYPEUPD message already sent to the WCS:
{| class="wikitable"
|-
! Field
! Type
! Size
! Offset
! Value
|-
|-
|MBX_RECORD_TYPE
|ZONED UNSIGNED
|3
|0
|271
|-
|MBX_DATE_TIME_STAMP
|CHARACTER
|14
|3
| Current Date/Time
|-
|MBX_PALLET_TYPE
|CHARACTER
|4
|17
|PALLET_TYPE of WARE_PALLET_TYPES
|-
|MBX_STATUS_FLAG
|CHARACTER
|1
|21
|A/D/X, depending on status
|-
|MBX_COMPANY_CODE
|CHARACTER
|3
|22
|Common company code
|-
|MBX_WAREHOUSE_ID
|CHARACTER
|3
|25
|Common Warehouse ID
|-
|'''FILLER/PALLET_DEPTH'''
|ZONED UNSIGNED
|4
|28
|PALLET_DEPTH of WARE_PALLET_TYPES
|-
|'''FILLER/PALLET_WIDTH'''
|ZONED UNSIGNED
|4
|32
|PALLET_WIDTH of WARE_PALLET_TYPES
|-
|'''FILLER/PALLET_HEIGHT'''
|ZONED UNSIGNED
|4
|36
|PALLET_HEIGHT of WARE_PALLET_TYPES
|-
|FILLER/TERMINATOR
|CHARACTER
|1
|40
|X
|}

== WCS-Server - Message Receipt ==
The WCS Server Incoming Message Processors for message types 271 and 281 will be modified to receive the new fields specified above. The message structures will be modified to hold these new fields.

==WCS-Server/RDTMenu1 - Logon Request==
The Logon request procedures in WCS-Server and RDTMenu1 will be modified to receive the new Owner/Warehouse rule 'Calculate Packs' in the logon message, taken from the warehouse object.

== WCS-Server - Part Pick Request ==
When an initial Pick Request is received by the WCS Server, the process must calculate the required cartons for the tasks being assigned to the user.

The WCS Server already calculates the number of cases and units required by the tasks being assigned to the user. This code must be modified to calculate the volume required per pick task, if the new Warehouse/Owner rule 'Calculate Packs' is enabled. This will be achieved by linking to the Stock record (which it does already to calculate cases and units values).
* The Stock Case Volume will be calculated by multiplying the Case Height, Depth and Width values together.
* The Stock Unit Volume will be calculated by dividing the Stock Case Volume above by the unit to case factor (Factor_1_2 of the Stock record).
{{note}} These values may be calculated in advance and stored against the Stock record at the point of receiving the Stock Drip Feed message, if required.

The Pick Task Volume required for the pick task will be the number of cases required for the pick task multiplied by the Stock Case Volume, plus the number of units required for the pick task multiplied by the Stock Unit Volume.

All of these Pick Task Volumes for all tasks on the allocated pick tasks will then be summed to provide a total volume required.

The cartons required will be calculated by retrieving a list of all the potential cartons used by the operation (from the Pallet Types table, where the pallet types have dimension information only.
* The Pallet Volume will be calculated by multiplying the Pallet Height, Depth and Width values together.
{{note}} This value may be calculated in advance and stored against the Pallet Type record at the point of receiving the Pallet Type Drip Feed message, if required.

The records should be retrieved in Ascending Carton Volume sequence.

In order to calculate the number of cartons required, the WCS Server will loop through the Pallet Types records from smallest to largest. If the Pallet Volume is greater than the Running Total Pick Task Volume, the pallet type will be added to a Suggested Cartons list and the process will exit.
If the end of the Pallet Types records is found and the Pallet Volume is not greater that the Total Pick Task Volume, the last (i.e. largest) carton will be added to the Suggested Cartons list, the Running Total Pick Task Volume will be reduced by the Pallet Volume of the last carton and the process will begin again.

The process will continue until a Pallet Volume is found that is greater than the Running Total Pick Task Volume. Every time a Pallet Type is added to the Suggested Cartons list, the process will check whether one of these pallet types has already been suggested. If not, one will be added with quantity 1. If found, the quantity will be updated by 1.

When completed, the Suggested Cartons will be placed in a string and added to the end of the Pick Reply message, so that the RDT process can extract these if necessary.

'''Examples:'''

There are 3 carton types:
*Small - can hold up to 30cc
*Medium - can hold up to 50cc
*Large - can hold up to 100cc

#If the order volume is 30cc, the system will suggest 1 small carton.
#If the order volume is 40cc, the system will suggest 1 medium carton.
#If the order volume is 60cc, the system will suggest 1 large carton.
#If the order volume is 100cc, the system will suggest 1 large carton.
#If the order volume is 110cc, the system will suggest 1 large carton and 1 small carton.

== RDTMenu1 - Part Picking ==

When the RDT process assigns a pick to an RF user (for Actavis, this is a single order), the RF unit displays an optional summary screen, showing the total quantity of stock to be picked. ''Calidus'' Mobile will also calculate the total volume of picks on this order and display a number of suggested Carton Types (Pallet Type) capable of holding the contents of the order.

The WCS Server will send across the suggested cartons with first pick request, at the end of the Pick Reply message, as seen in the previous section.

If the new Owner/Warehouse rule 'Calculate Packs' is enabled, the screen will display the carton plus the number of this type required. The display will be before the total quantity to pick on this screen. Each carton type suggested will have its own line. The screen will display the carton type passed, ' * ' and then the number of each carton type required.
The display will be as follows:
<pre>
Cartons:
TYPE1 * 2
TYPE2 * 1
</pre>

{{note}} Only the initial Order Summary screen display will be modified to display this carton information - if the screen is displayed between order lines, this will not be included.

{{note}} If the screen display is not big enough to display this and all the other information on the screen, the screen must be modified to page the information, scrollable by the user pressing the '''UP''' and '''DOWN''' cursor keys.



= Appendix A: TEST PLAN =

{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=Test the new Carton Suggestion functionality
|MenuAccess=RDT Main Menu, Picking option.
|Prerequisites=See the Setup section for details.
|Objective=Test that: the new WCS rule can be set; the dimensions standing data is interfaced correctly to the WCS and; the correct number of cartons are suggested as required based on the pick tasks assigned to the user.
}}
{{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=WCS Maintenance
|Notes=
}}

{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Ensure that the new 'Calculate Packs' rule is available on the Warehouse and Owner maintenance screens.
|Result=The rule is available
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Ensure that the values available are as designed, that the rule defaults correctly, that the help is as designed and that the values can be saved.
|Result=As expected.
|Remarks=
|PassFail=
}}
{{TestPlan_CycleFooter}}

{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Standing Data
|Notes=Ensure that the RF interface is enabled.
}}

{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Enter dimensions against a new pallet type. Save.
|Result=The new pallet type should be created in WCS. <br />The dimension values should be included.
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Type 'SEND' at the Action prompt.
|Result=All pallet types should be sent to the WCS. <br />Dimensions for those that have them should be included. <br />Those without should be created with default value 0.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Enter dimensions against a stock code. Save.
|Result=The stock code should be created in WCS. <br />The dimension values should be included.
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Type 'SEND' at the Action prompt.
|Result=All stock codes for the owner should be sent to the WCS. <br />Dimensions for those that have them should be included. <br />Those without should be created with default value 0.
}}

{{TestPlan_CycleFooter}}

{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Part Picking
|Notes=Create orders with two dimensioned Stock items.<br />Ensure that each order increases in volume, <br />one order using the smallest pallet type, <br />one using the largest, <br />one exceeding the largest pallet type, <br />one requiring more that two large pallet types, <br />one of a case volume that is less than the large pallet type, plus a unit volume that takes it over this<br />one that spans multiple pick groups (or split the pick group manually) where one pick group requires a small pallet type and one requires a large pallet type.
}}

{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Start Part Picking, ensuring that the user is provided the smallest order.
|Result=The RDT will display a summary screen showing that one of the small pallet types is required to fulfil the order.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Complete this pick. Ask for another order, ensuring that the second order is selected.
|Result=The RDT will display a summary screen showing that one of the large pallet types is required to fulfil the order.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Complete this pick. Ask for another order, ensuring that the third order is selected.
|Result=The RDT will display a summary screen showing that one of the large pallet types and one other are required to fulfil the order.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Complete this pick. Ask for another order, ensuring that the fourth order is selected.
|Result=The RDT will display a summary screen showing that two of the large pallet types and one other are required to fulfil the order.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Complete this pick. Ask for another order, ensuring that the fifth order is selected.
|Result=The RDT will display a summary screen showing that one of the large pallet types and one small are required to fulfil the order.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Complete this pick. Ask for another order. The user will be provided the first (small) pick group.
|Result=The RDT will display a summary screen showing that one of the small pallet types is required to fulfil the pick.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Complete this pick. Ask for another. The user will be provided the second (large) pick group.
|Result=The RDT will display a summary screen showing that one of the large pallet types is required to fulfil the pick.
}}
{{TestPlan_CycleFooter}}


{{Doc_Appendix
|Appendix=B
|Estimate=Y
|Glossary=WCS
|Ref1=EST 288575 DH-8GXFKZ Picker to select correct carton
|RefV1=2.0
|RefDate1=13/06/2011
|REQ=0
|EST=0.75
|FS=0.75
|TS=0
|DEV=3.25
|ST=1
|IMP=0
|Client=EXL
|Year=2011
|FSEST=Y
|Rev1=Phil Harding
|Rev1Title=OBS Project Manager
|Rev2=Darryl Horton
|Rev2Title=DHL IS Assistant Operations Manager
}}</div>
[[Category:FS EXL]]

FS 288575 DH-8GXFKZ Picker to select correct carton

2011-06-20T09:28:47Z

Pjh: minor edit to version number

<div class="noprint">
{{#vardefine:Client|DHL}}
{{#vardefine:System|Calidus Mobile}}
{{#vardefine:Doc_Title|Picker to select correct carton}}
{{#vardefine:Version|1.0}}
{{#vardefine:Date|16th June 2011}}
{{#vardefine:Reference|288575 DH-8GXFKZ}}
</div>
{{Doc_Title
|Client={{#var:Client}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==
Request for functionality to display on the RDT terminal, prior to start of Picking Task, to enable Picker to select correct size carton for Pick based on the size of the order - an initiative to reduce packaging.

== Solution Overview ==
The existing Stock Drip Feed message will be modified to include the dimensions (depth, width, height) of the stock codes.

The Pallet Types Drip Feed message will be modified to include the dimensions of the cartons (i.e. the Pallet Types).

When the RDT process assigns a pick to an RF user (for Actavis, this is a single order), the RF unit displays an optional summary screen, showing the total quantity of stock to be picked. ''Calidus'' Mobile will also calculate the total volume of picks on this order and display a number of suggested Carton Types (Pallet Type) capable of holding the contents of the order.
The screen will display the carton plus the number of this type required. Each carton type suggested will have its own line.

{{note}} '''The smallest number of smallest carton types capable of holding the entire contents of the order will be suggested'''.

Examples:

There are 3 carton types:
*Small - can hold up to 30cc
*Medium - can hold up to 50cc
*Large - can hold up to 100cc

#If the order volume is 30cc, the system will suggest 1 small carton.
#If the order volume is 40cc, the system will suggest 1 medium carton.
#If the order volume is 60cc, the system will suggest 1 large carton.
#If the order volume is 100cc, the system will suggest 1 large carton.
#If the order volume is 110cc, the system will suggest 1 large carton and 1 small carton.

{{Note}} '''In the final example, it may be more efficient in space utilisation within the carton to suggest 2*small cartons and 1*large cartons. This mechanism is, however, more efficient on the number of cartons and, therefore, more efficient for the picker.'''

The display of these suggested carton sizes will be rule-controlled in ''Calidus'' Mobile.

== Scope ==
*The changes will be made to version 3.4 of the ''Calidus'' Mobile system and version 4.14 of the ''Calidus'' WMS only.



= Set-up =
== Pre-requisites ==
A valid ''Calidus'' Mobile system must be connected to a valid ''Calidus'' WMS.

== Menu Structure ==
None

== Data ==
'''WMS'''

Enter the pallet type dimensions '''ONLY''' for those pallet types you wish to use as carton storage using the Pallet Types Maintenance screen WHS0045. If the WCS interface is enabled, this information will be automatically sent to the WCS. If not, enable the interface and type 'SEND' at the Action prompt.

Ensure that the Owner rule STDF is created and enabled for those owners requiring it.

Enter the stock case dimensions using the Stock Maintenance screen STKSTOC01B, Further Options (99), then Physical Attributes (06). If the WCS interface is enabled, this information will be automatically sent to the WCS. If not, enable the interface and type 'SEND' at the Action prompt of the top Stock Maintenance screen (STKSTOC01B).

'''WCS'''

Enable the new Picking rule 'Calculate Packs' for either the Owners requiring it, or against the Warehouse if no Owner values exist.



= Functional Description =
== WCS Database Changes ==
A new Owner and Warehouse rule will be created in the ''Calidus'' Mobile database, called 'Calculate Packs'. This rule will be on the 'Picking and Post-Picking Activities' group and will have the description 'If enabled, the Pick Information screen displayed initially in the Part Picking module will display the required cartons for the volume of picks'.

The rule will have values 'Y' and 'N', with the default value being 'N'.

The existing 'Pallet Types' table will be modified to store the width, depth and height of the pallet types. The fields will all be of large numeric type.

The existing 'Stock' table will be modified to store the width, depth and height of the stock unit, as above.

== WHS0909 - Stock Drip Feed ==
The existing Stock Drip Feed message will be modified to include the dimensions (depth, width, height) of the stock codes.

The following fields will be added to the MBX_EXWMS_PALDET message already sent to the WCS:
{| class="wikitable"
|-
! Field
! Type
! Size
! Offset
! Value
|-
|MBX_RECORD_TYPE
|ZONED UNSIGNED
|3
|0
|162
|-
|MBX_DATE_TIME_STAMP
|CHARACTER
|14
|3
|DTS
|-
|MBX_PALLET_NO
|CHARACTER
|8
|17
|0
|-
|MBX_PALLET_LOC
|CHARACTER
|10
|25
|Pick Location
|-
|MBX_OWNER_CODE
|CHARACTER
|3
|35
|Stockist Code
|-
|MBX_PRODUCT_CODE
|CHARACTER
|35
|38
|Stock Code
|-
|MBX_DESCRIPTION
|CHARACTER
|30
|73
|Description of Stock
|-
|MBX_QUANTITY
|ZONED UNSIGNED
|5
|103
|Factor 2/3
|-
|MBX_CUST_BATCH
|CHARACTER
|25
|108
|UOM
|-
|MBX_WMS_ROT
|CHARACTER
|14
|133
|HAZ+CHILL+MANU+SELLBY+BATCH<br />+SEALS Required (1 character, Oracle Only)<br />+Trace Code Required (1 character, 414 only)
|-
|MBX_RDT_ID
|CHARACTER
|2
|147
|Blank
|-
|MBX_LAST_PICK_FLAG
|CHARACTER
|1
|149
|Blank
|-
|MBX_STATUS_FLAG
|CHARACTER
|1
|150
|A/D/X
|-
|MBX_MANU_DATE
|ZONED UNSIGNED
|8
|151
|Factor 1/2
|-
|MBX_PRODUCT_SELLBY_DATE
|ZONED UNSIGNED
|8
|159
|STD Pallet Qty
|-
|MBX_COMPANY_CODE
|CHARACTER
|3
|167
|Blank
|-
|MBX_WAREHOUSE_ID
|CHARACTER
|3
|170
|Blank
|-
|MBX_CUST_PALLET_NO
|CHARACTER
|25
|173
|BARCODE of STOCK_UOMS
|-
|FILLER/LONG_DESCRIPTION
|CHARACTER
|40
|198
|Blank
|-
|FILLER/LONG_DESCRIPTION_2
|ZONED UNSIGNED
|10
|238
|DESCRIPTION_2 of STOCK
|-
|FILLER/PACK_SIZE
|CHARACTER
|10
|248
|SIZE_PACK of STOCK
|-
|FILLER/MEASURE_TYPE
|ZONED UNSIGNED
|11
|258
|MEASURE_TYPE of STOCK
|-
|FILLER/GOODS_RECEIPT_INFO_MSG
|ZONED UNSIGNED
|8
|269
|TEXT_LINE_1/2/3 of CUST_PRODUCT_TEXT
|-
|'''FILLER/CASE_DEPTH'''
|ZONED UNSIGNED
|4
|277
|CASE_LENGTH of STOCK
|-
|'''FILLER/CASE_WIDTH'''
|ZONED UNSIGNED
|4
|281
|CASE_WIDTH of STOCK
|-
|'''FILLER/CASE_HEIGHT'''
|ZONED UNSIGNED
|4
|285
|CASE_DEPTH of STOCK
|-
|FILLER/TERMINATOR
|CHARACTER
|1
|289
|"X"
|}

== WHS0045 - Pallet Types Drip Feed ==
The Pallet Types Drip Feed message will be modified to include the dimensions of the cartons (i.e. the Pallet Types).

The following fields will be added to the MBX_EXWMS_PALTYPEUPD message already sent to the WCS:
{| class="wikitable"
|-
! Field
! Type
! Size
! Offset
! Value
|-
|-
|MBX_RECORD_TYPE
|ZONED UNSIGNED
|3
|0
|271
|-
|MBX_DATE_TIME_STAMP
|CHARACTER
|14
|3
| Current Date/Time
|-
|MBX_PALLET_TYPE
|CHARACTER
|4
|17
|PALLET_TYPE of WARE_PALLET_TYPES
|-
|MBX_STATUS_FLAG
|CHARACTER
|1
|21
|A/D/X, depending on status
|-
|MBX_COMPANY_CODE
|CHARACTER
|3
|22
|Common company code
|-
|MBX_WAREHOUSE_ID
|CHARACTER
|3
|25
|Common Warehouse ID
|-
|'''FILLER/PALLET_DEPTH'''
|ZONED UNSIGNED
|4
|28
|PALLET_DEPTH of WARE_PALLET_TYPES
|-
|'''FILLER/PALLET_WIDTH'''
|ZONED UNSIGNED
|4
|32
|PALLET_WIDTH of WARE_PALLET_TYPES
|-
|'''FILLER/PALLET_HEIGHT'''
|ZONED UNSIGNED
|4
|36
|PALLET_HEIGHT of WARE_PALLET_TYPES
|-
|FILLER/TERMINATOR
|CHARACTER
|1
|40
|X
|}

== WCS-Server - Message Receipt ==
The WCS Server Incoming Message Processors for message types 271 and 281 will be modified to receive the new fields specified above. The message structures will be modified to hold these new fields.

==WCS-Server/RDTMenu1 - Logon Request==
The Logon request procedures in WCS-Server and RDTMenu1 will be modified to receive the new Owner/Warehouse rule 'Calculate Packs' in the logon message, taken from the warehouse object.

== WCS-Server - Part Pick Request ==
When an initial Pick Request is received by the WCS Server, the process must calculate the required cartons for the tasks being assigned to the user.

The WCS Server already calculates the number of cases and units required by the tasks being assigned to the user. This code must be modified to calculate the volume required per pick task, if the new Warehouse/Owner rule 'Calculate Packs' is enabled. This will be achieved by linking to the Stock record (which it does already to calculate cases and units values).
* The Stock Case Volume will be calculated by multiplying the Case Height, Depth and Width values together.
* The Stock Unit Volume will be calculated by dividing the Stock Case Volume above by the unit to case factor (Factor_1_2 of the Stock record).
{{note}} These values may be calculated in advance and stored against the Stock record at the point of receiving the Stock Drip Feed message, if required.

The Pick Task Volume required for the pick task will be the number of cases required for the pick task multiplied by the Stock Case Volume, plus the number of units required for the pick task multiplied by the Stock Unit Volume.

All of these Pick Task Volumes for all tasks on the allocated pick tasks will then be summed to provide a total volume required.

The cartons required will be calculated by retrieving a list of all the potential cartons used by the operation (from the Pallet Types table, where the pallet types have dimension information only.
* The Pallet Volume will be calculated by multiplying the Pallet Height, Depth and Width values together.
{{note}} This value may be calculated in advance and stored against the Pallet Type record at the point of receiving the Pallet Type Drip Feed message, if required.

The records should be retrieved in Ascending Carton Volume sequence.

In order to calculate the number of cartons required, the WCS Server will loop through the Pallet Types records from smallest to largest. If the Pallet Volume is greater than the Running Total Pick Task Volume, the pallet type will be added to a Suggested Cartons list and the process will exit.
If the end of the Pallet Types records is found and the Pallet Volume is not greater that the Total Pick Task Volume, the last (i.e. largest) carton will be added to the Suggested Cartons list, the Running Total Pick Task Volume will be reduced by the Pallet Volume of the last carton and the process will begin again.

The process will continue until a Pallet Volume is found that is greater than the Running Total Pick Task Volume. Every time a Pallet Type is added to the Suggested Cartons list, the process will check whether one of these pallet types has already been suggested. If not, one will be added with quantity 1. If found, the quantity will be updated by 1.

When completed, the Suggested Cartons will be placed in a string and added to the end of the Pick Reply message, so that the RDT process can extract these if necessary.

'''Examples:'''

There are 3 carton types:
*Small - can hold up to 30cc
*Medium - can hold up to 50cc
*Large - can hold up to 100cc

#If the order volume is 30cc, the system will suggest 1 small carton.
#If the order volume is 40cc, the system will suggest 1 medium carton.
#If the order volume is 60cc, the system will suggest 1 large carton.
#If the order volume is 100cc, the system will suggest 1 large carton.
#If the order volume is 110cc, the system will suggest 1 large carton and 1 small carton.

== RDTMenu1 - Part Picking ==

When the RDT process assigns a pick to an RF user (for Actavis, this is a single order), the RF unit displays an optional summary screen, showing the total quantity of stock to be picked. ''Calidus'' Mobile will also calculate the total volume of picks on this order and display a number of suggested Carton Types (Pallet Type) capable of holding the contents of the order.

The WCS Server will send across the suggested cartons with first pick request, at the end of the Pick Reply message, as seen in the previous section.

If the new Owner/Warehouse rule 'Calculate Packs' is enabled, the screen will display the carton plus the number of this type required. The display will be before the total quantity to pick on this screen. Each carton type suggested will have its own line. The screen will display the carton type passed, ' * ' and then the number of each carton type required.
The display will be as follows:
<pre>
Cartons:
TYPE1 * 2
TYPE2 * 1
</pre>

{{note}} Only the initial Order Summary screen display will be modified to display this carton information - if the screen is displayed between order lines, this will not be included.

{{note}} If the screen display is not big enough to display this and all the other information on the screen, the screen must be modified to page the information, scrollable by the user pressing the '''UP''' and '''DOWN''' cursor keys.



= Appendix A: TEST PLAN =

{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=Test the new Carton Suggestion functionality
|MenuAccess=RDT Main Menu, Picking option.
|Prerequisites=See the Setup section for details.
|Objective=Test that: the new WCS rule can be set; the dimensions standing data is interfaced correctly to the WCS and; the correct number of cartons are suggested as required based on the pick tasks assigned to the user.
}}
{{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=WCS Maintenance
|Notes=
}}

{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Ensure that the new 'Calculate Packs' rule is available on the Warehouse and Owner maintenance screens.
|Result=The rule is available
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Ensure that the values available are as designed, that the rule defaults correctly, that the help is as designed and that the values can be saved.
|Result=As expected.
|Remarks=
|PassFail=
}}
{{TestPlan_CycleFooter}}

{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Standing Data
|Notes=Ensure that the RF interface is enabled.
}}

{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Enter dimensions against a new pallet type. Save.
|Result=The new pallet type should be created in WCS. <br />The dimension values should be included.
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Type 'SEND' at the Action prompt.
|Result=All pallet types should be sent to the WCS. <br />Dimensions for those that have them should be included. <br />Those without should be created with default value 0.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Enter dimensions against a stock code. Save.
|Result=The stock code should be created in WCS. <br />The dimension values should be included.
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Type 'SEND' at the Action prompt.
|Result=All stock codes for the owner should be sent to the WCS. <br />Dimensions for those that have them should be included. <br />Those without should be created with default value 0.
}}

{{TestPlan_CycleFooter}}

{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Part Picking
|Notes=Create orders with two dimensioned Stock items.<br />Ensure that each order increases in volume, <br />one order using the smallest pallet type, <br />one using the largest, <br />one exceeding the largest pallet type, <br />one requiring more that two large pallet types, <br />one of a case volume that is less than the large pallet type, plus a unit volume that takes it over this<br />one that spans multiple pick groups (or split the pick group manually) where one pick group requires a small pallet type and one requires a large pallet type.
}}

{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Start Part Picking, ensuring that the user is provided the smallest order.
|Result=The RDT will display a summary screen showing that one of the small pallet types is required to fulfil the order.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Complete this pick. Ask for another order, ensuring that the second order is selected.
|Result=The RDT will display a summary screen showing that one of the large pallet types is required to fulfil the order.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Complete this pick. Ask for another order, ensuring that the third order is selected.
|Result=The RDT will display a summary screen showing that one of the large pallet types and one other are required to fulfil the order.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Complete this pick. Ask for another order, ensuring that the fourth order is selected.
|Result=The RDT will display a summary screen showing that two of the large pallet types and one other are required to fulfil the order.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Complete this pick. Ask for another order, ensuring that the fifth order is selected.
|Result=The RDT will display a summary screen showing that one of the large pallet types and one small are required to fulfil the order.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Complete this pick. Ask for another order. The user will be provided the first (small) pick group.
|Result=The RDT will display a summary screen showing that one of the small pallet types is required to fulfil the pick.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Complete this pick. Ask for another. The user will be provided the second (large) pick group.
|Result=The RDT will display a summary screen showing that one of the large pallet types is required to fulfil the pick.
}}
{{TestPlan_CycleFooter}}


{{Doc_Appendix
|Appendix=B
|Estimate=Y
|Glossary=WCS
|Ref1=EST 288575 DH-8GXFKZ Picker to select correct carton
|RefV1=2.0
|RefDate1=13/06/2011
|REQ=0
|EST=0.75
|FS=0.75
|TS=0
|DEV=3.25
|ST=1
|IMP=0
|Client=EXL
|Year=2011
|FSEST=Y
|Rev1=Phil Harding
|Rev1Title=OBS Project Manager
|Rev2=Darryl Horton
|Rev2Title=DHL IS Assistant Operations Manager
}}</div>
[[Category:FS EXL]]

EST 288575 DH-8GXFKZ Picker to select correct carton

2011-06-13T15:46:59Z

Pjh:

{{Template:Estimate
|Supimix_Client_Code=EXL
|Supimix_Project_Code=EMEA
|Supimix_Site_Code=CHE3
|Supimix_Client_Reference=DH-8GXFKZ
|Supimix_Number=288575
|The_version_of_the_document=2.0
|Your_Name=Tony Walker
|Supimix_PO_Reference=gb01 . gbban7 . wg . 853700
|Supimix_Priority=3|Date_(DD/MM/YY)=13/06/11
|Clients_Customer=Actavis
|System_Version_being_changed=3.4
|Client_Request=Request for functionality to display on the RDT terminal, prior to start of Picking Task, to enable Picker to select correct size carton for Pick based on the size of the order - an initiative to reduce packaging.
|OBS_Solution=
{{note}}'''The changes will be made to version 3.4 of the ''Calidus'' Mobile system and version 4.14 of the ''Calidus'' WMS only.'''
The existing Stock Drip Feed message will be modified to include the dimensions (depth, width, height) of the stock codes.

The Pallet Types Drip Feed message will be modified to include the dimensions of the cartons (i.e. the Pallet Types).

When the RDT process assigns a pick to an RF user (for Actavis, this is a single order), the RF unit displays an optional summary screen, showing the total quantity of stock to be picked. ''Calidus'' Mobile will also calculate the total volume of picks on this order and display a number of suggested Carton Types (Pallet Type) capable of holding the contents of the order.
The screen will display the carton plus the number of this type required. Each carton type suggested will have its own line.

{{note}} '''The smallest number of smallest carton types capable of holding the entire contents of the order will be suggested'''.

Examples:
There are 3 carton types:
*Small - can hold up to 30cc
*Medium - can hold up to 50cc
*Large - can hold up to 100cc

#If the order volume is 30cc, the system will suggest 1 small carton.
#If the order volume is 40cc, the system will suggest 1 medium carton.
#If the order volume is 60cc, the system will suggest 1 large carton.
#If the order volume is 100cc, the system will suggest 1 large carton.
#If the order volume is 110cc, the system will suggest 1 large carton and 1 small carton.

{{Note}} '''In the final example, it may be more efficient in space utilisation within the carton to suggest 2*small cartons and 1*large cartons. This mechanism is, however, more efficient on the number of cartons and, therefore, more efficient for the picker.'''
The display of these suggested carton sizes will be rule-controlled in ''Calidus'' Mobile.

|Requirements_Days=0
|Estimation_Days=0.75
|Functional_Specification_Days=.75
|Technical_Specification_Days=0
|Development_Days=3.25
|Testing_and_Release_Days=1
|Implementation_Days=0
|Year=2011
}}
[[Category:Estimates EXL]]

Template:EstimateCostDetails

2011-06-07T15:07:11Z

Pjh:

<noinclude>
Usage:

<nowiki>
{{EstimateCostDetails</nowiki><br />
|Client=Client for estimate rates. Required if an estimate section is to be produced.<br />
|Year=Year for estimate rates. Required if an estimate section is to be produced.<br />
|REQ=Requirements Time. Defaults to zero.<br />
|EST=Estimate Time. Defaults to zero.<br />
|FS=Functional Specification Time. Defaults to zero.<br />
|TS=Technical Specification Time. Defaults to zero.<br />
|DEV=Development Time. Defaults to zero.<br />
|ST=Testing Time. Defaults to zero.<br />
|IMP=Implementation Time. Defaults to zero.<br />
|FSEST=Y if this estimate is for production in a functional specification. Omit if no separate estimate and functional specification sections are required. If the values in the estimate differ from the functional specification, use the fields EREQ, EEST, EFS, ETS, EDEV, ESTT, EIMP to identify the Estimate values. If these are omitted, the Functional Specification values in fields REQ, EST, FS, TS, DEV, ST, IMP will be used.<br />
|EREQ=Estimate Requirements Time. Defaults to the value specified in REQ if omitted.<br />
|EEST=Estimate Estimate Time. Defaults to the value specified in EST if omitted.<br />
|EFS=Estimate Functional Specification Time. Defaults to the value specified in FS if omitted.<br />
|ETS=Estimate Technical Specification Time. Defaults to the value specified in TS if omitted.<br />
|EDEV=Estimate Development Time. Defaults to the value specified in DEV if omitted.<br />
|ESTT=Estimate Testing Time. Defaults to the value specified in ST if omitted.<br />
|EIMP=Estimate Implementation Time. Defaults to the value specified in IMP if omitted.<br />
}}
</nowiki>

{{note}} If on a separate page Ensure that you include the relevant Category tag at the bottom of the page.

{{note}} Costs should be numeric. If one is not included, it will default to zero (0).

{{note|This page should be kept up-to-date with the latest cost changes for all clients, otherwise the costs will default to zero (0)}}

</noinclude>
{{#ifeq:{{{Year}}}|2011|
{{#ifeq:{{{Client}}}|EXL|
{{#vardefine:CostREQ|510}}
{{#vardefine:CostEST|510}}
{{#vardefine:CostFS|510}}
{{#vardefine:CostTS|510}}
{{#vardefine:CostDEV|459}}
{{#vardefine:CostST|459}}
{{#vardefine:CostIMP|459}}
|
{{#ifeq:{{{Client}}}|DHL|
{{#vardefine:CostREQ|510}}
{{#vardefine:CostEST|510}}
{{#vardefine:CostFS|510}}
{{#vardefine:CostTS|510}}
{{#vardefine:CostDEV|438}}
{{#vardefine:CostST|438}}
{{#vardefine:CostIMP|438}}
|
{{#ifeq:{{{Client}}}|CERT|
{{#vardefine:CostREQ|600}}
{{#vardefine:CostEST|600}}
{{#vardefine:CostFS|600}}
{{#vardefine:CostTS|600}}
{{#vardefine:CostDEV|600}}
{{#vardefine:CostST|600}}
{{#vardefine:CostIMP|600}}
|

{{#vardefine:Message|Unknown costs for client/year ({{{Client|No client}}}/{{{Year|No year}}})}}
{{#vardefine:CostREQ|0}}
{{#vardefine:CostEST|0}}
{{#vardefine:CostFS|0}}
{{#vardefine:CostTS|0}}
{{#vardefine:CostDEV|0}}
{{#vardefine:CostST|0}}
{{#vardefine:CostIMP|0}}
}}
}}
}}
|

{{#vardefine:Message|Unknown costs for client/year ({{{Client|No client}}}/{{{Year|No year}}})}}
{{#vardefine:CostREQ|0}}
{{#vardefine:CostEST|0}}
{{#vardefine:CostFS|0}}
{{#vardefine:CostTS|0}}
{{#vardefine:CostDEV|0}}
{{#vardefine:CostST|0}}
{{#vardefine:CostIMP|0}}
}}
{{#if: {{#var:Message}} |{{warning|{{#var:Message}}}} |
<table border="1px" width="100%">
<tr><td bgcolor="silver" colspan={{#ifeq:{{{FSEST}}}|Y|5|4}}>'''Cost Details'''</td></tr>
<tr>
<td bgcolor="silver">'''Activity'''</td>
{{#ifeq:{{{FSEST}}}|Y|<td bgcolor="silver" align="center">'''Estimate<br />No. of Days'''</td>|}}
<td bgcolor="silver" align="center">'''No. of Days'''</td>
<td bgcolor="silver" align="center">'''Rate per Day (£)'''</td>
<td bgcolor="silver" align="center">'''Cost (£ Exc. VAT)'''</td>
</tr>
<tr>
<td bgcolor="silver">Requirements</td>
{{#ifeq:{{{FSEST}}}|Y|<td bgcolor="silver" align="center">{{#number_format: {{{EREQ|{{{REQ}}}}}} |2 }}</td>|}}
<td align="center">{{#number_format: {{{REQ|0}}} |2 }}</td>
<td bgcolor="silver" align="center">{{#var:CostREQ}}</td>
<td align="right">£{{#number_format: {{#expr: {{{REQ|0}}}*{{#var:CostREQ}} }} |2 }}</td>
</tr>
<tr>
<td bgcolor="silver">Change Request Evaluation</td>
{{#ifeq:{{{FSEST}}}|Y|<td bgcolor="silver" align="center">{{#number_format: {{{EEST|{{{EST}}}}}} |2 }}</td>|}}
<td align="center">{{#number_format: {{{EST|0}}} |2 }}</td>
<td bgcolor="silver" align="center">{{#var:CostEST}}</td>
<td align="right">£{{#number_format: {{#expr: {{{EST|0}}}*{{#var:CostEST}} }} |2 }}</td>
</tr>
<tr>
<td bgcolor="silver">Functional Specification</td>
{{#ifeq:{{{FSEST}}}|Y|<td bgcolor="silver" align="center">{{#number_format: {{{EFS|{{{FS}}}}}} |2 }}</td>|}}
<td align="center">{{#number_format: {{{FS|0}}} |2}}</td>
<td bgcolor="silver" align="center">{{#var:CostFS}}</td>
<td align="right">£{{#number_format: {{#expr: {{{FS|0}}}*{{#var:CostFS}} }} |2 }}</td>
</tr>
<tr>
<td bgcolor="silver">Technical Specification</td>
{{#ifeq:{{{FSEST}}}|Y|<td bgcolor="silver" align="center">{{#number_format: {{{ETS|{{{TS}}}}}} |2 }}</td>|}}
<td align="center">{{#number_format: {{{TS|0}}}|2 }}</td>
<td bgcolor="silver" align="center">{{#var:CostTS}}</td>
<td align="right">£{{#number_format: {{#expr: {{{TS|0}}}*{{#var:CostTS}} }} |2 }}</td>
</tr>
<tr>
<td bgcolor="silver">Development</td>
{{#ifeq:{{{FSEST}}}|Y|<td bgcolor="silver" align="center">{{#number_format: {{{EDEV|{{{DEV}}}}}} |2 }}</td>|}}
<td align="center">{{#number_format: {{{DEV|0}}} |2 }}</td>
<td bgcolor="silver" align="center">{{#var:CostDEV}}</td>
<td align="right">£{{#number_format: {{#expr: {{{DEV|0}}}*{{#var:CostDEV}} }} |2 }}</td>
</tr>
<tr>
<td bgcolor="silver">Testing and Release</td>
{{#ifeq:{{{FSEST}}}|Y|<td bgcolor="silver" align="center">{{#number_format: {{{ESTT|{{{ST}}}}}} |2 }}</td>|}}
<td align="center">{{#number_format: {{{ST|0}}} |2 }}</td>
<td bgcolor="silver" align="center">{{#var:CostST}}</td>
<td align="right">£{{#number_format: {{#expr: {{{ST|0}}}*{{#var:CostST}} }} |2}}</td>
</tr>
<tr>
<td bgcolor="silver">Implementation</td>
{{#ifeq:{{{FSEST}}}|Y|<td bgcolor="silver" align="center">{{#number_format: {{{EIMP|{{{IMP}}}}}} |2 }}</td>|}}
<td align="center">{{#number_format: {{{IMP|0}}} |2 }}</td>
<td bgcolor="silver" align="center">{{#var:CostIMP}}</td>
<td align="right">£{{#number_format: {{#expr: {{{IMP|0}}}*{{#var:CostIMP}} }}|2 }}</td>
</tr>
<tr><td colspan={{#ifeq:{{{FSEST}}}|Y|5|4}}> </td></tr>
<tr>
<td bgcolor="silver">'''TOTAL'''</td>
{{#ifeq:{{{FSEST}}}|Y|<td bgcolor="silver" align="center">{{#number_format: {{#expr: {{{EREQ|{{{REQ}}}}}}+{{{EEST|{{{EST}}}}}}+{{{EFS|{{{FS}}}}}}+{{{ETS|{{{TS}}}}}}+{{{EDEV|{{{DEV}}}}}}+{{{ESTT|{{{ST}}}}}}+{{{EIMP|{{{IMP}}}}}} }} |2 }}</td>|}}
<td align="center">{{#number_format: {{#expr: {{{REQ|0}}}+{{{EST|0}}}+{{{FS|0}}}+{{{TS|0}}}+{{{DEV|0}}}+{{{ST|0}}}+{{{IMP|0}}} }} |2 }}</td>
<td bgcolor="silver"> </td>
<td align="right">£{{#number_format: {{#expr: ({{{REQ|0}}}* {{#var:CostREQ}})+({{{EST|0}}}* {{#var:CostEST}})+({{{FS|0}}}* {{#var:CostFS}})+({{{TS|0}}}* {{#var:CostTS}})+({{{DEV|0}}}* {{#var:CostDEV}})+({{{ST|0}}}* {{#var:CostST}})+({{{IMP|0}}}* {{#var:CostIMP}}) }} |2 }}</td>
</tr>
</table>
<table width="100%"><tr><td align="center">'''Estimate excludes training, release to live and go live support.'''</td></tr></table>
}}
<noinclude>
[[Category:Templates|{{PAGENAME}}]]
</noinclude>

EST 288575 DH-8GXFKZ Picker to select correct carton

2011-06-07T15:03:50Z

Pjh: v1.0 issued to client

Enquiries

2010-04-22T15:47:37Z

Pjh:

''Enquiries'' allow the user to select the data through a variety of parameters:

[[Image:Enquiry1.PNG|border|600px]]

'''Parameters available -'''
*Report By - You can choose the Sort mechanism by choosing from the '''Report By''' drop-down list.
*Task Type - You can choose the Task Type to be displayed by choosing from the '''Task Type''' drop-down list.
*Timescale - The timescale of the query can be set using the '''Timescale''' drop-downs. This allows selection of various intervals (Day, Week, Month or Quarter), as well as specifying how you want to select (Current, All, Specific or Range of intervals). If Specific Or Range is specified, the user can use a pop-up calendar to identify the interval.
*Direction - The direction of the sort using the '''Direction '''drop-down list. If no direction is chosen, the data is not sorted.
*Level - Select an individual employee, report summary or detail information. The summary level of the report can be chosen using the '''Level '''drop-down list.
*Limit - You can limit the amount of data shown on the screen using the '''Limit''' drop-down list.

Click '''Go''' to execute the query.

[[Image:Enquiry2.PNG|border|600px]]

You can change the query selection and re-run the query by clicking the '''Change Enquiry Selection''' button.

When data has been loaded, the enquiry will paginate the data for you - buttons are provided on the bottom of the table to navigate the data.

The data can be sorted by clicking on the column titles. Multiple sorts can also be performed by holding the '''SHIFT''' key whilst clicking.

The data displayed can be quickly filtered using the search box provided. Entering search criteria here will match against any data similar to it in any of the columns in the table. The table will indicate in the status bar whether the data is filtered.

You can export the data using the '''Export to CSV'''. Depending on the system settings, this will either be to a plain CSV file or in styled HTML format. The browser will open the application necessary to view this file.

There are several enquiries within Vision and they support all or most of the features described above.

-----
Back to [[Main_Page|Main Page]] | Next to [[Predictors]]
[[Category:Vision User Guide]]

Enquiries

2010-04-22T15:45:57Z

Pjh:

''Enquiries'' allow the user to select the data through a variety of parameters:

[[Image:Enquiry1.PNG|border|600px]]

'''Parameters available -'''
*Report By - You can choose the Sort mechanism by choosing from the '''Report By''' drop-down list.
*Task Type - Allows the restriction to particular Task Types
*Timescale - Day - Week - Month
*Direction - The direction of the sort using the '''Direction '''drop-down list. If no direction is chosen, the data is not sorted.
*Level - Select an individual employee, report summary or detail information
*Limit - You can limit the amount of data shown on the screen using the '''Limit''' drop-down list.

You can choose the Task Type to be displayed by choosing from the '''Task Type''' drop-down list.

The timescale of the query can be set using the '''Timescale''' drop-downs. This allows selection of various intervals (Day, Week, Month or Quarter), as well as specifying how you want to select (Current, All, Specific or Range of intervals). If Specific Or Range is specified, the user can use a pop-up calendar to identify the interval.

The summary level of the report can be chosen using the '''Level '''drop-down list.
Click '''Go''' to execute the query.

[[Image:Enquiry2.PNG|border|600px]]

You can change the query selection and re-run the query by clicking the '''Change Enquiry Selection''' button.

When data has been loaded, the enquiry will paginate the data for you - buttons are provided on the bottom of the table to navigate the data.

The data can be sorted by clicking on the column titles. Multiple sorts can also be performed by holding the '''SHIFT''' key whilst clicking.

The data displayed can be quickly filtered using the search box provided. Entering search criteria here will match against any data similar to it in any of the columns in the table. The table will indicate in the status bar whether the data is filtered.

You can export the data using the '''Export to CSV'''. Depending on the system settings, this will either be to a plain CSV file or in styled HTML format. The browser will open the application necessary to view this file.

There are several enquiries within Vision and they support all or most of the features described above.

-----
Back to [[Main_Page|Main Page]] | Next to [[Predictors]]
[[Category:Vision User Guide]]

Enquiries

2010-04-22T15:44:52Z

Pjh:

''Enquiries'' allow the user to select the data through a variety of parameters:

[[Image:Enquiry1.PNG|border|600px]]

'''Parameters available -'''
*Report By - You can choose the Sort mechanism by choosing from the '''Report By''' drop-down list.
*Task Type - Allows the restriction to particular Task Types
*Timescale - Day - Week - Month
*Direction - The direction of the sort using the '''Direction '''drop-down list. If no direction is chosen, the data is not sorted.
*Level -
*Limit - You can limit the amount of data shown on the screen using the '''Limit''' drop-down list.

You can choose the Task Type to be displayed by choosing from the '''Task Type''' drop-down list.

The timescale of the query can be set using the '''Timescale''' drop-downs. This allows selection of various intervals (Day, Week, Month or Quarter), as well as specifying how you want to select (Current, All, Specific or Range of intervals). If Specific Or Range is specified, the user can use a pop-up calendar to identify the interval.

The summary level of the report can be chosen using the '''Level '''drop-down list.
Click '''Go''' to execute the query.

[[Image:Enquiry2.PNG|border|600px]]

You can change the query selection and re-run the query by clicking the '''Change Enquiry Selection''' button.

When data has been loaded, the enquiry will paginate the data for you - buttons are provided on the bottom of the table to navigate the data.

The data can be sorted by clicking on the column titles. Multiple sorts can also be performed by holding the '''SHIFT''' key whilst clicking.

The data displayed can be quickly filtered using the search box provided. Entering search criteria here will match against any data similar to it in any of the columns in the table. The table will indicate in the status bar whether the data is filtered.

You can export the data using the '''Export to CSV'''. Depending on the system settings, this will either be to a plain CSV file or in styled HTML format. The browser will open the application necessary to view this file.

There are several enquiries within Vision and they support all or most of the features described above.

-----
Back to [[Main_Page|Main Page]] | Next to [[Predictors]]
[[Category:Vision User Guide]]

Enquiries

2010-04-22T15:43:03Z

Pjh:

''Enquiries'' allow the user to select the data through a variety of parameters:

[[Image:Enquiry1.PNG|border|600px]]

'''Parameters available -'''
*Report By - You can choose the Sort mechanism by choosing from the '''Report By''' drop-down list.
*Task Type -
*Timescale -
*Direction - The direction of the sort using the '''Direction '''drop-down list. If no direction is chosen, the data is not sorted.
*Level -
*Limit - You can limit the amount of data shown on the screen using the '''Limit''' drop-down list.

You can choose the Task Type to be displayed by choosing from the '''Task Type''' drop-down list.

The timescale of the query can be set using the '''Timescale''' drop-downs. This allows selection of various intervals (Day, Week, Month or Quarter), as well as specifying how you want to select (Current, All, Specific or Range of intervals). If Specific Or Range is specified, the user can use a pop-up calendar to identify the interval.

The summary level of the report can be chosen using the '''Level '''drop-down list.
Click '''Go''' to execute the query.

[[Image:Enquiry2.PNG|border|600px]]

You can change the query selection and re-run the query by clicking the '''Change Enquiry Selection''' button.

When data has been loaded, the enquiry will paginate the data for you - buttons are provided on the bottom of the table to navigate the data.

The data can be sorted by clicking on the column titles. Multiple sorts can also be performed by holding the '''SHIFT''' key whilst clicking.

The data displayed can be quickly filtered using the search box provided. Entering search criteria here will match against any data similar to it in any of the columns in the table. The table will indicate in the status bar whether the data is filtered.

You can export the data using the '''Export to CSV'''. Depending on the system settings, this will either be to a plain CSV file or in styled HTML format. The browser will open the application necessary to view this file.

There are several enquiries within Vision and they support all or most of the features described above.

-----
Back to [[Main_Page|Main Page]] | Next to [[Predictors]]
[[Category:Vision User Guide]]

Enquiries

2010-04-22T15:39:58Z

Pjh:

''Enquiries'' allow the user to select the data through a variety of parameters:

[[Image:Enquiry1.PNG|border|600px]]

'''Parameters available -'''
Report By - You can choose the Sort mechanism by choosing from the '''Report By''' drop-down list.
Task Type -
Timescale -
Direction - The direction of the sort using the '''Direction '''drop-down list. If no direction is chosen, the data is not sorted.
Level -
Limit - You can limit the amount of data shown on the screen using the '''Limit''' drop-down list.

You can choose the Task Type to be displayed by choosing from the '''Task Type''' drop-down list.

The timescale of the query can be set using the '''Timescale''' drop-downs. This allows selection of various intervals (Day, Week, Month or Quarter), as well as specifying how you want to select (Current, All, Specific or Range of intervals). If Specific Or Range is specified, the user can use a pop-up calendar to identify the interval.

The summary level of the report can be chosen using the '''Level '''drop-down list.
Click '''Go''' to execute the query.

[[Image:Enquiry2.PNG|border|600px]]

You can change the query selection and re-run the query by clicking the '''Change Enquiry Selection''' button.

When data has been loaded, the enquiry will paginate the data for you - buttons are provided on the bottom of the table to navigate the data.

The data can be sorted by clicking on the column titles. Multiple sorts can also be performed by holding the '''SHIFT''' key whilst clicking.

The data displayed can be quickly filtered using the search box provided. Entering search criteria here will match against any data similar to it in any of the columns in the table. The table will indicate in the status bar whether the data is filtered.

You can export the data using the '''Export to CSV'''. Depending on the system settings, this will either be to a plain CSV file or in styled HTML format. The browser will open the application necessary to view this file.

There are several enquiries within Vision and they support all or most of the features described above.

-----
Back to [[Main_Page|Main Page]] | Next to [[Predictors]]
[[Category:Vision User Guide]]

Enquiries

2010-04-22T15:39:06Z

Pjh:

File:Slide3.PNG

2010-04-22T15:25:18Z

Pjh:

File:Slide2.PNG

2010-04-22T15:24:34Z

Pjh:

File:Slide1.PNG

2010-04-22T15:23:50Z

Pjh:

Vision Roadmap

2010-04-22T15:22:44Z

Pjh:

[[File:Slide1.PNG]]
[[File:Slide2.PNG]]
[[File:Slide3.PNG]]

Vision Roadmap

2010-04-22T15:19:14Z

Pjh:

[[File:Example.jpg]]
[http://www.example.com link title]

Vision Roadmap

2010-04-22T15:17:49Z

Pjh:

[[File:Example.jpg]]
[[Media:Example.ogg]]

File:Slide1.jpg

2010-04-22T15:16:31Z

Pjh:

Vision Roadmap

2010-04-22T15:07:49Z

Pjh: Created page with 'File:Example.jpg'

[[File:Example.jpg]]

Main Page

2010-04-22T15:07:09Z

Pjh:

=Calidus ''Vision''=

==[[System Overview]]==

==[[System Guide]]==

==[[Vision Roadmap]]==

Add User

2010-04-22T15:04:32Z

Pjh:

[[File:AdminUser.PNG|border|600px]]

This screen allows new users to be created.
The field ''''Security Level'''' defines which screens can be seen - any screens of a security level less than or equal to the user's security level may be viewed.<br>
''''Group Code'''' defines which systems may be seen. Currently this is:
*WCS - Calidus ''3pl'' - Mobile
*WMS - Calidus ''3pl''
*ADM - Calidus Vision Administration Functiona
*ALL - All Available Systems

Multiple systems may be defined by delimiting them with a comma, e.g. WCS,WMS.
Specifying ALL allows the user access to all available systems.

-----
Back to [[Main_Page|Main Page]] | Next to [[Event Log]]
[[Category:Vision User Guide]]

Names Maintenance

2010-04-22T15:00:26Z

Pjh:

[[File:AdminNames.PNG|border|600px]]

This screen allows the user to maintain the displayed names for system codes mined from external systems.

The ''''Type'''' column shows the type of name being maintained, the ''''Code'''' shows the extraced code, and the user is allowed to maintain the ''''Description'''' data.

Click '''Save''' when finished.

As these descriptions are also displayed on the Vision heading bar, click '''Reload App with New Settings''' to refresh the main screen.

----
Back to [[Main_Page|Main Page]]
[[Category:Vision User Guide]]

Names Maintenance

2010-04-22T14:59:06Z

Pjh:

[[File:AdminNames.PNG|border|600px]]

This screen allows the user to maintain the displayed names for system codes mined from external systems.

The Type column shows the type of name being maintained, the Code shows the code, and the user is allowed to maintain the description.

Click '''Save''' when finished.

As these descriptions are also displayed on the Vision heading bar, click '''Reload App with New Settings''' to refresh the main screen.

----
Back to [[Main_Page|Main Page]]
[[Category:Vision User Guide]]

Releases

2010-04-22T14:57:56Z

Pjh:

[[File:AdminReleases.PNG|border|600px]]

This screen allows users to see the history of software releases that have been made to this implementation of the Vision application.

To view the information click the release name for details of the amendments made in that release.

----
Back to [[Main_Page|Main Page]] | Next to [[Names Maintenance]]
[[Category:Vision User Guide]]

Rules

2010-04-22T14:56:18Z

Pjh:

[[File:AdminRules.PNG|border|600px]]

This screen allows users to amend the system rules.<br>
'''Warning:''' modifying the values of these rules affects the running of the system and, as such, could result in unpredictable productivity rates or a non-running system.
<br><br>
*Clicking on a title will display the rules associated to that title.
*Rules can be held against any title level.
*Rules are displayed on the right-hand side of the screen.
*Depending on the setup and validation criteria set against the rule, the screen will display an appropriate entry box and allow the user to change the value.
*Once changed, click '''Save''' to save the changes.

----
Back to [[Main_Page|Main Page]] | Next to [[Releases]]
[[Category:Vision User Guide]]

Event Log

2010-04-22T14:54:56Z

Pjh:

[[File:AdminEventLog.PNG|border|600px]]

This screen allows the user to view the logging created from the data mining scripts.
Choose the data mining script from the drop-down, then click ''''GO'''' to view the last log messages created for this process.

----
Back to [[Main_Page|Main Page]] | Next to [[Rules]]
[[Category:Vision User Guide]]

Event Log

2010-04-22T14:54:31Z

Pjh:

[[File:AdminEventLog.PNG|border|600px]]

This screen allows the user to view the logging created from the data mining scripts.
Choose the data mining script from the drop-down, then click 'GO' to view the last log messages created for this process.

----
Back to [[Main_Page|Main Page]] | Next to [[Rules]]
[[Category:Vision User Guide]]

Add User

2010-04-22T14:53:37Z

Pjh:

[[File:AdminUser.PNG|border|600px]]

This screen allows new users to be created.
The field ''''Security Level'''' defines which screens can be seen - any screens of a lower security level than the user's may be viewed.<br>
''''Group Code'''' defines which systems may be seen. Currently this is:
*WCS
*WMS
*Admin
*ALL

Multiple systems may be defined by delimiting them with a comma, e.g. WCS,WMS.
Specifying ALL allows the user access to all available systems.

-----
Back to [[Main_Page|Main Page]] | Next to [[Event Log]]
[[Category:Vision User Guide]]

Add User

2010-04-22T14:51:17Z

Pjh:

[[File:AdminUser.PNG|border|600px]]

This screen allows new users to be created.
The field ''''Security Level'''' defines which screens can be seen - any screens of a lower security level than the user's may be viewed.<br>
Group Code defines which systems may be seen. Currently this is:
*WCS
*WMS
*Admin
*ALL

Multiple systems may be defined by delimiting them with a comma, e.g. WCS,WMS.
Specifying ALL allows the user access to all available systems.

-----
Back to [[Main_Page|Main Page]] | Next to [[Event Log]]
[[Category:Vision User Guide]]

Extended Productivity

2010-04-22T14:47:03Z

Pjh:

[[File:SettingsProdExt.PNG|border|600px]]

This screen allows you to maintain the minimum and target productivity figures for extended data extracts. When you have set the values as desired, click Save.

-----
Back to [[Main_Page|Main Page]]
[[Category:Vision User Guide]]

Edit Screens

2010-04-22T14:42:07Z

Pjh:

[[Image:SettingsRunEdit.PNG|border|600px]]

To return to the ''Run Settings'' screen, click '''Back to Settings'''.

To select the screens to be displayed in this run, select the screen on the left pane and click the button to move the screen to the Selected Pane. You can select multiple screens at a time by holding the '''CTRL''' key, or a range of screens by holding the '''SHIFT''' key whilst clicking.

The buttons are, from top to bottom:
* '''->''' Move the indicated Available screen(s) to the Selected screens pane.
* '''<-''' Remove the indicated Selected screen(s) from the Selected screens pane.
* '''>>''' Move all the Available screens to the Selected screens pane.
* '''<<''' Remove all the Selected screens from the Selected screens pane.

Once you have selected all the screens to be displayed in the run, click '''Save''' to save the settings.

-----
Back to [[Run]]
[[Category:Vision User Guide]]

Edit Screens

2010-04-22T14:40:46Z

Pjh:

[[Image:SettingsRunEdit.PNG|border|600px]]

To return to the ''Run Settings'' screen, click '''Back to Settings'''.

To select the screens to be displayed in this run, select the screen on the left pane and click the button to move the screen to the Selected Pane. You can select multiple screens at a time by holding the '''CTRL''' key, or a range of screens by holding the '''SHIFT''' key whilst clicking.

The buttons are, from top to bottom:
* Move the indicated Available screen(s) to the Selected screens pane.
* Remove the indicated Selected screen(s) from the Selected screens pane.
* Move all the Available screens to the Selected screens pane.
* Remove all the Selected screens from the Selected screens pane.

Once you have selected all the screens to be displayed in the run, click '''Save''' to save the settings.

-----
Back to [[Run]]
[[Category:Vision User Guide]]

Web

2010-04-22T14:38:52Z

Pjh:

[[Image:SettingsWeb.PNG|border|600px]]

The title of the application can be amended to suit your needs by amending the value in '''Title on Header'''. Simple HTML span tags can be used to affect the text, such as the Italic tag seen in the example screen.
The overall Look and Feel of the application can be chosen from the values in the '''Style''' drop-down list.
The size of the form and relative size of the font can be adjusted to best suit your display using the '''Size of Font''' and '''Size of Display Frame''' drop-down lists. The relative size of the entire display can be adjusted using CTRL-+ and CTRL-- in your browser.
The delay between screen changes in the Dashboard Times Display can be set by choosing the value from the '''Time until new screen displayed''' drop-down list.
The screen display can be maximised in the Dashboard Timed Display view by choosing ’No’ from the '''Show menu and logo in timed display''' drop-down list.

When you have set the values you want, click '''Save'''.
To update the application with your new settings, click '''Reload App with New Settings'''.

-----
Back to [[Main_Page|Main Page]] | Next to [[Productivity]]
[[Category:Vision User Guide]]

System Select

2010-04-22T14:36:32Z

Pjh:

Calidus Vision is designed to mine data from multiple systems and display screens associated to them within the user interface. Currently those systems are:
* Calidus 3PL-Mobile (WCS)
* Calidus 3PL (WMS 7.70)
There are plans to expand Vision to cover all Calidus products - please see the product roadmap for details.
Additionally, Calidus Vision can be expanded to work with external non-OBS systems.

In order to allow the user to see the data and screens associated to each system, each user is allocated a group of systems that they can access when they are set up.

When the user logs on, all available screens from all available systems are displayed, as well as those that are system-independent. Each system-specific screen name on the menu is preceded by the system code '''((System) Screen Name)''' when multiple systems are being displayed.

[[Image:SysSel_MainMenuItem.PNG|border]]

The user can choose to view a single system by using the "System" button on the menu.

The button displays the current systems being displayed in the menus.

When the button is clicked, the user can select the system required from the menu.

[[Image:SysSel_Menu.PNG|border]]

When selected, the menu will automatically reload with the new menu options relating to the chosen system.

-----
Back to [[Main_Page|Main Page]].
[[Category:Vision User Guide]]

System Select

2010-04-22T14:36:21Z

Pjh:

Calidus Vision is designed to mine data from multiple systems and display screens associated to them within the user interface. Currently those systems are:
* Calidus 3PL-Mobile (WCS)
* Calidus 3PL (WMS 7.70)
There are plans to expand Vision to cover all Calidus products - please see the product roadmap for details.
Additionally, Calidus Vision can be expanded to work with external non-OBS systems.

In order to allow the user to see the data and screens associated to each system, each user is allocated a group of systems that they can access when they are set up.

When the user logs on, all available screens from all available systems are displayed, as well as those that are system-independent. Each system-specific screen name on the menu is preceded by the system code '''((System) Screen Name)'''when multiple systems are being displayed.

[[Image:SysSel_MainMenuItem.PNG|border]]

The user can choose to view a single system by using the "System" button on the menu.

The button displays the current systems being displayed in the menus.

When the button is clicked, the user can select the system required from the menu.

[[Image:SysSel_Menu.PNG|border]]

When selected, the menu will automatically reload with the new menu options relating to the chosen system.

-----
Back to [[Main_Page|Main Page]].
[[Category:Vision User Guide]]

System Select

2010-04-22T14:35:51Z

Pjh:

Calidus Vision is designed to mine data from multiple systems and display screens associated to them within the user interface. Currently those systems are:
* Calidus 3PL-Mobile (WCS)
* Calidus 3PL (WMS 7.70)
There are plans to expand Vision to cover all Calidus products - please see the product roadmap for details.
Additionally, Calidus Vision can be expanded to work with external non-OBS systems.

In order to allow the user to see the data and screens associated to each system, each user is allocated a group of systems that they can access when they are set up.

When the user logs on, all available screens from all available systems are displayed, as well as those that are system-independent. Each system-specific screen name on the menu is preceded by the system code ((System) Screen name)when multiple systems are being displayed.

[[Image:SysSel_MainMenuItem.PNG|border]]

The user can choose to view a single system by using the "System" button on the menu.

The button displays the current systems being displayed in the menus.

When the button is clicked, the user can select the system required from the menu.

[[Image:SysSel_Menu.PNG|border]]

When selected, the menu will automatically reload with the new menu options relating to the chosen system.

-----
Back to [[Main_Page|Main Page]].
[[Category:Vision User Guide]]

System Select

2010-04-22T14:34:38Z

Pjh:

Calidus Vision is designed to mine data from multiple systems and display screens associated to them within the user interface. Currently those systems are:
* Calidus 3PL-Mobile (WCS)
* Calidus 3PL (WMS 7.70)
There are plans to expand Vision to cover all Calidus products - please see the product roadmap for details.
Additionally, Calidus Vision can be expanded to work with external non-OBS systems.

In order to allow the user to see the data and screens associated to each system, each user is allocated a group of systems that they can access when they are set up.

When the user logs on, all available screens from all available systems are displayed, as well as those that are system-independent. Each system-specific screen name on the menu is preceded by the system code when multiple systems are being displayed.

[[Image:SysSel_MainMenuItem.PNG|border]]

The user can choose to view a single system by using the "System" button on the menu.

The button displays the current systems being displayed in the menus.

When the button is clicked, the user can select the system required from the menu.

[[Image:SysSel_Menu.PNG|border]]

When selected, the menu will automatically reload with the new menu options relating to the chosen system.

-----
Back to [[Main_Page|Main Page]].
[[Category:Vision User Guide]]

System Select

2010-04-22T14:33:40Z

Pjh:

Calidus Vision is designed to mine data from multiple systems and display screens associated to them within the user interface. Currently those systems are:
* Calidus 3PL-Mobile (WCS)
* Calidus 3PL (WMS 7.70)
There are plans to explan Vision to cover all Calidus products - please see the product roadmap for details.
Additionally, Calidus Vision can be expanded to work with other external systems.

In order to allow the user to see the data and screens associated to each system, each user is allocated a group of systems that they can access when they are set up.

When the user logs on, all available screens from all available systems are displayed, as well as those that are system-independent. Each system-specific screen name on the menu is preceded by the system code when multiple systems are being displayed.

[[Image:SysSel_MainMenuItem.PNG|border]]

The user can choose to view a single system by using the "System" button on the menu.

The button displays the current systems being displayed in the menus.

When the button is clicked, the user can select the system required from the menu.

[[Image:SysSel_Menu.PNG|border]]

When selected, the menu will automatically reload with the new menu options relating to the chosen system.

-----
Back to [[Main_Page|Main Page]].
[[Category:Vision User Guide]]

Look and Feel

2010-04-22T14:32:08Z

Pjh:

==Look and Feel==
Several different styles have been created based on client web sites:

[[Image:LNF1.PNG|400px]]

[[Image:LNF2.PNG|400px]]

[[Image:LNF3.PNG|400px]]

[[Image:LNF4.PNG|400px]]

A specific look and feel can be tailored to your need by the OBS development team.

-----
Back to [[Main_Page|Main Page]]. Next to [[Credits]]
[[Category:Vision User Guide]]

Main Screen (HOME)

2010-04-22T14:30:55Z

Pjh:

[[Image:Home.PNG|border|600px]]

This screen is accessible at any time by selecting '''''Home''''' on the main menu on the left side of the screen.

The screen displays summary help information.

The left side of the screen displays the main menu. This menu is displayed on all screens, except the Timed Display.

Menus can be opened and closed by clicking on them.
*''[[Summary Screens]]'' show combined views of information designed to give an overview of particular areas quickly and easily.
*''[[Single Screens]]'' show a single element, usually tailored for a specific purpose.
*''[[Graphs]]'' show graphical versions of the summary screens. In most cases, clicking on the graph will display the data used to create the graph.
*''[[Analysis]]'' allows the user to enquire on the productivity data using a series of defined parameters.
*''[[Monitor]]'' allows the user to view monitoring tools for the mined external systems.
*''[[Actions]]'' contains the ability for the user to show a Dashboard Timed Display.
*''[[Settings]]'' allows the user to change several parameters that affect how the system looks, feels and displays.
*''Log Off'' logs the user out of the application.

Each screen in the menu contains a description of what will be displayed - to see this, simply hover the mouse over the screen name.

-----
Back to [[Main_Page|Main Page]]. Next to [[Settings]]
[[Category:Vision User Guide]]

Main Screen (HOME)

2010-04-22T14:26:10Z

Pjh:

[[Image:Home.PNG|border|600px]]

This screen is accessible at any time by selecting '''''Home''''' on the main menu on the left side of the screen.

The screen displays summary help information.

The left side of the screen displays the main menu. This menu is displayed on all screens, except the Timed Display.

Menus can be opened and closed by clicking on them.
*''[[Summary Screens]]'' show combined views of information designed to give an overview of particular areas quickly and visibly.
*''[[Single Screens]]'' show a single element, usually tailored for a specific purpose.
*''[[Graphs]]'' show graphical versions of the summary screens. In most cases, clicking on the graph will display the data used to create the graph.
*''[[Analysis]]'' allow the user to enquire on the productivity data using a series of defined parameters.
*''[[Monitor]]'' allow the user to view monitoring tools for the mined external systems.
*''[[Actions]]'' contains the ability for the user to show a Dashboard Timed Display.
*''[[Settings]]'' allows the user to change several parameters that affect how the system looks, feels and displays.
*''Log Off'' logs the user out of the application.

Each screen in the menu contains a description of what will be displayed - to see this, simply hover the mouse over the screen name.

-----
Back to [[Main_Page|Main Page]]. Next to [[Settings]]
[[Category:Vision User Guide]]

Log On

2010-04-22T14:25:26Z

Pjh:

Users will be pre set up. Use the user names and passwords provided to log on to the system.
<center>[[Image:Logon.PNG]]</center>

-----
Back to [[Main_Page|Main Page]]. Next to [[Main_Screen_(HOME)|Home]]
[[Category:Vision User Guide]]

Log On

2010-04-22T14:25:09Z

Pjh:

Users will be pre set up for. Use the user names and passwords provided to log on to the system.
<center>[[Image:Logon.PNG]]</center>

-----
Back to [[Main_Page|Main Page]]. Next to [[Main_Screen_(HOME)|Home]]
[[Category:Vision User Guide]]

System Guide

2010-04-22T14:20:54Z

Pjh:

The Calidus ''Vision'' system combines several components:
* Dashboard - Simple queries and tabular summaries, designed to be used within a Warehouse to help improve productivity.
* Analytics - Queries, Graphs, Enquiries and summary screens providing a deeper analysis of the current warehouse operation. This component includes all the functionality of the Dashboard, plus additional 'deep dive' analysis and historical enquiries.
* Monitor - screens designed to allow users to gain visibility of potential errors within the systems monitored by Vision, within a reasonable timescale.

Additionally, Calidus Vision is designed to mine data from several systems and display screens associated to them within the user interface. To that end, each user is allocated a group of systems that they can access. Currently those systems are:
* Calidus 3PL-Mobile (WCS)
* Calidus 3PL (WMS 7.70)
* Admin Functions
There are plans to expand Vision to cover all Calidus products - please see the product roadmap for details.
Additionally, Calidus Vision can be expanded to work with external non-OBS systems.

The basic operation of the components are the same.
* [[Basics]]
* [[Log On]]
* [[Main Screen (HOME)]]
* [[System Select]]
* [[Settings]]
** [[Web]]
** [[Productivity]]
** [[Run]]
*** [[Edit Screens]]
** [[User]]
** [[Extended Productivity]]
* [[Admin]]
** [[Add User]]
** [[Event Log]]
** [[Rules]]
** [[Releases]]
** [[Names Maintenance]]
* [[Look and Feel]]
* [[Credits]]

==Dashboard==
A limited number of pertinent screens are included in the following categories:
* [[Summary Screens]]
* [[Single Screens]]
Additionally, the Dashboard display is started from:
* [[Actions]]

==Analytics==
A far greater number of screens are included than in the Dashboard stand-alone product. The queries show analysis of productivity versus targets and minimums, with historical analysis and enquiries included across all categories.
* [[Summary Screens]]
* [[Single Screens]]
* [[Graphs]]
* [[Analysis]]
** [[Enquiries]]
** [[Predictors]]
* [[Monitor]]
Additionally, the Dashboard display is started from:
* [[Actions]]

[[Category:Vision User Guide]]