WA Implementation Guide
WA Implementation Guide
Advantage
Implementation Guide
Version 13.9
HighJump
(800) 328–3271
5600 W 83rd Street, Suite 600, 8200 Tower, Minneapolis, Minnesota 55437
www.highjump.com
© Copyright 2005–2019 HighJump. All Rights Reserved. Reproduction and distribution under license only.
This document and the software it describes are confidential and proprietary information of HighJump and its affiliated
entities and are copyrighted properties of HighJump with all rights reserved. Information contained herein is subject to
change at any time in HighJump’s sole discretion. Neither this information nor the software may be copied in whole or
in part without the prior written consent of HighJump.
This documentation and the related software programs are “commercial computer software” and “commercial
computer software documentation” pursuant to DFAR Section 227.7202 and FAR Section 12.212 (and any successor
sections). Use of this documentation or the related software programs, including reproduction and display of them, by
the United States of America and/or any of its instrumentalities, regardless of form, (collectively, the “Government”),
is allowed only as governed by terms of a valid license agreement with HighJump or one of its affiliated companies.
Under no circumstances shall HighJump be obligated to comply with any Government requirements regarding cost or
pricing data or cost accounting requirements. If any Government requirement might apply, you must notify HighJump
of the Government requirement and obtain a waiver or exemption for the benefit of HighJump before you may use this
documentation or the related software programs.
HighJump® is a trademark of HighJump Software Inc. All other marks are the property of their respective owners.
Table of Contents
This guide describes the tasks required to complete the remaining tasks of the methodology and
provides guidelines for assisting you. Each task includes a “to do” list, a list of ideas to consider, and
a brief overview about the task. If you are new to this project, read the HighJump Warehouse
Advantage system specification before you perform tasks outlined in this guide.
Audience
The primary audience of this guide is the Customer Implementation team including:
• Project Leader
• System Administrator
• Trainers
Note
The audience may also include an IS department.
The secondary audience includes HighJump employees that will answer your questions and
complete their responsibilities during implementation. They include:
• Project Leader
• Technical Leader
• Application Development team
Knowledge Requirements
To complete the requirements in this guide, designated personnel in your company must acquire a
working knowledge of some or all of the following.
• Personal computers, servers, and the HighJump Warehouse Advantage system
• Microsoft Windows
• Your company network and host
• Radio frequency equipment, document printers, and label printers
Contact HighJump
If you have any questions about HighJump Warehouse Advantage, send an email to
[email protected] or call (800) 328–3271.
Documentation Feedback
Send your comments to HighJump’s documentation department at [email protected].
The primary goal of this guide is to enable you to quickly and cost effectively implement your
HighJump Warehouse Advantage system with minimal help from HighJump. This guide has been
written with the following assumptions:
• Phase 1 - Preparation is complete
• System specification has been agreed upon between your company and HighJump
• You received the project plan from HighJump
HighJump and your implementation team will frequently communicate in the following ways:
• Weekly conference calls to discuss progress, issues, risks, and goals for the next week
• Mid Project Review at HighJump
• Acceptance testing
• Conference calls, letters, and e-mail
You and HighJump share the responsibilities for the required tasks. HighJump will provide you with a
project plan that details the tasks for you and HighJump.
Identify your responsibilities stated in the HighJump project plan and develop a detailed project plan
to implement these responsibilities. Your project plan should include a training plan and materials,
escalation procedures for hardware, software, and network problems, and implementation tasks.
To ensure that there is minimal risk of failure and the implementation is cost effective, it is important
that you and system users do the following.
• Meet project deadlines.
• Complete tasks thoroughly.
• Communicate the Implementation Project Plan within your organization.
• Set realistic expectations and do not expect to have the system run perfectly at initial startup.
• Understand and communicate escalation plans.
• Outsource tasks for which you do not have internal expertise.
• Train everyone affected by the system. This may include order entry clerks or expeditors who
occasionally remove inventory.
Role of HighJump
You play the major role during the implementation phase while HighJump is involved to the degree
that you desire. At HighJump, your order is organized and entered into the accounting system.
Hardware is purchased, tested, and shipped to you.
The HighJump development team meets to review the application, specifications, and work plans.
The development team tailors the application to meet the system specifications. As each process is
tailored, it is thoroughly tested. After all tailoring has been completed, a system test is conducted
using your data to verify that the processes interact properly with one another.
You and HighJump meet to perform the functional Acceptance Testing, during which HighJump
demonstrates that the tailored application performs as specified. HighJump then cleans and tests the
application again.
Throughout the entire implementation, HighJump will keep you informed of our progress.
If you are unable to perform any of the tasks outlined in this guide, HighJump may be able to assist
you on a daily fee basis. For more information, contact your HighJump project leader.
As part of the implementation, manage change in a way that ensures that your employees adjust
easily and your organization meets its goals.
To understand how change will affect your employees, take notice of these four phases of change:
Denial, Resistance, Exploration, and Commitment.
Denial
At first employees deny change by a lack of reaction to the change. Although there is a sense of loss
among employees, productivity continues for a while causing managers to believe the transition has
been accomplished. However, you may notice a productivity loss as they continue to use the system.
At this point management must recognize that employees' resistance is normal and the organization
itself must respond to it.
Resistance
In the resistance phase strong feelings about the change emerge, such as self-doubt, anger,
depression, anxiety, frustration, or uncertainty. Productivity slips, and people are often upset and
negative. Some may want to leave the organization.
Employees must be allowed to express negativity safely. Group rituals such as award ceremonies
and celebration parties help people share their experiences.
People will reach low points on the change cycle at different rates, but eventually most will shift to the
up curve.
For example, a material handler says, "Our old system did not do it that way, it got the work done just
fine. There is no way this system will work better than the old system. I am going to leave the
company if we do not go back to the old system."
Exploration
During the exploration phase, people draw upon their internal resources and creativity to figure out
their new responsibilities and to visualize their future.
This can be a creative, exciting time when people take on the change as adventure and form
powerful new bonds with their fellow "pioneers".
For example, using the old system, a material handler's performance was measured on a weekly
basis. The material handler tries the new system for a period of time and then wants to know right
away whether his performance has improved. The supervisor informs the handler that his productivity
has improved by 15%. The handler's excitement is infectious, causing other employees to ask about
their performance improvements.
At this point, people are ready to make stable, long-range plans and to act on them. They are willing
to recreate their mission, their roles, and their expectations. This phase typically lasts until the next
cycle of change begins.
For example, a material handler has been using the system for a several months and when
HighJump tells the material handler that they want to turn off the system to upgrade it, the material
handler says, "Don't turn the system off, I need to use the system today to meet my performance
numbers." This material handler who had a high level of denial early on has become a strong
advocate of the new system.
Without change, organizations stagnate. At any given time, people in your company will be in one of
these phases of change, and you need to be sensitive to which phase they are experiencing.
Consider
• Provide help to users during system start up and identify problems.
• Evaluate host interface to insure communication and a timely responsiveness.
• Validate host processing of transactions.
• What training must be given to people affected by the new system?
• What items, locations, or hardware must be labeled?
• What must be done on the host side to accept the transactions?
• How will you verify data integrity during the data conversions?
• Who will be responsible for verifying data integrity during the conversions?
• Who will be responsible for monitoring the transactions between HighJump Warehouse
Advantage and the host?
• How will your organization resolve problems?
Implementation Stages
• What other areas of the business are affected by moving to this stage?
• Describe the milestones that must be met for each stage and how to accomplish those
milestones.
• Perform simulation(s) for each stage until the simulation has been completed successfully.
• What must be done to prepare an area included to move to the next stage?
• What training must be given to all affected people in this stage?
• What items, locations, or hardware must be labeled for this stage?
• What must be done on the host side to download files to HighJump Warehouse Advantage?
• Who will be responsible for hardware, software, and network problems?
User Errors
• If a user receives items physically, but does not record it in the system, how should this be
handled?
• If a user picks an order physically, but does not record it in the system, how should this be
handled?
• If someone does a shipping confirmation from the host terminal without performing a pick in
HighJump Warehouse Advantage, how does the system handle this?
• How will "problem" users be handled?
• Who will review exception reports twice daily?
• Who will perform system-generated cycle counts once every two to four hours during
implementation?
Develop an Implementation Project Plan that describes how you will convert your existing warehouse
management system to HighJump Warehouse Advantage. Refer to the HighJump project plan and
the sample Implementation Project Plan included in this guide as guidelines to create your own plan.
This plan should include implementation tasks, training plan, user's guide, problem escalation plan,
disaster recovery plan, and a backup strategy.
Prepare a draft of the plan by the Mid-Project Review. The final Implementation Project Plan should
be complete by Acceptance Testing.
To Do
• Write user's guide
• Develop a training plan and materials for system users in the following subject areas:
− New business processes
− Hardware device configuration and troubleshooting
− HighJump Warehouse Advantage system administration
− Accessing data
Consider
• When and where will the training take place?
• Who will be training each business process?
• Who will be attending the training classes? Provide training for all employees that will be
interacting with the system in the course of their work.
• Who is writing the training plan?
• Develop training materials; for example, overheads for presenting information, hands-on
exercises, Instructor's Guide, and Student's Guide to help facilitate classroom training.
• How will you test the user's skills and understanding? Certify trained users using a series of tests
or simple responses to specific scenarios to determine who is capable of operating the system.
Reward employees who become successfully certified.
• Users should not only know how to efficiently do their job, but also know where to go and what
steps to take when confronted with system problems. Review problem escalation plans with
users.
• At the end of the training sessions users should feel confident they have a good tool to do their
job. Emphasize that HighJump Warehouse Advantage will equip workers with an effective tool to
improve accuracy and not replace their position.
• System Administrators should attend the HighJump System Administrator's class
• Keep unions informed about how HighJump Warehouse Advantage is changing employee
workload and working conditions.
Why Train?
The success of the HighJump Warehouse Advantage system depends on the knowledge base of
those who will be operating the system from day to day. User misuse and fear of the system are two
of the leading causes for startup and operation failure and cascading mistakes. Without proper
working knowledge of the HighJump Warehouse Advantage system, your employees' productivity
may be lowered.
Choose individuals who are natural leaders and shown respect by their coworkers. The trainers
should have the ability to effectively share their knowledge with the remainder of the staff. Choose
enough trainers to cover a multi-shift operation.
Develop a training plan and materials for training users about the HighJump Warehouse Advantage
system. Include the training plan as part of the Implementation Project Plan. You may also need to
train system administrators and other users outside the warehouse site that interact with the system.
For example, order-entry employees might need to learn a new way to view the status of orders. After
you complete the training plan, HighJump will review the plan to ensure successful implementation.
Include the following in the training plan:
• A schedule including employee name, time, date, and the business processes that each
employee needs to be trained on.
• Classroom instruction covering the proper business context of each process in the HighJump
Warehouse Advantage application and demonstrations.
• Hands on time. Set up practice scenarios for users to try.
• Written certification test that verifies that users will know how to perform their job functions when
the system is brought live.
• Retraining for users who do not become certified.
To Do
• Write the user guide.
• Take the final draft of the user's guide to HighJump for acceptance testing.
Consider
• Put HighJump Warehouse Advantage application processes in the context of your business
processes.
• Will material handlers need to perform multiple tasks at the same time?
• Include suggestions for resolving possible problems.
• Integrate the user's guide with the training plan
The user's guide is a procedural document with reference information that describes how to use your
tailored HighJump Warehouse Advantage system. Use the user's guide during user training and after
the system is running. The user's guide is a companion document to HighJump Advantage Platform
Administrator's Guide.
The following are examples of topics you may want to include in your user guide.
• Introducing our warehouse management system
• Understanding our inventory
• Using and maintaining the RF equipment
• Logging on to a reader
• Procedures for each application process, for example, Putting Away Stock or Picking Parts Show
the sequencing of screens for menus and prompts.
Resolve Problems
To Do
• Write a problem escalation plan for software, hardware, and network problems
• Take the final draft of the Problem Escalation Plan to HighJump for acceptance testing
Consider
• How will problems be tracked?
• Who should be given the information about a problem at each level of problem solving?
• Use a step by step procedure to explain how to escalate problems within your organization
• What information does a problem solver need about a problem?
During implementation and while the HighJump Warehouse Advantage system is running you may
encounter problems with software, hardware, or network connectivity. You may also experience
performance problems between the HighJump Warehouse Advantage application, servers,
workstations, and host systems. It is important to determine ahead of time how you will resolve these
problems using troubleshooting techniques. To minimize system down time, include a Problem
Escalation Plan in your Implementation Project Plan which describes how to solve and escalate
problems.
During implementation you and HighJump will conference periodically (usually weekly) to check on
the status of unanswered problems and work toward answering them. Follow your escalation plan
when a problem arises. Contact HighJump if you cannot solve the problem then you can escalate the
problem to HighJump.
If you are unable to solve a problem on your own using your escalation plan, you can escalate this
problem to HighJump before the 6-month warranty period expires. The hardware warranty period
begins about one month after the hardware is shipped. The software warranty period begins one
month after the software is installed.
After the warranty expires, you can elect a support plan for your system. Plans range from no support
(pay as you go) to our Diamond Full Service plan. The Diamond Full Service includes 24-hour/day
pager support.
When you escalate a problem, HighJump keeps track of problems so that they do not remain
unanswered. To insure that all problems are resolved in an appropriate time frame, all incoming calls
are categorized according to mutually agreed upon severity level. Response from HighJump is based
on the assigned severity levels.
To Do
• Create a strategy document explaining how to backup the HighJump Warehouse Advantage
software, database, transaction log, and data
• Take a final draft of the backup strategy to HighJump for Acceptance testing
Consider
• How often to do you want to back up the files on the Application Server?
• Where do you want to store your backups?
• For information about data recovery and database restoration, refer to the SQL Server or Oracle
documentation
• Make contingency plans to run HighJump Warehouse Advantage on one server instead of two.
For more information, refer to HighJump Advantage Platform Administrator's Guide.
HighJump Warehouse Advantage and Transaction Log backups are coordinated as an overall
backup strategy for HighJump Warehouse Advantage. When you back up the HighJump Advantage
Application Database (AAD) and transaction log, a copy of its tables, data, and user-defined objects
is created. HighJump Warehouse Advantage stores the HighJump Advantage Application Database
(AAD) and Transaction Logs on different devices and automatically makes regular backups of the
HighJump Advantage Application Database (AAD) and Transaction Log. The Transaction log backup
is performed more frequently than a HighJump Advantage Application Database (AAD) backup.
In case of media failure, a disk failure for example, you can restore HighJump Warehouse Advantage
by loading the most recent HighJump Advantage Application Database (AAD) backup and then load
all the transaction log backups (in order) made since the database backup. For more information
about restoring HighJump Warehouse Advantage see HighJump Advantage Platform Administrator's
Guide.
Backup Data
After the HighJump Advantage Application Database (AAD) and Transaction Log backups are made
to the Database Server, HighJump Warehouse Advantage copies the backup data to the Application
Server. If you use a tape backup system to back up your Application Server, develop a tape rotation
schedule to provide multiple backups to protect your data. Ensure backups are occurring. Here is a
suggested four-week daily rotation:
• Keep the current week's tapes on site (one tape for each day ), replacing a tape each night
• At the end of the week, take the seven tapes to an offsite location and bring back seven of the
oldest tapes
• Remove a complete backup tape every four weeks and replace the tape in the rotation. Save the
removed tape as a monthly tape. Do not use tapes more than four times.
To Do
• Identify employee work groups. Define the processes that will be available on each workgroups
RF unit menu.
• Design menus for each workgroup using the Blank Application Menu Security Worksheet.
The HighJump Warehouse Advantage system allows you to plan the application process menus. As
shown in the following example, divide your employees into workgroups according to the application
processes that those employees will be authorized to use. Generally, one employee is assigned to
the System Administrator group, several to the Supervisor group, and several to other groups. You
can have a workgroup of one and an employee can be a member of several groups.
Workgroup Name Employees
System Administrator Sam Krapels
Pickers Bob Short
Richard Smith
Betsy Jones
Jose Gonzales
Victoria Principle
Receivers Richard smith
Betsy Jones
After you decide your workgroups, design application menus for each workgroup. You can add as
many options as you want to each menu. If the number of options exceeds 5, those options are
displayed on subsequent screens. From each option you can add a submenu with additional menu
options.
In the following example, the Main Menu shows the first five options. To view the Receipts submenu,
you would choose option #1 and press Enter.
Main Menu Receipts
1 Receipts 1 Unload Inbd Order
2 Putaway 2 Transfers
3 Replenishment 3 Vendor Receipts
4 Order Pick 4 Staged Receipt
5 Pack/Audit 5 Receipt from Prod
OPTION OPTION
To view the Main Menu options 6 and greater, you would type F8.
Main Menu Main Menu
1 Receipts 4 Order Pick
2 Putaway 5 Pack/Audit
3 Replenishment 6 Load/Ship
4 Order Pick 7 Inv Control
5 Pack/Audit 8 Movement
OPTION OPTION
Design a single menu for each workgroup, or structure them into a series of submenus. Duplicate the
following menu security worksheet and list the workgroups, menu name, options, and code. Assign a
unique code to each workgroup.
Workgroup Name Menu Name Menu Options Code
System Administrator Main 1. Quality Control 01
2. Cycle Counts
3. Inventory Status
4. Inv Adjustments
System Administrator Inv Adjustments 1. Adjust by Location 02
submenu
2. Adjust by LP
3. Decrement by Item
4. Increment by Item
Pickers Main 1. Picking 03
2. Movement
3. Inventory Status
4. Quality Control
To Do
• Create a disaster recovery plan.
• Take a final draft of the disaster recovery plan to HighJump for Acceptance Testing.
Consider
• Do you know the cost of reconstructing your company’s financial, personnel, and other business
data?
• Do you know if your business insurance would cover any or all of the cost of replacing data?
• Do you know how long it would take to reconstruct your business data? How would this translate
into lost future business?
• Do you know the cost per hour of server downtime?
• What data and how often do you need to back up?
• How will you save critical computer or other hardware configuration information that is not saved
during normal tape backups?
• What data needs to be stored on and off site, and how should it be stored?
• What training is required so server operators and administrators can respond quickly and
effectively if an emergency occurs?
• Who should be contacted?
• What does each employee need to do to recover from the system failure quickly?
• What preventative measures are in place to minimize down time?
• What should be done if the servers have hardware problems?
• What should be done if the RF network goes down?
• What should be done if the database crashes and needs to be recovered?
Because there are many articles in magazines and entire books that discuss disaster planning and
recovery, this section does not go into detail about any aspect of disaster planning. Instead, it
describes topics that you should think about in your planning. We recommend the following books
about disaster planning:
• Disaster Proof Your Business: A Planning Manual for Protecting a Company's Computer,
communications & Records Systems and Facilities.
Geoffrey H. Wold, Robert F. Shriver, 1991.
• Disaster Recovery Planning: For Computers and Communication Resources
Jon William Toigo, 1996.
Just as every business needs to plan and budget for future growth, you need to have a plan for
dealing with total or partial loss of business data. To determine what provisions to make for partial or
complete loss of data, determine the approximate dollar and manpower cost of replacing the data
your company uses.
HighJump Warehouse Advantage may cease operating for the following reasons.
• A corrupt database
• Network failure
• Power spike
• Hardware failure on the database server or application server
• Theft
• System tampering
In case one of these events occurs, you need to recover and bring HighJump Warehouse Advantage
back online quickly and minimize operation downtime. It is important that you plan for these events by
developing a disaster recovery plan that describes step by step procedures. You should keep copies
of your disaster recovery plan on site and off site, and key personnel should consider keeping a copy
at home. For more information about recovering from a system failure, see HighJump Advantage
Platform Administrator's Guide.
Acceptance Testing
To Do
• Validate that the application functions match the system specifications.
• Verify that data flows through the system according to the system specifications.
• Identify any changes to the system that deviate from the system specifications.
• Identify any errors in the system.
• Review implementation project plan, user's guide, training plan, problem escalation plan, disaster
recovery plan, and backup strategy.
• Sign the System Acceptance Agreement.
The HighJump project team meets with you at HighJump to perform Acceptance Testing. During
Acceptance Testing, HighJump performs some tests using a test HighJump Warehouse Advantage
system with a simulated host interface using the flat files that you provide.
HighJump will evaluate whether the plans are feasible. HighJump will also discuss any special
conditions that may arise that are not in your system specification and were not determined during
Phase 1-Preparation.
HighJump will use change order forms to track any system changes that result from the acceptance
testing. Changes may require additional tailoring charges and may affect the system installation date.
To Do
• Verify that the barcodes scan properly before placing labels on items and locations.
• Label items that are not vendor labeled.
• Label warehouse locations.
Consider
• Will any items have barcodes from vendors?
• Will you be able to label all locations?
• Are there structures to put barcodes on, for example, hanging signs?
• Will you need to paint lines for floor storage areas?
• Will you need to outsource this work?
• Are finished goods bar-coded? Is the barcode readable?
• Do the barcodes match your Item Master list?
• What are the scanning distances for each type of label or location type?
Prior to receiving the servers from HighJump, prepare an area at your warehouse site for the servers
and the HighJump installation team's working area. Select an area in your warehouse that is
electrically clean and relatively dust free. This area should be secure from theft or tampering.
The installation team visits your site after you have installed the hardware. They install the HighJump
Warehouse Advantage software and ensure that your system is operating correctly. The installation
team sometimes requires 24-hour access to the servers.
Consider
• Assigning each RF unit to an individual so that individual is responsible for taking care of their
own RF unit.
• Locking up RF units after each shift
• Making battery chargers and extra batteries available.
At the end of every shift, your material handlers will need to charge the batteries and store their RF
units and scanners.
To Do
• So that the HighJump Warehouse Advantage system operates at peak performance over your
network, make sure that the network has a minimum throughput of 4 Mbps/second; 10
Mbps/second is ideal. If the network is less than 4 Mbps/second, upgrade or replace it.
• Order network cabling to ensure that it is delivered to your site and you can run the cabling
before the servers arrive.
• Set up all network printers and provide the necessary printer drivers.
• Install and test the cabling to ensure access to HighJump Warehouse Advantage via your
network. Send data between the servers and workstations.
• If you are using 2.4 GHz network, use the ping command to verify that the access points are
communicating with HighJump Warehouse Advantage.
Consider
• Use an experienced person to install the network cabling.
Your company network will provide the vehicle for connecting the servers, RF equipment, and
workstations that make up your HighJump Warehouse Advantage system. You may need to expand
your network by installing additional network cabling. For more information about network installation
and facility maps, refer to the Intermec Spread Spectrum Site Survey Report.
To Do
Ensure that clean power is in close proximity to the equipment.
The servers, RF units, controllers, and printers require power to operate. This equipment should not
share circuits with equipment that will generate dirty power. Clean power is crucial to proper
maintenance of your HighJump Warehouse Advantage system. An uninterrupted power source is
ideal, but the following common disturbances may be beyond your control.
Disturbance Description and Results
Sags / brownouts The most common disturbance usually caused by start-up power
demands of electrical devices or by voltage levels lowered by
power companies to accommodate increased power demands in
hot weather.
Results: possible system crash, frozen keyboards, reduced
efficiency.
Blackout Complete power loss, caused by excessive demand on power grid,
lightning storms, car accidents, etc.
Results: system operation halted possible loss of data.
Spike / Impulse A sudden, dramatic increase in voltage usually due to lightning
strikes.
Results: data loss and/or extreme hardware damage.
Surge Short-term voltage increase caused by high-powered electrical
motors (air conditioners, etc.) in the vicinity. Voltage surges through
power line as equipment is switched off.
Results: premature failure and stress on computer components.
Noise: Electro-Magnetic Intermittent or chronic electrical noise that may be caused by
Interference (EMI) or Radio lightning, generators, radio transmitters, etc.
Frequency Interference (RFI)
Results: glitches and errors in executable programs and data files.
Power disturbance information taken from American Power Conversion’s, "The Problem with Power.”
Consider
Consider finding a cool, dry, place where boxes will maintain their form and not pose a fire hazard. If
you ever need to ship a piece of equipment to HighJump that needs repair, it is recommended that
you ship the equipment in its original box and packaging.
To Do
• Develop and test data files from the host program that will be used for the live system.
• Send test data files to HighJump for verification.
• Test files sent from HighJump using the host program that will be used for the live system.
• Set up a Windows workstation and, to the extent possible, test the connectivity between your host
and Windows.
• Set up and verify that your host appears as a file server on your network (if required).
• Create and test the FTP scripts to import and export files (if required).
Consider
• Ensure that the test files contain accurate and complete data that represents all possible
permutations of your data.
• Use the host program that will be used for the live system to test files from HighJump.
Program your host interface to accept this data so that your host can accept inventory, invoice, and
transaction data from HighJump Warehouse Advantage. You also must download files to HighJump
Warehouse Advantage. Ensure that these files contain accurate and complete data that represents
all the possible permutations of your data.
Your system specification lists file definitions, record layouts, and rules required to program the
interface for downloading and uploading data. HighJump may also tailor the HighJump Warehouse
Advantage application to send or receive data to and from your host.
HighJump will upload test files for inventory, invoicing, and transaction data to your host. Verify that
your host can accept these files.
To Do
• Set up Application and Database Servers.
• Set up workstations to access the servers on the network.
• Set up network printers.
• Set up RF equipment.
• Run and connect cables and attach the computers to the network and/or host system (if
appropriate).
After receiving and testing the hardware, HighJump ships the hardware to you. You are responsible
for properly placing the hardware.
Refer to the Intermec Spread Spectrum Site Survey Report for more information about placing the RF
equipment. HighJump personnel and your System Administrator will need easy and immediate
access to the hardware locations when HighJump visits your site.
To Do
• Place a small network hub near the Application Server and Database Server in case you need to
run the servers outside the network if your LAN/WAN is not functioning or performing well
enough.
• Create drive mappings using "K:" for workstations that access the Application Server.
• Create drive mappings using "M:" for workstations that access the Database Server.
• Setup user logins and passwords for user menus using HighJump One Platform.
• Set up directory and file permissions (as required).
• Set up a separate dial-in for HighJump to access the Application and Database servers.
• Set up HighJump Advantage Commander Permissions.
Consider
Neither server can be a Domain Controller or the backup Domain Controller in your company
network. Set up another server as your Domain Controller if you wish to use the Windows domain
security.
Permissions
HighJump Warehouse Advantage allows the system administrator to setup user permissions for
HighJump Advantage Commander menu options. This capability allows you to restrict access to one
or more HighJump Advantage Commander options for a single user. If you add or remove menu
options for a user, these options still appear in the menu structure when that user logs onto
HighJump Advantage Commander. If a user attempts to click an option to which he/she does not
have access, HighJump Advantage Commander displays a message stating that the user does not
have permission.
For more information about setting up HighJump Advantage Commander user permissions, refer to
HighJump Advantage Platform Administrator's Guide.
HighJump Warehouse Advantage Users need access to %HJSDIR% and all the subdirectories to
use the software. If you want to increase your security you can set directory and/or file read /write
permissions for devices communicating over the network including:
• Servers
• Virtual Terminal
• Queries, jobs, and reports from Remote HighJump Advantage Commanders
File and directory permissions are required for defining and performing Queries, Jobs and Reports
using a remote HighJump Advantage Commander.
Network Security
HighJump requires that you setup two user permissions for our project team to log onto your network
24 hours a day, seven days a week. The project team needs access to the Application and Database
Servers at all times. Please provide HighJump with a list of the User IDs and passwords.
Configure Menus
To Do
• Add the menu names to HighJump One Platform.
• Add the employees to HighJump One Platform.
Add the employees and menu names to HighJump One Platform. Assign a code and menu level to
each Employee record. The Menu level is the same as the Menu ID under the Menu option.
For more information about HighJump One Platform, refer to HighJump One Platform Administrator’s
Guide.
To Do
• Configure and verify that all hardware components are operating and communicating properly.
• Assist with the software configuration and host integration.
• Prepare test data.
• Schedule trainers for training.
After you install the hardware HighJump visits your warehouse management site to integrate the
hardware and software and check the network communications between hardware components,
software components, and the host interface.
Make arrangements to have the employees (involved in the installation) and the System
Administrator present at the HighJump site visit.
Once the system is installed and tested, train your trainers. HighJump also offers a comprehensive
training class that system administrators may want to take prior to this site visit.
When HighJump leaves your site, all aspects of the system are functioning.
To Do
Execute your training plan.
During and after the HighJump site visit, the trainers train the workgroups about system operation
that includes classroom as well as actual operation of the system on the warehouse floor. Each
workgroup should have the opportunity to use the system continually for several days before a
system simulation begins.
Integrate user training and simulations by running staged implementations. When you train the users
about the business processes follow these general steps.
• Train the workgroups who will be using business processes included in stage 1.
• Run simulations of stage 1 until users are running these processes live.
• Train the workgroups about the business processes included in stage 2.
• Run simulations for stage 2 until users are running these processes live.
• Repeat this process for each stage until your entire application is live.
To Do
• List the problems that you encounter.
• Identify the causes of problems.
• Fix the problems.
• Repeat the simulation until no problems are encountered.
• Verify that host transactions are processed correctly.
Consider
• When do the simulations take place?
• Who will be involved?
• What training will users need?
• Ensure that the inventory balances on your host and HighJump Warehouse Advantage are in
sync
• How do you measure success after a simulation? Do you have company specifications or
milestones?
Simulations are short, planned attempts to bring the HighJump Warehouse Advantage system live.
Users run the system as if it were just another "day in the life" of their business. The simulation tests
are broken down into stages, with certain application processes implemented at the same time. Once
each stage is running separately on its own, run the system in full production for a period as short as
one shift. If the simulation is flawless then the system can go live. If a simulation flushes out
significant system, employee skill, or process problems, then you can halt the simulation. Analyze
and correct the problems, and run each simulation repeatedly until no major issues arise and
everyone is confident that the application processes in each stage run smoothly by themselves.
To Do
Run the full system.
Consider
• Perform a productivity analysis.
• Perform a work flow analysis.
• Is HighJump Warehouse Advantage meeting your cost justification goals?
• Compare HighJump Warehouse Advantage inventory vs. host inventory.
• Check your performance standards to determine whether HighJump Warehouse Advantage
achieved these standards.
• Check to see if the orders filled by HighJump Warehouse Advantage were also filled at your host.
• Perform the cycle counting process often (hourly at first) to keep inventories accurate.
Once your HighJump Warehouse Advantage system is live, monitor your system. If you experience
problems while the system is running, track, resolve, or escalate those problems according to your
escalation plan. Ensure that backups, transaction files, and consistency checks are occurring as
planned.
Date: 4/15/16
This Implementation Project Plan will enable Mountain Ware employees to successfully implement
the HighJump Warehouse Advantage system in a timely and cost effective manner with as little
distribution volume degradation as possible.
The Implementation Project Plan is divided into two stages. Each stage will implement specific set of
application processes into the Mountain Ware distribution system while achieving important
milestone(s). Mountain Ware will perform simulation(s) for each stage until the milestone(s) has been
completed successfully.
Stage 1
Stage 1 of the implementation plan involves the successful integration of the following processes by
the material handlers into the Mountain Ware business system:
• Introduce the HighJump Warehouse Advantage system to Mountain Ware employees.
• Process the finished goods into the warehouse.
• Remove the finished goods using a decrement inventory process.
• Integrate the following processes into the Mountain Ware business system.
− Receipt from Production
− Move
− Inventory Adjustment by Location
− Inventory Adjustment by License Plate
− Inventory View by Location
− Inventory View by Item
− Cycle Count
− Location Status
− Physical
− Hold by License Plate
− Hold by Item
− Release by License Plate
− Release by Item
− Decrement Inventory
Stage 2
Stage 2 of the implementation plan involves the successful integration of the following processes by
the material handlers into the Mountain Ware business system:
• Introduce the picking process to specific users in each shift. Other users on each shift will use the
current system and the processes learned in Stage 1.
• Switch to the HighJump Warehouse Advantage system for all users using the picking processes.
• Integrate the picking, loading, and shipping processes.
Milestones
• Inventory accuracy by location.
• All employees are trained and certified on the above processes.
• No open issues with the following:
− Converting from existing picking/loading/shipping processes to those used in the HighJump
Warehouse Advantage system
− Host processing of the transactions generated by the above processes
− Picking rules
− Software and hardware support escalation within Mountain Ware
− Application processes
Vendors on Site
GTE - Terminate T1 line 12/3/16 Vendor unlimited
Intermec 12/4/16 - Intermec
12/5/16
Downtime
System 36 will need to be brought down, up to 1
hour downtime
AS/400 will need to be brought down, up to 1
hour downtime
3274 controller will need to be brought down
At the end of each training session you will be required to take a written certification test to make sure
that you know how to perform your job functions when the system is brought on-line. If you do not
pass a test for a certain process you will be retrained in that process.
You are required to attend all of your assigned sessions. If you are unable to attend a session, notify
your supervisor.
Session Trainer Work Group Date Time Location
Stage 1 Sean Connery Pickers 1/2/17 8:00 a.m. Training room /
Processes - Warehouse Floor
Picking
Stage 2 Bruce Willis Receivers 1/3/17 8:00 a.m. Training room /
Processes - Warehouse Floor
Receiving
Exception reports Pamela Team Leaders 1/10/17 8:00 a.m. Training room /
Anderson Warehouse Floor
Cycle counting Michael Team Leaders 1/12/17 8:00 a.m. Training room /
and movement Douglas Warehouse Floor
Hardware Clint System 1/22/17 8:00 a.m. Training room
configuration Eastwood Administrator
R&R Report Writer Richard Gere Team leaders 1/23/17 8:00 a.m. Training room
and Supervisors
Customer Service Clint Customer 1/23/17 10:00 a.m. Training room
Changes Eastwood Service
Representatives
Production James Bond Planners 1/23/17 1:00 p.m. Training room
Planning Changes
Monitoring the Billy Bob System 1/5/17 8:00 a.m. Training room
system Administrator
Accessing Data Clint System 1/24/17 8:00 a.m. Training room
Eastwood Administrator,
Team leaders
and Supervisors
System Simulations
Simulations are short, planned attempts to bring the HighJump Warehouse Advantage system live.
We have broken down the simulation tests into two stages; each stage includes a group of
application processes implemented at the same time. We will train each workgroup about the system
and the application processes for which they are responsible. Refer to the training schedule in this
plan.
We simulate the application processes of each stage as if it were just another "day in the life" of our
business.
If we experience problems during the simulation we will stop the simulation. We will then analyze and
correct the problems, and run each simulation repeatedly until no major issues arise and everyone is
confident that the application processes in each stage run smoothly. Once each stage is running live
and meets our milestones described earlier, we will begin work on the next stage.
Table of Contents
The manual is laid out to provide the user/reader a systematic approach to learning the functions and
processes related to the warehouse management system as applied to a storeroom. The Sections
are presented in the same order as the menu layout for users of the warehouse management
system.
Terms and definitions are explained. A comprehensive review of the terms should be completed
before advancing to the subsequent sections covering the storeroom operations. Review all
subsections to understand the storeroom processes and impact on information systems.
Conventions
<ENTER> -Anything enclosed as shown means an action, for example, pressing the Enter key.
[1234567] -Anything enclosed in square brackets indicates data that is typed or scanned in using
information from a bar code.
Bar Code Scanner -Device for scanning bar codes. Scanning is an alternative method to key entry
used for entering data into a system.
Bin -Representative of a storeroom location within the MACPAC environment. Example: 3L1002,
3L1001,...Different bin locations as seen in MACPAC.
Directed Move -Action within the Warehouse Management System that allows a user to log moves in
order to transfer material from one location to another.
Location -Storage location for material as controlled by Warehouse Management System. Example:
30101, B23, H1, 20105, B6
RF -Radio Frequency. The transaction managers used in conjunction with the Warehouse
Management System are wireless hand-helds that utilize spread spectrum RF technology.
TM -Transaction Manager. The transaction manager is the hand held device that communicates
between the user and Warehouse Management System. A bar code scanner may be built in or
attached to the transaction manager.
Scan Sheet -Sheet that contains bar codes representative of actions required by the transaction
manager. Used as an alternative to key entry.
Shelf -Storage area in the main storeroom that is the large racks.
Stock Put-Away -Refers to the action of receiving material into the storeroom and placing in a
designated location. Material can be raw material, subassemblies and received from any source
outside the storeroom.
Note
Remember this rule for all storeroom actions.
Every time material is physically received, picked, moved, or counted there is a
corresponding transaction that must take place in the Warehouse Management System and
MACPAC.
There are very few exceptions to this rule, those of which you will learn later in this training manual.
Basic flow for the storeroom is shown below.
However, one must know the process steps associated with controlling the incoming/outgoing
material and the internal storeroom operations, to fully understand the complexity of operations.
As one can see, there are more than several associated tasks for each type of general storeroom
process.
The Warehouse Management System is the interface between the MACPAC system and the
transaction managers. The Warehouse Management System receives all the pull requirements
generated by MACPAC and organizes and prioritizes the work so the storeroom can run efficiently.
Since the Warehouse Management System is an interface between the transaction managers and
MACPAC, it is configured to help step the users through different storeroom processes and post the
related transactions to MACPAC.
Bar code scanners are used with the transaction managers (TM) as a method of quick and accurate
data entry. In many cases, the data entered into the TM is verified by the Warehouse Management
System to ensure system integrity and accurate updates to MACPAC and SUPRA.
Each user has a log on ID and password and is assigned certain menu access based on level and
completion of training.
The Warehouse Management System also provides the ability to print reports, create custom reports
and queries, maintain data in the Warehouse Management System database, and control work
priorities.
The TM are hand held computers and should be treated in a manner consistent with using any type
of electronic equipment. The TM are designed for industrial use but repeated drops of the unit may
result in damage. If the unit is not operating properly or it is dropped, please report it to the system
administrator for inspection and diagnosis of the problem.
Mountain Ware trainers should use these basic rules and procedures to teach employees how to
execute the application processes using the handheld RF unit.
• If you move it, scan it.
• If you don't know, ask. These procedures affect inventory accuracy. It is not always clear which
process to use; however, it is critical that the right process is used. For example, materials could
be moved from production back to the warehouse by transfer in, move or return to inventory. The
correct process is return to inventory.
• The handheld will send messages to the screen prompting you to take certain actions or provide
certain information. You respond by pushing buttons on the handheld or scanning bar codes.
• F Keys. F1 backs up a screen. (You cannot back out of some screens.)
• Some items (such as pallets, bulk oil, and petroleum equipment) are not covered under the
warehouse management system.
A fully charged battery should last approximately eight hours. Always start your shift with a freshly
charged battery.
A battery signal on the TM indicates the charge is low and the battery should be replaced
immediately. Turn off the Transaction Manager before swapping the battery out. Charging batteries is
done using the appropriate Antares™ charger. For more information, see the manual.
A person will be assigned the task of battery upkeep, which will ensure the storeroom always has a
ready supply of charged batteries.
Business Processes
Note
Error messages may include "invalid user ID", "bad length password", "invalid location" or
"invalid loc type.” These errors may be resolved by entering correct information.
Notes
Error messages may include invalid P.O. number, invalid item number, item number not on
P.O., quantity too great, bad input, and cannot be zero.
You can add items to a P.O.
Care must be taken when correcting errors in quantity.
Note
Errors messages may include quantity too great, bad input, invalid item number, invalid
printer name, item already on forklift, input required or location not found.
Notes
Error messages may include quantity too great, bad input, invalid item number, invalid printer
name, item already on forklift, input required or location not found.
The bill of material number will not be validated in phase one.
You have the option of putting some or all of an item in this location. If you don't put all of the
item in the first location, you will put the rest in another location.
Note
In Phase 1, the usual picking documents are used. In Phase 2, picking documents are
scanned.
Note
You can put some or all of a quantity in this location. If you do not put all quantity in the first
location, you must put the rest in another location.
This problem escalation plan provides methods for solving and escalating common problems within
our organization. The plan lists the problems, a recommended solution and the escalation procedures
for team leaders and supervisors. If you encounter a problem with HighJump Warehouse Advantage
refer to this plan to determine how to solve and escalate the problem.
If you are unable to solve a problem with HighJump Warehouse Advantage using your escalation
plan, you can escalate this problem to HighJump. The hardware warranty period begins about one
month after the hardware is shipped. The software warranty period begins one month after the
software is installed.
When you escalate a problem, HighJump keeps track of problems so they do not remain
unanswered. To insure that all problems are resolved in an appropriate time frame, all incoming calls
are categorized according to mutually agreed upon severity level. Response from HighJump is based
on the assigned severity levels.
During implementation and after the system is live, document each problem in a problem log. You can maintain the log in a database,
spreadsheet, or word processing file. For each problem refer to the Problem-Solution table to obtain a solution. Record a description of the
problem, assign a problem number, action items, responsibility, and the current status, in the log. HighJump also keeps logs of problems that
you escalate to HighJump. HighJump will periodically request a problem status report from you. Create a log similar to the following.
Description Problem Action Items Responsibility Status
ID
The Order Import Process rolls 1 Redesign how host interface functions. Record interface HighJump and Closed
files but does not import the file, design in change order # 10. Mountain Ware
leaving 0 records imported in the
Increase the number of roll files from 10 to 100. This will
system log HighJump Advantage
allow a longer history of the files to be retained and
Application Database. The system
easier recovery.
also tries to start the Order import
file process but cannot and logs Install a new PD_FILE.DLL file that the Advantage
the message in the system log file. Workflow Engine software uses. This DLL file changes
This problem was not found in the how the HighJump Advantage Workflow Engine
Problem-Solution Table. processes triggered files.
Start the HighJump Advantage Workflow Engine.
User scans a location ID and the 2 Refer to Problem-Solution table. Supervisor Open
RF unit displays the message
Invalid Location.
Logging on an RF
unit
The user enters an Enter your User Id again including Log onto the RF unit. If this does work, Try to log-on to the RF unit with their
ID on their RF unit. the Warehouse Name. If this does watch the employee as they are trying User Id. If this does not work, run the
The RF unit displays not work, contact your team to log onto the RF unit for any Employee Query to make sure they are
the message Invalid leader. problems. If you cannot find the trying to use the correct User Id. If they
User Id. problem and cannot get the employee are and you still cannot get the RF unit
logged onto the RF unit, contact your to accept the Log-On, contact the
Supervisor. System Administrator.
The RF unit displays Log off of the RF unit and log on Using HighJump Advantage
the following again. The user may need to log Commander, run the Sign User Off
message: Log Off of on and then back off. If you cannot Radio Query to Log-Off the User.
RF unit [ ]# find the radio you need to log off
of, contact your Supervisor.
The user enters a Enter your password again and Log onto the RF unit at the User ID Run the Employee Query to make sure
password on their press enter. If this does not work Prompt and then again at the Password they are trying to use the correct
RF unit and the RF contact your Team Leader. prompt. If you can log onto the RF unit, password. If they are, try to enter the
unit displays Invalid have the radio operator enter their password for them. If this does not
Password. password into the RF unit while you are work, contact the System Administrator.
watching. If you cannot find any
problems with the password, contact
your Supervisor.
User enters an This number is incorrect. Scan or Make sure the employee is entering an Check your list to make sure that the
equipment number. enter a useable forklift, hi-lift or equipment number for a useable piece equipment number is a valid. If the
The RF unit displays Pallet Jack number. If this does of equipment. Scan or enter the number is correct enter the number
Invalid Location. not work contact your Team equipment number again. If this does yourself. If this does not work, contact
Leader. not work, contact your Supervisor. the System Administrator.
The RF unit displays Another user is logged onto an RF Check to see who is logged onto the
the message In Use unit using this equipment number. equipment incorrectly and have them
by [ ]. Enter another equipment number. correct their log ins.
If you cannot find an available
Using the Advantage Commander, run
equipment number, contact your
the Query LIST USER CURRENTLY
Supervisor.
LOGGED IN. Check under location_id
to see who is logged onto what
equipment.
The RF unit does Contact your Team Leader or Have user repeat the log in process. If it Have user repeat the log in process. If it
not display the Main Supervisor. still does not work, contact the System still does not work, contact the System
Menu after the user Administrator. Administrator.
logs on.
Receipts from
production
At the main menu Press F1 until you return to the
the user selects the Main Screen and select the correct
wrong option. option.
The RF unit is Enter the English equivalent. If you If this is a new pallet from production If this is a new pallet from production
prompting the user cannot read the English and it is a standard weight item, apply and it is a standard weight item, apply
to enter a Pallet ID, equivalent, contact your team another pallet label. another pallet label.
however the pallet leader or supervisor.
If this is a new pallet from production If this is a new pallet from production
tag is missing or
and it is a catch weight label, you could and it is a catch weight label, you could
torn.
reweigh the skid in shipping. You could reweigh the skid in shipping. You could
also send the pallet to production or also send the pallet to production or
cross out the pallet tag number and affix cross out the pallet tag number and affix
a new standard weight pallet label to a new standard weight pallet label to
the skid. the skid.
The user scans a This message means that this Make sure duplicate pallet tags have
Pallet ID and the RF pallet number has been scanned not been scanned. If they have, throw
unit displays the into the system. All pallet tags out and rescan. Run the Query HU IN
message Invalid MUST BE UNIQUE. Rescan the WHAT LOCATION to determine if this
Pallet ID. pallet. If you still received the pallet tag has been used.
above message, please see your
Scan the pallet tag if the Query did not
supervisor.
give you any prior history for the
particular pallet number.
If this does not work, apply a new pallet
tag to the product.
a) If this is a new pallet from production
and it is a standard weight item, apply
another pallet label.
b) If this is a new pallet from production
and it is a catch weight label, reweigh
and label the skid in shipping or send
back down to production (or) cross out
the pallet tag number only and affix a
pallet label to the skid from the standard
weight pallet labels.
The user enters a Usually means you did not scan Check above process again. You may
value and the RF what the system was asking for. need to put on another pallet tag for
unit displays the standard or have the skid weighed and
Rescan and make sure you are
message Bad labeled for a new pallet tag if a catch
using the Pallet Tag number.
Length. weight item. (OR) for Catch weight you
Try to enter the nine-digit pallet could cross out the pallet tag number
number using the English only and affix a pallet label to the skid
equivalent. from the standard weight pallet labels.
If after rescanning the pallet tag it Notify production of the problem with
still shows Bad Length check the the bar codes. Have them clean the
pallet label to see if anything is print heads and check the ribbon.
wrong in the label. If nothing
Contact the System Administrator if this
seems wrong, contact your Team
is still a problem.
Leader.
The RF unit prompts The bar code is incorrect or you If there is a problem with the bar code,
the UCC Bar Code are not scanning the correct bar enter all the information necessary to
and the RF unit code. have a correct bar code.
displays the
1. Scan another box on the skid. -OR-
message Faulty Bar
Code. 2. Enter all numerical information Run a new label from the shipping office
listed below the bar code. to affix to the skid. If the item is a catch
weight and you cannot get any of the
3. Look at the bar code to see if
boxes on that skid to scan, send the
you can find the problem. Contact
pallet back to ‘production’ to be
your Team Leader.
weighed and labeled or reweigh and
label the boxes in ‘shipping.’
-OR-
Cross out the pallet tag number and
affix a pallet label to the skid from the
standard weight pallet labels.
Notify production of the problem with
the labels and have then check the
ribbon and clean the print heads on the
label printers.
QC Hold and
Release
The user scans a This message means that there is Check to see if this pallet tag is showing
Pallet ID and the RF no pallet in the Warehouse with in Inventory. Use the Query HU IN
unit displays the that pallet number. Make sure you WHAT LOCATION. If it is you should be
message Pallet Not are scanning the correct bar code able to enter the pallet number. If it is
Found. and scan again. not, check the Query ALL ITEMS BY
LOCATION to see if this product shows
1. Enter the 9-digit pallet number
in this location. If system shows empty,
using the English Equivalent.
use the Physical process to put the
2. If this does not work, contact Inventory into the warehouse
your Supervisor. Write down the management system and then put on
pallet tag number and the Q. C. Hold. If the system says the
locations. product is there, but with a different
pallet tag number, key that number into
the RF gun and then use the Q.C. Hold
Process.
If this will not work, contact the System
Administrator.
The user scans This message means the wrong
Pallet ID tag and the information has been scanned.
RF unit displays the Scan the Pallet ID Tag again.
message Bad
1. Enter the nine-digit pallet
Length.
number.
2. If this does not work contact the
System Administrator.
The user scans a If contents of the skid is incorrect,
skid number. press F1 until you return to the
Adjustment Screens. Correct the
contents of the skid before placing
the skid on QC Hold.
The user enters a Make sure you are using a valid Run the Query Q.C. RELEASE to find
reason code and the reason code. See the bottom of out the pallet tag number. Enter this
RF unit displays the the scanner for a list of reason number.
message Reason codes. If you cannot read the
Not Found. pallet tag, contact your Supervisor.
The user enters a This pallet was never put on QC Run the Query PALLETS ON QC
Pallet ID. RF unit Hold, so you cannot release it. HOLD. If pallet is not listed it was never
displays the Check with your Supervisor to on QC HOLD therefore, you could not
message Pallet Not verify that the pallet is not on Q C release it. If pallet is listed, try the QC
Found. Hold. Release process again. If this still does
not work, contact the System
Administrator. If you cannot read the
pallet tag, run the Query to get the
pallet tag number. Use this number and
then scan it.
Move Process
The user scans a You did not scan what the system Using HighJump Advantage
Pallet ID and the RF was asking for. Scan and make Commander run the query HU IN
unit displays the sure you are using the Pallet Tag WHAT LOCATION. Enter the pallet
message Bad number. number and see if the system validates
Length. this number.
1. Enter the nine-digit pallet
number using the English
equivalent.
2. If this does not work, contact
your Supervisor. Write down the
pallet number and the location in
question and give to your
Supervisor.
The user scans a If you are using the keypad to 1. Make sure the user is scanning the
Location and the RF enter locations use a Capital correct bar code. This message usually
unit displays the Letter. For example, 2A101 not indicates that the wrong information has
message Bad 2a101. been scanned. Rescan the location bar
Length. code.
2. Enter location from the RF keypad
and press enter.
3. If this does not work, contact the
System Administrator.
User scans a 1. Make sure you are scanning a Check location to see if the system
location ID and the valid location and try to rescan. thinks there already is a product in that
RF unit displays the location. Using the Advantage
2. Try to enter the information from
message Invalid Commander run the Query WHATS IN
RF keypad and then press enter.
Location. A LOCATION (or) scan the Location
3. Check with the Supervisor in Status. Under the Administrative Menu
Charge. The system may think and select Scan the location and you
there is something already in this will receive information about the status
slot. Remember, only one 1 of that Location.
product code per location.
FI the message is not E=Empty the
system will not allow you to put product
in that location.
If the system does think there is product
there, but you can see that the product
does not exist, you should do a physical
on the location. This is done by a
Supervisor or Team Leader with
another gun. Then have the Warehouse
Staff Person complete the Move
Process.
Contact the system administrator if this
happens often. The system may not be
clearing out the location file.