> For the complete documentation index, see [llms.txt](https://docs.timvero.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.timvero.com/timveroos-admin-panel-documentation/v.8.2/setup/07-data-integration.md).

# Data Integration

## Overview

Configure Feature Store mappings, Metrics Engine calculations, and Covenants for data transformation, indicator calculation, and compliance monitoring.

## What You'll Configure

| Component          | Purpose                                    |
| ------------------ | ------------------------------------------ |
| **Feature Store**  | Data mappings from external sources        |
| **Metrics Engine** | Calculated indicators from mapped data     |
| **Covenants**      | Compliance rules validated against metrics |

## Configuration Guides

### [Feature Store](/timveroos-admin-panel-documentation/v.8.2/setup/07-data-integration/feature-store.md)

Configure mappings that extract and transform data from external sources.

**What you'll configure:**

* Data source mappings
* Field transformations

**Time to complete:** 2-4 hours per mapping set

***

### [Metrics Engine](/timveroos-admin-panel-documentation/v.8.2/setup/07-data-integration/metrics-engine.md)

Create calculated metrics based on Feature Store data.

**What you'll configure:**

* Metric definitions
* Calculation expressions
* Subject type associations

**Time to complete:** 30-60 minutes per metric

***

### [Covenants Setup](/timveroos-admin-panel-documentation/v.8.2/setup/07-data-integration/covenants-setup.md)

Configure covenant rules for compliance monitoring.

**What you'll configure:**

* Covenant definitions
* Metric associations
* Validation expressions
* Execution schedules (event-driven or scheduled)
* Anchored value configuration

**Time to complete:** 1-2 hours per covenant

***

## Dependency Chain

Covenants depend on a chain of configurations:

```
Data Source → Mapping (Feature Store) → Metric (Metrics Engine) → Covenant
```

Configure in this order to ensure dependencies are available.

## Prerequisites

* Development team has configured data sources on the Building Platform
* [Products](/timveroos-admin-panel-documentation/v.8.2/setup/03-products.md) configured (for covenant-product associations)

## Related Operations

Once configured, see how data integration affects operations:

* [Covenants & Anchored Values (OPS - Origination)](/timveroos-admin-panel-documentation/v.8.2/ops/01-origination/covenants-anchored-values.md) - Viewing anchored values at origination
* [Covenant Monitoring (OPS - Servicing)](/timveroos-admin-panel-documentation/v.8.2/ops/02-servicing/covenant-monitoring.md) - Monitoring and resolving covenant breaches

## Next Steps

After configuring data integration, proceed to:

* [Analytics](/timveroos-admin-panel-documentation/v.8.2/setup/08-analytics.md) - Configure BI dashboard catalog

***

*For additional support, consult your implementation team.*


---

# 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:

```
GET https://docs.timvero.com/timveroos-admin-panel-documentation/v.8.2/setup/07-data-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.