Manager Configures OnSite for All Users

All OnSite users across the organization.

-- or --

Allow each OnSite user to control notification behavior; users will set these options directly from OnSite.

If you allow users to set their own options, use this tab to set the default behavior, which users can then change using the OnSite app.

For security purposes, you can have OnSite automatically log out the current user if the user has been active for a set time period.

Complete this option with the number of hours the user must be inactive on OnSite before OnSite automatically logs out the user.

If you set this to Yes, each OnSite user can configure how notifications are set by completing the options directly from OnSite. The manager can set the below options with the default behavior, which technicians can then change using the OnSite app.

If you set this option to No, the following notification options apply to all OnSite users in your organization.

OnSite users can receive a notification each time new corrective work is assigned to them. Although their assigned work is listed on the opening screen, it is handy to receive this notification in case they do not immediately see the newly assigned work on the screen.

Control for what priority of work OnSite users receive notifications:

• Emergency priority

• Emergency and Urgent priorities

• All priorities

• None -- OnSite user does not receive notifications when work is assigned to them.

The OnSite user can receive notification each time the work request changes status (such as changing to Assigned, Approved, In Process, On Hold).

Select for users to receive status notification changes for Corrective work, Preventive Maintenance, or both.

If nothing is selected, the OnSite user becomes aware of status changes by periodically looking up a specific work request and viewing the status.

When an assigned request is overdue and becomes escalated, users can receive notification.

Select to receive notifications for escalated Corrective work, Preventive Maintenance, or both.

If nothing is selected, the OnSite user becomes aware of escalated work by periodically looking up a specific work request and viewing the status.

Check this option for the OnSite user to receive notification each time they are tagged in a comment.

If this option is not selected, OnSite users will be aware of tagged comments through email.

Since tracking labor hours is important for tracking costs, you might wish to enforce that OnSite users complete the hours worked on a job before they can complete the work request.

When this option is set to Required, OnSite users cannot complete the work request until they enter their hours on the Add Work Log form.

Comments about how a job was completed can add valuable information to the request.

When this option is set to Required, OnSite users cannot complete the work request until they enter comments; the Save button will not be enabled until a comment is entered.

When an OnSite user changes a work request status, it is good practice to document the reason for the change. For example, if they change a status to On Hold, you will want to know the reason for this status. To ensure that technician-made status changes are documented, you can have OnSite to require that a comment be entered when the OnSite user changes the status.

When this option is set to Required, the technician will not be able to save the status change until they enter a comment; the Save button will not be enabled until a comment is entered.

While OnSite users are in the field addressing an issue, they might see other problems and create requests to address them.

Since the Problem Type determines the SLA that governs the work request, it is important that new requests have a defined Problem Type; otherwise, the work request cannot be processed and a manager will have to enter a Problem Type.

When this option is set to Required, the OnSite user must complete Problem Type on the Create Request form; the Save button will not be enabled until this field is entered.

A site can have a descriptive name such as Bedford Campus (Site Name field) and an identifying code, such as BEDFORD (Site Code field).

Choose the field that you want OnSite to display.

A building can have a descriptive name such as Boston Medical Campus (Building Name field) and an identifying code, such as BOSMED (Building Code field).

Choose the field that you want OnSite to display.

Since the building address can take up space on the OnSite screen, you may wish to hide the building address. This is particularly useful if your company has only one building and the technicians do not need to travel between buildings.

Choose Show or Hide.

After the technician signs in, they see a screen that groups their work requests by priority, due date, schedule date, or building. The technician can use the Group By option to change how work requests are grouped.

All of the Group By options may not be appropriate to operations at your site. For example, if a technician works only in one building, they do not need to set Group by Building. In this case, you may wish to not include Building in the list of Group By options

Use this option to control the settings available in the Group By option. Select as many settings as apply for operations at your site. You can choose:

• By Priority

• By Due Date (Overdue, Today, Due Later)

• By Schedule Date (Past Scheduled, Today, Scheduled Later)

• By Site - Building

• By Priority and Due Date (Emergency, Overdue, Today, Due Later, PM)

The work list (the screen you access after you select the options by which work is grouped) includes a summary with key details about each job, such as priority and building. It can optionally include the Equipment Code and Equipment Standard if you select these fields with this option.

To make the work list easier to read, you may wish to hide the Equipment Code and Equipment Standard from the work list. You can then access this information once you drill into the work request details.