> 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.md).

# Systems Management

Define Systems and System Types in a Blueprint, then link Systems to Processes.

### 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 document scope and ownership. Use System Types to standardize reporting across Projects.

### Benefits

* Clearer scope definition across delivery teams
* Better reporting through consistent system classification
* Faster impact analysis when changes affect multiple Processes

### Setup Steps

{% stepper %}
{% step %}

### Create Systems

* [Create Systems](/blueprints/systems-management/create-systems.md)
  {% endstep %}

{% step %}

### Define System Types

* [System Types](/blueprints/systems-management/system-types.md)
  {% endstep %}

{% step %}

### Link Systems to Processes

Link Systems to Processes for traceability.
{% endstep %}
{% endstepper %}

### Best Practices

* Create separate System records for separate environments.
* Standardize System Type names across Blueprints.
* Keep System names stable and human-searchable.

### Summary

Systems Management defines the technology scope for a Blueprint. System Types and process links support reporting and traceability.


---

# 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.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.