Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
Asset Reliability | AssetWise APM
  • Product Communities
  • AssetWise
  • Asset Reliability | AssetWise APM
  • Cancel
Asset Reliability | AssetWise APM
Asset Reliability | AssetWise APM Wiki How to create a KPI to monitor a Scheduled Action
    • Sign In
    Asset Reliability | AssetWise APM requires membership for participation - click to join

     
     Questions about this article, topic, or product? Click here. 

    How to create a KPI to monitor a Scheduled Action

      Product(s): AssetWise APM Foundation
      Version(s): 07.05.00.55
      Environment: N\A
      Area: KPI
      Subarea: Scheduled Action

    Problem

    It is difficult to know if a scheduled action is running.

    Solution

    To determine if a scheduled action has been executed, the execution history of the scheduled action can be viewed:

     

    In this case, we will create a KPI to look at the execution history to see if the method has been executed in the past 24 hours. I am assuming in this case, the method should be executed at least once in a 24 hours period.

     Create a KPI, provide a name and use a numeric indicator type such as a ‘Count’

     

    On the calculation tab, select new Filter input:

     

    Provide a name to the input such as ‘NumberOfActionSchHistory’ and select ‘Scheduled action execution history’ in the list of object to select. The ‘scheduled action execution history’ is the record of when the method is executed.

     

    then click the ‘Regular Filter’ to add filters when counting these records.

     

    Now define the filter you wish to use. In this case, the created on date must be in the last 24 hours.

      

    If a specific scheduled action is wanted rather than all scheduled actions, add another filter providing the schedule method as a filter.

     

    Click the   for the join path. Expand and select the join path as show below and click ok.

     

    The input should look like this now:

     

    Now select the attribute to filter by as ‘Tooltip’. Complete the condition and value. Such as:

     

    Tooltip refers to the scheduled name shown on the list of scheduled actions on enterprise here:

     

    Once all the filter criteria are defined, add the input name into the calculation section of the indicator:

     

    Next is to setup a frequency when this should be executed. In this case, the filter is ‘in the last 24 hours’, so it would make sense to have this calculated every 24 hours. Here is an example where the calculation will be performed daily at 12:30AM each day.

     This KPI will count the number of time the scheduled actions are executed. So if the number of greater than zero that means the scheduled action executed within your time filter. If there is a wish to notify a user the value calculated is zero (meaning the scheduled action has not executed in your timeline), use the states on the KPI.

    Here are the states showing anything 1 or greater is normal, and anything else is alarmed.

    On the alarmed state, the type of notification can be selected. This is where the employees are selected to be notified. The email on the employee is used when this alarm is raised.

     

    An email will be sent to the users indicating the KPI is in alarm and requires attention.

     

    Email Title: 

    A(n) Warning alarm has been raised on the Scheduled Actions - Not performed in the past 24 hours indicator of asset 2 (Enterprise).

    Email Body:

    A(n) Warning alarm has been raised on the Scheduled Actions - Not performed in the past 24 hours indicator of asset 2 (Enterprise).

    The alarm was raised because a reading of 0.00 each was entered by  on Thursday, October 6, 2016 1:36:11 PM.

    A(n) Warning alarm on indicator Scheduled Actions - Not performed in the past 24 hours is defined as any value between  and 0.99 each.

    When this alarm occurs, the user should then go into APM and acknowledge the alarm with ‘Fixed during Inspection’ to ensure future emails are sent. The system suppresses sending duplicate messages for the same problem. So if the problem occurs several days in a row, the alarm was already sent and only 1 email will be sent. Once the alarm is acknowledged, future alarms will be sent.


      Original Author: Diana Drummond
    • AssetWise APM
    • Assetwise APM Foundation
    • 07.05.00.55
    • en
    • SELECTsupport
    • Share
    • History
    • More
    • Cancel
    • Diana Marin Created by Bentley Colleague Diana Marin
    • When: Tue, Oct 18 2016 11:49 AM
    • Diana Marin Last revision by Bentley Colleague Diana Marin
    • When: Tue, Oct 18 2016 1:38 PM
    • Revisions: 5
    • Comments: 0
    Recommended
    Related
    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies