Use case: How indicator scores appear on the bubble chart

Understand how application indicator scores are calculated and displayed as bubbles on the Application Rationalization bubble chart.

Scenario

Acme Corp's enterprise architecture team wants to rationalize its application portfolio using the TIME framework — a model developed by Gartner that classifies applications into four disposition categories:

• Tolerate — keep the application running for now, but do not invest further.
• Invest — actively develop and grow the application.
• Migrate — move the workload to a better alternative platform or application.
• Eliminate — retire or decommission the application.

In EA Workspace, these dispositions surface as Sustain (Tolerate/Invest), Migrate, and Retire (Eliminate) labels on the bubble chart quadrants.

Acme Corp evaluates five business applications on two dimensions:

• Business Value — how much value the application delivers to the business, gathered from stakeholder surveys.
• Technical Risk — how much technical risk the application carries, gathered from stakeholder surveys.

The bubble chart in EA Workspace plots these two dimensions on the X and Y axes, letting architects visually identify rationalization decisions.

Note:

The bubble color reflects the planned disposition set for each application. The legend at the bottom of the chart shows what each color means. The bubble color settings cannot be modified.

What is a scoring profile?

A scoring profile (apm_application_profile) is the central configuration object that defines how business applications are evaluated. It acts as the bridge between your indicators and your applications.

Note:

The sn_apm_ws.app_indicator_scoring_profile system property accepts only a single sys_id. Comma-separated values are not supported. If you enter multiple values, the bubble chart falls back to the Default Application Profile and ignores your custom profile.

Step 1: Set up indicators

As an EA admin user, navigate to Workspaces > Enterprise Architecture Workspace > Setup > Indicators and confirm that two default indicators are active:

Table 1. Indicator configuration

Indicator	Data source	Direction	Frequency
Business Value	Assessment	Maximize	Quarter
Technical Risk	Assessment	Minimize	Quarter

Business Value uses Maximize because a higher score is better. Technical Risk uses Minimize because a higher risk score is worse — the system inverts the normalized value so that riskier applications appear lower on the chart axis.

Note:

No new indicators need to be created for this use case. Both are available by default in the Default Application Profile. For information on how to create custom indicators, see Add or edit an application indicator.

How Minimize Direction Affects Chart Position

For Minimize-direction indicators, the score is inverted before being plotted. A raw score of 0 (zero risk) results in a normalized value of 1.0, which after inversion is set to 10.0 — the highest position on the axis. A raw score at the maximum (highest risk) inverts to 1.0 — the lowest position. The value 10 on the Y-axis means least risky, and 1 means most risky, for a Minimize indicator.

Maximize direction (Business Value)	Minimize direction (Technical Risk)
Higher raw score → higher normalized value → higher position on axis. A Business Value raw score of 85 normalizes to 10.0 — the top of the axis.	Higher raw score = worse condition. The system inverts the normalized value. A Technical Risk raw score of 90 (most risky) normalizes to 10.0 first, then inverts to 1.0 — the bottom of the axis
Formula: Normalized Value = (((raw - min) / (max - min)) × 9) + 1	Formula: Adjusted = (10 - Normalized Value) + 1 ← inversion step
Raw = 0 → Normalized = 1.0 (lowest on chart) Raw = max → Normalized = 10.0 (highest on chart)	Raw = 0 → Normalized = 1.0 → Inverted = 10.0 (highest on chart — zero risk is best!) Raw = max → Normalized = 10.0 → Inverted = 1.0 (lowest on chart — maximum risk is worst)

Indicator data sources

This use case uses Assessments as the data source, but EA Workspace supports five data source types. The choice of data source depends on what data is available and how frequently it is updated:

Data source	How it works	Example indicators	Best used for
Assessments	Survey-based ratings collected from stakeholders via the Service Portal. Assessors rate each application on a defined scale.	Business Value, Technical Risk, and Functional Fit	This use case
Performance Analytics (PA)	Scorecard data from an existing PA indicator (For example: incident count, change volume). Automatically sourced — no manual surveys are needed.	Number of Incidents via Service and Number of Changes via Service	Operational health indicators
Custom Script	A script that returns a per-application weight. Useful for complex calculations or external data lookups.	Portfolio TCO and Overall Score	Financial and composite indicators
Query Condition	A configurable table query (For example: count open vulnerabilities per app). No code required.	Usage (active users)	Simple count-based indicators
Indicators	Aggregates scores from child indicators into a parent indicator score.	Application Operational Metrics, and Business impact	Roll-up and composite scoring

Note:

Indicators from different data source types can coexist in the same scoring profile. For example, a profile might combine an Assessments indicator (Business Value), a Performance Analytics indicator (Number of Incidents), and a Custom Script indicator (Portfolio TCO). Each indicator type feeds into the same normalization and scoring pipeline regardless of its data source.

Applications Not Assessed — Visibility on the chart

If a business application has not been assessed for one or both axis indicators for the selected fiscal period, it will not appear on the bubble chart. A bubble requires indicator scores for both the X-axis and Y-axis indicator for the same fiscal period.

Applications with scores for only one axis are silently excluded. This applies regardless of data source type — an application that was not included in a PA breakdown, not assessed in a survey, or not returned by a custom script will have no score record and therefore no bubble is displayed.

To identify applications that are scored on one axis but not the other:

• Navigate to apm_app_indicator_score.list
• Filter by fiscal period = the period shown on the chart Filter by indicator = your X-axis indicator
• Compare the configuration item list to the same filter for your Y-axis indicator

Applications missing from either list will not render a bubble.

Note:

When an application is newly added to the portfolio after assessments have been generated, its assessment questions are not automatically included in existing assessment instances. You must regenerate assessments from the indicator's record to include new applications in the next assessment cycle.

Step 2: Set up the scoring profile

As an admin, navigate to Workspaces > Enterprise Architecture Workspace > Setup > Scoring Profiles > Default Application Profile and confirm that both indicators are listed in the Profile Indicators related list with the following weights:

Table 2. Scoring profile — indicator weights

Indicator	Weight
Business Value	50
Technical Risk	50

Equal weights mean each indicator contributes equally to the overall application score. Verify that all five business applications have their Application scoring profile field set to Default Application Profile. For information on how to attach profile indicators to a scoring profile, see Attach a profile indicator with an application scoring profile.

Step 3: Add indicators to the bubble chart table

Navigate to the Application Bubble Chart [apm_bubble_chart] table and confirm that both Business Value and Technical Risk are registered. The available X and Y axis options on the bubble chart are derived from this table. The indicator scores are gathered from the Indicator Scores [apm_app_indicator_score] table.

Note:

Only indicators registered in the Application Bubble Chart [apm_bubble_chart] table appear as axis options on the bubble chart. Adding an indicator to a scoring profile alone is not sufficient. For details on how to add X and Y axis indicators, see Add or edit an application indicator.

Step 4: Stakeholders complete assessments

The EA team sends out assessment surveys. Stakeholders rate each application on Business Value and Technical Risk. After all responses are collected, the platform aggregates them per application into the following raw scores (application weights):

Table 3. Raw assessment scores (application weights)

Application	Business Value (raw)	Technical Risk (raw)
App A — CRM Platform	85	20
App B — Legacy ERP	30	90
App C — Analytics Suite	70	40
App D — HR Portal	55	60
App E — Internal Wiki	20	75

Note:

Raw scores here are assessment aggregate values on a 0–100 scale. These are the application weights — the inputs to normalization. They are not directly plotted on the bubble chart.

Step 5: The scoring job runs and calculates normalized values

The admin runs the Load Application Indicators and compute Application Scores scheduled job. The system calculates a Normalized Value for each application per indicator, scaling all values to a 1–10 range relative to each other.

Verifying that the job ran successfully

• System log: Navigate to syslog.list, filter Message contains Load Application Indicators, Created = Last 30 minutes. A successful run shows two entries: #### Starting... and #### Completed execution of... <elapsed>ms. A missing completion entry means the job failed mid-run — add Level = Error to the filter to find the cause.
• Indicator scores: Navigate to apm_app_indicator_score.list, filter by Fiscal period = <FY26: Q2> and Configuration Item = any business application (from this use case). Both Business Value and Technical Risk rows must appear with a non-zero Normalized value. If rows are missing, check that all assessment instances were Complete or Canceled before regeneration ran.
• Progress Worker path: If you used sn_apm_regenerate_application_scores.do instead of the scheduled job, search syslog for APM: Regenerate application scores on <date> — this is the log marker for the background worker path.

Normalization formula:

This scales raw scores, so all applications are comparable on a 1–10 range regardless of absolute values. The lowest-scoring application always maps to 1.0 and the highest to 10.0, with all others distributed proportionally between.

Normalized Value = (((appWeight - minWeight) / (maxWeight - minWeight)) x 9) + 1

For indicators with Minimize direction, the normalized value is then inverted so that a lower raw value (better condition) results in a higher chart position:

Adjusted Normalized Value = (10 - Normalized Value) + 1

Business Value — normalized values (direction: Maximize)

Min = 20 (App E) · Max = 85 (App A) · Range = 65.

Table 4. Business Value — normalization calculation

Application	Raw score	Calculation	Normalized Value
App A — CRM Platform	85	(((85-20)/65)x9)+1	10.00
App B — Legacy ERP	30	(((30-20)/65)x9)+1	2.38
App C — Analytics Suite	70	(((70-20)/65)x9)+1	7.92
App D — HR Portal	55	(((55-20)/65)x9)+1	5.85
App E — Internal Wiki	20	(((20-20)/65)x9)+1	1.00

Technical Risk — normalized values (direction: Minimize, inverted)

Min = 20 (App A) · Max = 90 (App B) · Range = 70.

Table 5. Technical Risk — normalization and inversion calculation

Application	Raw score	Step 1: Normalize	Step 2: Invert	Final Normalized Value
App A — CRM Platform	20	1.00	(10-1.00)+1	10.00
App B — Legacy ERP	90	10.00	(10-10.00)+1	1.00
App C — Analytics Suite	40	3.57	(10-3.57)+1	7.43
App D — HR Portal	60	6.43	(10-6.43)+1	4.57
App E — Internal Wiki	75	8.57	(10-8.57)+1	2.43

Tip:

App B has the highest raw Technical Risk score (90), meaning it is the riskiest application. After inversion, it receives a normalized value of 1.00 — the lowest possible — placing it at the bottom of the Y-axis on the bubble chart. This makes the visual intuitive: riskier applications appear lower.

Step 6: Indicator scores and overall application scores are calculated

The system calculates each application's indicator score — the normalized value weighted by the indicator's share of the scoring profile — and sums them into an overall application score.

Indicator Score formula:

Indicator Score = Normalized Value x (Indicator Weight / Total Weights)

In this example, the weight share for each indicator is 50 / (50 + 50) = 0.5.

Table 6. Indicator scores and overall application scores

Application	BV normalized	BV indicator score	TR normalized	TR indicator score	Overall score
App A — CRM Platform	10.00	5.00	10.00	5.00	10.00
App C — Analytics Suite	7.92	3.96	7.43	3.72	7.68
App D — HR Portal	5.85	2.93	4.57	2.29	5.22
App E — Internal Wiki	1.00	0.50	2.43	1.22	1.72
App B — Legacy ERP	2.38	1.19	1.00	0.50	1.69

These values are stored across two separate tables:

• Indicator Score [apm_app_indicator_score] — holds the per-indicator, per-application, per-fiscal-period score records. The Normalized Value in this table is what the X and Y axes on the bubble chart read directly.
• Overall Application Score [apm_app_score] — holds the aggregate score per application per fiscal period, calculated by summing all Indicator Scores. This is visible in the List view of Application Rationalization and is used as the Bubble Size when the Overall Score option is selected in the chart settings.

Note:

The X and Y axis positions on the bubble chart are read from Indicator Score [apm_app_indicator_score] table. The overall score only affects bubble size.

Verify the business application default filter

Before a scored business application can appear on the bubble chart, verify the business application default filter. This filter is an encoded query stored in the sn_apm_ws.business_application_default_filter system property.

The default value is:

install_status!=2@install_status!=2000@life_cycle_stage!=End of Life@life_cycle_stage!=EMPTY

This means the chart excludes any business application that is in Retired or Decommissioned install status, or whose lifecycle stage is End of Life or empty. In this scenario, all five Acme Corp applications have an active install status and a current lifecycle stage, so all five pass the filter and are eligible to appear as bubbles.

Important:

If your organization has customized this property — for example, by adding a company scope filter such as company.sys_id=YOURCOMPANYID — any scored application that does not match the custom filter will be silently excluded from the chart, even if it has valid indicator scores for both axes. This is one of the most common causes of missing bubbles. To verify, apply the encoded query on the Business Applications [cmdb_ci_business_app.list] table and confirm your scored applications appear in the results.

The data pipeline

The bubble chart rendering depends on the following data chain. Verify that the following components are aligned for the chart to render data.

Link	Component	What it does	Where to check
1	Scoring profile property	Determines which scoring profile the bubble chart queries against.	System Property: sn_apm_ws.app_indicator_scoring_profile
2	Profile indicator configuration	Maps indicators to the scoring profile with weights and configuration.	Table: Profile indicator [apm_application_profile_indicator]
3	Bubble chart configuration	Maps specific indicators to the X, Y, and Z (bubble size) axes of the chart.	Table: Application Bubble Chart [apm_bubble_chart]
4	Indicator score data	Actual score records for business applications, per indicator, per fiscal period.	Table: Indicator Score [apm_app_indicator_score]
5	Business application default filter	Controls which business applications are visible in application rationalization.	System Property: sn_apm_ws.business_application_default_filter

Step 7: Reading the bubble chart

Before interpreting the chart, check the following details.

Table 7. Pre-flight checklist — things to verify before reading the chart

#	What to check	What good looks like
1	Correct scoring profile configured? [sn_apm_ws.app_indicator_scoring_profile]	Contains the sys_id of the profile under which indicator scores were created. If blank, the system uses the Default Application Profile. Only one sys_id is accepted — comma-separated values are not supported.
2	Indicators mapped to that profile? [apm_application_profile_indicator]	At least two indicators (for the X and Y axes) are listed in the Profile Indicators related list with non-zero weights.
3	Bubble chart configuration set up? [apm_bubble_chart]	An active record exists whose X and Y Indicator fields reference indicators that are also listed in the scoring profile from check 2.
4	Indicator scores exist for the selected fiscal period? [apm_app_indicator_score]	Records exist for business applications, for the fiscal period selected in the chart UI, under the same scoring profile. Both X and Y axis indicators must have scores — a bubble only renders if both axes have data for the same fiscal period.
5	Scored apps pass the default filter? (sn_apm_ws.business_application_default_filter)	The business applications with indicator scores are not excluded by the encoded query. Verify by applying the filter on cmdb_ci_business_app.list and confirming the scored apps appear.

Role required: sn_apm.apm_analyst.

The EA architect navigates to Workspaces > Enterprise Architecture Workspace, opens the Application Rationalization page by selecting the application rationalization icon (), and then selects Bubble chart.

The architect selects the settings icon () to configure the chart and selects Apply:

• X-axis: Technical Risk
• Y-axis: Business Value
• Bubble size: Overall Application Score
• Bubble labels: Toggle enabled, to display business application names on the chart.

Note:

The bubble chart plots the Normalized Value (1–10 scale) on each axis — not the raw assessment score and not the weighted indicator score. The axis scale is fixed at 0–10. For a bubble to appear on the chart, indicator scores for the selected fiscal period must be available for both the X-axis and Y-axis indicators.

After selecting Apply, business application bubbles are displayed on the chart. Each application appears at the intersection of its normalized values for the two chosen indicators:

Table 8. Bubble chart — application positions and quadrant assignments

Application	X (TR norm)	Y (BV norm)	Quadrant	Implication
App A — CRM Platform	1.00	10.00	Sustain	High value, low risk — maintain and monitor
App C — Analytics Suite	3.57	7.92	Sustain	Strong value, manageable risk — keep steady
App D — HR Portal	6.14	5.85	Invest	Moderate value, elevated risk — invest to reduce risk
App E — Internal Wiki	8.17	1.00	Migrate	Low value, high risk — migrate or replace
App B — Legacy ERP	10.00	2.38	Migrate	Low value, very high risk — urgent action needed

Note:

Business application bubbles whose X and Y axis values are within the value range of +/-0.25 of each other are grouped. A grouped bubble displays the total number of business application bubbles it contains. On selecting a grouped bubble, the info pane appears, displaying the list of individual business applications that are part of the grouped bubble.

Note:

The bubble chart displays up to 500 bubbles by default. If you have more than 500 assessed business applications, configure the sn_apm_ws.appRationalizationMaximumBubbles system property to increase this limit. For details, see Change the number of bubbles displayed on the bubble chart.

You can also generate insights into business applications using Now Assist. For information, see Generate insights into business applications.

Step 8: Taking action from the bubble chart

The architect identifies App B (Legacy ERP) in the Migrate quadrant. Its Business Value normalized score (2.38) and Technical Risk normalized score (1.00) indicate low value and very high risk, making it a priority for retirement. The architect takes the following actions directly from the bubble chart.

Set planned disposition

The architect selects the bubble for App B and performs the following, depending on the bubble type:

Table 9. Set planned disposition actions by bubble type

Bubble type	Action
Single bubble	Select the bubble for App B. In the pop-up window, select the context menu icon () and select Set planned disposition. In the Set planned disposition window, select Migrate from the Planned disposition list, enter a Planned disposition date, and add the justification in the Reasoning field. Select Update.
Grouped bubble	Select the grouped bubble. The info pane appears, displaying the list of individual business applications within the group. Select the context menu icon () next to App B and select Set planned disposition. In the Set planned disposition window, select Migrate from the Planned disposition list, enter a Planned disposition date, and add the justification in the Reasoning field. Select Update.

Create a demand

The architect also creates a demand for the retirement initiative directly from the bubble chart:

Table 10. Create demand actions by bubble type

Bubble type	Action
Single bubble	Select the bubble for App B. In the pop-up window, select the context menu icon () and select Create demand. On the Create demand form, fill in the fields and select Create. For a description of the field values, see Create demand form.
Grouped bubble	Select the grouped bubble. The info pane appears. Select the context menu icon () next to App B and select Create demand. On the Create demand form, fill in the fields and select Create. For a description of the field values, see Create demand form.

The architect also notes that App E (Internal Wiki) sits in the Migrate quadrant but has a slightly higher Technical Risk normalized value (2.43) compared to App B. Before setting a disposition, the architect selects the App E bubble to open the side panel, then selects Full details to review the full business application record without leaving the bubble chart. For more details, see Edit business application details in bubble chart view.

Summary: the full flow at a glance

The following sequence summarizes how a raw assessment score is set to a bubble position on the chart:

1. Stakeholder assessments produce a raw score per application (the application weight).
2. The scoring job normalizes raw scores to a 1–10 scale relative to all other applications in the set (Normalized Value). For Minimize-direction indicators, the value is inverted so that a lower raw score results in a higher chart position.
3. Weights are applied to each normalized value (Normalized Value x weight share = Indicator Score).
4. Indicator Scores are summed to produce the Overall Application Score.
5. Scores are stored in two tables: Indicator Scores [apm_app_indicator_score] table (per-indicator scores — drives axis positions) and Overall Application Score [apm_app_score] table (overall aggregate score — drives bubble size when Overall Score is selected).
6. The default application filter (sn_apm_ws.business_application_default_filter) is applied. Only applications that pass this encoded query filter are eligible to appear as bubbles.
7. The bubble chart plots the Normalized Value on the X and Y axes. The axis scale is fixed at 0–10. Bubble color reflects the planned disposition value set for each application.

Key behaviors this example illustrates

Position is relative, not absolute. An application's bubble position depends on how it compares to all other applications in the evaluated set — not on its raw score alone. If you add or remove applications from the portfolio, the normalized values recalculate and bubbles shift.

The chart plots normalized values. Even though the scoring profile uses weighted indicator scores to calculate the overall application score, the X and Y axes show the normalized value (1–10). Changing indicator weights does not move bubbles left or right — it only changes the overall score, which controls bubble size when configured that way.

Minimize-direction indicators are inverted on the chart. Technical Risk is set to Minimize. Because Technical Risk is on the X-axis, a riskier application appears further right. The Invest quadrant (top-right) represents applications with high business value but elevated technical risk — applications worth investing in to reduce that risk.

Fiscal period alignment is critical. If the indicators are set to Quarter frequency and the fiscal period filter on the chart is set to a month, no data appears. The period filter must match the indicator frequency.

Bubble size adds a third dimension. Configuring an indicator or the overall score as the Bubble Size lets you compare a third metric visually without adding another axis — for example, using Portfolio TCO as the bubble size shows cost alongside value and risk.

Closely scored applications are grouped. Bubbles whose X and Y axis values are within +/-0.25 of each other are combined into a single grouped bubble showing a count. Select a grouped bubble to open the info pane and see the individual applications inside.

Related concepts

• Use bubble chart view

Related tasks

• Analyze applications using the bubble chart
• Create a demand using the bubble chart
• Set the planned disposition of a business application
• Add business application lifecycle data using the bubble chart
• Edit business application details in bubble chart view
• Change the number of bubbles displayed on the bubble chart