> 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/id/iot-query/schema-overview/bronze-layer.md).

# Lapisan data mentah

Lapisan data mentah menyimpan entitas bisnis, telemetri perangkat, dan catatan aset dalam tiga skema. Telusuri tabel utama dan format bidang untuk analisis SQL langsung

Lapisan data mentah berisi 3 skema data yang berbeda, masing-masing melayani aspek yang berbeda dari platform telematika dan intelijen bisnis:

* [`raw_business_data`](/docs/analytics/id/iot-query/schema-overview/bronze-layer/raw-business-data.md) - berisi tabel, atribut, dan nilai yang terkait dengan informasi bisnis, seperti Kendaraan, karyawan, geofence yang ditambahkan oleh pengguna, dll.
* [`raw_telematics_data`](/docs/analytics/id/iot-query/schema-overview/bronze-layer/raw-telematics-data.md) - berisi tabel, atribut, dan nilai yang terkait dengan data telematika yang dikirim dari perangkat yang dipantau, seperti lokasi, input, output, dan peristiwa.
* [BDR (Repositori data bisnis)](/docs/analytics/id/iot-query/schema-overview/bronze-layer/bdr.md) - berisi tabel untuk manajemen Aset dan inventaris, termasuk jenis aset yang dapat dikonfigurasi, Kolom isian, hubungan aset, dan data geospasial untuk pelacakan sumber daya organisasi.

Setiap skema dioptimalkan untuk domain data dan pola aksesnya yang spesifik, sehingga memberikan cakupan menyeluruh untuk kebutuhan operasional, telematika, dan manajemen Aset.


---

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