The fields described below have special functions. For a complete list of available fields, see the Lucity Data Dictionary.
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:
|
Start Date Interval |
Indicates the number of (date) units between Work Order start dates.
|
Start Interval Code |
Specifies the type of units between Work Orders that the Start Date Interval represents (e.g., days, weeks, months, years).
|
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:
Calculation
|
More information about Fixed Schedule PMs
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.
|
End Date Interval |
Indicates the number of (date) units between one Work Order ending and the next beginning.
|
End Interval Code |
Specifies the type of units between Work Orders that the End Date Interval represents (e.g., days, weeks, months, years).
|
End Next Date |
Marks the next date the PM Group will generate a Work Order.
|
More information about Floating Schedule PMs
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.
|
Odometer Interval |
Indicates the number of miles between Work Orders.
|
Next Odometer |
Specifies the upcoming odometer reading or number of miles on the vehicle that will trigger a new Work Order.
|
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.
|
Hourmeter Interval |
Indicates the number of hours the vehicle is used between Work Orders.
|
Next Hourmeter |
Specifies the upcoming hourmeter reading or number of hours on the vehicle that will trigger a new Work Order.
|
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.
|
Other Meter Interval |
Indicates the number of meter units between Work Orders.
|
Next Other Meter |
Specifies the upcoming other meter reading on the vehicle that will trigger a new Work Order.
|
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.
Example: You have a PM Group that is scheduled to generate every 3 months and want it to generate early:
|
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.
Example: You have a PM Group that is scheduled to generate every 3000 miles and want it to generate early:
|
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.
Example: You have a PM Group that is scheduled to generate every 200 miles and want it to generate early:
|
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.
Example: You have a PM Group that is scheduled to generate every 100000 units and want it to generate early:
|
Schedule Status fields
Status |
Indicates the status of the PM Group's Schedule.
|
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. |