ServiceAnalytics 1
On This Page:
Once you have the ServiceAnalytics application installed (see ServiceAnalytics Installation) then you will need to configure it for use within your environment.
Database configuration
There are a number of parameters in the sp083_system_parameters
database table which are used as initial or default values when performing calculations with some of the reports.
Parameter | Installed Default | Description |
---|---|---|
| 7.5 | The default number of technician hours worked per day. A warning issued if not defined. |
| 10 | The default number of minutes under which idle time is ignored when calculating idle percentages. A warning is issued if not defined. |
| 35 | The default average job duration used to calculate capacity when an operative does not have any jobs schedule. |
| 365 | This specifies the max duration of any report in which the duration can be specified in terms of days/weeks/months. The default is 365 days; calculation is performed on the basis of 7 day weeks and 30 day months. |
Custom Reports
The Custom Reports menu takes the same structure as the folder that the reports are stored in
For example (without the actual reports): | Would produce a menu structure as follows: |
The following entries in the sp083_system_parameters
database table will need to be configured to give ServiceAnalytics access to the location of the custom reports. This directory also needs to be accessible by the web application.
Parameter | Value (example) | Description |
---|---|---|
|
| This is the location of the directory containing the custom reports. |
|
(Defaults to | The custom reports menu is cached on initial use, and reloaded from this cache on each user access. This saves time on each subsequent log on, however live custom report updates are not reflected on the menu and require a Web Server restart. |
N.B. You should not install your custom reports within the Web Application directory structure because, during upgrades, this directory may be updated, causing your reports to be lost. It is safe to set this location to a directory at the same level as your ServiceManager modules directory, see Deploying Standard Version.