> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/getting-started/use-cases.md). # Use Cases Twelve step-by-step walkthroughs that combine Command features to answer common portfolio and architecture questions. These walkthroughs show how Command's features fit together to answer real questions, from retiring applications to publishing a technology radar. Each one names the content types and the assistant requests involved. You do not need to type the requests word for word. {% hint style="info" %} **What you get depends on your data.** If your instance has no TIME scores, measures or lifecycle dates, the views say so rather than invent numbers. See [A view is empty](/command/getting-started/faq.md#a-view-is-empty-or-says-there-is-no-data). {% endhint %} | # | Question | Main tools | | -- | ------------------------------------------------------------------------------------------ | ---------------------------------------------- | | 1 | [Which applications should we decommission?](#1-which-applications-should-we-decommission) | Command Dialog, TIME Analysis, Advisory Report | | 2 | [Should we retire this one application?](#2-should-we-retire-this-one-application) | Advisory Report | | 3 | [What breaks if this system goes down?](#3-what-breaks-if-this-system-goes-down) | Dependency Map | | 4 | [Build a three-year roadmap](#4-build-a-three-year-roadmap) | Roadmap, Data Hub | | 5 | [Run a SWOT for a business capability](#5-run-a-swot-for-a-business-capability) | SWOT, Note | | 6 | [Assess and improve data quality](#6-assess-and-improve-data-quality) | Table, Form, Dashboard | | 7 | [Plan a cost reduction](#7-plan-a-cost-reduction) | Command Dialog, Gravity Map, Scenario | | 8 | [Compare consolidation options](#8-compare-consolidation-options) | Scenario, Scenario Comparison | | 9 | [Map capabilities to applications](#9-map-capabilities-to-applications) | Hierarchy Map | | 10 | [Give leadership a live dashboard](#10-give-leadership-a-live-dashboard) | Dashboard | | 11 | [Publish a technology radar](#11-publish-a-technology-radar) | Orbit | | 12 | [Evaluate new ideas](#12-evaluate-new-ideas) | Ideation Portal, Idea Assessment | *** ## 1. Which applications should we decommission? **When to use it.** You need a defensible shortlist of retirement candidates. **How to** 1. Open the **Command Dialog** and ask `which applications should we decommission?` 2. The assistant ranks your applications by their TIME business and technical fit. Those in the Eliminate quadrant (low on both) come first. 3. Click **Show these as a TIME Analysis**. Command creates a TIME Analysis in a new My Space folder called "Decommission candidates" and opens it. 4. In the TIME Analysis, expand a row to see its **Score inputs** and check that the position is fair. 5. For any candidate, click its recommendation chip, or ask `should we retire ?`. An Advisory Report opens (see [use case 2](#2-should-we-retire-this-one-application)). 6. Before you commit, ask `what depends on ?` (see [use case 3](#3-what-breaks-if-this-system-goes-down)). 7. Click **Show these on a Roadmap** to plan when each one goes. **Good to know** * The answer shows up to ten applications per quadrant and says so when there are more, for example "Eliminate 11 (top 10 shown)". * The ranking uses TIME business and technical fit. Cost trend and lifecycle stage are not part of it yet, so check them on the Advisory Report and the Roadmap.
The Command Dialog answering which applications to decommission, with the ranked Eliminate candidates, the Show these as a TIME Analysis chip and the full table opened in the main window.

The decommission answer ranks the weakest applications first

*** ## 2. Should we retire this one application? **When to use it.** You need a clear recommendation for a single application, ready for a decision forum. **How to** 1. Ask the assistant `should we retire PayGate?`, using your application's name. If several records match, it asks which one. 2. An **Advisory Report** opens. Read the verdict: **Ready to decide**, **Needs approval** or **Not ready**. 3. Read **Why: the factor ledger**. Each factor names its source and is graded **attested**, **measured**, **declared** or **unsupported**. 4. If the verdict is **Not ready**, read **To raise confidence** and click **Notify owner** to ask the owner to fix the gaps. 5. Once the data is fixed, click **Re-run assessment**. 6. Click **Accept plan** to record your decision, and **Download PDF** for the meeting. **Good to know.** Accepting a plan records a decision. It does not change any record. See [Advisory Report](/command/the-portal/content-types.md#advisory-report). *** ## 3. What breaks if this system goes down? **When to use it.** You need the blast radius before an outage, a migration or a retirement. **How to** 1. Ask the assistant `which applications are affected if Identity Service goes down?` or `what depends on ?`. Or create a **Dependency Map** and drag the record onto it from the Data Hub. 2. Set **Direction** to **Downstream impact**. 3. Increase the hop depth to follow the chain further. 4. Set **Simulate** to **Outage** to highlight everything affected. 5. For a planned retirement, set **Simulate** to **Retirement** and switch on the **Timeline** to see the cutover waves by quarter. 6. Share the map with the owners of the affected systems. **Good to know.** See [Dependency Map](/command/the-portal/content-types.md#dependency-map) for every control. *** ## 4. Build a three-year roadmap **When to use it.** You need a sequenced plan with phases, milestones and owners. **How to** 1. Create a folder in My Space, for example `Roadmap 2027-2029`, and add a **Roadmap** inside it. 2. Open the **Data Hub**, pick the table (for example Business Application), filter to the scope you need, and drag the records onto the roadmap. 3. In the **View** row, set the **Date range** to three years and the **Axis** to **Quarter**. 4. Choose the **Lifecycle** that drives the bars, and **Group by** collection to arrange records into workstreams. 5. Click **Edit**. Drag phases to new dates, and use **Add milestone…** for key events. Give each milestone a status. 6. Click **Save changes**. If your organisation requires approval for phase changes, those changes wait for the approver. 7. Switch on the **Metric** panel to see cost or other measures, and the **Timeline** to see them change by period. 8. Share the folder with the programme team as **Editor** and with stakeholders as **Viewer**. **Good to know.** Planned systems that do not exist yet can be added as **Future state** records from the Data Hub (**New**), so they sit on the same roadmap. *** ## 5. Run a SWOT for a business capability **When to use it.** You want a shared, cited view of where a capability stands. **How to** 1. Ask the assistant `create a SWOT for `. It drafts the matrix and opens it in view mode, with a unique title. 2. Click **Edit**. Review each card, rewrite where needed, and add cards with **＋ Add Card**. 3. Drag the supporting applications from the Data Hub onto the cards, so each point links to a real record. 4. Add a **Note** in the same folder for decisions and actions, and link the SWOT into it by dragging it from My Space. 5. Before the next review, ask `refresh this SWOT` to get an updated copy dated today, and compare. *** ## 6. Assess and improve data quality **When to use it.** You need to know whether the data is good enough to base decisions on, and to fix the gaps. **How to** 1. Ask the assistant `which data is missing for business applications I own?` for a quick list of gaps on your own records. 2. Create a **Table** of the records you care about. In **Fields > Advanced > Data Quality**, add a data-quality column. 3. Sort by that column to find the weakest records. 4. Open a weak record with **Edit**. On its **Data quality** card, click **Open details** to see the gaps. 5. Fill the missing fields, use **Verify** or **Verify all** on fields due for review, then **Reassess now**. 6. For a standing view, add a **Data quality** widget to a team Dashboard. **Good to know.** If no data-quality columns are offered, your administrator has not set up a governance scope for that table yet. See [Data Governance](/command/features/data-governance.md). *** ## 7. Plan a cost reduction **When to use it.** You need a scoped cost-reduction exercise with a target and a deadline. **How to** 1. Ask the assistant `how can we reduce cost by 25% by end of this year?` 2. It opens a **Cost reduction assessment** and asks, one step at a time, for the target percentage, the deadline, the cost measures, the areas (applications, contracts, people, infrastructure), the scope and any constraints. Your answers appear as chips you can change. 3. At the end it confirms the scope and names the sources to verify before savings are calculated. It does not invent savings figures. 4. To explore options visually, create a **Gravity Map** of the applications in scope, pick your cost measure as a magnet, and choose the **Rationalize** preset. 5. Model the cut as a **Scenario** (see [use case 8](#8-compare-consolidation-options)). **Good to know.** Cost reduction is the one guided analysis method that is live today. If your instance has no cost measures yet, the assistant says so; an administrator can add them in **Global Settings > Measures**. *** ## 8. Compare consolidation options **When to use it.** You need to choose between alternative paths on the same criteria. **How to** 1. Create a **Scenario** called `Option A: consolidate on platform X` and drag in the affected applications. 2. Mark retiring applications **Removed** with a decommission date, the replacement **Added** with an introduction date, and changed ones **Modified**. 3. Type planned values into measure cells where costs change. 4. Set **Compare** to **Scenario vs Baseline** to see the effect. 5. Use **Duplicate** on Option A to make `Option B`, and change it. 6. Set each scenario's **Status** to **Active** when it is ready to be scored. 7. Create a **Scenario Comparison** and drag both scenarios onto it. 8. Read the rows (cost, risk, benefit, rating) and the **Recommended** badge. **Good to know.** Live data stays untouched until a decision is made. *** ## 9. Map capabilities to applications **When to use it.** You need a capability map showing which applications support each capability, and where coverage is thin. **How to** 1. Ask the assistant `which applications support the business capabilities?` for a coverage answer. 2. Ask `create a hierarchy map with all business capabilities`. A Hierarchy Map opens with the capability tree. 3. In **View**, choose the **Nested boxes** or **Landscape** layout and set **Level** to the depth you want. 4. Drag the supporting applications from the Data Hub onto their capabilities. 5. Click **Edit** to fix placements by dragging nodes. 6. Download as PNG or PDF for a presentation. *** ## 10. Give leadership a live dashboard **When to use it.** You need an executive view that stays current without a reporting cycle. **How to** 1. Ask the assistant `build a CIO dashboard` (or CFO, CTO, COO, EA, PMO). Other topics include `create a CMDB health dashboard` and `create an application portfolio overview`. 2. Read the preview: how many widgets, how many records it can read, and any evidence gaps. 3. Click **Yes, create it**. The dashboard opens. 4. Click **Edit** to add widgets, for example a **Measure trend** for cost or a **Data quality** widget. 5. Drag a saved Roadmap from My Space onto the canvas to embed it. 6. Share it with the leadership group as **Viewer**. **Good to know.** A generated dashboard contains only widgets that have the data they need, and its description is a plain one-sentence summary. *** ## 11. Publish a technology radar **When to use it.** You want to show which technologies are adopted, on trial or being retired. **How to** 1. Create an **Orbit** and drag the technology records onto it. 2. Set **Sectors** to the category field (for example technology type), grouped at the top level. 3. Set **Rings** to **Lifecycle** or **TIME disposition**. 4. Set **Color by** to **Ring stage**. 5. Share it, or embed it in a Dashboard. *** ## 12. Evaluate new ideas **When to use it.** You need to decide which ideas to fund, tied to the systems they affect. **How to** 1. People submit ideas in the **Ideation Portal** with **+ New idea** and **Submit idea**. 2. Create an **Idea Assessment** and filter to the ideas under review. 3. Compare them on the **Value vs Feasibility** quadrant. 4. For a promising idea, drag the affected applications from the Data Hub into **Impacted Enterprise Assets**. 5. Use **Request clarification** where information is missing, then **Approve** or **Reject**. **Good to know.** See [Ideation Portal](/command/features/ideation-portal.md) for the submission side. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ins-pi.com/command/getting-started/use-cases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.