> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/analytics/es/iot-query/schema-overview/bronze-layer.md).

# Capa de datos brutos

La capa de datos brutos almacena entidades de negocio, telemetría de dispositivos y registros de activos en tres esquemas. Explore las tablas clave y los formatos de campo para el análisis SQL directo

La capa de Datos brutos contiene 3 esquemas de datos distintos, cada uno orientado a diferentes aspectos de la plataforma de telemática e inteligencia de negocios:

* [`raw_business_data`](/docs/analytics/es/iot-query/schema-overview/bronze-layer/raw-business-data.md) - que contiene tablas, atributos y valores relacionados con la información de negocio, como Gestión de vehículos, empleados, geocercas agregadas por los usuarios, etc.
* [`raw_telematics_data`](/docs/analytics/es/iot-query/schema-overview/bronze-layer/raw-telematics-data.md) - que contiene tablas, atributos y valores relacionados con los datos telemáticos transmitidos desde dispositivos bajo monitoreo, como ubicaciones, entradas, salidas y eventos.
* [BDR (Repositorio de datos de negocio)](/docs/analytics/es/iot-query/schema-overview/bronze-layer/bdr.md) - que contiene tablas para la gestión de Activo y de inventario, incluidos tipos de Activo configurables, campos personalizados, relaciones entre Activo y datos geoespaciales para el seguimiento de recursos organizacionales.

Cada esquema está optimizado para su dominio de datos y patrones de acceso específicos, y ofrece una cobertura integral de las necesidades operativas, telemáticas y de gestión de Activo.


---

# 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://navixy.com/docs/analytics/es/iot-query/schema-overview/bronze-layer.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.