Concepts

Tasks

Settings

Dynamic Inspection Routes

A dynamic inspection route is defined on a standard task and comprises a list of assets (ordered in walk-around sequence) and a set of criteria for including the assets’ indicators. When a list of indicators to read is generated using the standard task, indicators with properties that match the criteria are included.

This section explains how dynamic routes work.

Inclusion Criteria for Dynamic Indicators

Dynamic indicators are selected based on the inclusion criteria specified in the standard task, which can be any of the following:

•

Trade

•	Expected frequency

•	Asset operating condition

•	Maintenance group

•	PdM technology

•	Indicator collection set

For example, if collection frequency, trade, and asset operating condition are used as inclusion criteria, indicators with the same collection frequency, same trade, and same operating condition as the standard task are included in the task’s list of indicators.

When defining a criterion, you can name up to three values in addition to the one on the standard task. For example, you could select indicators based on four PdM technologies: the standard task’s technology and three additional technologies that you specify. Indicators that have not been assigned a property can also be considered for inclusion. Using this example, you would also select Indicator’s technology is blank. An indicator with any of the four technologies or none at all would be included in the list.

Tip: You can add inclusion criteria to dynamic routes by customizing the application. For example, a custom property could be added to both standard task and indicator. Then a validation rule is added to the task’s dynamic indicator collection. For more information, see “Customization Guide” in Help.

Route Assets

A route asset is typically a system asset or large piece of equipment with one or more indicators to be read as part of an inspection task or PM inspection route. Route assets are listed on the standard task in the order in which they are visited.

The same route asset can be included more than once on a route. For example, a large asset might be visited once to read indicators on the front and again later (after other assets) to read indicators on the back of the asset. You can assign a sequence number to a route asset, specify whether it includes the assets below the current one in the physical hierarchy, and give it a collection group that identifies a location. You can also specify the asset statuses that allow indicators to be triggered.

Collection groups are handy for large assets whose indicators are read at different points in the route. For example, with a larger piece of equipment, indicators could be split into two groups: front and back indicators. The front and back of the asset might be visited at different times on the route or possibly on different routes (standard tasks).

Dynamic and Static Indicators

Dynamic indicators are virtual links between indicators and standard tasks; they are not stored in the APM database as indicators to read on the standard task. Consequently, you cannot define task-specific values, such as sequence numbers with dynamic indicators on the standard task (these values must be specified on the indicator instead). Dynamic indicators are used to create indicators to read only when a checksheet or work order task is created from the standard task.

You can add indicators to a standard task instead of, or in addition to, using a dynamic route. These are termed “static indicators” and can be grouped with a route asset so that they are listed with the asset’s dynamically-selected indicators in the list of indicators to read. Otherwise, static indicators are placed and the end of the list in sequence number order.

For more information, see Setting up a Dynamic Inspection Route on a Standard Task.

Options for Indicator Collection Timing

There are four options for selecting the indicator readings to included on checksheets and work order tasks:

•	You can specify that all of the standard task’s indicators are included whenever a checksheet or work order task is created for the standard task. This option is handy for repair tasks, for example.

•

Alternatively, you can specify that only indicators that are due to be collected before the task’s next due date are included in the list of indicators to read. For example, if the task’s next triggering is determined by its monthly frequency, all indicators due to be collected in 30 days are included in the list of indicators to read.

With this option, you can also specify planning lead time, which is the amount of time needed between generating the list of indicators and taking the readings. For example, you might generate checksheets two days ahead of time to allow the work to be planned and scheduled. When the list of indicators is generated, the start date of the task cycle is offset by the planning lead time.

For example, consider a monthly task with a five-day lead time. The system calculates the collection end date by adding the planning lead time (five days) and the task’s frequency (30 days) to the current date. All indicators with a “next reading due date” that falls before the end date are included in the list of indicators to read.

•	The third option for controlling how indicators are included on checksheets and tasks is to specify a collection horizon. For example, if the horizon period is one year, only indicators with frequencies of one year or less are included.

•

The fourth option is exception-based inspection. This means that indicator readings included in the checksheet are restricted to those that are mandatory, for indicators where the previous reading resulted in an alarm, or for indicators where the alarm on the previous reading was acknowledged with “monitor” or a work document and the document is not closed.

In addition, you can specify the minimum percentage of indicators that must be read before the checksheet can be processed.

For more information, see Setting Inspection Options for a Standard Task.

Site Settings for Dynamic Inspection Routes

Before setting up dynamic routes on standard tasks, you can define site-level settings to make route creation efficient.

In reliability program settings, you can select default values for inspection routes. When a standard task is created, these values are copied to the inspection route. The person setting up the route can change them as required.

Inspection routes settings are:

•	Indicator selection criteria. When a standard task is created, the criteria are selected by default in the Dynamic tab.

•	Default options for route assets. You can specify that collection group is a matching criterion. You can also decide whether the asset alone or the asset and its descendants is the default selection.

•	Default planning lead time. This is the interval between when the list of indicators is generated and when the work is performed.

For more information, see Setting Default Values for Inspection Routes.

In the site’s indicator settings, you can create the collection sets and collection groups that will be used to select indicators for inclusion on dynamic routes. For more information, see Setting up Collection Groups for Dynamic Routes and Setting up Collection Sets for Dynamic Routes.

Indicator Collection Reports

You can define and generate indicator collection reports that show the status of an asset’s indicators. The report can include indicators for the asset only or for the asset and its descendants.

The report’s main purpose is to show indicators that are not being collected on any standard task. It also lists:

•	Indicators that are being collected on one standard task

•	Indicators that are being collected on two or more standard tasks

•	Information about the tasks that collect the asset’s indicators, including whether the indicator was dynamically added to the task or is a static indicator

•	Differences (mismatches) between indicator and standard task search criteria (trades, expected frequencies, operating conditions, maintenance groups, PdM technologies, and collection sets)

The collection report allows you to identify redundancies and omissions in indicator collection. You can then use this information to modify indicators and standard tasks, ensuring that indicator readings are being collected efficiently.

The indicator collection report can be set up to run manually or automatically based on a pre-defined recurrence pattern. It can also be suspended or activated.

For more information, see Working With Indicator Collection Audit Reports.