Advantages

1. Bandwidth requirement (between headquarter and remote site) is low
2. Off-line capability
3. Support multiple remote sites

Disadvantages

1. Unaware to problems in remote sites

Erratic input from remote sites may not be noticed until batch execution in headquarter was performed. Even when an error occurs, the remote sites still unaware of the problem and may keep making the same error until headquarter notifies them.

2. Increase workload to system administrator

The system administrator have to check for error log after each batch operation, and take appropriate actions to rectify the problems.

3. The rectification work need co-operations between headquarter and remote site

As errors are usually caused by erratic input from remote sites, the headquarter cannot correct the data by itself. Headquarter must obtain from the remote sites for a new set of correct data to rectify the problem. However, time lag in the re-submit of data from remote site may seriously affect the integrity of data (in headquarter) which results in incomplete reports to managers and inappropriate decisions to the company.

4. Requires users to log-off during batch execution

During the period when batch execution takes place in headquarter, no user can gain access to the system, either changing or simply lookup data. Depends on the size of data and the performance of the system, this period may lasts for several hours which is unacceptable to mission critical operations requiring a 24x7 environment.

Batch Operations is good for:

1. Simple operations

Simple operations with straight-forward data input are less likely to generate errors. Retail stores sending only their sales transactions to headquarter in Batch Operations mode is good.

However, in real-life situations, most jobs involve complicated tasks rather than simple operations.

2. Moderate pace of work-flow

Data input from remote sites are collected together as a batch and wait to submit to the headquarter for batch execution after a pre-defined period. In addition, there is a 'no access' period during batch execution is performed in headquarter. Thus, Batch Operations is suitable for a moderate pace of work-flow.

However, in real-life situations, especially in Asian manufacturing industries, quick pace and interactive operations are required.

3. Users are highly self-disciplined

As the remote sites are not aware immediately of errors they have made, all users must follow strictly to the operation procedures and guidelines, or else they may bring problem during batch operation.

In case of error really happens, all users must keep following the pre-stated workflow strictly, but not to correct the problem in their own way. Any action attempting to correct the problem without following the stated procedures may leads to errors during batch operation.

However, in real-life situations, highly self-disciplined staff are always in high demand.

Batch Operations is not good for:

1. Complex operations

Batch Operations is not suitable for jobs involving different complicated tasks. Typically speaking, ERP systems taking care of purchasing, sales, manufacturing, accounting, inventory control and other activities in the entire company should not be performed in Batch Operations mode.

2. Bi-directional data exchange

Batch Operations conducts in one-way communication (data collects in batch from remote-site, submits to headquarter for operations) manner. When a bi-directional data exchange (two-way communication, data transfers back and forth between remote site and headquarter) is required, Batch Operations fails to handle efficiently.

3. Frequent modifications to data

Batch Operations incurs a period which data in the remote sites are modified but not yet submitted to the headquarter. The headquarter must wait for the data submission from the remote sites and reflects any data change in the batch execution result. However, the remote sites may have further modified the data after data submission, even before batch execution in headquarter completed. As a result, when there is frequent modifications to data, Batch Operations cannot provides the headquarter an up-to-date data set and cannot keep up with a fast pace working environment.