App Rationalization Bubble Chart - Axes Update

[Zach Allen1]

Hey Community,

Looking for some insights on the feasibility of modifying the X & Y axis within Application Rationalization section under the EA Workspace.

OOTB goes up to 10 on both X & Y axes. Due to some historical data we are looking to import, scoring goes up to 5 for certain stakeholders. To accommodate  this, I am looking to understand if it is simple fix to change each axis ceiling to 5 instead of 10.

Thanks for any insights!

[MaxMixali]

Modifying X & Y Axis in Application Rationalization (EA Workspace)
===================================================================

Overview
---------
The Application Rationalization quadrant chart in the Enterprise Architecture (EA) Workspace uses a fixed 0–10 scale for both X (Technical Fit) and Y (Business Value) axes. This range is defined in the out-of-the-box scoring model and visualization logic.

Because of historical data (e.g., legacy assessments scored 1–5), organizations sometimes want to adjust the scale. However, this is not a configurable parameter in the UI or through a system property.

----------------------------------------------------
1. Why the Scale is Fixed at 10
----------------------------------------------------
- The chart references scores stored in the `ea_app_score` table or derived from scoring models such as Technical Fit and Business Value.
- The visualization uses a normalization function (0–10) to align data with the quadrant layout.
- The scaling and chart axis logic are hardcoded within the EA Workspace component (part of the `sn_ea_workspace` scoped app).

----------------------------------------------------
2. Feasibility of Modification
----------------------------------------------------
There is **no simple out-of-the-box way** to change the axis limits to 5 instead of 10. The component does not expose configuration properties for axis limits in UI Builder.

Changing it directly would require **customization of the UI Builder component** or replacing it with a custom visualization.

----------------------------------------------------
3. Recommended Workarounds
----------------------------------------------------

Option A – Normalize Imported Data (Best Practice)
----------------------------------------------------
Instead of modifying the visualization, scale your imported 0–5 data to the expected 0–10 range.
Formula:
Normalized Score = (ExistingScore / 5) * 10

Advantages:
- Easy to implement.
- No code customization.
- Upgrade-safe.

----------------------------------------------------

Option B – Clone the Workspace Component
----------------------------------------------------
If you must display a 0–5 axis visually:
1. Open **UI Builder → Experience: EA Workspace → Application Rationalization page.**
2. Locate the **Quadrant Visualization** component.
3. Clone or replace the page/component with a **custom chart**.
4. Adjust the JSON configuration or use the **Now Experience UI Framework** to define your own scale.

Considerations:
- Requires front-end customization (React component override).
- May break on upgrades.

----------------------------------------------------

Option C – Modify Scoring Model Logic (Not Recommended)
----------------------------------------------------
You could theoretically change the scoring normalization script to output 0–5 instead of 0–10. However:
- It will misalign with all other EA dashboards.
- Future updates or dependencies (like Portfolio Scoring) may break.

----------------------------------------------------
4. Recommendation Summary
----------------------------------------------------

| Approach | Effort | Upgrade-Safe | Recommended |
|------------------------------|--------|---------------|--------------|
| Normalize data (Option A) | Low | ✅ Yes | ✅✅✅ |
| Clone UI component (Option B)| Medium | ⚠️ No | ⚠️ Optional |
| Modify scoring engine (C) | High | ❌ No | 🚫 No |

----------------------------------------------------
5. Key Takeaways
----------------------------------------------------
- The 0–10 axis scale is **hardcoded** and **not configurable** through UI or properties.
- The **recommended solution** is to normalize all imported data to a 0–10 scale.
- Only consider UI customization if visual alignment to 0–5 is business-critical.