Applications
The Applications page lists your whole portfolio; each application has its own page with everything APM+ knows about it.
The Applications list
- Search by name or Assets key, and filter by lifecycle, tier, where the application exists (see below) and Stale only.
- Columns show tier, lifecycle, owners, freshness and the Assets object. Click a column heading to sort.
- New application creates the application in Assets too (name, description, tier and status).
Where an application exists
The Assets filter shows counts for each state:
| State | Meaning |
|---|---|
| In APM+ and Assets | Linked to a live Assets object. The normal state. |
| Gone from Assets | Its Assets object was deleted. APM+ keeps the record and its data, read only, until you delete it. |
| Not in Assets | Never linked to an Assets object (from an earlier APM+ version). |
Objects that are only in Assets appear in APM+ with the next sync. Admins can check the whole picture with Compare with Assets.
Bulk change
Tick applications (or tick the header to select the page) and set a new tier, lifecycle status and/or Business Owner for all of them. A new Business Owner replaces the current one(s). Up to 500 applications per change; progress is shown, Stop finishes the batches in flight, and anything that failed or was skipped stays selected so you can retry.
The application page
The header shows the tier, freshness and Assets key. Confirm details are accurate marks the record reviewed (resetting its freshness); Ask stakeholders to confirm sends its owners a review request. Editors can also Clone (copies the Assets object and APM+'s data, but not assessments, risk or history) and Delete (APM+ only, or Assets too).
| Tab | What it holds |
|---|---|
| Overview | Description, tier, lifecycle status, in-service and out-of-service dates, vendor and product, licence model and licensed entity, and any duplicate suggestions. |
| Lifecycle | Dates for each lifecycle phase. Setting one phase's end fills the next phase's start (the day after), and the other way round. |
| Stakeholders | People and their roles: Business Owner, Technology Owner, Subject Matter Expert (roles are configurable). One role per person. |
| Capabilities | The business capabilities the application supports, with AI-suggested mappings to accept or reject. |
| Services | The JSM business services it supports (services come from Assets). |
| Interactions | Data exchanges with other applications (direction and type) and a context diagram of its neighbours. |
| Assessments & TCO | Functional and technical assessments with a TIME decision, cost items, and the total cost of ownership over time. |
| Risk | Risk assessments and their details, with the risk rating over time. |
| Tech stack | The software components it runs on, with their end-of-support position. |
| Licences | Licence metrics (for example users or cores) and quantities. |
| Documents | Links to where its documents live (http or https only). |
| Review requests | Every review request raised for it, and the answers. |
| Tickets | Incidents, open incidents, changes and all tickets in the last 90 days, counted live from Jira (only tickets you can see). Click a count to open the search. |
| History | Who changed what, and when. |
Tiers, lifecycle and freshness
- Tier uses Assets' values: Tier 1 is the most critical, Tier 4 the least. New applications default to Tier 3.
- Lifecycle status uses the statuses your Assets Status attribute allows (the JSM template has Active, Pending and Archived). Archived applications are out of the active portfolio: they're left out of reviews, gaps and end-of-support exposure.
- Freshness (0–100) halves every year since the record was last confirmed. Below 40 a record is stale; 70 and above is fresh. Confirming a record, or an owner approving a review, resets it.