Overview

There are two reasons why you may wish to use the distributed version of Acumen:

• Multiple branch sites

• Independence of Point Of Sale functions (Robustness)

If you have a need to operate Acumen at a location where it is not possible or feasible to access the Main Acumen files via network connection then you require the distributed version. Likewise if you require the ability to continue using Acumen at the Point Of Sale regardless of the availability of Acumen's main files (ie. when the Server, Network (LAN) or Acumen's main files are unavailable) then you also require the distributed version.

{bmc help0020.wmf}

The operation and abilities of a station in a distributed system is different for those stations that have the ability to access the main files via a network (LAN) and those that don't. We refer to stations that have network access as Network stations and those that don't as Remote stations.

Distribution of Acumen is achieved by creating a duplicate of the master files (ie. those files necessary to execute standard Point Of Sale operations) and distributing this to all stations. Those stations that have network (LAN) access to Acumen's main files can update their copy of this Master information whenever the network is operation (typically once a day). Those stations that do not have network access to the main files can receive updates of the Master information via file transfer by diskette, modem etc..

Documents created at a distributed station are recorded and transmitted back to the main files via Network, Modem or diskette. The following diagram shows the flow of information at the main site of a Distributed Acumen installation:

{bmc help0021.wmf}

Installation at remote sites can be as simple as a single remote machine, to a networked branch. Note that there can be only one Branch Purchase, Order and Stock file. This means that where there is more than one branch machine and any of these files are in use there must be a LAN to connect them.

{bmc help0022.wmf}