Admin ServiceManager Further Details ServiceAnalytics

On This Page:

Database configuration
Custom Reports

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
`sm_rpt_AvgTechHoursPerDay`	7.5	The default number of technician hours worked per day. A warning issued if not defined.
`sm_rpt_IdleThreshold`	10	The default number of minutes under which idle time is ignored when calculating idle percentages. A warning is issued if not defined.
`sm_rpt_AverageJobDuration`	35	The default average job duration used to calculate capacity when an operative does not have any jobs schedule.
`sm_rpt_MaxDaysDuration`	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.

Additionally, if you are using Crystal Reports Server, the following parameters must also be configured based on the values as installed.

Name	Value (example)	Description
`sm_rpt_CRS_CMSName`		This is the name of the CRS server; unless a value is defined here CRS integration will be disabled. Contact your CRS administrator for this information.
`sm_rpt_CRS_Username`	ServiceAnalytics	This is the name of the user who will manage the ServiceAnalytics reports.
`sm_rpt_CRS_Password`		The password for the above user.
`sm_rpt_CRS_AuthType`	secEnterprise	The authentication type, the default is secEnterprise. Check CRS documentation (or your CRS administrator) for other types supported.
`sm_rpt_CRS_ReportDir`	Analytics	This is the name of the folder created to hold the reports.

It is the responsibility of the CRS user (ServiceAnalytics, in the above example) to manage the reports on CRS. If CRS is reinstalled, moved etc. the reports will need to be reloaded and any changes to the CRS setup need to be updated in the ServiceScheduling database table above.

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

sm_rpt_CustomReportDir

C:\Custom Reports\TestReports

This is the location of the directory containing the custom reports.

sm_rpt_CRS_CustomReportDir

C:\Custom Reports\TestReports

This is the name of the folder containing the custom reports. The folder must belong to the user defined in the CRS setup (defined in Deploying Crystal Reports Server (CRS) Version).

sm_rpt_CustomReportMenuCache

YES or NO

(Defaults to YES, i.e. cache the report menu)

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.