PM Groups are the mechanism by which PM Cases are generated and work is scheduled for completion.

...

For Users with adequate Permissions, this view provides access to existing PM Groups, as well as the tools to manage (i.e., create, modify) PM Groups. The view follows InfraLink's standard grid view presentation.

Filtering Tips

Grid view filters allow Users to review the records displayed within the viewing pane. The following filters are helpful within the PM, Inspecting, Testing Groups grid view.

...

Follow these steps to create a new PM Group. Please note, to take full advantage of InfraLink PM work management capabilities, PM Groups should be configured according to the PM and Inspection Plan(s).

1. Access the PM, Inspecting, Testing Groups grid view.
2. Select New from the commands at the top of the view.
3. InfraLink will present the New Group form which includes two configuration tabs, General and Scope.
4. Populate all required fields, which are marked with an asterisk ( * ) and any optional fields that apply. Refer to the field-specific guidance provided below, as well as the illustration at the bottom of this section. 
   1. General Tab - Here, the User defines the following PM Group attributes and scheduling parameters:
      1. Name -  It is a beneficial to establish a naming convention for PM Groups, which makes it easier for administrators and Users to navigate the PM schedule. It is common to include references to the Contract, Location, System and/or System Element Type being maintained, as well as the frequency.
         1. Note: A PM Group Name must be unique within the associated Contract.
         2. This name will appear everywhere the PM Group is displayed, (e.g., PM schedule, Cases, Work Tickets, work history). 
      2. Status - By default, the PM Group will be in Draft status. The PM Group Status determines whether or not the PM Generator will process the PM Group definitions and generate (or update) the corresponding PM Cases. The PM Group Status also determines whether or not changes to the PM Group definitions are allowed.
         • Draft - PM Generator does not process PM Group definitions. Any PM Group settings can be modified.
           • Note: When creating a new PM Group, it is a good practice to create the group in Draft status and allow yourself an opportunity to review the configuration and make any necessary corrections before generating the associated PM Cases.

         • Active - The PM Generator processes PM Group definitions and generates (or updates) PM Cases accordingly. PM Group settings cannot be modified.

         • Inactive - The PM generator does not process PM Group definitions. As such, a PM Group should be changed to "Inactive" status when it no longer relevant or needed. PM Group settings can be modified. (Note: Users may temporarily change a PM Group's status to Inactive to modify settings.)

      3. Description - This optional field is often used to describe the purpose, specific scheduling and/or work consideration that apply to the PM.
         1. Example: A PM defined for equipment installed in spaces with restricted access may say "All items on this PM are in the restricted areas and access needs to be coordinated ahead of time."
      4. Contract - A PM Group can be associated with only one (1) Contract. This selection will impact the options displayed in subsequent fields. 
         1. Note:
            1. Certain items (e.g., PM-Type Case Category, associated Case Workflow, Priority) must be configured and associated with the selected Contract before they can be configured for the PM Group.
            2. Only System Elements associated with the selected Contract may be included in the scope of the PM Group.
            3. Only Work Forms available under the selected Contract may be included in the scope of the PM Group.
            4. If you change the Contract selection after making selections under the Scope tab, all scope definitions will be cleared and will have to be re-created.
      5. Case Category - A PM-Type Case Category is required within the PM Group configuration. This determines the Case Category and workflow associated with all Cases generated from the PM Group, once activated.
         1. Note: The desired Case Category and workflow must be created and associated with the selected Contract prior to PM Group configuration.
      6. Default Case Priority - Cases automatically generated from the PM Group will be assigned this default Priority upon creation.
         1. Note:The desired Priority must be configured within the Contract Details prior to PM Group configuration.
      7. Job Number - This optional field applies only to Contracts or Instances that utilize Job Numbers within Case records (uncommon).
      8. Advance scheduling intervals - control how far in advance the PM Cases will be generated  
         1. Example: If the PM Group defines weekly PMs and this field is set to "2" , the PM Generator will schedule work 2 intervals in advance. That is, each time the PM Generator runs, it will make sure the PM Cases are generated for the next two weeks.
      9. QC Certification Requirements - If set to "Yes", each completed task must be reviewed by authorized User (e.g., QC specialist, Maintenance Supervisor) before the PM Case can be closed.
      10. Restrict PMs to SE Statuses - The PM Generator will generate/update PM Tasks for only those System Elements in statuses that meet selected criteria at the time the generator runs.
      11. Default Assignee(s) - Generated/updated PM Cases will be automatically assigned to any User(s) defined here.
      12. Schedule Type - Select the Schedule Type that is appropriate for the intended PM Intervals. Once a Schedule Type is selected, additional configuration fields will allow you to further refine the scheduling parameters.  
          1. Once - for work that must be performed only one time, such as initial commissioning work or a one-time / ad-hoc inspection
          2. Daily - for work that must occur every day, on specific days, or every X number of days
          3. Weekly - for work that must occur every week or every X number of weeks
          4. Monthly - for work that must occur every month or during specific months
          5. Annually - for work that must occur every year or every X number of years
      13. Schedule Range
          1. 1. Start Date - defines when the PM Group schedule becomes applicable.
                1. The PM Generator will not process PM Group definitions (i.e., create/update PM Cases) prior to this date.
             2. End Date - defines when the PM Group schedule becomes inapplicable.
                1. You can define End Date by specifying the number of occurrences to be performed or by setting a specific date.
                2. The PM Generator will not generate additional PM Cases once the specified number of occurrences is reached or when the calculated Due Date for the next occurrence falls beyond the defined End Date.
             3. Scheduling Window - control how far in advance of their Due Date the work can be performed
                
                1. This setting helps control the spacing between consecutive PMs. For example, you would not want a monthly PM performed on the last week of one month and the first week of the following month.
   2. Scope Tab - Here, the User defines the System Elements associated with the PM work and the PM Tasks to be performed (i.e., Work Forms). Note: The User must make a Contract selection under the General definitions in order to specify the PM Group Scope. The Contract selection, under the General tab, determines what System Elements, Locations, and Work Forms are available for selection.
      1. Define System Elements covered by PM Group, using one of the two methods described below. (I.e., Users cannot combine the two methods for the same PM Group.) 
         1. 1. System Element Type and Location - This is the most efficient means by which to define System Elements, and this method is practical when the System Element selection is easily and accurately defined by Location and System Element Type (e.g., camera, server, etc.) A notable benefit of this option is that newly System Elements will be automatically added to the PM, as long as they meet the PM Group's specified criteria.

               1. After selecting By System Element Type and Location, click Select SE Type(s) to select one or more System Element Types.

            2. List of select System Elements - When PM-applicable System Elements cannot be easily and accurately defined by System Element Type and Location, Users must specify the individual System Elements to be included. This may occur when the System Element selection is based on somewhat complex criteria (e.g., all items of a particular kind mounted at a particular height and requiring certain equipment to complete the work). A notable drawback of this option is that InfraLink will not automatically pick up any new items that may be installed and need to be covered by the PM. It is up to Users to manually add new System Elements to the list (i.e., PM Group Scope).
               1. Click Select SE(s)... to add System Elements one by one.
               2. Click Upload System Elements to add System Elements from an imported list (See the Uploading a List of System Elements section below for guidance).
         2. Work Form - To the right of each selected System Element Type or System Element, Users define the associated Work Form. Users can select different Work Forms representing the procedures to be performed on the different System Element Types or System Elements (based on the method selected above.) Note: If only one Work Form is associated with the Contract and a System Element Type, that Work Form will populate automatically. If no Work Form (or multiple Work Forms) apply, the User will be prompted to "Select Form..."
            
            1. Work Form must be associated with selected Contract.
            2. Work Form must be associated with Selected System Element Type.
            3. If the selection options do not include the form(s) you're looking for, check the Work Form definitions and make sure they include necessary system element type and contract associations.
         3. Location - Select one or multiple Location(s) using the standard Location selector.
5. When complete, select OK at the bottom of the New Group form.

...

• The first line of the file should include the proper column names/headers (see below).
• Subsequent lines should include details for the System Elements to be added to the PM Group Scope.

Import Exceptions

Populating System Elements to the PM Group scope via file import can be a valuable time saver, but efficiency will depend on the accuracy of data within the CSV file and prerequisite configuration within InfraLink.

...

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.

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.

...

1. selecting one or multiple PM Groups within the PM, Inspecting, Testing Groups grid view,
2. opening the Task Generator menu, and
3. selecting the Run Task Generator option.

Permissions

Access to InfraLink tools and features is controlled by User Permissions. All features may not be accessible by all Users. Contact your Instance Administrator regarding User Permissions. Permissions associated with tools and features described above include:

...