# Presentation: 264495

## Symbol “Mobile Terminal” (Scan Gun)

- MC 9090G
- Windows CE 5.0
- Yantra 7X Mobile Application

## Getting started

- 	Symbol 9090 G Quickstart Guide and Training PowerPoint
- For
- Fire Cache Warehouse Operations

## Slide 3

## How to get a good scan

## Don’t hurt yourself!

## Getting Started

_**First Time Usage**_
- Battery Charging and Battery Change Out
- Refer to pages1-5 through 1-8 User’s Manual

## Battery Management

_**Battery Saving Tips**_
- Leave the mobile computer connected to AC power at all times when not in use.
- Set the mobile computer to turn off after a short time period of non-use.
- Set the display and keyboard backlight to turn off after a short period of non-use.
- Power off the mobile computer when charging to charge at a faster rate.

## Starting the Mobile Computer

- Press the red Power button
- If the mobile computer does not power on, perform a cold boot (page 2-50 User’s Manual)

## Changing the Power Setting

- To Turn the Computer Off After a Short Period of Non-Use:
- Devices equipped with CE 5.0 tap: Start>Settings>Control Panel>Power icon>Power Off tab.
- Select the **On battery power**: Turn off device if not used for: check box and select value from the drop down menu.
- Tap **OK.**

## Scanning Bar Codes

- Ensure that a scan enabled application is loaded on the mobile computer.
- Aim the scan exit window at the bar code.
- Pull the trigger.
- For mobile computers with a laser scanner, ensure the red scan beam covers the entire bar code.

**Notes:**
Optimal scanning distance varies with bar code density and scanner optics
Hold the scanner away for larger symbols.
Move the scanner closer for symbols with bars that are close together.

## Inbound PO/Requisition Receipt

- Inbound shipments can be received at the dock location and then transferred to the storage location using a separate move task.
- When required, a user can bypass deposit to the dock location and deposit directly to the storage location (NOTE: The user will need to input the storage location versus the system directing the user to a storage location.)
**	****	**
**	**The steps described below should be followed for receiving inbound orders like POs and requisitions.

## Inbound PO/Requisition Receipt (cont)

- Login to the mobile terminal
- 2.	From the menu page, select ‘Receive’ and hit Enter
- 3.	The Receive window displays the list of available document types
- 4.	Select the ‘Purchase Order’ document type and hit Enter
- 5.	In the resulting screen, enter the Shipment # if known, or else hit the ‘Go’ button to display a list of all shipments that can be received. The user can then click on the relevant shipment to be received.

## Inbound PO/Requisition Receipt (cont)

- 6.	This brings up the receiving screen where the user should scan the receiving location and then hit ‘Go’
- 7.	The user then enters/scans the item ID of the item that is to be received and then hits ‘Go’.
- 8.	In the resulting screen, the quantity to be received is entered. This may or may not match the original ordered quantity for the PO/Requisition.  Also, the Receiving Disposition will default to RFI.  The user can modify this as required to other pre-defined dispositions. The user will input the Receiving Price (if different than the price that defaults from the Supplier Price value).

## Inbound PO/Requisition Receipt (cont)

- 9.	If there are more items to be scanned for the particular shipment, then step 8 can be repeated, else hit the ‘Done’ button until the shipment entry screen in step 5 is displayed.
- 10. If there are any more shipments to be received, steps 5 through 9 should be followed.
- 11. After a receipt is completed, the receipt can be closed through the Yantra console UI.

## (A) Figure 4.1.1 Inbound Receipt – Resource

- (B) Figure 4.1.2 Inbound Receipt – Menu Screen

- (A)

- (B)

## (C) Figure 4.1.2 Inbound Receipt – Document Type

- (D) Figure 4.1.3 Inbound Receipt – Details

- (C)

- (D)

## (E) Figure 4.1.4 Inbound Receipt – Shipment List

- (F) Figure 4.1.5 Inbound Receipt – Receipt Location

- (E)

- (F)

## (G) Figure 4.1.6 Inbound Receipt – Receipt Item

- (H) Figure 4.1.7 Inbound Receipt – Receipt Quantity (NOTE: Disposition Code defaults to RFI.  Also, Receiving
- Price will be added to this screen)

- (G)

- (H)

## Receipt of Items With Trackable IDs

- Items that have Trackable IDs are received in the same manner as non-Trackable items except that the Trackable ID is also scanned/entered during receipt.
- Depending on the quantity of items to be received, multiple Trackable IDs can be scanned one after another.

## Receipt of Items With Trackable IDs (cont)

- For purchase order receiving, the serial capture window appears only if the “Serial Numbers Tracked in Inventory” is checked in the ICBS Configurator. For returns receiving, the serial capture window appears if  “Serial Numbers Tracked in Inventory” or “Serial Numbers tracked in Returns and Outbound” is checked.
- The mobile terminal screen for receiving Trackable items is shown in the figure below:

## Figure 4.1.8 Trackable Items Receipt

- The Trackable number entered into the dialog box will correspond with the standardized Alpha-Numeric number established for that particular cache.

- (I)

## Receiving Screen-Tag Controlled Items

- Items that are tag controlled can be received in the same manner as non-tag controlled items except that the user will be prompted to enter tag information like manufacturer information during the receipt.
- The tag information screens for the mobile terminal are shown in the screen shots below:

## Receiving Screen-Tag Controlled Items (cont)

- (J) Figure 4.1.9 Inbound Receipt – Lot number Scan
- (K) Figure 4.1.10 Inbound Receipt – Kit ID Scan

- (J)

- (K)

## Receiving Screen-Tag Controlled Items (cont)

- (L) Figure 4.1.11 Inbound Receipt – Scan Last Tested Date
- (M) Figure 4.1.12 Inbound Receipt – Manufacturer Name

- (L)

- (M)

## Receiving Screen-Tag Controlled Items (cont)

- (N) Figure 4.1.13 Inbound Receipt – Manufacturer ID
- (O) Figure 4.1.14 Inbound Receipt – Model Number

- (N)

- (O)

## Trackable and Tag Controlled Receipts

- 	For receiving items that are both Trackable and tag controlled, like radio kits, the tag information will be:
- Scanned first and then the Trackable ID will be scanned. The screens shown in the previous sections for tag information and Trackable ID capture apply to this scenario also.

## Putaway Process for Inbound Orders

- 	Putaway tasks are automatically generated whenever there is a receipt at the warehouse.
-    Since a typical warehouse has several different locations, the putaway process first asks for a reference location to be scanned.
-    This reference location tells the system where the operator is located in the warehouse.

## Putaway Process for Inbound Orders (cont)

- 	Based on where the operator is located in the warehouse, the system presents the nearest putaway location to the user.

## Putaway Process for Inbound Orders (cont)

-    The following steps describe the putaway process using the mobile terminal:
- Login to the mobile terminal
- In the resulting menu, click on the “Task Controller” menu option

## Putaway Process for Inbound Orders (cont)

- In the next screen, the “Start Location” can be scanned.
- The ‘Equipment #’ field can be left unspecified.
- The start location is only scanned for reference purposes. It tells the system where the user is physically located in the warehouse, so that the nearest putaway task can be suggested.

## Putaway Process for Inbound Orders (cont)

- The item number can then be scanned in the resulting field. The system suggests the appropriate item to be scanned for the task at hand.
- If the item is Trackable or tag controlled, the user can scan one or more Trackable IDs in the resulting screen.

## Put away Process for Inbound Orders (cont)

- Finally, the location to put away the item can be scanned.
- The “Deposit All” button puts away the items to the final storage location.
- Note that the system will not prompt the user for a pick location, since the task is already associated with that location, where the item was originally received.
- If there are additional putaway tasks to be completed, the system will prompt the user again and steps 3-6 are carried out.

## The following screen shots illustrate the 

- Putaway process in ICBS

## (A) Figure 4.2.1 Inbound Putaway – Menu Screen

- (B) Figure 4.2.2 Inbound Putaway – Reference Location Scan

- (A)

- (B)

## (C) Figure 4.2.3 Inbound Putaway – Deposit Location Scan

- (C)

## Outbound Pick Tasks

- 	The outbound pick tasks are for outbound shipments for incident/other issues.
- 	The outbound pick tasks will be automatically generated when a shipment is created for the incident/other issue.
- 	On the AIT mobile terminal, the pick tasks will be split as two separate tasks – one for doing the actual pickup of the item from the pick location and another for doing the deposit (locating to a shipping area).

## Outbound Pick Tasks(cont)

- The following steps illustrate the processing of pick tasks for incident/other issues:
- Log into the mobile terminal
- Choose the “Task Controller” menu option on the resulting screen.
- Enter/scan the reference “Start Location” on the mobile terminal.

## Outbound Pick Tasks (cont)

- In the resulting screen, scan the pick location for the pick task.
- The system automatically suggests the pick location from where to pick.
- Hit the “Go” button
- On the next screen, scan the suggested item and quantity and hit the “Go” button.

## Outbound Pick Tasks (cont)

- If all the pick tasks have been completed, the system suggests the next deposit task.
- Scan the deposit location and item on the deposit screen and hit “Go” button. This will deposit the item into the shipping location
- This will complete the pick task cycle.

## Outbound Pick Tasks (cont)

-    The outbound pick task screen would need to display the following customized fields (not currently shown on the mock-up screens that follow):
- Issue Number – This should be displayed on the retrieval screen, along with item information, for all tasks associated with incident issues.
- Incident Number – This should be displayed on the retrieval screen, along with item information, for all tasks associated with incident issues.

## Outbound Pick Tasks (cont)

- Incident Name – This, too, should be displayed on the retrieval screen, along with item information.
- A button will be added, called “Issue Info” which will present the user with key information for the Issue such as Ship-To address and Account Numbers
- Because of the limited “footprint” of the mobile terminal screen, not all information on a full-sized issue screen will appear (e.g. If an issue has split account codes, there’s not enough room to show the additional codes)

**The following screen shots illustrate the pick cycle **
**for outbound shipments**

## (A) Figure 5.1.1 Outbound Pick – Reference Location Scan

- (B) Figure 5.1.2 Outbound Pick – Pick Location Scan

- (A)

- (B)

## (C) Figure 5.1.3 Outbound Pick – Item & Qty Scan (scan or manually enter Quantity)

- (D) Figure 5.1.4 Outbound Pick – Deposit Location Scan

- (C)

- (D)

## (E) Figure 5.1.5 Outbound Pick – Deposit to Ship Location

- (F) Figure 5.1.6 Outbound Pick – All Tasks Completed

- (E)

- (F)

## Ad hoc Move Requests 

- Ad hoc move requests that are created in the console will generate pick and deposit tasks that can be executed through the AIT mobile devices.
-  Ad-hoc moves may be created for several reasons, including movement of goods from the Receiving Dock to Storage or movement of product between two locations in storage.
- It is particularly useful if authorized users are manually consolidating inventory locations to conserve space.

## Ad hoc Move Requests(cont)

**The process for executing ad-hoc move tasks is described below:**
- Log into the Yantra Mobile terminal.
- Enter the reference location for the start location.
- In the resulting screen, scan the suggested pick location for the move task and hit “Go”.

## Ad hoc Move Requests (cont)

- On the next screen, scan the suggested item and hit “Go”. If the item is tag controlled and/or Trackable, then scan the lot attributes and Trackable IDs in the resulting screens.
- On the deposit screen, scan the suggested item and deposit location and hit “Go”
- This completes the move cycle.
-    The following screen shots illustrate the ad-hoc move process:

## (A) Figure 6.1.1 Ad Hoc Move – Pick Location Scan

- (B) Figure 6.1.2 Ad Hoc Move – Item Scan

- (A)

- (B)

## (C) Figure 6.1.3 Ad Hoc Move – Lot Number Scan

- (D) Figure 6.1.4 Ad Hoc Move – Batch Number Scan

- (C)

- (D)

## (E) Figure 6.1.5 Ad Hoc Move – Revision # Scan

- (F) Figure 6.1.6 Ad Hoc Move – Trackable ID Scan

- (E)

- (F)

## (G) Figure 6.1.7 Ad Hoc Move – Deposit Request

- (H) Figure 6.1.8 Ad Hoc Move – Tasks Completed

- (G)

- (H)

## Executing Count Tasks

- The ICBS mobile terminal can be used to perform count tasks like:
- Count pallets
- Count items in pallets and locations
- Count serial tracked items in a pallet or location

## Executing Count Tasks(cont)

- 	The execution of counts may be either user-directed or system-directed.
- 	In system-directed count tasks, the system suggests the count tasks to be executed and the user can scan the location or item to signify the acceptance of the count task.
- 	In user-directed process, the user chooses the count tasks that need to be executed.

## Executing Count Tasks (cont)

- 	The following steps describe the execution of the count process. This process assumes that the original count request has already been created in the system, using the ICBS console User Interface (the PC-based application)
- Log into the mobile terminal.
- On the menu list, select the “Task Controller” menu option.

## Executing Count Tasks (cont)

- Enter the start location as the reference location which indicates where the user is physically located in the warehouse.
- The count task for the location that is nearest to the physical location of the user is presented
- The user scans in the suggested location and the suggested item for the count task.

## Executing Count Tasks (cont)

- In the resulting screen, the user scans the count quantity and hits “Go”.
- The system then displays the count quantities. The user can accept the count or re-scan.
- If the user chooses to re-scan, the count tasks from step 4 will need to be performed again.
- If the user chooses to accept the count quantity and that quantity is different from what is present in the system, then variance tasks will be created

## Executing Count Tasks (cont)

- The variance tasks are completed in the same way as regular count tasks. The user can also record the inventory disposition and product class during the scan.
- The user then records the variance count task quantity and hits the “Done” button.

## Executing Count Tasks (cont)

- The system quantity as well as the variance count quantity would be displayed and the user can either accept the count quantity or re-scan.
- Once the user accepts the count quantity, the count result is recorded.
- The following screen shots illustrate the count process:

## (A) Figure 7.1.1 Physical/Cycle Count – Reference Location Scan

- (B) Figure 7.1.2 Physical/Cycle Count – Count Location Scan

- (A)

- (B)

## (C) Figure 7.1.3 Physical/Cycle Count – Item ID Scan

- (D) Figure 7.1.4 Physical/Cycle Count – Count Quantity Scan

- (C)

- (D)

## (E) Figure 7.1.5 Physical/Cycle Count – Complete Count

- (F) Figure 7.1.6 Physical/Cycle Count – Accept Count

- (E)

- (F)

## Executing Variance Tasks

- 	Execution of variance tasks is similar to the execution of normal count tasks.
- 	The following screen shots
- 	illustrate how variance counts are executed.

## (A) Figure 7.2.1 Variance Tasks – Location Scan

- (B) Figure 7.2.2 Variance Tasks – Inv Status Scan

- (A)

- (B)

## (C) Figure 7.2.3 Variance Tasks – Variance Qty Scan

- (D) Figure 7.2.4 Variance Tasks – Accept Count

- (C)

- (D)

## Returns Receipt

- Returns information needs to be entered in!
- This will be done at Business release 2.

## Returns Receipt (cont)

- A scanning device module to support cache return processes involves a considerable amount of customization to the Yantra application and has not yet been developed and tested.
- Due to returns being such a large business process within the cache system, it was determined, by the ICBS-R Steering Group, that this functionality needed to be developed.

## Returns Process (cont)

- Funding was consequently allocated to the development of the returns process using the scan devices.
- This functionality will  be developed in 2008 and will be available in a future release of the new ICBS.
- Due to the fact that this functionality is not, at this time, in the current business release, this PowerPoint will be updated to include the Returns Process at such a time when it does exist.