> 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/architecture.md). # Architecture How YouDesign Command is built as a native ServiceNow application with a browser portal, an in-browser assistant and one shared data model. YouDesign Command runs entirely inside your ServiceNow instance. It has two parts: the **portal** you work in, and the **application** in your instance that stores the data and enforces the rules. Both use the same records your organisation already keeps in the CMDB. Nothing is copied to an outside system. ## At a glance | Question | Answer | | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Where does it run? | 100% natively in ServiceNow, as a scoped application installed from the ServiceNow Store. | | Do I need other ServiceNow products? | No. It needs only the core ServiceNow platform. | | Where is the data stored? | In your instance, in the CMDB and in the application's own tables. | | How do people use it? | Through the Command portal, a page in your instance that opens in the browser. Classic ServiceNow forms, lists and dashboards keep working against the same data. | | Where does the assistant run? | Its language understanding runs in the browser. It does not send your questions or data to an external AI provider and does not use paid AI tokens. | | Who controls access? | ServiceNow roles, groups and access rules, checked by the instance on every read. | {% hint style="success" %} **No other ServiceNow plugins required** YouDesign Command does not require other ServiceNow modules or plugins, such as HR, PPM, APM or GRC. It can add value when they are installed. {% endhint %} ## The two parts | Part | What it does | | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **The portal** | The workspace people use: Home, My Space, the content you create (tables, roadmaps, maps, dashboards, reports, scenarios and more), the Data Hub and the Command Dialog assistant. Every view reads live records each time it opens, so it is never out of date. See [The Portal](/command/the-portal/portal.md). | | **The application in your instance** | Stores your saved content and its sharing, and provides the services the portal calls: lifecycle, measures, scores, scenarios and future state, data governance, policy checks and approvals. It enforces permissions on the server. | ## One data model Every portfolio object, such as a business application, a capability or a project, is a record in the ServiceNow CMDB. YouDesign Command adds one shared parent class, the **Portfolio Element**, on top of the CMDB configuration item. Every portfolio class inherits from it, so fields, lifecycles, relationships and indicators work the same way on every class. Your ServiceNow administrator can adapt and extend this model like any other ServiceNow application. See [Metamodel](/command/metamodel/metamodel.md) for the full model. ![The main components of YouDesign Command running natively on ServiceNow](https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-b7b25d814f95390e07b4a83a278bce48451ce184%2Fd48132a-UPM-X_Architecture.png?alt=media) ## How the capabilities fit together | Capability | What it holds | Read more | | ------------------------------------- | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | | Lifecycle | Dated phases and milestones for each element, and the roadmap | [Lifecycle](/command/features/lifecycle.md) | | Measures | The figures you track, such as cost, risk or adoption, actual and planned, over time | [Measures](/command/features/measures.md) | | Scoring | Weighted judgments built from measures, with a red, amber or green headline | [Scoring](/command/features/scoring.md) | | Future State Repository and Scenarios | Planned elements and alternative futures, kept apart from today's records until you commit them | [Future State Repository](/command/features/future-state-repository.md) | | Data Governance | The completeness, currentness and correctness of the data the other capabilities rely on | [Data Governance](/command/features/data-governance.md) | | My Space and sharing | Your saved content, folders, sharing with people and groups, tasks and notifications | [My Space and Sharing](/command/the-portal/my-space.md) | {% hint style="info" %} **Live data, never a copy** Saved content stores what you built and which records it points to. Figures such as measures, lifecycle dates and report evidence are read again from the instance each time you open the content. {% endhint %} ## Browser support Use a current version of Chrome, Edge, Firefox or Safari. Internet Explorer and Edge Legacy are not supported. --- # 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/architecture.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.