Dependencies between object monitoring lines

  • Updated

With dependencies, you link object monitoring lines of the same technical object so that one activity also covers the other. Typical cases: A vehicle is inspected every 2 years or every 30,000 km – whichever comes first. Or the annual maintenance of a pump includes the semi-annual maintenance.

Prerequisites

One-sided and double-sided dependency

You set up the dependency on the line whose activity also covers the other. The other line is then the dependent line.

  • One-sided: The higher-level line covers the dependent line, but not vice versa. Example: The annual maintenance is the higher-level line, the semi-annual maintenance is dependent.
  • Double-sided: Both lines cover each other. Example: Inspection after 2 years (monitoring type Date) and after 30,000 km (monitoring type Counter), both with the same time schedule.

Set up a dependency

  1. Open the technical object and choose the Monitoring action.
  2. Select the higher-level line, for example the annual maintenance, and choose Object Monitoring Line › Dependencies. The Dependent Object Monitoring Lines page opens.
  3. In a new line, select the other object monitoring line in the Dependent Line No. field. Only lines of the same object are offered. Dependent Line Description shows its description.
  4. maintool asks Do you want to create a double sided dependency?
    • Yes: maintool also creates the reverse dependency.
    • No: The dependency only applies in this direction.

Result: On the Object Monitoring Lines page, the No. of Dependencies column shows how many dependent lines a line has; clicking the number opens the dependencies. The Dependent Line Nos. column lists them; you can show it via Personalize if required.

If you select the line itself or a line that refers back to this line via further dependencies, maintool displays Line … could not have a dependency to oneself.

Effect of the dependency

For the work order

  • If a work order is created from the higher-level line, maintool also enters this work order for the dependent lines. Their next date or next value is then based on this work order – each according to its own Set next Action at setting.
  • If further lines depend on a dependent line, this also applies to them.
  • If you delete the work order or its origin line, maintool also reverses the date for the dependent lines.

In the date proposal

If both the higher-level line and the dependent line are due in the period of the date proposal, maintool omits the proposal of the dependent line if the higher-level line has priority. Priority is given to:

  1. an overdue proposal over a due one,
  2. a line with the monitoring type Date over other monitoring types,
  3. otherwise the line with the earlier date or – for counters – with the smaller next value.

With a one-sided dependency, only the proposal of the dependent line can be omitted in this way; with a double-sided dependency, the proposal of either line.

Notes and limitations

  • Dependencies only exist between lines of the same technical object.
  • The dependency does not change any intervals. Each line keeps its own time schedule, its interval and its Set next Action at setting.
  • For the double-sided inspection by time or kilometers, both lines can use the same time schedule; for different activities, use different time schedules.

Related articles

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request