---
sourceDocument: Zurich Enterprise Architecture (formerly Application Portfolio Management)
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/application-portfolio-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Enterprise Architecture (formerly Application Portfolio Management)

ft:clusterId :

    - appportman

bundleId :

    - appportman

workflow :

    - Technology


---

# Performance Analytics indicators for applications

# Performance Analytics indicators for applications {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Performance Analytics indicators for applications

Performance Analytics (PA) indicators help ServiceNow customers monitor the counts of incidents, problems, changes, and closed change requests related to business applications.
This insight supports improving application performance by providing measurable data collected and analyzed through Enterprise Architecture.
Show full answer Show less  

## Key Features

* **Indicator Data Collection:** PA indicators collect data on incidents, problems, changes, and change requests both daily and historically.
* **Scheduled Job Execution Order:** To generate accurate application performance scores, run the PA jobs in this order:
  1. \[PA Incident\] Daily Data Collection
  2. \[PA Change\] Daily Data Collection
  3. \[PA Problem\] Daily Data Collection
  4. \[Enterprise Architecture Scheduled job\] Load Application Indicators and compute Application Scores
* **Historic Data Collection:** For data older than six months, Performance Analytics Premium is required. Historic jobs must be run in the same order as daily jobs, followed by regenerating Enterprise Architecture scores to replace existing data.
* **Indicator Score Frequency:** Scores are generated according to indicator frequency:
  * Monthly scores on the last day of the month
  * Quarterly scores on the last day of the quarter
  * Yearly scores on the last day of the year

  Fiscal periods must align with the timezone of score generation.
* **Data Frequency Alignment:** Enterprise Architecture indicators must have a frequency equal to or greater than the data source indicators. For example:
  * Monthly Enterprise Architecture indicators collect from Monthly data sources
  * Quarterly indicators collect from Monthly and Quarterly data sources
  * Yearly indicators collect from Monthly, Quarterly, and Yearly data sources
* **Release Update Note:** In the Zurich release, daily frequency for PA data source indicators is removed and replaced with Monthly frequency automatically by a fix script.
* **System Property Limits:** When many business applications exist, the number of breakdown elements shown in PA scoresheets may be limited by system properties. Customers can adjust these limits under Performance Analytics \> System \> Properties by increasing:
  * Maximum number of elements of a breakdown in Scoresheet
  * Maximum number of breakdown elements in scorecard lists

## Practical Benefits

* Enables continuous monitoring of application-related incidents, problems, and changes to identify performance issues.
* Facilitates data-driven decision-making with scheduled and historical analytics.
* Supports customization to handle large environments by increasing breakdown display limits.
* Ensures consistent timing and frequency of data collection aligning with business fiscal periods.  
Use performance analytic (PA) indicators to know the count of incidents, problems, and
changes logged against a business application and use this insight to improve the performance of
your applications.

Enterprise Architecture uses indicators that are sourced from Performance Analytics (PA). These indicators give a count of incidents, problems, changes, and the number of change requests that
were closed on a given day. Follow the given order to run the PA jobs at the scheduled time, and get the scores of the indicators to evaluate the performance of your business applications.

## Order in which to run PA jobs and generate scores {#pa-indicators-jobs__section_dvb_2qd_5gb}

You should run the scheduled jobs in the following order:

1. \[PA Incident\] Daily Data Collection.
2. \[PA Change\] Daily Data Collection.
3. \[PA Problem\] Daily Data Collection.
4. \[Enterprise Architecture Scheduled job\] Load Application Indicators and compute Application Scores.

{#pa-indicators-jobs__ol_t5s_vqd_5gb}

If there are historic data, then run them in the following order:  
Note:  
You require Performance Analytics Premium for Enterprise Architecture (com.snc.pa.premium.apm) plugin to retrieve historic data that are older than six months.

1. \[PA Incident\] Historic Data Collection.
2. \[PA Change\] Historic Data Collection.
3. \[PA Problem\] Historic Data Collection.
4. Regenerate Enterprise Architecture scores for required time period. This action deletes the existing scores including daily scores and generates new scores instead of just updating the existing scores.
{#pa-indicators-jobs__ol_kps_vsd_5gb}

## Frequency at which indicator scores are generated {#pa-indicators-jobs__section_tjt_j4d_5gb}

Scores are generated as per the scheduled run of the job that executes the script. If the
indicator frequency is:

Monthly
:   scores are generated only on the last day of a month.

Quarter
:   scores are generated only on the last day of a quarter.

Yearly
: scores are generated only on the last day of a year.  
Note:  
Fiscal periods should be generated in the same time zone in which the scores are generated.

## Collection of PA indicator score data {#pa-indicators-jobs__CollectionPAIndicators}

The period unit (days, weeks, or month) at which the PA indicator scores are collected and
preserved depends on the frequency of the data source indicator. However, the frequency at which
the application indicator collects the PA indicator data source scores varies.

In Enterprise Architecture, the frequency of the application indicator must be greater than or equal to the frequency of the data source indicator.

The following table describes the frequency at which Enterprise Architecture collects data from the data source indicators after the job runs:
{#pa-indicators-jobs__table_fsq_f5d_1lb__entry__2}

| Enterprise Architecture frequency | Data source indicator frequency |
|-|-|
| Monthly | Monthly |
| Quarterly | Monthly and Quarterly |
| Yearly | Monthly, Quarterly, and Yearly |
[Table 1. APM data collection frequency]

{#pa-indicators-jobs__table_fsq_f5d_1lb}

If you are an Enterprise Architecture customer, who has upgraded to the Zurich release, then the Daily frequency of Performance Analytics data source indicator is not available. RemoveDailyFreqAndUpdatePAIndicator fix script
automatically removes the Daily frequency of PA indicators and updates the frequency to Monthly.

## Limitations to display application breakdowns in PA scoresheet {#pa-indicators-jobs__section_ac2_sbl_5gb}

If there is a large number of business applications installed, then all the breakdowns are not
displayed in the Performance AnalyticsScoresheet, as there is a limitation set in the system properties:
com.snc.pa.scoresheet.max_elements and
com.snc.pa.scorecards.max_breakdown_elements. To reconfigure the property
limitation:

1. Navigate to Performance AnalyticsSystemProperties.
2. Enter the maximum number in the Maximum number of elements of a breakdown in Scoresheet field. The number must be greater than or equal to the number of business applications installed in your system.  
3. Enter the maximum number in the Maximum number of breakdown elements in scorecard lists field.
4. Click Save.
{#pa-indicators-jobs__ol_cnc_gdl_5gb}

*[\>]: and then