Sustainability & Risk / Health & Safety / Background Data

Defining Problem Types

A safety manager may want to generate a service request to follow up on a workplace incident. For example, if an employee slips in the parking lot on his way to work due to icy conditions, the safety manager will want to issue a service request to sand and shovel the area.

Note: In order to generate a service request for a workplace incident, you must have a license for the Archibus Service Desk application. Service Desk Managers or others familiar with operations at your site will use the Service Desk application to define the rules (the SLA) for guiding the service request through the system. With these rules defined, users can create service requests for handling the issue and the system will know how to handle it.

If you have a Service Desk license and want to take advantage of service requests in handling workplace incidents, you first need to define health and safety-related problem types. The service request system uses problem types to determine how to route a request through the system.

The Problem Types Table

In the Problem Types table, enter typical problems that result in workplace incidents. For example, you might define problem types of leaks, spills, general safety, and fumes as these types of issues can lead to workplace incidents.

The Problem Types table is used by other applications, including Hazard Abatement, and offers the unlimited-tier hierarchy feature so that you can optionally prefix the problem types to show related items. For example, the sample data uses the parent "CB" for the various Hazard Abatement actions, such as CB|INSPECT and CB||ABATE. To create a multilevel value, complete the Problem Type Code field in the format PARENT|CHILD, such as LEAK|CEILING and LEAK|RESTROOM. Note that "CB" stands for "Clean Building" -- the former name of the Hazard Abatement application.

You can then enter a descriptive name and comments.