|
|
| Line 1: |
Line 1: |
| =Calidus ''Vision''= | | =Calidus ''Vision''= |
|
| |
|
| ==System Guide== | | ==[[System Overview]]== |
| [[System Guide]] | |
|
| |
|
| ==Introduction== | | ==[[System Guide]]== |
| The purpose of the Calidus ''Vision'' product is to allow visibility of productivity, system and business information through the use of graphs, charts and data lists.
| |
| | |
| There is a business need to extract and see information regarding the operation and its performance within the warehouse.
| |
| | |
| Therefore the Calidus Vision product will be used to display this information.
| |
| | |
| As Calidus 3''pl''-Mobile (the WCS) is highly used and must remain responsive at the highest level at all times, the data for Vision is 'mined' into a new database, where productivity analysis begins.
| |
| | |
| ==Network Diagram==
| |
|
| |
| [[Image:Network.PNG]] | |
| | |
| In this instance, Calidus 3''pl''-Mobile exists on one server and the Data Mining process and Calidus Vision are on a separate server, for simplicity. As all of the processes are Windows-based, all could co-exist on the same server or be distributed to separate servers as required.
| |
| Additionally, although the Data Mining Process and Application Server databases are separate in the diagram, they are normally combined.
| |
| | |
| ==Data Mining==
| |
| OBS have created data mining processes for the extraction of system, activity and productivity data from the Calidus 3''pl''-Mobile database. This includes (but is not limited to):<br>
| |
| '''System Data:'''
| |
| * Receipts in Progress
| |
| * Total Cases SKUs on Receipts
| |
| * Total number of SKUs on Receipts
| |
| * Number of Putaways and total quantity.
| |
| * Number of Moves and total quantity
| |
| * Number of Replens and total quantity
| |
| * Number of Full-pallet Picks and total quantity
| |
| * Number of Part-pallet picks and total quantity
| |
| * Number of Stock Take tasks
| |
| * Number and Status of loading tasks (Pending, Held, In Progress, Ready for Despatch)
| |
| '''Activity Data:'''
| |
| * All Activities performed by RF users
| |
| '''Productivity Data (Calculated from the Activity Data):'''
| |
| * Summary of number of tasks completed per day
| |
| * Detail of number of tasks completed per session
| |
| * Productivity figures derived from tasks per hour, per day.
| |
| '''Monitor Data:'''
| |
| * Various (depending on system.
| |
| | |
| '''Platform:''' Windows
| |
| Technology: Windows Script, ADO, MySQL Database
| |
| | |
| ==Parameters==
| |
| The data mining database has been created to allow the entry of parameters to show Minimum and Desired Productivity rates for each functional area.
| |
| | |
| As the data mining tools are further developed, this will also include:
| |
| * Historical analysis of productivity in functional areas, to learn productivity rates and predictions.
| |
| | |
| For more details, please consult the product road map.
| |
| | |
| ==Calidus ''Vision'' Front-End==
| |
| The Calidus ''Vision'' web front end displays the data on timed changing display, optionally displaying the data in forms, graphs and tables.
| |
| | |
| This supports:
| |
| * System Choice (through system popup menu) and multiple system access.
| |
| * Productivity views (per task, per Warehouse/Owner/Employee, in days, weeks, months and quarters.
| |
| * System views, showing the current state of the system mined in terms of tasks outstanding.
| |
| * Enquiries on the data in tabular form.
| |
| * Filtering (enter values in Search box provided), paging (use buttons below table), sorting (click or shift-click on column headers) and CSV extract (using the button provided) through Enquiries.
| |
| * Graphs (including drill-down to data, through clicking graph points).
| |
| * RAG Colour-highlighting (through Productivity Enquiry and Order Status screens).
| |
| * Quick Menu (contents can be modified through the User Settings screen).
| |
| * Definable menu structure.
| |
| * Dashboard (through Timed Display), including configurable dashboard display (through Run Settings).
| |
| * Assist help.
| |
| * Multi-owner/warehouse access (through User Settings).
| |
| * Client look & feel styling and display configuration (through Web Settings).
| |
| * Configurable productivity targets (through Productivity Settings) at each level (company/Warehouse, owner).
| |
| * Multiple information streams displayed on one form (2 horizontally, 2 vertically, 4 corners).
| |
| * Task Completion prediction.
| |
| | |
| | |
| '''Platform:''' Windows/Linux
| |
| '''Technology:''' IIS (Windows), ASP, ADO, JavaScript, HTML, CSS
| |
| | |
| '''Browser Requirements''':<br>
| |
| The Vision system is browser-independent, but requires that the browser support the following functionality:
| |
| * Frames
| |
| * JavaScript
| |
| * Cookies
| |
| * Flash
| |
| | |
| The system has been tested on:
| |
| * Mozilla Firefox 3.0/3.5/3.6
| |
| * Microsoft Internet Explorer 7/8/Compatibility Mode
| |
| * Opera 8/9
| |
| * Google Chrome
| |
| | |
| ==Productivity Measurement Method==
| |
| | |
| One of the main functions within Vision is to collate and display productivity rates for various tasks within the mined systems. This is dependent on the data mined.
| |
| The current productivity figures displayed within Vision come from the data stored within Calidus 3PL-Mobile, the OBS Logistics RF solution.
| |
| | |
| The detailed activity data is mined from Calidus 3PL-Mobile, which includes the following information:
| |
| * The type of activity, for example:
| |
| ** Task information (receipt, pick, putaway, etc).
| |
| ** Log-on/off information.
| |
| * The start date/time of the activity
| |
| * The end date/time of the activity
| |
| * Who performed the activity.
| |
| * For task-based information, this also includes:
| |
| ** Pallet information
| |
| ** Company/Warehouse/Owner information
| |
| ** Location information
| |
| | |
| This is mined and loaded into Calidus Vision's database, then analysed to produce productivity figures for the company, warehouse, owner and employee for the following intervals:
| |
| * Daily
| |
| * Weekly
| |
| * Monthly
| |
| * Quarterly
| |
| | |
| The Productivity data is calculated in tasks/hour (and quantity of stock/hour) by storing the total quantity of tasks completed, the quantity of stock moved and the total time taken for these tasks in summary form for each of the time intervals.
| |
| | |
| The productivity of a user on a task type is calculated as: <br>
| |
| The total time taken on the task (in seconds) <br>
| |
| divided by <br>
| |
| the number of seconds in an hour, multipled by the number of tasks completed
| |
| | |
| The case productivity of a user on a task type is calculated as: <br>
| |
| The total time taken on the task (in seconds) <br>
| |
| divided by <br>
| |
| the number of seconds in an hour, multipled by the number of cases in the tasks completed.
| |
| | |
| There are two methods of calculating the time taken for a task, configurable within the system.
| |
| | |
| ===By Core System===
| |
| In this method, Vision calculates the time taken to complete each task by using the core system's start and end time stamps for each individual task and producing a number of seconds taken for each task. These are stored against the summary values.
| |
| | |
| ===To Next Task===
| |
| In this method, Vision calculates the time taken to complete each task as the elapsed time from the start of this task to the start of the following task, in seconds, if the next task is the same type as the current task, or a log off activity.
| |
| | |
| So, for example:
| |
| | |
| <table border="1">
| |
| <tr><td>Task<br>#</td><td>Start<br>Time</td><td>End<br>Time</td><td>Type</td><td>Current Time<br>Elapsed</td><td>New Time<br>Elapsed</td></tr>
| |
| <tr><td>1</td><td>0</td><td>5</td><td>Putaway</td><td>5</td><td>10</td></tr>
| |
| <tr><td>2</td><td>10</td><td>15</td><td>Putaway</td><td>5</td><td>10</td></tr>
| |
| <tr><td>3</td><td>20</td><td>-</td><td>Log Off</td><td>0</td><td>0</td></tr>
| |
| <tr><td>4</td><td>30</td><td>-</td><td>Log On</td><td>0</td><td>0</td></tr>
| |
| <tr><td>5</td><td>40</td><td>45</td><td>Putaway</td><td>5</td><td>10</td></tr>
| |
| <tr><td>6</td><td>50</td><td>55</td><td>Putaway</td><td>5</td><td>5</td></tr>
| |
| <tr><td>7</td><td>60</td><td>65</td><td>Pick</td><td>5</td><td>10</td></tr>
| |
| <tr><td>8</td><td>70</td><td>75</td><td>Pick</td><td>5</td><td>10</td></tr>
| |
| <tr><td>9</td><td>80</td><td></td><td>Log Off</td><td>0</td><td>0</td></tr>
| |
| </table>
| |
| | |
| This method then accounts for time when the user may have finished one task but not yet started the next. Only time changing tasks is seen as inactive time.
| |
| | |
| ==Extended Productivity Measurement==
| |
| Vision currently breaks tasks down by a general task type field, which identifies each task with an action, for example, for Calidus 3PL-Mobile, the list is as follows:
| |
| * Receipt
| |
| * Putaway
| |
| * Pallet Move
| |
| * Replen
| |
| * Part Pick
| |
| * Full-pallet Pick
| |
| * Pre-Deconsolidation
| |
| * Deconsolidation
| |
| * Loading
| |
| | |
| Vision has the capability of breaking down these tasks by a selection of criteria.
| |
| So, for example, where part picks would normally come from a pick face, it is not unusual for an operation to pick cases or units from a pallet that is high in the racking. In this case, the productivity rates for these tasks may need to be measured separately from the normal task counts. The extended productivity measurement functionality allows for this.
| |
| | |
| The process extracts both the current system tasks and the productivity information that matches the criteria provided, from the following:
| |
| * Task Type
| |
| * Source Location
| |
| * Destination Location
| |
| * Company
| |
| * Warehouse
| |
| * Owner
| |
| * Priority (for system data only)
| |
| | |
| Each activity that matches the criteria specified is collated and stored separately to the generic data and can be viewed within Vision.
| |
| <br>
| |
| '''Example:'''
| |
| | |
| Certain of owner ABC's orders for export are always taken to a specific marshalling location "MAREXP", as they are packaged differently. Additionally, all picks taken from locations not in level 1 need to be recorded separately, resulting in two extended data extracts:
| |
| * Export Low
| |
| * Export High
| |
| | |
| The criteria matched is:<br>
| |
| | |
| '''To match orders as Export:'''
| |
| * Company = "X"
| |
| * Warehouse = "Y"
| |
| * Owner = "ABC"
| |
| * Task Type = "Part Picks"
| |
| * Destination Location = "MAREXP"
| |
| In this criteria, if the task details match explicity, the task is marked as "Export", otherwise it is not marked for extended data extract.
| |
| | |
| '''To match orders as from High or Low (pick face) locations:'''
| |
| * Company = "X"
| |
| * Warehouse = "Y"
| |
| * Owner = "ABC"
| |
| * Task Type = "Part Picks"
| |
| * Source Location's right-most character = "1" = "Low", else "High"
| |
| In this criteria, if the Task's source location's right-most character is "1", the task is marked as "Low", otherwise it is marked as "High".
| |
| <br>
| |
| | |
| The criteria specified are cumulative, in that each set of criteria is matched against all tasks, and those that match are marked with the specified text from the criteria matched.
| |
| In this example, the following tasks will be marked as follows:
| |
| | |
| <table border="1">
| |
| <tr><td>Task #</td><td>Task </td><td>Source Loc</td><td>Dest Loc</td><td>Extended Type</td></tr>
| |
| <tr><td>1</td><td>Putaway</td><td>RECBAY</td><td>AA0011</td><td>-</td></tr>
| |
| <tr><td>2</td><td>Part Pick</td><td>AA0011</td><td>MAREXP</td><td>Export Low</td></tr>
| |
| <tr><td>3</td><td>Part Pick</td><td>AA0014</td><td>MAREXP</td><td>Export High</td></tr>
| |
| <tr><td>4</td><td>Part Pick</td><td>AA0011</td><td>MAR001</td><td>Low</td></tr>
| |
| <tr><td>5</td><td>Part Pick</td><td>AA0014</td><td>MAR001</td><td>High</td></tr>
| |
| </table>
| |
| | |
| It can be seen in this example that it is possible to have one group of criteria matching while the other does not, resulting in single rather than cumulative matches (see tasks 4 and 5 above). This allows for extremely flexible rules to be set and allows the data mining process to be efficient.
| |
| | |
| '''Note:''' This assumes that all the tasks are for Company "X", warehouse "Y" owner "ABC".
| |
| | |
| ==Initial Installation==
| |
| [[Initial Installation]]
| |
| ==Release Process==
| |
| [[Release Process]]
| |
| ==Development Process==
| |
| [[Development Process]]
| |
| [[Category:Vision Overview]]
| |
