Acme is not only "real time" it’s "better time"

 

Unlike many systems, Acme has no problem running when your accounting system is down or in single user mode due to month end processing, re-indexing or network failure.

In any system there is lag time between when inventory is physically received and the purchase order is processed in the system. This creates one gap in any real time system.

 

With Acme, if you run the bridge after PO receipts you have real time data and better time fault tolerance which results in more up time.

In Acme all registers usually use one Acme database container the same way a networked accounting system reads data from its own database. In Acme when you start with 10 widgets and sell 4 from register a lookup on any other register in the store shows you are down to 6 widgets. The same logic applies to customer account balances if you do "in house" charges.

 

Acme is "better-time" becasue of how it performs when the network or accounting system goes down for routine or unplanned maintenance. In other systems this is often a business disaster. In Acme we just keep the check out lanes moving.

During network downtime you can keep your check out lanes by switching Acme to processing off of a local copy of the Acme data during the event.

 

Acme keeps running while you close the month, clear the flags, re-index the accounting system data or do other "exclusive use" tasks in your host system.

 

The Data Pump can be run manually or automatically via Scheduling the Data Pump