System 4 – Notes, Thoughts, and Calculation

• Capture volume is missing: assumed volume: B/W scan with 1,000 pages/day

• Calculated size: (1,000 [captures] + 1,000 [imports] + 400)/8 = 300 MB + 2.5 GB of e-mails per day → 2.8 GB of data per day

• DV load calculation: (2,400 [imports] + 10,000 [e-mails])/day (8 h) → 26 pages per minute

  Plus OCR: 400/day plus 10% of e-mails (=1,000) 1,400 OCR pages per day → three pages per minute → one OCR core

• A second OCR core (license) for enaio® capture is required. OCR on the client workstation.

• An MSSQL server is already available in the infrastructure. enaio® receives its own database, schema, and login for this. The specified resources are still available on the instances.
  No information on legacy data, complexity of rights system, or scripts; for that reason, two CPUs each with 6 GB RAM.

• WORK is located centrally. Space requirement 1:1 in line with the object volume generated from enaio® capture and by enaio® exchange.

  The rendition cache is also locally centrally, calculated here with a cache size of 500 GB, long cache retention time for rapid dispatch to enaio® webclient and space required for e-mails from enaio® exchange.

• The size of the C:\ partition may be freely selected on all servers.

• enaio® components receive their own partition (here: E:\ on all servers).

• One Microsoft Office instance must be installed on servers 1 and 3 (enaio® documentviewer).

• No special features with regards to enaio® documentviewer and enaio® fulltext. Scaled up in line with database. Drive F:\ still has a buffer of 100 GB for up to approx. 12 to 15 million documents for the full-text database.

  The first recommendation is the preferred option. Here, the load is more effectively distributed across the Windows servers. In addition, a separate application server is provided for the core services.