Routes are most often used with inspections. They consist of a set of locations or assets with a sequence that defines the order in which the inspection will take place, each record in the set is known as a Route Stop. Routes can be applied directly to a work order using the action Apply Route or a route can be referenced on a PM.

A route stop references either a location or an asset, but not both. If the asset resides at a particular location then when the route is applied to a work order the asset’s location is derived. If a location is referenced on a route stop then when the route is applied to a work order and the location has just one asset then it will be derived on the work order.

When a route is applied to a work order there are three options for what sort of records the route stops create:

  • Child Work Order
  • Entries in the Work Order’s Multi Asset, Location and CI Table
  • Work Order Tasks

Child work orders have similar capability as a standalone work order. Work Order Tasks are stored in the same table as a work order and are defined with attribute ISTASK=1. Tasks are at the bottom of the work order hierarchy and do not normally have a Job Plan or Safety Plan applied to it (not without converting it to a work order). An asset or location that becomes a record in the work order’s Multi Asset, Location and CI table (object MULTIASSETLOCCI) will still be added into the work order history of the asset or location but time and costs are not recorded individually against the asset or location. If an inspection uses the Multi Asset, Location and CI table then you can indicate that the asset or location was inspected, record meter readings or record an asset’s downtime, but not much else.

When defining a route a Job Plan can be defined on a route stop but only if the route is set to create Child Work Orders. A Job Plan cannot be defined for the other two settings, the field will be read-only.

A route is defined at the object level of SITE and can only contain assets and locations from the same site, therefore a single inspection cannot be performed across multiple Maximo sites.

The route checkbox “Route stops inherit status changes” (attribute PARENTCHGSSTATUS) is copied to the same attribute on the work order for both the parent work order and its child work orders or tasks. This field controls whether a status change on a parent work order will roll down to its children or tasks.

When a route is applied to a work order and child work orders or tasks are created then the route’s description is used as the child work order or task description. The route (attribute ROUTE) is referenced on all of the work order records including the record against which the route was applied. The identifier of the route stop (attribute ROUTESTOPID) is copied to each child work order or task and the route stop sequence number is copied to the work order sequence (attribute WOSEQUENCE).

There are a set of standard crossover fields on the route stops whose data will be copied to the work order. Attribute RTS1, RTS2, RTS3, RTS4 and RTS5 are copied to work order attributes WORTS1-WORTS5 respectively. If you add fields to the ROUTE or ROUTE_STOP objects then these can be copied to the work order using a crossover domain, however when adding a domain to attribute WORKORDER.ROUTESTOPID you will need to use a MAXLOOKUPMAP to bind in this attribute and also the ROUTE attribute as the lookup will need to use both attributes to find the right records. Therefore, in the first instance use the RTS1-RTS5 fields and redefine them to the data type and length you need.

Route Stops can support segments of a linear asset and the Path Selector button is used for finding the part of the linear asset on which the inspection will be made for each route stop.