> 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/system-types.md).

# System Types

Classify Systems for filtering, reporting, and consistent governance.

### Overview

System Types classify Systems into meaningful groups. This supports consistent filtering and reporting across Projects.

### Key Concepts

* **System Type**: reusable classification for Systems
* **Reporting consistency**: standard types reduce one-off naming

### How It’s Used

Use System Types to group Systems by function. Use types in views, exports, and reporting workflows.

### Benefits

* Cleaner reporting across Projects
* Faster filtering in large System lists
* More consistent governance and ownership reviews

### Setup Steps

{% stepper %}
{% step %}

### Define System Types

Create a small set of stable types. For example: `ERP`, `CRM`, `Data`, `Integration`, and `Payments`.
{% endstep %}

{% step %}

### Assign types to Systems

Update Systems to include the correct System Type.
{% endstep %}
{% endstepper %}

### Best Practices

* Keep the list small and stable.
* Avoid overlapping types that create ambiguous reporting.
* Document type meanings in an internal SOP.

### Summary

System Types standardize classification for Systems. They support filtering and reporting across Projects.


---

# 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/system-types.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.