Volume of Objects

For optimal sizing, in addition to the actual objects in the system, consider, among other things, nested register structures in folder objects that must also be managed (document, metadata, index/control data).

Calculate the following values in the units shown in brackets.

These values provide a rough estimate of the amount of data. You can make a rough estimate or use a higher amount, for example, "20 GB of documents per year plus 100 GB of legacy data from the outset. Roughly 20 percent of the data is image objects". Please note, however, that the more precisely you define the amount of data, the more accurately you will be able to estimate the number of objects. This could look something like this: "40 of the 120 GB/year are e-mails sent via enaio® exchange, 40 GB are from SAP, 20 GB are from daily/incoming e-mails, and the remaining 20 GB are received via other interfaces (enaio® appconnector); incoming e-mails are image files only (tiff/jpg)".

• Existing data volume: Number of objects/metadata/index data/control data/documents (size and quantity in GB/TB)

• Legacy data to be imported: Is there a legacy archive that needs to be imported in full or a filesystem share that has to be transferred? (GB/TB)

• Periodically added data: Hourly jobs, daily imports, monthly statements, input from interfaces, etc. Is enaio® repository-manager or enaio® exchange in use? (GB/TB per unit of time)

• Allocation of documents to categories: Categorization as image material (scanned, without a defined text) or searchable materials. You can do this by taking random samples or making a conservative estimate. (in % of volume of data)