| How AutoPalletP3 works with your WMS |
| |
| AutoPalletP3 is not a Warehouse Management System (WMS), but it is a pallet building algorithm component that is designed to work in conjunction with your existing WMS. This section explains options of how AutoPalletP3 can be used in your environment. |
| |
| Question |
Applies if your answer is YES |
| Are you using an off-the-shelf WMS? |
In adaptation mode, AutoPalletP3 operates under its dedicated Windows 2000 Server. It will have to operate in conjunction with your WMS which may run under another operating system. Please check out the section on Adaptation below. |
| Are you the manufacturer of a WMS? |
If your company is the manufacturer of a WMS, it is possible to integrate the APP3 Core module (platform independent C++ code) into your WMS product. Please check out the section on Integration below. |
| Are you using a custom built WMS? |
If you use your own WMS (custom built), both options may be feasible. Adaptation is more than likely the cheaper and more practical solution, but Integration may have benefits which make the extra effort worthwhile. |
| |
| What are the pro's and con's of Adaptation vs Integration? |
| |
|
The main advantage of the adaptation option is that it is relatively quick to implement. One downside is that whenever you upgrade your existing WMS Software, a strong possibility exists that changes need to be made to your AutoPalletP3 software. Another disadvantage is that the AutoPalletP3 user interface (UI) is significantly different from your WMS UI.
The main advantage of the integration option is that APP3 Core is a seemingly integral part of your WMS. However, the integration of APP3 Core into your WMS is likely going to take considerably longer (increased costs) than adapting AutoPalletP3 to your WMS. Another disadvantage is that APP3 more than likely needs to be tailored for your WMS and upgrading to a new version of APP3 Core may not be trivial.
|
| |
| Data model required by AutoPalletP3 or APP3 Core |
| |
| Please check out the data model required by the AutoPalletP3 algorithm at the end of this page. |
| |
| Any further questions? |
| |
| We hope this page answers most of your questions. However, if you need further technical information, please contact us or send us an e-mail. |
| |
| Adapting AutoPalletP3 to your existing WMS |
| |
| To make AutoPalletP3 suitable to work in conjunction with as many off-the-shelf WMS as possible, we have designed AutoPalletP3 to operate on its own server. In addition, AutoPalletP3 provides a thin client user interface. All that is required of AutoPalletP3 clients is a modern web browser (e.g. Internet Explorer or Netscape Navigator). |
| |
| Runtime Environment |
| |
 |
| |
| The diagram above reflects how AutoPalletP3 works with your existing WMS, how it communicates with your WMS Database Management System (DBMS) and how APP3 Client Workstations communicate with the AutoPalletP3 Server. |
| |
| Database Access: |
| |
| The path to access data from the SQL Server (A) and from the WMS DBMS (B) are explained in more detail below. Path B is always expected to be available and in use while Path A may or may not be needed. However, if Path A is also in use, APP3 Core will use Path B for read only access. If Path A is not used, APP3 Core will need to be able to read/write via Path B. |
| |
|
 The APP3 Core module communicates with the SQL Server 2000 database through ADO (OLE-DB/ODBC). The SQL Server 2000 database will only be used if it is not feasible to implement the data AutoPalletP3 requires under the WMS DBMS itself. APP3 Core maintains a logical link to the WMS DBMS through Path B.
 APP3 Core must be able to access data from your WMS DBMS. This can occur via an ODBC connection or C-ESQL (embedded SQL). The access is read only if Path A is also in use or read/write if AutoPalletP3 specific data is added to the WMS DBMS.
|
| |
|
Note: AutoPalletP3's web interface can only be used to modify data that is AutoPalletP3 specific. AutoPalletP3 does not modify any data native to the WMS.
|
| |
| Adaptation Issues |
| |
| Issue |
Explained |
AutoPalletP3 Adaptation |
| HW and OS Platform |
In adaptation mode, AutoPalletP3 operates under Windows 2000 Server. It will have to operate in conjunction with your WMS which may run under another operating system. |
We have been careful when building AutoPalletP3 to ensure that very few requirements must be met by an existing WMS in order to use AutoPalletP3. These requirements are:
WMS Server: AutoPalletP3 must be able to read data from the WMS database. AutoPalletP3 has built in components to communicate with your database directly through embedded SQL (C-ESQL) or ODBC. Other options may be possible but require extra effort during the installation. In all cases, the network must be configured such the AutoPalletP3 Server can communicate with the WMS Server.
Client Workstations: All that is required on client workstations is a WEB Browser (thin client). The client workstations must be able to establish a TCP/IP connection with the AutoPalletP3 Server. All communication occurs via HTTP which requires that port 80 be open on the AutoPalletP3 Server.
|
| Complementing data in the WMS database |
AutoPalletP3 requires data that may not be available from your WMS. For example, AutoPalletP3 requires the dimensions of each product. |
When we adapt AutoPalletP3 to your WMS, we will create a database that contains data required by AutoPalletP3 but missing in your WMS. This can either be achieved by implementing a database on the AutoPalletP3 Server (SQL Server 2000) or by adding extra tables to your WMS database (see also Security below). AutoPalletP3 takes care of linking the data logically.
When AutoPalletP3 is invoked to produce a pick list for an order, it will load all the data relevant for the order into its own database and maintain a one-to-one relationship to the data in your own database. The AutoPalletP3 Database contains only data that is not contained in your WMS. These additional details are entered into the AutoPalletP3 database through the AutoPalletP3 web interface. AutoPalletP3 will issue warnings if relevant data has not been added to the AutoPalletP3 database.
|
|
Language and Units of Measure
|
AutoPalletP3 can be used in different countries. |
The language and units of measure can be tuned by setting system parameters accordingly. |
| Security |
Enhancing your WMS database with the details AutoPalletP3 requires may cause problems with your existing WMS software or pose a security risk. |
Because you do not have control over the WMS software, enhancing your WMS database may cause problems. Even if it does not cause technical problems, you may be reluctant to give us permission to add AutoPalletP3 tables to your database. If no such concerns exist, adding extra tables to your WMS database will reduce maintenance costs and licensing fees.
In these cases, AutoPalletP3 tables can be implemented under SQL Server 2000 database on the AutoPalletP3 Server or a separate Windows 2000 Server. However, read access permissions to the WMS database are still required.
|
| |
| Installation Tasks |
|
|
| Task |
Description |
| AutoPalletP3 Server |
AutoPalletP3 requires a dedicated Microsoft Windows 2000 Server. If your implementation requires SQL Server 2000, performance can be increased by deploying another Microsoft Windows 2000 Server running SQL Server 2000. The minimum system requirements are:
Pentium III 500MHz +
256MB RAM
10GB SCSI HDD
Fast Network card |
| Analyzing your WMS database |
We will analyze your WMS DBMS in order to determine the data required by AutoPalletP3 but missing from your WMS DBMS. The data that is missing needs to be implemented in AutoPalletP3's database. |
| WMS DBMS Access |
Your network must be configured such that the AutoPalletP3 server can access data from your WMS DBMS. AutoPalletP3 must be granted read access (if AutoPalletP3 uses its own SQL Server 2000 database) or read/write access (if the WMS DBMS is used to implement additional tables required by AutoPalletP3). |
| Warehouse Map |
AutoPalletP3 contains a data model to map your warehouse layout and the pick locations in a way that allows the algorithm to efficiently determine the distance between any two locations in the warehouse and thus minimize the total travel distance when turning orders into pick lists. We will enter these details as part of the installation process. All we require is a warehouse layout (to scale) reflecting pick location identifiers. |
| Data Entry |
Two options are available to enter data that is required by AutoPalletP3 but not already available from your WMS DBMS. If you do not enter this data and run AutoPalletP3, warning messages will be generated telling you what data is missing. You can then go back and supply the missing data and run AutoPalletP3 again. Over time, the warning messages will disappear.
Alternatively, we could populate the AutoPalletP3 database with bare bone data and a data entry operator could enter the missing details using AutoPalletP3's web browser interface.
|
| Backup Procedures |
We will ensure that AutoPalletP3 specific data is backed up regularly. |
| Warehouse Parameters |
As part of the installation, the warehouse parameters must be fine tuned to best match your particular warehouse. |
|
| |
| Maintenance Tasks |
| |
| All the administration tasks listed below can be taken care of by us through the use of remote access software (PC Anywhere, Control IT, etc) and the Internet, cutting administration costs to a minimum and increasing response times significantly. For this reason, we strongly recommend this kind of configuration. |
| |
| Task |
Description |
| Warehouse Map |
Whenever changes to your actual warehouse take place, the warehouse map needs to be adjusted accordingly. For example, you may add a new aisle, additional racks etc. All these changes must be reflected in the Warehouse Map. |
| WMS System Upgrades |
From time to time, you may receive updated WMS Software. This may affect AutoPalletP3 as the product has no control over the internals of your WMS DBMS. The effort required to get AutoPalletP3 fine tuned to operate with this new version depends on the changes to the data in the WMS DBMS. |
| AutoPalletP3 Upgrades |
Each upgrade to AutoPalletP3 is likely to require some minor system changes. We will take care of this for you. |
| Trouble Shooting |
We will be available to determine and correct any AutoPalletP3 related problems you may encounter. |
|
| |
| Integrating AutoPalletP3 with your WMS |
| |
| The AutoPalletP3 core software (written in ANSI C++) is compiler and platform independent. This offers the opportunity to integrate the software with existing off-the-shelf warehouse management systems. The only provisions are, an ANSI C++ compatible compiler must be available and the existing warehouse management software must have some mechanisms available to make calls to the C++ library. |
| |
| Runtime Environment |
| |
 |
| |
|
The APP3 Core module is written in platform independent C++ code. The APP3 C-ESQL layer is used to access (read/write) your WMS Database Management System (DBMS). In very basic terms, the Integration with an existing WMS requires:
- Enhancement of the WMS DBMS with data required by AutoPalletP3
- Enhancement of the WMS software with a user interface to maintain the data required by AutoPalletP3
- Implementation of an interface between existing WMS code and AutoPalletP3 if C++ can not be used directly
|
| |
| Integration Issues |
| |
| Issue |
Explained |
AutoPalletP3 Integration |
| HW and OS Platform |
Your WMS software needs to be able to communicate with the APP3 Core. |
APP3 Core is a C++ class library written in platform independent C++ code. If your WMS has been written in a language that does not provide an interface for C++ class libraries, an intermediate layer may have to be developed to overcome this restriction. |
| Complementing data in the WMS database |
AutoPalletP3 requires data that may not be available from your WMS DBMS. For example, AutoPalletP3 requires the dimensions of each product. |
Existing tables in your WMS DBMS should be enhanced and new ones added to include tables and attributes missing but required by APP3 Core. |
| Language and Units of Measure |
AutoPalletP3 can be used in different countries. |
Your WMS may already use system parameters and mechanisms to ensure language independence. APP3 core will have to be modified to use your system settings rather than its own. |
| User Interface |
APP3 Core has no user interface components. |
The user interface of the existing WMS will have to be enhanced to enable users to also maintain data used exclusively by APP3 Core. |
| APP3 C-ESQL |
Writing embedded SQL for the C language may not be an option with your WMS DBMS. |
Some DBMS may not provide an embedded SQL for C precompiler (please check with your DBMS vendor). If this is the case, the APP3 C-ESQL module will have to be replaced with a module that uses a DBMS specific API. |
| |
| Installation Tasks |
| |
| Task |
Description |
| Warehouse Map |
APP3 Core contains a data model to map your warehouse layout and the pick locations in a way that allows the algorithm to efficiently determine the distance between any two locations in the warehouse and thus minimize the total travel distance when turning orders into pick lists. We will enter these details as part of the installation process. All we require is a warehouse layout (to scale) reflecting pick location identifiers. |
| Data Entry |
Two options are available to enter data that is required by APP3 Core but not already available from your WMS DBMS. If you do not enter this data and run AutoPalletP3, warning messages will be generated telling you what data is missing. You can then go back and supply the missing data and run AutoPalletP3 again. Over time, the warning messages will disappear.
Alternatively, we could populate the AutoPalletP3 database with bare bone data and a data entry operator could enter the missing details using AutoPalletP3's web browser interface.
|
| Warehouse Parameters |
As part of the installation, the warehouse parameters must be fine tuned to best match your particular warehouse. |
|
| |
| Maintenance Tasks |
| |
| All the administration tasks listed below can be taken care of by us through the use of remote access software (PC Anywhere, Control IT, etc) and the Internet, cutting administration costs to a minimum and increasing response times significantly. For this reason, we strongly recommend this kind of configuration. |
| |
| Task |
Description |
| Warehouse Map |
Whenever changes to your actual warehouse take place, the warehouse map needs to be adjusted accordingly. For example, you may add a new aisle, additional racks etc. All these changes must be reflected in the Warehouse Map. |
|
| |
| Logical Data model |
| |
 |
| |
| The logical data model above reflects (with the exception of the Warehouse Map) entities and relationships required by AutoPalletP3. A subset of this data will be contained within your WMS DBMS and the rest in the AutoPalletP3 specific database. While AutoPalletP3's web-based front end allows users to view all data from the above model, only the data stored in AutoPalletP3's database can be modified. |
| |
| Any further questions? |
| |
| We hope most of your questions have been answered here. However, if you need further technical information, please contact us or send us an e-mail. |
