> 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/iot-query/schema-overview/transformation-layer/common-transformations.md).

# Common transformations

Ready-made analytical entities in the Transformation layer, available to query immediately and adaptable through Transformation Builder

The Transformation layer includes a set of common transformations developed and maintained by Navixy. These transformations run automatically on a schedule and populate the `processed_common_data` schema with normalized analytical entities derived from raw telematics and business data.

You can start querying this data immediately after connecting to IoT Query — no configuration required. Each transformation produces a specific table with a documented output schema, update schedule, and processing logic.

{% hint style="info" %}
To build a custom version of any listed transformation, download the corresponding workflow template from the [Templates](/docs/analytics/iot-query/schema-overview/transformation-layer/transformation-builder/templates.md) page and import it into Transformation Builder.
{% endhint %}

## Available transformations

The table below lists transformations Navixy maintains in `processed_common_data`. Each entry links to a dedicated page covering the output schema, the algorithm that produces the rows, and the customization options you can apply when building a derived workflow in `processed_custom_data`.

<table><thead><tr><th width="148">Transformation</th><th width="273">Table</th><th>Description</th></tr></thead><tbody><tr><td><a href="/docs/analytics/iot-query/schema-overview/transformation-layer/common-transformations/trips.md">Trips</a></td><td><code>processed_common_data.trips</code></td><td>Vehicle trips derived from raw telematics data, including start and end times, distance, speed statistics, and zone detection.</td></tr><tr><td><a href="/docs/analytics/iot-query/schema-overview/transformation-layer/common-transformations/sensor-data-aggregation.md">Sensor data aggregation</a></td><td><code>processed_common_data.sensors_data_by_hours</code></td><td>Hourly aggregates of sensor readings, including average, minimum, and maximum values, fuel calibration interpolation, and human-readable enrichment.</td></tr><tr><td><a href="/docs/analytics/iot-query/schema-overview/transformation-layer/common-transformations/rule-based-driver-events.md">Rule-based driver events</a></td><td><code>processed_common_data.rule_based_driver_events</code></td><td>Real-time driving violation events detected from telematics, ignition state, and sensor data, including harsh driving, speeding, idling, and RPM violations.</td></tr><tr><td><a href="/docs/analytics/iot-query/schema-overview/transformation-layer/common-transformations/input-change-events.md">Input change events</a></td><td><code>processed_common_data.input_change_events</code></td><td>Discrete input changes matched against configured <code>input_change</code> rules, including the triggering rule, input number and value, and zone context.</td></tr></tbody></table>

## Next steps

* [**Trips**](/docs/analytics/iot-query/schema-overview/transformation-layer/common-transformations/trips.md): Output schema, algorithm description, customization options, and workflow template download.
* [**Sensor data aggregation**](/docs/analytics/iot-query/schema-overview/transformation-layer/common-transformations/sensor-data-aggregation.md): Output schema, algorithm description, bucket size variations, and workflow template download.
* [**Rule-based driver events**](/docs/analytics/iot-query/schema-overview/transformation-layer/common-transformations/rule-based-driver-events.md): Driving violation events evaluated against the alert rules configured on your account.
* [**Input change events**](/docs/analytics/iot-query/schema-overview/transformation-layer/common-transformations/input-change-events.md): Discrete input changes matched against configured `input_change` rules, refreshed every 15 minutes.
* [**Templates**](/docs/analytics/iot-query/schema-overview/transformation-layer/transformation-builder/templates.md): Download workflow templates for common transformations and import them into Transformation Builder.
* [**Transformation layer**](/docs/analytics/iot-query/schema-overview/transformation-layer.md): How the Transformation layer organizes processed data into schemas and how to query it.
* [**Transformation Builder**](/docs/analytics/iot-query/schema-overview/transformation-layer/transformation-builder.md): Design and adapt transformation workflows using the visual interface.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/analytics/iot-query/schema-overview/transformation-layer/common-transformations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.