PEI Release 3.13B

December 2020

Version 3.13B brings updates to existing features of IMS. Its main target is to stabilize and improve performance.

Cost KPI for MEC

IMSFB-15962

1. Configuring MEC Costs per module

The MEC costs on schedules can be mandatory or optional, depending on the site’s configuration. By default, the IMS modules are configured as follows:

• MEC Costs mandatory: RCM
• MEC Costs optional: PEI, PLSS

This can be configured by defining optional modules in the application settings.

In addition, specific schedule types, on which MEC Costs are used, can also be listed. By default, IMS is configured to show MEC costs on inspection, corrosion, CAIR and preventive schedules.

Figure 1:

Application setting for configuring MEC costs. 

2. Visibility of MEC Costs for every user

If the MEC costs are set as mandatory, the schedules in that module will show the costs. However, if the MEC costs are set as optional for the module, by default the costs will not be shown on the schedules.

Nevertheless, in a module for which MEC Costs are optional, a user can still turn on the visibility of MEC Costs for himself. This can be done in the user settings (see Figure 2). This setting will not be available in modules for which the MEC Costs are set to be mandatory.

Figure 2: User settings for turning on MEC Costs in optional modules

The visibility of MEC Costs is summarized in Table 1. The visibility depends on the application setting (Mandatory vs Optional) and, in the Optional case, it also depends on the user setting (Turned on vs Turned off).

Table 1: Visibility of the MEC Costs.

3. MEC Costs features

When the MEC Costs are visible, the following features are available:

3.1 Defining the cost of a schedule

In modules, with the MEC Cost set as optional, the costs are shown in a subtle button.

Figure 3: Showing MEC Costs in optional modules

When you click the cost button, a cost breakdown will be shown in an expanded view (see the figure below). This view is the default view for modules with the MEC Cost set to mandatory.

For a schedule, the costs can be defined as a complex cost, consisting out of labor costs, material costs and misc. costs. However, the cost can also be defined as a simple total cost. In this case the other cost categories will not be editable.

Figure 4: Costs breakdown and defining cost on a schedule

Note: The approval status of a schedule will not be impacted when the costs are being defined, i.e. a schedule that is in final approval state will not go back to draft when the costs are entered.

3.2 Defining default schedule costs

To make it easier to define the costs, default costs can be defined for schedules, depending on their properties. Default costs can be defined with following properties:

• Location default,
• Equipment group,
• Equipment/SAP type,
• Schedule type,
• Schedule driver,
• TA candidate status, and
• Plan codes.

This default cost configuration can be configured in:

Settings à Top level à Select location à MEC Cost

Figure 5: Example of default cost rules

 The following logic is used to determine the default costs for a specific schedule:

• Use the location default checkbox to define a cost specific only for this part of the hierarchy. This is a “safety net” for when no other criteria are met.
• Define default cost by using equipment group, SAP type, schedule type, schedule driver, TA Candidate status and plan codes.
• In cases where a schedule meets multiple criteria, IMS PEI will suggest the higher cost as a default cost.
• In cases where a schedule meets multiple criteria that differs only in terms of plan codes, IMS PEI will sum the values and suggest their sum as a cost.

To help make this process easier, there is now also an import for the default cost configuration, and an export button is visible on the MEC Cost grid.

3.3 Using default cost on a schedule

When a schedule is being created, IMS PEI will look up the default cost for this schedule. This cost will be captured and saved by default. The user can remove the default cost and enter a more accurate cost.

When plan codes are used, the scope needs to be final approved before IMS PEI captures the SUM of the costs, which is defined for each plan code.

To remove the default cost, click on a checkbox. This will enable the fields so that different costs can be entered.

Figure 6: Example of a schedule with the default cost

3.4 Defining Schedule costs via the import

To define the costs faster, a dedicated export for import was made: Check the desired schedules in the grid and click the export button. Two new options for exporting costs will then be shown. By selecting one of these the schedule ID and relevant information, with regards to determining the costs, will be exported. The exported template can then be filled in and imported back into IMS PEI.

Figure 7: Export for import and import template for schedule costs

 3.5 Determining annual cost

A schedule’s total cost is annualized if the schedule is recurring. If a schedule is not recurring, IMS PEI will assume that the schedule represents a one-time job, and the annual cost will be the same as the total cost.

The annual cost is defined by the following formula:

The annual cost is only for schedules with defined intervals. A schedule also needs to be approved before the annual cost is calculated (if the interval is added afterwards).

Figure 8: Example of a schedule with an annual cost

 3.6 Determining if a cost is TA or Non-TA

Depending on the schedule characteristics, a cost can also be classified as a turnaround or non-turnaround cost.

This is decided based on two schedule properties:

• TA candidate flag
• Connection to a planned event

If one of those conditions are met, the schedule cost will be considered as a TA cost. Otherwise, the cost will be considered as non-TA cost. This is also indicated by the heading of the schedule cost.

Figure 9: Example of a schedule with TA cost 

3.7 Showing costs in the schedule grid

Total costs and annual costs can be shown in the schedule main grid. These options are by default not visible, but a user can turn them on in the grid.

Figure 10: Showing total and annual cost in schedule grid

 3.8 Filtering on schedule cost

On the Schedule main grid, two additional filters are also available.

The first filter is a range filter for the total schedule cost.

The second filter can be used to find schedules with no cost defined, schedules with default cost, and schedules with defined cost.

Figure 11: Schedule cost filters

  4. MEC Cost index

Once schedule costs are defined, it is time to calculate the MEC cost index. The MEC Cost index is calculated as follows:

The MEC Cost index is calculated for a specific year and for a specific location (site, plant or unit).

The annual costs are based on:

• Annualized costs for the schedule
• Annual POC on the tasks (RCM)

The benchmark factor is determined by the user, for a specific year.

The cost for a specific year is determined based on the schedule’s next inspection date (due date). If a schedule is overdue, the year is assumed to be the current year.

4.1 Annual POC on tasks

Annual costs of schedules are determined as explained previously (see 1.3.5). To these costs, IMS PEI then adds an annual Price of Conformance (POC), which can be found on tasks in IMS RCM.

The cost is classified as a TA cost if the task has a “TA Candidate” flag. The task cost is also ignored if a task has a “Merged to Task” flag.

 Figure 12: Annual POC on tasks

 4.2 Calculating MEC Cost index for a specific year

To calculate the MEC cost index, got to:

Settings à Top level à Select location à MEC Cost

The MEC Cost tab is used to define a group, year and a benchmark index for that year. For example, multiple locations can be reported as one – select in “Cost Configuration” group under which current location should be reporting as.

Figure 13: MEC Group definition

 When ready, click the calculate button in the upper right corner. IMS will then summarize the costs (from schedules and tasks), apply the default costs (if the rules changed), and calculate the MEC Cost index based on the summarised costs.

The calculation takes in consideration all active equipment, except the ones in status “IN CONSTRUCTION”, and active and approved schedules (schedules in final approval state of type Inspection and Corrosion).

Figure 14: Example of MEC Cost index calculation

 Click on the + button in the grid, to add a “Year” and a “Benchmark Factor”. The “Index Type” indicates the nature of the benchmark factor but does not play a role in the MEC Cost index calculation.

Figure 15: Creating a new yearly record

 

Table 2: Cost Configuration example

4.3 Overview of Benchmarks

To see all reporting groups and available years, click on “OPCO” in the settings. Settings à Toplevel à OPCO

There you can see the reporting “MEC Groups” and all Cost configurations.

Figure 16: Overview in OPCO

5. The MEC Cost dashboard

A MEC Cost dashboard is available to help track your costs. The dashboard shows: Schedules with costs; Number of equipment which have at least one schedule with a cost; and Number of schedules without defined costs. To get a deeper insight in the costs, you can also drill down to see the costs per site, equipment group and year.

The dashboard also shows an overview of all MEC Cost indexes, on all locations for which a year and a benchmark are defined.

Figure 17: The MEC Cost dashboard

Other features

1. Global dashboard export enhancement

IMSFB-17061

An additional row has been added to the Global Dashboard export. The new row shows sparklines of the monthly data.

Figure 18: Global Dashboard - Export in excel

 

The source data for the sparklines are available in a separate excel sheet, named “Sparkline”.

Figure 19: Global Dashboard - Sparkline sheet

  2. Generic Spec import

IMSFB-11957

In the past the “Spec import” was only available in the “Export Specs” functionality on the FLOC and Equipment level. Now, there is a new “Hierarchy specs” import functionality, which can be used to import a single Spec to multiple entities.

This new import functionality can import Specs on the following levels:

• FLOC,
• Equipment,
• Component,
• Circuit, and
• CML.

Figure 20: Hierarchy spec import and template

 It is important to fill in the minimum necessary hierarchy information, for the desired destination, into the import template. For example, if a user wants to import Specs on the Component level, it is important to fill in both the Equipment name and the Component name. When a user wants to import Specs to the CML level, he must provide Sub circuit, Circuit name (and not the Component name) together with the Equipment name. Thus, the Component name and the Circuit name are not required simultaneously, i.e.in the same row.

3. New key material data on the RBI grid

IMSFB-17185

With the global material list clean-up, we eliminated "PWHT" from the base material list. Instead "PWHT" was added to the equipment specifications. Key material data was also added to the RBI main screen grid and to the Component/RBI section of the Corrosion Loop (see Figure 21 and Figure 23Figure 22). This will help to better visualize the heat treatment and special data, such as weld overlay, lining, and cladding.

Figure 21: Components/RBI grid on the Corrosion Loop

 

Figure 22: RBI Main search grid

 

4. The new logic for the “In construction” Equipment status

IMSFB-14984 IMSFB-10313

The logic for the Equipment status: “In construction” has changed. Now, when the Equipment status: "In construction" is selected, the Equipment will stay active. This change will help sites where, for a large project, the engineering contractor sometimes reserves equipment for years upfront. In these cases, the equipment comes to IMS while remaining in the "In construction" state.

5. The new query for the SAP Maintenance plan Overhaul

A new “SAP Maintenance plan Overhaul” query checks SAP for recurring PSV overhaul schedules and checks in IMS if the overhaul schedules exist. It then flags the missing IMS overhauls. This query is available in the BLP SAP Dashboard.

Figure 23: BLP SAP Dashboard - Maintenance plan Overhaul

6. Accept deviation on the BLP SAP Dashboard

IMSFB-17056

The “Accept Deviation” functionality, which was already available for the SAP Dashboard, is now also available for the BLP SAP Dashboard. All the queries, in the “Misaligned” section of the BLP SAP Dashboard, now have the possibility to “Accept Deviation”. Once the deviation is accepted, it will be visible in the “Accepted Deviations” section of the Dashboard.

Figure 24: BLP SAP Dashboard - ACCEPTED DEVIATIONS

AIR Enhancements

We have made some enhancements with regards to the AIR annotations.

1. ECH Code Mapping

As shown in Figure 25, there are now a list of ECH codes to choose from. The selected ECH code will be sent through to AIR.

Figure 25: You can now choose from a list of ECH codes. 

2. Rotating Option

To better cover the affected area, you can now rotate the selector box to any desired angle. This selection will be sent through to AIR.

To do so:

• Click on the pointer tool and select the rotation icon (see Figure 26);
• Select one of the selector box’s sides (not a corner); and
• Rotate the selector box by moving your mouse in the desired direction.

Figure 26: Click the rotation icon to rotate the selection box.

3. Creating Polygons

You can now add corners to a selector box and also drag the corners to form a shape that better covers the affected area. This selection will be sent through to AIR.

Figure 27: Use the polygon tool to add and move the corners of a selector box.

To make a selector box’s corners editable:

• Use the pointer tool, to select your selector box;
• Click on the polygon tool icon (see Figure 27); and
• Click the smaller polygon icon (that appears), to toggle from rectangle to polygon.

To add a corner:

• Click the + icon; and
• Click on the desired location to add a corner.

To move a corner:

• Select the desired corners; and
• Drag to the desired location.

To remove a corner:

• Click the - icon; and
• Click on the desired corner to remove it.

To change the polygon back to a rectangle:

• First remove extra corners, so that only four remains; and
• Click the smaller polygon icon again, to toggle back from polygon to rectangle.

Resolved issues