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
- Allows the team to define the objectives the schedule must achieve
- 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.
The user with sufficient privileges may select one or multiple entries in the plan and use the Purge function to permanently delete them. Note that the "purge" action reflects the fact that IMMS will permanently remove the entries (as opposed to maintaining them in the database, but marking them as deleted).