GT:Up and Running with Whistle - Revision history

64.122.111.148: /* Setup Scenarios */

2006-09-13T20:07:46Z

‎Setup Scenarios

64.122.111.148: /* Setup Scenarios */

2006-09-13T19:25:49Z

‎Setup Scenarios

64.122.111.148: /* Setup Scenarios */

2006-09-13T19:23:11Z

‎Setup Scenarios

64.122.111.148: /* Setup Scenarios */

2006-09-13T19:20:39Z

‎Setup Scenarios

Anita: /* Setup Scenarios */

2006-09-13T19:17:35Z

‎Setup Scenarios

64.122.111.148: /* Setup Scenarios */

2006-09-13T19:14:05Z

‎Setup Scenarios

64.122.111.148: /* Setup Scenarios */

2006-09-13T19:11:01Z

‎Setup Scenarios

64.122.111.148: /* Setup Scenarios */

2006-09-13T19:10:10Z

‎Setup Scenarios

Mjc at 22:23, 16 November 2005

2005-11-16T22:23:47Z

64.122.111.148: /* Up and Running with Whistle */

2005-11-14T17:00:04Z

‎Up and Running with Whistle

@@ Line 70: / Line 70: @@
 [[Image:Chapter3_PIC3.GIF|700px|Image:Chapter3_PIC3.GIF|700px]]
 This fourth diagram depicts a fairly complex system, similar to the second system except that there are two Whistle databases.  The first is the local one that the system uses to perform all Whistle transactions.  The second is the main whistle database that is updated separately as time and transmission speed allow.  This setup overcomes the problem of having the functioning Whistle database located off site (and thus long transmission times).  Also, if the connection between the Main Whistle database and the application server is lost, Whistle will still function using the local database.
-[[Image:Chapter3_PIC4.GIF|100px|Image:Chapter3_PIC4.GIF|100px]]
+[[Image:Chapter3_PIC4.GIF|700px|Image:Chapter3_PIC4.GIF|700px]]

@@ Line 69: / Line 69: @@
 This diagram depicts a setup in which both the Whistle system and ERP system databases are located off premises.  The Whistle application server communicates with the Whistle database and the ERP database over a network such as a WAN.  The setup has the same disadvantage as setup #2, mainly that data transmission times can be long.  This system also relies on a functioning external network, one that may be possibly fail and halt all Whistle system operations.
-[[Image:Chapter3_PIC3.GIF|300px|Image:Chapter3_PIC3.GIF|300px]]
+[[Image:Chapter3_PIC3.GIF|700px|Image:Chapter3_PIC3.GIF|700px]]
 This fourth diagram depicts a fairly complex system, similar to the second system except that there are two Whistle databases.  The first is the local one that the system uses to perform all Whistle transactions.  The second is the main whistle database that is updated separately as time and transmission speed allow.  This setup overcomes the problem of having the functioning Whistle database located off site (and thus long transmission times).  Also, if the connection between the Main Whistle database and the application server is lost, Whistle will still function using the local database.
-[[Image:Chapter3_PIC4.GIF|700px|Image:Chapter3_PIC4.GIF|700px]]
+[[Image:Chapter3_PIC4.GIF|100px|Image:Chapter3_PIC4.GIF|100px]]

@@ Line 69: / Line 69: @@
 This diagram depicts a setup in which both the Whistle system and ERP system databases are located off premises.  The Whistle application server communicates with the Whistle database and the ERP database over a network such as a WAN.  The setup has the same disadvantage as setup #2, mainly that data transmission times can be long.  This system also relies on a functioning external network, one that may be possibly fail and halt all Whistle system operations.
-[[Image:Chapter3_PIC3.GIF|700px|Image:Chapter3_PIC3.GIF|700px]]
+[[Image:Chapter3_PIC3.GIF|300px|Image:Chapter3_PIC3.GIF|300px]]
 This fourth diagram depicts a fairly complex system, similar to the second system except that there are two Whistle databases.  The first is the local one that the system uses to perform all Whistle transactions.  The second is the main whistle database that is updated separately as time and transmission speed allow.  This setup overcomes the problem of having the functioning Whistle database located off site (and thus long transmission times).  Also, if the connection between the Main Whistle database and the application server is lost, Whistle will still function using the local database.
 [[Image:Chapter3_PIC4.GIF|700px|Image:Chapter3_PIC4.GIF|700px]]

@@ Line 60: / Line 60: @@
 [[Image:Chapter3_PIC1.GIF|700px|Image:Chapter3_PIC1.GIF|700px]]
 This second diagram is similar to the first, except that the ERP system database is remotely located.  This situation is common amongst larger companies that have many physical warehouses and plants, but only one centrally located ERP system.  In this case the ERP system and Whistle system communicate with each other to synchronize their common pool of data.  The main disadvantages of this system are that (1) Whistle - ERP communications can be slow and (2) The ERP system relies on an open functioning network connection to synchronize it's data with Whistle data.  The main advantage of this system is the fact that many satellite locations can connect to one central ERP system that manages and synchronizes all enterprise-wide transactions.
 This diagram depicts a setup in which both the Whistle system and ERP system databases are located off premises.  The Whistle application server communicates with the Whistle database and the ERP database over a network such as a WAN.  The setup has the same disadvantage as setup #2, mainly that data transmission times can be long.  This system also relies on a functioning external network, one that may be possibly fail and halt all Whistle system operations.
 This fourth diagram depicts a fairly complex system, similar to the second system except that there are two Whistle databases.  The first is the local one that the system uses to perform all Whistle transactions.  The second is the main whistle database that is updated separately as time and transmission speed allow.  This setup overcomes the problem of having the functioning Whistle database located off site (and thus long transmission times).  Also, if the connection between the Main Whistle database and the application server is lost, Whistle will still function using the local database.

@@ Line 59: / Line 59: @@
 This first system diagram depicts a completely self-contained Whistle system.  All of the system components are located in one location, be it a warehouse, plant, store, office, or other.  This setup is most suitable to small companies that may only have one location from which their operations are based.  The advantages of this system setup are speed and easy system management.  Data is transmitted between components at a faster rate due to the lack of long transmission distances (Wide Area Networks - WANs).  The entire Whistle system is easier to administer simply because everything is one place.
-[[Image:Chapter3PIC1.GIF|Image:Chapter3PIC1.GIF]]
+[[Image:Chapter3_PIC1.GIF|700px|Image:Chapter3_PIC1.GIF|700px]]
 This second diagram is similar to the first, except that the ERP system database is remotely located.  This situation is common amongst larger companies that have many physical warehouses and plants, but only one centrally located ERP system.  In this case the ERP system and Whistle system communicate with each other to synchronize their common pool of data.  The main disadvantages of this system are that (1) Whistle - ERP communications can be slow and (2) The ERP system relies on an open functioning network connection to synchronize it's data with Whistle data.  The main advantage of this system is the fact that many satellite locations can connect to one central ERP system that manages and synchronizes all enterprise-wide transactions.

← Older revision		Revision as of 19:10, 13 September 2006
Line 58:		Line 58:

	This first system diagram depicts a completely self-contained Whistle system. All of the system components are located in one location, be it a warehouse, plant, store, office, or other. This setup is most suitable to small companies that may only have one location from which their operations are based. The advantages of this system setup are speed and easy system management. Data is transmitted between components at a faster rate due to the lack of long transmission distances (Wide Area Networks - WANs). The entire Whistle system is easier to administer simply because everything is one place.		This first system diagram depicts a completely self-contained Whistle system. All of the system components are located in one location, be it a warehouse, plant, store, office, or other. This setup is most suitable to small companies that may only have one location from which their operations are based. The advantages of this system setup are speed and easy system management. Data is transmitted between components at a faster rate due to the lack of long transmission distances (Wide Area Networks - WANs). The entire Whistle system is easier to administer simply because everything is one place.
		+
		+	[[Image:Chapter3PIC1.gif\|500px\|Image:Chapter3PIC1.gif\|500px]]

	This second diagram is similar to the first, except that the ERP system database is remotely located. This situation is common amongst larger companies that have many physical warehouses and plants, but only one centrally located ERP system. In this case the ERP system and Whistle system communicate with each other to synchronize their common pool of data. The main disadvantages of this system are that (1) Whistle - ERP communications can be slow and (2) The ERP system relies on an open functioning network connection to synchronize it's data with Whistle data. The main advantage of this system is the fact that many satellite locations can connect to one central ERP system that manages and synchronizes all enterprise-wide transactions.		This second diagram is similar to the first, except that the ERP system database is remotely located. This situation is common amongst larger companies that have many physical warehouses and plants, but only one centrally located ERP system. In this case the ERP system and Whistle system communicate with each other to synchronize their common pool of data. The main disadvantages of this system are that (1) Whistle - ERP communications can be slow and (2) The ERP system relies on an open functioning network connection to synchronize it's data with Whistle data. The main advantage of this system is the fact that many satellite locations can connect to one central ERP system that manages and synchronizes all enterprise-wide transactions.

@@ Line 1: / Line 1: @@
-==Up and Running with Whistle==
+=Up and Running with Whistle=
 To say that Whistle system setup is a diverse and involved topic is an understatement.  There are many facets to a Whistle System Setup.
@@ Line 14: / Line 14: @@
 There are simply not enough room in this user’s manual to expound on each of these topics at length.  What we provide in this manual is a brief overview of these topics.  Use this manual to gain a general understanding of the way an entire Whistle System operates.  Advanced User’s and System Administrators will need to refer to our System Installation Library (WSL INS2004 series) for detailed system installation information.
-===Whistle System Key Concepts===
+==Whistle System Key Concepts==
-====Enterprise Resource Planning (ERP) system====
+===Enterprise Resource Planning (ERP) system===
 Whistle is designed to expand the benefits of your ERP system.  Your ERP system handles many different inventory functions, including handling…
@@ Line 30: / Line 30: @@
 Whistle is designed to interact with your ERP system to optimize the handling of these functions.  Your ERP system may be located in a central network location or, in the case of smaller businesses, on site with the rest of the system.
-====The Whistle Application====
+===The Whistle Application===
 The Whistle Application is responsible for handling all Whistle transactions, including :
@@ Line 38: / Line 38: @@
 The Whistle application is usually run on a central warehouse computer.  This application is responsible for coordinating all Whistle transactions throughout the warehouse.  Whistle must interact with many remote systems to accomplish its tasks.  It must communicate with the users of Whistle through the use of their handheld or forklift mounted keyboards and computer screens.  It must be able to integrate seamlessly with your ERP.  It must have access to the Warehouse database.
-====Databases – Whistle (Warehouse) and ERP====
+===Databases – Whistle (Warehouse) and ERP===
 Both Whistle and your ERP system have large database components with which they interact.  These databases store all of your warehouse inventory data, production order, sales order, and pack order information, and much more.  These database components must be seamlessly integrated with your ERP application and the Whistle application.
-====Remote Inventory Devices====
+===Remote Inventory Devices===
 Almost all Whistle transactions are performed using remote input/output devices.  These include handheld barcode scanners and portable computer terminals.  These battery-operated devices are used throughout a warehouse to perform all key Whistle transactions.
-====Radio Frequency Transmitters====
+===Radio Frequency Transmitters===
 Remote inventory devices connect to the main Whistle Application Server through a wireless radio frequency network.  All networks are customized to suit the needs of the warehouse and/or plant.  The size of the radio network depends on both plant size and layout.  Antennas are strategically placed throughout a warehouse to provide full wireless connectivity throughout the entire building.  This wireless grid satisfies the critical need for warehouse employees to be able to access Whistle from any point within the warehouse.
-====Telnet Application====
+===Telnet Application===
 Remote inventory devices require both (1) a connection to the Whistle application server (radio frequency transmitters) and (2) a device that can transmit the data over the open connection.  The Whistle system employs a ‘Telnet’ application to handle this function.  A telnet application must be installed on both the application server and all remote inventory devices.
-====Operating Systems====
+===Operating Systems===
 As mentioned earlier, the main Whistle application is usually located on a central server within the warehouse.  Whistle is designed to be able to run on just about any operating system.  Our goals are to have Whistle be able to operate on the following operating systems:
@@ Line 54: / Line 54: @@
 *Unix (AIX, HP-UX, Solaris, Linux)
-====Setup Scenarios====
+===Setup Scenarios===
 What follows are several different diagrams depicting possible Whistle system setups.    Please refer to the previous section, ‘Key Concepts’, for information regarding the particular system components.