What's new in 11​.2

What's new in AVEVA™ Operational Safety Management 11.2

New features in OSM Administration

AVEVA™ Identity Manager for authentication

We have introduced AVEVA™ Identity Manager for client authentication. In response to cybersecurity issues in today's networked world, it was necessary to integrate an identity manager. Sign in through AVEVA Identity Manager requires a user to enter Windows credentials or an OSM user name.

Identity Manager is only for web application authentication. For more information, see AVEVA™ Identity Manager.

Enhancements to the Isolations module

The Isolations module underwent a major technical upgrade.

• We made changes to Isolation lists and how they work. We added a new Isolation list type.

• You can create and save custom Isolation list types based on either a mechanical template or an electrical template.

  

• P&IDs have been renamed to schematics.

• Electrical list types can now have schematics.

• There is the ability to specify schematic classes for each Isolation list type.

• Isolation list types are highly-configurable with the new Dynamic Functionality feature.

Dynamic Functionality

The new Dynamic functionality feature offers great flexibility in configuring how an Isolation List type works.

You can create and save custom combinations of functionalities for different Isolation List types. In the Web application, the columns for Isolation Lists will appear and work as configured.

Isolation Point label printing

The ability to print Isolation Labels is now determined by a dynamic functionality. By default, the functionality to print labels is set to off. Isolation Point labels can only be printed if a template has been been uploaded.

There is a new label-point-pos-maintenance-new field for the Isolations Label schema template. See Field values for isolation point labels.

Extending work permits

There are changes to the way to configure work permit extensions. See Configure ability to extend work permits.

Previously, there were Active and ActiveExtended statuses. In version 11.2, there is Active status only . You will need to reconfigure work permit extensions to match the new configuration.

Configure work permit status for inclusion on Monitoring tab

The Monitoring business rule identifies which statuses for work permits will cause a work permit to appear in the Monitoring tab of Work Permit Library. You will need to enable the Monitoring business rule on each status of the work permit entity — where you want the work permit to be considered relevant for the current shift.

Plot Plans

There is a new Plot Plan item on Main menu. The new options enable you to view and calibrate a plot plan manually without using Image Calibration Tool. You can also set coordinates manually.

• Connect/disconnect area

• Adjust projection / cross section

• Validate transformation matrix (matrices)

Access Groups

User groups have been renamed to Access groups. The functionality is the same; however, there is now an Access group code.

Template Users

A template user is primarily a dummy account that is configured with the roles and access for a specific job role. See Template users.

Company Units

Organization units have been renamed to Company units. The functionality is the same; however, there is now a Company unit code.

Invalidate Signatures in Approval Loop

There is new configuration to invalidate signatures when a work item is sent backwards in the workflow. See Invalidate signatures in approval loop.

Business Rules for Work Permits

There are two new business rules for work permits:

• Cannot process work permit if not associated with a TRA

• Cannot process work permit if not associated with a SJA

Do Not Reply email address

When AVEVA™ Operational Safety Management is sending an email to a user regarding a work item (for example, a work permit that is to be approved), the Sender email address will be equal to "[email protected]". This is to indicate that the email cannot be replied to.

The Do Not Reply email address can be configured with smtp_donotreplyemailaddress in Application Settings.

For more information, see Set the DoNotReply email address.

Job Schedules

We have made some minor changes to the Job Schedule window.

• The Start date is now required to be scheduled at least 24 hours after the current database time.

• The If a job could not be performed property and options have been removed. If a job fails to perform, all jobs will run again at the next schedule time.

• It is now possible to add notification recipients to a job without stopping the job.

• The Error log report is renamed to Failure log report.

Life cycle stages

There is a new Life Cycle Stages drop-down menu on the Status window for Entities and workflows. This replaces the need to use progvalues to apply life cycle stages.

Support for Spanish (Mexican)

• We have added support for Spanish (Mexican) as supported language.

Product Name Changes

The name of AVEVA NET has changed to AVEVA™ Asset Information Management (AIM).

Deprecated features in OSM Administration

Functionality is marked as deprecated when a feature is still supported in the current release, but might be removed in a future release. We advise that you phase these features out of your projects and begin to use alternative features.

• User Groups - The Access groups category on the System Administration menu has been deprecated. This will be replaced in the future by a new user management system.

• Operational Safety Management 11.2 is the last version that will support HTTP. Future versions will require using HTTPS.

  Discontinued features in OSM Administration

Discontinued features have been removed from the product, or are no longer supported.

• Discontinued support for Internet Explorer - Internet Explorer is no longer a supported browser. For more information, see the AVEVA Operational Safety Management Installer Guide.

• Discontinued support for Oracle 18c and earlier.

• Discontinued support for .NET 4.7.1 and 4.7.2. - These versions are no longer supported due to security problem in CLR (CVSS 10.0).

  Changes to installation requirements

There are the following changes to installation requirements.

• Windows Server 2019

• Oracle 19c required

• .NET 4.8 required

• Connection to AVEVA™ Identity Manager Server is required.

  Security updates

We made the following security updates.

• Increased password strength rules.

• Restricted the access for cowapp system user.

  Security Warning: Before a supplementary form template in HTML is uploaded to the OSM database, it is important that the HTML contains no malicious code. Introducing malicious code into the HTML could result in an XSS attack in OSM Web Application. The customer is responsible for creating an HTML file that is well-formed HTML.