Content Comparison

...

Windows Specific Requirements

The Windows MSI Installers installer for ServiceOptimizer requires that Windows Installer Version 2.0 or higher to be present on the machine on which the product is being installed.
The In addition, ServiceOptimizer will require both the Microsoft ODBC Driver 17 for SQL Server on Windows is required by ServiceOptimizer.
- In the event that ServiceOptimizer is being installed on the same Windows server as the MS SQL Server database, then no action is required; otherwise
- The ODBC Driver will need to be installed on the Windows server before installing ServiceOptimizer.
The and the Microsoft Visual C++ Redistributable Package 2017 is required by ServiceOptimizer. During installation of ServiceScheduling, the . However, these packages do not need to be installed as prerequisites for launching the ServiceOptimizer Windows MSI Installer - the installer will launch a Prerequisites Setup Wizard if required, to allow the package(s) to be installed.

...

ServiceScheduling will run using the default value of all initialisation initialization parameters, with one exception: OPEN_CURSORS should be checked to ensure it is set to a minimum of 300.
The ServicePower schema needs to be set to have the following:
- The locale of the Database server is assumed to be UK;
- Database instance must have the following settings:
  - NLS_CHARACTERSET is AL32UTF8; and
  - NLS_LANG is English English.

...

To run the ServiceOptimizer scripts, an installation of Perl will be required (Note: 64 bit Perl required.)
The Perl installation must include the relevant DBI and DBD for the appropriate database (DBD::Oracle modules for Oracle); these may need to be installed separately, in addition to the main Perl installation.
The standard Oracle 12c installation includes a suitable version of Perl (including the DBI and DBD modules). If your database platform is Oracle 12c the PATH and PERL5LIB environment variables should be configured to use this version of Perl.

...

The amount of storage space required will depend on the number of technicians being scheduled and, most importantly, on the number of jobs carried out by each technician. Consideration should also be given to the amount of historical data to be stored.
The ServicePower implementation team can provide advice on database storage requirements as part of the ServiceScheduling implementation process. As a general guideline, however, you should allow for a minimum disk requirement of:
- Oracle Software: 3,500 Mb
- Database instance: Total: 7,600 Mb
  - System tablespace: 300 Mb
  - Temporary tablespace: 300 Mb
  - Undo tablespace: 500 Mb
  - Redo logs: 1,500 Mb
  - ServiceScheduling data (one instance): 1,500 Mb

...

Users that need to upgrade the database will need to be able to perform schema changes. Such a user should be given at least the 'db_owner' role, and preferably the 'System Administrator' role.
A database tidy facility (called sp_dbtidy) needs to add and remove indexes, so it also needs to be run as a user who is a member of the 'db_owner' role.

...

Other users who just access the database (such as a user of a ServiceScheduling Client that accesses the database) can be given lower access privileges; but as a minimum, this should allow access to all tables, stored procedures/functions and views.

...

To run the ServiceOptimizer scripts, an installation of Perl will be required (Note: 64 bit Perl required.)
The Perl installation must include the relevant DBI and DBD for the appropriate database (DBD::ODBC for SQL Server); these may need to be installed separately, in addition to the main Perl installation.

...