About Checkpoint Schedule Definition

You can define a schedule for a checkpoint via the Checkpoint Task, which is linked to the Measurement Location or Lubrication Requirement representing the checkpoint. The Checkpoint Task datasheet appears in the Schedule section of the workspace for a selected Checkpoint.

Notes:

When you schedule a checkpoint task for a ML or a LR, the minimum time between events should at least be 15 minutes.
You cannot define schedules for Checkpoints that are part of a condition.

Details

When you are working with Checkpoint Tasks and schedules associated with checkpoints, it is important that you understand how the fields in the Checkpoint Tasks work and how the GE Digital APM system determines what Routes and checkpoints are due or overdue. The schedule that you define for the checkpoint determines the following dates for the reading associated with a checkpoint:

The next date and time on which the reading becomes due (i.e., the earliest time at which the reading should be completed). This value is stored in the Next Date field in the Checkpoint Task and is calculated automatically according to the defined schedule.
The date and time on which the reading becomes non-compliant (i.e., overdue). This value appears in the Non-compliance Date field in the Checkpoint Task and is calculated according to the defined schedule and Non-compliance Interval, if defined. The following examples assume that the Non-compliance interval is undefined.

For example, if you specified that the checkpoint should be completed every 4 hours, and should not adjust for Daylight Saving Time:

The schedule might be defined as Due every 4 hours beginning on Nov 2, 2015, at 11 A.M.
The Next Date value would be Nov 2, 2015, at 3 P.M.
The Non-Compliance Date value would be Nov 2, 2015, at 07:00 P.M.
The Non-Compliance Next Check Date value also would be Nov 2, 2015, at 07:00 P.M.

As you can see, the values are separated by 4 hour increments, which is in accordance with the defined schedule.

When a new reading is taken for a checkpoint, the following fields are updated in the Checkpoint Task:

Last Date, which contains the last date and time on which a reading was taken for the checkpoint.
Next Date
Non-compliance Date
Non-compliance Next Check Date

Continuing with the previous example, if you took the reading on Nov 2, 2015, at 03:30 P.M.:

The Last Date value would be Nov 2, 2015, at 03:30 P.M., which is the time that you took the reading.
The Next Date value would be updated to Nov 2, 2015, at 07:00 P.M.
The Non-compliance Date value would be updated to Nov 2, 2015, at 11:00 P.M.
The Non-Compliance Next Check Date value also would be Nov 2, 2015, at 11:00 P.M.

As you can see, the Next Date and Non-compliance Date values are updated according to the defined schedule and not according to the Last Date value.

Note: You can also define a schedule in which the next date that a reading should be completed is a certain amount of time after the reading was last completed. With this type of schedule, the Last Date value would be used to determine the Next Date and Non-compliance Date values. For example, if the defined schedule in this example was Due 4 hours after last occurrence, the Next Date value would be Nov 2, 2015, at 07:30 P.M. (i.e., 4 hours after the date and time in the Last Date field).