You have a few options depending on how closely you want the activities tied to each route asset.
Option 1 - Child Work Orders (recommended)
Configure the Route to create Child Work Orders. This route option allows a Job Plan to be associated to the Route Stop. When the PM generates work, each Route Stop becomes its own child work order against the relevant asset/location and receives the associated Job Plan tasks. This is generally the preferred approach when the same set of activities must be performed independently against each asset.
Option 2 - Route Stops as Work Order Tasks
If the preference is to avoid child work orders, Route Stops can be configured as Work Order Tasks. In this case, each Route Stop effectively becomes the activity itself, with the description populated as the inspection/check to perform.
As the Route Stop can reference an asset or location, and the same asset can be specified multiple times on a route, this can be used to model multiple activities against the same asset.
The drawback is that you are maintaining the activity definitions on the Route rather than within a Job Plan, so the same information can end up being maintained in multiple places.
Option 3 - Inspection Forms
If these 10 activities are really inspection questions/checks rather than maintenance tasks, it may be worth considering Inspection Forms instead.
An Inspection Form can be associated to:
a Route Stop
a Multi Asset/Location record
an Asset or Location directly
This often provides a cleaner solution than creating large numbers of tasks purely to capture inspection responses.
Additional consideration - Multi Asset/Location
If a single work order is being used across multiple assets, the Multi Asset, Location and CI table includes the PROGRESS checkbox. This can be used as a per-asset sign-off to indicate that work has been completed against that specific asset/location. Some organizations use this as a lightweight way of tracking completion at the asset level and then add validation logic to ensure all applicable assets have been marked complete before the parent work order can be completed.
Ultimately, if the requirement is:
"Perform the same 10 activities independently against every asset on the route"
then the Child Work Order approach is usually the cleanest and most maintainable solution. If the activities are actually inspections, an Inspection Form may be a better fit than tasks altogether.
I hope this helps but as you have found out job plan tasks and route_stop tasks work independently of each other.
If you have any more questions don't hesitate to ask
------------------------------
Joey Baah
Naviam
------------------------------