Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

OSM Installation

Upgrade Notes for OSM 11​.2

  • Last UpdatedNov 01, 2023
  • 3 minute read

This release contains major changes to the Isolations module and AIM configuration.

AVEVA™ Asset Information Management Connections

Previous connections to AVEVA™ Asset Information Management (formerly AVEVA NET) will need to be manually reconfigured for all sites and for all types of isolation lists.

Note: The name of AVEVA NET has changed to AVEVA™ Asset Information Management.

Merging statuses for Isolation list

Previously, there was one default isolation list type, and it contained a lengthy set of statuses to account for different possible isolation list types, such as mechanical and electrical types. In Operational Safety Management 11.2, you can add separate new isolation list types and give them each their own set of statuses. Therefore, it is no longer necessary for the default isolation entity to contain such a large set of statuses to account for all types.

You will need to make a choice during upgrade whether to merge existing statuses for Isolation lists or retain the existing statuses. The mandatory statuses are 100 New, 800 Closed, and 900 Canceled.

Merge option

If you answer Yes to the question, the duplicate statuses that were previously used for different types of isolation list will be removed.

  • Reduces number of statuses in list to unique statuses only.

  • Keeps the first occurrence of a status and removes duplicate statuses.

  • You can renumber or rename statuses after the merge.

    Note: There is no Undo operation. Be certain you want to remove duplicate statuses, before selecting Yes.

Keep option

If you answer No to the question, then most previous mechanical and electrical statuses are retained as a comprehensive list of statuses.

  • Only the mandatory statuses 100 New, 800 Closed, 900 Canceled will be merged.

Previous statuses for default isolation list entity

Here is an example of the previous existing statuses for isolation list entity before upgrade.

  • 1.1.0 – New (Mechanical)

  • 1.1.5 – Approval pending (Mechanical)

  • 1.3.0 – Active (Mechanical)

  • 1.5.0 – Reset requested (Mechanical)

  • 1.5.5 – Reset in execution (Mechanical)

  • 1.6.0 – Completed (Mechanical)

  • 1.9.0 – Canceled (Mechanical)

  • 3.1.0 – New (Electrical)

  • 3.1.5 – Approval pending (Electrical)

  • 3.3.0 – Active (Electrical)

  • 3.4.0 – Test in execution (Electrical)

  • 3.5.0 – Reset requested (Electrical)

  • 3.5.5 – Reset in execution (Electrical)

  • 3.6.0 – Completed (Electrical)

Example of statuses for isolation list after merging

This table shows an example what might happen when previously duplicate statuses for isolation list entity are merged during upgrade.

Statuses Before Upgrade

Statuses After Upgrade

Statuses After Manual Renaming

Mandatory

Statuses for Mechanical type

110 – New

Kept. 110 – New

100 – New

Yes

115 – Approval pending

Kept. 115 – Approval pending

150 – Approval pending

130 – Active

Kept. 130 – Active

300 – Active

150 – Reset requested

Kept. 150 – Reset requested

500 – Reset requested

155 – Reset in execution

Kept. 155 – Reset in execution

530 – Reset in execution

160 – Completed

Kept. 160 – Completed

800 – Closed

Yes

190 – Canceled

Kept. 190 – Canceled

900 – Canceled

Yes

Statuses for Electrical type

310 – New

Removed.

Superseded by 110 – New

315 – Approval pending

Removed.

Superseded by 115 – Approval pending

330 – Active

Removed.

Superseded by 130 – Active

340 – Test in execution

Kept. 340 – Test in execution

570 – Test in execution

350 – Reset requested

Removed.

Superseded by 150 – Reset requested

355 – Reset in execution

Removed.

Superseded by 155 – Reset in execution

360 – Completed

Removed.

Superseded by 160 – Completed

390 – Canceled

Removed.

Superseded by 190 – Canceled

Status codes with less than 3 digits will not upgrade

You must fix all status codes with less than 3 digits before upgrade can proceed.

Upgrading statuses for wmm_isolationlist entity

Before performing the upgrade on the database, the customer and project manager should decide how existing statuses for the wmm_isolationlist entity should be treated during upgrade.

Statuses can be merged to a reduced list or kept as they are.

Upgrading business rule for wmm_isolationlist entity

We recommend that before upgrading the database, you should make a record of the business rules configuration for the wmm_isolationlist entity.

Configuring Print labels for Isolation List type

You will need to configure the Dynamic functionality for Print labels for Isolation List type after the upgrade. This is not done automatically.

In This Topic
TitleResults for “How to create a CRG?”Also Available in