ONE IMS Release 2022.1

April 2022

Version 2022.1 brings the following updates related to ONE IMS, i.e., to all modules: HSSE Criticality, Dynamic Forms, IOWs, MEC Cost, and User (Role) management. New to IMS is the Systems which can be used to group FLOCs and Equipment. 

IMS 2022 Q1 Realization

One IMS:

HSSE Criticality

IMSFB-28419

The HSSE Critical Equipment and Activity SAP Alignment Project will change how Shell manages equipment and Tasks/Schedules/Notifications. The deployment of the changes will be per site.

To enable the new HSSE functionality, it must first be enabled in the Application Settings.

Figure 1: The HSSE functionality is enabled n the Application Settings.The Critical Codes, as well as the old HEMP field, has been removed from the Equipment Details section. These Critical Codes and HEMP data have been copied into the Specs section and will be read only (legacy).

Figure 2: Critical Code and Hemp will no longer be shown in the Equipment Details screen.

Figure 3: The Legacy HEMP and Critical Codes shown in the Specs section.A new HSSE Criticality field has been added to the Equipment and FLOC Details screens, as well as to the main grids. To show in the main grids, this column must be selected in the grid settings. You can already select the HSSE Criticality when the FLOC or Equipment is being created.Figure 4: The new HSSE Critical field.The FLOC and Equipment main screens have also been enhanced with the additional “HSSE Criticality” filter.

Users can select the following values for the HSSE Criticality:

• A – HSSE Critical
• B – Production Critical
• C – Non-Critical
• D – Regulatory (Legal)
• -

Figure 5: The HSSE Criticality filter. 

Introducing Systems

IMSFB-29710

IMSFB-17786

IMS now supports Systems in PEI. This enables the organization of FLOCs and Equipment in the best possible way to manage it. A new “Systems List” is now available as one of the Main Menus. Creation of Systems is available for ADMIN Roles such as INSP Admin.

Figure 6: The Systems Main Menu in PEI. 

Creating a System

A new System can be created by defining its location (site, plant, or a unit), name, description, and a discipline. For PEI, the discipline is preselected as “Pressure Equipment Inspector”. For now, IMS supports only “Operational Systems” as a type, while “Functional Systems” is still planned.Figure 7: Creating a system in PEI.

Once a System is created, a narrative can be added for more information, or a drawing can also be added.

Figure 8: Adding a drawing to the System. 

Mapping FLOCs to Systems

Most importantly is adding FLOCs, which should be grouped together, to the System. FLOCs can be added in two ways:

• by mapping FLOC to a drawing, or
• by adding FLOC manually to a System.

To add a FLOC to a System via drawing, click on the drawing and then on the “PEFS” button. This opens a list of FLOCs mapped to a drawing, which will usually still be empty. To map a FLOC, right-click on the drawing. This will show the option to map a new FLOC to the drawing. Select the FLOC and map it to the exact location on a drawing.

Figure 9: Mapping a FLOC to a drawing.One FLOC can be mapped to a drawing multiple times, if needed. Just select the FLOC on the right side and right-click on the drawing. You can then map the selected part of the drawing to the existing FLOC. To remove a FLOC, just right-click on the drawing and click “Remove”. Removing the FLOC mapping from a drawing will not remove FLOC from the System.

Figure 10: Mapping an existing FLOC to the drawing multiple times.Alternatively, FLOCs can be added to a System in bulk. Either via the importer with a template or via a mapping wizard. In the Systems Details Page, in the FLOC List section, click the “+” button: This opens a wizard to help you add or remove FLOCs to/from the System in bulk. The left side will show a list of unmapped FLOCs for this System and on the right the mapped FLOCs will show. Select the unmapped FLOCs that you want to add and click the arrow to add them, or visa verso to remove them.

Figure 11: Adding and removing FLOCs from a System in bulk.Systems can also be created and the FLOCs map in bulk via importer. The importer templates (“Systems” and “Mapping FLOC to System”) are available in: Data Transfer \ Import Data \ Other.

Figure 12: Import templates for creating Systems and mapping FLOCs. 

Filtering per System

Once a System has assigned FLOCs, the System is shown as an (alternative) hierarchy option in the Main screen grid. Click on the hierarchy icon and select the System. Then click “Show”. The grid is filtered per System, and it sticks across other menus, which has assigned FLOCs. The main grids that support this kind of System filtering are:

• FLOC
• Equipment
• RBI
• Components
• Circuits
• CML
• Schedules
• Condition Histories
  Figure 13: Selecting System in the hierarchy.

Showing Systems on FLOC and Equipment Detail Pages

For FLOCs and Equipment, the Systems to which they are assignment are shown under “Hierarchy and Systems”, in the Details section. When a System name hyperlink is clicked the System Details Page will open.

Figure 14: Showing related System information on the FLOC. 

Using Systems with Dashboards

The power of Systems comes with the Dashboards. In the same way that the Main Screen grid can be filtered, Dashboard can also be filtered for a selected System (where sources have FLOC information). This way, like when Dashboards are filtered per site-plant-unit, Dashboard can now be filtered per System. Please note that Systems can filter only sources with FLOCs inside them.

Figure 15: System filtering on Dashboard.

Dynamic Form Checklists

Simplifying Checklist configuration

To simplify the Checklist configuration (via Dynamic Forms), Templates are no longer required. A Checklist can now be configured by just adding Fields (questions) to the Dynamic Form Sections. All the properties previously available in the Templates are now available for the Field itself.

Figure 16: Checklist wizard, before and after.The Templates will now rather be used as true templates. This means that once you create a Field (question) for your Checklist with all its properties defined (input type, dropdown, unit of measure…), IMS will remember the Field. Later, when you try to define the same Field (question) in another Checklist, IMS will recognize it and pre-configured it, so you do not need to define it again. If needed, you can change the properties, but the changes will be applied only to that Checklist, without impacting other Checklists.

Figure 17: Adding an existing Field (question) to a Section.

Review collected data with Checklists

IMSFB-28335

IMS now has additional capabilities with regards assessing and reviewing the captured condition history Checklist data, collected during the inspections. Review the data can give useful insights.

To review the collected data, your Checklist can be selected in the Custom Reports Main Screen. Custom Reports has a new tab called Collected data. Alternatively, you can go to the Condition history Main screen, select the desired condition histories, and click on the new button in the toolbar .

Once opened, three different types of views are available:

1. Findings
2. Overview of stages
3. Answers

Findings

The Findings view shows all the answers across the condition histories per row – one row is one answer. These answers are filtered by default per the classification “Issues”. The filter can be changed to see all answers, regardless of the classification. Here you can see all issues identified in your Checklist, which may need some form of mitigation. Thus, from here it is possible to add a remark on certain finding and see if an issue has been mitigated with a CAIR. If not, you can create a Schedule directly from the grid and include the selected issue in a CAIR.

Figure 18: Findings overview with all options available.To capture a remark, click on the “Edit” icon which opens the edit mode for remarks. In addition to adding a remark, it is also possible to edit the classification, so that the list of issues can be managed properly. Once done with capturing remarks, click on the “Save”  icon in the upper left corner to save the changes. To cancel the edits, click on the “Cancel” icon .

For diving into an even more detailed assessment, use the export icon to export the data in the excel sheet.

Figure 19: Capturing a remark in the Findings overview.To add an issue into the scope of a Schedule, click on the middle icon . For all issues selected (across all equipment) one Schedule per equipment will be created. The Schedules will then group and select the issues. If some of the issues are already mitigated, IMS will show a message in green stating that the issue has been already mitigated with an existing Schedule.

Figure 20: Creating a schedule from findings overview.

For a quick overview of mitigated issues, use the filters to show issues with Schedule (Mitigated = Yes). Issues that are not mitigated are without Schedules. To find issues that have Observations, the Observations filter can be used.

Figure 21: Observations and mitigation filters in Findings.

To assess the Observations, you do not need to open the individual Condition History, just click on the expand button and the observations will be listed (if there are any).

Figure 22: Observations in the expand of a Finding.

Alternatively, click on the attachment icon  to see a preview of the attachments and Observations in the side bar. With the preview open, you can click on the row that you are interested in to show the attachments and observations in the preview.

Figure 23: Quick preview of Observations in the sidebar. 

Overview of Stages

To track progress across stages, open the tab Overview of Stages. This view tracks progress on a higher level – stage statuses on condition histories that are using the Checklist.

Figure 24: The Stage overview.

Statuses of stages depends on the number of questions answered:

• Not started – 0 questions answered (0/n)
• In progress – some questions answered but not all (x/n)
• Completed – all questions completed (n/n)
• User set as completed – some questions not answered but set as completed
• Not applicable – no questions answered and set as done

For example, a condition history with a Checklist as shown in Figure 25 is translated into a stage overview record as shown in Figure 26.

Figure 25: The Checklist. 

Figure 26: The Stages Overview record.

Again, attachments can be assessed also from this view by clicking on the same icon. However, this time the preview shows all attachments for the condition history.

Figure 27: The preview shows attachments for each condition history.

Answers

The third way of assessing data is the simplest one – it shows the captured answers in columns, per question. Like as before, this view can also be exported into an excel sheet by clicking on the export button  for a more detailed assessment. Data can also be filtered by clicking on the filter icon.

Figure 28: Overview of all answers in a Checklist.

Mentioned views are also available as sources for Custom Queries or a Dashboard. When creating custom reports, use the following sources:

• Findings: ECH Checklist Findings
• Stages:  ECH Checklist Stages
• Answers: ECH Checklist Answers

Figure 29: Selecting sources for Custom Queries or a Dashboard.

Switching between AND/OR in Conditions

IMSFB-30052

To prevent inconveniences when a condition needs to be switched from AND to OR, it is now possible to switch the condition with one click.

Just hover over the condition, next to the delete icon the “switch” indicator will show. When you click on it, you can switch between the OR and AND conditions.

This is also available on Custom Queries and on a Dashboard.Figure 30: Switching between AND & OR condition. 

Define Categories for Data Fields (questions)

IMSFB-30042

Categories are now available for user creation. This way you can categorize your Data Fields (questions) in the Checklists by defining categories for them. Previously Categories were unavailable for the users to define, but from this version any Category can be created.

The Categories are added on the Data Field level.

Figure 31: Showing a Category in the form.

A new Category can be defined by clicking on the “+” button on the Category field.

Figure 32: Creating a Category. 

Define default spec lookups

IMSFB-30004

In the new version it is now possible to define spec lookup defaults. This means that a Checklist can read from the available Specs on the FLOC or Equipment and show that information in the Checklist.

Define the spec lookup by clicking “+” on the default data bind and entering the exact name of the Spec, usually all capital letters.

Figure 33: Creating a default data bind.

Clearing all answers

IMSFB-30003

In the cases where the “All acceptable” button is selected for a Checklist, you can now also clear all the answers in just two clicks.

Use this functionality with caution as it deletes all answers. This is also why we require two clicks – one for selecting “Clear all” and a second one for confirming it.

Figure 34: The clear all functionality in the Checklists. 

Checklists: Showing number of Observations on Stages

IMSFB-28526 

To highlight valuable findings in Checklists, IMS now have an Observation indicator. Like the “Issues” indicator, for every Stage, the number of Observations is shown, if there are any. This way it is easier to find additional comments and photos captured in the Checklist’s Observations.Figure 35: The observation indicators are shown on the Stage cards. 

Logic/Rules for dropdown options

Previously it was only possible to defined logic/rules (if…then) for Fields, Sections and Stages. But not it is also possible to do so for the dropdowns (Lookup Lists). For instance, if for Question A, the answer is X, then show option Y in the dropdown list of Question B. To achieve this, we use a new Routing Type called “Lookup Option Visible”.Figure 36: Example of logic on a dropdown (Lookup List). 

Auto-selecting (single) dropdown options

Latching on to the dropdown logic/rules, a Field can now be configured for a dropdown (Lookup List) to auto-select an option, if it is the only option remaining. In the Field editor there is a new option called “Auto select Lookup on Single Value”. When this option is checked, then when there is only one remaining options (due to the logic on the Lookup Lists), that option will be auto-selected.

Figure 37: Option to auto-select only option in the dropdown. 

Overview of issues inside the Condition history

IMSFB-30332

To summarize all the issues captured in the condition history, we now have a configurable element which can be added to the condition history as part of the dynamic form. The element shows all issues which are captured in the current condition history. It also shows if any of those issues is addressed with a CAIR or a corrective schedule.                              

Figure 38: Showing an overview of issues in the condition history. 

To configure this element, add a field of a type “HTML” and define “Business logic” to be “Issue Overview”. 

Figure 39: Configuring an overview of issues in the DF wizard.

Hiding and showing “All acceptable” button

IMSFB-30339

The “All acceptable” button is handy to mark all things are good. However, sometimes it is important to check questions, one by one. Therefore, we now also have the option to turn off the “All acceptable” button per stage. This can be configured for every form as needed.

Figure 40: Configuring visibility of the "All acceptable" button on the stage level. 

Sharing and Installing Checklists 

IMSFB-30959

IMS now supports the sharing and installation of checklists from a share repository. The “Shared Libraries” repository is available under the “Custom reports” menu. This is a common, shared, repository of configurations such as checklists. All checklists, which have been shared by others publicly, will be available here.                                

Figure 41: Navigating to the Shared Library.

A checklist needs to be published and made available, before it can be installed by others. When the form is ready to be shared, users can click the new “Publish Package” button.

Figure 42: Publishing a form.

After publishing a form, a new record, with the same name, will show in the “Shared Library”. Forms can have different statuses:

•  Available – form is available on shared library and can be installed
• In use – form is installed 
• Your publish – this is your form which has been published
• Upgrade available – there is new version of the installed form available

To install a form, click the “Install/Upgrade Package” button in the toolbar. The same checklist will then be recreated. 

Figure 43: The install button as well as the form Statuses as shown in the Shared Library.

IOW Enhancements

IMSFB-28980

The IOW has been enhanced in terms of the Virtual Tag functionality, PI Tag search functionality, and the quality indicator status (shown in the CL grid). Also, the exceedance and tracking has been improved and, lastly, a new variable and UoM have been added.

Virtual Tags

IMSFB-29217

As a part of IOW improvements, IMS now supports Virtual Tag configuration.

A Virtual Tag is a way of defining tags using dynamic expressions. Expression can be composed using PI Tags and built-in functions like:

• +, -, *, /
• MIN, MAX, MEAN, SUM, ABS, SQRT, STD
• If then else
• ( ) 

Below is an example where a Virtual Tag expression is defined and verified. Users can select a PI Tag from the list and click the Add button to add the Tag to the expression. When done defining the expression, it can be verified by clicking the Test button.

Figure 44: A PI Tag is added to the expression with the Add button. The Test button is used to verify the expression.

When the Virtual Tag’s expression is verified, IMS will either show a green valid message or a red error message.

Figure 45:An error message is shown in case of, e.g., a syntax error in the expression.

When the expression has been verified, the Virtual Tag can be configured for the IOW.

Figure 46: Configuring a Virtual Tag.

The Virtual Tag will then be added to the IOW main grid as a “Virtual Tag” variable. The expression will be shown in the description field and the calculated value will also be shown.

Figure 47: Adding a Virtual Tag to the IOW grid.

This way exceedance calculations can now also be based on the Virtual Tag, like how it is done for PI Tags.

Figure 48: A Virtual Tag in the IOW grid, where the exceedance requirements can be added. 

PI Tags search using wildcards

IMSFB-29218

When adding PI Tags to the IOW (also when adding it to a Virtual Tag expression), users can search for the Tag name using wildcards in search string. Valid examples are:

• *Test* (this is also default behavior when no wildcard is used)
• Test*
• *Test
• Test

Figure 49: Searching for a PI Tag using wildcards. 

IOW Quality Indicator and Number of IOW variables in CL grid

IMSFB-26282

Two new columns are now available in the Corrosion Loop Main Screen Grid: "IOW Quality Indicator" and "Nr Of IOW Variable". If a CL has multiple IOW variables, then the highest/best IOW Quality Indicator will be shown. For instance, if one IOW's Quality Indicator is grey ("Not interfaced..."), but the other IOW's is green ("Interfaced with PI..."), then the Quality Indicator shown will be the green one.

Figure 50: The two new columns that were added to the CL. 

When users hover over a Quality Indicator, the definition of the Quality Indicators will show.

Figure 51: When hovering over a Quality Indicator, a definition of the Quality Indicators will show. 

Additional information will also show for the title of the "IOW Quality Indicator" column when hovering over it.

Figure 52: Showing additional info when hovering over the title.

Users can also filter the Corrosion Loop Main Screen grid for a specific IOW Quality Indicator.

Figure 53: The IOW Quality Indicator filter for the CL.

 

Exceedance Tracking

Exceedance tracking has been improved by adding two new fields and in terms of the unit format. Note that also the exceedance for virtual tags can be tracked (see Virtual Tags).

Two new fields

Two new columns were added to the IOW grid:

• “Nr Exceedances last three months” (End Date is 3 months from today)
• “Nr Exceedances last year” (End Date is12 months from today)

Figure 54:The IOW with the 2 new columns shown.

Unit format for IOW Max time exceedances

IMSFB-16109

The units for “IOW Maximum time single exceedance” and “Maximum time cumulative exceedance” that are used in the import template are now in the format: day:hour:minutes as shown in the figure below.

Figure 55: Unit format for IOW Max time exceedances. 

IOW grid improvements in terms of UoM and variables

New Measurement Unit for “Pump-in Rate”

IMSFB-16160

For the “Pump-in Rate” Variable a new Measurement Unit: “Gallons per Day” was added.Figure 56:The Pump-in Rate” variable with the new Measure Unit: “Gallons per Day”.

New “Corrosion Coupon” Variable

IMSFB-16647

We added the “Corrosion Coupon” Variable with Measurement Unit: “Mils per year” to the IOW dropdowns.Figure 57: The new “Corrosion Coupon” Variable with Measurement Unit: “Mils per year”. 

MEC Cost Calculation update

The MEC Cost Index calculation has been updated in terms of the Task Costs.

Only approved Tasks included in MEC Cost Index

IMSFB-27267

To better control the Tasks that are included in the final MEC Cost Index calculation, IMS now takes only approved Tasks into consideration. Tasks with in the status “NA – Not Approved“ are not used in the calculation. Both “Automatically Approved“ and “Manually Approved“ Tasks are taken into consideration when the MEC Cost Index is calculated.

Figure 58: Approval status of tasks in RCM. 

Task Cost calculation change

IMSFB-27957

Previously IMS used the total detailed cost as the Task Cost. This included Total Production Losses + Total Repair Cost + Total Labour Cost. This calculation thus included costs of downtime and reduced throughput.

The Task Cost calculations has been updated to include only the Total Repair Cost + Total Labour Cost. This cost is the annualized with the interval before being included in the MEC Cost index calculation. The equation for Annualized Task Cost now is:    Figure 59: Only the red Task Costs are included in MEC Cost Index calculation.

 To increase transparency, a new custom Query, called “Tasks cost overview“, is available to show the Task Costs, including the new Annualized Cost, that takes part in the MEC Cost Index calculation.

Figure 60: New custom report with task overview for MEC Costs.

The final equations of the MEC Cost index, however, remains unchanged:

Other ONE IMS Improvements

Role Assigning Privileges

IMSFB-26514

We have reviewed the Role rights with regards to the Roles assigning privileges and implemented the following logic:

• The CSA has the absolute power, he can assign any Role to anyone across any module.
• Users with Admin Roles can assign Roles from their own methodology to users from any methodology. The Roles assigned must be lower or on the same level as their own. For example, the PEI ADMIN can assign this same Role to an RCM user.
• VIEWER Roles can be added to users across the methodologies
• An exception to this rule is the INSP Admin Role. He can also assign the Fabric Maintenance and Civil Roles. The same applies to the RCM Admin Role. He can assign the CHANGE/DEFERRAL Role.

Take note: Only users with an Admin Role can edit other users.Figure 61: The Role levels, with 15 being the highest.

Sending Query results immediately via email

IMSFB-19849

IMS can now send Query results immediately in an excel sheet via email. In the past it was only possible to schedule these reports - daily, weekly, monthly, etc. Now IMS also supports the manual triggering of those Queries. This is handy if the results are needed immediately, but also if one wants to test the Query.

Take note: Queries must be created and saved before it will be sent via email.

When a query is created, the user will have the options: Send to me now and Send to all recipients now (entire group that is listed). If selected it will then be sent after the query is saved.Figure 62: When a query is created you can now send the results immediately.

The results are delivered as an excel sheet in the attachment of an email.

Figure 63: The email with the query results.

Dashboard Improvements

Dashboard color coding

IMSFB-29037

To better distinction between system dashboards and user-created dashboards, color coding has been introduced to the dashboard picker. Also, the icon look has changed.

System dashboards are now highlighted in grey in the picker, while the user-created dashboards or site-specific dashboards are colored in white.Figure 64: System dashboards are now highlighted in grey.

Similar as previously, icons communicate if a Dashboard is editable. The lock icon means that dashboard cannot be edited but it is visible to everyone. The unlock icon means that everyone can edit it, and everyone can see it. The user icon indicates that the Dashboard is private, editable, and visible only to the creator.

Icons communicating visibility and editability:

Improved Dashboard behavior on tablets

The Dashboard layout now adjusts to the device screen. This means that charts are resized to fit on the screen. The order of elements and sections remains the same, but their size depends on the screen size. Also, when sections are re-arranged, the element will be moved as well depending on their relationship with the sections (left-right or down).Figure 65: The Dashboard layout on a tablet.

Advanced Condition History expand option

IMSFB-29861

IMSFB-28904

The expand option, in the Condition History Main Screen grid and in the Equipment Details Page in the “Condition history” section, has been enriched with information. Previously when the expand button was clicked only the Narrative was shown. Now the following is shown: Codes (Actions Performed, Conditions Found, Repairs Planned), Narrative, Observations, Issues, and Attachment.Figure 66: New advanced expand in the Condition History Main Screen grid.

Network Indicators

It can happen that the network or the VPN is lost while using IMS, and then it may be unclear where the issue is. IMS can now detect whether it is the internet connection that is lost or the connection to the server. This information is shown in the IMS header. One of the following two icons will be shown when a network issue is detected:

The first icon indicates an issue with the server, while the other icon indicates that the internet connectivity is the issue.

Faster rendering of main grids

The Main Screen grid list rendering speed has been improved. IMS is now smart enough to only render the data that is needed. If the grid should show 200 records, but only 40 records fit on the screen, IMS will now only render the 40 records shown. The additional items are shown with scrolling, until the 200th item is reached, similar as before. This way rendering speed is increased by 60%.

Remembering last used Labels

Due to the increasing number of IMS users, the number of labels is also increasing. This can make it difficult to quickly find one’s label. For this reason, IMS now remembers the last used label. When using labels, the last used label will be suggested to the user. Note: The last used label is remembered per module, as labels are usually not shared across modules.Figure 67: Preselecting last used label.

Quick Tip for Alternative Hierarchy Move

IMSFB-28156

The quick tip message for the moving of an item to an Alternative Hierarchy has been updated. This is to avoid confusion between moving items to an Alternative Hierarchy and to a different CMMS unit.Figure 68: The quick tip message for the moving of an item to an Alternative Hierarchy. 

Showing the owners of FLOC types and Equipment groups

IMSFB-30132 

To increase transparency, equipment groups and FLOC Types CMMS Owners are now shown in IMS. The CMMS Owners are the methodologies (i.e., disciplines). This is important information to be visible on the type level and can be found in the Settings \ Maintenance \ Configuration \ Configuration per Hierarchy Type.                               Figure 69: CMMS Owner field in settings.