Versions Compared

Old Version 7

changes.mady.by.user Sharon Hawkins

Saved on

compared with

New Version Current

changes.mady.by.user Sharon Hawkins

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. From the PM, InSpection, Testing Groups grid view, select the desired PM Group.
  2. Select Deactivate from the commands at the top of the grid view.
  3. InfraLink will display a warning, "One or more PM Rules will be changed to inactive. PM Tasks, Cases and WTs in initial state generated for these rules will be deleted. Do you want to continue?"
  4. Select Yes.
  5. Select the inactive PM Group.
    1. Note: User may have to adjust Status filter to include inactive PM Groups within the grid view.
  6. Select Edit to open theEdit Group form.
  7. Modify the desired PM Group settings.
  8. Enter a note in the Comments field (* required) related to the change.
  9. Change the Status back to Active once all configuration changes have been completed.
  10. Click OK at the bottom of the form.
  11. InfraLink will prompt the User, "Parameters of PM Cases generation have been updated. Do you want to regenerate PM tickets?"

  12. Click Yes to apply changes to PM Tasks that are in the default initial Status (i.e., not yet in progress).


Note
titleImpacts of PM Group Edits

Because the PM Generator creates may create PM Intervals (i.e., Cases) in advance, based on PM Group definitions, edits to a PM Group's definitions schedule and/or scope should be applied to already-created PM Cases that are not yet in progress. For this purpose, the PM Generator determines:

  • if the Case Due Date is greater than the PM Generator Start Date/Time. (Ii.e., the PM Generator only updates the Cases scheduled to be completed in the future); and
  • if the Case Status is set to the default initial value (Ii.e., the Case is not yet in progress, no work on Tasks, no update made to Case record).

For each of such Cases, the PM Generator will

  • Remove Tasks that no longer match the PM Group scope (e.g. the system element type or location have changed and no longer match the criteria specified in the PM group)
  • Remove Tasks associated with System Elements that are marked as "Deleted"
  • Add Tasks associated with active (not deleted) System Elements that match the PM Group scope criteria (i.e., those which now match the PM scope but are not currently included in the PM Case being updated)
  • For each System Element, update the Work Form reference to match that specified in the PM Group (i.e., if Work Form definitions were edited within the PM Group scope)

...

The InfraLink PM Generator generates PM Cases, including their associated Tasks, based on the requirements defined within active PM Groups. To, be clear, the PM Generator creates a separate PM Case for each occurrence of the work, as defined by the PM Group.

Gliffy Diagram
displayNameSample PM Calendar
nameSample PM Calendar
pagePin14

Daily PM Generator Runs

The PM Generator runs automatically on a daily basis. The default start time for the PM Generator is 2:00 AM (in the time zone specified for the InfraLink server). However, this start time may be adjusted by the Instance Administrator based on specific workload and usage patterns for the instance.

...