Last Updated on November 19, 2022 by maximosecrets


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 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.

17 responses to “Routes”

  1. Keshav avatar

    Great Post

  2. Taran avatar


    Why is the route stops becomes function in the route applications?

    If i was to reuse a route on two different PMs. on PM 1 i want to use the multi asset list and on PM 2 i want to create child work orders, i would then need to duplicate the route just to change the route stop becomes function

    Is there anyway to not have to duplicate the route object to do this?

    1. maximosecrets avatar

      Hi Taran, you are right you will need to duplicate the route and keep both maintained. There is no way to apply the function as part of applying the route, as if it were a parameter. Regards Andrew

  3. Richard Barber avatar
    Richard Barber

    Hi Andrew, love these secrets thanks for producing them first of all. With regards to the paragraph: 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. I understand that this is how it works but do you know why, and do you know if it can be changed easily, so the job plan could be added to the work order as a task for each route stop?

    1. maximosecrets avatar

      Hi Richard – pleased you are finding Maximo Secrets useful.
      You can apply a Job Plan to a Work Order Task by navigating to the Activities and Tasks application and going to the Resources tab and selecting a Job Plan. After the job plan has been applied to the task it will appear in the Children of Work Order table window and not the tasks table window, it is now a child work order. It works this way irrespective of whether the Job Plan has itself tasks. The same principle is applied with a Nested Job Plan on a Job Plan Task, the task gets created as a Child Work Order and the nested job plan applied to it.
      Therefore, if the Route was allowed to create tasks with job plans applied to each route stop, the end result would be child work orders, and so the only option for the Route which makes sense to allow the Job Plan to be entered is when child work orders are being created by the Route.
      Regards – Andrew


    This is helpful but I do have a glitch in my plan. I am trying to use the Routes in various ways. I am really wanting to use Tasks. If I drop a second task on a job plan, I can add a pre job site inspection to it, that works great. If I add 30 assets to a route and apply it to the Work Order or utilize a PM, I do get the tasks just as I would want them. However, the tasks don’t have an inspection form tied to them. I was wanting to run the work order open until all route stops had been completed, launching the Work Center inspection for, from the tasks. Do you have an idea how to direct the tasks from the route to be associated to an inspection form?

  5. james avatar

    slightly off topic, but if a route_stop is applied to an asset whose location is now in a repair store room because it was swapped with another asset. Is it reasonable to expect the route to automatically be applied to the new replacement asset?

    1. maximosecrets avatar

      Hi James,
      You are very close to the solution. When you make a route that includes rotating assets, consider making the route stop the location where the rotating asset belongs. Then Maximo will create a work order or task against the location, and if the location has one asset it will add that asset to the work order or task. It then doesn’t matter which asset actually exists at the operating location.
      Maximo records work order history against both the operating location and the asset at that operating location.
      Hope that helps – Andrew J.

  6. George avatar

    Are there pros and cons to using a child work order based route versus creating individual PMs? Is there a best practice that dictates when best to use which?

    1. maximosecrets avatar

      Hi George, I’ve not seen any best practice, but here are some functional considerations:
      1. Look at the differences between a work order and a task – one obvious one is that there is no safety on a task only on a work order. The checks on material availability is also not on a task.
      2. A work order can have tasks, a task cannot have tasks – well it sort of can but the parent task becomes a work order.
      On a task you can enter meter readings, report downtime, add failure report, add/remove SLA, and do all the normal planned and actuals for the resources, labor, crews, materials, services and tools. Multi Asset, Loc and CI is also on a task, so is a service address.

      So functionality wise there is little difference, there might be more when you consider the add-ons and industry solutions of course. But if we stick with core Maximo I would stick with a task where it feels right to be a task, and create work orders where there is more of a discreet piece of work that will be planned separately from the other sibling work orders. Some industries, O&G in particular, may be using tasks for days of work, where as in other industries tasks are normally in hours or even less than an hour. So there cannot really be a best practise because if there were one it would be industry specific.
      Regards – Andrew

      1. George avatar

        Thanks Andrew. Both options I mentioned are work order based. It’s just that one is coming straight from a PM and one from a route. So, say I have 10 similar assets. I can create a PM for each asset, or I can create just one PM with an asset-based route where the route stops become child work orders. This is the scenario I was referring to.

      2. maximosecrets avatar

        Hi George – If the PM frequency of several similar assets are the same then, use one PM and a Route. The setting on the Route will determine how it is presented on a work order. A conversation yesterday had 20 assets performed in less than one hour. Here you would definitely want one PM, one work order, with the assets on the Multi Asset, Location and CI table. On the other hand, if the work for your assets can and is normally performed by different people, then you want one PM and use child work order setting on route. If one person performs all work, but you need to record more than downtime or meter readings, or the total duration of all work on all 10 assets is at least more than one day, then consider using tasks setting. Regards – Andrew

  7. Taran avatar

    Hi Andrew,

    Currently i have many routed PM datasheet calibrations, theses generate many child work orders that i think are not required. I don’t need to understand costs or labour hours of completing each calibration on each asset or loction.

    When using a route on a PM that is selected to create entries in the multi asset and location work order table, can a data sheet calbribation be completed on all the assets and Loctions listed on the work order?


  8. Tim Pratt avatar
    Tim Pratt

    Hi Andrew, first, I love your website and reference it all the time. It has been a useful tool for me to demonstrate the value and capabilities of Maximo with leadership. Thanks.

    My question has to do with using Routes on PM records. I have set up a number of Routes of like type assets in specific buildings, all exhaust fans, for example, and set them as entries on the Multi-Asset, Location, and CI table. The location of these assets are all the same, the building level location identifier as we don’t currently have location data down past that level. I’m noticing that the work orders do not derive a location when they are created. I am assuming that this is a design feature of routes as they do not always contain assets in the same location, or could reference numerous locations. Is there a way to change this based on all of the referenced assets residing at the same location?

    1. maximosecrets avatar

      Hi Tim, when you create the PM, reference the building location and the Route. The work order will be against the location, and the Multi Asset Location and CI table will reference whatever you have defined for route stops, in your case the exhaust fan assets.
      Hope that answered your question. Andrew

  9. Piotr avatar

    Hi, I have a question, Is it possible to show routes in Locations and Asset? When I try it to connect and present in listbox it shows a list of routes which are not connected with this Asset/Location.

    1. maximosecrets avatar

      Hi Piotr – Maximo already does this. In the Assets application and Work tab, use the View Work Details button and go to the Routes tab. By default, this shows the route stops that also Include Children. Deselect this and Refresh and it is only showing the Routes where the asset is referenced as a route stop. The same dialog is available in the Locations application but as an action. Regards. Andrew

Leave a Reply

%d bloggers like this: