SCHEMA TEMPLATES
Application Portfolio
Build a searchable inventory of applications that connects business ownership, technology, cost and lifecycle.
Applications often have different business and technical owners, costs and retirement plans. This template makes those relationships visible in one inventory, helping teams prioritize security reviews, lifecycle changes and spending decisions.
Fields
An application inventory should help answer more than “what software do we have?” Use this structure to connect each system to its people, operating model and future plans.
| Field | Type | What it captures |
|---|---|---|
| ApplicationRequired · Indexed | Text | Name of the application represented by this record. |
| Business ownerRequired · Indexed | Confluence user | Business-side person accountable for the application. |
| Technical ownerRequired · Indexed | Confluence user | Person accountable for the application's technical operation. |
| Business criticalityIndexed | Single choice | Importance of the application or asset to business operations.Choices: Low, Medium, High, Critical |
| Lifecycle statusRequired · Indexed | Single choice | Whether an application is planned, active, being retired or retired.Choices: Planned, Active, Sunset, Retired |
| Hosting modelIndexed | Single choice | How the application is hosted or delivered.Choices: SaaS, Cloud, On-premises, Hybrid |
| Data classificationIndexed | Single choice | Sensitivity of the information processed by an application.Choices: Public, Internal, Confidential, Restricted |
| VendorIndexed | Text | Supplier of the service or application. |
| Annual costIndexed | Number | Estimated yearly cost of running the application. |
| Last security reviewIndexed | Date | Date of the application's most recent security assessment. |
| End-of-life dateIndexed | Date | Planned or known retirement date of the application. |