Pre-Requisites

Assumptions

You have a good working knowledge of Windows, the basic principals of databases, their setup and administration

You have knowledge of Windows Services, command line functionality and the registry

You have direct dial in access to the Windows server (via remote desktop) where V1 is to be installed

The Windows server where V1 is to be installed is internet connected

You have received your licenses from the V1 Support team

.NET 3.5 SP1 is installed on the V1 server and client PC’s (where applicable)

You have access to the SQL / Oracle / PostGRE instance you are going to use and have credentials to hand sufficient to create a database

You have access to the appropriate database management tool (such as the SQL Server Management Studio / pgAdmin)

If any of the above are not in place / you're unsure, STOP.
Do not continue unless all the assumptions are satisfied or there is the potential for lengthy and costly delays to the project.

---

Document Archiving

The core of Document Archiving modules includes the authentication module (DbLogin) and a repository (DbArchive) to store the scanned / imported images.
The minimum high level requirements for a server to run the core Document Archiving components are:

Component	Specification
Operating Systems	Microsoft Windows Server 2012 (R2) Microsoft Windows Server 2016 Microsoft Windows Server 2019 Microsoft Windows Server 2022
RAM	8GB
Processor	Quad Core
Disk Space	10 gigabytes
LAN	Min 1GB LAN to clients

Component	Specification
Supported Databases	Microsoft SQL Server 2008 (R2) Microsoft SQL Server 2012 Microsoft SQL Server 2014 Microsoft SQL Server 2016 Microsoft SQL Server 2017 Microsoft SQL Server 2019 Microsoft SQL Server 2022 Oracle 11g only PostGRE13 onwards

NOTE: Microsoft Azure SQL Databases are not supported.

The server topography can be either of the following:

• PostGRE, on the same server as the V1 server
• PostGRE, on a different server to the V1 server
• SQL, on the same server as the V1 server
• SQL, on a different server to the V1 server
• Oracle, on the same server as the V1 server
• Oracle, on a different server to the V1 server

The minimum requirements for a client PC to run the core Document Delivery / Archiving components are:

Component	Specification
Operating Systems	Windows 7 onwards 32 or 64 bit
RAM	8GB
Processor	Quad Core
Disk Space	5 gigabytes

---

OCR

The `core` OCR components include the authentication module (DbLogin), a file repository* (DbArchive) to store the scanned / imported images, an OCR module (ABBYY) and the services necessary to process images.

The OCR process is very processor and memory intensive so if the minimum specification (or better) is not adhered to, the installation will experience performance and reliability problems.

Ideally, the server components should always be installed on a dedicated server.
Under no circumstances should they be installed on, for instance, the same application server as the FMS / ERP being integrated with.

Essentially, the better the specification of the server, the better it will perform. The minimum high level requirements for a server to run the core OCR components are.

Component	Specification
Operating Systems	Microsoft Windows Server 2012 (R2) Microsoft Windows Server 2016 Microsoft Windows Server 2019 Microsoft Windows Server 2022
RAM	16GB
Processor	8 Cores
Clockspeed	2.8GHz
Disk Space	10 gigabytes
Disk Plate	Solid State
LAN	Min 1GB LAN to clients

Component	Specification
Supported Databases	Microsoft SQL Server 2008 (R2) Microsoft SQL Server 2012 Microsoft SQL Server 2014 Microsoft SQL Server 2016 Microsoft SQL Server 2017 Microsoft SQL Server 2019 Microsoft SQL Server 2022

NOTE: Microsoft Azure SQL Databases are not supported.

It is recommended in all cases the database server is seperate to the OCR server.

The minimum requirements for a client PC to run the core OCR components are:

Component	Specification
Operating Systems	Windows 7 onwards 32 or 64 bit onwards
RAM	8GB
Processor	Quad Core
Disk Space	5 gigabytes

---

Email

During the implementation of SmartMail, you will be prompted for the following details and they must be known before installation to ensure it's setup is completed successfully.

• You have details of the customer’s mail server configuration
• SMTP or hosted by Outlook365 / Gmail
• Server address
• Server authentication
• Administrative email address (this email address is one who will be informed of activities on the server, so the I.T department for instance)

The minimum requirements for a server to allow mail relaying are:

Component	Specification
Mail Server	Mail Server Supporting SMTP delivery, MAPI or MSGraph Hosted Outlook 365 Hosted Gmail

---

Print

You are advised to have at least one physical printer capable of printing A4/Letter documents from PDF's configured and available for testing.

Where barcode printing, a barcode printer configured and available for testing (recommendations below).

When shared, ensure the share name doesn’t contain spaces.

These details include ensuring you have setup a user who has these printers shared against them. If this is not a requirement, this can be skipped.

Ensure the transactional printers and barcode printer(s) to be used are accessible and visible to the server you intend to install V1. They must be accessible by the Windows user.

For example, when logged in to the server where V1 is installed, logging in with the Windows user and opening Windows File Explorer, entering \\PRINTSERVER\ shows the printer(s).

---

Scanning and Hardware

The recommendations to allow image processing for Document Archiving are:

Component	Specification
Scanner	TWAIN or ISIS / Kofax - Compatible workgroup scanner capable of scanning to TIFF or JPEG. Low volume - A4/Letter only – KodakAlaris S2000 series, eg S2070 Medium volume - KodakAlaris S3000 series, eg S3060 High volume - KodakAlaris i4000 or i5000 series, eg i4850 NOTE: Kofax VRS Elite / AIPE recommended when using barcode recognition.
Barcode Printing	Desktop Zebra Label Printer - preferably with Ethernet port - Zebra ZD421 Printer is connected to the network via a print server. Depending on the configuration, this must be accessible by a domain Windows user.
Barcode Labels	Type A 55mm x 32mm if your transaction numbers are typically less than 13 characters Type C 89mm x 39mm if your transaction numbers are typically greater than 13 characters
Transactional Printers	Printers must be ‘PDF enabled’, so assuming printing from the command line on the V1 Server: copy mypdf.pdf \\myprintserver\mysharedprinter Produces the result: 1 file copied. The PDF prints to the printer specified.