> For the complete documentation index, see [llms.txt](https://documentation.ocsinventory-ng.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ocsinventory-ng.org/quickstart-guides/for-users/base-and-template-inventory.md).

# Base and Template Inventory

Assets in OCS have two types of inventory data: **base inventory** and **template inventory**.

## Base Inventory

The **base inventory** provides a default set of core information about an asset. This inventory is always available and includes the following fields:

* Name
* Description
* Serial Number
* OS Name
* OS Version
* UUID
* IP Address
* Mac Address
* Domain
* Agent Version

## Template Inventory

To extend the **base inventory**, OCS uses a **template system**. These templates add extra fields and define what method should be used to retrieve the corresponding data.

### **Preloaded Templates**

By default, OCS includes six preloaded templates, visible at **Configurations** **→** **Inventory** **→** **Templates**:

* **Legacy** (for compatibility with legacy agents, version 2.X)
* **Linux (Debian based)**
* **Linux (RHEL based)**
* **MacOS**
* **Windows**
* **Generic SNMP**

***

### **Template Assignment**

OCS automatically assigns templates to assets based on their operating system/agent version during the first inventory using predefined [Rules](https://documentation.ocsinventory-ng.org/administrator-docs/server-setup/configuration/advanced/managing-rules.md).

Out of the box, OCS provides six predefined rules, evaluated against the **OS Name** or **Agent** field of the base inventory and used to assign Templates automatically:

{% columns %}
{% column width="33.33333333333333%" %}

<p align="center"><strong>Field evaluated</strong></p>

<p align="center">OS Name</p>

<p align="center">OS Name</p>

<p align="center">OS Name</p>

<p align="center">OS Name</p>

<p align="center">Agent</p>

<p align="center">OS Name</p>
{% endcolumn %}

{% column width="41.66666666666667%" %}

<p align="center"><strong>Value(s) expected</strong></p>

<p align="center">Windows</p>

<p align="center">Ubuntu, Debian</p>

<p align="center">Redhat, Centos, Alma, Rocky</p>

<p align="center">Mac</p>

<p align="center">OCS-NG</p>

<p align="center">SNMP</p>
{% endcolumn %}

{% column width="24.999999999999986%" %}

<p align="center"><strong>Template</strong></p>

<p align="center">Windows</p>

<p align="center">Debian based</p>

<p align="center">RHEL based</p>

<p align="center">macOS</p>

<p align="center">Legacy</p>

<p align="center">Generic SNMP</p>
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}

#### **Notes on automatic assignment:**

* Rules are evaluated with each incoming inventory.
* If no rule matches, the asset will only report using the base inventory.
* Template assignment can also be switched to manual selection per device. More details are available on the [Managing Rules](https://documentation.ocsinventory-ng.org/administrator-docs/server-setup/configuration/advanced/managing-rules.md) page.
  {% endhint %}


---

# 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://documentation.ocsinventory-ng.org/quickstart-guides/for-users/base-and-template-inventory.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.
