What Modernization Readiness Is
Modernization Readiness sums up the modernization vectors of all applications you keep, for one modernization topic (see Modernization Vector: The Route to Ready). It answers the question a rollout depends on: how ready are we?
To keep the answer simple, the dashboard puts every application into one of two groups:
- Ready: the route Ready (No Fix Needed), including applications whose only findings are in current HCL template code.
- Needs Fix: every other route, from Fix Master Template to Individual Code Fixes.
Sunset applications have no modernization vector and do not appear here.
Why Usage Matters
Counting applications alone can mislead. A ready application that nobody opens matters less than one in daily use, and a single application that needs fixes can hold back many users. That is why the dashboard compares the share of applications with the share of usage they carry in the last 90 and 365 days:
- If the ready applications carry a smaller share of usage than their share of applications, readiness sits mostly in applications people rarely use.
- If a route carries a large share of usage with few applications, fixing those few applications reaches many users. That is where to start.
Where to Find It
In the iDNA Portal: [App Lifecycle] → [Modernization Readiness].
How to Read It
The dashboard has one filter, [Modernization Topic]; it opens with Notes 64-bit.
Overview Tab
- Applications by Modernization Readiness and Usage in the last 90 days: all kept applications in one bar, split into Ready and Needs Fix and each again into used and not used in the last 90 days. The Needs Fix part that nobody used recently deserves a second look before anyone invests work in it.
- Modernization Readiness by Share of Applications compared with Share of Usage: the share of Ready (green) against Needs Fix (grey), once by number of applications and twice by usage. In the example above, about half of the kept applications are ready, but they carry less than half of the usage: the applications people use most are more often the ones that need fixes.
- The link [Applications with Usage in the Last 90 Days] opens the Modernization Overview limited to recently used applications.
Modernization Vectors Tab
The same comparison per route, next to a short explanation of each route:
Look for routes where the usage bars are much longer than the applications bar. In the example, Fix Master Template holds only a few applications but well over a tenth of the usage: fixing one master template here makes a large part of the users' daily work ready.
Did you know?
You can copy a screenshot of this dashboard, paste it into your AI client and ask the iDNA Applications Companion to interpret it, for example: "This is our Modernization Readiness for Notes 64-bit. Where does a small fix effort help the most users?" With the Companion connected to iDNA's MCP server, you can go straight on: "Which work sessions make our most used applications ready?" See Setting up the iDNA Applications Companion.
What to Do Next
- To see which application is on which route: Modernization Vector: The Route to Ready.
- To turn the routes into a ranked work plan: Modernization Planning: Work Sessions.
- Switch the [Modernization Topic] to compare the targets: an estate can be close to ready for Notes 64-bit and still need much more work for Nomad.
Related Topics
- Usage: how iDNA collects and measures usage.
- Lifecycle Vector: Keep or Sunset: which applications are kept and therefore counted here.