InfoShip® Central Server Overview

For companies that have more than one distribution center, CLS offers InfoShip in a centralized server configuration. Workstations located at each distribution center communicate over a WAN to the central InfoShip DMS server and its SQL Server database. The SQL Server database typically runs on a separate server to provide optimum performance. Of course, separate InfoShip systems can be installed at each distribution center if a company prefers to have local systems.

InfoShip is configured for each distribution center to ship via BAX Global®, DHL®, FedEx®, UPS®, UPS Supply Chain Solutions®, USPS®, and LTL carriers using that center’s specific carrier account numbers. Collect and Third Party Billing shipments can also be processed. Closing out carriers can be performed at any distribution center while the other centers are still shipping.

InfoShip can be configured to communicate to the company’s host system(s) either from the central server or from each workstation. CLS integrators consult with you regarding which method is optimal for your particular installation.

Integration to an ERP, WMS, or other host systems can be accomplished through real-time communications or in batch mode. InfoShip systems are typically integrated using XML or simple text message structures communicated via sockets real-time directly to ERP, WMS, or homegrown host systems, and to middleware products from companies such as DataDirect® (formerly NEON Systems). Many InfoShip systems connect directly to host databases, such as Oracle®, DB2® or Sybase®. If data resides on multiple host systems, InfoShip has the ability to communicate with many systems simultaneously to retrieve and/or post data as needed.

Typically, InfoShip passes key lookup data to the host for the shipment being processed. The host returns the order header and line item information. When the order detail information includes unique package IDs to indicate which package contains which line items, and no manual adjustments to any order information is required, then the shipment can be processed by simply scanning the bar coded unique package IDs and capturing the package weights.

InfoShip can be configured so all distribution centers follow identical business rules. Or, if some of the distribution centers have special requirements, InfoShip can be configured to operate differently only at those DC’s to meet those unique requirements. InfoShip utilizes Profiles to implement and control specific operational functionality, which ensures specific workstations at a given distribution center operate identically. Profiles are also used to configure workstations differently at the same distribution center; for example, some workstations might be configured with a profile for shipping small package shipments, while other workstations use different profiles to configure them to process LTL or international shipments.

All system configuration information is stored in SQL Server so managing and supporting the system is simplified. Changes made to a profile in SQL Server are automatically pushed to the workstations using that profile.

Here are a few examples of business rules that might be implemented:

1) Host system Incoterms, country codes, and carrier service codes are converted to InfoShip codes for Freight Terms, Country IDs, and Services.

2) To prevent expensive merchandise shipments from being redirected to another destination, InfoShip can be configured to disallow editing the consignee name and address retrieved from the host system, preventing the operator from overriding it.
3) Routing guides of major retailers that clients ship to can be implemented in InfoShip.

4) If clients’ customers call and place orders on hold or cancel them after pick tickets have been generated and the order is picked, InfoShip can check a flag either retrieved from the host system or from a local InfoShip table to see if the order is on hold or canceled; if so, InfoShip can display a dialog notifying the operator of the order’s status and disallows shipment.

5) If clients self insure shipments valued at less than a specific dollar amount, say $1,500 for example, but use the carrier’s insurance for higher valued shipments charging the customer the insurance fees, InfoShip can compute the merchandise value in each box and set the carrier’s Declared Value/Insurance amount to the merchandise amount if it is higher than $1,500.

6) If FedEx picks up shipments later than UPS, InfoShip can automatically set the carrier service to a FedEx equivalent service for any UPS air shipment that is shipped after the UPS pick up time so the packages are delivered overnight or in two days as intended.

The above description of a central server based InfoShip system is a brief example of how InfoShip can be configured. Contact CLS at 800-407-0280 to discuss your company’s specific requirements and find out how InfoShip can benefit your operations.