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 it
- Allows allows the team to define the objectives the schedule must achieve, and
- Provides provides a way to monitor whether the program meets the objectives.
| Table of Contents |
|---|
Important Concepts
...
Use the PM and Inspection Plan menu in the PM, Inspect, Test stack of the main menu.
IMMS InfraLink 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.
...
- Contract - the contract, which the entry applies to. Note that multiple contracts may be defined within the IMMS InfraLink 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 InfraLink 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 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 InfraLink 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.
...
As PM&I Plan entries have no defined workflow or performance history, they may be removed from the IMMS InfraLink 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 InfraLink will permanently remove the entries (as opposed to maintaining them in the database, but marking them as deleted).