# Core data model

A Monitoring record consists of an authorisation/licence and one or more defined monitoring scopes.

The basic hierarchy is:

```
<div class="relative w-full mt-4 mb-1"><div class=""><div class="contents"><div class="relative"><div class="h-full min-h-0 min-w-0"><div class="h-full min-h-0 min-w-0"><div class="border border-token-border-light border-radius-3xl corner-superellipse/1.1 rounded-3xl"><div class="h-full w-full border-radius-3xl bg-(--code-block-surface) corner-superellipse/1.1 overflow-clip rounded-3xl [--code-block-surface:var(--bg-elevated-secondary)] dark:[--code-block-surface:var(--composer-surface-primary)] lxnfua_clipPathFallback"><div class="relative"><div class="pe-11 pt-3"><div class="relative z-0 flex max-w-full"><div class="q9tKkq_viewer cm-editor z-10 light:cm-light dark:cm-light flex h-full w-full flex-col items-stretch ͼd ͼr" dir="ltr" id="bkmrk-authorisation-%2F-lice-1"><div class="cm-scroller"><code><span>Authorisation / Licence
│
├── Scope 1
│   ├── Product
│   ├── Tariff Heading
│   ├── Quantity limit
│   ├── Value limit
│   ├── Period
│   └── Monitoring rules
│
├── Scope 2
│   ├── Product
│   ├── Tariff Heading
│   ├── Quantity limit
│   └── ...
│
└── Documents</span></code></div></div></div></div></div></div></div></div></div></div></div></div></div>
```

A Product is an existing BzCtrl master-data object, referring to the Taric service.

A Product may therefore occur in multiple monitoring scopes, depending on the authorisation.

The scope must support the relevant dimensions required by the particular licence. Not every monitoring record necessarily has both a quantity and a value limitation.