RCM Release 3.13D

August 2021

In addition to the overall stabilizations and performance improvements, version 3.13D contains improvements of the MEC Optimization board, Added Global RSL templates, enhancements in Change and Deferral module etc.

MEC Optimization Board

Some improvements were done to the usability of the MEC Optimization Board, among them a better representation of the data on the MEC Overview graphs and better handling of the TA Costs.

1. MEC optimization board Overview

1.1 MEI Threshold labels

MEI Threshold labels were added to the Average maintenance cost per year vs. MEI (cumulative) and the MEI vs. maintenance cost per year per Failure mode graphs. Now the graph label indicates:

• Site Default MEI Threshold (MEC = 1)
• Unit default MEI Threshold (if set) for all units to which currently loaded FLOC/Equipment belongs to.

Average maintenance cost per year vs. MEI (cumulative) graph. 

MEI vs. maintenance cost per year per Failure mode graph. 

1.2 Turnaround tasks costs

On the Long-term maintenance cost profile graph The TA tasks costs now include:

• Tasks having Frequency set to TA
• Tasks marked as TA Candidate

For both categories of tasks, the Task Interval is now taken into account and the costs are shown only on bars having the corresponding interval.

Also, for both categories of tasks, the Task Interval is checked against the TA interval set on UNIT level (on the Unit to which the System belongs to) and potential Run Limiters are counted and show in a label when hoovering each TA cost bar.

Long-term maintenance cost profile graph. 

2. Turnaround tasks columns

The Turnaround tasks representation on the Optimization board has been updated correspondently: now there is no just one TA column but a number of them:

• There is a TA-n column per each interval greater than 1 Year
• The intervals lower than 1 year are rounded up in categories T/A-0, T/A-0.1, T/A-0.2, T/A-0.3 and T/A-0.5

T/A-n columns on the MEC Optimization Board. 

3. Merge tasks to destination task using Drag and drop

IMSD-26701

Merging tasks functionality was upgraded so the user now has more possibilities and options when merging tasks:

• Now the merge can be done using the drag and drop functionality: you can pick a single task or more of them by holding the CTRL (control) KEY, and then you can drag them to a task to which you like to merge to.
• The dragging will result in a “SNAP” mark on the master when you correctly position the dragged task over it, to prevent you from just moving the tasks between frequencies.
• All the other validations for merging tasks are still valid (i.e., you cannot merge tasks belonging to different equipment, etc.).

Merging tasks using Drag and Drop: dragged task and master task (dashed blue line). 

4. System / Unit Run limiters

Now the Task Intervals for TA and TA Candidate tasks are checked against the TA interval set on UNIT level (on the Unit to which the System belongs to) and potential Run Limiters are marked on the task cards with a red label text “Run Limiter”.

Run Limiter marks on task cards.

The Run Limiter tasks can be filtered out with a filter present on the System optimization levels.

Run Limiter filter.

If a Turnaround interval is changed in Settings / Top level tree new Run limiters will be calculated and flags on the cards will be updated.

Turnaround interval set on UNIT level. 

5. Tasks grouping – Task main screen

Task Grouping functionality was added to Task main screen as a part of a new toolbar section - Bulk Actions (together with the already existing Task Requirements functionality).

Add Task to Task Group.

Similar to Task Requirements, the user can add one or multiple task groups at the same time, by using the + / - action button.

Add Task to Task Group dialog Box.

All Task Groups are shown in the grid as a CSV value in Task Group column.

Maintenance Libraries

1. Global RSL templates upload

IMSFB-18233

Several Global RSL templates was made available to the community.

Published Global RSL templates:

2. RSL Strategies based on Specs

2.1 Preselection of Spec values

Now when setting up the RSL Strategies only the necessary Spec for building up the decision tree logic can be selected, thus avoiding dealing with too many Spec values, and having a clearer Tasks / RSL strategies matrix shown on screen.

2.2 Task Uniqueness in RSL Strategies

Task uniqueness is now aligned with the Task uniqueness used in MEC optimization strategies and it is based on:

• Task name
• Task description

Change and Deferral

IMSFB-19744

The Deferrals functionality is enhanced and now the Deferral requests contains additional fields to follow better the Deferral process. Added fields are:

• Reason for Deferral
• Requirements by Authority
• Deferral Extension
• Unmitigated risk defined by PACE matrix

Reason for Deferral filed. 

1. Link to Schedule

Deferral requests are now based on schedules: when creating the request, the user can pick multiple Schedules from IMS modules depending on the roles (RCM, PEI … ).

Reason for Deferral – link to schedule.

For each Schedule, the user can enter:

• Schedule ID: via a pop-up screen
• Workorder number
• Maintenance Plan number
• Notification

Each one of this method will result in a Schedule to which the Request will be related.

Select Schedule pop-up. 

Selected Schedule data. 

2. Request Priority based on Workorder Basic Finish Date

The Request Priority and Due date values are now based on the related Workorder.

• The Request Due Date is automatically prefilled with the Workorder Basic Finish Date
• The Request Priority category is then automatically set to the timeframe calculated from the difference between the Due Date and the Submittal Date.

3. Repeated deferral request – Extension of existing

If a Deferral request is created for Schedules that were already deferred at least once, the count is automatically set per each schedule, and a “master” Extension number is set per Request as a highest value of all Schedules extension.

Repeated deferral request.

All the functionality to define another set of approvers if the Deferral is a repeated one using the Auto Approval functionality is adjusted to this new definition of repetition.

4. CHD related SPECs for included FLOCs/Equipment

A new flag has been introduced to mark certain spec relevant to the Change and Deferral process. Thus, those specs can be loaded and displayed when linking FLOC / Equipment to the request.

Change and Deferral related specs. 

5. PACE risk matrix for unmitigated Risk Score

Sections for defining the Risk Analysis and Mitigation are added.

Unmitigated Risk Score can be set using the PACE (People, Assets, Community, Environment) risk matrix.

Risk Analysis and Mitigation sections.

By clicking on any category, a PACE risk matrix is displayed in which a combination of Consequence and Likelihood can be set.

Risk Analysis and Mitigation sections.

Additional fields available to the user are:

• Comments on Risk (rich text)
• Mitigations in Place – Operations (check box)
• Comments on Mitigation (rich text)

6. Request Priority based on the Due date

The Due date field is added to the Deferral Request. The Due date is based on the Workorder Basic Finish Date but can be overridden or set manually by the user.

The due date then impacts the Request Priority: based on the number of days between the due date and the request submittal date the right Priority category is chosen.

Request Priority based on the Due Date. 

7. Technical evaluation section

The Technical evaluation section in added for evaluating the equipment for which the request is issued. The section is built from generic fields:

• Summary of Past Inspections (rich text)
• Technical Evaluation Summary (rich text)

A number of Equipment Groups additional details are covered by the dynamic forms:

• PIPE
• TANK
• RELIEF VALVE

Dynamic form for PIPE Equipment Group. 

Dynamic form for TANK Equipment Group. 

Dynamic form for RELIEF VALVE Equipment Group. 

8. Initiate Request from Schedule details screen

The request connected to a Schedule can be now seen in the Deferral Request section on the Schedule details screen.

From the same section a new Deferral request can be issued: all the Schedule related values will be prefilled.

Dynamic form for PIPE Equipment Group. 

Various usability enhancements

1. Export and Import of Specs

IMSFB-20209

Export and import of SPECs has been added to RCM module so the SPECs can be set on FLOC and on Equipment level. The SPEC import is limited only to the Location Types / Equipment Groups owned by the RCM module.

There is no default import template because it depends on the Location Types, so before the import the user should first create the template by choosing the desired FLOC / Equipment and running the Export functionality.

Export Specs button.

The user can set multiple FLOC / Equipment to be updated, however, if they belong to different Location Types then the export will generate a ZIP file containing all the different templates.

Spec import template for MOTOR-FLOC Location Type.

Once filled, the import template can be loaded using the new FLOC/Equipment Specs option in the standard import functionality.

Spec import. 

Spec import report. 

Imported Specs visible in the FLOC details screen.

2. Assigning Labels using import functionality

IMSFB-20405

A functionality for assigning Labels using the import mechanism was added.

TagLabel Import Option.

Now it is possible to assign Labels in bulk to:

• FLOCs
• Equipment
• RCM Functional Systems
• RCM Schedules
• Tasks
• ECH
• Change and Deferral requests

TagLabel Import Template.

The user should select the object type from the first column, enter the desired ObjectID (name) and select from a list of available labels.

3. Smarter setting of the Perform RCM flag

IMSFB-19742

Two Application settings were created, to set the default Perform RCM value when creating Floc or Equipment, so it each site can customize this flag which define the total amount of FLOC / Equipment to be analyzed and thus impact the KPI data.

Application Setting – Perform RCM.

Moreover, if a flag is set to FALSE, the tool will automatically set it to TRUE when adding a FLOC or Equipment to a System and will set the corresponding Equipment or FLOC to Perform RCM = FALSE because of the rule that an analysis can be performed or on FLOC or on Equipment but not on both at the same time.

4. Labelling functionality (Tags -> Analysis -> Tasks)

IMSFB-19647

The labelling functionality has been extended. Now the user can create a label hierarchy by adding the same label to the FLOC / Equipment – Analysis – Tasks at the same time choosing any of those three levels as a starting point. On each level, the other two are shown as an option.

In this case it is easier to track that information when dealing with analyses and tasks on various screens, reports, etc.

Adding labels on Tags / Analyses / Tasks.

5. Analysis approval status

IMSFB-20229

Column Approved is added to the RCM Analysis main grid and filter. Now the analyses can be filtered out based on if they are:

• NA – Not Approved
• AA – Automatically Approved (by any of the existing logic: MEI Threshold, Mandatory Tasks, Legal Requirements)
• MA – Manually Approved

Approved filter. 

Approved column. 

6. ECS – searching the applicable strategy

IMSFB-19760

A search box is added to the ECS assignment pop-up window in order to facilitate the search for an ECS strategy to assign.

ECS Strategy Search functionality. 

7. Settings – Failure Mode per Equipment Type setup

IMSFB-19780

Setting a Failure mode compatibility to multiple Equipment Groups has been improved by adding the possibility to pick multiple Failure modes at the same time in the Settings / Maintenance / RCM Specific Data screen.

Failure Mode per Equipment Type setup. 

Resolved issues