Skip to content

Cataloguing applications

Applications live in the Assets surface (Estate → Assets, /assets) — one unified catalogue with a lens switcher; select the Applications lens (the old /applications link redirects here). This is where most teams spend the most time. This guide covers getting applications in and enriching them.

Get them in fast

Don't hand-create applications one by one if you have a list. Import a CSV from your CMDB or spreadsheet (Importing data), or connect a sync source (Discovery & connecting). Catalogue first; enrich later.

What to fill in (in priority order)

For each application, the highest-value fields are:

  1. Criticality tier — T1 Mission Critical / T2 Business Critical / T3 Standard. Set inline via the criticality picker. This is your judgement as an architect.
  2. Capabilities it realises — the application's why. Link from the Architecture context section, or confirm an AI suggestion.
  3. Lifecycle status — Active / Planned / Retiring.
  4. Product owner — the asset-level accountable person (see Assigning owners).
  5. Technology it runs on — links that power blast-radius and EOL risk.

The application page

Each application has a purpose-built page:

  • Profile strip — product owner, lifecycle, version, support dates, monthly cost, tech contact, and deployment model + cloud provider (where the app runs — On-prem / Cloud / SaaS / Hybrid). All inline-editable (click a field; saves on blur/Enter).
  • Business owner (derived) — read-only, shown when the app is mapped to capabilities; it flows from those capabilities' business owners.
  • Signals bar — flags issues to act on: never checked in, ARB review in progress, NFR contradictions, no owning org unit.
  • Architecture context — Delivers (capabilities) and Runs on (technology), side by side.
  • Collapsible detail: Risk & Health, Governance (check-in), Cost, Procurement & Standards, Initiatives, Data, Comments.

Working efficiently

  • Use the portfolio filters and stats tiles to work through the estate by criticality, lifecycle, or risk.
  • Set criticality on your top ~20 applications first — that's what makes every downstream view meaningful.
  • Don't aim for 100% completeness on day one. A catalogued, criticality-tiered, capability-linked top tier beats a fully-detailed nothing.