The workloads and the required functionality on a ASYCUDA system can vary significantly between installation sites and user countries.
The configurations listed hereafter should only be regarded as samples. We advise you to contact the Geneva development center before you make final decisions about your hardware.

ASYCUDA++ Clients

The ASYCUDA clients form the front end to the user. All clients should be equipped with a mouse and a floppy disk drive.
Since the clients are not dedicated to ASYCUDA but should generally support office automatization, they should be compatible with Windows 3.x, Windows95, or Windows98.
The ASYCUDA software is  distributed on CD-ROM. Sites that are in charge for the dissemination of software in their country should have at least one high end PC with a CD-ROM drive.

ASYCUDA++ Server 

The main task of an ASYCUDA server is to serve client requests in accessing the relational database. As typical OnLine Transaction Processing Servers (OLTP) they are likely to improve performance from fast and fault tolerant hard disks and from additional RAM. Each server should be equipped with a Backup device (Streamer, DAT) and if necessary be protected by a UPS.

The typical data transfer between a client and the server is moderate. Fiber optic lines are therefore unlikely to improve performance. Sites that are in charge for control table maintenance will have a slightly higher network access.
ASYCUDA server applications do not require graphic terminals.

The required disk space for the ASYCUDA database can roughly be estimated with: 50 MB (Control Tables) + 20 MB (Informix/Oracle System Tables) + 5 kB * Number of Declarations (Declaration with two items) + 2 MB * number of ASYCUDA users (printouts; file transfer)

The ASYCUDA executables and DLL's will require about 15 MB, the A++ platform an additional 20 MB disk space.
 

ASYCUDA has been ported to many platforms other than Intel. For a comparable system configuration on these platforms please contact your hardware supplier.