> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/blueprints/systems-management/create-systems.md).

# Create Systems

Add Systems to a Blueprint, then link Systems to Processes for traceability.

### Overview

Systems represent applications and platforms in scope for delivery work. Linking Systems to Processes supports traceability and reporting.

### Key Concepts

* **System**: application, platform, or service in scope
* **System Type**: classification used for filtering and reporting
* **Environment**: production, test, or sandbox context for a System record

### How It’s Used

Use Systems to define technology scope alongside Processes. Use System Types to standardize reporting across Projects.

### Benefits

* Clearer technology scope for delivery teams
* Better reporting through consistent classification
* Faster impact analysis through links to Processes

### Setup Steps

{% stepper %}
{% step %}

### Add a System to a Blueprint

1. Navigate to **Blueprints**.
2. Open a Blueprint.
3. Open **Systems** (or **Systems Management**).
4. Select **Add system**.
   {% endstep %}

{% step %}

### Define core fields

Required:

* **Name**: stable internal name, such as `ERP — Production`

Optional fields when enabled:

* **System Type**: such as `ERP`, `CRM`, `Data`, `Integration`
* **Environment**: Production, Sandbox, UAT, Dev
* **Owner / Admin**
* **URL / login**
* **Description**
  {% endstep %}

{% step %}

### Link Systems to Processes

Linking is many-to-many. One Process can run on several Systems.

For example:

* `Procure-to-Pay` → `ERP — Production`
* `Customer lifecycle` → `CRM — Production`
* `Data integration` → `Integration platform`
  {% endstep %}
  {% endstepper %}

### Best Practices

* Create separate System records for separate environments.
* Keep System Types small and stable.
* Avoid generic System names without environment context.

### Summary

Systems define technology scope for a Blueprint. Links to Processes support traceability and reporting.

#### Troubleshooting

<details>

<summary>System cannot be linked to a process</summary>

Confirm both items are active. Confirm Blueprint edit permission exists.

</details>

<details>

<summary>System does not appear in a Project</summary>

Confirm the System exists in the Blueprint. Confirm the Project was created after the System was added.

</details>

Related:

* [What Are Blueprints?](/blueprints/blueprint-fundamentals/what-are-blueprints.md)
* [Processes](/blueprints/creating-blueprints/processes.md)
* [Process Hierarchy](/blueprints/creating-blueprints/process-hierarchy.md)
* [Systems Management](/blueprints/systems-management.md)
* [System Types](/blueprints/systems-management/system-types.md)


---

# 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://help.transform.ai/blueprints/systems-management/create-systems.md?ask=<question>&goal=<user_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.