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

This article provides information and guidance on the following topics related to PM Groups.

PM, Inspecting, Testing Groups Grid View

PM Groups define what tasks needs to be performed on what equipment and how often. The InfraLink PM Generator automatically creates PM Cases, or updates existing PM Cases, based on those PM Group definitions.

PM Groups are accessed and managed (e.g., created, edited) from the PM, Inspection, Testing Groups grid view. To access this view:

1. Open the Main Menu from the top-level navigation bar.
2. Select Manage Groups from the PM, Test, Inspect stack.

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.

• Contract -This filter limits the view to the groups associated with one or more selected Contracts. Note: Each PM Group is associated with only one Contract.
• Category - Each PM Group generates Cases of a PM-Type Case Category. This filter limits the view to groups that generate Cases of a particular Case Category.
• Status - This filter limits the view to PM Groups by their current status (i.e., Draft, Active, Inactive).
• Recurrence Type - This filter limits the view to groups according to their PM frequency (e.g., daily, weekly, monthly).
• Location - This filter limits the view to PM Groups whose scope includes at least one System Element associated with a particular Location (or its sub-locations).
• System - This filter limits the view to PM Groups whose scope includes at least one System Element belongs to a particular (i.e., selected) System.
• System Element Types - This filter limits the view to PM Groups associated with one or more selected System Element Types.
• System Elements - This filter limits the view to PM Groups associated with one or more selected System Elements (i.e., specific System, Device, Component, etc.) 
• Requires QC Certification - This filter limits the view based on PM Groups' QC Certification configuration (i.e., required, not required or both).

Creating a PM Group

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.

Uploading a List of System Elements

When defining the System Elements under the PM Group scope, you may save time by uploading a file with the listed System Elements instead of selecting System Elements one by one.

1. Upon selecting List of System Elements as your method for identifying System Elements, click the Upload System Elements button.
2. InfraLink will present the Import System Elements / Forms form. Populate all required fields.
   1. Top Level System - Required for newly created System Elements only
   2. Base Location - Used as the default Location for newly created System Elements if no Location specified within the import file.
   3. File - If all System Elements within your import file already exist in InfraLink, File is the only required field.
3. Once all required fields are complete, select Import at the bottom of the form.
   1. If InfraLink finds errors in the data file, a Processing Error(s) summary will be provided.  All errors must be corrected before the import file will be accepted.
   2. If InfraLink finds no errors in the data file, the listed System Elements will be populated to the PM Group scope.

File Format

Before you can upload a list of System Elements to your PM Group Scope, you must prepare a properly formatted file in comma-separated values (CSV) format.

• 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.

Data errors will result in a failed import. All identified processing errors must be corrected before the list of System Elements will import. InfraLink does not process partial imports.

Cloning a PM Group

In some situations, the creation of a new PM Group may be quickly accomplished by cloning an existing PM Group. This option is most often utilized when the new PM Group will vary only slightly from an existing PM Group. To accomplish this, you would create a clone of the existing Group, incorporate the necessary modifications, and save as a new Group with a unique name.

1. Access the Main Menu from the Top-Level Navigation toolbar.
2. Select Manage Groups from within the PM, Inspect, Test stack.
3. From the PM, Inspection, Testing Groups grid view, select the existing Group you wish to clone.
   1. User may need to apply filters to locate the desired PM Group.
4. Click the Clone button at the top of the top of the view. This will open the Clone Group form.
   1. Form field entries and selections will mirror that of the existing PM Group, but the Status field will be set to Draft.
5. By default, the form will list the Name as "Copy of..." the existing group. Enter a new PM Group name that is clearly distinguishable.
6. Edit other fields in the General or Scope sections, as needed.
   1. Reference the Creating a PM Group section above for field-specific guidance.
7. When changes are complete, select the OK at the bottom of the Clone Group form.

Editing a PM Group

To prevent discrepancies, InfraLink will not allow changes to a PM Group that is Active status. If you need to make changes to an existing PM Group:

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).

Removing a PM Group From the Schedule

If a PM Group is no longer needed and the PM Generator should not schedule work based on the group's definitions, the PM Group Status should be changed to Inactive. 

InfraLink PM Generator

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.

Manual PM Generator Runs

In some situations it may be necessary to run the PM Generator manually, without waiting for the scheduled daily run. For example, if one or more PM Groups are modified and the changes must take effect immediately, you may run the PM Generator manually so that the project team can start completing the associated PM Tasks.

Users with sufficient Permissions can run the PM Generator manually by:

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:

• PM, Inspecting, Testing Groups Grid View Access: PM Rules → General → Read and PM Rules → General → Create, Delete, or Update
• Creating PM Group: PM Rules → General → Read  and  PM Rules → General → Create
• Cloning PM Group: PM Rules → General → Read  and  PM Rules → General → Create 
• Editing PM Group: PM Rules → General → Read  and  PM Rules → General → Update
• Deleting PM Group: PM Rules → General → Read  and  PM Rules → Delete
• Manual PM Generator Run: PM Rules → PM Generator → PM Generator Launch

A preventive maintenance schedule (or a schedule of similar activities, as discussed in the intro) is generated based on a collection of PM groups. Each PM group defines

• What system elements the work needs to be performed on;
• What form (procedure) should be used for each system element;
• When the work is due to be completed; and
• How frequently it should be repeated. 

This document will discuss how to navigate already defined PM groups, how to create and modify them, and how to disable the groups that are no longer relevant.

• Browsing Defined PM Groups
  • Filtering Options
  • Quick Search
• Defining a New PM Group
  • Specifying PM Group Name and Description
  • Selecting PM Group Contract
  • PM Group Status
  • Setting PM Schedule
  • Specifying Scope
    • Specifying PM Scope by Selecting the System Element Location(s) and Type(s)
    • Specifying PM Scope by Selecting Individual System Elements
• Removing a PM Group From the Schedule

Browsing Defined PM Groups

The "Manage Groups" view provides access to the configured PM groups, as well as the controls to create new and modify the existing ones. The view is available to users with the "PM Group - View" and "PM Group - Create" or "PM Group - Edit" permissions under at least one of the contracts. In other words, a view is intended to be used by the individuals responsible for managing PM schedules under their respective contracts.

Filtering Options

The Manage Groups view relies on a typical layout with a filtering panel on the left and the content area configured as a grid. The most common filtering options available for the Manage Groups view are described below:

...

Use this filter to narrow down the view by status:

• Draft - focus on the PM groups that are being defined and have not been activated yet. That is helpful during the initial phases of the project.
• Active - focus the PM groups that are active and are processed by the PM generator.
• Inactive - focus on the already deactivated groups. This option may be useful to keep an eye on the PM groups that have been temporarily deactivated for the purposes of making changes.

...

Quick Search

In addition to the filter options included in the filter panel, you can use the Quick Search control in the top right corner of the Manage Groups view to filter the list by PM group name.

Defining a New PM Group

The "Manage Groups" view (Main Menu -> PM, Inspections -> Manage Groups) allows the users with sufficient privileges to create new PM groups and to edit the existing ones:

• The "New Group" control, which initiates creation of a new PM group, is available to all users who have the "PM Group - Create" permission under at least one of the contracts.
• The "Edit" control, which initiates modification of an existing PM group, becomes available when a PM group is selected, provided that the user has the "PM Group - Edit" permission under the contract, with which the selected PM group is associated.

The following sections offer detailed instructions for configuring the key elements of the PM group definitions that include:

• PM Group Name and Description
• PM Group Contract
• PM Group Status
• PM Schedule Definitions
• PM Scope

...

Specifying PM Group Name and Description

The PM Group Name is an alphanumeric identifier of the PM Group, which will appear everywhere the PM group is displayed, i.e. on the PM schedule, individual cases and work tickets, and work history records.

...

From the operational standpoint, it is a good idea to establish a naming convention for PM groups to make it easier for the IMMS 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, and frequency in the PM group name.

The PM Group Description is a free text field. In most cases, it is used to capture the notes describing the purpose and, perhaps, specific scheduling and/or work consideration that apply to the PM. For 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."

Selecting PM Group Contract

Any work tracked in IMMS, including PMs and similar activities, must be associated with a contract, which, in turn, drives the workflow, access privileges, and what equipment the work may be related to. As such, a PM group must be associated with a contract, and the contract association defined for the PM group will also apply to all cases and work tickets, if defined, generated based on the PM group definition.

Additionally, associating a PM group with a contract has the following implications:

• Only the system elements associated with the selected contract may be included in the scope of the PM;
• Only the forms available under the selected contract can be chosen when defining the scope.

When creating or editing a PM group, the contract selections will be limited to those items for which you have the "Contract - View" and "PM Group - Create" permissions.

PM Group Status

The status of the PM group determines whether or not the PM generator will process the PM group definition and generate or update the corresponding PM occurrences (represented by cases in IMMS). The status also determines whether or not changes to the schedule and scope components of the PM group are allowed.

IMMS supports the following PM group status options:

• Draft. When you first create a PM group, it will be saved as "Draft". Any settings can be modified while the PM group is in the draft status.
• Active. When the PM group is fully defined, its status needs to be changed to "Active". The PM generator processes Active PM groups and generates PM cases based on their definitions.
• Inactive. Inactive PM groups are not processed by the PM generator. As such, a PM group's status should be changed to "Inactive" when the PM group is no longer relevant (i.e. the corresponding work no longer needs to be performed). Additionally, you may be required to temporarily change the PM group status to inactive to modify some of its configuration settings.
  

Setting PM Schedule

In general, the PM schedule defines when the work is required to be completed. The IMMS PM generator will create a PM case for each due date calculated based on the schedule defined by the PM group. This is best explained using an example. 

For example, if PM group is defined for work to be completed every 2 weeks by Thursday starting on March 4, 2016, the IMMS PM generator will generate a PM case with the due date of March 4, 2016, another PM case with the due date of March 18, 2016, yet another PM case with the due date of April 1, 2016, and so on.

Additional schedule-related settings included in the PM group define when the schedule becomes effective, when it stops being effective, how far in advance the PM occurrences will be generated by the IMMS PM generator, and, finally, how much time the project team will be given to complete each PM.

The following table discusses each of the applicable configuration settings in greater detail:

...

In order to assign work to technicians and manage the team's workload, you want the PM cases for the specific occurrences to be generated. At the same time, you don't want to generate cases for the PM occurrences that are too far in the future, as they may likely change and will only clutter the views in the system.

This configuration setting allows you to control how far in advance the PM cases will be generated.

For example, if the PM group is defined as weekly, and this setting is set to 2 (i.e. "Schedule work 2 intervals in advance"), then each time the IMMS PM generator runs, it will make sure the PM cases are generated for the next two weeks.

...

This setting defines the recurrence pattern:

• The "Once" option is used to define work, which needs to occur only one time, such as initial commissioning work or a one-time / ad-hoc inspection;
• The "Daily" option is used to define work, which must occur every day or on specific days every so often;
• The "Weekly" option is used to define work, which must occur every week or every several weeks (e.g. every 2 weeks);
• The "Monthly" option is used to define work, which will be due every month or during specific months; and, finally,
• The "Annually" option is used to define work, which will be due every year or every several years.

...

After the schedule type is selected, IMMS will allow you to specify the frequency and to further refine when the PM completion will be due. Specifically,

• If the schedule is defined as weekly, you will be able to specify by which day of the week the work will have to be completed.
• If the schedule is defined as monthly, you will be able to specify completion by a certain date (e.g. 25th of each month) or by a certain day of a certain week (e.g. second Thursday of a month);
• If the schedule is defined as annual, you will be able to specify completion by a certain date (e.g. 25th of June) or by a certain day of a certain month (e.g. last Friday of September);

...

This section contains a few additional parameters that define how the work is scheduled and when it will be expected to be performed.

• Scheduling Window <N> days. The scheduling window defines how far ahead of the due date the work can be performed. For example, if a PM schedule requires work to be completed by Friday of each week, it may not make sense to complete the work on Friday one week, on Monday the next week, and on Friday the following week, as the interval between the second and third occurrences of the PM will be almost two weeks. The scheduling window allows the PM planner to prevent such situations by specifying a short scheduling window. For example, if the scheduling window is set to 1 day, the work will have to be performed on the due date; If the scheduling window is set to 2 days, the work can be performed on the due date or the day prior, and so on.
• Start Date. The start date defines when the schedule defined by the PM group becomes applicable.
  For instance, if the PM group defines work to be completed by Thursday of each week, and the start date is specified as November 1, 2015, the first occurrence of the PM generated by the IMMS PM generator would be due on November 5, 2015 (which is the first Thursday following the specified start date).
• End Date. In addition to the start date, you can put an end date on the PM schedule. You can do that by either specifying the number of occurrences to be performed or by setting a specific end date. The PM generator will not generate additional cases for PM occurrences when the specified number of occurrences is reached or when the calculated due date for the next occurrence falls beyond the specified end date.

Specifying Scope

As the name suggests, the "scope" section defines the work required to be performed. That is accomplished by

• Specifying the system elements, that the work is to be performed on, and
• Specifying the work form, which defines the work to be completed for each system element.

IMMS provides two options for specifying the system elements to be included in the scope of the PM group:

1. Specifying the system element type and location, so that system elements can be selected automatically. This option is practical when the system element selection is easily defined by location and type (e.g. camera). The main benefit of this option is that new system elements installed during the course of the project will be automatically added to the PM, as long as they meet the specified criteria (location and type).
2. Select individual system elements. This option is practical, when the system elements need to be selected based on a somewhat complex criteria (e.g. all items of a particular kind mounted at a particular height and requiring certain equipment to complete the work). The drawback of this option, however, is that IMMS will not automatically pick up new items that may be installed and need to be covered by the PM.

You cannot combine the two definition methods for the same PM group. However, either method will allow you to define a PM group, which includes system elements of different types and located at different locations. You will also be able to select different work forms representing the procedures to be performed on the different system elements included in the PM group.

The subsequent sections provide additional details on each of these options.

Specifying PM Scope by Selecting the System Element Location(s) and Type(s)

...

...

When a group is defined by selecting the system element location(s) and type(s), the PM generator will automatically add all active (not disabled) system elements whose type and location match the criteria to the created PM case. In other words, a system element will be added to the case if

• The system element record is not marked as "Deleted"; and
• The type of the system element is one of the types selected in the PM group scope; and
• The location of the system element is one of the locations selected in the PM group scope or is a sub-location of one of the locations selected in the PM group scope.

Use this PM group scope definition method to ensure that newly installed system elements are automatically added to the PM schedule. Since the PM generator relies on the type and location as the criteria when processing the groups, you will not need to add newly installed system elements to the respective PM groups manually.

Specifying PM Scope by Selecting Individual System Elements

Manually Selecting System Elements

When the PM group's scope cannot be defined simply by specifying the system element type(s) and location(s), you will need to select individual system elements to be included in the PM, as follows:

...

Select one or multiple system elements by clicking on "Select SE(s)..." and using the standard system element selector

...

Uploading a List of System Elements

If you already have the list of system elements to be included in the scope of a PM group you are configuring, you may save time by uploading a file with the list instead of selecting system elements one by one. The feature is available by clicking on the "Upload System Elements" button located next to the "Select SE(s)..." button.

To define the PM group scope, you need to prepare the file in a comma-separated values (CSV) format. The first line of the file should include column names and the rest of the lines should include the system elements to be added to the PM group scope, as discussed below:

...

Optional. Specify the location path, e.g. "/Area 1/Building 2/Room 123". If the location is specified, the IMMS will look for the system element with the name matching that specified in the Device_ID column and with the location matching the specified one.

Note, the location path is added to the path specified as the "Base Location" on the file upload form. For instance, if the Base Location is specified as "USA / VA" and the system element location included in the file is specified as "Sterling/LG4/300", IMMS will look for system elements located at "USA / VA / Sterling / LG4 / 300".

...

Optional. You can use the column to specify the work form to be used for the particular system element. The specified form name must match that stored in IMMS. 

Note, if there's only one work form defined for the particular type of system element, you do not need to specify the form name in the file, as it will be selected automatically.

...

Removing a PM Group From the Schedule

...