# Consumptions Monitoring

Consumptions monitoring is the One Platform area used to inspect product usage after a service starts producing measurable activity.

The page lets operators select a customer, choose one of the customer's products, and review the metrics recorded for that product over time.

## Main Capabilities

| Capability | Description |
|  --- | --- |
| Customer selection | Select the customer or monitoring unit whose usage must be inspected. |
| Product selection | Choose the product context for which metrics are available. |
| Product overview | Review the product consumption summary and the available metrics. |
| Metric detail | Inspect a metric with yearly, daily, and attribute-based views. |
| Attribute analysis | Break down a metric by the attributes attached to the consumption records. |


## Business Relation Context

Every consumption belongs to a `BusinessRelation`.

A Business Relation is the operational context that connects usage to:

| Context | Meaning |
|  --- | --- |
| Product | The product or service that generated the usage. |
| Customer or monitoring unit | The consumer context whose usage is being monitored. |
| Legal entity | The organization or legal entity responsible for the relation. |
| Integrator | The product application or integration that sends the usage data. |
| Consumer path | The customer hierarchy used for aggregation, reporting, or billing support. |


The Business Relation Identifier, often called BRI, is the identifier that product applications use when sending consumptions to One Platform. It ensures that usage is stored under the correct product and customer context.

Why the BRI matters
Consumptions are not interpreted only by product name or customer name. The BRI is the stable technical reference that tells One Platform which business relation the consumption belongs to.

## Customer Selection

The monitoring page starts from a customer selection.

Use the customer selector to choose the customer or monitoring unit whose product usage must be inspected. The selected consumer determines which products and Business Relations are available in the next view.

## Product Selection

After selecting the customer, choose the product to inspect.

The product list represents the products for which One Platform has a usage context for the selected customer. Behind the scenes, each selectable product is backed by one or more Business Relations.

## Product Detail

The product detail view summarizes the consumption context for the selected customer and product.

Use this view to identify:

- the selected customer or monitoring unit;
- the selected product;
- the available product metrics;
- the latest or aggregated values shown by the portal;
- the period currently used by the monitoring view.


## Metric Detail

A product can expose one or more metrics. A metric defines what is measured, for example documents, transactions, requests, storage, or another product-specific unit.

Open a metric to inspect how the value changes over time and which dimensions are available for analysis.

## Time-Based Views

Metric values can be reviewed at different time granularities.

The yearly view gives an aggregated overview of usage across the selected year.

The daily view is used to inspect usage for a specific day or shorter operational period.

## Attribute-Based Views

Attributes describe qualitative dimensions of a consumption. They explain what the usage refers to inside the product domain.

For example, a product can use attributes to distinguish document types, channels, operation categories, countries, or other product-specific dimensions.

When more than one attribute dimension is available, the portal can expose a more detailed breakdown.

## Data Model

Each consumption record is interpreted through these elements:

| Element | Purpose |
|  --- | --- |
| Business Relation | Identifies the product, customer context, legal entity, integrator, and consumer path. |
| Product metric | Defines what is measured. |
| Value | Usage amount recorded for the metric. |
| Timestamp | When the usage event happened. |
| Datestamp | Date used to group usage in monitoring and aggregation views. |
| Attributes | Optional dimensions used to classify and break down the usage. |


## Related Sections

- [Key Concepts - Consumptions](/products/oneplatform/one-platform-knowledge-center/01-get-started/02-key-concepts/key-concepts#consumptions)
- [Customer Management](/products/oneplatform/one-platform-knowledge-center/03-products-and-modules/01-web-platform/customer-management)
- [Contracts Management](/products/oneplatform/one-platform-knowledge-center/03-products-and-modules/01-web-platform/contracts-management)
- [Credit Management](/products/oneplatform/one-platform-knowledge-center/03-products-and-modules/01-web-platform/credit-management)
- [Retrieve Consumptions](/products/oneplatform/one-platform-knowledge-center/04-api-and-integration/integration-guides/retrieve-consumptions)