What’s New in APM 7.12.5

Two of the enhancements made to AssetWise Performance Management (APM) in release 7.12.5 pertain to APM when AssetWise Enterprise Interoperability (AWEIS) has been implemented to exchange data with an external CMMS. This release also introduces enhancements to features, indicators, work schedules, and more.

Contents

AWEIS – Failure Codes

AWEIS – Publish APM Events

Data Loading

Features Management

Inspection Management

Reliability Program – Remove Overrides

SELECTserver Licensing Simplified

Supported Database Software

Work Schedules – Limiting Hours

AWEIS – Failure Codes

With AWEIS 1.2.7.0 and APM 7.12.5, you can define as many as five levels of failure codes and name them to match the codes used in the CMMS (for example, activity type, activity cause, and activity source). APM can then be populated with instances of failure codes from the work orders, work requests, and solution packages sent from the CMMS. In APM, you can add failure codes to requests for work, failure records, and failure modes.

Failure codes provide a more flexible alternative to the object parts, damage codes, and activity codes referenced on recommendations from events. Failure codes and levels are independent of each other, unlike object parts, damage codes, activity codes, which form logical hierarchies of ownership. The Failure code type setting in the site interoperability profile determines if failure codes, object parts (and so on), or neither are available on a site.

AWEIS conforms to the current site interoperability profile and standard behavior when adding and updating failure codes in APM. For example:

•	If a new work order arrives with failure codes from five levels but APM supports only three levels, three codes are recorded on the interop work order and a message is logged in AWEIS

•	If a new work order arrives with a failure code that does not exist in APM (and APM supports the failure code level), the code is recorded on the interop work order and added to APM

•	If incoming failure codes already exist in APM but with different details, the code details are not updated in APM

•	Updates to existing failure codes are subject to the Value Lists settings in the site interoperability profile. These settings control which failure code properties can be updated and actions performed by AWEIS

Note: To use this functionality in APM, you must first enable feature 46. In the Enterprise window, select the Features view and the Enabled Features tab. Click Browse, select “Failure codes support with AssetWise Interoperability”, and click OK. If APM is running as a smart client, click Refresh Enabled Features on the server. Then restart the client to use the functionality.

Setting up APM to use Failure Codes

Setting up failure codes involves the following steps:

•	In the Site Interoperability Profile window, select the Work Management and Failure Coding tabs. In the Failure code type options, select Failure codes. The tab changes as follows:

The default number of failure code levels is three. You can select a different number (up to five). Provide a descriptive name for each level. For example:

•

AWEIS can then import failure code values into APM from the CMMS. When a failure code value is added or updated in the CMMS or when a work document is sent from the CMMS, failure code values in APM are updated. To view the codes, open the Site window, select the Work Management view, Settings, and Failure Codes tabs. You will see one tab for each of the levels you added in the site profile.

•	Once codes have been defined at the next level, you can edit a higher-level code to specify which codes from the next lower level are allowed to be selected in a request for work, for example. In this example of a first-level code, the second-level codes are available for selection:

For more information, see Setting up Failure Codes.

•	You can set up your work types to specify whether a failure code is mandatory on a request for work. In the Work Type and Site Settings dialog, select the Requests or Trigger Requests tab and then the Mandatory Properties tab. Select the failure code levels that are mandatory. For example:

Similarly, you can specify that failure codes are read-only in APM.

For more information, see Setting up Site-Specific Work Types.

Requests for Work

Request for Work windows have been updated to accommodate failure codes:

•	When recommendations from events are supported, the Events tab is available, where you can add events and select part groups, parts, damage codes, and activity codes. Here is an example from a request for work created from scratch:

•	When failure codes are supported, the Failure Codes tab is available, where you can select failure code values and add a description. Here is an example from a request for work created from scratch:

•	Work information like type, priority, and dates now appear on the General tab, rather than on the Details tab

•	The Details tab, if it appears, contains the user-defined fields that have been set up in the interoperability site profile

•	The Reference Numbers tab appears if reference numbers have been set up in the interoperability site profile

Similar changes have been made to Acknowledge Indicator Alarm windows when the acknowledgment method is Request for Work, as well as in other windows where you can create requests.

For more information, see Creating a Request for Work from Scratch.

Interop Work Requests and Interop Work Orders

The Interop Work Request and Interop Work Order windows, Properties view, contain tabs labeled either Event or Failure Codes, depending on the Failure code type setting in the site’s interoperability profile. The Recommendations tab is now called Tasks, and it displays recommendation tasks.

Maintenance Action Plans

When you are developing failure modes on a strategy development analysis (MTA2, RCM2, or RBI), you can add failure data and patterns in the Maintenance Action Plan window, Failure Information view. The third tab in this view is labeled either Events or Failure Codes, depending on the Failure code type setting in the site’s interoperability profile.

On the Failure Codes tab, you can select codes and add a failure description. For example:

Failure Records

In the Failure or Anomaly window, the Properties view contains a tab labeled either Events or Failure Codes, depending on the Failure code type setting in the site’s interoperability profile.

When you reference a failure mode on the General tab, the failure mode’s failure codes and description are copied to the Failure Codes tab. You can also select codes and add a failure description. For example:

Solution Packages

Solution packages support failure codes, if specified by the Failure code type setting in the site’s interoperability profile. You can select failure codes and provide a default description on solution package templates. When a solution package is referenced in a request for work or other work document, the failure codes are copied from the solution package. Note that if the work document already has one or more failure codes, those codes are not replaced by values from the solution package.

AWEIS – Publish APM Events

When APM objects are created, updated, or deleted, events can be produced (serialized) and published to an external system using AWEIS. Configuring this functionality involves creating interface classes and a package, creating an APM outbound event service provider, and configuring a service instance.

For more information, see Setting up APM Outbound Events.

Note: For APM 7.12.5, the Publish APM Events feature does not support Oracle DBMS without additional steps. If you wish to use this feature with Oracle 12, contact Bentley Support.

Data Loading

This release includes the following new or enhanced data loaders. In addition, the “Technology Preview” designation has been removed from the following data loader:

•	Suppliers (Purchasing)

MTA Templates

This data loader adds or updates MTA templates in APM.

RBI FMEA

The RBI FMEA data loader now supports the following information:

•

Evident

•	Inspection coverage percentage

•	Inspection location

•	Inspection location note

•	Material type

•	Selected degradation rate

•	Selected degradation rate units

•	Suggested technology (PdM technology)

•	Theoretical degradation rate

•	Theoretical degradation rate units

Features Management

It is now easier to view and work with APM product features.

Site Window

In the Site window, you can click the Administration or Help menu and then APM Features to open the Available APM Features dialog. Use the navigation buttons to browse through the features that are generally available or available for preview. For example:

Enterprise Window

In the Enterprise window, the Enabled Features tab moved from the Customization Center to the new Features view:

The new Features tab provides three ways to filter information:

The “All features” configuration includes development status and “Updated on” columns.

We recommend using your Test environment to enable and explore features that are available for preview. It is expected that only completed features would be enabled in a Production database.

Note: We recommend using APM security to ensure that only appropriate users have access to the features management function.

For more information, see Features Management.

Inspection Management

The following enhancements have been made to indicators and checksheets.

Checksheets – Approvals

The Automatic Approval Rule on approval routes allows approval requests to be automatically approved if they fall under a certain value. For example, work orders under a planned value of $100 could be automatically approved so that the route’s approvers do not have to review and approve them.

The approval threshold is currently used with documents that have a dollar amount associated with them: work orders, work requests, requisitions, and so on. With this release, the functionality has been expanded to include checksheets.

To use this functionality, set up a checksheet approval route with any non-zero approval threshold. As a result, when an approval request is processed for a checksheet with a checksheet type that uses that route, the request is automatically approved.

For more information, see Setting up Automatic Approvals.

“Default to Normal” Setting

You can now turn on a setting that defines the Default to Normal is allowed for this indicator option as the default on indicator templates for the site.

In the Site window, click the Administration menu, Inspection Management Settings, and then Indicator Management to open the Indicator Settings dialog. Select the Defaults tab and click Checksheet default to normal default:

On new descriptive indicator templates, the States and Alarms tab shows the result:

The setting is copied to indicators based on the template, and checksheet readings have the Default to Normal option available.

Calculation Auditing

To improve product performance, you can control the amount of auditing information generated when a reading is created for a calculated indicator. The audit information is displayed in the Indicator Reading window, Calculation tab.

To set the level, open the Indicator window. Select the appropriate option on the Calculation tab, Auditing tab. For example:

Setting Name

Description

Auditing level for the indicator’s readings

Auditing levels are: • Full auditing – Full information is displayed on the reading’s Calculation tab • Description and input values – The reading’s Calculation tab displays the description and input values in the text field. The table of input values is not displayed • No auditing – The reading’s Calculation tab is not displayed

Calculation Metrics

You can now monitor the performance of calculated indicators by reviewing calculation times on readings. For an individual indicator, select the Readings view and the Calculation Times tab. The “Calculation time” table displays the indicator’s readings and the time it took APM to calculate each reading value in milliseconds.

In the Site window, select the Analytics view and the Calculated Indicators tab. The configuration list provides three ways to view the information:

•	“Calculation time” lists readings by calculation time, from highest to lowest values

•	“Calculation summary per indicator” lists indicators with grouped rows of readings that you can expand. Each indicator’s summary includes the average calculation time and the number of readings

•	“Calculation time by indicator” lists assets, their indicators, collected on dates, and calculation times in descending order

Reliability Program – Remove Overrides

You can now open a task template and remove overrides from the standard tasks that are linked to it. In the template’s Standard Task window, click the Tools menu and then Remove Overrides. The Remove Overrides dialog appears listing only standard tasks that were created from the template and that have overrides. For example:

Select the standard tasks that you wish to change and click OK. Their overridden properties will be returned to the template’s values.

Note: To use this functionality in APM, you must first enable feature 52. In the Enterprise window, select the Features view and the Enabled Features tab. Click Browse, select “Remove overrides from a task template’s standard tasks”, and click OK. If APM is running as a smart client, click Refresh Enabled Features on the server. Then restart the client to use the functionality.

SELECTserver Licensing Simplified

Managing licensing for APM products has been simplified. For example, instead of multiple product codes, one code – 2386 – is used for APM and its product modules and APM Remote.

You will notice this when downloading software. AssetWise APM Foundation is the only package you need.

As a result, licensed products are no longer displayed in Enterprise Properties. The License page in the Web Monitor has been simplified.

Supported Database Software

APM no longer supports version 11.2.x of the Oracle® database management system.

For a complete list of supported software, see APM Installation Prerequisites.

Work Schedules – Limiting Hours

This release provides enhanced flexibility for scheduling work order tasks. On the task, you can set a limit to the amount of time allocated to each shift when the work is scheduled.

Consider the example of a work order task that requires three hours of an inspector’s time during each day shift for consecutive shifts until the 15 hour labor requirement is completed. APM can automatically generate schedule entries for five weekdays, each with a duration of three hours.

To set this up, you would set the Limit scheduled duration property on the work order task to 3 hours. For example:

Note that you can set limits on standard task templates and then apply the changes to standard tasks that are based on the templates. When work orders are created from the standard tasks, the limits are copied to the work order tasks.

When creating the maintenance schedule, ensure that entries respect shift and date boundaries:

When you create the first schedule entry, assign the work order task, duration, shift, and start date. When you click OK, APM automatically generates entries for the remaining time requirements, that is, three hours for each of the remaining days of the week. For example:

Note: To use this functionality in APM, you must first enable feature 50. In the Enterprise window, select the Features view and the Enabled Features tab. Click Browse, select “Support ability to limit the duration that is scheduled for a work order task”, and click OK. If APM is running as a smart client, click Refresh Enabled Features on the server. Then restart the client to use the functionality.