Lucity PM Service

This service performs necessary database maintenance and updates on the GBAEquip and GBAWork databases. Once a day, this service starts an executable called PMWOGen.exe. This process does the following actions:

Fleet

Updates Fleet Calculations

General

Updates Street Name Indexes

Performs Database cleanup maintenance

Clears old object locks

Clears audit login table records older than 90 days

Clears active user login table records older than 90 days

Clears license locks older than 5 times the license timeout

Clears Email error log records older than 90 days

Deletes expired subsets

Inventory

Sends Part Reorder Notifications

Sewer

Updates Current Asset Values for Sewer Construction records

Street

Updates most recent Street Field Inspection flags

Work

Updates Exclusion Days to the current year for season PMs

Processes PMs and creates Work Orders based on the PM schedule

Updates Planning and Budgeting calculations.

Updates Project Management calculations

Checks for overdue Requests and Work Orders and sends Notifications

Sends Start Date Notifications

Checks to see if the Work Order Numbers need to rollover

Clears out orphaned work records

Removes stale availability records

Updates Work Order calculations.

Logging

Log Files

In the process of performing these tasks, the GSXProc.exe process will be called 4 times in succession. Once this process is complete, a log file (PMWOGen.log) is created in one of the following directories:

Documents and Settings\[user name]\Application Data\Lucity_Services or Documents and Settings\[user name]\Application Data\Lucity.

Any errors will also be written to a log file in this directory.

Errors that occur in the GSXProc.exe portion of the process are written to the end of the GSLog.htm file. These htm files are stamped with their date and time. Error logs will differ from the Mobile Desktop htm logs in that error logs are usually generated in the middle of the night.

Logging in Database

The PM Service is also logged in the GBAUser.dbo.SYSTEMLOG table. Each process will have a unique identifier within this table and it will be useful to administrators because it will show which processes hung or took a long time to run.

Notification Emails

The PM Service can also be configured to automatically send out emails when it is complete. This provides users with a daily update letting them know that the nightly processes were successful. If they have this configured and do not receive and email in the morning then the processes most likely failed.

This email is configured in the Lucity Administration Tool > System > Settings > Email tab. The following settings must be configured:

List of email addresses for system health notifications
Send daily email when nightly services processes finish

Available User Parameters

All of the user configurable parameters that are available stored on the server in the CONFIG\pmchkwo.ini file. Settings and information available in the file are listed below:

[PM]

STR:TIMEPROCESS=2:00:00 AM

STR:DATEPROCESS=11/10/2005

STR:USER=MYNAME

Parameters in bold below may be customized in the program by going to Work>>Administration>>PM Setup. A brief description of each of these settings/parameters is listed below:

STR:TIMEPROCESS - This is a user defined value that identifies when the service will run. No database backups should be run during this time. The process will take 5 to 45 minutes (depending on the amount of data being processed).
STR:DATEPROCESS - When the process is called, it updates this parameter in the file to identify when it last ran (date and time).
STR:USER - This is where user information is stored. The services need this information to import the data. If a user is not listed or if the user no longer exists, the system will use the first user listed in the user database.