Application indicator score calculation in Enterprise Architecture Workspace

  • Release version: Australia
  • Updated May 20, 2026
  • 5 minutes to read
  • Summarize
    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 Application indicator score calculation in Enterprise Architecture Workspace

    Enterprise Architecture Workspace calculates a composite score for each business application and business capability by processing configured indicators through a standardized scoring pipeline. This pipeline normalizes raw data, applies weighted contributions, and aggregates results into a final score for each fiscal period. Scores are stored historically, enabling comparison over time and across different data types such as assessments, operational metrics, and custom scripts.

    Show full answer Show less

    This scoring model allows ServiceNow customers to meaningfully evaluate and compare applications and capabilities using a consistent, weighted approach controlled by administrators.

    Key Features

    • Indicators: Metrics representing aspects of applications or capabilities. They can be subjective (e.g., assessment responses) or objective (e.g., incident counts).
    • Scoring Profiles: Groups of indicators assigned to applications or capabilities, with configurable weights determining each indicator's impact on the final score.
    • Data Sources: Indicators collect raw weights from Performance Analytics, custom scripts, database queries, assessments, or composite parent indicators aggregating child values.
    • Normalization: Converts raw values to a 1–10 scale for comparability, where 10 always reflects the best performance. Direction settings control whether higher or lower raw values score better.
    • Indicator Scoring: Calculates each indicator's contribution proportionally to its weight within the profile, enabling a precise composite application score.
    • Business Capability Scoring: Applies the same process to leaf capabilities, with parent capability scores rolled up as averages of their children’s scores, supporting hierarchical analysis.
    • Score Storage: Scores are stored in dedicated tables per application or capability per fiscal period, preserving historical data for trend analysis.
    • Visualization: Capability heat maps use color thresholds to represent score gaps, customizable per widget to highlight risk or performance areas visually.

    Practical Application for ServiceNow Customers

    By configuring indicators and scoring profiles, customers can tailor scoring to their organization's priorities, enabling objective assessment and rationalization of business applications and capabilities. The normalized and weighted scores facilitate decision-making around application investments, risk management, and capability improvements.

    Administrators can regenerate scores on demand to keep data current, and leverage related functionality such as managing indicators and scoring profiles directly within Enterprise Architecture Workspace.

    The integration with ServiceNow’s Common Service Data Model (CSDM) and Performance Analytics ensures scores are based on reliable, contextual data, supporting enterprise-wide architecture governance and optimization initiatives.

    Enterprise Architecture Workspace calculates a composite score for each business application and business capability by running data from configured indicators through a multi-step pipeline that normalizes raw values, applies weighted contributions, and aggregates the results into a final score per fiscal period.

    Scoring pipeline overview

    An indicator is a single metric or measure of a particular aspect of a business application or business capability. Indicators can be subjective, such as assessment responses, or objective, such as operational or risk data from the CSDM service graph — for example, the number of incidents linked to an application.

    By running indicators through a consistent scoring pipeline, Enterprise Architecture Workspace confirms that applications assessed on different data types—such as assessment responses, change counts, or custom script outputs—can be compared meaningfully on a single score. Scores are stored per application per fiscal period, so historical data is preserved across scoring runs.

    Administrators control which indicators contribute to a profile, how they are weighted, and whether fixed or dynamic value ranges are used during normalization.

    Key tables

    Table 1. Key tables for indicator score calculation
    Table Label Role
    apm_application_profile Scoring Profile Groups indicators together. One profile is assigned to each business application.
    apm_application_profile_indicator Profile Indicator Maps an indicator to a profile and stores the weight value for that profile.
    apm_metric Indicator Defines the data source, direction, and normalization settings for each indicator.
    apm_app_indicator_score Indicator Score Stores the per-indicator, per-application, per-fiscal-period score after the pipeline runs.
    apm_app_score Application Score Stores the final aggregated score per application per fiscal period.

    Raw weight collection by indicator type

    Each indicator has a data source that determines how the raw weight is collected for each business application.

    Indicator type Data source value How the raw weight is collected
    Performance Analytics pa Pulls a value from the configured Platform Analytics indicator for the fiscal period. The breakdown must target the same CI class as the profile (for example, Business Application).
    Custom script script Executes the script defined on the indicator. The script must return a JSON object that contains the application sys_id and the corresponding weight.
    Query condition condition Runs a GlideAggregate query on the configured table and filter, then aggregates results using the selected method: SUM, COUNT, AVERAGE, MIN, or MAX.
    Assessment assessment Aggregates assessment metric results for the fiscal period across all assessment groups that are associated with the application.
    Composite (parent indicator) indicators Sums the normalized values of all child indicators for each application. Only the parent indicator's weightage is counted in the profile score.

    Normalization

    After the raw weight is collected for each application, the system normalizes the value to a 1–10 scale so that indicators using different units and ranges can be combined meaningfully. Regardless of direction, a normalized value of 10 always represents the best-performing application for that indicator, and 1 represents the worst. The Direction setting controls how the raw value maps to this scale.

    Condition Formula
    All applications have the same raw weight (max equals min)
    normalizedValue = 10
    Direction = Maximize (the application with the highest raw value scores 10; the application with the lowest raw value scores 1; for example, Business Valu)
    normalizedValue =
      (((appWeight − minWeight) /
        (maxWeight − minWeight)) × 9) + 1
    Direction = Minimize (the application with the lowest raw value scores 10; the application with the highest raw value scores 1; for example, Incident Count)
    normalizedValue =
      10 − (((appWeight − minWeight) /
              (maxWeight − minWeight)) × 9)
    In the formulas:
    • appWeight is the raw value for this application.
    • minWeight and maxWeight are the lowest and highest raw values across all applications for this indicator in the fiscal period. If Consider absolute values is selected on the indicator, the system uses the Target minimum and Target maximum values from the indicator record instead.
    Note:
    Assessment-type indicators don't support Target maximum and Target minimum fields. The system uses 1 as the minimum and 10 as the maximum automatically for assessments.

    If a Normalization script is defined on the indicator record, it overrides the standard formulas preceding.

    Indicator score

    The indicator score represents the contribution of one indicator to the overall application score, proportional to its weightage in the profile.

    indicatorScore =
      normalizedValue × indicatorWeightage / totalProfileWeightage

    totalProfileWeightage is the sum of weightage values across all indicators in the same scoring profile. All values are rounded to two decimal places.

    Assessment-based indicator example

    This example shows how an indicator score is calculated for a single business application using an assessment-based indicator in one fiscal period.

    Setup: A scoring profile has three indicators, each with a weightage of 33 (total profile weightage = 99). One indicator is a Business Fit assessment indicator. Two assessment groups fall within the fiscal period for this application.

    Calculation step Value How it is calculated
    Assessment group 1 — average rating 4.7 SUM of metric results for the application ÷ number of results in the assessment group.
    Assessment group 1 — application weight 9.46 (scaleFactor × rating) + 1, where scaleFactor = 9 ÷ 5 = 1.80. Result: (1.80 × 4.7) + 1.
    Assessment group 2 — average rating 4.5 Calculated the same way as assessment group 1.
    Assessment group 2 — application weight 9.10 (1.80 × 4.5) + 1.
    Normalized value 9.28 Total application weight ÷ number of assessment groups: (9.46 + 9.10) ÷ 2.
    Indicator weightage 33 Configured on the profile indicator record.
    Total profile weightage 99 33 + 33 + 33 (sum of all indicator weightages in the profile).
    Indicator score 3.09 9.28 × 33 / 99, rounded to two decimal places.

    The overall application score is the sum of all indicator scores where Use in app score calc is selected. If all three indicators in this profile each returned a score of 3.09, the application score would be 9.27.

    Business capability score calculation

    Business capability scoring uses the same indicator and profile infrastructure as application scoring. The key difference is that scores are calculated directly only for leaf capabilities (capabilities with no children), and parent scores are derived by roll-up.

    Aspect Behavior
    Which capabilities are scored directly Leaf capabilities only (leaf_node = true). The indicator pipeline runs against leaf nodes the same way it runs against business applications.
    Parent score roll-up Each parent capability score is the arithmetic mean of its direct children's scores. Capabilities with a score of –1 (not assessed) are excluded from the mean.
    Indicator-level roll-up Individual indicator scores — such as People, Process, and Technology — are also averaged across children at each level of the hierarchy.
    Score storage Stored in the Application Score [apm_app_score] table, the same table as application scores. The profile uses ci_class = cmdb_ci_business_capability.

    Capability heat map color thresholds

    The capability heat map translates numeric scores into color-coded gap ratings. The default thresholds are as follows.

    Score range Color Interpretation
    7 to 10 Green No gap
    4 to less than 7 Orange Medium gap
    0 to less than 4 Red Major gap
    –1 or empty Gray Not assessed
    Note:
    The No gap threshold and Mid gap threshold values are configurable per widget in the Capability map widget instance [apm_capability_map_instance] table.