Versions Compared

Key

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

The PM Plan feature allows projects to specify and track compliance with high-level PM, inspection, and other recurring activity requirements for various system elements across the project and also to audit the schedule for compliance and coverage. In other words, PM Plan is not a schedule, but

  1. Allows the team to define the objectives the schedule must achieve
  2. Provides a way to monitor whether the program meets the objectives

Table of Contents

Important Concepts

PM Plan Entries

A PM Plan consists of entries (i.e., rules). At a very basic level, each entry of the PM Plan defines a criteria like "System elements of the types X or Y must be maintained/inspected every N days using a one of the scripts S1, S2, or S3 under the contract C". 

  • One or multiple system element types: specifying multiple system element types streamlines creation and maintenance plans by eliminating the need to define individual entries for each type.
  • Optional ability to specify the system and/or location to define specific PM Plan requirements (e.g. higher frequency inspections for outdoor locations)
  • Ability to select one or multiple work procedures (smart forms) that must be completed: Selecting multiple smart forms streamlines administration by allowing the administrator to create a single plan entry to cover multiple system element types that require different procedures (smart forms) but have otherwise similar requirements
  • At-a-glance compliance reporting:
    • Total number of system elements that fall under each PM Plan entry
    • Number of system elements with PMs planned and completed on schedule
    • Number of system elements with PMs planned, but late
    • Number of system elements not covered by PM schedule
    • Coverage Rate and On-Schedule Completion Rate metrics/KPIs

Viewing the PM Plan

Use the PM and Inspection Plan menu in the PM, Inspect, Test stack of the main menu. 

IMMS presents the PM&I Plan as a collection of the PM&I entries using the standard three-pane view with the left-most pane providing filtering options, the center occupied by the list of entries, and the right-most pane displaying the details of a selected PM&I entry. 

Filtering Options

The filtering options allow the user with sufficient privileges to narrow down the list of the PM&I plan entries by contract, system element type(s), location, and frequency. 

PM&I Plan Entry List as a Compliance Dashboard

In addition to listing the PM&I Plan entries, the view provides immediate feedback to the user and serves as a real-time dashboard for monitoring compliance of the program with the PM&I objectives. 

Specifically, each entry of the PM&I plan is displayed with the following information:

  • Contract - the contract, which the entry applies to. Note that multiple contracts may be defined within the IMMS instance, and they will have different PM&I objectives reflected by different PM&I plan entries. 
  • Name - the user-friendly name assigned to the rule by the administrator (creator of the rule). Since the rule may contain a variety of criteria, the purpose of the name is to provide a concise descriptor to it, e.g. "Generator - Monthly PM" or something of that nature.
  • System Elements - displays the number of deployed system elements that match the rule criteria. Note that the number of system elements is subject to the user permissions, and IMMS will only count the system elements the user has access to. Therefore, it is important that the users monitoring and managing the PM&I plan have properly assigned permissions. 
  • Interval - specifies the maximum number of days between consecutive PMs/inspections performed on a given system element. For instance, the value 365 means each system element matching the rule must be maintained/inspected every 365 days (1 year).
  • # Planned on Schedule - the number of system elements that match the plan entry criteria and have the next cycle of PM due in the future
  • # Planned Late - is an exception counter, which shows the number of system elements that match the plan entry criteria and have the next cycle of PM scheduled, but overdue
  • # Not Planned - is an exception counter, which shows the number of system elements that match the plan entry criteria but have no PM scheduled 
  • % Coverage - is a compliance metric, which shows the share of system elements matching the entry criteria and have their PMs scheduled
  • % On Schedule - is a compliance metric, which shows the share of system elements matching the entry criteria that have them PMs scheduled and completed within the intervals specified by the entry

The system element counters shown in the PM&I plan view provide the user an easy way to navigate (drill-down) to the corresponding lists of system elements. 

PM&I Plan Entry Details

When the user selects an entry in the list, IMM displays its details in the right-most panel. The structure of the details follows that of the entry definition. 

Defining PM&I Plan Entries

The PM&I Plan view provides standard controls to create new entries and to modify existing ones:

  • A user with sufficient privileges can create additional PM&I entries from scratch using the New button in the PM&I Plan view. 
  • As a time-saving feature, the user may also select and existing entry and use the Clone function to start a new entry by initializing its definitions using the values from the selected existing one.  
  • A user with sufficient privileges can modify a previously defined entry at any time by selecting it in the list and choosing the Edit function

Creating and modifying a PM&I plan entry follows the same structure, as outlined below. 

  • The general section section of the entry includes the following:
    • Contract - each PM&I Plan entry must be associated with a single contract. 
    • Name - the user-friendly name assigned to the rule by the administrator (creator of the rule). Since the rule may contain a variety of criteria, the purpose of the name is to provide a concise descriptor to it, e.g. "Generator - Monthly PM" or something of that nature.
    • Interval - specifies the maximum number of days between consecutive PMs/inspections performed on a given system element. For instance, the value 365 means each system element matching the rule must be maintained/inspected every 365 days (1 year).
  • The core of the PM&I entry is the system element selection criteria, which consists of one or a combination of the following:
    • System Element Types - the rule must apply to one or multiple system element types. When IMMS uses the rule to monitor compliance, it will count the system elements whose types are included in the list. For example, if the infrastructure includes multiple types of diesel generators, including all the types in the rule will allow the single rule to define and monitor the common PM&I requirements
    • System Element System(s) - allows the administrator to restrict the rule to one or multiple branches of the system hierarchy. 
    • Locations - allows the administrator to restrict the rule to one or multiple branches of the location hierarchy. For example, the administrator may define different rules with different location criteria to specify PM&I requirements for the same kinds of system elements deployed in harsh environments vs the ones deployed in normal conditions.
    • Work Forms - allows the administrator to specify what work procedures (forms) must be used for the PM&I activities. Listing multiple work forms allows the administrator to reflect the fact that the different types of system elements covered by the entry may require different procedures.
  • The user may include notes and comments. The text field is useful to include references to contract and/or OEM requirements or other similar information.

Deleting (Purging) PM Plan Entries

As PM&I Plan entries have no defined workflow or performance history, they may be removed from the IMMS configuration when not needed. 

...

and Inspection Plans offer a high-level planning capability that is focused on proactive compliance management for large-scale maintenance and inspection programs. 

This article provides information and guidance on these topics related to PM and Inspection Plans.

Table of Contents

PM and Inspection Plan Grid View

PM and Inspection Plans can be accessed and managed (e.g., created, edited) from the PM and Inspection Plan grid view. To access this view:

  1. Access the Main Menu from the top-level navigation bar.
  2. Select PM and Inspection Plan from the PM, Test, Inspect stack.

Filters

The PM and Inspection Plan grid view allows Users to filter plan entries by: Contract(s), Cycle/Interval, System Element Types (i.e., plans that match at least one selected Type), and Locations (i.e., Plans that match at least one selected Location).

Data Columns

The PM and Inspection Plan grid view displays basic details about each plan, including the number of associated System Elements. The view also displays coverage and on-time performance details based on the schedule and completion of the PM Tasks (i.e., Work Forms) associated with each plan. The following table provides details on the most useful data columns.

Column

Description

ContractContract associated with the PM Plan
NameName of the PM and Inspection Plan
# System ElementsNumber of System Elements associated with the Contract and matching the scope criteria defined for the PM and Inspection Plan
Interval (Days)Length of the interval as defined in the PM and Inspection Plan, which is the maximum days between consecutive PMs
# Planned On Schedule

Number of System Elements that meet the PM and Inspection Plan scope and one of the following criteria:

  • The number of days between the completion of the most recent PM/Inspection using a Work Form defined in the PM and Inspection Plan and the Due Date of the next scheduled PM/Inspection using a Work Form defined in the PM and Inspection Plan does not exceed the defined Interval; AND the Due Date of that next scheduled PM/Inspection is in the future.

OR

  • The System Element has no completed PM/Inspection using a Work Form defined in the PM and Inspection Plan; AND the Due Date of the next scheduled PM/Inspect using a Work Form defined in the PM and Inspection Plan is in the future; AND the difference between the Due Date of that next scheduled PM/Inspection and the System Element creation date is less than defined Interval.
# Planned Late

The number of System Elements that meet the PM and Inspection Plan scope and one of the following criteria:

  • Number of days between the last complete PM or Inspection using a Work Form defined in the PM and Inspection Plan and the next scheduled PM/Inspection using a Work Form defined in the PM and Inspection Plan does not exceed the defined  Interval; AND the Due Date of that next scheduled PM/Inspection is in the past.

OR

  • The number of days between completion of the most recent PM/Inspection using a Work Form defined in the PM and Inspection Plan and the next scheduled PM/Inspection using a Work Form defined in the PM and Inspection Plan exceeds the defined Interval

OR

  • The System Element has no completed PM/Inspection using a Work Form defined in the PM and Inspection Plan; AND the Due Date of the next scheduled PM/Inspection using a Work Form defined in the PM and Inspection Plan is in the future; AND the difference between the Due Date of that next scheduled PM/Inspection and the latest of i) System Element creation date and II) Contract Start Date is greater than defined Interval.
# Not Planned

Number of System Elements that meet the PM and Inspection Plan scope AND for which there is no scheduled (i.e., future) PM/Inspection using a Work Form defined in the PM and Inspection Plan

% On Schedule= (# Planned on Schedule) / (# System Elements), expressed as %
% Coverage= 1 - (# Not Planned) / (# System Elements), expressed as %

Creating a PM and Inspection Plan

To create a PM and Inspection Plan for a defined group of System Elements under a specified Contract:

  1. Access the Main Menu from the top-level navigation bar.
  2. Select PM and Inspection Plan from the PM, Test, Inspect stack.
  3. From the grid commands at the top of the PM and Inspection Plan view, select New. This will open the New PM Plan form.
  4. Populate all required form fields:
    1. Contract - Only one Contract can be selected per PM and Inspection Plan.
    2. Name - Enter a concise Name that clearly communicates the nature of the associated PM/Inspection (e.g., devices, recurrence, etc.)
    3. PM Interval, Days - Enter the maximum allowed days between PM/Inspections
    4. System Element Types - Select one or more System Element Types for which the PM/Inspection applies
    5. Work Forms - Select one or more Work Forms that define the work to be performed with the PM/Inspection; Note:
      1. Work Form must be associated with the selected Contract
      2. Work Form(s) must be associated with selected System Element Type(s)
      3. If the desired Work Form does not appear for selection, open the Work Form Details to check these associations.
  5. Populate optional fields (i.e., Systems, Locations) if desired.
    1. These fields can be used to narrow the scope of the PM and Inspection Plan. This may be necessary if a different Work Form applies to different Systems or Locations.
  6. Click OK when complete

Gliffy Diagram
displayNameNew PM Plan Annotated
nameNew PM Plan Annotated
pagePin2


Editing a PM and Inspection Plan

To edit an existing PM and Inspection Plan:

  1. Access the Main Menu from the top-level navigation bar.
  2. Select PM and Inspection Plan from the PM, Test, Inspect stack.
  3. Apply filters along left side of the PM and Inspection Plan view as necessary to identify the desired PM and Inspection Plan.
  4. Select the desired PM and Inspection Plan from the grid view.  
  5. From the grid commands at the top of the view, select Edit. This will open the Edit PM Plan form.
  6. Change form fields values as necessary to amend PM and Inspection Plan scope.
  7. Click OK when complete

Deleting a PM and Inspection Plan

As PM and Inspection Plans have no defined workflow or performance history, they can be removed from the InfraLink configuration when they are no longer needed. Users with sufficient Permissions can:

  1. Access the Main Menu from the top-level navigation bar.
  2. Select PM and Inspection Plan from the PM, Test, Inspect stack.
  3. Apply filters along left side of the PM and Inspection Plan view as necessary to identify the desired PM and Inspection Plan(s).
  4. Select the desired PM and Inspection Plan(s) from the grid view.  
  5. From the grid commands at the top of the view, select Purge.
  6. InfraLink will present the following warning message: "Are you sure you want to permanently purge the 1 selected entries? Note: this will also permanently purge all related entities and history. Click YES to continue."
  7. Select Yes.

Note: The Purge action permanently removes the selected entries. A deleted copy is not maintained in the database.

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:

  • Accessing/Viewing PM and Inspection Plans: PM Plan→General→Read  and   PM Plan→General→Create, Delete or Update
  • Creating PM and Inspection Plans: PM Plan→General→Read  and  PM Plan→General→Create
  • Editing PM and Inspection Plans: PM Plan→General→Read  and  PM Plan→General→Update
  • Deleting PM and Inspection Plans: PM Plan→General→Read  and  PM Plan→General→Delete