> 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/overview/calculations.md). # Calculations The calculated indicators YouDesign Command keeps on portfolio elements, what each one tells you, and where newer Measures and Scoring take over. YouDesign Command keeps a set of calculated indicators on every portfolio element, such as the number of incidents, the days left until end of life, or a rationalization score. They are filled in automatically and are read-only. This page explains what each indicator tells you, so you can use it in lists, reports and decisions. {% hint style="info" %} **Measures and Scoring in the portal** In the portal, figures and weighted judgments are handled by [Measures](/command/features/measures.md) and [Scoring](/command/features/scoring.md). They track values over time, show how complete the data is, and explain each score by its inputs and weights. Where a classic calculated field below is replaced by Measures or Scoring, the upgrade guide for that version says so. See the [Product Roadmap](/command/overview/roadmap.md). {% endhint %} ## Counts | Indicator | What it tells you | | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Incidents** | The number of incidents related to the element in the last 12 months. | | **Outdated Software** | The number of software products the element uses that have reached an expiring, exceptional or end-of-life phase, such as Expiring, Exception, Extended Support, End of Life, Retired, Rejected, Forbidden or Obsolete. The count is rolled up to the related portfolio elements. | | **Relationships** | The number of direct upstream and downstream relationships. | | **Users** | The latest actual number of users, taken from the users KPI. | {% hint style="warning" %} **One users value per day** Record only one users value per element per day. If several are recorded on the same day, they are not taken into account. {% endhint %} ## Lifecycle indicators | Indicator | What it tells you | | ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Days in Prod** | How many days the element has been in productive use according to its internal lifecycle. A negative value shows how many days remain until it goes into production. Counting stops once the element reaches the Non-Productive stage. | | **Days to EOL** | How many days remain until the element reaches the Non-Productive stage, for example Retired, Obsolete, Completed or Canceled. | | **Days to Benefit** | How many days remain until the expected benefits are due. | | **Internal Lifecycle** and **Manufacturer Lifecycle** | The current phase of each lifecycle type. A lifecycle type your administrator adds needs its own field to show its current phase. | See [Lifecycle Stages & Phases](/command/overview/lifecycle-stages-phases.md) for the stages and phases these indicators use. ## Cost indicators | Indicator | What it tells you | | ----------------- | -------------------------------------------------------------------------------------------------------------------- | | **Cost Rollup** | Total operating (OPEX) and capital (CAPEX) cost, added up from related elements to the elements that depend on them. | | **Cost Sum** | The cost totals and breakdowns shown on an element, such as baseline, planned, current-year and total cost. | | **OPEX per User** | The current year's operating cost of the element divided by its number of users. | ## Business and risk scores | Indicator | What it tells you | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Capability Score** | How business-critical the capabilities are that the element supports. | | **Process Score** | How business-critical the processes are that the element supports. | | **Business Value Score** | The element's business value, based on the capabilities and processes it supports and their business criticality. | | **Compliance Risk Score** | How many of the element's relationships are non-compliant or non-conformant. | | **Functional Redundancy Score** | How many other elements are mapped to the same reference model entry, which points to overlapping functionality. | | **Rationalization Score** | How strong a candidate the element is for rationalization. The higher the score, the stronger the candidate. It combines relationships, compliance risk, incidents, users, business criticality, capability and process scores, operating cost per user and days to end of life. | ## Decision indicators | Indicator | What it tells you | | ---------------------- | -------------------------------------------------------------- | | **Recommendation** | The most recently updated recommendation for the element. | | **Scenario Score** | The total score of a scenario across its evaluation criteria. | | **Stakeholder Rating** | The average rating the element receives from its stakeholders. | --- # 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/overview/calculations.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.