Grouped PM Scheduling Fields

The fields described below have special functions. For a complete list of available fields, see the Lucity Data Dictionary.

Scheduling Fields - Fixed Schedule

The following fields are found on the Grouped PM Scheduling record and are used for Fixed Schedules to define when the work will occur. These fields are deactivated if the Floating Schedule fields are populated.

Last Start Date

Stores the last Start Date for a Work Order generated by the PM Group.

Note: This will typically also be the last date the PM Group generated a Work Order unless:

  • The Days Ahead field is used,
  • Previous Work Orders for the PM Group were closed late.

Start Date Interval

Indicates the number of (date) units between Work Order start dates.

  • Used to calculate the Start Next Date.

Start Interval Code

Specifies the type of units between Work Orders that the Start Date Interval represents (e.g., days, weeks, months, years).

  • Used to calculate the Start Next Date.

Start Next Date

Marks the start date for the next Work Order generated by the PM Group.

Note: This will typically also be the next date that the PM Group generates a Work Order unless:

  • The Days Ahead field is used,
  • Previous Work Orders for the PM were closed late.

Calculation

  • Calculated automatically when the Last Start Date and Start Date Interval and Start Interval Code are entered.
  • Example: A Work Order is generated on 8/15/2018 which is put in the Last Start Date field. The Start Date Interval is 1 and the Start Interval Code is Years. The system calculates the Start Next Date to be 8/15/2019.

More information about Fixed Schedule PMs

Scheduling Fields - Floating Schedule

The following fields are found on the Grouped PM Scheduling record and are used for Floating Schedules to define when the work will occur. These fields are deactivated if the Fixed Schedule fields are populated.

Last End Date

Stores the End Date for the last Work Order generated by the PM Group. Work Orders will be generated based on the last time the job was completed.

  • This is populated by the system no matter which type of scheduling is used.

End Date Interval

Indicates the number of (date) units between one Work Order ending and the next beginning.

  • Used to calculate the End Next Date.

End Interval Code

Specifies the type of units between Work Orders that the End Date Interval represents (e.g., days, weeks, months, years).

  • Used to calculate the End Next Date.

End Next Date

Marks the next date the PM Group will generate a Work Order.

  • Calculated automatically when the Last Start Date and Start Date Interval and Start Interval Code are entered.
  • Example: A Work Order is generated on 8/15/2018 and completed on 8/17/2018 which is put in the Last End Date field. The End Date Interval is 1 and the End Interval Code is Years. The system calculates the End Next Date to be 8/17/2019.

More information about Floating Schedule PMs

Scheduling Fields - Meter Based

The following fields are used to generate work based on meter readings entered for the asset.

Note: These are only enabled if the PM does not have the Grouped Asset PM box enabled and the record's Category is associated to the Fleet or Equipment module.

More information about Meter Based Scheduling

Odometer Scheduling

The following fields apply to assets whose use is measured in miles.

Previous Odometer

Specifies the number of miles on the vehicle the last time it was worked on.

  • Automatically populates from the previous Work Order's Asset > Odometer field.
  • Used to calculate the Next Odometer.

Odometer Interval

Indicates the number of miles between Work Orders.

  • Used to calculate the Next Odometer.
  • Example: If you want to set up an oil change PM to generate a Work Order every 3,000 miles, your Odometer Interval would be 3000.

Next Odometer

Specifies the upcoming odometer reading or number of miles on the vehicle that will trigger a new Work Order.

  • Automatically calculates when the Previous Odometer and Odometer Interval are entered.
  • Example: A fleet vehicle was last serviced at 52,956 miles. The Previous Odometer is 52,956 miles and the Odometer Interval is 3,000 miles. The system calculates the Next Odometer to be 55,956 miles.

Hourmeter Scheduling

The following fields apply to assets whose use is measured in hours.

Previous Hourmeter

Specifies the number of hours on the vehicle the last time it was worked on.

  • Automatically populates from the previous Work Order's Asset > Hourmeter field.
  • Used to calculate the Next Hourmeter.

Hourmeter Interval

Indicates the number of hours the vehicle is used between Work Orders.

  • Used to calculate the Next Hourmeter.
  • Example: If you want to set up a maintenance PM to generate a Work Order every 200 hours, your Hourmeter Interval would be 200.

Next Hourmeter

Specifies the upcoming hourmeter reading or number of hours on the vehicle that will trigger a new Work Order.

  • Automatically calculates when the Previous Hourmeter and Hourmeter Interval are entered.
  • Example: A pump was last serviced at 2,800 hours. The Previous Hourmeter is 2,800 hours and the Hourmeter Interval is 200 hours. The system calculates the Next Hourmeter to be 3,000 hours.

Other Meter Scheduling

The following fields apply to assets whose use is measured in some unit other than miles or hours.

Previous Other

Specifies the number of meter units on the vehicle the last time it was worked on.

  • Automatically populates from the previous Work Order's Asset > Other meter field.
  • Used to calculate the Next Other meter.

Other Meter Interval

Indicates the number of meter units between Work Orders.

  • Used to calculate the Next Other meter.
  • Example: If you want to set up a maintenance PM to generate a Work Order every 100,000 units, your Other meter Interval would be 100000.

Next Other Meter

Specifies the upcoming other meter reading on the vehicle that will trigger a new Work Order.

  • Automatically calculates when the Previous Other meter and Other meter Interval are entered.
  • Example: A piece of equipment was last serviced at 119,200 units. The Previous Other meter is 119,200 units and the Other meter Interval is 100000 units. The system calculates the Next Other meter to be 219,200 units.

 

Scheduling Fields - Other

Generating work ahead of schedule

The following fields match up with the other scheduling fields to force a PM Group to generate a Work Order early.

Days Ahead

Enables users to generate a PM Group's Work Order before the next specified date is reached. This gives you a heads up that the work should start soon.

  • This field applies to Fixed and Floating Schedules.

Example: You have a PM Group that is scheduled to generate every 3 months and want it to generate early:

  • Enter 2 in the Days Ahead field.
  • The Work Order will generate 2 days before the scheduled Start Next Date.
  • The Work Order's Start Date will still be the same as the PM's Start Next Date.

Odometer Ahead

Enables users to generate a PM Group's Work Order before the next specified odometer reading is achieved. This gives you a heads up that the work should start soon.

  • This field applies to Odometer schedules

Example: You have a PM Group that is scheduled to generate every 3000 miles and want it to generate early:

  • Enter 100 in the Odometer Ahead field.
  • The Work Order will generate when the asset's Current Odometer is within 100 miles of the PM Schedule's Next Odometer.

Hourmeter Ahead

Enables users to generate a PM Group's Work Order before the next specified hourmeter reading is achieved. This gives you a heads up that the work should start soon.

  • This field applies to Hourmeter schedules

Example: You have a PM Group that is scheduled to generate every 200 miles and want it to generate early:

  • Enter 10 in the Hourmeter Ahead field.
  • The Work Order will generate when the asset's Current Hourmeter is within 10 hours of the PM Group Schedule's Next Hourmeter.

Interval Ahead

Enables users to generate a PM Group's Work Order before the next specified other meter reading is achieved. This gives you a heads up that the work should start soon.

  • This field applies to Other Meter schedules

Example: You have a PM Group that is scheduled to generate every 100000 units and want it to generate early:

  • Enter 10000 in the Other meter Ahead field.
  • The Work Order will generate when the asset's Current Other Meter is within 10000 units of the PM Schedule's Next Other Meter.

 

Schedule Status fields

Status

Indicates the status of the PM Group's Schedule.

  • 1|Awaiting WO Generation - The PM Group is scheduled but is waiting to be triggered to generate a Work Order.
  • 2|WO Generated - The PM Group's Schedule was triggered and a Work Order was created. The PM Group is waiting for the Work Order to close.

WO Number

Displays the ID for the active Work Order that is linked to the PM Group when the group's Status is 2| WO Generated.

Appears blank when the group's Status is 1|Awaiting WO Generation.

Initiated Date

Displays the date the active Work Order that is linked to the PM Group was created. When the PM Group's Status is 2| WO Generated.

Appears blank when the PM Group's Status is 1|Awaiting WO Generation.