Available Features

APMupgradetips, Technology Preview, features, Available

The following product features have the availability status "Available" as of the APM ~~7.22~~7.23 release. They are functionally complete and have been fully tested. A feature must be manually enabled at the enterprise level before you can use it in APM.

Number	Feature	Description
000115	Practical RBI - criticality evaluation calculations	This feature introduces the ability to automate the process of analyzing a failure mode's criticality through the use of lookup tables and delivered calculations. The ability for the user to define their own custom calculations is also supported.
000114	Ability to identify start and end locations on a video on indicator and measurement point reading	This feature introduces the ability to identify one or more videos to a checksheet. Once the videos have been linked to the checksheet, the locations on the video where an anomaly can be seen can be identified on individual readings. Inspection videos are typically used in places where inspectors cannot access the equipment or structure themselves and an unmanned vehicle is used.
000113	Support for drilling platform asset specifications	This feature introduces support for asset properties related to oil drilling platforms.
000112	Support for the ability to add readings to a checksheet based on the value of a reading	This feature introduces the ability to have additional conditional readings added to a checksheet based on the state entered for a reading. For example, if an indicator is in alarm, additional checks or readings need to be taken. These additional readings are only required if the first reading is in alarm. With this feature, you can identify the conditional indicators as part of the indicator state properties.
000111	Solution package data loader	This feature introduces two new data loaders for solution package tasks. The first allows the standard tasks associated with a solution package to be created or updated. The second allows task templates associated with a solution package template to be created or updated.
000110	Indicator due date data loader	This feature introduces a new Indicator Due Date data loader. The data loader allows new due dates to be loaded for one or more indicators. The data loader is included as part of the Inspection Management data loaders on Enterprise.
000109	Prevent redrafting of a checksheet based on the checksheet status	This feature introduces the ability to control the availability of the redraft method based on the checksheet status.
000108	Anomaly risk assessment	This feature introduces the ability to integrate APM with an Anomaly Assessment and Tracking (AA&T) system.
000107	Calibration template support	This feature introduces the ability to define calibration templates. Calibration templates can be used to provide default values for a checksheet subtype. Currently, five subtypes are supported to enter calibration details on a checksheet: Ultrasonic calibration, Radiography calibration, dye penetration inspection, magnetic particle inspection, and eddy current inspection. Calibration templates can be created for each subtype.
000106	Option to limit an asset status change to the current asset only	This feature introduces the ability to limit an asset status change to the current asset only. The status of the asset's descendants is not updated.
000105	Support the ability to update the warehouse item's storage locations when entering a count	This feature introduces the ability to correct the warehouse item's inventory storage locations when recording a count. The warehouse item's locations are updated when the resulting adjustment transaction is posted.
000104	Support for displaying asset PI&D or other document as part of the asset specifications	This feature introduces the ability to display an asset document as part of the asset's specifications. The document displayed can be any document linked to the asset and can be a PDF, graphic image, Word document etc.
000103	Support for Platform Inspection subtypes on Measurement Point Readings	This feature introduces the ability to record information related to platform inspections. It controls access to the following subtypes for measurement point readings: ·Platform general visual inspection ·Platform debris ·Platform scour ·Flooded member detection ·Weld survey ·Platform cathodic protection
000102	Support structural minimum thickness when calculating an asset's minimum thickness	This feature expands the existing minimum thickness calculation function to include support for Structural Minimum Thickness.
000099	Support for reliability projects	This feature expands the functionality associated with projects to allow the different types of analyses and other objects to bel linked to a project. The types of objects that can be linked to a project are: Strategy development analysis Asset prioritization analysis Asset condition analysis Reliability strategy selection analysis Failure or anomaly Root cause analysis Safety provision version Asset restoration plan SDA study
000098	Support for project tasks	This feature introduces the ability to identify tasks to be performed for a project. Project tasks provide a simple method of identifying tasks or actions to be performed without requiring the use of work orders or tasks. Project tasks have a limited set of properties and are not meant to replace work orders and tasks in cases where work planning is required.
000097	Support site filtering rules of analysis team members	This feature introduces the ability to control the employees who can be selected as team members. The new settings allow you to allow employees from: The same site as the analysis The same site and its higher level sites The same site and its lower level sites Sites in the same branch of the site hierarchy Any site These options apply to team members on a strategy development analysis, asset prioritization analysis, asset condition analysis, and RCA.
000096	Support for Dead Leg Piping section asset specifications	This feature introduces the ability to define properties related to a dead leg piping sections on an asset's specifications.
000095	Support for Fabric Inspection subtype on Measurement Point Readings	This feature introduces the ability to record information related to fabric or structure inspection for an oil drilling platform.
000093	Support for Oil Drilling Platform asset specifications	This feature introduces the ability to define properties related to an oil drilling platform on an asset's specifications.
000092	Publish indicator readings to an external system	This feature introduces the ability to publish indicator readings to an external system such as SAP or Maximo.
000091	Support for Oil and Gas asset specifications	This feature introduces support for asset properties related to the oil and gas industry.
000090	Support display of an indicator's measurement point values in a grid format	This feature introduces the ability to display an indicator reading's measurement point values in a grid format. The ability to compare the values for two readings is also supported
000089	Standard task due date data loader	This feature introduces a new Standard Task Due Date data loader. The data loader allows new due dates or proposed due date to be loaded for a standard tasks. The data loader is included as part of the Inspection Management data loaders on Enterprise.
000088	Maintenance action plan corrective task data loader	This feature introduces a new maintenance action plan inspection task data loader. The data loader allows corrective tasks and corrective solution packages to be loaded for maintenance action plans.
000087	Maintenance action plan inspection task data loader	This feature introduces a new maintenance action plan inspection task data loader. The data loader allows inspection tasks to be loaded for maintenance action plans.
000085	Asset prioritization and condition analyses data loaders	This feature introduces two new data loaders to the APM collection of data loaders: Asset prioritization analysis data loader and the asset condition analysis data loader. The asset prioritization analysis is part of the strategy development data loaders. The asset condition analysis is part of the asset health data loaders.
000084	Create checksheet from Interop work orders' and work requests' recommendations from events	This feature introduces the ability to create a checksheet based on the recommendations from event on both Interop work orders and work requests. Solution packages are not required to generate the checksheets. When the features is enabled, the Create Checksheet (From Template) action is available on a task template.
000083	Ability to create a checksheet from a Task Template	This feature introduces the ability to create a checksheet directly from a task template. When the features is enabled, the Create Checksheet (From Template) action is available on a task template
000082	Allow Interop Work Order and Interop Work Request to be manually set on a checksheet	This feature allows users to manually select the source Interop Work Order and Interop Work Request on a checksheet. The source Interop Work Order and Interop Work Request references are typically set when the checksheet is created from the work order or linked to a work request. This feature allows users to set the link in cases where it was not automatically set. For example, if a checksheet is manually created and is related to a work order, the link can be manually set.
000081	Data loaders for degradation rates	This feature introduces two new data loaders: Asset degradation rate data loader and Indicator degradation rate data loader.
000079	Data loader for Measurement Point readings	This feature introduces a new data loader for Measurement point readings.
000078	Approvals support for requests for work	This feature introduces support for approvals for Requests for Work. When the feature is enabled, standard APM approvals support is available for Requests for Work.
000077	Support for Interop work document change requests	Work document change requests are used to request changes to an Interop Work Order or Interop Work Request. A change request can request: An update to the document's work status. For example, request that an SAP Maintenance Order be updated to TECO (technical complete) when the work is completed Enter a new comment Record hours work Update a Recommendation for Event as completed Record the actual start and end dates for the work Request the planned start and end dates be updated Change requests can also request that any of the user flex fields be updated. The user flex fields consist of 10 string fields, 5 date fields, 5 check boxes, and 5 reference numbers. When a change request is entered, it is communicated to the CMMS via AssetWise Interoperability where it is processed. If the request is accepted, the CMMS work order or request is updated. The APM copy of the work order or request is updated when the Sync Document object is received from AssetWise Interoperability. The APM document is only updated after the request is accepted and processed by the CMMS Work Document Change Requests are only available when AssetWise Interoperability is being used.
000076	Support for asset links	This feature introduces the ability to link 1 to 5 assets to another asset. For example, in a electrical distribution network, the network protector and network switch can be linked to their transformer. The asset links can be manually maintained or automated using rules defined on the asset type.
000075	Support for user asset specifications	This feature provides the ability to extend an asset's information through the use of User Asset Specifications. User asset specifications include support for the following properties: 5 string attributes 5 check boxes 5 dates 5 decimal number Using the settings of class User Asset Specification Settings, you can identify which of the 20 properties are being used. You are able to provide a name for each property used. Settings on asset type allow you to identify if user asset specifications are used with assets of a type. You can identify the user asset specification settings to use. This allows different properties to be used with different types of assets. User asset specifications are also a convenient location for adding custom properties to asset.
000074	Support for type of inspection evaluation as part of the failure mode RBI analysis	This feature introduces a new step in the RBI Analysis process: the type of inspection analysis. Type of inspection analysis is performed after the confidence analysis. The results of the type of inspection can identify if an internal, external, in-service or out of service inspection is required.
000073	Support for circuit assets	Ability to link circuits and the assets on a circuit. A circuit can identify things like an electrical circuit or corrosion loop. When this feature is enabled, you can identify up to 10 circuits that include the asset. An unlimited number of assets can be included on a circuit. To enable circuit support, there are settings on the asset type. For each type of asset you can: Identify that assets of the type can be included on a circuit Identify that assets of the type are a circuit On assets included on a circuit, you can view the list of circuits that asset is a part of. For a circuit asset, the Circuits view is visible. On this view, you can see the circuit's assets and a variety of information about the circuit and its assets, including: Process description Degradation information Operating parameters Failure modes Barriers Indicators Standard tasks Solution packages if you are using AssetWise Interoperability Work orders The Circuits tab on the site's assets view shows you a list of all the circuits at a site. The same level of information is displayed for each circuit as on the asset's Circuits view. When the feature is enabled you can: View the indicators associated with the circuit's assets when browsing indicators. For example, when browsing for indicators to include on a standard tasks or maintenance action plan. you can view the indicators for the circuit's assets Include the circuit's assets when creating the assets for a strategy development analysis
000069	Ability to link checksheets and Interoperability work requests	This feature introduces the ability to link an Interop work order's checksheets to Interop work requests related to the work order. When the feature is enabled, the Checksheet and work request linking group box is included on the Checksheet Generation tab under the Checksheet settings the Inspection Management Settings. The settings in the group box are used to enable checksheet and work request linking. Work request and checksheet linking is only applicable when AssetWise Interoperability is being used.
000068	Support for follow-up requests for work	This feature introduces the ability to generate a request for work based on the completion of a interop work order or work request.
000065	Display asset properties on selected objects	This feature provides the ability to display a set of asset properties on the following objects: Checksheet Indicator reading Request for work When the feature is enabled, you are able to define at the asset type level on which objects you want asset properties displayed and the panel to use. An Asset Properties view (on checksheet) or page (Indicator Reading and Request for Work) is added to the user interface if the asset's asset type has enabled support for displaying asset properties.
000064	Ability to restrict the priorities used on a work request based on the maintenance group	This feature provides the ability to define the available work priorities based on the maintenance group assigned to a request for work. When the feature is enabled, a new Priorities tab is displayed on the Maintenance Group Properties. On the Priorities tab, available priorities are restricted to the priorities identified on the maintenance group. When creating a request for work, the priorities available for selection are limited to the priorities that are valid for the maintenance group. The ability to restrict priorities based on maintenance group is only available when AssetWise Interop Work Documents are being used.
000063	Ability to make the creation of the work document mandatory on an indicator reading	This feature introduces the ability to make the creation of a work document (request for work) mandatory based on the indicator state. This feature expands on the existing ability to create a work document as part of an indicator reading by making the creation of the work document mandatory. A new setting has been added to indicator state to make the work document mandatory. The ability to create a work document as part of an indicator reading is only available when using AssetWise Interoperability.
000062	Distribution Network work information on AssetWise Interoperability work documents	This feature extends the information supported on AssetWise Interoperability work documents. The information includes properties related to working on electrical equipment in an urban area. This includes: How was the work identified High public exposure Commercial or industrial customer Urban area Remote or low population density area High fire risk area A waterway Is a traffic plan required Is flagging required Is this a customer issue Is a underground safety alert required Is a city moratorium on work active Is this a urban wildlife area Is the work related to a substation Is the work related to a company or regulatory board audit Does the work require verification Distribution network information is available for entry on a request for work, when acknowledging an alarm, creating a work document as part of an indicator reading, follow up work requests and other places where work can be initiated in APM. The information is also visible on Interop work requests, Interop work orders and solution packages. This feature is generally available.
000061	Regulatory reporting tracking support on assets	This feature introduces the ability to track regulatory reporting information on assets When it is enabled, you can track up to three levels of regulatory information for an asset. For example, federal regulations, regional regulations, and industry organization requirements could be tracked. For each regulatory requirement being tracked you can: Identify the agency (Federal government, Regional government etc.) Define up to 10 check boxes. You are able to provide the text for each of the check boxes being used. For example, OHS Regulations, Federal environmental regulations, Provincial safety codes, and so on. A maximum of 100 characters can be entered to describe each check box Define up to 5 reporting dates. You are able to provide the name of each date being used. For example, last date reported on and next report due on could be the names for two of the dates Define up to 5 text attributes If regulatory reporting is supported, you can identify by the type of asset.
000060	Collector's note mandatory based on type of alarm and marking asset as unavailable for reading	Ability to make it mandatory to enter collector's notes on manually-entered indicator readings, based on the alarm type or if the asset is unavailable for reading. This feature is generally available.
000058	Notes support	Notes or asset notes allow notes to be added to a number of APM objects. See the list below. Each note consists of: A short description or title The note Time stamp information of when the note was entered and who entered it Optionally, a note can be reviewed. Reviewing a note allows a user to respond to the original note. The note type controls whether review is supported for a note. Depending on the source of the note, the note is also linked to related objects. As an example, a indicator reading note is also linked to the indicator and the checksheet the reading is on. Notes related to an asset-specific object are also linked to the asset. For example, a standard task note is linked to the standard task's asset. Notes are supported for the following types of objects: Asset Asset activity analysis Asset change request Asset health index Asset program profile Cable splice Check sheets Gas transaction Indicator, including indicator templates, KPIs and KPI templates Indicator readings Interop work order and work request Lab fluid sample Production loss event Request for work Safety override incident Standard tasks, including task templates
000057	Default approval route support	Ability to identify a default approval route to use when an approval request is created. Default approval routes can be identified for each type of document that supports approval. A default set of approval routes can be identified for both employees and site. When an approval request is created, the current employee is checked to see it a default route has been identified. If a default route has been identified, it is used. If an employee default has not been identified, the system checks for a site default. The site default, if identified, is used.
000056	Review or approval support for Asset Change Requests	This feature introduces the ability to implement the review or approval process for asset change requests. The review process is an informal process where a user with the appropriate security privileges can mark an asset change request as reviewed. The approval process is a formal process that uses APM approvals. When the approval process is used, asset change requests are submitted for approval. One or more approvers are required to approve the request before it can be sent to your asset registry system Asset change requests only apply when Bentley AssetWise Interoperability has been implemented. The objects associated with this functionality include: Asset change request Asset change request type Approval route Approval request
000055	Ability to request changes to asset properties outside of a construction form	Asset change requests were introduced as part of Construction Management. They are used to communicate information to the external CMMS that owns assets. The asset update is performed in the CMMS and the resulting asset update request is then communicated to APM. The purpose of the functionality is to support the ability to initiate a properties change outside of a construction form. As with asset change requests initiated from a construction form, the new asset change request is only used when AssetWise Interoperability is used. The request is communicated to your asset registry system (typically your CMMS). The asset registry system accepts the request and updates its records. An Asset Sync event is then sent to APM, resulting in the APM asset being updated. Asset change requests only apply when Bentley AssetWise Interoperability has been implemented. The objects associated with the new asset change request capability include: New asset change request Asset change request type Asset change request status Asset change request template Approval request
000054	Fluid condition tracking and results	This feature allows you to enable the APM Fluid Condition function. Fluid Condition allows you to export and import fluid samples to a Fluid Analysis Lab and record the results on a Fluid Condition checksheet. Enabling the feature allows you to: View the Fluid Analysis view on site and asset Define the values lists and settings that pertain to fluid condition Export fluid samples to either an internal or external fluid lab Import the results of the lab analysis into a fluid condition checksheet for review Monitor trends for the indicators used to track the fluid condition
000053	Fluid sample support	This feature allows you to enable the ability to record information pertaining to a fluid sample on an Indicator Reading. Enabling the feature allows you to: Identify on an indicator that the indicator is used for record fluid sample information Identify on an indicator state that a sample was taken and allows the sample values to be entered on the reading Enter fluid sample information on an indicator reading When the feature is disabled, the fluid sample properties on indicator type, indicator, indicator state and reading are hidden.
000052	Remove overrides from a task template's standard tasks	Support the ability to remove the overrides from Standard Tasks based on a Task Template. This feature introduces the ability to remove the overrides from a task template's standard tasks. Previously, it was necessary to open each standard task and remove its overrides. When this feature is enabled, it is now possible to remove the overrides from the task template itself. When performed, a list of the template's standard tasks with overrides is displayed. Select all or some of these standard tasks and click OK. The overrides are removed from the selected standard tasks. This feature is generally available.
000051	Support generation of checksheets for standard tasks without requiring a work order	Support the Generation of Checksheets for standard tasks This feature introduces the ability to generate checksheets from APM standard tasks without requiring the use of work orders. When this feature is enabled, you are able to identify that a standard task does not require a work order. The standard tasks checksheets can be generated directly from the standard task. The standard task must be configured to track its due date. The task due date can be based on its frequency or indicators due dates. A new scheduled action is used to generate the checksheets on a recurring basis. This functionality is used to support Operator Care Rounds or Operator Inspections. This feature is generally available.
000050	Support ability to limit the duration that is scheduled for a work order task	Support the ability to limit the duration scheduled per shift for a work order task This feature allows you to set a limit to the amount of time allocated to each shift when the work is scheduled. As described by the customer who submitted the request: I would like to see an enhancement made to the system so that a work task can be flagged or limited so that it will only schedule a portion of the hours for a shift and if possible, it would schedule it on consecutive days for the same number of hours until the hour requirement is met. What I would like to see it a way to make a weekly work order task (PM) that can be used for each day of the week but limit its hours for each day. For example, if you had a work order that required 15 hours per week, but you need to spread that out based on 3 hours per day on Monday through Friday without creating 5 separate tasks for 3 hours each. I have seen this done in other systems using the duration field to calculate this out. It had the option (a check-box was available when this option was desired) to manually enter a duration (rather than auto calculate) after the number of craftsmen and hours were entered on the order. If you stated that you needed 15 hours of work scheduled over a duration of 40 hours (settings for the day are 8 hours per day), then when you schedule that work order it would break it up into 5 consecutive days with 3 hours per day scheduled for that order. When the feature is enabled, you are able to identify that the work is to be limited to a set duration when it is scheduled. The scheduling limit can be defined on a standard task and is copied to the work order task. The limits can also be defined directly on the work order task. This feature is generally available.
000049	Link an acknowledgment to a work document with AssetWise Interoperability	This feature allows you to acknowledge an indicator alarm by referencing an existing Request for Work, Interop Work Request, or Interop Work Order. When an alarm is acknowledged with an existing work document, a new Request for Work is not created. No information is passed to the CMMS. The link to the existing work document remains known to APM only. It is assumed the user knows that the scope of the existing work addresses the new alarm. When the feature is enabled, you are able to identify that an alarm is being acknowledged with an existing work document. The existing work document must be identified. When the feature is disabled, alarms can only be acknowledged with a new Request for Work.
000048	Support for user defined fields on AssetWise Interoperability Work Documents	Support for user-defined fields with AssetWise Interoperability This feature allows you to extend the information on the Interop work documents to include a number of user fields. The user fields consist of: 10 string attributes named User String 1, User String 2, User String 3, User String 4, User String 5, User String 6, User String 7, User String 8, User String 9, and User String 10 5 date attributes named User Date 1, User Date 2,User Date 3,User Date 4, and User Date 5 5 check box (Booleans) named User Check Box 1, User Check Box 2, User Check Box 3, User Check Box 4, and User Check Box 5 When the feature is enabled, you are able to identify the user fields to be used and name each of the used fields. Additionally you are able to identify if any of the used fields are mandatory or read only by work type and site. User fields are supported on Interop work order, Interop work requests, solution packages, and requests for work. This includes all places where a request for work can be initiated, such as an alarm acknowledgment or follow up work request. When the feature is disabled, the user fields cannot be used. This feature is generally available.
000046	Failure codes support with AssetWise Interoperability	Support for additional failure codes with AssetWise Interoperability This feature allows you to define the failure codes used on Interop work documents and failures. Enabling the feature allows you to: Use object part, damage and activity codes Use up to five flexible failure codes. When the failure codes are being used, you are able to identify the number of failure codes are used (1, 2, 3, 4, or 5),name each of the codes and identify which codes are mandatory on a work document Turn off failure codes When the feature is disabled, Object part, damage codes and activity codes are used. This feature is generally available.
000042	Support for critical parts identification on a maintenance action plan	Critical Parts Analysis on a Maintenance Action Plan This feature provides the ability to identify the critical parts, or spares, required for a failure mode's action plans. The feature includes: The ability to define a catalog of critical parts The ability to identify the critical parts for a failure mode's action plans. The critical part can be identified by selecting the critical part from the critical parts catalog, a material resource form the resource catalog or by identifying the part directly on the action plan critical part record A list of all the parts required for an analysis as part of the Analysis Summary view Critical parts can be identified on all types of strategy development analyses, including templates. This feature is generally available.
000039	Criteria based probability evaluation on an asset prioritization analysis	Criteria-based probability of failure evaluation as part of an asset prioritization analysis Provides the ability to assess the probability of failure for an asset based on multiple criteria when performing an asset prioritization analysis. The feature includes: Ability to identify the method used to analyze the probability of failure. The two supported methods are selecting the probability of failure from a list of probabilities or performing a formal analysis Ability to identify multiple criteria that are used to assess probability of failure Ability to identify multiple details for each probability of failure criterion Ability to identify the selection policy for the probability of failure Ability to analyze probability of failure as part of the asset's prioritization analysis When this feature is enabled, you are able to identify the method used to analyze the probability of failure. The two supported methods are by selecting the probability of failure from a list of probabilities or performing a formal analysis. If the feature is not enabled, only the simple method is available. This feature is generally available.
000036	Updating existing data to be ready for use with AssetWise Interoperability	Updating data to be ready for AssetWise Interoperability Before implementing AssetWise Interoperability, it is necessary to update existing data objects to be ready for use. This is done by creating and processing AssetWise Data Readiness Requests. One or more AssetWise Data Readiness Requests are required for each type of object for which you have existing data that needs to be updated. Refer to the product implementation guides for more information. When this feature is enabled, you are able to create instances of AssetWise Data Readiness Requests from the Data Readiness Requests tab on the Interoperability Settings tab on the Enterprise's Integrations view. When the feature is disabled, the Data Readiness Requests tab is hidden. This feature is generally available.
000034	Advanced production loss accounting	Advanced production loss accounting Provides additional functionality related to production loss accounting: Ability to identify multiple products per asset Ability to link production loss equations to a specific product Support for Production Loss Events When this feature is enabled, you are able to identify the production loss accounting level as basic or advanced for each site. Basic production loss accounting is based on downtime incidents and a single product per asset. Advanced production loss accounting enables the new functionality. The production loss accounting level is identified on the site's production view settings. This feature is generally available.
000033	Hierarchy recursion support for exports	Hierarchy Recursion Support on Reports This feature enables the ability to define reports with hierarchy recursion support, for example, a list of Requests for Work for an asset and its descendants or a list of Requests for Work for a site and its ancestors. This feature is generally available.
000032	Integration with 4D Analytics	This feature enables the ability to integrate APM with 4D Analytics system. The 4D Analytics integration allows you to view the readings history for an indicator where the readings are stored in the 4D Analytics system. Currently, 4D Analytics integration is only available if you are using SQL Server DBMS. 4D Analytics does not work with a Oracle DBMS.
000028	Asset change requests	Asset Change Requests Asset change requests are used to communicate information to the external CMMS that owns assets. The asset update is performed in the CMMS and the resulting asset update request is then communicated to APM. Asset change requests only apply when Bentley AssetWise Interoperability has been implemented. Three types of asset change requests are supported: Property changes - Used to request a new asset or property updates to existing assets. This type of asset change request is currently only initiated from a construction form Asset status change - Used to request a change to an asset's status. Asset status change requests are currently only initiated from a work order's asset inspection status Remove equipment request - Used to request that an asset be removed from its current location and move to another location The objects associated with asset change requests include: Asset change request Asset change request type Asset change request status This feature is generally available.
000027	Asset program profile	Asset Program Profiles This feature consists of a set of new objects that are used to generate reliability and inspection programs for assets. The objects associated with asset program profiles include: Asset program profiles - used to group a set of asset program profile details and processing rules Asset program profile details - filters used to identify the assets that the rules apply to, the inspection and reliability templates used to create the assets' objects, and the standard documents to assign to assets Generate Asset Program scheduled action - automatically updates the site's assets at predetermined intervals Asset program profiles can be created from the Assets view, Program Profiles tab. Asset programs can be manually generated from assets, asset program profiles, and the site. The features does not control the availability of the asset program profile functionality in the context of construction forms. This feature is generally available.
000024	Allowing work orders with multiple assets to be sent to SAP	Allow work orders with multiple assets to be sent to SAP This feature allows work orders with tasks for different assets to be sent to SAP. Otherwise, only work orders where all of the tasks are for the same asset can be sent to SAP. When enabled, work orders with tasks for different assets can be sent to SAP. If the feature is enabled, the base product transform that converts the APM work order to a SAP maintenance order does not communicate the different assets to SAP. Only the primary task asset is sent to SAP. It is your responsibility to update the transform. This feature is generally available.
000023	Asset characteristics	Asset Characteristics Support This feature consists of a set of objects that are used to import asset characteristics from an external CMMS (e.g. SAP). Once imported, the characteristic values can be mapped to asset properties, enabling standard system functions like: Ability to view the value on an Asset properties tab like the other asset properties Ability to include the property as a column on an asset configuration. This allows all of the standard configuration functions to be used, including: Filtering, including filter sets which use more than 1 characteristic value Sorting Grouping Counts Using the property as an input for a calculated indicator or KPI The objects associated with asset characteristics include: Characteristic class - used to group a set of characteristics Characteristic - a specific characteristic that is tracked Asset characteristic - the value for a characteristic for a specific asset Characteristic mapping set - used to define the rules for mapping data between asset characteristics and asset properties Data loaders for characteristics and asset characteristics - in the absence of an automated interface, data loaders can be used to import characteristic values This feature is generally available.
000022	Construction management	Construction Management This feature consists of a set of new objects that are used to manage equipment construction activities performed by field crews at your facilities. The objects associated with construction management include: Construction forms - used to identify the equipment installed as part of a construction job. The equipment can be existing equipment that is being installed at a new location or new assets Construction form templates - used to identify the content, rules and behavior of the construction form Construction management is a view on both site and asset. This feature is generally available.
000021	Regulated gas management	Regulated Gas Management This feature consists of a set of new objects that are used to manage regulated gases at your facilities. For example, you can manage activities related to sulfur hexafluoride (SF6), which is a highly regulated gas in some jurisdictions. When enabled, the feature can be used to track all activities for a type of gas. The objects associated with regulated gas management include: Gas type - used to identify a regulated gas being tracked Gas container - identifies the different types of containers (cylinders, bottles, etc.) the gas is stored in Gas vendor - identifies the vendors from whom the gas is purchased. Includes the ability to link the gas vendor to a purchasing supplier Gas transaction type - used to identify the different types of transactions performed for the gas and the characteristics and behavior of each Gas transaction - used to track all activities related to a regulated gas includes receipts and returns to vendors, equipment fills, container weights and loss to atmosphere events Regulated gas management is a view on both site and asset. This feature is generally available.
000017	Data loader for user site security profiles	This feature consists of a new data loader for User Site Security Profiles. When enabled, this feature can be accessed from the Data Loaders view on Enterprise under the Personnel tab.
000009	Time zones by site	Time Zones by Site This feature allows you to have a different time zone for each of your sites. Currently, all sites must use the Enterprise time, whether they are in the same time zone or not. When a different time zone is specified for a site, all date and time data will be displayed using the time zone selected. As always, all date and time data will continue to be stored on the database in Coordinated Universal Time format (UTC). When enabled, the time zone for a site can be set via its Properties dialog. This feature is generally available.