Documentation Index

Fetch the complete documentation index at: https://ims-handbook.cenosco.com/llms.txt

Use this file to discover all available pages before exploring further.

Understanding the Difference between Visibility and Ownership

Updated
  • Updated on May 22, 2026
  • Published on Mar 9, 2026
  • 2 minute(s) read
  • Tomislav Renic
  • Elsa Tolsma
 Prev Next

It is important to understand the distinction between Visibility and Ownership.

Visibility: Specific Equipment Groups or FLOC Types can be configured to be visible in certain modules, while hidden in others. For example, for your site it could be setup that PEI will not see the Analyser Equipment group, while RCM will see the Bundle Equipment group. When a Hierarchy Type is visible in a module, all Equipment IDs or FLOC IDs belonging to that Hierarchy Type can be viewed within that module.

Ownership: For a specific Equipment ID or FLOC ID to be owned by a module, the corresponding Hierarchy Type must be both owned by and visible in that module. Only Equipment IDs and FLOC IDs owned by a module (discipline) can be edited within that module.

By default, RCM users have access to nearly all Hierarchy types. This allows RCM users to create various types of Equipment, such as Pipe Equipment, even when they do not own them. The same applies when the CMMS  interface is enabled exclusively for the RCM side.

Visibility and Ownership per Hierarchy Type are configured via: Settings \ Maintenance \ Configuration \ Configuration per Hierarchy Type.

Managing Visibility - Practical Considerations and Solutions

It occurs often that users need to remove something from any given module. Typically, PEI users will want to make Floc/Equipment not visible in PEI. This practice has shown to be rather problematic in a real-world application due to the following reasons:

  • There may be multiple Equipment under the same Floc, complicating the matter of assigning correct visibility.

  • Once Floc/Equipment is removed from PEI (no longer visible) other users will not be aware of their existence.

  • Any history for inspections already performed on stated Floc/Equipment will no longer be accessible.

  • Due to various functionalities, Flocs/Equipment may be automatically put back into PEI. For example, the CMMS interface, when triggered, will align the Floc/Equipment visibility to the CMMS type visibility.

The proposed solution is to use existing IMS features (Inspection Reason and Filters) to manage Flocs, Equipment, or Circuits that are not intended for inspection, while keeping them accessible to all users who may need to view them:

  1. Firstly make sure that all Flocs/Equipment/Circuits that should not be inspected (at least not any longer) in PEI have an appropriate Inspection Reason assigned. For this purpose, there are two appropriate options: “Class 4” and “No Insp. req” (in the standard list of inspection reasons configured). Doing so will prevent default Schedules from being created on Equipment with the appropriate Inspection Reason.

  1. Next, we recommend filtering out “Class 4” and “No Insp. Req” from Floc/Equipment/Circuit grids. IMS allows several ways of managing filters. In the below example, we are showing how to create and save a new filter on the Floc grid:

    1. Filter out inactive Flocs and Flocs with Class 4 Inspection Reason.

    2. Save the filter to make it easily available for future use.

    3. The saved filter can be selected from the drop-down list. After the filter is selected it is applied automatically to the grid results.

To learn more about filters see IMS Main Screen (Grid List).